One of the more disorienting experiences for the senior leader new to civilian is the way decisions get made. Or rather, the way they often do not get made. Or rather, the way they get made several times and then unmade and then made again.
For someone trained inside a chain of command, this looks like dysfunction. It is not, usually. It is a different operating model, and once you understand what it is for, you stop fighting it and start using it.
Military decision-making runs on a model the analysts call the OODA loop. Observe, orient, decide, act. The cycle is intentionally fast. The faster you can run it, the more you outpace the adversary, and outpacing the adversary is most of what matters. The decision is the moment. The decision closes the loop. You move on.
Civilian C-suite decision-making does not run on that model and was not designed to. It runs on a model that is closer to what consensus theorists call a deliberative loop. The cycle is intentionally slow. Information surfaces over weeks. Positions get aired. Coalitions form and dissolve. The decision arrives at the end of the cycle as a consequence of the process, not as the start of the action that follows.
Why does the civilian model run slow? Because in most civilian operating contexts, the cost of a wrong decision at the senior level is higher than the cost of a slow one. The company can usually survive a quarter of indecision. It often cannot survive a single decision that turns out to be wrong in a way that costs the next three years of operating runway. The slow cycle is a risk management mechanism.
The military person reads this and bristles. The military person has spent twenty years inside contexts where the cost of a slow decision is higher than the cost of a wrong one. The OODA loop is not a preference. It is a survival mechanism. The civilian deliberative loop, by the military read, looks like institutional cowardice.
The reframe that helps. The civilian cycle is not slow because the room is afraid. It is slow because the room is structurally distributed, and distributed decisions require time to absorb. There is no commander whose decision binds the room. There are nine people whose decisions, taken collectively, bind the room. Nine people need time. You are one of the nine. You contribute. You wait.
What this means in practice is that the senior leader new to civilian needs to recalibrate two things at the same time.
The first thing is your sense of pace. A decision that should have taken a week is going to take a quarter. The way to survive this is to identify the small number of decisions that actually need to move faster, and to spend your political capital pushing those. Most decisions do not need to move faster. The slow cycle is fine for them. Save the pressure for the ones that matter.
The second thing is your sense of finality. In the military model, a decision was final. The chain absorbed it and acted on it and the decision held. In the civilian model, a decision often is not final the first time it is made. The decision will get re-litigated as new information surfaces. The position you took in week three will be revisited in month five. This is not weakness. This is the system working as designed. The senior leader who treats every decision as final is going to be exhausted by month eight. The senior leader who treats each decision as a way station along a longer track operates with more patience and lasts longer.
None of this is to say the civilian model is better than the military one. They are different models for different operating contexts. The senior leader who can switch registers between them is the leader who lasts at altitude in both. The senior leader who cannot switch reverts to the model they trained on, and the new context rejects them on a slow timeline.
Stop running the OPORD. Run the cycle. It is not what you trained for, but it is the operating system you are in.