Managing Timelines

# Managing Timelines - All Guest Insights

*13 guests, 14 mentions*

---

## Ada Chen Rekhi
*Ada Chen Rekhi*

> "Figure out, maybe the night before, the one thing that you want to get done in your day, and then at the earliest opportunity, just try to give yourself five minutes on it."

**Insight:** Overcome 'productive procrastination' by committing to just five minutes of your most important task early in the day.

**Tactical advice:**
- Identify your 'one thing' the night before.
- Use the 'five-minute rule' to lower the mental hurdle of starting a difficult task.

*Timestamp: 01:15:43*


## Annie Pearl
*Annie Pearl*

> "Something we've done over the last year is really kind of moved to a model of talking about dates and promising and committing to dates that are within our control. And so, if you think about the product development life cycle, we can commit to a discovery effort... we've gotten a lot better at making the commitments around the work that's right in front of us versus making a commitment around a project six months out when we haven't even done enough discovery."

**Insight:** Commit to dates only for the immediate phase of work (discovery or solutioning) rather than long-term delivery dates for un-scoped projects.

**Tactical advice:**
- Break the lifecycle into Discovery, Solutioning, Build, and Launch.
- Only provide engineering delivery dates once the solutioning phase is complete and estimation is accurate.

*Timestamp: 00:36:30*


## Aparna Chennapragada
*Aparna Chennapragada*

> "What I'm seeing is that the time to first demo is much shorter, but the time to a full deployment is going to take longer. So I think that there's going to be an uneven cadence. So typically, I think there was much more of a you've been this thing, you take a few weeks and then you can iterate and so on. But that inner loop of prototyping and iterating and getting even user research through AI conversations, all of that gets shortened. But I think the bar for scale, therefore becomes much high."

**Insight:** AI development creates an uneven cadence where initial prototypes happen rapidly, but reaching production-grade scale and reliability takes significantly longer than traditional software.

**Tactical advice:**
- Plan for a shortened 'inner loop' for prototyping and discovery
- Allocate significant time for the 'outer loop' of scaling and deployment
- Manage stakeholder expectations regarding the gap between a successful demo and a shippable product

*Timestamp: 00:24:04*


## Brian Chesky
*Brian Chesky*

> "I had a head program manager that would score all the projects. Either they're green, yellow, or red. Meaning they're on track or not on track to ship... I use the reviews of the work every single week. And the reason there's not a lot of bureaucracy... is I'd review the work and if something wasn't happening, then I would stop the meeting and say, 'Why isn't this happening?'"

**Insight:** Use high-status program management and frequent executive reviews to maintain shipping velocity and identify bottlenecks.

**Tactical advice:**
- Elevate program management to a high-status role
- Use a simple RAG (Red, Amber, Green) status for project tracking
- Review work weekly to identify and unblock individual engineers

*Timestamp: 00:27:11*


## Dylan Field
*Dylan Field 2.0*

> "If timelines are maybe not well reasoned through from first principles and perhaps there's padding that has been well intentionally added by different folks, you have to understand fully, okay, what are the assumptions of how long things will actually take and what is a padding? Then, really work through that with the team."

**Insight:** Challenge timeline estimates by digging into the underlying assumptions and identifying unnecessary padding.

**Tactical advice:**
- Ask 'why' to uncover hidden constraints or unnecessary padding in estimates
- Work through timeline assumptions from first principles with the team

*Timestamp: 00:10:27*


## Eli Sch