Leading the Change: How Ellen Juhlin Introduced Discovery Habits at Orion Labs

Teresa Torres interviews Ellen Juhlin, a product leader at Orion Labs, about how she introduced continuous discovery habits to a team that had been driven by founder-led outputs, sales-driven feature requests, and bloated priority meetings. Ellen started small by having product managers run story-based customer interviews during a pilot, then gradually added outcome-based thinking to the roadmap and brought engineers into structured brainstorming, story mapping, and assumption testing. Her approach was to meet each group where it was rather than forcing the whole framework at once, redirecting energy instead of shutting it down. The conversation matters because it shows incremental adoption working in a real, non-idealized org over about two and a half years.

01Key takeaways

• Introduce one discovery habit at a time to the people most receptive to it rather than demanding full adoption from the whole organization.
• Story-based interviews reveal the context behind requests, which is far more useful than a list of features from sales or customer success.
• Attach business outcomes to every proposed output so priority debates center on whether work will actually move the metric.
• Frame engineers' concerns as assumptions to label and test, redirecting their energy instead of shutting down their ideas.
• Externalize solution thinking with story maps and assumption maps; the shared artifact reduces contentious opinion-based decisions even before any test runs.
• Changing product strategy to outcomes also asks other executives to change how they think about business strategy, so expect slow, gentle iteration.

02Key sections

Starting point at Orion Labs

Orion's product decisions were driven by fire drills, investor and competitor pressure, and bloated priority meetings with too many opinions. Six-week planning cycles and a smaller product strategy board helped, but customer knowledge was filtered through sales and customer success.

Story-based interviews as the first habit

A product manager running the logistics of a customer pilot gained direct access to end users, and story-based interviewing surfaced context far richer than feature requests. Teammates adopted the practice after seeing its value.

Adding outcomes to the roadmap

Ellen linked each output on the prioritization spreadsheet to a business outcome, nudging the strategy board to question whether features would actually drive those outcomes.

Engineers join brainstorming and story mapping

In a one-hour session, a product manager-designer and mobile engineers generated and story-mapped solutions, then surfaced key assumptions that were mapped and later tested with a quick prototype. Ellen facilitated by labeling engineers' concerns as assumptions rather than dismissing them.

Lessons from pacing and iteration

Ellen avoided wholesale mandates, which had failed in her past, and introduced one habit at a time to receptive groups. Two and a half years later, the outcome map anchors strategy meetings and assumption artifacts reduce opinion-driven debates.

03From the post

“For many product teams, continuous discovery is a brand-new way of working. It involves strengthening your understanding of business outcomes, fostering collaboration in product trios, and cultivating many other habits like conducting regular story-based interviews, mapping opportunities on the opportunity solution tree, and identifying and testing assumptions. While”

04Frameworks mentioned

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