Before Adding Staff, Deconstruct and Visualize Workflows in a System

Is “We’re Busy, So We Need More People” Really the Right Call?

When facing a perceived labor shortage, many organizations reflexively conclude, “We can’t manage without more staff.” However, this decision often jumps to a solution without first identifying the root problem. Before adding headcount, you must pause and ask: Can you explain what tasks are being performed, how often, and at what workload?

The Management Decision Layer (Why)

You Can’t Scale What You Can’t See

The decision to hire more people carries implicit assumptions: that you have a grasp of the entire workflow, understand where bottlenecks are, and know that adding staff will solve the problem. In reality, work is often discussed in terms of “feeling” or “busyness.” Hiring under these conditions typically leads to more people without understanding the cause of the busyness, resulting in increased management and coordination costs.

The Meaning of Deconstructing Work “in a System”

Here, “system” does not refer to major IT investments. Minimal mechanisms like spreadsheets, task management tools, or simple workflows are sufficient. The key is to externalize the work from people’s heads.

The Specialist Implementation Layer (How)

What Deconstruction and Visualization Always Reveal

When you lay out workflows in a system, facts emerge: there are more routine tasks than imagined, decision-making is concentrated in specific steps, and some tasks lack clear ownership. Often, the conclusion is not a lack of people, but a lack of visibility into the structure.

The Unit of Deconstruction is “Decisions,” Not “Tasks”

A common mistake is deconstructing work at the task level. From the perspective of reversible management decisions, the unit should always be a “decision.” By listing “what is being decided here,” “the criteria for the decision,” and “where the outcome impacts,” you can separate decisions that should be delegated, those that can be standardized or automated, and those that are unnecessary.

Three Effects of Visualization

① Hiring Decisions Become Concrete

You can explain, based on facts rather than feelings, what kind of decision-maker is needed and the approximate workload involved.

② Alternatives to Hiring Emerge

You can realistically consider options like systemization, outsourcing, or eliminating/consolidating tasks.

③ Room to Reverse Decisions Remains

With a clear structure, adjustments like reallocating resources, repositioning decision points, or stepping back to redesign become easier. This is the first step toward building an organization with reversibility.

Common Misconceptions

Misconception ①: We’re too busy to deconstruct our work

A state of constant busyness is precisely a sign that work is not structured. Without deconstruction, the busyness becomes a permanent feature of your structure.

Misconception ②: Visualization will confuse the team

The cause of confusion is not visualization itself, but the surfacing of previously hidden realities. Ignoring these and simply adding staff creates far greater confusion in the medium to long term.

Final Questions to Ask Before Making This Decision

Are there tasks that could be resolved without adding staff? Where is decision-making concentrated? Are there any fundamentally unnecessary tasks included? If you cannot answer these, there is value in first deconstructing and visualizing your workflows.

Summary (No Single Answer)

Before adding staff, externalize your workflows. Deconstruct by decisions, not tasks. Visualization is a tool for enabling reversibility. Whether to hire more people is a question to consider after you can see the work clearly. This is the core of sound, reversible management decision-making for SMEs.