- The Question: “Should We Implement a Tool First?”
- Management Decision Layer (Why)
- Tools are Observation Devices, But Not Ideal for Initial Observation
- The Choice of Manual Observation
- Three Values Gained from Manual Observation
- ① Decision Points are Exposed
- ② Unnecessary Data Becomes Apparent
- ③ The Ability to Revert is Maintained
- Specialist Implementation Layer (How)
- Conditions for Moving from Manual Observation to Tool Implementation
- What Happens in Organizations that Rush Tool Implementation
- Common Misconceptions
- Misconception ①: Manual Work is Outdated
- Misconception ②: You Can’t Improve Without a Tool
- Final Questions to Check with This Decision
- Summary (No Single Correct Answer)
The Question: “Should We Implement a Tool First?”
When a new task or challenge emerges, the first option many organizations consider is “implementing a dedicated tool.” The idea that introducing SaaS will enable visualization and that manual work is inefficient to be avoided seems logical at first glance. However, getting this management decision wrong can lead to a situation where tool implementation becomes a *substitute for observation*, potentially solidifying processes without a clear understanding of reality.
Management Decision Layer (Why)
Tools are Observation Devices, But Not Ideal for Initial Observation
Tools are designed for processing large volumes of data, continuous operation, and standardized input. What is needed during the launch or assessment phase of a task, however, is to roughly grasp what is happening, even if it’s messy. Introducing a tool at this stage pulls thinking toward input fields, and work begins premised on the tool. The result is a structure where operation becomes the goal rather than observation, and the mere form of the work becomes fixed before the reality is understood.
The Choice of Manual Observation
Manual observation is a method of temporarily and reversibly recording reality using spreadsheets, notes, or simple logs. While it may seem inefficient at first glance, this initial “messiness” holds significant meaning in the management decisions of small and medium-sized enterprises.
Three Values Gained from Manual Observation
① Decision Points are Exposed
It becomes clear where confusion arises and which decisions occur frequently. Exposing the moments when people are thinking—moments that would be hidden by a tool—is valuable information for later organizational design and delegation of authority.
② Unnecessary Data Becomes Apparent
Before implementing a tool, you can separate truly necessary information from information that will likely go unused. Keeping business processes simple from the start by not adding unnecessary data items is easier than deleting them later.
③ The Ability to Revert is Maintained
If something doesn’t fit, you can easily stop or change how you record it. Maintaining this reversibility (the ability to go back) in the observation process itself enables flexible management decisions.
Specialist Implementation Layer (How)
Conditions for Moving from Manual Observation to Tool Implementation
Only after going through manual observation and confirming the following states should you consider implementing a tool.
- Decision patterns have stabilized.
- Input items have naturally solidified.
- Observation costs have become clear.
Tool implementation in this state functions not as a substitute for decision-making, but as an extension of observation.
What Happens in Organizations that Rush Tool Implementation
Skipping manual observation and implementing a tool leads to an increase in unused fields and more complex operational rules. Furthermore, a “fear of cancellation” often emerges, resulting in a reversal where the tool itself becomes the goal, and the crucial observation is left behind.
Common Misconceptions
Misconception ①: Manual Work is Outdated
Manual work is not outdated; it is simply following the correct sequence of observation and understanding.
Misconception ②: You Can’t Improve Without a Tool
What’s needed for improvement is understanding reality and separating decisions. Tool implementation can be considered at the stage of solidifying business processes that follows.
Final Questions to Check with This Decision
Are you in an operational phase or an observation phase? Can you explain the phenomenon without a tool? Is it a stage where solidification is not a problem? If you cannot answer these, you may not yet be at the stage to implement a tool.
Summary (No Single Correct Answer)
Tool implementation is not a substitute for observation. In the initial stages, reversible manual observation is the safest approach. Only after business decision patterns and necessary information have solidified should you begin considering tool implementation. The management decision of “whether to implement a tool” can be made *after* observation is complete. This is a core step toward efficient business improvement and sustainable organizational design.


Comments