The customer describes an experience
A household asking for better internet may describe a broad dissatisfaction in very few words. The product interface can respond just as quickly by presenting a higher connection tier. That response is convenient because the available commercial option already has a name and a place in the catalogue. Yet the household may be speaking about a particular room, a device or a use that does not work as expected. Before the product turns the request into a sale, it needs to understand which question has actually been asked. An available upgrade is not, by itself, an explanation of the experience.
In the fictional 2025 needs review at Hoshinora Communications, eighty of 125 households expressed interest in changing their connection tier. Forty-five described weak coverage in a room. These were stated needs recorded in the review, not engineering diagnoses. I would not use them to identify the cause of a fault or to claim that one particular intervention would solve it. They did show that the same entry point could contain two different conversations. Some households were considering the service tier; others were describing the experience of using the connection in a location inside the home.
That distinction led us to allocate JPY 260 million to a separate coverage-assessment route beside tier selection. Keisuke Naruhase preferred a more direct upgrade journey, with fewer branches between the initial request and the available product. I understood the commercial and explanatory appeal. The risk was that the journey would quietly make a causal claim: if the customer wants a better experience, the next tier is the relevant answer. The research did not support that conclusion for every household. We chose to add a route that could establish the nature of the question before the proposition implied a solution.
The decision does not mean connection tiers are irrelevant. A household may have a well-founded reason to consider a different service arrangement, and the product should make those choices understandable. It means that the tier and the experience in a particular room should not be treated as interchangeable descriptions. Wireless conditions can depend on the home, equipment and devices as well as the service arrangement. The product leader does not need to diagnose all of those conditions personally. The product does need a responsible way of directing a room-specific question to people and processes equipped to examine it.
A product option is not a diagnosis
I am careful about the language used around assessment because a new route can acquire more authority than it has earned. Calling something a coverage assessment does not establish that every underlying issue will be identified or resolved. The route needs a defined purpose, appropriate capability and a clear account of what follows from its findings. A preliminary conversation may establish that the household is asking about one room without establishing why that room has a different experience. Product copy should retain that distinction rather than turn a helpful classification into a technical conclusion it cannot support.
The same discipline applies to the numbers in the case. The forty-five households are not forty-five confirmed equipment faults, and the eighty tier enquiries are not eighty completed upgrades. No measured performance improvement is reported in this account. The work concerns the product decision to separate routes and the expense allocated to developing them. That can still be a meaningful executive judgement. A product leader sometimes creates value by preventing the organisation from making an unsupported connection between a customer’s words and an available offer, even before a later service outcome can be measured.
The route also changes what the organisation must explain internally. A commercial team needs to know why some enquiries leave the immediate tier-selection path. A service team needs to know what the coverage route is asking it to establish. The customer needs to understand why a question has been asked rather than experience the additional step as an unexplained delay. If these accounts disagree, the new branch can become an administrative obstacle instead of a useful distinction. The development work therefore concerns the relationship among the routes, not merely the addition of another option to the interface.
There is a trade-off in accepting that work. A single upgrade journey is easier to present, and separating the questions may make some commercial conversations less immediate. I do not think that cost should be hidden behind a general claim that every additional question is beneficial. The questions should earn their place by helping distinguish needs that would otherwise be conflated. They should also remain proportionate to the decision being made. A household considering a clearly understood tier change should not be forced through an unrelated investigation simply because another household’s room experience requires a different kind of attention.
Keep the commercial choice connected to the actual question
For a product review, I would ask the team to show the starting descriptions customers use, the decisions each route is intended to support and the statements the route is allowed to make. This makes the implied reasoning inspectable. It can reveal a point where an interface moves from asking what the household experiences to assuming what will improve it. That point deserves attention because commercial language can sound like technical explanation without anyone deliberately intending to mislead. The product sponsor is responsible for noticing when the structure of the journey creates that implication.
I would also keep the specialist boundaries visible in the executive account. Network and in-home conditions require appropriate assessment, while the terms of an actual offer require their own review. A fictional product case should not borrow authority from a technical concept and then announce a general performance or compliance result. In a real organisation, the relevant evidence and responsibilities would need to be established for the service and location concerned. The leader’s contribution is to ensure that the product question reaches those responsibilities, rather than to replace them with an attractive story about a more responsive catalogue.
The lesson I take from the work is about listening before naming the answer. A customer’s broad phrase can conceal a specific place and activity. The organisation’s ready-made product can make that specificity disappear unless the journey allows it to be expressed. Separating tier selection from a coverage question is one example of keeping the offer connected to the experience it is meant to address. It leaves room for a commercial choice and for a technical investigation without pretending they are the same act. The household deserves to know which conversation it is having before the service asks it to decide.