managing-timelines
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.
Commit to phases, not distant delivery dates
More from refoundai/lenny-skills
personal-productivity
Help users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done.
4.6Kcompetitive-analysis
Help users understand and respond to competition. Use when someone is positioning against competitors, evaluating market threats, running competitive war games, or deciding how much to focus on competitors versus customers.
1.9Kbrand-storytelling
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
1.8Kwriting-prds
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
1.7Kcontent-marketing
Help users build content marketing strategies. Use when someone is starting a blog, building SEO, creating thought leadership content, or deciding on content formats and distribution channels.
1.7Kvibe-coding
Help users build software using AI coding tools. Use when someone is using AI to generate code, building prototypes without deep technical skills, or exploring how non-engineers can create functional software through natural language.
1.7K