W1
The reader-first frame
How professional writers think about the reader before writing a word — and the doc anti-patterns everyone falls into.
Cohort 14 starts Feb 10 · 22 seats left
Master technical writing in 8 weeks.
A cohort-based course for engineers and PMs who want to write docs people actually read. Live sessions, weekly assignments, 1:1 feedback from working documentation leads.
Cohort 14
Enrolment closes in
Twenty-two of forty seats left. The teaching team is sized to the cohort, so when the seats go the doors close until June.
2,400+ alumni · 13 cohorts
4.9/5 average rating
90-day guarantee
Stipend-eligible
01OutcomesThirteen cohorts in
- 2,400++
- Alumni across 13 cohorts
- 4.9/5
- Average cohort rating · 412 reviews
- 92%%
- Finish every assignment
- 8wk
- From enrolment to portfolio piece
02CurriculumAll sessions recorded
The eight weeks
Two live sessions a week (recorded), one assignment with real feedback, and a portfolio piece from your actual work.
W2
Structure + scannability
Drafting a doc people can read in 30 seconds and come back to in six months.
W3
Tutorial, reference, explanation
The framework for knowing which doc you're writing — and why blending them is where most docs go wrong.
W4
Code samples + diagrams
What makes a sample useful, when a diagram earns its place, and tools that don't fight you.
W5
Voice + register
Friendly without chatty, authoritative without cold. Building a docs voice your whole team can write in.
W6
Editing yourself
The cuts that take a draft from "fine" to "publishable." Pair-editing practice with your cohort.
W7
Maintenance + ownership
Docs systems that don't rot: reviews, ownership models, deprecation. The week managers thank us for.
W8
Portfolio review
You present a rewritten doc from your actual job and get whole-class feedback. This is the piece you ship at work.
Taught by someone who ships docs, not courses.
I've spent ten years leading documentation at developer-platform companies — the kind whose docs you end up on at 1am when something is broken. This course is the playbook I wish someone had handed me in year one.
- Ten years leading docs teams at developer platforms
- Regular speaker at documentation and DevRel conferences
- Still writing docs weekly — the material stays current
03Built for working schedules
How the cohort runs
Two live sessions a week
Tuesday and Thursday, one hour each, always recorded and posted within 24 hours. Most students attend about two-thirds live.
One real assignment
Each week you rewrite something from your actual job — no toy exercises. Expect three to four focused hours.
Feedback that names the fix
Written feedback on every assignment from the teaching team, plus a 1:1 portfolio review in the final fortnight.
The alumni room
Lifetime access to the alumni Slack — where docs leads swap reviews, job leads, and style-guide wars, indefinitely.
Enrolment
Pick your seat
Cohort 14 · February 10 – April 4 · 22 seats left. Every tier carries the 90-day guarantee.
The guarantee
If it does not change how you write, you do not pay
Take the course, do the assignments, and give it ninety days at your actual job. If your writing has not measurably improved — fewer review comments, faster drafts, docs your team reuses — email us and we refund the fee in full.
- Applies to every tier, including team seats
- No form, no exit interview — one email is enough
- Keep the recordings and the alumni Slack either way
- Refunds processed within five working days
The one condition is the work: the guarantee assumes the eight assignments were submitted. It exists so that price is never the reason someone talks themselves out of getting better at this.
Alumni say
Half the review comments, twice the confidence.
5 out of 5 stars
“Changed how I think about every doc I write — my PRs get half the review comments now. I came in not knowing what good looked like and left with a portfolio piece my company actually published.”
L
Lana R.
Product manager · cohort 11
04Fit + logistics
Common questions
Do I need to be technical?+
Yes — the examples are technical (APIs, infra, dev tools). PMs at technical companies do great; pure-marketing writers usually find it too advanced.
What if I miss a live session?+
Everything is recorded and posted within 24 hours, and the cohort Slack picks up the discussion. Most students attend 50–70% live.
How does the guarantee work?+
Finish the course, do the assignments, and if it didn't move the needle on your writing within 90 days — full refund, no argument.
Can my company pay?+
Every cohort is 30–40% company-funded. We provide a stipend-justification template and proper invoicing.
Self-paced vs cohort — honestly?+
The cohort. Deadlines and feedback are the product; the videos alone are just very good videos. Self-paced exists for the genuinely time-zoned-out.
How much time per week?+
Five to six hours all-in: two live hours, three to four on the assignment. Week 8 is lighter — it's your presentation.
Cohort 14 starts February 10.
22 seats left. The next cohort after this one starts in June — your docs can't wait that long.
90-day guarantee · stipend template provided
Enrol or ask a question
Not sure it's the right fit? Say what you write and for whom — we answer every question within one business day, honestly.
- hello@example.com
- February 10 – April 4
- Tue + Thu · 12pm ET, recorded