Productside Webinar
How to Write Great Outcome Statements
Craft outcome statements that inspire action, align stakeholders, and guide your team to success.
Date:
Time EST:
Is your team guessing what success looks like? Join Tom Evans and Ryan Cantwell on January 29 for a webinar that breaks down the art of writing clear and actionable outcome statements. Learn how to differentiate between business and product outcomes, articulate measurable goals, and ensure your team is always focused on what matters most. Don’t let vague outcomes slow you down—bring clarity and focus to your roadmap.
What You Will Learn:
- The difference between Business Outcomes and Product Outcomes—and why both matter.
- How to craft outcome statements that drive alignment and action.
- Best practices to guide your team toward measurable, impactful goals
Welcome and Introduction
Ryan Kwell | 00:00–02:50
Hello everybody and welcome! I’m Ryan Kwell and I’m joined today by Tom Evans. We both work together at Productside as consultants and trainers. We’re thrilled to talk about today’s topic: writing good outcome statements.
Tom Evans | 02:51–05:00
I’ve been with Productside for almost 15 years, working with clients around the world to implement better product management practices. I’m based in Austin, Texas, and I’m excited for today’s session.
About Productside
Ryan Kwell | 05:01–07:10
At Productside, we know how hard it can be to deliver products people love. Whether it’s aligning stakeholders, predicting customer needs, or managing backlogs, we’ve seen it all. We want to be your outcome-driven partner, tailoring solutions to your challenges and driving transformation.
Poll #1 – Which Goals Does Your Executive Team Use?
Tom Evans | 07:11–10:00
Let’s start with a poll: Which goals does your executive team use to guide product managers? Business outcomes, product outcomes, feature delivery, or something else?
Ryan Kwell | 10:01–11:00
58% said “Business Outcomes.” That’s great—it means teams are focusing more on value and results than outputs.
Why Focus on Outcomes?
Tom Evans | 11:01–16:30
An output is what you deliver—features, capabilities, or products. An outcome is the difference your work makes. Outputs drive outcomes, but if we focus only on outputs, we miss whether we’re making an impact.
Ryan Kwell | 16:31–18:00
An outcome gives you the “why” behind the work. It helps your team align around a common goal rather than just checking off tasks.
Business Outcomes Explained
Tom Evans | 18:01–25:30
Business outcomes support company goals. Whether you’re in a for-profit, nonprofit, or internal team, your work drives organizational success. Business outcomes may focus on revenue, growth, or efficiency. The key is to connect product work to business impact.
Ryan Kwell | 25:31–27:00
Right—goals like “grow revenue 20%” are general, while “expand market share in Asia Pacific by 10%” is targeted. Specificity helps teams prioritize.
Five Strategies for Achieving Business Outcomes
Tom Evans | 27:01–33:20
To achieve business outcomes, companies can: (1) retain current customers, (2) win customers from competitors, (3) increase purchases from existing customers, (4) expand value propositions, or (5) enter new or underserved markets. These strategies help teams focus their product planning.
Ryan Kwell | 33:21–35:00
So Tom, how do you know which strategy is right for you?
Tom Evans | 35:01–37:00
That’s where market analysis comes in—understanding market share, competition, and growth opportunities guides which strategy fits best.
From Business Outcomes to Product Outcomes
Tom Evans | 37:01–43:00
Product outcomes deliver value to customers. They’re about benefits to users, not the company. For example, in an airport, a security operations manager’s outcome might be “reduce passenger wait times.” Those user outcomes roll up into customer or business outcomes.
Ryan Kwell | 43:01–45:00
Exactly. The name “product outcome” can be misleading—it’s really about the people you serve and the improvement they want to make.
How to Express Product Outcomes
Ryan Kwell | 45:01–48:00
Customers want to increase or decrease something—speed, efficiency, or errors. For instance: “Increase passengers processed per hour” or “Decrease unprepared passengers.” These clear metrics help prioritize features.
Communicating Outcomes to Stakeholders
Tom Evans | 48:01–51:00
Communicate outcomes by showing how outputs connect to product outcomes, and how those connect to business outcomes. This alignment story helps stakeholders understand your decisions and support your strategy.
Poll #2 – Applying What You’ve Learned
Ryan Kwell | 51:01–53:00
Which of today’s topics will you apply first? Writing clearer business outcomes, writing product outcomes, or communicating outcomes to stakeholders?
Tom Evans | 53:01–54:00
Most participants chose improving business and product outcomes. That’s great—it shows practical value from today’s discussion.
Q&A and Closing Remarks
Rina Alexin | 54:01–59:00
Questions included how to define outcomes, align executives, and shift from feature-focused to outcome-focused work. Thank you to everyone who participated!
Ryan Kwell | 59:01–End
Thank you all for joining. Don’t miss our upcoming webinar on “Agentic AI” with Dean Peters on February 12. Visit Productside.com to register and learn more.
Webinar Panelists
Tom Evans