Hey everyone,
I’ve seen a lot of chatter lately about a classic PM tension that feels more relevant than ever: the tug-of-war between Discovery and Delivery. We all champion the ideals of continuous discovery—deeply understanding user problems, testing assumptions, and iterating on prototypes. Yet, the reality for many of us is the relentless pressure of the delivery train. The backlog needs feeding, stakeholders want timelines, and the engineering team is waiting for specced-out tickets.
Before we know it, we’re spending 90% of our time on delivery logistics and 10% on actual discovery. This imbalance is dangerous. It’s how we end up with beautifully engineered features that miss the mark on user value, leading to team burnout and a product that bloats instead of evolves. The goal isn’t to stop the delivery train, but to be laying the tracks just a few feet ahead of it, ensuring we’re always heading in the right direction. It’s about weaving these two motions together, not treating them as separate functions competing for time.
So, how is your team managing this balance? Are you successfully running a dual-track process, or have you found a different way to embed true discovery into your sprints?