Series ID: EDKS-BASIC-ZH-0095 · Lesson No.095 · C2-Direction Multi-Audience Writing

Writing Executive, Public and Technical Versions | 行政、公众与技术版本写作

Expert writing preserves the same truth while changing the packaging.

An executive brief, public explanation and technical note should not contain three different realities. They should contain the same core evidence, adapted for purpose, prior knowledge, detail and decision need.

高级写作最强的测试之一，是把同一个证据系统写成三个版本，同时保持事实、范围、不确定性和来源归属不变。

Chinese Edition Hub · 中文版入口 · ← Lesson No.094 · Expert Listening and Multi-Layer Source Tracking

The three-version map | 三版本地图

core proposition
audience
purpose
decision need
background knowledge
evidence density
terminology
uncertainty
source ownership
actionability

1. Core proposition first | 先锁定核心命题

Before adapting, write one sentence that all versions must preserve.

The pilot reduced average response time, but the sample was small and no clear reduction in error rate was observed.

2. Core evidence ledger | 核心证据账本

Item	Must stay stable?
response time fell	yes
sample small	yes
error rate unclear	yes
recommended action	may vary by audience purpose

3. Executive version | 行政版

Executive readers often need:

decision
evidence
risk
options
next action

4. Executive lead | 行政版开头

Recommendation: continue the pilot rather than scale immediately.

Then give the evidence and main risk.

5. Executive compression | 行政压缩

Cut background that does not affect the decision.

6. Executive uncertainty | 行政版也不能删不确定性

Weak:

The pilot worked.

Better:

Response time improved, but the small sample and unchanged error rate do not yet support full rollout.

7. Executive action language | 行政行动语言

recommend
defer
continue testing
monitor
escalate
review

8. Executive risk language | 风险语言

main risk
key uncertainty
decision dependency
minimum evidence needed

9. Public version | 公众版

Public readers often need:

plain language
context
why it matters
what is known
what is not yet known

10. Public lead | 公众版开头

An early test found faster response times, but it is too soon to know whether the system also reduces errors.

11. Public simplification | 公众简化

Technical:

External validity remains uncertain because the sample is narrow.

Public:

The test involved a small group, so the same result may not appear everywhere.

12. Simplify terms, not evidence | 简化术语，不简化事实

Remove jargon. Keep limitations.

13. Public examples | 公众例子

Use concrete examples to explain abstract method concepts.

14. Public analogy | 公众类比

Use only if it clarifies, and state the limit when necessary.

15. Public trust language | 公众信任

Useful:

what we know
what remains uncertain
what happens next

16. Technical version | 技术版

Technical readers may need:

method
sample
measurement
effect size
uncertainty
limitations
analysis choices

17. Technical lead | 技术版开头

In the pilot sample, mean response time declined, while the estimated change in error rate remained uncertain.

18. Technical specificity | 技术精度

State:

what was measured
how
for whom
for how long

19. Technical uncertainty | 技术不确定性

Use appropriate measures and cautious interpretation.

20. Technical source ownership | 技术版来源归属

Mark whether statements come from:

data
participants
authors
your interpretation

21. Same fact, three versions | 同事实三版本

Core:

The study did not establish a causal relationship.

Executive: The evidence is not strong enough to attribute the change to the programme alone.
Public: The two things happened together, but the study cannot show that one caused the other.
Technical: The observational design does not identify a causal effect.

22. Same uncertainty, three versions | 同不确定性三版本

Do not make the public version more certain just because it is simpler.

23. Same source distance | 同来源距离

If the technical paper says suggests, the executive version should not say proves.

24. Same scope | 同范围

adult participants in this trial must not silently become people in general.

25. Executive omission rules | 行政版可以省什么

You may omit:

low-value procedural detail
long literature history
non-decision-relevant technical explanation

26. Executive non-omission rules | 行政版不能省什么

Do not omit:

material risk
key uncertainty
critical dependency
major limitation

27. Public omission rules | 公众版可以省什么

Remove specialist terminology if the concept can be explained plainly.

28. Public non-omission rules | 公众版不能省什么

Do not remove uncertainty simply because it is harder to explain.

29. Technical omission rules | 技术版也要编辑

Technical detail should still serve the question. More detail is not automatically better.

30. Decision relevance | 决策相关性

Executive version asks:

What should we do?

31. Public relevance | 公众相关性

Public version asks:

What does this mean for me/us?

32. Technical relevance | 技术相关性

Technical version asks:

How strong is the evidence, and how was it produced?

33. Length changes | 长度变化

Example:

executive: 150 words
public: 300 words
technical: 700 words

Actual length depends on task.

34. Order changes | 顺序变化

Executive: conclusion first.
Public: context → finding → meaning.
Technical: question → method → result → interpretation.

35. Headings change | 标题也要适应

Executive: Recommendation / Risk / Next Step
Public: What We Found / What It Means / What We Still Don’t Know
Technical: Method / Results / Limitations / Interpretation

36. Data presentation | 数据呈现

Executive: key number.
Public: meaningful comparison.
Technical: full measure with uncertainty where appropriate.

37. Relative vs absolute change | 相对 vs 绝对变化

Public and executive versions should avoid dramatic percentage framing without a useful baseline.

38. Visual language | 图表语言

If summarising a graph, preserve axis scale, denominator and uncertainty.

39. Recommendation strength | 建议强度

Match recommendation to evidence:

proceed
pilot
monitor
defer
reject

40. Recommendation conditions | 条件式建议

Proceed only if error rate remains below X.

41. Public reassurance vs honesty | 公众安抚 vs 诚实

Do not use reassuring tone to hide uncertainty.

42. Technical caution vs readability | 技术谨慎 vs 可读性

Do not bury every sentence under hedges. Use precise, necessary qualification.

43. Executive certainty vs decisiveness | 决策果断不等于假装确定

You can make a decision under uncertainty while stating the uncertainty honestly.

44. Style consistency | 风格一致

Each version should sound natural in its own register.

45. Cross-version audit | 跨版本审计

Check	Executive	Public	Technical
core claim	same	same	same
uncertainty	same	same	same
detail	low	medium	high
terminology	decision-focused	plain	specialist

46. Version-drift detection | 版本漂移检测

Compare all three versions for:

certainty drift
scope drift
causality drift
source drift
recommendation drift

47. Mandarin transfer: “行政版”不是官样文章 | 简洁优先

Executive English should usually be clearer and shorter, not more bureaucratic.

48. Mandarin transfer: 公众版不是“儿童版” | 清楚但不幼稚

Plain English respects the reader by reducing unnecessary decoding.

49. Mandarin transfer: 技术版不等于长句堆叠 | 精度优先

Technical writing can still be direct.

50. Practice source | 练习材料

A six-week pilot with 84 participants reduced average response time by 12%. Error rate changed by less than one percentage point. Participation was voluntary, and no comparison group was used.

51. Executive task | 行政任务

Write 120 words with:

recommendation
main evidence
main risk
next action

52. Public task | 公众任务

Write 250 words explaining what was found and what cannot yet be concluded.

53. Technical task | 技术任务

Write 500 words covering sample, design, measurement, result, limitation and interpretation.

54. Error clinic | 常见问题

Problem	Repair
Executive version removes caveat.	Keep material uncertainty.
Public version overexplains jargon.	Translate concept plainly.
Technical version becomes unreadable.	Use direct structure.
Three versions make different claims.	Return to core ledger.
Recommendation changes silently.	State audience-specific purpose.

55. First weak link diagnosis | 第一个卡点诊断

meaning changes → proposition stability.
public version loses limits → simplification control.
executive version becomes vague → decision relevance.
technical version becomes dense → structure/register.
recommendation too strong → evidence calibration.

56. Seven-day training cycle | 七天训练

Day 1	core evidence ledger	核心证据
Day 2	executive version	行政版
Day 3	public version	公众版
Day 4	technical version	技术版
Day 5	cross-version audit	跨版本审计
Day 6	recommendation calibration	建议强度
Day 7	one-source three-version challenge	综合

57. Self-test | 自测

Write executive, public and technical versions of one evidence set while preserving core proposition, uncertainty, source ownership, scope and causal strength.

58. For parents and teachers | 给家长和老师

Compare the three versions line by line for meaning drift.

Reward accurate simplification and purposeful compression.

For Mandarin speakers, discourage bureaucratic English as a substitute for professional clarity.

59. Final real-world challenge | 最终真实任务

Select one complex evidence set.
Create a core proposition ledger.
Write a 150-word executive brief.
Write a 300-word public explanation.
Write a 700-word technical note.
Preserve uncertainty.
Preserve source ownership.
Preserve causal strength.
Run a cross-version audit.
Explain every major adaptation by audience purpose.

Next: Lesson No.096 | 下一课

The next lesson closes this sequence with a C2-direction capstone and a lifelong maintenance system: how to keep high-level English alive through transfer, repair, verification, reading breadth, speaking pressure and deliberate editing.

Lesson No.096 · C2-Direction Capstone and Lifelong Language Maintenance · C2 方向顶点与终身语言维护

Reference floor: C2-direction multi-audience writing; adaptation changes detail and register, never the truth conditions of the evidence.

Small Group Tutorials

How to Learn Basic English (Chinese Edition) | Lesson No.095 | Writing Executive, Public and Technical Versions | 行政、公众与技术版本写作