Continuous discovery is the practice of talking to customers on a recurring cadence so that product decisions are always grounded in current customer context. It's not a research phase with a start and end date. It's a habit.
The term comes from Teresa Torres. The core idea: if you're only talking to customers before big launches or when something breaks, you're already too late. By the time a research sprint wraps up, the team has usually already made the decisions it was meant to inform.
What it looks like in practice
It doesn't mean running formal usability studies every week. Continuous discovery is usually lighter, short structured interviews, quick customer calls, or regular observation of how people use your product.
The goal is to stay close enough to customers that insights arrive as a steady stream, not a flood. When your team reviews what to work on next in FeatureOS Boards, you want to be drawing from recent, specific conversations, not month-old survey data.
Why most teams skip it
Talking to customers takes coordination and doesn't produce a deliverable. When the backlog is full and the sprint is starting, customer calls feel like a distraction.
But teams that keep the cadence tend to waste less time building things nobody wants. One weekly interview beats three weeks of post-launch scrambling.