How I connect the attractive feature with the task it must support

The product brief for a 280-home community contained a sixty-square-metre shared workroom. It was easy to describe as flexible: residents could work there, make calls or use the larger space for an occasional event. The difficulty appeared in the activity accounts from twenty-eight research participants. Sixteen described a need for private calls; twelve described quiet focus. These were not simply two ways of using the same desk. Their expectations could conflict even while each resident was making an entirely reasonable use of a room advertised for work.

Graham Kelvenby favoured keeping the larger room, partly because its flexibility made the amenity list stronger and allowed more possible event arrangements. I accepted that splitting the area would remove one of those possibilities. I did not think the word flexible explained how the everyday conflict between calls and quiet would be handled. Asking residents to negotiate it repeatedly after occupation would make them complete a product decision we had avoided in the brief.

I supported A$1.7 million development of two thirty-square-metre rooms instead of one sixty-square-metre room. The brief gave one setting to quiet work and the other to calls, with the actual design requiring the appropriate architectural, acoustic and other specialist assessment. A later eighteen-person prototype exercise included eleven quiet users and seven call users. It supplied further product observation, not permission to construct the space or proof of a universal resident preference.

The choice surrendered the single larger event room. That cost belongs in the case because the split was not simply an improvement that made every use better. It privileged two recurring activities while limiting another. We kept the full trade-off visible to the development and operating teams instead of presenting two rooms as though they retained every capability of the original one.

I take from the case a practical test for amenity language. If a word such as flexible covers activities that interfere with each other, the product needs a more specific account of how the conflict will be resolved. The plan can then be examined for its intended use, with the technical design and approvals still carried out by the people responsible for them.

At Torvellan Living I approved a wardrobe module whose external opening was 600 mm. The number had travelled through the product review as a useful description of the storage feature. In the physical trial, however, the clear opening through which an item could pass was 550 mm. Twelve of twenty-four participating residents brought 560 mm cases that could not fit. The specification had not become numerically false; the product account had used the wrong dimension to answer the resident’s question.

Fiona Marvellan challenged my approval. I initially thought a clearer drawing could explain the difference between the external and clear opening. She asked why the resident should be expected to adapt to a module that the product brief had presented as suitable for the task. That moved the discussion from improving an explanation to changing the design decision I had endorsed.

We committed A$380000 to redesign the module with a 650 mm external opening and 590 mm clear opening, allocating another 50 mm to it. The wider allocation was the sacrifice. It had to be reconciled with the surrounding product layout rather than treated as space that appeared without consequence. Qualified design colleagues retained the technical work and any applicable assessment; my role was to change the brief and accept the allocation it required.

A separate twenty-person prototype exercise recorded seventeen items fitting and three larger-item exceptions. I did not describe that as every resident’s storage need solved. Nor could a sample fit test establish a general accessibility or building-compliance conclusion. The result supported the revised product choice within the scope observed, while the larger exceptions remained visible.

This case belongs in my record because the tempting account would begin with the successful redesign and leave out the dimension I approved. The more useful account shows why I changed my mind. A correct number can still be the wrong basis for a product claim. We needed the dimension that governed the object’s movement, and we needed to acknowledge the room taken up by improving it. Both facts made the brief more usable than another explanation defending its earlier form.

The proposed parcel feature at Mervellen Places contained 120 standard lockers. The count was prominent in the product discussion because it was easy to compare and made the amenity appear generous. A fortnight of observation changed the question. Of 400 parcels in the reviewed set, 310 fitted the standard compartment and ninety did not. The feature count had said little about the larger objects that would still arrive at the building.

Graham Kelvenby wanted to retain the 120-slot headline and let the service team handle the oversized items separately. That preserved a larger ordinary capacity and a simpler product description. I thought it left too much of the observed variety outside the physical proposition. A service exception was still necessary for some objects, but it should not be the only answer to a recurring size difference already visible in the research.

We chose eighty standard and twenty larger compartments, reducing the total to 100, with a separately handled route for items outside that mix. A$640000 supported the programme. The choice required the team to explain why a lower compartment count could be a more appropriate design response. It also required an operating account for the oversized route rather than a vague assurance that somebody at the building would deal with whatever did not fit.

The 400 observations described this reviewed fortnight. They did not establish the permanent distribution of every parcel at every community. The product decision made no claim that theft had fallen, that all deliveries could be accepted or that responsibility for a particular parcel had been legally settled. Those matters would need their own evidence and appropriate agreements. The case records the selected mix and the continuing exception path.

The trade-off was visible: twenty fewer compartments in return for larger accommodation within part of the installation. I wanted the executive account to preserve both sides. If we reported only the number of lockers, we would have made the revised proposition look worse for doing the work more specifically. Product leadership needs a vocabulary for usefulness that can survive a reduction in the easiest number to put into the brochure.

A six-guest-suite amenity proposal created a strong initial picture of hospitality within a residential community. It also consumed six equivalent rooms that could have supported other uses. In the review involving seventy-two households, forty-two accounts focused on overnight visitors and thirty focused on resident storage. The two needs were not competing marketing slogans. They concerned how people would use a limited amount of shared space after moving in.

Graham Kelvenby supported retaining all six suites. They were easier to present as a distinctive amenity, while storage seemed more ordinary and potentially less valuable in the viewing conversation. I agreed that a guest proposition could matter. I questioned whether its visual appeal should make the resident’s everyday storage problem a secondary issue by default. The product brief needed to consider the space displaced by the more attractive feature, not just the feature’s own merits.

We chose four guest suites and two equivalent rooms for storage, with A$2.6 million development. The choice reduced the scale of the guest proposition and made room for the other use. It did not allocate every household’s belongings or establish a universal entitlement to a shared room. The detailed design, operating arrangements and relevant specialist review still had to define how the spaces would work.

The household accounts were evidence for a product decision, not a forecast of actual guest nights or an explanation of future rent. We did not treat forty-two expressions of a visitor need as forty-two bookings, and we did not infer that the thirty storage accounts represented all residents who might eventually use it. The result recorded here is the chosen development mix and the work funded to pursue it.

I value the case because it made an ordinary need compete on equal terms with a feature that photographed better. The product leader had to choose, and the choice gave something up. Four guest suites were not six. But neither were the two storage rooms empty space left over after the important design work. They were part of the residential proposition, selected because a home must keep working when the viewing is finished and the possessions have arrived.

The amenity-booking prototype began with an app-only route. It fitted the product team’s preference for one visible flow and offered a straightforward demonstration of the service. In a task exercise with ninety-six residents, seventy-five completed the booking and twenty-one could not. The result did not identify a single universal cause or justify assumptions about the residents who encountered difficulty. It did show that the preferred route could not be treated as the complete service proposition for the reviewed group.

Fiona Marvellan proposed adding assisted and telephone routes. The opposing view was to improve the application first and preserve one process, avoiding additional requests that staff would have to manage. I recognised that an extra channel can create expense and ambiguity. I supported it only with an agreed operating account, rather than treating the publication of a telephone number as completion of the product work.

A$1.2 million funded development of the additional routes and the process through which requests would be received and confirmed. Product and resident-service colleagues had to agree which request details were needed, the responsible team and the way a resident would know whether a booking had actually been made. The channel was not intended to imply automatic access to any space or to bypass the arrangements governing its use.

The prototype finding remained seventy-five completions and twenty-one incomplete tasks in that exercise. We did not turn the introduction of another route into a claim of universal accessibility, legal compliance or a measured adoption improvement. Those would require different evidence. The recorded decision was to make the service available through more than the original application flow, with the supporting work assigned rather than assumed.

My group-company nominee role made the fulfilment question particularly important. A product promise can arrive at a subsidiary as a stream of requests without the means to answer them. I wanted the operating responsibility designed alongside the new route. The case therefore concerns more than a digital feature: it asks whether the resident can reach a service whose owner understands and can carry out the commitment the product description has made.