Show the journey around the translated screen

A translated interface can be visually persuasive. The layout looks orderly, the words appear complete and the buyer can imagine its own product in another language. Yet the screenshot may leave out the part of the journey that makes the localisation task difficult: the action that leads to the screen, the error that follows, or the source content that changes in the next release. I want a demonstration to help buyers recognise those questions. If it makes the work look simpler by removing them, it has improved the picture while weakening the explanation.

At Serlavi we prepared thirty-six demonstration journeys across Hindi, Bengali and Japanese, twelve in each language. The campaign treatment initially selected attractive screens from those journeys. Delivery review identified eleven examples whose presentation concealed relevant context. We held those eleven and spent ₹28 lakh on a four-week rebuild, while retaining the twenty-five that passed review. This was our own constructed demonstration material, not a review of client products. The exercise changed how we presented the service and how we planned specialist involvement before publication.

## Choose the context that explains the work

A demonstration cannot show every detail. Selection is necessary, and a marketing page should remain comprehensible to someone who is not a localisation specialist. The question is which omission changes the meaning of the example. A preceding action might explain why a label needs a different treatment; an error path might reveal text that the main screen never shows; a changing source might demonstrate why review is a continuing activity rather than a one-time translation. Those details earn their place when they help the buyer understand the service decision, not merely because the team can display more technical complexity.

The same principle applies to the language of the explanation. We should say what the example is intended to illustrate and which part of the work the company performs. A buyer may need linguistic review, interface testing, release integration or some combination. A polished screen does not establish that all those activities have been included. Marketing should make the relationship visible without turning the page into a proposal specification. The objective is to prepare a better conversation about scope, including the client's own responsibilities and the material needed to assess its product in context.

Constructed examples can be useful when they are clearly presented as demonstrations and do not borrow protected customer content. They allow a company to explain a recurring problem without disclosing a client's interface or commercial information. They also have limits. The example has been designed for a purpose and should not be treated as evidence that every real product will behave in the same way. I want the buyer to recognise the relevant question and bring its own context into discovery, rather than assume that a similar-looking screenshot means the scope, effort or outcome has already been established.

## Let specialists challenge the presentation early

In our review, delivery leader Farah Dolvani asked whether the selected screens represented the journeys accurately. Her colleagues examined the language and engineering aspects within their respective expertise. I did not try to settle those judgements through a marketing preference for a cleaner composition. At the same time, the creative team had a legitimate concern: too much context could make the material hard to follow. The solution was to develop the explanation with the specialists, choosing the surrounding interaction needed to make the example meaningful while preserving a clear path through the page.

The eleven rebuilt journeys were not a reason to discard the whole programme. Twenty-five had passed the agreed review and remained useful. Keeping those populations separate helped us explain the scope of the correction and avoid a dramatic but inaccurate account in which every original example had failed. The ₹28 lakh expense and four-week delay related to the rebuild. We retained the review record so that a later change to the demonstration could be assessed against the reason for the earlier decision, rather than return to the same attractive but incomplete screenshot because its context had been forgotten.

The timing of specialist review was the part I most wanted to improve. If the visual treatment is already polished and campaign dates are close, a necessary correction can feel like an attack on finished work. Bringing specialists in earlier allows the example and its presentation to develop together. It also gives the creative team better material to work with. The most interesting demonstration may come from the difficult interaction the original brief would have excluded. Review should therefore be part of shaping the story, not only a final approval step designed to catch an error after the expensive decisions have been made.

## Keep publication evidence distinct from customer outcomes

The completed set contained thirty-six journeys reviewed through the agreed process. That was the result we could support. We did not describe it as certification of the three languages, a general accessibility assessment or proof that every future client interface would work correctly. Nor did we claim that reviewing the demonstration established a revenue benefit. Publication quality and commercial performance are related questions, but they require different evidence. A useful marketing account should show the improvement in the material and then examine how buyers use it, rather than attach an unsupported business outcome to the act of finishing production.

The next review should ask whether the demonstration improves the discovery conversation. Do buyers identify the relevant preparation questions? Can account teams explain the difference between language review and integration without inventing scope? Are there recurring misunderstandings that the material still encourages? Those observations can guide another revision. They should be gathered with a method appropriate to the decision, not converted automatically into a broad claim about every buyer. A demonstration remains a working explanation of a service, and its usefulness can change when the service, product environment or audience changes.

For directors, the material issue is whether the company's market story is kept connected to its capability and obligations. They do not need to review every screen. They can ask who has authority to support a claim, how significant changes are handled and whether the organisation distinguishes illustrative material from evidence about delivered work. A business that lets the most attractive example define its promise may create expectations delivery never agreed to meet. A business that removes all illustration can make a valuable service unnecessarily difficult to understand. Oversight should encourage a disciplined relationship between explanation and evidence.

I would like our demonstrations to leave buyers better prepared, even when the next step is to recognise that their own source, interface context or release ownership needs more work. That is a useful marketing outcome because it improves the basis of the service conversation. The translated screen still matters; it is often the most immediate way to make the idea visible. It becomes more convincing when the journey around it is honestly represented. The aim is not to make a complex service look effortless, but to make its purpose and the work it requires clear enough for someone else to decide responsibly.