The Army Taught Me a Better Way to Think Under Pressure
The Army didn’t teach me effectual thinking by name. It taught me by putting an artillery unit in Bayji, Iraq and changing the mission constantly. Route clearance. Patrolling. Training and advising Iraqi soldiers who showed up to their own operations with incomplete equipment and complicated loyalties. None of that was in the field manual. The insurgency didn’t care what we were trained for.
What that environment forced on us was a cognitive shift that I didn’t have language for until much later: the move from causal to effectual reasoning. Causal thinking starts with a goal and works backward, assembling the resources and steps required to reach it. It is linear, optimized, and well-suited to stable conditions where the environment between now and the objective can be reasonably modeled. Most of what business schools teach is causal. Most corporate planning processes are causal. The logic is sound when the assumptions hold.
Effectual thinking inverts the sequence. You start with what you actually have: the team in front of you, the capabilities they carry, the information available at this moment. From that foundation you ask what is achievable, and you adjust as conditions shift. The unexpected is not a failure of planning. It is data. The plan is a departure point, not a contract.
Why the Distinction Matters Beyond a Warzone
The counterinsurgency environment was an extreme case, but the underlying dynamic is not rare. Any organization operating in a fast-moving market, a regulatory environment under revision, or an industry being reshaped by technology is dealing with the same structural problem: the conditions that made the plan sensible are changing faster than the plan can be updated.
AI is accelerating this. The organizations watching their competitive assumptions get compressed from years to months are discovering that their planning infrastructure, however sophisticated, cannot respond quickly enough. The bottleneck is not data or tools. It is whether the leadership layer can think and decide effectively when the environment refuses to cooperate with the roadmap.
The leaders who can do that have internalized effectual reasoning. They do not wait for certainty. They do not treat an outdated plan as a source of authority. They read what is in front of them, recalibrate with the resources at hand, and move.
The Failure Mode Organizations Build For Themselves
The organizational failure mode is not a lack of planning. It is an over-investment in causal capacity at the expense of effectual capacity. Companies hire planners. They reward milestone delivery. They build incentive structures that favor execution fidelity over situational judgment. That works well when the environment holds. When it does not, the whole system stalls, because no one is equipped or authorized to adapt without a revised plan.
I watched this play out in Iraq with units that had rigid task organizations and no culture of initiative below a certain grade. When conditions changed, which they always did, decisions had to climb back up the chain before they could come back down. The delay was not bureaucracy in the pejorative sense. It was the structural result of building a system that expected causality: if we execute the plan correctly, the outcome follows. The insurgency did not follow.
The corporate equivalent is slower, less dramatic, and harder to diagnose because the environment rarely signals failure as clearly as a firefight does. But the mechanism is identical. The system is calibrated for a world it no longer inhabits, and the leadership layer lacks the cognitive wiring to close that gap in real time.
What Leaders Actually Control
The fix is not to abandon planning. Causal thinking remains the right tool for stable operations, defined processes, and environments where execution quality is the primary variable. Abandoning it in favor of pure improvisation is not effectual thinking. It is just chaos.
The question is whether your organization has built effectual capacity alongside its causal infrastructure. That means developing leaders who can make sound decisions with incomplete information, who treat constraints as inputs rather than obstacles, and who are authorized to adapt without waiting for permission from a planning cycle. It also means creating accountability systems that can distinguish between a bad outcome from a sound decision and a bad outcome from poor judgment. Those are different problems. Treating them the same way destroys the very adaptive capacity you are trying to build.
In Iraq, the leaders who were most effective were not the ones with the best plans. They were the ones who could read a situation accurately, commit to a course of action with the assets available, and update without ego when the situation changed. That is a teachable disposition. Most organizations are not teaching it.
The real question for any executive looking at the next two to three years is not whether the plan is good. It is whether the people executing it can function when the plan stops being true. The answer to that question will determine more than any strategy document.