Curriculum

How my team learns to do this work.

A reading list, not a syllabus. 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

1. Read How Systeric Works and The Team first. Context for everything else.
2. Read The Journey. This is how we build things.
3. Read Core in order, end to end. Once.
4. Read your role track. Once.
5. Revisit when the situation calls for it. New project? Reread Project Onboarding. Hard 1:1 coming? Reread Feedback & Difficult Conversations.
6. When a section feels wrong or thin, tell me.

How We Build Things

• Quarterly Roadmap
• Discover
• Define
• Build
• Launch
• Learn

Role Tracks

• Core — every role reads this. Foundations, thinking, communication, operating cadence, career.
• Product Engineer
• Product Manager
• Product Designer — early, mostly still being written

Not Here Yet

Hiring & interviewing, 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.