The Capacity Building Stack
A practical companion to the Enactment Arc
In the first two pieces of this series, I introduced the Enactment Arc and then looked at how it breaks under pressure. The arc gave us a way to map how agency moves from signal to action. The failure modes showed us what distorts that movement when stress enters the picture.
But diagnosis alone is not enough. Once I can see where the arc is breaking, the real question is: what needs to be built in response?
That is where the Capacity Building Stack comes in.
Before I get into the stack itself, I want to say what I mean by capacity, because it is one of those words that can sound vague or faintly self-improving.
I do not mean it that way.
Capacity is simply what makes a different response available when the moment comes. It is what holds under pressure. It is what lets insight become action rather than just admiration. A person can be highly self-aware and still buckle when things get hard. A leader can understand the pattern intellectually and still repeat it. A team can have strong values on paper and still react badly when the stakes rise.
That is not necessarily a failure of honesty or intelligence. Often it is a failure of capacity. The needed muscle has not been built strongly enough yet.
This is why I have grown less interested in breakthrough language on its own. Breakthroughs matter. Insight matters. But if none of it changes what becomes possible in the next real moment, something is still missing. Capacity is what closes that gap.
The stack mirrors the arc
Every stage of the arc depends on a different ability. If the arc shows how agency moves, the stack shows what has to be strong enough for that movement to hold.
Salience capacity is simply the ability to notice what actually matters. It sounds obvious until you try to do it inside chronic overload. We are swimming in noise: media noise, organizational noise, emotional noise, AI-generated noise. Attention gets pulled toward what is loud, new, or emotionally charged rather than what is actually significant. A lot of leadership failure begins right here, before any decision has been made, because the signals being tracked were the wrong ones to begin with.
Desire capacity is where things get more uncomfortable. Once something becomes salient, desire forms around it, and desire is rarely as clean as we like to think. Sometimes what feels like purpose is fear wearing a nicer story. Sometimes what looks like ambition is borrowed desire, goals we absorbed from elsewhere without ever really choosing them. Desire capacity is not about wanting more strongly. It is about wanting more honestly, which means being willing to ask whether the thing you are chasing is actually yours.
Knowledge capacity is usable understanding, not just information. The question is not only “what do I know?” but “what am I only assuming?” High intelligence does not protect against this. Sometimes it makes the problem harder to spot, because fluency can mimic understanding. This matters especially now, when polished output is easy to generate and coherence is easy to perform. Fluency is not truth. Knowledge capacity is what keeps you in honest contact with the difference.
Will capacity is where understanding has to become commitment. This is where most people wobble. They keep reopening the decision, seeking one more signal, one more reassurance. But will can fail in the opposite direction too, hardening too quickly, locking in, treating revision as weakness. Strong will is neither of those things. It is the ability to choose cleanly, stand behind the choice, and still remain genuinely open to being wrong.
Action capacity is less about whether you move and more about whether your movement is grounded. A lot of organizations are highly developed in motion and underdeveloped in coherent action. Meetings get scheduled, features get launched, initiatives multiply, everyone is busy, and yet the underlying confusion stays untouched. Reactive action is not the same as grounded action, even when both look productive from the outside.
Integration capacity is the one I have come to respect most. It is where the lesson actually lands, or fails to. Without it, insight stays cosmetic. The pattern returns, sometimes wearing new clothes, sometimes not even bothering with that. A lesson is not fully learned until it changes what becomes possible next time. That is the bar integration has to clear.
What I find most useful about the stack is not the list itself
It is the question it lets me ask when something goes wrong.
Instead of “why does this keep happening?” or “why am I like this?” I can ask: what capacity is missing here?
If I am hijacked by noise, the missing capacity is probably attention and discernment. If I am chasing something that does not actually feel like mine, it is probably values clarity. If I am gripping certainty too tightly, it is probably sensemaking. If I cannot seem to commit, it is decision hygiene. If I am moving but not landing anywhere useful, it is coherent execution. If the same pattern keeps returning, it is integration.
That shift moves the question away from vague self-blame and toward something specific and workable. It also makes coaching, leadership development, and facilitation considerably more precise. You do not have to solve everything at once. You just have to see which part of the arc is breaking, and what that particular breakdown is asking you to build.
The point of all this is not optimization
It is not becoming invulnerable to pressure or infinitely improved at everything.
It is restoration.
Pressure is not going away. Overload is not going away. The conditions that strain agency are only getting more demanding, not less. So the work is not to wait for calmer times to do the inner and collective development this moment requires.
The work is to build the capacities that keep action coherent inside the times we are already in.
And the question that guides that work is not “what is wrong with me?” It is: what needs to grow strong enough for a wiser response to actually become possible?
That, to me, is worth taking seriously.
Integration part hit me. Got a concrete example of catching one of the six in yourself in real time? Feels like the actual teaching is in the catch, not the framework