The Pitfall of Systemizing “Intuition”: The Irreversible Structure of Talent Dependency

The Irreversible Trap Between “Personalization” and “Systemization”

“How can we somehow systemize our ace salesperson’s intuition into the organization?” This is a wish many small and medium-sized business owners harbor at least once, and simultaneously, the beginning of a dangerous trap. The two news stories we examine here reflect both ends of this trap.

One is an article about a recruitment company publicly sharing a seminar on organizational methods that do not rely on an “ace’s intuition.” The other is a report on Nexon restructuring its virtual asset-related subsidiaries and reorganizing its business. The former is an attempt to “systemize personal capabilities,” the latter a decision to “restructure a systematized business.” At first glance, they seem to be opposite vectors.

However, both share a hidden “point of no return.” That is the moment when a decision is solidified while the boundary between “human capability” and “work structure” remains ambiguous. This time, we present concrete perspectives for advancing organizational transformation with reversibility while keeping this boundary clear.

Case Study: Behind the Organizational Transformation that Broke Through the “30-Person Wall” in Recruitment

According to the news, Brain Lab Inc. held a seminar on organizational transformation to help companies break through the “30-person scale wall” commonly faced in the recruitment business. Its core is “systemization that does not rely on an ace’s intuition.”

Here, the “irreversible decision” many managers make follows this flow:

1. Attempting to model “that person’s method”: Making the top salesperson’s actions and senses “visible” and incorporating them into manuals and workflows.
2. Fixing the model as the “correct answer”: Applying the created manual to everyone, demanding compliance, and incorporating it into evaluation criteria.
3. Shifting to a “people problem”: Employees who cannot follow the model are evaluated as “lacking ability” or “lacking motivation,” becoming targets for training or personnel replacement.

What is lost in this process is the opportunity to verify “whether that model is truly a universal success factor.” The ace’s success may be supported not only by their personal “intuition” but also by a specific period, a specific customer segment, or support structures from their surroundings that even they are unaware of. Uncritically fixing this as a “structure” and forcing it on everyone leads to an irreversible decision that strips the organization of flexibility and excludes diverse talents for “not fitting the model.”

Designing Reversible “Systemization”: Deconstructing Work and Observing Hypotheses

So, what does “reversible systemization” look like? It involves viewing it not as directly copying “human capability,” but as an experiment to deconstruct and reconstruct “a series of tasks that produce business outcomes.”

Specifically, we design reversibility through the following steps.

Step One: Identify the “bundle of tasks” that produces results (Look at the work, separate from the person)
Instead of the outcome “the ace secures a contract,” list “the ‘bundle of tasks’ they perform in a week: customer contact, information organization, proposal document creation, follow-up, etc.” The key here is to focus not on their “sense” or “way of thinking,” but on actions and their outputs (emails, documents, records) that can be observed externally.

Step Two: Assign a “hypothetical value” to each task (Place it tentatively, without fixation)
Formulate a hypothesis for how each listed task contributes to the final outcome. “Checking industry news every morning” → “Contributes to creating conversation starters (hypothesis).” This hypothesis is merely a “tentative placement,” not an absolute correct answer.

Step Three: Execute an “experiment” within a limited scope and observe
Apply the hypothesis to a limited scope, such as a specific team or period (e.g., a quarter). At that time, evaluate not the “task implementation rate,” but “whether the outcome metrics moved as hypothesized.” If increasing industry news checks does not change conversation starters or contract rates, that hypothesis is rejected. This “rejection” is the core of reversibility. It is positioned not as failure, but as “learning” that pares away unnecessary elements.

Learning from Nexon’s Business Restructuring: The Reversible Termination of a Systematized “Business”

On the other hand, the news about Nexon’s restructuring of its virtual asset-related subsidiaries provides material for considering how to restructure a business that was once systematized and launched in a “reversible form.” The virtual asset (blockchain) business is an area where many companies have entered in recent years, only to be forced to withdraw later. At the time of entry, it was likely given a clear structure (subsidiary, specialized team, budget) as a “future growth business.”

The “irreversible decision” here is to fix the termination of the business with a final label like “failure” or “withdrawal,” burying the decision-making process and learning that led there in darkness. Then, the organization is left only with the emotional memory that “that business was a failure,” unable to leverage the valuable insight of “why we entered, what we observed, and where we deviated from the criteria for continuation” for the next endeavor.

Decide the “Termination Conditions” for Business Experiments in Advance

Start by declaring that new business ventures or subsidiary establishments are grand “experiments.” And always set “termination conditions” in advance for the experiment.

• Observation Metrics: Set unique metrics that measure the business’s essential value, not just sales, such as “customer acquisition cost,” “protocol usage frequency,” or “number of external developer participants.”
• Evaluation Timing: Establish mandatory “continue/terminate” decision meetings every quarter or upon achieving specific milestones. This is not a business plan review, but a meeting to verify the experimental hypothesis.
• Method of Reversion upon Termination: When liquidating a subsidiary, decide in advance the procedures for how to “harvest” (not rollback, but harvest) the technology, insights, and human networks gained there back to the parent company or other businesses.

It is unclear if Nexon’s case followed this, but applying this framework positions business restructuring as a positive decision: “The experimental hypothesis was not supported by observation results, so we are reallocating resources to another experiment.” This is the mindset of “reversible management.”

The Common Principle: Separate the Evaluation of People from the Evaluation of Work

Whether in systematizing recruitment or terminating a new business, what is fundamentally crucial is to thoroughly separate the “evaluation of people” from the “evaluation of work structure (or business model).”

When modeling an “ace’s intuition” fails, it becomes difficult to immediately discern whether “the model is bad (the hypothesis about the work structure is wrong)” or “the person executing the model is bad (a people problem).” Many organizations easily conclude the latter (people problem) and rush into the irreversible decision of replacing people. Similarly, when a business is not going well, confusion arises between “a problem with the business model itself” and “a problem with the execution team’s capability or fit,” losing valuable learning opportunities about the business model.

The simplest way to prevent this is to “conduct parallel experiments with the same work structure using different people or teams.” For example, have Team A and Team B simultaneously try a new sales flow created by deconstructing the ace’s work. For new challenges like a virtual asset business, instead of betting everything at once by establishing a large subsidiary, run multiple small-scale experimental projects in parallel, also varying the team composition.

Doing so allows you to discern, based on data, whether “it works when that person does it but not when this person does it” is due to a work structure problem or a problem with personal characteristics or fit. The basis for judgment shifts from “that person’s sense” or “momentum” to “observed facts.”

Three Practical Checklists for “Reversible Organizational Transformation”

Finally, we present a checklist for organizational design incorporating reversibility that you can implement in your company starting tomorrow.

1. Have you listed “observable actions” before modeling?
Have you specified down to the level of “sends a thank-you email summarizing key points within 24 hours after the first visit,” rather than “has high communication skills”? If it cannot be specified, it is still a “black box” that cannot be evaluated or improved and is not even a candidate for systemization.

2. Have you set an “evaluation period” and “rejection conditions” for the rules or flows being introduced?
Have you gained prior agreement from everyone on when and what to observe for judgment? For example, “Try the new sales flow. Evaluation period: 3 months. Rejection condition: if the average days to close a deal increases by 15% or more.” Changes without agreement are merely “top-down impositions,” and responsibility becomes ambiguous when they fail.

3. Have you defined the “recovery procedure upon termination” for the business or project?
If this project is discontinued, in what format and where will the developed code, customer list, and insights gained from failure be stored, and who will have access? Is there a designed process for “termination” itself, not just “stopping,” and a clear path to reliably recover the investment as seeds for the next challenge?

Systemizing “intuition” and challenging new businesses are both essential joys of management. However, what makes that joy sustainable is not success itself, but the design philosophy of “how minimally damaging and how maximally learned from one can return when things don’t go well.” It relies neither too much on human capability nor stubbornly adheres to inorganic manuals. Supporting that delicate balance is the concept of decision reversibility.