176 / Axel Sooriah: Discovery Done Right To Drive Product Success

Our conversation with Atlassian’s Axel Sooriah is the fourth in a series that Product Momentum recorded at INDUSTRY. And it’s interesting to see the common themes that are emerging – serendipitously – most notably that even as AI casts its long shadow over all things product, our recent episodes seem to be bringing us back to product management fundamentals: good process (John Cutler), sound communication (Sahil Jain), data readiness / skills development (Shensi Ding), and making bets (Michelle Parsons) (episode coming soon!).

In this episode, Axel touches on another common theme: “Everywhere in product management, wherever you sit, whichever size the organization is, it’s pretty much the same challenges everywhere.” In other words, we all seem to face the same disjointed collaboration among stakeholders, the absence of evidence-based decision making, a lack of clarity around goals, and the looming disconnect between them and organizational objectives.

Discovery will help teams move beyond just “finding user problems,” Axel says, to actually delivering the outcomes they’re seeking.

Here’s what we learned:

Clear Goals and Outcomes Enable Discovery

One of the biggest challenges Axel sees is product teams operating without clarity around goals or desired outcomes. This undermines their ability to conduct meaningful discovery, he says. The remedy, Axel offers, is to treat goal‑setting as part of discovery by asking questions like: ‘If we solved this customer problem tomorrow, what does success look like?’ and position our discovery activities around those outcomes.

Experimentation and Evidence Create Decision Confidence

The lack of structured frameworks for generating evidence leads to shaky decisions rather than confident ones. “A lot of teams today make decisions that are not anchored in evidence,” Axel says. “It’s not because they don’t want to, it’s sometimes because they’re not set up to do it.”

His recommended approach is a structured discovery flow: start with qualitative customer interviews to identify the problem, then prototype and experiment before coding for the full build. This exploration helps validate problems and solutions, so delivery is built on a firm base of evidence rather than a host of assumptions.

Transparent Stakeholder Engagement Through Discovery Story‑telling

Too often, discovery that is performed happens in isolation and doesn’t engage the organization’s leadership. Axel explains: “One of the ways we address this in our product teams, for example, is we use a lot of video reels of our customers – and then share it with stakeholders. There is no arguing with a video of customers explaining the intensity of a problem … it steers the conversation, because … why would an exec not agree with the reality of a customer?” In other words, sharing discovery artifacts helps build alignment and buy‑in. When you bring stakeholders into the process early on, discovery becomes a strategic communication tool rather than just part of a pre‑build checklist.

Discovery isn’t optional. Full stop. It’s the foundation for making confident product decisions and delivering real user value.

---

Be sure to catch the entire episode with Axel Sooriah and learn about Atlassian’s “4 Stages of an Idea.”

The post 176 / Axel Sooriah: Discovery Done Right To Drive Product Success appeared first on ITX Corp..