ROI Case File No.570: 'Trying to Fill Everything with Appeal, the Foundation Was Missing'

Trying to Fill Everything with Appeal, the Foundation Was Missing

---

Chapter 1: We Have Eye-Catching Features—but the Foundation Won't Settle

"I want to build an IoT platform for housing. And link it with humanoid robots and delivery robots, too."

Nozomu Iemori, product lead at TechNest, described the concept. It was a project commissioned by Toei Communications, a firm whose main business is housing construction. "Answering the needs of partner homebuilders and management companies, we build an IoT-and-AI housing-management platform. Start with remote management of condominium common areas, and ultimately reach whole homes including detached houses. We also envision links with humanoid robots, elevators, and delivery robots."

"Are you starting the design from the linking features?" Claude asked.

"That's right," Iemori answered. "I want to differentiate, so I've been thinking about eye-catching linking features first. But the more features I line up, the less I can tell what's foundation and what's the selling point."

"Are you separating the basic features from the eye-catching ones?" I asked, to confirm.

"...I'm not," Iemori answered. "I was trying to fill everything with attractive features. But management companies' facility management is inefficient, and existing IoT is fragmented by maker and hard to integrate. This foundation part gets put off. Chasing only eye-catching features, the ordinary foundation was missing."

"Fill everything with appeal, and without a foundation you won't be chosen," I replied. "Let's break this down with KANO."

Chapter 2: KANO Asks—Stack the Three Layers of Must-Be, Performance, and Attractive

"This case calls for KANO."

Claude wrote on the whiteboard: "Must-be quality, Performance quality, Attractive quality."

"KANO—the Kano model—splits quality into three layers, must-be, performance, and attractive, and pinpoints what to stack where," I explained. "The key is not to mix the three layers. Must-be quality is the foundation that breeds dissatisfaction if absent. Performance quality is the part where more brings more satisfaction. Attractive quality is the differentiation that delights when present. Without firming the foundation, stack only appeal and you won't be chosen. A tool for stacking the three layers in order."

"First, let's measure the current cost," Gemini said, opening ROI Polygraph. The data Iemori provided was entered.

"Here is the monthly cost," Gemini read out. "Inefficient labor in management companies' facility-management work: 180 hours per month on average, at ¥3,800 per hour, ¥684,000 per month. Double management and inefficiency from the inability to integrate maker-by-maker IoT: ¥420,000 per month. Delayed provision of advanced services from a shortage of AI-use know-how: ¥360,000 per month. Opportunity loss in nationwide rollout from a lack of scalability: ¥380,000 per month. Rework and competitor-lead risk from unclear development priorities: ¥340,000 per month. A total of ¥2,184,000 per month. Roughly ¥26.21 million per year."

Iemori stared at the figures. "I was only looking at the linking features. Add the foundation's integration failure and inefficiency, and it comes to this much."

"Then let's design it with KANO," I continued.

---

[Must-be quality—Firm the foundation of integrated management]

"First, firm the must-be quality," Claude said. "What a management company wants at bottom is integrated facility management. Integrate the maker-by-maker fragmented IoT and eliminate double management. This is the foundation that breeds dissatisfaction if absent. Firm this first."

---

[Performance quality—Stack satisfaction with precision and speed]

"Next, stack the performance quality," Gemini continued. "Remote-operation precision, response speed, security measures. Pinpoint through detailed research the parts where more brings more satisfaction, and polish them. On the foundation, stack the height of satisfaction."

---

[Attractive quality—Differentiate with linking features]

"After performance, add the attractive quality," I continued. "Links with humanoid robots, elevators, and delivery robots. Add the differentiation that delights when present, here. Only with foundation and performance does appeal work as a selling point."

---

[Deployment—Stack the three layers and scale]

"Finally, stack the three layers and deploy," Claude continued. "Stack in the order of must-be, performance, and attractive, and make a scalable design that withstands nationwide rollout. Build a foundation that can extend from common areas to detached houses. Because the three layers are in place, you can roll it out ahead of competitors."

---

[Estimating the payback]

"Let's run the numbers on ROI Proposal Generator," Gemini proposed.

• Initial cost: an IoT integrated-management foundation, a remote-management system, security design, robot-linking features, and scalable design—¥5.9 million total
• Monthly cost: platform operation and maintenance combined, ¥240,000
• Monthly savings: streamlining facility-management work = ¥480,000 (assuming a 70% reduction); eliminating double management via IoT integration = ¥420,000; new acquisitions via advanced services = ¥340,000; accelerated rollout via scalable design = ¥340,000; totaling ¥1,580,000 per month
• Net monthly savings: ¥1,580,000 − ¥240,000 = ¥1,340,000 per month
• Payback period: ¥5.9 million ÷ ¥1.34 million = about 4.4 months

"Just over four months to recoup," Gemini summarized. "What works is not building from the appeal features, but stacking from the foundation of must-be quality. Build only linking features first, and without the foundation of integrated management you won't be chosen. Stack the three layers in order, and appeal works on top of the foundation. The investment doesn't miss."

Iemori checked the figures. "To differentiate, I was building from the appeal features. Without firming the foundation, appeal doesn't ride on top."

"KANO is a tool for stacking must-be, performance, and attractive in order," I replied.

Chapter 3: An Implementation Plan That Stacks Quality Across Three Layers

"Let me lay out the approach," I said, standing at the whiteboard.

"Month one—classify quality into the three layers and define the requirements of must-be quality (integrated management). Month two—collect feedback from homebuilders and management companies and identify the performance quality. Months three and four—build the IoT integrated-management foundation and the remote-management system. Month five—implement security design and robot-linking features (attractive quality). Month six—trial operation and effect verification. Month seven onward—extend to detached houses and scale toward nationwide rollout."

"Is it all right to put the attractive linking features off?" Iemori asked.

"That order is correct," Claude replied. "Build the appeal features first, and without the foundation of integrated management, management companies stay dissatisfied and won't choose you. Firm the must-be quality first with KANO, stack satisfaction with performance, and differentiate with appeal last. Because there's a foundation, robot linking works as a selling point. Because you stack in order, it also withstands the scale of nationwide rollout."

Iemori took notes. "Before filling with appeal, firm the ordinary foundation. Now I see the order."

Chapter 4: The Day the Foundation Supported the Appeal

Ten months later, a report arrived from Iemori.

After the integration foundation was built, facility management grew far more efficient. "IoT that had been fragmented by maker could now be managed on a single screen. The effort of double management vanished," Iemori wrote.

Remote-management performance rose, too. Precision, response speed, and security were polished. "Remote management of common areas reached practical precision. Management companies could use it with confidence," the report read.

The biggest change showed in the order of development. From building from the appeal features, to firming the foundation first. "To differentiate, I was building from the linking features. Once I firmed the must-be quality first, robot linking began to work as a selling point on top of it," Iemori wrote.

The rollout outlook took shape as well. The scalable design supported nationwide extension. "The path of extending from common areas to detached houses came into view. A foundation to get ahead of competitors was built," the report read.

As a side effect, the way quality was viewed changed. Not filling everything with appeal, but stacking across three layers, took root. "We stopped starting from eye-catching features. We started separating what's foundation, what's satisfaction, and what's the selling point," Iemori wrote.

At the end of Iemori's report was this: "I thought the IoT-platform struggle was the differentiating features. But the real problem was that, trying to fill everything with appeal, the ordinary foundation was missing. The moment we split it into three layers with KANO, the order to stack in came into view. Before filling with appeal, firming the foundation came first."

The day a company that tried to fill everything with appeal while missing the foundation became a company that could stack quality across three layers, platform development had shifted from the pursuit of eye-catching features to a design that stacks must-be, performance, and attractive in order.

"Platform-development requests usually arrive as 'we want a differentiating feature.' But before stacking appeal, there's a question to ask: is the foundation that breeds dissatisfaction if absent firm? What KANO asks is the three layers of must-be, performance, and attractive quality. Firm the foundation, then add appeal, and differentiation works. The day a company that tried to fill everything with appeal while missing the foundation could stack across three layers, what changed was not the flashiness of the features but the very perspective that stacks must-be, performance, and attractive in order."

---

Related Files

Tools Used

• ROI Polygraph — Visualizing inefficient facility-management labor, double management from IoT integration failure, and opportunity loss in nationwide rollout
• ROI Proposal Generator — Payback simulation for IoT platform development, starting from a three-layer design of must-be, performance, and attractive