The date conceals a sequence
An address-change form encourages a simple account of moving. There is an old location, a new location and a date between them. That account may suit the way a service records an address, but it does not necessarily describe the household’s experience. Someone may begin working from the new home while another person remains at the earlier one. Belongings may move in stages. The day entered into a form can therefore sit inside a longer period of change. If the product asks only for the date, it may fail to ask about the part of the transition that matters most.
In our fictional 2023 research, sixty-one of one hundred households wanted a seven-day overlap between the two service arrangements. Thirty-nine wanted a same-day change. I do not read those counts as a universal distribution of moving behaviour. I read them as sufficient reason to question whether one journey could honestly represent both intentions. The households were describing a relationship between two places over time. Compressing that relationship into a single switch could make the internal process easier while leaving customers to discover that their circumstances had never been part of the choice.
Keisuke Naruhase preferred the same-day route because it gave the proposition a clear structure and reduced the number of paths the team needed to explain. That argument deserved consideration. Adding a choice can create work for service teams and further questions for customers. Yet simplicity needs a subject: simple for whom, during which part of the experience? A form with fewer options may be more difficult for a household whose move does not fit the assumption behind it. We needed to judge the work created by the alternative against the work already being displaced onto those households.
The decision was to develop two paths with JPY 210 million allocated to the work. The seven-day overlap became an explicit option beside the same-day route. This did not mean every home could receive either arrangement under every condition. The product brief needed installation, network and contractual assessment before an actual commitment could be made. The choice described the intended journey; it did not erase the practical work necessary to fulfil it. I wanted the team to keep that distinction clear as the proposition became more concrete, because an attractive transition description can otherwise become a promise before its conditions are settled.
An overlap has to be an explicit choice
An overlap is more than an extra field added to the form. It changes how the customer understands the relationship between two service arrangements. The old location does not simply disappear from the account the moment the new one is entered. The product needs to explain what the customer is selecting, how the relevant period is represented and what still requires confirmation. Those questions should be examined with the people responsible for fulfilment. A designer cannot settle them by making a timeline look continuous when the underlying service arrangements remain subject to separate decisions.
I also wanted the same-day path to remain a serious choice. A team can become so enthusiastic about the newly discovered need that it treats everyone who prefers the original route as an exception. The thirty-nine households in the research mattered too. Some people wanted a clear transition without an overlap period. Our product decision was not to announce that moving always requires seven days. It was to acknowledge two observed intentions and give them an intelligible place in the proposition. That preserves the reason for the alternative without turning a research finding into a rule for every future customer.
The later pilot involved eighty households, of whom forty-nine selected overlap and thirty-one selected same-day change. Those numbers are choices recorded in the pilot. They do not state that eighty installations were completed or that every household experienced uninterrupted connectivity. Treating selection as delivery would remove exactly the distinction the work needed to preserve. I would expect a product review to show the chosen journey and the evidence available for its practical fulfilment separately, so that an encouraging response to the proposition cannot conceal a different question about the service’s ability to provide it.
There is a cost to keeping both paths. The team has more to explain and maintain, and the operating arrangement must account for a transition that does not fit one internal date. That cost should remain visible in the decision rather than disappear behind the word customer. Customer need is a reason to examine an alternative, not a reason to exempt it from scrutiny. The sponsor should explain why the added work is proportionate, which circumstances it is intended to address and which requests it still cannot support. A choice is more credible when its boundaries are part of its design.
A selected journey is not a delivered connection
This case changes how I read a product paper about moving. I look first for the household sequence, then for the service commitments that the proposed sequence depends on. A date may still be necessary, but it should not be asked to carry every meaning of the transition. If the paper gives one date, I want to know which activity occurs then and what continues before or after it. If it describes an overlap, I want to know what must be confirmed before that overlap can be offered to the particular household under the applicable arrangement.
The distinction also matters in executive communication. A summary can say that customers selected the new route, and a later reader may remember only that the move was made easier. That is a broader claim. It could be true in some circumstances, but it needs its own evidence. I prefer to retain the modest statement the pilot supports and make the remaining work visible. It is possible to explain a worthwhile product choice without announcing a delivery result that the account has not established. Restraint keeps the decision available for examination rather than protecting it with a larger story.
For me, the wider lesson concerns the unit of design. An organisation may organise an event around the moment its records change, while a household experiences a period in which two situations overlap. Neither account can simply be ignored. The product leader’s work is to bring them into a relationship that the customer can understand and the service can responsibly support. That means accepting some additional complexity where it reflects a real situation, while refusing to let the visible journey outrun the practical commitments beneath it. The switch date remains useful once it has stopped pretending to be the whole move.