Belief Isn’t Enough (Part II)

Development doesn’t always need to be scheduled. But it always needs to be protected.

In the first piece, I wrote about how development becomes conditional under pressure. This is the next layer I’ve been exploring since. That’s the tension I keep coming back to.

When you zoom out and look across different environments, sports, organisations, and cultures, you start to see the same misunderstanding show up again and again. People debate how development should happen: structured or organic, planned or flexible. In reality, the environments that get this right don’t choose one or the other.

There are really two types of development happening all the time.

The first is structured development. This is the part you deliberately design, the one that shows up in the calendar, in individual conversations that go beyond performance review, and in time protected for reflection, even when the week gets busy or results start to tighten. This is where intent lives. It’s where you make it clear, to yourself and to the people around you, that development is not an afterthought.

A coach said it to me simply: “If it’s not in the schedule, it doesn’t exist.” That stuck.

Without this layer, development becomes inconsistent. It depends on energy, personality, and timing. Some people get more of it than others. Some moments are used, others are missed. It becomes uneven without anyone really noticing.

The second type is embedded development. This is less visible but far more powerful. It lives inside the day-to-day. It shows up in the small decisions: a coach choosing to ask a question instead of immediately giving the answer, holding a moment just a few seconds longer after a mistake so there is actually something to learn from, or allowing someone to struggle just enough to figure something out instead of stepping in too early to fix it. This is where behaviour lives, and ultimately, behaviour is what shapes development.

In the best environments I’ve been around and learned from, these two are connected. Structure sets the direction; daily behaviour brings it to life. One without the other doesn’t hold.

If you only rely on structure, development can look good on paper but fail to transfer. Conversations happen, plans are made, boxes are ticked, but when the pressure increases, nothing really changes. If you only rely on development happening organically, it becomes fragile. It depends on who is leading, how confident people feel, and how much time seems available. That’s the key shift for me; we don’t schedule development to control it. We schedule it to protect it.

When things speed up, when results start to matter more, when the noise increases, the unscheduled things are always the first to go. Not intentionally. Not consciously. Just structurally. Attention narrows. Priorities tighten. And anything that isn’t clearly anchored gets pushed aside.

So no, development doesn’t always need to live in the schedule. But if there is nothing in your environment that guarantees space for it, then you are relying on people to choose development in moments where performance is under pressure. And that’s a difficult ask, for players, staff, and leaders. Because in those moments, people don’t rise to intention. They fall back on what the environment has consistently reinforced.

That’s the part I’m becoming more aware of in my own work; not just where we talk about development, but where we actually protect it. The goal isn’t to force development into rigid blocks or over-structure something that should stay fluid. The goal is to make sure it is never left to chance.

Because the environments that truly develop people don’t hope it happens. They build for it.

JP