The room does not end at the edge of the bench

## A correct drawing can support an incorrect promise

The outline of a bench is easy to draw, measure and compare. It is also easy to make that outline do more work than it can. When we call a product compact, a customer may hear a promise about the space needed to perform a task, not merely the rectangle occupied by the furniture. Those are different things. Parts arrive, unfinished work waits, a drawer opens and somebody needs to move around the arrangement. None of that activity disappears because the product drawing has a reassuringly small area printed beneath it.

I approved such a proposition in our fictional range review. The bench footprint was 0.9 square metres. The figure was accurate, and I thought a supporting diagram would be enough to explain its use. Our study of twenty-four customer teams then showed a median observed working envelope of 1.7 square metres. Fourteen teams needed a wider arrangement and ten a narrower one. The study did not establish a universal clearance requirement, but it made the weakness of our universal compactness claim difficult to ignore. I had allowed a product measurement to imply an answer about the task around it.

Sana, our head of design, asked us to change the main proposition rather than rely on a note beside it. My first response was defensive. The drawing had not lied, and customers could see the dimensions. But the drawing was not being read in isolation. It sat within a commercial story about creating useful work positions in limited rooms. A qualification would have had to undo an assumption the headline had already encouraged. The better correction was to make the task arrangement part of the proposition itself, even if that made the message less convenient.

This is a product-management question before it becomes a matter of presentation. The claim affects which options receive development effort, what sales colleagues demonstrate and what customers believe they are comparing. If the product team treats the surrounding work as somebody else's concern, a smaller footprint may win an internal comparison while leaving the customer with a worse arrangement. I do not want researchers to design an entire workplace from a brief observation. I want them to notice when our product claim has crossed from what we measured into what we have merely assumed.

## Observe what arrives and what stays

A clean demonstration bench hides much of an ordinary task. The presenter has selected the items, arranged them neatly and removed the work that does not belong in the demonstration. In a customer's setting, several stages may coexist. An incoming component waits beside an item under inspection; a completed piece needs somewhere to go; a tool is set down temporarily and then used again. Observing those movements can explain why a narrow surface appears adequate in a catalogue while the customer keeps adding another table beside it.

The research needs a defined context. Which task is being observed, what configuration is in use and who is interpreting the result? A median from twenty-four teams describes those observations, not every customer or every application. A researcher should record the circumstances that make one arrangement different from another. The useful conclusion may be that the range needs two propositions, or that a configuration is suitable for a narrower class of work than the original brief assumed. It need not be a grand claim about productivity or a universal rule for workshop layout.

The distinction between product research and specialist assessment also matters. Our study did not certify an ergonomic benefit, establish a safety clearance or authorise use in an unassessed setting. Engineering, quality and the customer's responsible workplace specialists retained those questions. Product management used the observations to shape the offer and its development scope. Keeping those boundaries clear makes the research more useful, not less. It allows the evidence to support the decision it actually informs without borrowing authority from a different assessment that has not been performed.

I also want to hear the person who buys the furniture and the person who works at it. The buyer may be solving a room-capacity or budget problem, while the user is managing the sequence of a task. Neither account should automatically dominate. A wider arrangement may help the work but reduce the number of positions that fit in a room. A smaller arrangement may meet the purchasing brief while requiring additional storage elsewhere. The product decision should expose that trade-off rather than make one group discover it after delivery.

## Carry the difference into the range decision

We funded ₹36 lakh of study and development around two depth propositions. Sales colleagues objected that the additional choice would make the range harder to explain and stock. They had a reasonable concern. More accurate segmentation can create more operational complexity, and a product leader should not treat that cost as evidence that commercial colleagues do not understand users. The question was whether the simpler proposition still described the observed work honestly. In this case I concluded that it did not, and accepted the cost of carrying a more specific choice into the range.

The propositions reached customers in 2025. By March 2026, eighty-four workstations had been sold: fifty-two wider and thirty-two narrower. That mix tells us what was purchased in the recorded period. It does not validate the original twenty-four-team study as a market forecast, nor establish that the wider arrangement is generally superior. Customers may have selected for reasons beyond the research, and a sale does not measure every aspect of use. I report the mix because a product decision should remain connected to what subsequently happened, while retaining the limits of the interpretation.

The commercial story changed. We could explain the work behind each option instead of claiming that one small outline solved every room problem. That required more disciplined selection material and a demonstration that did not quietly use space absent from the customer's proposed arrangement. I wanted the product page, quotation and demonstration to describe the same undertaking. Otherwise the range could be technically differentiated while the buying experience still pushed everyone towards whichever version looked simplest or cheapest at first glance.

I would ask the surrounding-work question earlier next time, before a compactness claim enters the launch plan. Once a phrase becomes part of a campaign, withdrawing it can feel like giving up a benefit the company already owns. In reality the benefit may never have been established at the breadth implied. An early task study helps the team decide what to promise before design effort and commercial expectations make that decision harder to revisit. It also gives dissenting colleagues a concrete account to examine instead of asking them to choose between user empathy and sales simplicity.

The lesson I would take into an oversight discussion is to ask where the product's stated boundary ends and the customer's required work continues. That question applies to configuration, delivery and evaluation as well as physical space. It does not require a board to approve a bench dimension. It helps the board understand whether a product proposition depends on work or cost that has been left outside the recommendation. In our case the omitted space was visible once we watched an ordinary task. I want our product decisions to make room for that observation before the catalogue makes the promise.