A follow-up can take five minutes to send and keep returning to mind for days.

Every Monday I put one question at the top of my screen. I call it the Commanding Question. A recent one was: Have I taken action on every real and live opportunity in my funnel?

The wording asked me to look honestly at what was in motion and what I had done about it. Keeping it visible gave me a way to return to that intention as the week filled up.

In this article, I share what I am finding useful about the practice and how to try it with one commitment that keeps drawing your attention.

An instruction tends to feel complete to the person giving it. The missing context is already in their head.

In a recent communications session, the read-back was new to most of the room. What stayed with me was the conversation it opened about assumptions, questions, and how leaders make it easier to find out what someone has understood.

I wrote about the picture behind an instruction, and two questions you can use on your next handoff.

Where is leadership capacity currently limiting growth?

“We need better managers” can describe several different pressure points: authority remains concentrated, managers keep supplying the answers, bench strength is unclear, standards vary across teams, or execution loses clarity as it travels.

Each pattern points to different work, a different starting group, and a different development path.

I closed September's series with a practical way to identify the constraint, choose the people closest to it, and build the smallest useful path around the pressure already visible.

“Hard work is sustained work.”

That was Iain McCorkindale’s answer when I asked him what hard work means. He was describing a long horizon: earning competence, building trust, learning through mistakes, and staying with a mission long enough for something lasting to take shape.

I wanted to interview Iain because he knows what it takes to get complex projects built, and he thinks deeply about the culture, code, and purpose that allow people to deliver them together.

Ten years after he founded M3 Development Management Ltd, it has 36 people across five offices. Its leaders are shaping the next plan, and Iain is making room for them to own it.

I wrote about our conversation and what it taught me about sustained leadership, the DNA of a company, and trusting the people who will carry it forward.

Execution begins before anyone starts executing.

A leadership team can leave the room with a clear priority, a named owner, and a decision everyone believes has been made. The real test begins as that clarity moves through managers, team meetings, one-to-ones, handoffs, and the judgment calls of the working week.

I have written before about strategic clarity, role clarity, and decision clarity. This article looks at the management layer that helps all three survive the trip: expectations, delegation, feedback, and accountability.

These four conversations create much of the operating environment a team experiences.

Bench strength often gets discussed with a name and a nod.

Someone has real potential. A few heads nod. The conclusion forms quickly, often with very little evidence underneath it.

Readiness becomes more useful when it gets specific: ready for what kind of complexity, under which conditions, with what support, and across how many repetitions?

I wrote about the operating signals that make leadership readiness visible, how to design useful stretch opportunities, and how a depth chart turns those observations into a real development path.

One real decision can tell you a great deal about delegation.

Watch what happens after a manager has gathered the information, applied the criteria, and reached a consequential call. Notice whether the decision remains with them, which boundaries become active, and what happens when risk rises.

Organizations learn that boundary through repeated leadership behaviour: decisions that get reopened, approvals that return after ownership was granted, and senior leaders who step back in at the moment authority becomes consequential.

I wrote about where authority actually lives, how judgment develops, and the four elements that make an authority transfer real.

Growth changes the leadership job before it changes the title.

A leader usually notices the added volume first: more meetings, more decisions, more places where the work still seems to require their presence. The deeper shift is in what the organization now needs their leadership to accomplish.

The strengths that carried early growth still matter. As complexity rises, proximity has to create shared visibility, instinct has to become judgment others can use, and capable gap-filling has to become clearer ownership and stronger leadership around the work.

I wrote about that transition, and the three levels where leadership capacity needs to grow: self, team, and system.

Nobody votes on the September speed-up.

The meetings come back. The inbox fills. Response times tighten. Within a week or two, everyone is moving at full tempo again.

It feels inevitable because nobody experienced it as a decision.

The slower weeks gave you a rare look at the organization operating under different conditions.

Some work ran fine with less attention.

Some meetings disappeared and nobody missed them.

Some things mattered more than the calendar had suggested.

That information is easy to lose once momentum returns.

I wrote about the small window leaders have to choose the pace of the coming season before habit chooses it for them.

A vacation schedule can tell you more about succession than a performance review.

Someone senior steps away, and a real gap opens up.

Who notices it?

Who steps toward it without being asked?

Who can keep the priorities of the role intact, make real decisions, and ask for help at the right moments?

Most organizations treat summer coverage as a scheduling problem to solve and then forget.

It is also a live readiness assessment.

I wrote about what those temporary gaps can reveal about judgment, potential, and the actual depth of your leadership bench.