The design team brought knowledge the reader did not have
In a 2025 review, thirty-six participants interpreted a product's folding instructions. Fifteen misread one sequence. The authors could explain what the illustration meant because they already understood the mechanism and the intended order of actions. The reviewed readers did not consistently receive that meaning from the material itself. We funded ₹42 lakh for illustration, translation and retesting before claiming that revised instructions had resolved the problem.
The finding was about the instructions and the reviewed group. It was not a judgement that fifteen people were careless or that every future user would misunderstand the product. It did not rank languages or establish an injury outcome. Those boundaries mattered because a comprehension result can be used carelessly to create a story about readers rather than examine the communication the enterprise supplied.
A product team carries a great deal of invisible knowledge. Designers have seen the mechanism in different states, discussed its constraints and watched colleagues demonstrate it. An arrow or image can activate that shared understanding with very little detail. A reader encountering the product for the first time may not know which part moves, what changes between images or what the sequence assumes. The instruction has to communicate across that difference.
I wanted the response to begin with the meaning we intended to convey and the meaning participants actually took from the material. That is a more useful question than whether the page had been approved or translated on schedule. Approval and delivery are necessary process events, but neither establishes comprehension. The enterprise needs evidence that the relevant reader can understand the intended sequence under the conditions being claimed.
Translation and illustration answer connected but different questions
The programme included both illustration and translation work because the ambiguity could not be assumed to belong to only one medium. Translating an unclear visual sequence may preserve the same uncertainty in another language. A clearer picture may still depend on wording that readers interpret differently. The work needed to connect the two, while retaining the appropriate technical and language expertise.
This does not mean that every instruction should become longer. More words can make an account harder to follow if they repeat what is already clear or bury the decision a reader must make. The question is whether the necessary meaning is accessible. A concise image sequence can be effective when it conveys the relevant change, while a short phrase can be misleading if it assumes knowledge the reader does not have.
The review also needed to distinguish understanding from performance of an actual operating task. Our stated finding concerned interpretation of one folding sequence by the participants. It did not establish every aspect of safe use, product suitability or field behaviour. Qualified safety and product-acceptance owners retained their responsibilities. The fictional case provides no directions for using or modifying a real folding mechanism.
I would not ask an executive committee to choose the angle of every illustration. I would ask it to understand whether the enterprise has treated communication as part of the product proposition and whether the evidence supports the intended claim. The technical owner should be able to explain what the reader needs to understand and how the review examined that question. That is different from reporting only that the document has been issued.
The thirty-six-person population also remained visible. Fifteen misinterpretations described that review; they were not a universal rate for all users, products or languages. The result justified further work without establishing the scale of every possible field consequence. A later assessment of revised material would need its own population and conditions before it could support a changed conclusion.
Publication is a milestone before understanding is demonstrated
The ₹42 lakh programme was approved work, not evidence that comprehension had already improved. I wanted the enterprise account to retain that sequence. The finding came first, the response followed and the result of the response remained to be assessed. Compressing those stages into a success story would have removed the very question the programme was intended to answer.
The response also needed to avoid blaming the final reader for a design assumption. When the authors know the mechanism well, they may find it difficult to imagine another interpretation. That difficulty is a reason to examine the material with people who do not share the same background. It is not proof that those people are unsuitable users. Leadership should make room for the uncomfortable finding rather than protect the authors' confidence at the expense of the product account.
This is where engineering and communication responsibilities meet. The instruction must remain technically correct, but technical correctness alone does not establish that its meaning reaches the reader. Equally, a friendly or attractive presentation cannot compensate for an inaccurate sequence. The work needs both kinds of competence, with clear approval responsibilities and evidence that the combination serves the intended purpose.
My own earlier acoustic approval helps me recognise the temptation to treat one form of evidence as complete. I had accepted an unloaded demonstration for a loaded-use claim. In the instruction case, the comparable temptation would be to accept author understanding as evidence of reader understanding. The technical tasks are different, but the executive question is similar: whose condition does the evidence actually represent?
For a board, the concern is whether material product communication is governed by evidence rather than assumed competence. Directors need not rewrite instructions. They can ask how management knows that an important statement or sequence is understood, what the review actually covered and what remains unresolved. They can also ask whether programme reporting distinguishes publication from demonstrated improvement.
The strongest response to a comprehension finding is not necessarily a dramatic redesign of every document. It is a proportionate investigation of the meaning that failed to travel. The enterprise should understand the specific gap, organise the relevant expertise and assess the revised material honestly. That approach can produce a more useful result than a broad declaration that all instructions have been simplified without evidence of what changed.
I keep the fifteen interpretations in the case because they remind me that communication is an encounter between a product account and a reader's understanding. The authors' intention is only one side of that encounter. Publication makes the material available; it does not establish what the reader takes from it. Our responsibility was to examine that gap, fund the work and wait for evidence before calling the revised sequence complete.