Learn the system.
The whole curriculum, click to read. Take the slice your role needs; everyone starts at the top.
Everyone (mandatory)
01The complete picture: the machine, what it can do, how to work it, the app and the model.
- 01How the system works
- 02What I can do for you
- 03How to work with me
- 04Where you work, and the model behind it
Weekly operators
02The craft on top of the operating model: the power moves, the writing standards, your own expert.
- 01A few moves that lift the quality
- 02The three writing standards
- 03Building your own expert on a subject
Weekly operators
03Make your own: a knowledge file, a spec, a skill, and the feedback loop.
- 01Teaching me something once, so I keep it
- 02Writing down a plan for a bigger job
- 03Turning something you repeat into a reusable job
- 04How your corrections make me better
End users
04Working a domain day to day: the rhythm, context and data, the job.
Domain owners
05Stewarding a domain: ownership, the boundary, curation, the plan, the anti-patterns.
- 01What owning a domain means
- 02What you decide vs. what the builder decides
- 03Keeping the knowledge right, on a rhythm
- 04The owner role as a job description
- 05The boundary under real-week pressure
- 06Tracking the work, and handing it to a builder
- 07The mistakes owners make
System owners & execs
07Leading the rollout: roles, governance, security, adoption, the compounding.
- 01Who can change what
- 02The five seats
- 03Placing your people in the seats
- 04How updates reach you, and what stays sealed
- 05Security in plain terms
- 06Designing roles across your team
- 07Making it stick past week one
- 08Knowing it’s working
Reference, on demand
ASurfaces, channels, connected tools, git, model and effort — out of the main path.
- 01The desktop and phone apps
- 02Letting long work run on its own
- 03A quick chat vs. real work
- 04Reaching me from a chat app you already live in
- 05What each connected system unlocks
- 06The logbook by its real name — git
- 07Choosing the model and the effort