Unit 5: The discovery-delivery balance when AI accelerates execution

Learning objectives

Establish the right ratio of discovery to delivery work. Prevent AI-driven execution speed from crowding out discovery. Build organizational rhythms that protect discovery time.

Video script

Reading material

Structuring dual-track work

Teresa Torres' dual-track approach remains the gold standard for balancing discovery and delivery, adapted for AI-accelerated teams.

Discovery track. Runs continuously in parallel with delivery. Weekly customer touchpoints. Assumption testing. Prototype validation. Data analysis. Competitive monitoring. This track generates the insights that inform what the delivery track builds.

Delivery track. Sprints or cycles focused on building, shipping, and maintaining the product. The delivery track executes on the solutions that the discovery track has validated.

The connection point. A weekly "discovery review" where the product trio shares what they've learned and how it affects current and planned delivery work. This is where discovery insights translate into delivery decisions.

In an AI-accelerated context, the delivery track moves faster, which means the connection points need to be more frequent. If your team used to review discovery weekly, consider making it twice weekly when delivery cycles are shorter. The faster you build, the more frequently you need to check that you're building the right thing.

Protecting discovery from organizational pressure

Make discovery outcomes visible. Share a weekly "what we learned" update alongside your delivery progress. Example: "This week we shipped the notification redesign (delivery) and learned that 3 out of 5 users we tested with couldn't find the new settings panel (discovery). We're adjusting the next sprint based on this."

Tie discovery to business outcomes. When a discovery insight leads to a better product decision, highlight it. "Our customer interviews revealed that the feature we planned to build wouldn't address the actual problem. We changed course and the revised approach improved retention by 8%. This is why we invest in discovery."

Set organizational expectations. Product leaders should explicitly communicate the discovery-delivery balance to stakeholders. "Our teams spend 20% of their capacity on customer research and experimentation. This investment is what ensures the other 80% is spent building the right things."

Practical exercise

Exercise: Discovery-delivery audit and plan

1. Estimate your current discovery-delivery ratio. What percentage of your team's time goes to each?
2. Identify the specific discovery activities your team does (or should do) regularly.
3. Design a weekly rhythm that allocates 20-25% to discovery. Be specific: which activities, when, who participates.
4. Identify the top 3 organizational pressures that would undermine this allocation. For each, describe how you'd protect the discovery time.
5. Write the "what we learned" update you'd share after one week of this rhythm.

Leadership reflection: When was the last time a discovery insight changed a delivery decision on your team? If you can't remember, what does that tell you?