1 min lesson
Scope before you schedule
Explain the order in "Scope before you schedule", then say how you would verify the result.
Step 1 of 2
Scope before you schedulethe order matters
Committing a date before you understand the dependency chain is how TPMs lose credibility in their first quarter. Walk the structure first, then the calendar falls out of it.
- 1Write the one-line goal. Metric, direction, guardrail, date. If you can't fit it on one line, you don't understand it yet.
- 2Name the owner of each work-stream. Not a team - a person. In a flat org, “Infra owns this” is a way to own nothing.
- 3Map the dependencies. What must finish before each piece can start? The longest chain is your real timeline, not the sum of optimistic estimates.
- 4Surface the top three to five risks now. Name them and the leading indicator you'll watch for each, while it's cheap to plan around them.
- 5Only then commit a date. Add explicit buffer where the critical pathThe longest end-to-end chain of dependent work in a plan; it sets the realistic timeline no matter how parallel everything else looks. A slip on the critical path moves the date; a slip on a task with slack does not. Press Enter for the full definition. crosses a team boundary, because handoffs slip.
Learn more
Full explanation
Right-size the process to the problem
Right-size the process to the problemoutcomes over ceremony
Cursor screens hard against process-for-its-own-sake. A two-week cost spike does not need a steering committee, a RACI matrix and a weekly 12-person sync. It needs a one-page doc, two owners and a daily glance at one dashboard.
Living risk register with named owners.
Weekly written status, monthly leadership review.
Explicit rollback gates and validation at each cutover step.
One scoping doc, two owners, one dashboard.
Async status in a thread; escalate only on a real blocker.
No standing meeting - the doc is the meeting.