The product account should preserve the relationship that changes its meaning.

The 2023 small-shop prototype at the fictional Neravelle Assurance combined a base physical-damage proposition with an optional income element. In a comprehension exercise involving 120 owners, seventy-eight assumed the income benefit was part of the base and forty-two retained the distinction. Yunshao Pei favoured a broad package name because it gave distribution colleagues one coherent story to introduce. I understood that attraction, but the exercise showed that coherence was being achieved partly through an expectation the invented base proposition did not support.

The first suggestion was to keep the name and make the optional element more prominent further into the explanation. I asked whether that would undo the interpretation already formed at the opening. The research did not prove every reader would make the same assumption, but it did give us a specific reason to question the main description. We separated the base and optional accounts and supported CNY 12 million of product development and research. Underwriting, actuarial pricing and legal review retained responsibility for the decisions within their remits; the product team did not treat a wording exercise as authority to approve real coverage.

A later exercise involved one hundred different readers. Eighty-one correctly distinguished the base from the option and nineteen interpretations remained unresolved. We kept those nineteen visible and delayed the proposed launch while further product work continued. The two groups did not establish a precise population improvement rate. The evidence concerned how the revised prototype was understood in the defined exercise, not actual sales, claims, customer suitability or approval of a live policy. The result needed those boundaries to remain credible.

The trade-off was a less unified opening story and a later development timetable. I accepted both because the broad name was doing explanatory work we had not intended it to do. A product proposition can be attractive without making an option appear automatic. My responsibility was to change the description and the next development step when the owner exercise challenged the preferred account. The case illustrates a decision to preserve the product boundary before launch, rather than wait for a later event to reveal that the person had understood a different promise.

In 2003, as product manager at the fictional Calvren Insurance, I approved a summary using immediate-protection language for an invented scenario with a thirty-day illness waiting period. A sixty-reader exercise produced twenty-two interpretations of illness protection from day one and thirty-eight that retained the stated distinction. Lanqiu Zhen challenged the headline. I initially pointed to the waiting-period qualification elsewhere in the material, believing the explanatory material was available to anyone who read further. The exercise showed why availability was not the same as an understood relationship.

The main description gave the reader an expectation before the qualification tried to narrow it. I needed to change that description rather than defend it through the length of the document. We withdrew the wording I had endorsed and supported CNY 1.6 million of explanatory redevelopment. The revised account placed the fictional start and condition distinctions together and used a defined scenario to examine the interpretation. The case does not describe the actual cover under any real policy, and no conclusion about a policyholder’s medical or financial position follows from it.

The subsequent exercise used fifty-four different readers. Forty-five retained the distinction and nine interpretations remained unresolved. I kept the latter group in the account. The revision was a product-development response supported by bounded comprehension evidence; it was not a claim that every person now understood the proposition. The different populations also meant that a simple subtraction of percentages would not establish a precise general improvement. Legal interpretation, underwriting and applicable approvals remained with their own accountable specialists throughout the work.

The cost included revisiting material colleagues had prepared around my earlier approval and accepting that the headline itself needed correction. I could not attribute the problem entirely to readers failing to study the qualification. The responsibility lay in the account I had allowed to lead. The practical lesson was that a summary should preserve the condition that changes its meaning, even when a fuller wording remains available. An explanation becomes more useful when its own structure helps the reader understand the boundary, rather than relying on the reader to discover and reconcile an apparent contradiction later.

A 2012 travel-product illustration at the fictional Neravelle Assurance used an invented CNY 10000 aggregate baggage limit and a CNY 2000 per-item cap. Both numbers appeared in the material. In an eighty-reader scenario exercise, fifty-six interpreted the larger figure as potentially available for one item, while twenty-four retained the per-item distinction. A distribution colleague wanted to keep the aggregate as the dominant message because it was easy to recognise. I wanted the explanation to preserve how the two limits worked together within the fictional scenario, rather than assume that printing both figures achieved that understanding.

We examined the point at which the reader moved from seeing the headline amount to imagining an individual loss. Repeating the smaller number in a footnote would not necessarily change that mental step. I supported CNY 3.8 million of explanatory redevelopment, including two worked illustrations and a direct statement of both limits. The illustrations were descriptions of invented conditions, not calculations of a real claim. Claims, underwriting and legal colleagues retained their actual authority, and the product team did not promise an entitlement by demonstrating the hypothetical relationship.

A different ninety-two-reader exercise followed. Sixty-eight interpretations retained the relationship and twenty-four remained unresolved. The result showed why the revised explanation still needed examination. It did not justify announcing universal comprehension or a population-level improvement calculated from two separate groups. Nor did it establish a payout, an approval or an effect on sales. The useful outcome was a more explicit illustration and a defined account of what readers still found difficult, with the remaining work kept inside the product discussion.

The trade-off was a less dominant headline and more space devoted to a condition that constrained it. I accepted that cost because the aggregate alone was encouraging an unsupported single-item expectation in the exercise. The case taught me that prominence is part of the explanation. A smaller figure can be numerically present and functionally absent from the reader’s account. Product leadership should examine that relationship before treating a document containing the correct numbers as evidence that the intended proposition has been understood.

The 2018 home-assistance review at the fictional Neravelle Assurance examined a proposition describing a call-out service. In a 160-reader exercise, fifty-six assumed every repair cost was included and 104 retained the stated service distinction. The service sponsor wanted to preserve one reassuring assistance message. I understood the desire for a straightforward account at a stressful moment, but the exercise showed that the message could be heard as a different financial promise. A service arrangement and reimbursement of all repair costs were not interchangeable descriptions of the invented proposition.

I asked the team to separate what assistance was arranged from which costs the hypothetical account actually included. The distinction had to appear in the main explanation, not as a surprise after the broad service promise. CNY 8.6 million supported product and communication work on that separation. Service operations, contracting, claims and legal review kept their respective responsibilities. The decision did not alter actual customer contracts or establish a new charging system through product copy alone. The scope of the work needed to be as clear internally as the proposition was intended to be externally.

The retest involved 120 different readers. Ninety-four retained the intended distinction and twenty-six interpretations remained unresolved. I did not treat the latter group as evidence that their expectations were irrelevant. They identified further work in the explanation or proposition. The exercise supplied no subsequent claims outcome, actual repair-cost finding or legal determination. It also did not establish how everyone would interpret the material during a real household incident. We recorded the narrower development result and the uncertainty that still required attention.

The commercial description became less sweeping, and the teams had to explain a service boundary that the original reassurance had left indistinct. I accepted that consequence. The purpose of an assistance proposition is not served by allowing reassurance to become an unexamined expectation about payment. My contribution was to make the distinction consequential in the product review while leaving the specialised decisions with the people authorised to make them. A useful service story can be calm and clear without saying more about reimbursement than the actual proposition supports.

The 2025 comparison at the fictional Neravelle Assurance covered thirty-six proposed renewal wordings. Twenty-four changed benefit limits and twelve changed presentation only. A programme colleague wanted a common administrative-update message to keep the communication consistent. I opposed using that description across the full set. A revised layout and an altered benefit boundary were different kinds of change. Consistency in the message would have made the account shorter by reducing the reader’s ability to recognise what had actually changed in the proposed proposition.

I asked for the comparison to begin with the effect of the revision, then determine how that effect should be explained. CNY 14 million supported a comparison-and-explanation programme. The twenty-four benefit-limit changes remained distinct from the twelve presentation revisions. The work required product colleagues to coordinate with underwriting, distribution, claims and legal owners rather than classify every difference from the appearance of the document alone. The programme did not itself approve the proposed changes, establish that customers had accepted them or decide what process applied to an actual renewal.

The consequence was a less uniform communication task. Some changes needed a fuller explanation, and a shared administrative label could no longer carry the whole programme. I accepted that extra work because the reason for communicating a revision is to make the relevant difference understandable. The fictional case claims no improvement in renewal rate, retention or customer comprehension after the programme. It records the decision to preserve the distinction and the funded work required to prepare the account. Subsequent approval and customer responses would need their own evidence.

The lesson was to resist a category that describes our work rather than the person’s changed proposition. A team may regard every document in a programme as part of one administrative exercise, while the reader encounters a material difference in what is being offered. Product leadership should ask which perspective the label serves. I wanted the comparison to make an altered limit visible without announcing a conclusion about its suitability or legality. That leaves the responsible specialists and the customer able to examine the proposed change on its actual terms, rather than through a reassuring description that fits only part of the set.