No Time for Discovery? Here’s How to Fix It.

Teresa Torres and Hope Gurion walk through the seven most common reasons product teams say they have no time for discovery, and offer practical fixes for each. The core argument is that discovery should run in tandem with delivery rather than competing with it, and that 'no time' usually masks a deeper cause such as delivery overload, stakeholder or meeting overload, cross-team dependencies, support burden, weak organizational value for discovery, or discovery that is slow because the team has not built tools or process. Their advice is to diagnose the real root cause, then start small with one tangible habit that proves value. This matters because teams that wait for time to appear before starting rarely begin at all.

01Key takeaways

• Diagnose the real root cause behind 'no time' before trying to fix it.
• Move delivery tasks like story writing and stand-ups to engineers to recover calendar hours.
• Replace recurring status meetings with shared visual artifacts such as opportunity trees and story maps.
• Audit your meetings and test whether your presence is actually required before attending.
• Start with one small discovery habit, like weekly customer interviews or assumption mapping, and let visible results build interest.
• Automate recruiting and tooling early, since discovery should get faster as the team matures.

02Key sections

Delivery and stakeholder overload

Teams consumed by backlog management, status reporting, and stakeholder meetings can shift work to engineers and replace meetings with shared visual artifacts. Freed-up hours can go toward solution discovery and assumption testing.

Cross-team coordination and dependencies

Org structures that create many interdependencies drain time through large reconciliation meetings. Decoupling one or two teams and visualizing dependencies with shared artifacts reduces this load.

Product support burden

Constant questions from sales and support signal either an unstable product or insufficient enablement. The fix depends on the diagnosis: stabilize with outcomes around support ticket reduction, or build scalable enablement through documentation, specialists, and dedicated time blocks.

Meeting overload and culture

Calendars full of meetings often reflect a need to be seen rather than real necessity. Auditing meetings, moving updates to async channels, and testing absence are recommended, and when discovery is undervalued, leaders should reward fast learning and start with a small, tangible habit that others notice.

Discovery that takes too long

Early discovery feels slow because of a learning tax and missing tooling. Automating recruiting and adopting survey, analytics, and unmoderated testing tools makes discovery faster over time, so teams should track whether their tests are getting quicker week over week.

03From the post

“It’s true that discovery takes time. Interviewing customers, building opportunity solution trees, running assumption tests—these are all activities that take your attention away from delivery. But I’m also a firm believer that discovery doesn’t come at the expense of delivery. Both activities should happen in tandem”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.