Chief Product Officer / India
The simplicity we changed and the work we accepted
Decisions & consequences
01Replacing the single moving date I had approved
In 2022 our relocation planner asked for one moving date and arranged the household's tasks around it. I had approved the model because it made the opening experience concise. A study of thirty-two households found twenty-one describing a phased move and eleven a single stage. The work start, the departure of other household members and the movement of belongings did not always belong on one date. Users were having to make their situation inaccurate to make the product look orderly.
The commercial sponsor favoured retaining the simple flow and letting support handle unusual arrangements. That would preserve a familiar demonstration and avoid a more demanding first interaction. I chose to change the planning structure instead. We allocated ₹39 lakh to representing separate stages and their relationships, while keeping a single-stage path for people whose circumstances suited it. The study did not establish that every household preferred a phased move.
A distinct twelve-household pilot found nine able to complete the revised planning task without assistance and three needing help. Those were task results, not evidence of completed relocations or successful provider delivery. Independent providers retained actual quotations, schedules, acceptance and transport decisions. The product could organise a household's intentions without making external arrangements true merely because they appeared on a timeline.
The choice gave up the ease of one date and required clearer explanations of how stages related. Support remained necessary for the three pilot households; we did not hide them inside a general success claim. I would now investigate the household's decision structure before choosing the first screen's organising field. A product can offer simplicity without demanding that every user share the same life pattern. The difficult part was acknowledging that the apparent exception had been created by the model I had approved, rather than by users failing to understand an otherwise complete design.
Giving the sponsor progress without the private household inventory
In 2023 we reviewed employer-facing views across forty-eight prototype relocation plans. Seventeen exposed private-inventory detail beyond the intended sponsor scope, while thirty-one matched that scope. The employer was funding access and had legitimate questions about agreed progress. That did not mean it needed the detailed list of household belongings that users entered for their own planning. The prototype had allowed a commercial relationship to imply a broader view than its purpose required.
The enterprise-sales sponsor wanted a comprehensive dashboard because buyers often asked for visibility. I accepted the value of a useful sponsor account but rejected the assumption that complete visibility was the correct default. We allocated ₹24 lakh to separating views and reviewing permissions with qualified privacy, legal and commercial owners. Product work translated the agreed scope; it did not claim to settle the legal basis by itself.
Sixteen of the seventeen excessive prototype views were corrected. The remaining preview was withheld from the employer-facing design until its issue could be resolved. The thirty-one appropriately scoped views were not evidence that every future arrangement would be suitable. This fictional case concerns a design review before release of the reviewed views, not real household records disclosed to an employer. No actual privacy incident or universal compliance outcome is asserted.
The cost was a less comprehensive-looking sales demonstration and additional design and review work. We retained a useful progress account without making the sponsor the owner of the household's private inventory. I would agree the purpose of each participant's view before building a broad dashboard, then test what a recipient can actually infer from it. The person paying for software and the person using it may both be customers in different senses. A product leader must make their relationship workable without quietly collapsing their interests and permissions into one account.
Letting people describe belongings without a compulsory photograph
In 2024 a forty-participant task study tested our photo-only inventory flow. Twenty-six adults completed the task and fourteen could not. The findings did not assign a single reason to every difficulty. Some people needed another way to enter the description; others did not want to photograph the relevant belongings. The product had made one convenient method a requirement for completing a more general planning task.
The design team favoured photography because it reduced typing and made the inventory easy to recognise. Those advantages were real for some users. I chose to retain photographs as an option while adding text and optional voice entry with a user review step. The ₹18 lakh programme included clearer confirmation and an assistance route. Voice input was not treated as perfect transcription, and a description still needed to be checked by the person providing it.
In a separate later group of thirty-two task sessions, twenty-seven were completed without assistance and five needed help. The groups and conditions were different, so the figures do not establish a controlled improvement. Nor do they prove universal usability or formal accessibility conformance. The five unresolved tasks remained part of the product account and informed further work. Provider acceptance and handling requirements remained with the relevant providers; an inventory entry did not settle them.
The choice increased the design and support responsibility because several input paths had to reach an understandable common review. It also gave up the simplicity of a single mandatory method. I would now define the details the task genuinely needs before deciding how every person must supply it. A useful default can remain prominent without becoming a barrier. The product should help users make an accurate account through an approach they can use, rather than treat failure to operate our preferred input method as failure to understand their own belongings.
Resuming a plan while leaving an old quotation in history
In 2025 we tested how a paused relocation plan resumed. Of thirty-four prototype users, twenty-one expected the earlier provider price to remain current and thirteen understood that a fresh confirmation was needed. The saved plan displayed the old quotation beside a continuation action without making its historical status clear enough. The software had preserved useful work but also suggested that an external commitment had survived unchanged.
The sales sponsor preferred a one-click continuation because it made returning to the product feel effortless. I supported preserving the household's work but rejected silently treating an expired quotation as current. We allocated ₹29 lakh to separating the historical quote from the request for a new provider confirmation. Users could see what had previously been quoted and what still needed checking before they relied on a renewed arrangement.
A separate later set of thirty task sessions found twenty-five users understanding the distinction and five still requiring support. These were different groups, not a controlled comparison proving a causal improvement. The five difficulties remained visible. The product did not itself renew a provider's price, confirm availability or book a move. Households contracted directly with providers, and qualified commercial owners retained the applicable terms. No payment, refund or completed transport outcome is claimed.
The consequence was a more deliberate return path with an extra confirmation question. We gave up the appearance that everything could resume exactly where it stopped. I would now specify which parts of a saved plan are historical, which remain usable and which depend on somebody else's renewed agreement. Preserving a user's effort is valuable. Preserving an obsolete implication is not. The product needs to distinguish those two kinds of continuity before a household treats a convenient saved screen as evidence of a commitment the provider has not made again.