Many management problems appear to occur during execution, but in reality, they are already determined before the work even begins.

You only start chasing progress when a project is already out of control. You only pull people together to align when collaboration has already stalled. You only hold a retrospective when the results fall short. None of these actions are wrong, but they share one thing in common: management intervenes too late.

They happen at the stage where “results have already begun to take shape”—they are post-hoc corrections, not pre-hoc design.

I once mistook this kind of busyness for management competence. Wherever there was a problem, I showed up. Wherever there was a risk, I stepped in. In the short term, the organization seemed stable. But in the long term, it became increasingly dependent on individual judgment. The system didn’t get stronger; the manager was simply forced to become a buffer.

Over time, I came to realize a more fundamental issue: if management always exerts its force during execution, it is essentially gambling against probability.

Once a task is set in motion, variables multiply exponentially. Differences in understanding, changes in context, and information decay are all amplified during execution. The harder you push during the process, the more it reveals how much ambiguity was left unresolved beforehand. And that ambiguity could have been addressed in advance.

Truly effective management often happens where things have “not yet occurred.”

For example, before tasks are broken down, clarify “under what circumstances can decisions be made autonomously, and when must they be escalated?” Before a plan is finalized, define “which failures are we willing to pay for?” As soon as a goal is proposed, align on “is this an exploratory goal or a delivery goal?”

These discussions may seem slow and even frustrating in the moment. But their value lies in this: they compress the uncertainty of the execution phase.

Once you enter the execution phase, the team is no longer asking “what should we do?” but rather “by which principle should we act?”

From this perspective, shifting the focus of management forward is essentially doing one thing: turning implicit judgments into explicit consensus in advance.

The reason many organizations experience constant friction during execution is not a lack of capability, but that people are operating with different “built-in rules” for making decisions. When a manager constantly intervenes during execution, they are temporarily unifying those rules on the fly. But this kind of unification is neither replicable nor scalable.

The significance of pre-process management is to complete this “rule alignment” ahead of time.

There is another often-overlooked point: when management’s focus stays on execution for too long, the organization gradually develops a dangerous psychological expectation—“someone will step in to save the day eventually.”

Once this expectation takes hold, individual judgment naturally deteriorates. Not because people are lazy, but because the system rewards “waiting for instructions.” Over time, the busier the manager gets, the more passive the team becomes. What looks like seamless coordination is actually collective degradation.

Shifting management forward sends a strong signal to the organization: judgment is not concentrated at the last moment, but distributed from the very beginning.

This also reshapes the role of the manager. You are no longer the “final arbiter” in the execution chain, but the “designer” of the decision-making environment. Your focus shifts from whether things are going the way you want to: if you weren’t there, would things still go roughly right?

Of course, this style of management doesn’t feel “satisfying” in the moment. It lacks immediate feedback and is hard to justify with short-term results. You do a lot of invisible preparation that doesn’t map directly to any single outcome. But over time, it becomes clear that the periods with the fewest problems are often the periods when management is most effective.

So, shifting the focus of management from in-process to pre-process is not about managing less, but about managing differently. It’s not about solving problems faster, but about making fewer problems occur. It’s not about pursuing the correctness of every intervention, but about pursuing the long-term stability and self-consistency of the system.

If the managers in an organization become increasingly “quiet” and yet firefighting becomes rare, that is often not a sign of retreat, but a sign that management has truly begun to work.