managing-timelines

SKILL.md

Help teams set realistic deadlines and hit them consistently using frameworks from 13 product leaders.

Diagnose timeline problems as estimation issues, scoping issues, distraction issues, or unrealistic stakeholder expectations, then apply the right framework (phase-based commitments, hill charts, or early shipping)

Commit to phases within your control (discovery, solutioning, build, launch) rather than distant delivery dates; only provide engineering dates once solutioning is complete

Ship early and iterate with remaining time instead of front-loading estimation; use hill charts to visualize uncertainty and identify high-risk work stuck in discovery

Account for the planning fallacy (tasks take 3x longer than estimated due to distractions) and treat deadlines as hard constraints; use weekly RAG status reviews to surface and unblock issues early

Managing Timelines

Help the user set and hit realistic project timelines using approaches from 13 product leaders.

How to Help

When the user asks for help with timelines:

Understand the context - Ask about the nature of the deadline (external commitment, internal target, manufactured milestone), the stage of the work, and what's driving the timeline pressure

Diagnose the problem - Determine if this is an estimation issue, a scoping issue, a distraction issue, or unrealistic stakeholder expectations

Apply the right framework - Help them use phase-based commitments, hill charts, or early shipping strategies depending on their situation

Build healthy habits - Guide them toward sustainable timeline practices rather than one-time fixes

Core Principles

Treat real deadlines as P0 - nothing else matters

Nan Yu: "The only way to make deadlines real is to take them so seriously that they are basically like a P0 problem, and everything else has to not matter in comparison." Don't have too many deadlines. Reserve them for critical external events and protect the team from all other distractions once set.