Continuous Product Discovery is for Everyone [Case Study]

Teresa Torres argues that continuous product discovery is not limited to famous consumer tech companies; any product team, including those at traditional enterprises, can practice it. She uses a case study of Farm Credit Services of America, a lender serving farmers that builds its own tools, to show a team learning to connect customer contact with product decisions. The team had been jumping to solutions based on assumed customer needs and relying on business owners as intermediaries. With coaching, they began structured customer interviews, built lo-fi experiments, and defined success criteria up front. The piece matters because it reframes discovery as a practice available to any team willing to change its habits, not a privilege of certain companies.

01Key takeaways

• Any team can practice continuous discovery; the question is whether it is willing to change its habits, not whether its industry is suitable.
• Regular customer contact only becomes valuable when it is deliberately used to inform product decisions.
• Notice when your team jumps to solutions and treats its own process needs as customer needs.
• Validate with lightweight prototypes shown to a handful of customers before investing in heavy measurement.
• Define what success, failure, and need for more research look like before running an experiment.

02Key sections

The excuse of being different

Torres observes that teams often assume continuous discovery only works for consumer giants, and that this belief is a way of avoiding change. She reframes the useful question from who does it well to how any team could do it.

The case study setup

She introduces FCSAmerica, an agricultural lender with its own technology shop, as an unlikely but committed discovery team. The team already cared about customers but struggled to turn those conversations into product insight.

From customer contact to customer needs

Team members describe starting with solutions in mind, relying on intermediaries for customer access, and running usability tests that checked design rather than whether the solution met a real need. Coaching helped them realize customers valued business partnership more than digital tools alone.

Simpler experiments and clearer metrics

Torres steered the team away from over-engineering validation and toward showing lo-fi prototypes to five to ten customers. The team then defined in advance what success, further research, or abandonment would look like.

Lasting changes

The team reports building just enough of a solution to learn, with customer interviews spreading to other groups and reshaping how insights are gathered. The team still describes itself as in early stages.

03From the post

“When I write or speak about continuous discovery, I worry that people are enamored with this way of working, but aren’t doing the work to put it into practice. It’s easy to read about a continuous discovery habit and think, “That could never work for my team. Our”

04Frameworks mentioned

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