← Back to portfolio
TD
TECHWRITING_DECODEDInsights · Examples · Growth

AI in Technical Writing:
A Simple Roadmap

Build the craft first. Add AI where it actually helps. One clear path from beginner to AI-augmented writer — no hype, no shortcuts around the fundamentals.

The one idea to remember: You're the author. AI is the assistant.

New to writing?

Learn the craft first. Then let AI speed up your learning — don't skip the foundations.

Already writing?

Use AI to remove friction, not thinking. Automate the busywork, keep the judgment.

7

The 7-step roadmap

follow in order
1

See what great docs look like

Read the best documentation closely. Notice the structure, clarity, tone, and depth before you write your own.

→ You'll build an eye for quality Learn from: Stripe · GitHub · Google Cloud · Microsoft · AWS · Atlassian
2

Learn the fundamentals

Who is the reader and what do they need? When is it a guide vs. a reference? This is the craft under everything.

→ You'll know what makes docs work audience analysis · structure · clarity · content reuse · style & tone
3

Get comfortable with the tools

You don't need all of them — just enough to build and ship docs the way modern teams do.

→ You'll know how docs get built Markdown · Git & GitHub · docs-as-code · Confluence · MadCap Flare · DITA/Oxygen
4

Write a lot

Pick a product you already use and document it end to end: guides, tutorials, FAQs, API pages, release notes.

→ You'll build real experience & a portfolio
5

Learn the workflow

Follow a doc through its whole life. This lifecycle is also exactly where AI plugs in (next section).

PlanWriteReviewPublishMaintain
→ You'll think like a writer, end to end
6

Spot the busywork

Ask yourself three questions: What do I repeat every day? What eats most of my time? What needs no real creativity?

→ You'll find what's worth automating
7

Add AI where it counts

Bring AI into those spots as a force multiplier — not everywhere. Start small, measure the impact, keep what works.

→ You'll amplify your skills, not outsource them

Where AI helps — and what to actually ask it

Plan & researchBefore you write
Summarize this 30-page spec into the 8 things a new user must know.
DraftBeat the blank page
Turn these rough notes into a first-draft how-to in a clear, neutral voice.
ReviewA second pair of eyes
Find gaps, ambiguity, and missing prerequisites in this procedure.
PublishThe last mile
Draft release notes from these merged PRs, grouped by feature and fix.
MaintainKeep it true
Compare this guide to the new API spec and list what's now out of date.

Smart use vs. lazy use

Smart — you stay the author

  • Ask it to draft, then verify every fact yourself
  • Use it to critique and stress-test your draft
  • Let it break blank-page freeze and rephrase
  • Hand it repetitive formatting and cleanup

Lazy — you lose the plot

  • Ship AI text you never read
  • Trust its facts, versions, and steps blindly
  • Let it invent how the product behaves
  • Skip learning the craft underneath
!What AI should never do alonealways needs a human
Publish unreviewed. Nothing ships without your eyes on it.
Judge accuracy, compliance, or safety. That's on you.
Understand your reader or your business context.
Replace expertise and critical thinking.

Principles to keep

🎯

Solve the reader's problem — not just finish the doc.

👥

Write for your audience — not for yourself.

💎

Clarity beats cleverness. Every time.

🛡️

Accuracy and trust are non-negotiable.

Which stage are you at today?

Pick the number that best describes where you are — and use the roadmap above to move to the next one.

1
Learning the basics
2
Writing docs regularly
3
Exploring AI for docs
4
AI in my daily flow
Build the craft first. Add AI where it actually helps.