Curriculum
How my team learns to do this work.
A reading list, not a syllabus. Every role reads Core first, then their role track. Tells you how to think and what to read next, not what every page says.
If two people on the team disagree, the curriculum is what we both agreed to before the disagreement.
How to Use It
- Read Core in order, end to end. Once.
- Read your role track. Once.
- Revisit when the situation calls for it. New project? Reread Project Onboarding. Hard 1:1 coming? Reread Feedback & Difficult Conversations.
- When a section feels wrong or thin, tell me.
The Tracks
- Core — every role reads first. Foundations, thinking, communication, operating cadence, career.
- Product Engineer
- Product Manager
- Product Designer — early, mostly still being written
Not Here Yet
Hiring & interviewing, on-call & incident response, working with customers/sales/support, cross-functional playbooks. Ask if you need one now.
Inspired by Matt Mochary's curriculum, which I refer back to often.