Why You Should Map Outcomes to Impact Metrics
Jeff Gothelf
Teaching executives to simplify prioritization and decision-making by putting the customer first.
Last summer I published?a post defining the terms impact, outcome, output and KPI’s . Much of?the OKR conversation ?lately has been about deciding what is a good outcome to use as your key result. Given our customers do so many things in our products, how do we know which behavior is the one we should optimize for this quarter? Next quarter?
PUT YOUR OUTCOMES IN CONTEXT
An outcome is a measure of human behavior. These behaviors don’t happen in a vacuum. Something happens before each one. Something happens after. As you set out to determine this quarter’s key results, consider creating?a user journey map ?or?user story map ?for the product or experience you have control over as a way to visualize the paths your customers take. Once you have the various journeys mapped, start consolidating them into one tree that looks like this:
Each step in the map connects a customer behavior to another one, until we reach company metrics.
In this exercise you are visualizing the explicit connection between what customers do in the system and how the company makes money. You’re doing this without mentioning any kind of specific features or launches. The conversation you are mapping is focused exclusively on the customer, their actual behavior in the product and the various ways that impacts the organization’s impact metrics – the high level measures of the health of the business.?
领英推荐
CUSTOMER JOURNEYS AREN’T ALWAYS OBVIOUS OR KNOWN
Many teams aren’t able to reliably predict specific customer paths through the product. This can be a result of a lack of access to data, a lack of data or too much distance between the team and the customer. If you find yourself in this situation you have at least two options:
PRIORITIZING WITH EVIDENCE
Once you have mapped your outcomes to your impact metrics, you’re ready to prioritize your team’s work. This part of the exercise is best served by having your stakeholders involved in the conversation. Structure it this way:
ALIGNING TEAMS AND STAKEHOLDERS ON OUTCOMES
This exercise paints a clear picture of how to positively impact the success of the company. It removes any meaningful conversation around features and instead focuses both team and stakeholders on changing customer behaviors. When the teams have an approved set of outcomes to work towards they can write meaningful, relevant and achievable goals using OKRs.?
Evolution through Illumination
2 年"Start running experiments and prioritize with evidence" is a great guide to be considered in a wide-range of scenarios.
Senior Technical Leader/Architect
2 年It is hard to get past the "wouldn't it be cool to add this feature" conversation. I think user Journeys and asking "why" around "wouldn't it be cool" could get to the behaviors we are trying to influence?
Teaching executives to simplify prioritization and decision-making by putting the customer first.
2 年Learn more about setting a user journey and optimizing consumer behaviors in my OKRs course! Check it out: https://senseandrespondpress.thinkific.com/courses/objectives-key-results-everything-you-need-to-know-to-get-started