Decision Pattern 10｜Is it a People Problem or a Design Problem?

The Conclusion: “It’s That Person’s Fault”

When trouble or stagnation occurs within an organization, one conclusion emerges most quickly and forcefully: “That person lacks the skills,” “They’re not responsible enough,” or “They’re not a good fit.” While this judgment is easy to understand, offers a quick fix, and leads to immediate action, it is also the judgment that overlooks the most significant underlying problems.

Management Decision Layer (Why)

Labeling it a “People Problem” Stops Design Thinking

When a problem is treated as a “people problem,” organizational thinking stops at “Let’s rehire,” “Let’s replace them,” or “Let’s train them.” This isn’t necessarily wrong in itself. However, if you replace a person without considering *why* they made that decision, the same problem will recur, leading to a cycle of repeatedly hiring for the same role. This is a state where the critical thinking needed to question the “design” of the organization or its processes has stopped.

The Decision to Frame it as a Design Problem

Framing it as a design problem is not simply about not blaming the individual. It involves verifying in the moment: “What decision was required?” “Were the criteria for the decision shared?” “Was the scope of responsibility appropriate?” In other words, it requires a reversible management decision that asks, “Would this problem have occurred even with a different person?”

Three Typical Patterns That Look Like People Problems

① No Clear Decision Criteria Exist

When the correct answer isn’t verbalized and decisions are left to individual intuition, the results will vary no matter who is in charge.

② Ambiguous Scope of Responsibility

When it’s unclear how much one is allowed to decide and there is no defined recovery procedure for failures, decision-making slows down and becomes overly conservative.

③ The Design and Reality Are Misaligned

In cases where systems exist but aren’t used, or roles differ from what was intended, the problem lies not with the person, but with a design that hasn’t kept pace with reality.

Specialist Implementation Layer (How)

Three Questions to Distinguish the Problem

To distinguish between a “people problem” and a “design problem,” the following three questions are effective:

• Would anyone have been confused by this decision?
• Were the decision criteria shared in advance?
• Was a recovery method designed in case of failure?

If any of these are lacking, it’s highly likely to be a design problem.

Cases That Should Be Treated as People Problems

“Reversible Management,” which prioritizes decisions that allow for course correction, does not mean treating everything as a design problem. Cases involving clear violations of standards, intentional disregard of rules, or failure to act despite understanding one’s responsibilities require judgment as people problems. The crucial point is maintaining the sequence: “First, question the design.”

Common Misconceptions

Misconception ①: Treating it as a Design Problem is Being Soft

Reviewing the design is not about diluting individual accountability. On the contrary, it is the shortest route to preventing the same failure from happening again and strengthens organizational design.

Misconception ②: Not Admitting People Problems Leads to a Lax Organization

The cause of a lax organization is rarely a lack of reprimands or discipline, but rather the “absence of a decision-making structure.” Autonomous action only emerges when there are proper work processes and delegated authority.

The Final Question to Confirm with This Decision

When a problem occurs, the final questions to confirm are:

• Would this problem disappear if we changed the person?
• Would it not have happened if someone else worked under the same design?
• Were the decision criteria and scope of responsibility clear?

If you cannot answer these, the problem likely lies not with the person, but with the design.

Summary (Without Giving a Single Answer)

The conclusion “It’s a people problem” easily leads to a halt in critical thinking and moves you away from a fundamental solution. On the other hand, reviewing it as a “design problem” is a reversible decision that leads to recurrence prevention and organizational strengthening. For SME leaders, what’s crucial is the sequence of this distinction: “Before questioning the person, have you questioned the design?” This is the core of the decision-making pattern that builds a sustainable organization.