Translate | ISO 9241-11:2018 Usability Research, Task Success, Context of Use and User Satisfaction

Translate | ISO 9241-11:2018 Usability Research, Task Success, Context of Use and User Satisfaction: To translate ISO 9241-11:2018 usability research accurately, preserve the difference between what a user achieved, the effort needed to achieve it, the user’s reaction to the experience and the context in which the task occurred. A statement such as ‘80% completed the task’ is incomplete without its participant group, task definition and conditions. This article gives UX researchers, multilingual interface teams and product managers a practical method for translating usability study findings, task-success metrics, efficiency observations and satisfaction reports without making a system sound easier or more effective than the evidence shows.

ISO 9241-11:2018 provides a framework for understanding usability across systems, products and services. It concerns usability as an outcome of use, rather than prescribing one universal test protocol or score threshold. That distinction matters when a translator works with research summaries, executive dashboards, accessibility notes, customer interviews or global product release documents. A credible translation preserves the object evaluated, the specified users, the goals and the relevant environment. It separates observed performance from researcher interpretation and makes negative user comments just as intelligible as positive ones.

At a glance. Quick guide: identify users, goals and context of use; keep effectiveness, efficiency and satisfaction separate; define every metric and denominator; retain failed or abandoned tasks; distinguish reported feelings from observed behaviour; preserve assistive-technology details; state sample limitations; and validate the target-language summary with a bilingual researcher before it is published.

What this guide helps you translate

A working team may receive a short label, a long report, a user-facing summary, an internal register and an approval email that all describe the same matter differently. This guide is written for UX researchers, accessibility reviewers, interface localization teams, product managers and multilingual usability analysts. Its practical object is usability studies and user-research findings, not the whole field of translation. Each exercise uses original invented source passages, so the examples illustrate decision-making rather than reproduce licensed ISO clauses. A confident translator should be able to tell the reader what occurred, what is proposed, who is responsible, what remains uncertain, and which statement is supported by evidence. Those five questions are more reliable than treating fluent syntax as proof of accuracy.

The official ISO catalogue describes ISO 9241-11:2018 at https://www.iso.org/standard/63500.html. This article explains how to communicate documents influenced by that subject matter; it is not an authorized translation, substitute for the licensed standard, legal opinion, certification or professional sign-off. Jurisdiction-specific duties, product rules or research ethics must be checked with the responsible specialists. Where an actual source document is vague, the translator’s job is to expose the question rather than supply an answer that the evidence cannot establish.

A practical table of contents

1. Read the source as a decision
2. Ten core translation distinctions
3. Twenty-four worked source-to-reader cases
4. Controlled terminology register
5. Independent bilingual review and release
6. Frequently asked questions
7. Four-week practice plan and further reading

1. Read the source as a decision, not a string of words

Before opening a translation tool, identify the actual document: a draft, specification, study result, approved statement, training plan, label or public advisory. Ask who wrote it, who must rely on it, and what decision follows. The same English verb can carry a different consequence in a marketing headline, internal note, legal record or safety instruction. A natural target-language sentence should preserve that decision. If the document says an action is planned, the translation should not announce its completion. If it reports a sample, the translation should not claim the entire population. If it describes an authorized role, the translation should not assign that responsibility to someone else.

Work in two passes. In the first pass, map propositions: subject, action, object, condition, time, evidence and status. In the second pass, draft readable sentences for the intended audience. This order prevents a common failure: writing something beautiful before understanding exactly what the writer has and has not claimed. Keep difficult terms in a working register, but do not turn the page into a glossary before solving the reader’s question. Definitions become useful when tied to a real decision. A short text can contain several different decisions, particularly when numbers, permissions and exceptions appear together.

For multilingual teams, treat every approved translation as a controlled edition. Record locale rather than language alone where conventions differ; maintain a source version and target version; identify the approving owner; and note unresolved terminology. Translation memory can accelerate consistency, but an old approved segment does not automatically apply to a new product, project, role or research population. The reviewer needs the surrounding document and the original data, not merely a side-by-side sentence pair. Good revision therefore combines language expertise with source-system literacy and an understandable path for correction.

2. Ten core translation distinctions

1. Usability is contextual, not an unconditional property

A product can be usable for one group and task yet difficult for another. Always state the user, goal, setting and available resources. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

A translation that says an application is ‘universally intuitive’ may exceed a narrow test with trained employees in a quiet laboratory. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Add a concise context-of-use box and never silently transfer a result to a new population. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

2. Effectiveness concerns goals achieved

Success rate, accuracy and completeness need their task definitions, not just a favorable percentage. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

A participant who reached the wrong account screen has not necessarily completed the intended task because the interface showed a success banner. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Map every headline metric to an observable success criterion that can survive translation. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

3. Efficiency includes resources expended

Time on task, effort and extra steps can mean different things depending on how they were recorded. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

A shorter duration can reflect abandonment, familiarity or skipping a necessary check rather than better usability. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Translate measurement method and exclusions alongside performance claims. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

4. Satisfaction is reported or inferred carefully

Survey ratings, spontaneous remarks and researcher judgments are different evidence types. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

A five-star scale is not automatically comparable to a seven-point agreement scale; both are vulnerable to language and culture effects. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Keep instrument wording and response anchors together in the bilingual evidence pack. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

5. Task boundaries determine what counts

Starting a journey, completing a transaction, correcting an error and locating help are distinct tasks. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

A study can report success at navigation while participants fail to understand the consequences of pressing a button. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Translate the entire action chain, including confirmation and recovery steps. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

6. Participant characteristics belong with findings

Experience level, language proficiency, accessibility needs and device familiarity can explain results. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

Calling all users ‘novices’ when several have extensive experience disguises what was actually sampled. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Use participant descriptors only as far as consent and the study permit; preserve anonymization. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

7. Observations are not recommendations

A researcher may observe hesitation and then recommend a design change. Those statements have different evidentiary statuses. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

A translation that turns ‘participants hesitated’ into ‘the design is defective’ overstates a descriptive finding. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Keep observation, interpretation and proposed action in distinct fields. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

8. Failure evidence should remain visible

Abandonment, accidental actions, navigation loops and recovery errors provide information that positive averages cannot. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

Summaries that omit unsuccessful participants make a release look safer or easier than the study supports. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Maintain a failure taxonomy and compare its target-language categories with original session records. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

9. Translations affect the test itself

The same localized wording can alter a participant’s response, perceived difficulty or ability to finish. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

Changing a button’s meaning while testing a localized interface creates a different task, not simply a different translation. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Treat UI copy and questionnaire translation as experimental materials with controlled versions. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

10. A result is not a certification

ISO 9241-11 does not itself supply a universal pass score or an automatic usability certificate. This distinction is worth making explicit because an international reader may lack the original organization’s context. A word with a familiar everyday meaning can have a narrower professional meaning in usability studies and user-research findings. Define the term through the action it permits, the conclusion it supports and the evidence available, rather than through a misleading one-word synonym.

A marketing summary claiming ISO-approved usability because the team cited the framework is not supported by that citation. The translator should compare the source phrase with the reader’s likely inference: would someone change a purchase, safety behaviour, research interpretation or employment decision on the basis of this sentence? If so, the scope and conditions belong in the visible text, not hidden in the translator’s assumptions. Publish only study-specific conclusions and note the limits of the method. Keep a short decision log showing who resolved any ambiguity and why the accepted expression is defensible.

3. Twenty-four worked translation cases

The following examples are fictional but designed to model the kinds of records encountered in real international work. They give a source expression, a misleading shortcut, a reader-safe rendering, the practical reason for the distinction and a specific review test. The ‘reader-safe’ sentence is an explanatory English reformulation for translators to adapt into their actual target languages, not an official prescribed translation. Use the complete source document, and when needed consult an authorized subject specialist before publication.

Case 1: A completed checkout

Imagine a project file containing this source line: “Eight of ten participants completed checkout without facilitator help.”. It looks compact, yet several hidden questions must be settled before a translator can write for an international reader. A tempting but misleading adaptation would be “All customers can check out effortlessly.”. Two people did not complete the task, and the sample is neither the entire market nor a guarantee of low effort. The error is not merely stylistic. It changes what a reader can reasonably decide or rely on, especially when the phrase is lifted out of its original document and placed in a report summary or search result.

Write the working translation as “Eight of ten tested participants completed the defined checkout task independently.”. Notice that it avoids the unsupported extra promise in the tempting version. The goal is not cautious language for its own sake; the goal is to preserve the source’s evidence and consequence. Two people did not complete the task, and the sample is neither the entire market nor a guarantee of low effort. When the target audience is unfamiliar with the document type, a precise subordinate clause can be more helpful than a polished but overconfident headline.

For release, Check the definition of completion, assistance rule and participant count. Afterwards, test the target phrase with a representative reader: what happened, what remains conditional, who acts next, and what information is missing? If the answers differ from the original, rewrite and retest rather than concealing the problem in a footnote. Preserve the source excerpt and reviewer sign-off so a later revision can trace how the decision was reached.

Case 2: A fast abandonment

A multilingual team receives a document stating “Median time on task fell because three users exited before confirming.”. Before drafting, the translator should identify the speaker, relevant evidence, time frame and action requested. The shortcut “The redesigned flow was faster.” may sound fluent, but it crosses an important boundary. Shorter elapsed time is not automatically greater efficiency when the goal was not achieved. A responsible translation should be understandable without implying powers, results or permissions that the source never established.

The controlled rendering should read “The median recorded duration fell; three early exits must be considered when interpreting the result.”, adapted grammatically for the chosen locale. This offers a clearer connection between the observed fact or rule and the decision it supports. Shorter elapsed time is not automatically greater efficiency when the goal was not achieved. If readers need a definition, place it close to the decision point. Do not replace an unfamiliar technical distinction by a stronger claim simply because that stronger claim is easier to market.

The final quality gate is specific: Compare time calculations with the event log and failure classification. Do not settle the issue merely by running another machine translation pass; a second fluent sentence can repeat the same conceptual error. Have an independent reviewer inspect the numerical, temporal or authority-related fields and the page layout. If publication requires an organizational commitment, it is the authorized owner rather than the translator who makes that commitment.

Case 3: A satisfaction scale

In this fictional case the original reads “The mean satisfaction response was 5.1 on a seven-point scale.”. It will be easy to concentrate on grammar and overlook the decision hiding inside the sentence. One incorrect rendering is “The product received a satisfaction score of 5.1 out of five.”. Changing the scale denominator invents a near-perfect score. A reader might repeat the simplified statement in an email, spreadsheet or press release, where the missing qualifier would become even harder to recover.

For a reader-facing edition, prefer “The observed mean was 5.1 on the study’s seven-point scale.”. It answers the question the original was capable of answering, without pretending to answer larger questions. Changing the scale denominator invents a near-perfect score. A small qualifier often carries enormous practical value. Preserving that qualifier can matter more than mirroring word order, and it prevents the next editor from unknowingly widening a statement.

To review this case, Keep original response anchors and check whether higher values mean agreement. A bilingual colleague should then read the target wording without seeing the approved English reformulation and explain what action or conclusion it licenses. Compare that explanation against the source and flag any added certainty, widened audience or missing condition. Record the final decision in the terminology and version log. A translation becomes ready for release only when both its language and its operational interpretation have been checked.

Case 4: A multilingual questionnaire

Consider an editor asked to localize the source wording “The Spanish version used a different term for ‘confidence’ from the English form.”. The proposed shorthand, “All languages measured exactly the same feeling.”, is superficially convenient, particularly on a crowded page. A semantic shift can change the construct being measured even if survey layout is identical. The central check is not whether every word sounds technical; it is whether a reader could use the translation to reach the same sound conclusion as someone reading the original with its proper context.

A safer target-language-ready explanation is “The language versions used different confidence wording; comparability requires review.”. This keeps the critical distinction visible while leaving room for idiomatic wording in a specific language. The translator should preserve the factual object, status and limits of the source. A semantic shift can change the construct being measured even if survey layout is identical. If an equivalent everyday term creates a different commitment, use a short clarification rather than borrowing an inaccurate prestigious-sounding label.

A practical verification test is to Compare the questions through bilingual cognitive interviewing before merging results. Ask a subject reviewer to state what evidence would make the sentence false, and confirm that the translation points to the same evidence. If the reviewer cannot identify an owner or a status, stop the publication route and request clarification. The corrective step should be visible in the release record, because future translators need to distinguish a resolved ambiguity from a guess that happened to survive one review.

Case 5: A research setting

Imagine a project file containing this source line: “Participants tested on desktop computers with stable broadband.”. It looks compact, yet several hidden questions must be settled before a translator can write for an international reader. A tempting but misleading adaptation would be “The experience was validated for mobile users everywhere.”. A mobile environment introduces different screen sizes, gestures and connectivity constraints. The error is not merely stylistic. It changes what a reader can reasonably decide or rely on, especially when the phrase is lifted out of its original document and placed in a report summary or search result.

Write the working translation as “The usability findings come from desktop sessions under stable-network conditions.”. Notice that it avoids the unsupported extra promise in the tempting version. The goal is not cautious language for its own sake; the goal is to preserve the source’s evidence and consequence. A mobile environment introduces different screen sizes, gestures and connectivity constraints. When the target audience is unfamiliar with the document type, a precise subordinate clause can be more helpful than a polished but overconfident headline.

For release, Retain hardware, software and environmental notes in the summary. Afterwards, test the target phrase with a representative reader: what happened, what remains conditional, who acts next, and what information is missing? If the answers differ from the original, rewrite and retest rather than concealing the problem in a footnote. Preserve the source excerpt and reviewer sign-off so a later revision can trace how the decision was reached.

Case 6: A participant group

A multilingual team receives a document stating “The study included experienced account administrators only.”. Before drafting, the translator should identify the speaker, relevant evidence, time frame and action requested. The shortcut “All new users understood the interface.” may sound fluent, but it crosses an important boundary. Experience lowers friction and changes expectations, so general claims about novices are unsupported. A responsible translation should be understandable without implying powers, results or permissions that the source never established.

The controlled rendering should read “The tested group consisted of experienced account administrators.”, adapted grammatically for the chosen locale. This offers a clearer connection between the observed fact or rule and the decision it supports. Experience lowers friction and changes expectations, so general claims about novices are unsupported. If readers need a definition, place it close to the decision point. Do not replace an unfamiliar technical distinction by a stronger claim simply because that stronger claim is easier to market.

The final quality gate is specific: Confirm recruiting criteria and participant descriptors. Do not settle the issue merely by running another machine translation pass; a second fluent sentence can repeat the same conceptual error. Have an independent reviewer inspect the numerical, temporal or authority-related fields and the page layout. If publication requires an organizational commitment, it is the authorized owner rather than the translator who makes that commitment.

Case 7: A corrected mistake

In this fictional case the original reads “Participants succeeded after receiving a hint from the moderator.”. It will be easy to concentrate on grammar and overlook the decision hiding inside the sentence. One incorrect rendering is “Every participant succeeded independently.”. Assisted completion differs from unassisted success and affects any effectiveness metric. A reader might repeat the simplified statement in an email, spreadsheet or press release, where the missing qualifier would become even harder to recover.

For a reader-facing edition, prefer “The participants completed the task after receiving the recorded moderator hint.”. It answers the question the original was capable of answering, without pretending to answer larger questions. Assisted completion differs from unassisted success and affects any effectiveness metric. A small qualifier often carries enormous practical value. Preserving that qualifier can matter more than mirroring word order, and it prevents the next editor from unknowingly widening a statement.

To review this case, Inspect intervention logs and distinguish moderator prompts from system guidance. A bilingual colleague should then read the target wording without seeing the approved English reformulation and explain what action or conclusion it licenses. Compare that explanation against the source and flag any added certainty, widened audience or missing condition. Record the final decision in the terminology and version log. A translation becomes ready for release only when both its language and its operational interpretation have been checked.

Case 8: A missed privacy control

Consider an editor asked to localize the source wording “Most participants completed registration but overlooked optional privacy settings.”. The proposed shorthand, “Participants understood all registration controls.”, is superficially convenient, particularly on a crowded page. Transaction completion is not proof of comprehension or informed choice. The central check is not whether every word sounds technical; it is whether a reader could use the translation to reach the same sound conclusion as someone reading the original with its proper context.

A safer target-language-ready explanation is “Most finished registration; the optional privacy settings were often overlooked.”. This keeps the critical distinction visible while leaving room for idiomatic wording in a specific language. The translator should preserve the factual object, status and limits of the source. Transaction completion is not proof of comprehension or informed choice. If an equivalent everyday term creates a different commitment, use a short clarification rather than borrowing an inaccurate prestigious-sounding label.

A practical verification test is to Review the task objective and whether settings awareness was independently assessed. Ask a subject reviewer to state what evidence would make the sentence false, and confirm that the translation points to the same evidence. If the reviewer cannot identify an owner or a status, stop the publication route and request clarification. The corrective step should be visible in the release record, because future translators need to distinguish a resolved ambiguity from a guess that happened to survive one review.

Case 9: An error recovery

Imagine a project file containing this source line: “Six users restored their saved draft after following a help article.”. It looks compact, yet several hidden questions must be settled before a translator can write for an international reader. A tempting but misleading adaptation would be “The application never loses data.”. Successful recovery says nothing about whether a loss event can occur, and help usage adds effort. The error is not merely stylistic. It changes what a reader can reasonably decide or rely on, especially when the phrase is lifted out of its original document and placed in a report summary or search result.

Write the working translation as “Six tested users recovered their drafts using the documented help route.”. Notice that it avoids the unsupported extra promise in the tempting version. The goal is not cautious language for its own sake; the goal is to preserve the source’s evidence and consequence. Successful recovery says nothing about whether a loss event can occur, and help usage adds effort. When the target audience is unfamiliar with the document type, a precise subordinate clause can be more helpful than a polished but overconfident headline.

For release, Check whether any drafts were permanently lost and how many assistance steps were necessary. Afterwards, test the target phrase with a representative reader: what happened, what remains conditional, who acts next, and what information is missing? If the answers differ from the original, rewrite and retest rather than concealing the problem in a footnote. Preserve the source excerpt and reviewer sign-off so a later revision can trace how the decision was reached.

Case 10: An accessibility session

A multilingual team receives a document stating “A screen-reader user encountered an unlabeled action button.”. Before drafting, the translator should identify the speaker, relevant evidence, time frame and action requested. The shortcut “All disabled users could not use the service.” may sound fluent, but it crosses an important boundary. One observed barrier is important, but not a measure of every disability or assistive setup. A responsible translation should be understandable without implying powers, results or permissions that the source never established.

The controlled rendering should read “One participant using a screen reader encountered an unlabeled action button.”, adapted grammatically for the chosen locale. This offers a clearer connection between the observed fact or rule and the decision it supports. One observed barrier is important, but not a measure of every disability or assistive setup. If readers need a definition, place it close to the decision point. Do not replace an unfamiliar technical distinction by a stronger claim simply because that stronger claim is easier to market.

The final quality gate is specific: Name the tested technology and ask an accessibility specialist to review the severity. Do not settle the issue merely by running another machine translation pass; a second fluent sentence can repeat the same conceptual error. Have an independent reviewer inspect the numerical, temporal or authority-related fields and the page layout. If publication requires an organizational commitment, it is the authorized owner rather than the translator who makes that commitment.

Case 11: A preference statement

In this fictional case the original reads “A participant said the older layout felt calmer.”. It will be easy to concentrate on grammar and overlook the decision hiding inside the sentence. One incorrect rendering is “The old layout had objectively higher usability.”. A quote expresses preference, not comparative task effectiveness. A reader might repeat the simplified statement in an email, spreadsheet or press release, where the missing qualifier would become even harder to recover.

For a reader-facing edition, prefer “One participant preferred the calmer feel of the older layout.”. It answers the question the original was capable of answering, without pretending to answer larger questions. A quote expresses preference, not comparative task effectiveness. A small qualifier often carries enormous practical value. Preserving that qualifier can matter more than mirroring word order, and it prevents the next editor from unknowingly widening a statement.

To review this case, Retain anonymity, quotation context and distinction between feeling and measured performance. A bilingual colleague should then read the target wording without seeing the approved English reformulation and explain what action or conclusion it licenses. Compare that explanation against the source and flag any added certainty, widened audience or missing condition. Record the final decision in the terminology and version log. A translation becomes ready for release only when both its language and its operational interpretation have been checked.

Case 12: A research recommendation

Consider an editor asked to localize the source wording “The team recommends shortening the recovery message.”. The proposed shorthand, “The present message failed the standard.”, is superficially convenient, particularly on a crowded page. A proposal for improvement is not automatically a finding of formal nonconformance. The central check is not whether every word sounds technical; it is whether a reader could use the translation to reach the same sound conclusion as someone reading the original with its proper context.

A safer target-language-ready explanation is “The research team recommends a shorter recovery message based on the recorded observations.”. This keeps the critical distinction visible while leaving room for idiomatic wording in a specific language. The translator should preserve the factual object, status and limits of the source. A proposal for improvement is not automatically a finding of formal nonconformance. If an equivalent everyday term creates a different commitment, use a short clarification rather than borrowing an inaccurate prestigious-sounding label.

A practical verification test is to Ask the researcher which observations support the recommendation. Ask a subject reviewer to state what evidence would make the sentence false, and confirm that the translation points to the same evidence. If the reviewer cannot identify an owner or a status, stop the publication route and request clarification. The corrective step should be visible in the release record, because future translators need to distinguish a resolved ambiguity from a guess that happened to survive one review.

Case 13: A partial task

Imagine a project file containing this source line: “Participants located the refund form but did not submit it.”. It looks compact, yet several hidden questions must be settled before a translator can write for an international reader. A tempting but misleading adaptation would be “The refund request was completed.”. Finding a page and performing the complete service transaction are different outcomes. The error is not merely stylistic. It changes what a reader can reasonably decide or rely on, especially when the phrase is lifted out of its original document and placed in a report summary or search result.

Write the working translation as “Participants found the refund form; submission was outside the tested task.”. Notice that it avoids the unsupported extra promise in the tempting version. The goal is not cautious language for its own sake; the goal is to preserve the source’s evidence and consequence. Finding a page and performing the complete service transaction are different outcomes. When the target audience is unfamiliar with the document type, a precise subordinate clause can be more helpful than a polished but overconfident headline.

For release, Recheck the scenario script and goal specification. Afterwards, test the target phrase with a representative reader: what happened, what remains conditional, who acts next, and what information is missing? If the answers differ from the original, rewrite and retest rather than concealing the problem in a footnote. Preserve the source excerpt and reviewer sign-off so a later revision can trace how the decision was reached.

Case 14: A linguistic comprehension problem

A multilingual team receives a document stating “The phrase ‘available balance’ was interpreted as withdrawable cash by some participants.”. Before drafting, the translator should identify the speaker, relevant evidence, time frame and action requested. The shortcut “Users misunderstood every financial field.” may sound fluent, but it crosses an important boundary. The observed ambiguity has a narrow referent, and the distinction may be legally consequential. A responsible translation should be understandable without implying powers, results or permissions that the source never established.

The controlled rendering should read “Some participants confused the available-balance label with immediately withdrawable funds.”, adapted grammatically for the chosen locale. This offers a clearer connection between the observed fact or rule and the decision it supports. The observed ambiguity has a narrow referent, and the distinction may be legally consequential. If readers need a definition, place it close to the decision point. Do not replace an unfamiliar technical distinction by a stronger claim simply because that stronger claim is easier to market.

The final quality gate is specific: Review definitions in the financial product and test candidate localized labels. Do not settle the issue merely by running another machine translation pass; a second fluent sentence can repeat the same conceptual error. Have an independent reviewer inspect the numerical, temporal or authority-related fields and the page layout. If publication requires an organizational commitment, it is the authorized owner rather than the translator who makes that commitment.

Case 15: A mixed-device study

In this fictional case the original reads “Tablet and desktop results were pooled into one completion rate.”. It will be easy to concentrate on grammar and overlook the decision hiding inside the sentence. One incorrect rendering is “Both devices performed equally well.”. An average may conceal a poor experience in one device group. A reader might repeat the simplified statement in an email, spreadsheet or press release, where the missing qualifier would become even harder to recover.

For a reader-facing edition, prefer “The combined completion rate covers tablet and desktop sessions and does not by itself establish device parity.”. It answers the question the original was capable of answering, without pretending to answer larger questions. An average may conceal a poor experience in one device group. A small qualifier often carries enormous practical value. Preserving that qualifier can matter more than mirroring word order, and it prevents the next editor from unknowingly widening a statement.

To review this case, Request subgroup counts before publishing device comparisons. A bilingual colleague should then read the target wording without seeing the approved English reformulation and explain what action or conclusion it licenses. Compare that explanation against the source and flag any added certainty, widened audience or missing condition. Record the final decision in the terminology and version log. A translation becomes ready for release only when both its language and its operational interpretation have been checked.

Case 16: An interrupted session

Consider an editor asked to localize the source wording “One participant stopped because of a network outage.”. The proposed shorthand, “The interface caused a task failure.”, is superficially convenient, particularly on a crowded page. A technical interruption and an interface-comprehension failure need separate classifications. The central check is not whether every word sounds technical; it is whether a reader could use the translation to reach the same sound conclusion as someone reading the original with its proper context.

A safer target-language-ready explanation is “One session ended because of a recorded network outage.”. This keeps the critical distinction visible while leaving room for idiomatic wording in a specific language. The translator should preserve the factual object, status and limits of the source. A technical interruption and an interface-comprehension failure need separate classifications. If an equivalent everyday term creates a different commitment, use a short clarification rather than borrowing an inaccurate prestigious-sounding label.

A practical verification test is to Check session notes and reporting rules for exclusion or inclusion. Ask a subject reviewer to state what evidence would make the sentence false, and confirm that the translation points to the same evidence. If the reviewer cannot identify an owner or a status, stop the publication route and request clarification. The corrective step should be visible in the release record, because future translators need to distinguish a resolved ambiguity from a guess that happened to survive one review.

Case 17: A small qualitative sample

Imagine a project file containing this source line: “Five interviews suggested that users wanted clearer labels.”. It looks compact, yet several hidden questions must be settled before a translator can write for an international reader. A tempting but misleading adaptation would be “Most users worldwide demand new labels.”. Qualitative insight is valuable without being a population estimate. The error is not merely stylistic. It changes what a reader can reasonably decide or rely on, especially when the phrase is lifted out of its original document and placed in a report summary or search result.

Write the working translation as “Five interviewees expressed a preference for clearer labels.”. Notice that it avoids the unsupported extra promise in the tempting version. The goal is not cautious language for its own sake; the goal is to preserve the source’s evidence and consequence. Qualitative insight is valuable without being a population estimate. When the target audience is unfamiliar with the document type, a precise subordinate clause can be more helpful than a polished but overconfident headline.

For release, Preserve sample size and method when translating the insight. Afterwards, test the target phrase with a representative reader: what happened, what remains conditional, who acts next, and what information is missing? If the answers differ from the original, rewrite and retest rather than concealing the problem in a footnote. Preserve the source excerpt and reviewer sign-off so a later revision can trace how the decision was reached.

Case 18: A task-success denominator

A multilingual team receives a document stating “Twelve successful attempts were recorded across fifteen attempts from ten people.”. Before drafting, the translator should identify the speaker, relevant evidence, time frame and action requested. The shortcut “Twelve of fifteen users succeeded.” may sound fluent, but it crosses an important boundary. Attempts and people are different units of analysis. A responsible translation should be understandable without implying powers, results or permissions that the source never established.

The controlled rendering should read “Twelve of fifteen task attempts succeeded; ten participants contributed those attempts.”, adapted grammatically for the chosen locale. This offers a clearer connection between the observed fact or rule and the decision it supports. Attempts and people are different units of analysis. If readers need a definition, place it close to the decision point. Do not replace an unfamiliar technical distinction by a stronger claim simply because that stronger claim is easier to market.

The final quality gate is specific: Check repeated attempts and person-level rates separately. Do not settle the issue merely by running another machine translation pass; a second fluent sentence can repeat the same conceptual error. Have an independent reviewer inspect the numerical, temporal or authority-related fields and the page layout. If publication requires an organizational commitment, it is the authorized owner rather than the translator who makes that commitment.

Case 19: A cultural response pattern

In this fictional case the original reads “Several respondents avoided the extreme ends of the agreement scale.”. It will be easy to concentrate on grammar and overlook the decision hiding inside the sentence. One incorrect rendering is “These users were undecided.”. Response style may reflect language, norms, or real ambivalence; interpretation must remain cautious. A reader might repeat the simplified statement in an email, spreadsheet or press release, where the missing qualifier would become even harder to recover.

For a reader-facing edition, prefer “Several respondents selected middle categories; the reason was not established by the survey alone.”. It answers the question the original was capable of answering, without pretending to answer larger questions. Response style may reflect language, norms, or real ambivalence; interpretation must remain cautious. A small qualifier often carries enormous practical value. Preserving that qualifier can matter more than mirroring word order, and it prevents the next editor from unknowingly widening a statement.

To review this case, Review translated response anchors and conduct follow-up research. A bilingual colleague should then read the target wording without seeing the approved English reformulation and explain what action or conclusion it licenses. Compare that explanation against the source and flag any added certainty, widened audience or missing condition. Record the final decision in the terminology and version log. A translation becomes ready for release only when both its language and its operational interpretation have been checked.

Case 20: An instruction layout

Consider an editor asked to localize the source wording “A localized warning wrapped onto three lines and obscured the continue button.”. The proposed shorthand, “The warning was readable in all languages.”, is superficially convenient, particularly on a crowded page. Text expansion can change the actual interface and therefore the task result. The central check is not whether every word sounds technical; it is whether a reader could use the translation to reach the same sound conclusion as someone reading the original with its proper context.

A safer target-language-ready explanation is “In the tested locale, the longer warning overlapped the next action.”. This keeps the critical distinction visible while leaving room for idiomatic wording in a specific language. The translator should preserve the factual object, status and limits of the source. Text expansion can change the actual interface and therefore the task result. If an equivalent everyday term creates a different commitment, use a short clarification rather than borrowing an inaccurate prestigious-sounding label.

A practical verification test is to Capture screenshots and repeat layout checks at realistic screen sizes. Ask a subject reviewer to state what evidence would make the sentence false, and confirm that the translation points to the same evidence. If the reviewer cannot identify an owner or a status, stop the publication route and request clarification. The corrective step should be visible in the release record, because future translators need to distinguish a resolved ambiguity from a guess that happened to survive one review.

Case 21: A post-release regression

Imagine a project file containing this source line: “A study of version 2 showed higher task completion than version 1.”. It looks compact, yet several hidden questions must be settled before a translator can write for an international reader. A tempting but misleading adaptation would be “Future versions are proven more usable.”. A past result does not guarantee the same effect in a future release. The error is not merely stylistic. It changes what a reader can reasonably decide or rely on, especially when the phrase is lifted out of its original document and placed in a report summary or search result.

Write the working translation as “Version 2 showed higher completion in the stated comparison study.”. Notice that it avoids the unsupported extra promise in the tempting version. The goal is not cautious language for its own sake; the goal is to preserve the source’s evidence and consequence. A past result does not guarantee the same effect in a future release. When the target audience is unfamiliar with the document type, a precise subordinate clause can be more helpful than a polished but overconfident headline.

For release, Preserve version numbers, study conditions and effect sizes. Afterwards, test the target phrase with a representative reader: what happened, what remains conditional, who acts next, and what information is missing? If the answers differ from the original, rewrite and retest rather than concealing the problem in a footnote. Preserve the source excerpt and reviewer sign-off so a later revision can trace how the decision was reached.

Case 22: A statistical interval

A multilingual team receives a document stating “The reported difference had a wide uncertainty interval.”. Before drafting, the translator should identify the speaker, relevant evidence, time frame and action requested. The shortcut “The improvement was conclusive.” may sound fluent, but it crosses an important boundary. Removing uncertainty turns preliminary evidence into an unjustified definitive claim. A responsible translation should be understandable without implying powers, results or permissions that the source never established.

The controlled rendering should read “The observed improvement was accompanied by substantial uncertainty.”, adapted grammatically for the chosen locale. This offers a clearer connection between the observed fact or rule and the decision it supports. Removing uncertainty turns preliminary evidence into an unjustified definitive claim. If readers need a definition, place it close to the decision point. Do not replace an unfamiliar technical distinction by a stronger claim simply because that stronger claim is easier to market.

The final quality gate is specific: Check the original statistical method and never infer significance from a chart alone. Do not settle the issue merely by running another machine translation pass; a second fluent sentence can repeat the same conceptual error. Have an independent reviewer inspect the numerical, temporal or authority-related fields and the page layout. If publication requires an organizational commitment, it is the authorized owner rather than the translator who makes that commitment.

Case 23: A consent boundary

In this fictional case the original reads “Participants agreed to internal research use of their anonymized comments.”. It will be easy to concentrate on grammar and overlook the decision hiding inside the sentence. One incorrect rendering is “Their comments may be published with names globally.”. Translation cannot expand consent or reveal identities. A reader might repeat the simplified statement in an email, spreadsheet or press release, where the missing qualifier would become even harder to recover.

For a reader-facing edition, prefer “Participants consented to the specified internal research use of anonymized comments.”. It answers the question the original was capable of answering, without pretending to answer larger questions. Translation cannot expand consent or reveal identities. A small qualifier often carries enormous practical value. Preserving that qualifier can matter more than mirroring word order, and it prevents the next editor from unknowingly widening a statement.

To review this case, Check the consent form and redact personal details in every language. A bilingual colleague should then read the target wording without seeing the approved English reformulation and explain what action or conclusion it licenses. Compare that explanation against the source and flag any added certainty, widened audience or missing condition. Record the final decision in the terminology and version log. A translation becomes ready for release only when both its language and its operational interpretation have been checked.

Case 24: An improvement backlog

Consider an editor asked to localize the source wording “The observed login confusion was assigned for future investigation.”. The proposed shorthand, “The login issue was fixed.”, is superficially convenient, particularly on a crowded page. A ticket status is not a production result. The central check is not whether every word sounds technical; it is whether a reader could use the translation to reach the same sound conclusion as someone reading the original with its proper context.

A safer target-language-ready explanation is “The login confusion was logged for investigation; no completed fix is asserted.”. This keeps the critical distinction visible while leaving room for idiomatic wording in a specific language. The translator should preserve the factual object, status and limits of the source. A ticket status is not a production result. If an equivalent everyday term creates a different commitment, use a short clarification rather than borrowing an inaccurate prestigious-sounding label.

A practical verification test is to Check owner, issue state and deployed version before issuing a release note. Ask a subject reviewer to state what evidence would make the sentence false, and confirm that the translation points to the same evidence. If the reviewer cannot identify an owner or a status, stop the publication route and request clarification. The corrective step should be visible in the release record, because future translators need to distinguish a resolved ambiguity from a guess that happened to survive one review.

4. Controlled terminology register

A multilingual terminology register is more useful when each entry identifies what a term includes, what it excludes and which documents control it. The following definitions are educational working distinctions rather than verbatim clauses from the standard. Adapt labels to the target-language conventions while keeping their underlying boundaries stable. Where a word is also used in law, procurement or a regulated industry, ask the appropriate local specialist to review the accepted expression.

Usability

Outcome of use for specified users, goals and context, not a universal quality label. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Effectiveness

Accuracy and completeness with which users reach specified goals. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Efficiency

Resources expended relative to the result achieved. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Satisfaction

Users’ perceptions and responses to using the system or service. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Context of use

The users, tasks, equipment, resources and environments relevant to the interaction. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Task success

A result only after the study defines successful completion. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Attempt

One trial of a task, not necessarily one unique person. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Participant

A study individual whose characteristics and consent affect interpretation. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Moderator assistance

Intervention that may invalidate a claim of independent completion. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Abandonment

An incomplete task that should not be mistaken for fast completion. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Response anchor

The words defining points on a questionnaire scale. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Cognitive interview

A method for checking whether respondents understand questions as intended. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Observed behaviour

What researchers witnessed or recorded rather than inferred motivation. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Finding

An evidence-based result distinct from the team’s recommendation. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Usability recommendation

A proposed improvement that should retain its provisional status. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

Localization regression

A usability problem introduced or revived by a language or layout change. In a translation register, attach an example sentence, an approved term owner and a link to the governing source; mark terms provisional when the organization’s context is not yet established.

5. Bilingual review and controlled release

1. Create a source-of-truth packet

Gather the approved document, relevant supporting evidence, responsible owner, document type, audience, locale list and applicable rule or programme. Mark superseded documents clearly. For usability studies and user-research findings, keep the source’s evidence period, status and key identifiers alongside the wording to be translated. Do not ask a translator to repair factual contradictions alone. A reviewer should be able to reconstruct the intended decision from the packet without searching through unrelated email chains.

2. Separate language risks from subject risks

The bilingual reviewer checks semantic equivalence, grammar, readability, negatives, numerical formatting and consistency. The subject specialist checks whether assertions, actions, thresholds, statuses and qualifications accurately reflect the source domain. These tasks overlap but are not identical. A beautiful translation may still contain an incorrect technical promise, and a technically faithful string may still be unusable for real readers. Each reviewer should sign the part they can genuinely assess.

3. Check the document in context

Review headings, tables, charts, labels, screenshots, captions and links in final layout. Reflow can separate a qualification from the claim it limits. Text expansion may hide a button or push a warning away from the relevant instruction. Inspect not only sentences but the sequence of information encountered by a person trying to act. If the audience will use assistive technology, test the accessible text order and any alternatives for visual information.

4. Perform a decision-equivalence test

Give the target version to a representative reader and ask four questions: what is established; what remains uncertain; what must happen next; and who is responsible? Compare the answers with the approved source. Where this test fails, correct the root cause rather than merely choosing a more formal synonym. Maintain a change log that records the misleading inference, corrected wording and reason. This method often reveals a material error that a grammar-only proofread misses.

5. Authorize and version the release

Obtain the required technical, legal, accessibility or policy approval according to the subject and intended market. Keep the source and translated edition numbers together. Publish any limitations at the same visibility level as the headline claim, not buried in an inaccessible annex. Set a process for correcting translations when the underlying evidence changes. A release is an operational event: its date, audience and authoritative owner should be documented.

6. Frequently asked questions

Does ISO 9241-11 prescribe one usability score?

No. It provides a conceptual framework for understanding usability, not a single universal pass mark. Explain the particular study’s metric, participants and tasks. For this particular document, record any exceptions rather than extending a general answer beyond the evidence. If a translated statement creates a new legal, safety, research or employment consequence, require explicit approval from the subject owner before distribution.

Is a higher satisfaction score proof of greater effectiveness?

No. People may prefer an interface while making more errors or taking longer. Translate each evidence stream separately. For this particular document, record any exceptions rather than extending a general answer beyond the evidence. If a translated statement creates a new legal, safety, research or employment consequence, require explicit approval from the subject owner before distribution.

Can a translated survey reuse the same numerical scale?

The numbers may remain the same, but anchors and culturally mediated interpretations still need testing. Confirm conceptual equivalence before pooling responses. For this particular document, record any exceptions rather than extending a general answer beyond the evidence. If a translated statement creates a new legal, safety, research or employment consequence, require explicit approval from the subject owner before distribution.

What is the difference between task success and ease?

Task success addresses whether the goal was reached. Ease may concern efficiency, effort or satisfaction. A successful task can still be frustrating. For this particular document, record any exceptions rather than extending a general answer beyond the evidence. If a translated statement creates a new legal, safety, research or employment consequence, require explicit approval from the subject owner before distribution.

Should a failed session be removed from results?

Follow the study’s pre-established exclusion rules and disclose exceptions. Never discard a negative result merely to improve a headline. For this particular document, record any exceptions rather than extending a general answer beyond the evidence. If a translated statement creates a new legal, safety, research or employment consequence, require explicit approval from the subject owner before distribution.

How should research quotes be translated?

Preserve meaning, register and uncertainty, avoid creating a stronger claim, and respect consent and anonymity. Do not attribute invented wording to participants. For this particular document, record any exceptions rather than extending a general answer beyond the evidence. If a translated statement creates a new legal, safety, research or employment consequence, require explicit approval from the subject owner before distribution.

Do accessibility studies fit this topic?

Yes. Assistive technology, sensory and cognitive requirements may materially change context of use; a study should state whom it actually represented. For this particular document, record any exceptions rather than extending a general answer beyond the evidence. If a translated statement creates a new legal, safety, research or employment consequence, require explicit approval from the subject owner before distribution.

Is this a general guide to all UX design?

No. It addresses translation and accurate international communication of usability evidence, while the protected translation master remains the broader curriculum. For this particular document, record any exceptions rather than extending a general answer beyond the evidence. If a translated statement creates a new legal, safety, research or employment consequence, require explicit approval from the subject owner before distribution.

7. Four-week learning and application plan

Week one: reconstruct meaning

Choose eight short authentic examples of usability studies and user-research findings, with permission to use them. For each example, identify the source author, intended audience, key proposition, evidence, uncertainty and reader action. Write a plain-language source explanation before drafting another language. Then compare it against the full document and ask an expert to correct any mistaken assumptions. Start a living terminology sheet with definitions and rejected alternatives. The learning aim is to recognize the decision structure rather than memorize phrases.

Week two: draft a controlled bilingual packet

Translate the selected texts into one target locale. Annotate the tense, responsibility, quantities, negative clauses, status and exceptions. Include two versions of each disputed phrase: an attractive but misleading one and a reader-safe alternative. Explain why the latter better preserves the source. Do not treat a machine-generated draft as approved evidence; use it as one hypothesis to test against the original. Discuss choices with an informed native reader and record where local regulatory or cultural expertise is still required.

Week three: test understanding with readers

Present the translations in realistic layouts and let representative readers perform the relevant interpretation task. Ask them to restate what is established, conditional, prohibited, planned or measured. Compare their answers with what the original document actually permits them to infer. Count failures by severity and type rather than by grammatical mistakes alone. Revise phrases that produce wrong real-world actions. Where a source is itself ambiguous, open a clarification request with the document owner instead of fabricating an answer.

Week four: release and sustain quality

Carry out independent bilingual review, specialist sign-off and version reconciliation. Confirm external links, numerals, units, names, access controls, status markers and any source updates. Publish only the approved target edition, together with a practical correction contact and documented scope. Review whether the learning process helped the team catch material errors earlier and whether repeated problems justify a new glossary entry or checklist rule. Preserve this record for future translators, while keeping personal and confidential material appropriately protected.

Sources, scope and connected learning

The scope and edition of ISO 9241-11:2018 were checked against the official ISO catalogue record on 5 November 2026. This article uses original fictional cases and offers educational translation procedures, not copyrighted full-text clauses, a compliance assessment or authorization to claim conformity. Real documents may be governed by additional standards, official translations, contractual rules and local laws. Consult the authoritative document and appropriate specialists before relying on a translated conclusion.

This is a specialist child lesson and not a new translation hub. Study the wider conceptual system through The Master Art of Translation, build the meanings and contextual word choices through the protected Vocabulary Learning Hub, and strengthen clause-level interpretation through How English Works. These resources support, rather than compete with, the translation architecture: the master owns the overview, vocabulary owns lexical development, English works owns sentence meaning, and this article applies those foundations to one bounded professional problem.