ROI Case File No.573 'Trying to Flatten Everything Evenly, We Couldn't See the Vital Twenty Percent'
![]()
Trying to flatten everything evenly, we couldn't see the vital twenty percent
- Chapter 1: There's a lot to do—but our hands can't reach it all
- Chapter 2: What the Pareto Principle asks—concentrate on the vital twenty percent
- Chapter 3: An implementation plan that concentrates on the vital twenty percent
- Chapter 4: The day the twenty percent moved the eighty
- Related Files
- Tools Used
Chapter 1: There's a lot to do—but our hands can't reach it all
"We want to migrate the university's mail server. I'd like advice on whether the settings are sound and on security."
Kaname Morita, in charge of systems infrastructure at TechSol, described the situation. "The support period for the Linux mail server we run on-premises is closing in. Even with the extension, it's half a year. Spam is increasing too. For the migration target we're assuming Google Workspace or Microsoft 365. We'll do the work in-house, but there's a lot of anxiety—whether the settings are sound, whether security is all right."
"How are you trying to clear that anxiety?" Claude asked.
"By trying to act on everything evenly," Morita answered. "Settings, security, spam, migration procedure. I line up the items and try to knock them down one after another. But there are too many, and my hands can't reach them all."
"Among them, do you see which one is the most effective?" I confirmed.
"…I don't," Morita answered. "I've been treating everything with the same weight. Where to concentrate so that most of the anxiety disappears—I've never pinned down the vital twenty percent."
"Try to flatten everything evenly, and the vital twenty percent gets buried," I replied. "Let's break it down with the Pareto Principle."
Chapter 2: What the Pareto Principle asks—concentrate on the vital twenty percent
"This case calls for the Pareto Principle."
Claude wrote on the whiteboard: "80 : 20."
"The Pareto Principle—the 80:20 rule—is a framework that sees eighty percent of results as arising from twenty percent of causes, and concentrates resources on the vital twenty percent," I explained. "The crux is not acting on everything evenly. Most problems arise from a handful of vital points. Pin those down and concentrate, and most of it is handled with few moves. It's a tool for producing the greatest effect with limited resources."
"First, let's measure the current cost," Gemini said, opening ROI Polygraph. He entered the data Morita had provided.
"The monthly cost is out," Gemini read off. "Settings-verification and rework labor for the migration averages 170 hours a month; at ¥4,000 an hour, that's ¥680,000 a month. Inefficiency in handling spam averages ¥400,000 a month. Migration-delay risk from the closing support deadline averages ¥380,000 a month. The scatter from a lack of priorities—treating everything evenly—averages ¥340,000 a month. The limited-options risk from vendor lock-in averages ¥300,000 a month. The total is ¥2,100,000 a month—about ¥25.2 million a year."
Morita stared at the figures. "I'd been watching only the labor of the work. Once you add the cost of the scatter from acting on everything evenly, it comes to this much."
"Then let's design it with the Pareto Principle," I continued.
[The vital point—pin down the effective twenty percent]
"First, pin down the vital point," Claude said. "Eighty percent of the anxiety comes from this twenty percent—the closing support deadline and spam countermeasures. Settle these and most of the anxiety disappears. Don't line up all items flat; identify the effective twenty percent."
[Selection—compare migration targets on two strengths]
"Next, selecting the migration target," Gemini continued. "Compare Google Workspace and Microsoft 365 on whether they work on the vital point. Spam countermeasures and ease of operation. Choose the one that works most on the need, by the twenty-percent criterion."
[Concentration—pour resources into settings soundness and security]
"After selection, concentration," I continued. "Pour the limited in-house hands into the effective twenty percent—verifying the soundness of settings and strengthening security. Have a specialist check the vital points. Don't spread thin and flat; concentrate and firm it up."
[Ripple—spread the twenty-percent result across the remaining eighty]
"Last, the ripple," Claude continued. "Once the twenty-percent vital points are firm, the fine anxieties of the remaining eighty naturally lighten. On top of that, build new connections outside the locked-in vendor. The result of concentration spreads across the whole."
[Estimating the payback]
"Let's run the numbers with the ROI Proposal Generator," Gemini proposed.
- Initial cost: migration design, identifying the effective twenty percent, verifying settings soundness, strengthening security, and migration support—¥5.4 million total
- Monthly cost: new-service use plus ongoing operation—¥230,000
- Monthly savings: migration efficiency through twenty-percent concentration = ¥550,000 (assuming a 70% reduction); stronger spam countermeasures = ¥340,000; strengthened security = ¥280,000; resolution of selection drift = ¥280,000; ¥1,450,000 a month total
- Net monthly savings: ¥1,450,000 − ¥230,000 = ¥1,220,000 a month
- Payback period: ¥5.4 million ÷ ¥1,220,000 = about 4.4 months
"A little over four months to recover," Gemini summarized. "What works is not flattening everything but concentrating on the effective twenty percent. Act evenly and resources thin out and the vital points get buried. Pour into the twenty percent and most is handled with few moves. The investment doesn't swing at empty air."
Morita said as he checked the numbers. "I'd been trying to act on everything. Unless you concentrate on the effective twenty percent, resources scatter."
"The Pareto Principle is a tool for concentrating on the effective twenty percent," I replied.
Chapter 3: An implementation plan that concentrates on the vital twenty percent
"Let me lay out the approach," I said, standing before the whiteboard.
"Month one—identify the effective twenty percent and set priorities. Month two—compare and select the migration target and fix the evaluation criteria. Month three—concentrate on verifying settings soundness and strengthening security. Month four—carry out the migration and trial run. Month five—verify effects and fine-tune the remaining eighty percent. Month six—embed operations and review spam countermeasures. Month seven onward—build a continuing relationship with the new partner."
"If we don't knock everything down, won't anxiety remain?" Morita confirmed.
"It's the reverse," Claude replied. "Try to flatten everything, and each thing ends up half-done and anxiety remains. Concentrate on the effective twenty percent—the deadline and spam vital points—and most of the anxiety vanishes together. The remaining eighty lightens after the twenty is firm. Concentration is the shortest path to reducing anxiety."
Morita said as he took notes. "Before acting on everything, pin down the effective twenty percent. I can see the order now."
Chapter 4: The day the twenty percent moved the eighty
Ten months later, a report arrived from Morita.
The migration proceeded without a hitch after the twenty-percent concentration. "Once I secured the support-deadline vital point first, the migration itself went smoothly. Rework fell," Morita wrote.
Spam decreased too. Countermeasures poured into the effective twenty percent suppressed most of it. "The spam that had only grown fell visibly. The security anxiety, too, vanished with the specialist's check," the report said.
The biggest change showed in how the hands were played. From flattening everything, they shifted to concentrating on the effective twenty percent. "I stopped lining up items and knocking them down one after another. Once I first identified where the effective twenty percent was, most was handled with few moves," Morita wrote.
Options widened too. A new connection formed outside the locked-in vendor. "My future consulting options increased. The groundwork for a continuing relationship is in place," the report said.
As a side effect, the way problems were viewed changed. Rather than acting on everything, the habit of seeking the effective twenty percent took root. "I stopped doing each thing evenly. I began to think in terms of where the twenty percent that produces the eighty is," Morita wrote.
At the end of Morita's report was written: "I thought the mail-migration trouble was that there was too much to do. But the real problem was that, trying to flatten everything evenly, I couldn't see the vital twenty percent. The moment I concentrated on the twenty percent with the Pareto Principle, most of it was handled. Before acting on everything, pinning down the effective twenty percent came first."
On the day a company that had tried to flatten everything evenly and couldn't see the vital twenty percent became a company that could concentrate on the twenty to move the eighty, the mail migration had changed from an even round-robin into a design that concentrates on the vital twenty percent to move the remaining eighty.
"A consultation about a system migration usually arrives in the form of 'there's too much to do.' But before acting on everything, there's something to ask. Where is the vital twenty percent? What the Pareto Principle asks is the twenty percent that produces eighty percent of the results. Concentrate there and most is handled with few moves. On the day a company that had tried to flatten everything evenly pinned down the vital twenty percent, what changed was not the volume of work but the very perspective of concentrating on the vital twenty percent to move the whole."
Related Files
Tools Used
- ROI Polygraph — visualizing migration-rework labor, spam inefficiency, and the scatter cost of having no priorities
- ROI Proposal Generator — a payback simulation for the mail-server migration, starting from concentration on the vital twenty percent