grounding-translation-in-reader-cognition

name	grounding-translation-in-reader-cognition
description	Shape the target text around how readers perceive, remember, attend, learn and solve problems: minimise processing effort and cognitive load so the text is easy to read, understand and act on.
kind	skill
status	ready
provenance	{"principles":["P003","P009","P010","P017","P023","P025","P030","P031","P037","P043","P045","P057","P058","P060","P062","P063","P082","P111","P112","P118","P123","P137"],"claims":["C00001","C00033","C00089","C00118","C00228","C00275","C00286","C00296","C00306","C00324","C00356","C00595"],"evidence":["E00001","E00026","E00078","E00105","E00210","E00257","E00268","E00278"],"source_anchors":[]}

Grounding Translation in Reader Cognition

Purpose

This skill guides the translator to shape the target text around how readers perceive, remember, attend, learn and solve problems: minimise processing effort and cognitive load so the text is easy to read, understand and act on. It advises on the decision; it does not produce the final translation, override the client's brief, or sign off safety-critical or legally-mandated content — those are handed back to the translator and the commissioner.

When to use

• The document includes layout, graphics, publication tooling, or multiple contributors.
• any sci-tech translation delivered to end users.
• Readers must hold, retrieve, or apply procedural information while using the guide.
• Users must learn unfamiliar procedures or concepts.
• Users must alternate between reading instructions and performing procedures.
• Technical or instructional documents must help readers perform real tasks.
• Readers need to retrieve and use information quickly.
• Users consult instructions while simultaneously operating software or equipment.
• Novices face unfamiliar tasks or may transfer misleading prior assumptions.

Procedure

1. Treat scientific and technical translation as a communicative service for people, whose delivered target text should function as an authentic target-language document, because users care most about accessing its information effectively. (P003)
2. Reduce working-memory burden through chunking, short retention gaps, familiar groupings, relevant visuals, and recognition-based cues. (P009)
3. Prime and teach new material by linking it to related concepts, existing schemes, examples, habits, and visible reinforcement. (P010)
4. Use one-idea sentences and uniform phrasing to reduce memory load, build habits, improve recognition, and free attention for the task. (P017)
5. Treat technical translation as target-user usability work, not as source-text transfer alone. (P023)
6. Minimize target-reader processing effort by making context, intended interpretation, and given-new progression easy to follow. (P025)
7. Minimize attention switching because reading the guide and doing the task draw on the same limited cognitive capacity. (P030)
8. Help users frame problems correctly, surface misconceptions, and provide enough declarative background before expecting fluent action. (P031)
9. Use repetition, sentence flow, and parallel structure only when they reinforce action, memory, clarity, or habit formation. (P037)
10. Ground technical translation in target-audience communicative service, Skopos purpose, and reader cognitive demands. (P043)
11. Make target-relevant information easy to find, select, assimilate, and proportionally redundant. (P045)
12. Use repetition and practice to support procedural automaticity without creating unnecessary dependence. (P057)
13. Shape translated documentation around reader cognition, including perception, memory, attention, learning, and problem solving. (P058)
14. Provide enough information for the current user purpose, avoiding both overload and under-specification. (P060)
15. Serve multiple proficiency levels with predictable novice support and efficient reference for experienced users. (P062)
16. Prevent likely errors, make recovery easy, and use consistent familiar terminology and interaction patterns. (P063)
17. Concentrate strategy decisions on target audience needs and native-quality technical communication. (P082)
18. Make tutorials gentle, supportive, and never confusing, too-advanced, or wrong — because readers tend to blame themselves for problems following instructions even when the text is substandard — keeping information density low and always including the hazard warnings EU law requires; for transfer users, avoid explaining every concept yet do not over-simplify to the point of patronizing them. (P111)
19. Treat user guides as structured instructional documents in simple language supported by graphics whose usability rests on broadly universal human cognition but also carries culture-specific features and rarely targets a single culture, so translating them is not always straightforward. (P112)
20. Judge efficiency from the user total task, and keep guide information clear, digestible, and concise. (P118)
21. Keep language clear, simple, and to the point as a core value of technical communication: use simple declarative sentences rather than complex ones and give instructions in chronological or logical cause-and-effect order, especially for readers who are hurried, stressed, or non-native. (P123)
22. Optimize for usability — how well readers can read, understand, and perform or remember the task, and how unstressed they are afterward — by giving the right information in the right proportions at the right time and format, using these strategies: consistent terminology without polysemy, clear simple language, chronological instructions, direct and active language, no unnecessary information, Iconic Linkage, and a minimum of tenses. (P137)
23. Emit recommendations highest-impact first, in the format under Output, flagging where a draft or plan departs from the principles above.

Inputs

• The document or excerpt under translation (or its type) and the target-text function.
• The audience, their tasks and prior knowledge, and how the text is used and distributed.
• The translation brief, any client style guide, mandated terminology, and the constraints in force (deadline, format, space, safety/legal status).

Output

Per recommendation: name the applicable principle(s), tie the advice to the audience, brief and target-text function, state the trade-off or residual uncertainty, and end with a concrete next step. Order recommendations highest-impact first. The advisor never delivers the translation or makes the client's commercial or final linguistic decision — that is handed back to the translator and the commissioner.

References

See ../../references/technical-translation-principles-index.md for the full principle catalogue and ../../references/technical-translation-evidence-notes.md for grounding notes. For adjacent concerns, see the sibling skills: analyzing-audience-brief-and-skopos, selecting-translation-strategy-and-procedures, handling-terminology-units-and-nomenclature, applying-iconic-linkage-and-consistency, matching-document-type-and-genre, designing-document-structure-and-presentation, planning-usability-evaluations, running-and-analyzing-usability-studies, assuring-quality-safety-and-practice.

Provenance

Derived from P003, P009, P010, P017, P023, P025, P030, P031, P037, P043, P045, P057, P058, P060, P062, P063, P082, P111, P112, P118, P123, P137, grounded in Jody Byrne's Technical Translation: Usability Strategies for Translating Technical Documentation (2006) and Scientific and Technical Translation Explained (2012) (distillation-only). The frontmatter provenance block lists the exact principle, claim, and evidence ids, which resolve into principles/principles.yaml, analysis/claims.jsonl, and evidence/evidence-records.yaml.