Technical Writing for Teams Lab

The Technical Writing for Teams Lab is Unori's dedicated track for squads who ship docs alongside code. Three panels below map skills, tooling, and review checkpoints.

1 — Skills map

Foundations

  • ▸ Voice & tone matrix
  • ▸ Terminology control
  • ▸ Inclusive language pass

Delivery

  • ▸ Release notes
  • ▸ API reference
  • ▸ Runbooks & incident comms

Governance

  • ▸ Review cadence
  • ▸ Doc ownership
  • ▸ Deprecation notices

2 — Tools & workflow stack

Git + Markdown Source of truth for docs in PRs
OpenAPI 3.x Reference generation and tutorial splits
Mermaid / Excalidraw Diagrams versioned with text
Markdown lint Automated style enforcement in CI
Notion / Confluence Internal drafts with export paths
Review threads 48h mentor SLA in cohort workspace
Technical writer reviewing API documentation on monitor

3 — Practice milestones & review checkpoints

  1. Week 1–2 Charter + style guide v1 Mentor sign-off on scope doc
  2. Week 3–4 API or release-notes sprint Peer + mentor dual review
  3. Week 5–6 Runbook or onboarding path On-call engineer tabletop
  4. Week 7–8 Portfolio pack Team readout with checklist handoff
View full program