A convincing room image can make a promise the software cannot keep

I wanted the room visualiser to work. I had supported its pilot, understood the effort behind it and seen customers become more engaged when they could discuss a room through an image. Those were reasons to examine the service carefully, not reasons to protect every claim that had become associated with it. The difficult evidence arrived when viewers described what they thought the image established. Some were treating an illustrative result as an exact preview of the shade they would see in their own homes.

The distinction mattered in floor-covering retail. A visual tool can help someone discuss arrangement and relationships without establishing the physical appearance of a material under particular lighting and viewing conditions. Our internal description recognised that limit. The experience presented to the customer did not always carry it with the same force. I had to assess the service through the belief it created, including beliefs nobody intended to encourage, rather than only through the statements the project team believed it had made.

## Test the belief created by the demonstration

The pilot cost ₹1.4 crore. In a review of 176 viewers, forty-three understood the image as an exact shade preview. That finding did not mean forty-three customers had received unsuitable flooring or made a purchase on that basis. It described an interpretation in the pilot review. I kept that boundary clear because the decision did not need an invented customer-loss figure. A material gap between the service's supported use and the viewer's understanding was already relevant to whether and how we should proceed.

Commercial colleagues saw a tool that made consultation more engaging. They were not wrong to value that. Customers could discuss an arrangement with more confidence than when looking at disconnected samples or trying to imagine the whole room. The software also gave staff a shared object around which to structure a conversation. Those benefits deserved to survive if they could be delivered responsibly. The question was whether the experience could retain its useful role without implying a precision about material appearance that we had not established.

I asked the team to separate what the technology produced from what the customer inferred. The first question concerned the image and the service's technical scope. The second concerned the way the demonstration, surrounding words and sales conversation shaped understanding. Neither team could answer both alone. Product specialists, commercial colleagues and the technology team needed to agree on the supported use and on the points where a physical sample or further advice remained necessary. The CIO's role was to connect that judgement with the system decision and the investment account.

There was a temptation to treat the forty-three responses as a communications problem outside the software project. That would have been convenient for me because it preserved the technical delivery as complete. But the image was part of the communication. Its appearance, the controls around it and the way staff used it all contributed to the inference. A product can be technically within its specification while the experience encourages an unsupported conclusion. Leadership should examine that combined effect rather than allocate the concern to whichever function owns the smallest line of explanatory text.

## A clearer sentence may not change the inference

Our first response was to revise the explanation and the demonstration sequence. In a later group of 180 viewers, twenty-six still understood the image as an exact shade preview. The groups were different, so I did not present the change as a controlled estimate of the explanation's effect. It was enough to show that the misunderstanding remained material in the revised experience. The lower count did not establish that the proposition was now sound, and the presence of a clearer sentence did not settle what viewers actually took away.

This was the point where my own investment in the project became most visible to me. I could list the useful features and explain why the remaining misunderstanding might reduce with better staff practice. Those possibilities deserved consideration, but they were not evidence that the current service supported the stronger promise. I needed to distinguish a plausible future improvement from the experience we could responsibly make available now. Otherwise I would be asking customers to supply the confidence that the project had not yet earned through its own evidence.

We chose to retain layout exploration while removing the unsupported shade-preview claim and the interface treatment that encouraged it. The commercial and product teams clarified where physical samples and their advice belonged in the conversation. The technical team revised the service accordingly. I did not describe the decision as abandoning visualisation. It was a decision about the scope of this implementation and the meaning it could reasonably carry. A narrower tool can still be useful when its limits are part of how the service operates, rather than a footnote competing with the demonstration.

The additional work cost ₹18 lakh. It was separate from the ₹1.4 crore pilot and belonged in the investment account. CEO Nusrat Delvani supported the reduced scope even though it meant accepting that an attractive part of the original proposition would not proceed as imagined. That support mattered because project teams watch what happens when evidence challenges a senior sponsor's enthusiasm. If the only acceptable result is confirmation of the original idea, the review becomes an exercise in finding language that protects the decision already made.

## Give the narrower service an honest investment account

At the October 2026 review, the restricted layout service was available. We had not established its separate commercial return, and a new interpretation study was still outstanding. I reported both facts. Continuing to use the tool did not demonstrate that it had recovered the investment. Nor did limiting its scope establish that all risk of misunderstanding had disappeared. The next review needed to examine the narrower service on its own terms, including what customers understood and whether the business value justified its continuing expense.

Money already spent can make a change of scope emotionally difficult without making the original claim more supportable. I find it useful to state the expenditure before discussing the revised choice. That prevents a team from treating a retreat in ambition as though it cost nothing. It also prevents the opposite error of treating the sunk amount as a reason to keep pursuing a proposition regardless of new evidence. Directors need an account of what remains possible, what further spending is proposed and what the next decision will depend on.

For someone moving from executive technology work towards board service, this is a useful discipline. A director should not become the product designer or decide the wording of every screen. They can ask whether the evidence addresses the way customers interpret the service, whether the limits are reflected in operating practice and whether management has separated observed benefit from hoped-for return. They can also ask how the organisation responds when a sponsor's preferred feature creates a problem that was not apparent in the original business case.

I remain interested in visual tools because they can make a difficult conversation easier. The lesson is to be precise about which conversation they improve. Layout exploration, physical shade assessment and product suitability are related but different decisions. A persuasive image should not be allowed to collapse them merely because doing so makes the demonstration more exciting. My responsibility is to help the company preserve useful capability while withdrawing a confidence the evidence cannot support, including when I helped create the enthusiasm in the first place.