Timeline Padding Audit
Keep startup pace by curiously separating real constraints from padding, and killing projects that won't converge.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 82%
A leadership practice for maintaining fast pace in a maturing company: interrogate timelines from first principles to distinguish genuine constraints from well-intentioned padding, question hidden path dependencies, and be willing to cut projects that drag. Use it when a scaling org starts to slow and estimates balloon.
Origin
Asked how Figma keeps startup pace at 13 years old, Field described selecting well-motivated problems, then attacking timeline padding through curiosity, checking path-dependency assumptions, and moving off projects that fail to converge.
Core principles
- 01Start from well-motivated problem selection before worrying about speed.
- 02Approach estimates from curiosity, not confrontation; often you are the one missing a constraint.
- 03Interrogate path dependencies: assumed requirements that aren't real, and real ones being ignored.
- 04If a project won't converge, be willing to move on rather than let it drag.
How to run it
- 1
Understand the underlying work
Get curious and learn the actual work being done; the more you understand, the better you can challenge or accept an estimate.
Pro tip Lean on team members who are more expert than you in their area; the audit is not a solo act.
- 2
Separate constraint from padding
Work through with the team what the true assumptions about duration are and what is padding, staffing, or a genuine hidden constraint.
Watch out Often the estimate is right and you're missing a real constraint; sometimes the team is under-resourced and needs more, not less.
- 3
Check path dependencies
Test whether an assumed requirement is actually required, and whether something dismissed as optional is in fact critical and worth slowing for.
- 4
Cut what won't converge
If a project keeps dragging without converging, move resources (and sometimes people) to better-fit work.
Pro tip Match people to the projects they're genuinely fired up about; motivated people outperform, unmotivated ones merely cope.
- 5
Watch for systematic tech debt
When things are chronically slow, check whether tech debt or wrong-way construction is the real cause, and balance fixing it against pushing new work.
In the wild
Field said his intense questioning of timelines comes from a place of curiosity, and that often the estimate is longer because of constraints he doesn't know about, not because of padding. Sometimes an area simply needs to be resourced better.
→ A questioning process that surfaces the real driver of a slow timeline rather than just pressuring for a smaller number.
Common mistakes
Assuming every long estimate is padding
Frequently the timeline is long for real reasons the leader doesn't yet see; interrogating from curiosity avoids wrongly compressing it.
Letting non-converging projects drag on
Refusing to move on from work that won't converge quietly kills company pace.
Is it for you?
Best for
Founders and leaders of scaling companies trying to keep startup velocity as headcount and process grow.
Not ideal for
Teams that are actually under-resourced, where the answer is more staffing, not faster estimates.
From the transcript
“if things are not converging, dragging out, you have to be willing to um move on and move to other projects.”
“you have to kind of understand fully okay what are the assumptions of how long things will actually take and what's what is padding and…”
“There's a lot of times that folks will um assume that there's some requirement that actually is not a requirement”
From the episode
Figma’s CEO: Why AI makes design, craft, and quality the new moat for startups
Dylan Field