Adopting a Continuous Discovery Mindset Across the Organization

Teresa Torres, who teaches design-based courses at Northwestern, argues that continuous discovery principles extend beyond product work to broader organizational challenges like engagement, team effectiveness, and knowledge sharing. She frames these as open-ended 'design challenges' with unknown problem spaces, multiple criteria, and no silver bullet. Her core approach moves teams from output-focused programs toward outcome-focused goals, discovers opportunities through stories of both problems and bright spots, and tests multiple solutions through rapid prototyping. The piece matters because the same mindset that makes product teams effective only works if the wider organization adopts it too.

01Key takeaways

• Define the desired outcome first by asking how you would know the challenge is solved.
• Measure teams on achieving outcomes, not on delivering the programs they were assigned.
• Set outcomes at a scope matching the team's span of control to avoid dictating outputs or overreaching.
• Break a vague organizational problem into specific moments in time that can be intervened in.
• Compare several candidate solutions rather than adopting the first quick fix, to counter confirmation bias.
• Prototype only the riskiest parts of a solution with the people it affects to gather reliable feedback quickly.

02Key sections

Why this extends beyond product

Torres describes teaching design methods to students and executives tackling internal people problems, finding the same approach effective outside product. She notes that Agile teams hit friction when the rest of the business didn't share the mindset.

What a design approach is

Design challenges have unknown problem spaces, several evaluation criteria, and no single fix, so the work begins by defining the desired outcome and framing the problem before solving it.

Shifting from outputs to outcomes

Launching programs like social networks or lunch-and-learns does not prove progress; teams should be measured on whether the outcome was achieved, with the right scope of outcome matched to their span of control.

Discovering opportunities and solutions

Interviews uncover pain points and bright spots, which are broken into small solvable moments. Teams then compare multiple solutions and prototype the riskiest parts with the people affected.

Managing messy progress

The process loops back on itself; failed prototypes reveal new understanding, so teams should keep revising their path to the outcome while co-creating with constituents.

03From the post

“I teach two courses at Northwestern University. I want to share a little bit more about the work that I am doing there as I think it’s relevant for people working at companies who are starting to adopt continuous discovery practices (in other words, many of you). The first”

04Frameworks mentioned

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