Team
Self, and Leadership's Leading and Managing, are about how you operate. This is about how the work itself gets organized — the recurring rhythms, planning structures, and execution methods that hold regardless of who's running them.
Ordered by where it sits in the cycle, not alphabetically: planning an initiative, doing the work — including the ambient rhythm it all runs inside — and reflecting on what broke.
Plan
Build real understanding of the customer, decide what to build and why, then plan the specific initiative before you run it.
Tenets
Short, memorable principles for how the team should decide when nothing else spells it out.
Research
Customer discovery, interviews, and Jobs to Be Done — building real understanding of the customer, not the fast intake version Product Management uses to get started.
Product Management
Product strategy, roadmapping, and prioritization — defining what to build and why, before Project & Program Management figures out how.
Project & Program Management
Project Charter, RACI/DACI, Critical Path, Risk Management, and more — planning a specific initiative before you run it.
Do
Turn the plan into the thing itself, cycle by cycle.
Team Operating Rhythm & Cadence
Standups, retros, and status reporting — the ambient cycle everything else happens inside.
Agile / Delivery Process
Scrum, Kanban, and sprint ceremonies — how the plan actually gets executed, cycle by cycle. Also home to Retrospectives, Post-Mortems, and Pre-Mortems.
Technical / Engineering Process
Design docs, code review, and technical design — how the thing itself gets built.
Reflect
Figure out what broke and why.
Team Building
Doesn't belong to Plan, Do, or Reflect alone — building how the team works together as people, not just how the work itself gets organized.