Solving Buys Learning, Not Reassurance
Solving is the discipline of designing a move that links action to learning. Most organizations design moves that buy reassurance instead and call it execution.
The room had done the hard part. It could describe its market without flattering itself, it could name what it refused to trade away, and it could finally say in one sentence which problem it was solving. Then the meeting turned into a contest of proposals. Three people had a plan ready. The fastest voice set the agenda, the cleverest slide got the nods, and by the end there was a deck, an owner, and a date.
Everyone left relieved. Six weeks later nobody could say what the organization had learned. The plan had produced activity, status updates, and a revised timeline. It had not produced information. When the numbers came in soft, the room could not tell whether the move was wrong or whether it had been executed badly, so it argued about both.
The misdiagnosis
The usual reading is that this is an execution problem. Discipline slipped, ownership was fuzzy, the operating rhythm needs tightening. The second reading is a resourcing problem: the plan was right and under-staffed. Both readings assume the move itself was sound and only its delivery failed.
Neither one touches the constraint. The move was never designed to teach the organization anything. It was designed to make the discomfort of not knowing stop. That is a different failure, and no amount of operational rigor corrects it, because rigor applied to an untestable move just produces a better-managed guess.
What is Solving?
Solving is the fourth stage of the Progression of Meaningful Response, the discipline of designing a move that links action to learning, so each step either accumulates progress or sends the organization back upstream early enough to still choose. It is where logic, expertise, and method finally earn their keep, because Sense-Making, Meaning-Making, and Framing have already cleared the air.
Two distinctions make it usable. The first separates it from the stage before it. A Frame decides which problem is worth solving. Solving decides what kind of move you are going to make against it. A Frame makes the path possible; it does not make the path obvious. Rooms that skip this distinction treat a clean Frame as permission to start proposing, and proposals are not the same thing as a designed move.
The second distinction is the one that does the work. Some moves are designed to buy reassurance. Others are designed to buy learning. Both look decisive from the outside. Only one accumulates. Reassurance is the more attractive of the two because it reads as care: it promises that people can stop worrying, that the next quarter will behave, that harder execution will make the world cooperate. Under pressure, senior leaders reach for it without noticing — tightening control, demanding certainty from people who do not have it, treating estimates as vows. The system gets efficient inside assumptions that are already decaying.
Solving refuses that. It does not mean acting timidly; it means acting cleanly. Every move carries a hypothesis whether or not anyone writes it down — the quiet belief that justifies the action. If we do this, we believe that will happen, and we believe the cost is worth paying. Making that belief explicit is what turns a plan into something reality can answer.
How do you tell reassurance from learning?
Three signals are worth checking against your own organization this week:
- The move has no stated hypothesis. Ask three people in the room what the organization believes will happen and why. If you get three different answers, or an answer about activity rather than consequence, the move cannot be tested and will not teach.
- Nobody has said what would make you stop. A learning move names, in advance, the signal that sends you back upstream. A reassurance move has only a completion date, which means the only available conclusion is that it finished.
- The plan has no constraints, only intentions. Teams that are stuck are almost never short on ideas. They are short on constraints. Without them, the organization cannot tell whether it is iterating toward something or cycling through preferences.
The third signal is the one leaders resist most, because constraints feel like withholding. Structurally they are the opposite. A constraint removes a category of debate, which is what stops the system from spending attention on choices it cannot afford.
What to do with it
Write the decision record. Not a deck, not a slogan — a short record in full sentences that a person can hold while making a call without you in the room.
State the hypothesis in the language of the actual work, not in strategy vocabulary: if we narrow what we ship for the next ninety days, we will cut rework enough to regain reliability with current customers and learn which demand is real rather than assumed. Then write two or three constraints particular enough that people feel them, including at least one that costs something — a class of deal you will not accept, a form of recovery you will not fund with silent weekend work, a dependency you will not create because it becomes a Future Horizon burden later. End with the review: the same signals, the same room, a fixed interval, and an explicit commitment to return upstream if the hypothesis is not holding.
This costs a quarter of discomfort and some near-term revenue you could have booked. It buys the thing an untested plan cannot: judgment that travels. A solution that only holds when a few senior people are present is not a solution. It is a dependency disguised as strategy.
Accumulation, not motion
Go back to the room that turned a clean Frame into a contest of proposals. Nobody there lacked competence, and nobody needed to be told to move faster. What the room needed was to know which of the proposals on the table could be wrong in a way it would recognize in time.
Solving is not movement. Solving is accumulation others can repeat with integrity. The work that follows it is protecting the space where that repetition happens — but the first honest question is simpler than that: does this move teach us anything, or does it just keep us busy until reality sends us back upstream?
Solving is the fourth stage of the Progression of Meaningful Response, the flow of four disciplines every level of an organization runs.
Solving is developed in The Capability Advantage by Jose J. Ruiz, Volume I of the Built to Endure series.