ROI Case File No.562: 'The Tool Could Be Swapped, but There Was No System to Wield It'
The Tool Could Be Swapped, but There Was No System to Wield It
Chapter 1: The Tool Was Decided, but the System Wasn't
"Next I want to push company-wide AI adoption with Google Gemini. But I don't know how to build the system for it."
Mitsuru Ginga, AI adoption lead at Galactic Solutions, recounted the background. "I became the adoption lead this January. We brought in a generative-AI tool in April, and that contract expires at the end of May. I want to get the most out of Gemini next, but swapping the tool alone doesn't feel like it moves us forward."
"Does swapping tools make adoption progress?" Claude asked.
"I don't think so," Ginga answered. "The tool we brought in in April—people learned the basics, but it never spread beyond that. The gap between those who use it and those who don't stayed wide. A new tool feels like it would end up the same way."
"Are the strategy, people, and mechanisms around the tool in place?" I asked, to confirm.
"...They're not," Ginga answered. "I was only thinking about the tool. Who waves the flag, what mechanism runs it, how it's taught—I've never assembled that whole picture."
"Swap only the tool, and if the surroundings don't mesh, it spins in place," I replied. "Let's break this down with 7S."
Chapter 2: 7S Asks—Mesh the Seven Elements
"This case calls for 7S."
Claude wrote on the whiteboard: "Strategy, Structure, Systems, Shared Values, Style, Staff, Skills."
"7S—the seven elements of strategy, structure, systems, shared values, style, staff, and skills—views an organization from seven angles and designs measures for whole-system optimization," I explained. "The key is not to treat the seven separately, but to mesh them. Introducing a tool is merely one element of 'systems.' Strategy sets the direction, structure carries the flag-waving, shared values create motivation, and staff and skills support execution. Only when all seven align does the tool come alive."
"First, let's measure the current cost," Gemini said, opening ROI Polygraph. The data Ginga provided was entered.
"Here is the monthly cost," Gemini read out. "Unmet labor savings because AI adoption stalls at the basics: 170 hours per month on average, at ¥3,800 per hour, ¥646,000 per month. Information-search labor from cumbersome internal data retrieval: ¥380,000 per month. Duplicated trial-and-error from no established best practices: ¥340,000 per month. Uneven, stalled adoption from the absence of a driving structure: ¥360,000 per month. Switching costs as know-how is severed with each tool change: ¥280,000 per month. A total of ¥2,006,000 per month. Roughly ¥24.07 million per year."
Ginga stared at the figures. "I was only looking at the tool's cost. Add the cost of adoption never spreading for lack of a system, and it comes to this much."
"Then let's design it with 7S," I continued.
[Strategy, Structure, Systems—Assemble the three hard elements]
"First, assemble the three hard elements," Claude said. "Strategy—set the direction of pushing labor savings and efficiency company-wide with Gemini. Structure—choose core members around the lead and divide the roles. Systems—connect Gemini to internal systems and simplify data retrieval. This is the foundation."
[Shared Values, Style—Create motivation with the two soft elements]
"Next, create motivation with the two soft elements," Gemini continued. "Shared values—share the benefits of AI use company-wide and grow a culture of using it. Style—hold regular training and workshops, making a place to learn through practice. Mechanisms alone don't move people. This is the crux of the mesh."
[Staff, Skills—Grow the two elements that carry execution]
"After values, grow the two execution elements," I continued. "Staff—give core members specialist training and raise them into adoption leaders. Skills—share, company-wide, the methods and best practices for using Gemini effectively. With people and skills in place, the measures run on the floor."
[Alignment—Close the gaps across the seven]
"Finally, take the alignment across all seven," Claude continued. "Is strategy out of step with structure? Do shared values mesh with style? Miss even one, and the whole spins in place. Only after closing the gaps across the seven does the tool take hold."
[Estimating the payback]
"Let's run the numbers on ROI Proposal Generator," Gemini proposed.
- Initial cost: building the driving structure, Gemini internal integration, data-retrieval simplification, training/workshop design, and specialist training—¥4.8 million total
- Monthly cost: tool licensing and operation combined, ¥200,000
- Monthly savings: labor savings from adoption taking hold = ¥450,000 (assuming 70% achievement); simplified data retrieval = ¥340,000; reduced trial-and-error via shared best practices = ¥300,000; expanded adoption via the driving structure = ¥300,000; totaling ¥1,390,000 per month
- Net monthly savings: ¥1,390,000 − ¥200,000 = ¥1,190,000 per month
- Payback period: ¥4.8 million ÷ ¥1.19 million = about 4.0 months
"Four months to recoup," Gemini summarized. "What works is not settling for a tool swap, but meshing the seven elements. Renew only the system, and if strategy and people don't follow, adoption never spreads. Align all seven, and the tool takes hold. The investment doesn't miss."
Ginga checked the figures. "I thought swapping the tool would move things forward. Unless you assemble the other six around it, the tool never comes alive."
"7S is a tool for meshing seven elements to move the whole," I replied.
Chapter 3: An Implementation Plan That Meshes the Seven Elements
"Let me lay out the approach," I said, standing at the whiteboard.
"Month one—fix the strategy, form the driving structure, and inventory the current state of the seven elements. Month two—design Gemini's internal integration and data-retrieval simplification. Months three and four—run training and workshops and cultivate shared values. Month five—give core members specialist training and share best practices. Month six—trial operation and effect verification. Month seven onward—continuously check the alignment of the seven and expand the scope of adoption."
"Won't we start from scratch every time we swap tools?" Ginga asked.
"You won't," Claude replied. "You return to scratch because know-how is tied to the tool and there's no system. Assemble strategy, structure, values, staff, and skills with 7S, and the foundation remains even when the tool changes. Whatever tool comes next, there's a frame to mesh it into. The severing at each switch stops."
Ginga took notes. "Before swapping the tool, assemble the seven elements. Now I see the order."
Chapter 4: The Day the System Made the Tool Come Alive
Ten months later, a report arrived from Ginga.
After building the system, AI adoption broke past the basics. "The gap between those who could use it and those who couldn't had stayed wide. Training and a sharing mechanism went in, and the company's floor rose," Ginga wrote.
Data retrieval grew simpler, too. Integrating Gemini with internal systems cut the effort of hunting for information. "The time we spent searching dropped visibly," the report read.
The biggest change showed in how tool switches were received. From returning to square one with each change, to keeping the foundation. "Swap a tool and start over—that was the norm. Once the seven elements were assembled, even switching to Gemini let the system stay alive as is," Ginga wrote.
Duplicated trial-and-error dropped as well. Sharing best practices removed the waste of repeating the same fumbling. "One person figuring something out from zero, then another doing it from zero again—that decreased," the report read.
As a side effect, the way measures were viewed changed. Seeing the whole rather than the tool alone took root in the company. "We stopped ending things at 'we brought in a tool.' We started asking whether strategy, structure, and people were all in place," Ginga wrote.
At the end of Ginga's report was this: "I thought driving AI adoption meant choosing a good tool. But the real problem was that there was no system to wield the tool. The moment we meshed the seven elements with 7S, the tool started to come alive. Before swapping the tool, assembling the other six came first."
The day a company that could swap tools but had no system to wield them became a company that could make tools come alive by meshing seven elements, driving AI adoption had shifted from tool selection to a design that assembles seven elements for whole-system optimization.
"Requests to drive AI adoption usually arrive as 'which tool should we choose.' But before swapping tools, there's a question to ask: is the system to wield it in place? What 7S asks is the seven—strategy, structure, systems, shared values, style, staff, and skills. The tool is merely one of them. Only by meshing all seven does the tool take hold. The day a company that could swap tools but had no system made its tools come alive, what changed was not the performance of the tool but the very perspective that meshes seven elements to move the whole."
Related Files
Tools Used
- ROI Polygraph — Visualizing stalled-adoption labor, information-search labor, and switching costs
- ROI Proposal Generator — Payback simulation for AI adoption, starting from meshing the seven elements
