# Writing Style

## Voice

Write like a practitioner who has seen the work break in real life.

The voice is:

- Direct, oral, and judgment-led.
- Business-facing rather than academic.
- Structured but not stiff.
- Willing to say "这个问题问早了" or "这不是重点".
- Grounded in process, organization, product, AI, skill, or delivery scenes.

Avoid:

- "赋能未来，智领新程" style slogans.
- Generic AI excitement.
- Long theoretical definitions before the business problem is clear.
- Passive academic scaffolding such as "本文将从多个维度展开".

## Title Patterns

Use titles that contain a claim:

- `AI流程改造，不是把人换成模型`
- `别再问“AI该怎么学”了`
- `企业做 AI，必须先有一支尖刀队`
- `企业最宽的护城河，是把超级个体编组成超级组织`
- `AI时代，别再用“好员工”的旧尺子量人`
- `真正的问题不是“会不会被替代”`
- `第一步不是找工具，是沿着流还原现场`
- `上线不是终点，评测才是发动机`

## Opening Moves

Pick one:

- Personal observation: "这两天，我一直被一个问题卡住。"
- Work-scene question: "很多 AI 项目，第一张图就画错了。"
- Contrarian finding: "别被使用率骗了。"
- Boundary statement: "这篇文章拆的不是政治，而是流程。"
- Conversation trigger: "我经常被问同一个问题。"

The opening should reach the core problem within 6-10 short paragraphs.

## Sentence Patterns

Use these patterns naturally:

- `不是 X，而是 Y。`
- `这句话听起来有点抽象，放到现实里其实很具体。`
- `问题表面看是 A，底层其实是 B。`
- `第一步不是 A。第一步是 B。`
- `这不是反对 A，而是承认两套机制不同。`
- `如果只做到 A，那还不叫真正会 B。`
- `真正要迁移的，不是工具，而是团队能力。`

## Section Rhythm

For each chapter:

1. State the claim.
2. Explain why common practice fails.
3. Name the underlying structure.
4. Give a concrete example.
5. Turn the idea into a visual.
6. End with a strong-line takeaway.

## Strong Lines

Every 2-4 slides should contain a memorable line:

- `不要把烂流程自动化。`
- `AI 放大的不是岗位，而是一个人的闭环能力。`
- `传统 IT 守住确定性，尖刀队突破不确定性。`
- `真正的分水岭不是会不会问 AI，而是会不会验 AI。`
- `没有总控，协同越多，风险越大。`

Strong lines are good candidates for gold quote slides.

## Ending

End with one of:

- Three-sentence summary.
- 72-hour action plan.
- Evaluation checklist.
- Resource handoff.
- "能力迁移" conclusion: what the team or organization must learn next.

