Two of the six making activities connect Need and Resources. Scoping uses what you have to bound what you're pursuing: it reads capacity and shapes ambition accordingly. Provisioning goes the other direction: it uses what you're pursuing to drive what you build capacity for. One constrains. The other invests. When both run together as your dominant attention pair, they create a circuit between preparation and feasibility that can spin indefinitely.
Here's how the loop works. Scoping looks at current capabilities and asks: given what we have, what's a realistic version of this goal? That produces a bounded target. Provisioning picks up that bounded target and asks: what do we need to become to hit it? That produces investment in new capabilities. But new capabilities change the feasibility picture, which re-triggers Scoping. Now you can realistically pursue more. Which means Provisioning has a bigger target to build toward. Which changes what's feasible. Which...
The circuit is self-sustaining. Ambition gets bounded, capacity gets built, ambition expands, capacity gets built again. There's visible progress at every step. Goals are realistic. Investment is purposeful. The work feels responsible.
And nothing gets made.
The system that stays empty
Solution sits outside this loop entirely. The concrete artifact, the thing you're supposedly making, doesn't enter the circuit. Neither Scoping nor Provisioning produces it. Between them, they negotiate what's feasible and develop the capacity to achieve it. The actual achievement requires activities the loop doesn't contain.
This matters structurally, not just practically. Four of the six activities need Solution to function. Specification would translate the bounded need into concrete form, but that form is a Solution artifact. Delivery would turn capacity into tangible output, producing Solution directly. Validation uses Solution evidence to test whether the need is right. Verification uses Solution evidence to improve how you work. All four depend on there being something concrete in the world. And the Scoping-Provisioning circuit produces no concrete thing.
So it's not that these four activities are merely "outside" the loop. They're starved of their essential input. The loop doesn't just neglect Solution. It removes the precondition for the feedback that would correct it.
The person inside this loop isn't lazy. They're not procrastinating in the usual sense. They're doing real cognitive work: assessing constraints, identifying gaps, developing skills, acquiring tools, refining the plan. It has the texture and weight of making. But the thing being "made" is readiness itself. And readiness is not the deliverable.
What the loop feels like from inside
The characteristic experience is perpetual almost-readiness. One more skill to develop. One more tool to acquire. One more constraint to understand. Each step is defensible. None is the step where something gets built.
There's a flavor of risk aversion here, though it doesn't feel like risk aversion from inside. It feels like responsibility. You don't commit to producing something until you're confident you can deliver. But confidence requires capacity. And capacity keeps revealing new requirements. So "ready enough" keeps receding. Not because you deliberately moved the goalposts, but because the goalposts are genuinely far away and your improved vantage point keeps showing you how far.
The order within the pair matters. Someone who leads with Scoping and flows into Provisioning starts by bounding ambition, then builds capacity to match. Their stuckness looks like incrementalism: goals stay modest because capacity constrains imagination, and investment stays conservative because goals were already capped. The circuit spirals inward. Smaller and smaller. Very responsible. Very stuck.
Someone who leads with Provisioning and flows into Scoping starts by surveying what's needed and building toward it, then checks feasibility. Their version oscillates: ambitious capability development that keeps getting trimmed once reality is consulted. Grand plans that get bounded, then new ambitions that stretch slightly beyond, then another trim. Lots of motion. The amplitude may even grow. But output stays at zero.
Teams and organizations
A company that cycles between strategic planning and organizational development without shipping product is running this loop at the organizational level. The strategy retreat produces goals bounded by current capacity. The capability initiative builds toward those goals. Next year's retreat notes the expanded capacity and scopes more ambitious targets. The board sees realistic planning and purposeful investment. What the board doesn't see, because the loop doesn't generate it, is whether any of this produces something the market wants.
Research programs fall here too. The researcher refines the question while building methodological capacity. The question gets sharper. The methods get more sophisticated. Papers don't get written. Not because the researcher can't write, but because writing means committing to the current state of the question and the current capability, and both keep evolving in ways that make commitment feel premature.
The common thread: the loop produces progress along two of three dimensions. Feasibility understanding improves. Capability improves. But concrete output, the thing that could generate feedback, that could be tested against actual need, that could reveal whether all this preparation was pointed in the right direction, stays flat.
The blind spot's blind spot
The deepest problem isn't that nothing ships. It's that the loop has no way of discovering whether its own assumptions are correct.
Scoping produces bounded targets. But are they the right targets? Does the feasibility picture match reality? Those questions require Solution-space evidence: something concrete to test against the world. Validation would answer them, but Validation needs an artifact to evaluate. The loop doesn't produce one.
Provisioning develops capability. But capability for what? Is the capacity being built actually the right capacity? Those questions also require concrete output. Verification would answer them, but Verification needs something to examine. The loop doesn't produce that either.
So the loop can refine endlessly without discovering it's refining in the wrong direction. The bounded target can be a beautifully realistic version of the wrong goal. The developed capability can be a thorough investment in the wrong skills. And the loop, from the inside, can't tell. It would need the empty system to reveal the error. And the empty system stays empty.
Breaking out
The response isn't to stop scoping or provisioning. Both serve real functions. Bounding ambition prevents overcommitment. Building capacity prevents stagnation. When the loop is part of a larger cycle that includes concrete production and testing, it's genuinely valuable.
The response is to make something. Ship something. Before the feasibility analysis is complete. Before the capability is fully developed. Not because those activities don't matter, but because what you make will teach you things about your need and your capability that no amount of Scoping and Provisioning can discover alone.
A prototype tests whether the bounded need was right. A draft reveals whether the developed capability is the right capability. A pilot breaks the loop not by stopping the circuit but by feeding it information from outside its own boundaries.
The readiness you're building has a missing input. And that input only comes from the system your attention doesn't reach.