Success Metrics
There are two formatting options available. The tradition desired outcome statement is a structure used in the Outcome-Driven Innovation methodology. Since many stakeholders - especially when involved with marketing or UX teams - push back on the utilitarian nature of desired outcomes statements since people don’t talk like that, the alternative is a natural language structure that gets to the heart of the outcome and tries to avoid tasks and activities where feasible.
This catalog contains 20 potential metrics using each formatting option. You will likely need to reduce this set for a survey. The number of statements that have been generated is arbitrary and can be expanded to accommodate your needs.
Desired Outcome Statements (ODI)
- Minimize the time it takes to evaluate the product against initial expectations and requirements, e.g., performance metrics, feature checklist, etc.
- Minimize the time it takes to gather feedback from all users of the product, e.g., surveys, informal discussions, feedback forms, etc.
- Minimize the time it takes to compare the product’s performance with alternative options or competitors, e.g., benchmarking studies, online reviews, etc.
- Minimize the time it takes to assess the product's impact on productivity or efficiency, e.g., time saved, workflow improvements, etc.
- Minimize the time it takes to evaluate the long-term value and return on investment of the product, e.g., cost-benefit analysis, durability assessments, etc.
- Minimize the time it takes to identify any unmet needs or gaps in functionality, e.g., missing features, additional requirements, etc.
- Minimize the time it takes to understand how the product integrates with and enhances existing systems or processes, e.g., compatibility checks, system improvements, etc.
- Minimize the time it takes to assess customer support and service experiences related to the product, e.g., responsiveness, problem resolution, etc.
- Minimize the time it takes to evaluate the ease of use and user-friendliness of the product, e.g., learning curve, intuitive design, etc.
- Minimize the time it takes to determine the product’s reliability and consistency in performance, e.g., uptime, error rates, etc.
- Minimize the time it takes to consider the product's scalability and adaptability to future needs, e.g., upgrade paths, modular features, etc.
- Minimize the time it takes to assess the environmental and ethical impact of using the product, e.g., sustainability, ethical sourcing, etc.
- Minimize the time it takes to evaluate the overall satisfaction and willingness to recommend the product to others, e.g., Net Promoter Score, testimonials, etc.
- Minimize the time it takes to plan for ongoing or additional training if required for maximizing product use, e.g., advanced tutorials, expert consultations, etc.
- Minimize the time it takes to analyze the product's impact on personal or organizational goals, e.g., KPIs, strategic objectives, etc.
- Minimize the likelihood of biased or inaccurate assessments due to limited data or perspectives, e.g., seeking diverse feedback, using objective metrics, etc.
- Minimize the time it takes to identify opportunities for enhancing product use through additional features or accessories, e.g., add-ons, upgrades, etc.
- Minimize the time it takes to plan for regular reviews of product satisfaction and performance, e.g., scheduled evaluations, periodic check-ins, etc.
- Minimize the time it takes to understand the process for escalating concerns or dissatisfaction with the product, e.g., customer service channels, warranty claims, etc.
- Minimize the time it takes to assess the financial implications of continuing, expanding, or discontinuing product use, e.g., budget impact, cost of alternatives, etc.
Customer Success Statements (PJTBD)
- Evaluate the product against initial expectations and requirements, e.g., performance metrics, feature checklist, etc.
- Gather feedback from all users of the product, e.g., surveys, informal discussions, feedback forms, etc.
- Compare the product’s performance with alternative options or competitors, e.g., benchmarking studies, online reviews, etc.
- Assess the product's impact on productivity or efficiency, e.g., time saved, workflow improvements, etc.
- Evaluate the long-term value and return on investment of the product, e.g., cost-benefit analysis, durability assessments, etc.
- Identify any unmet needs or gaps in functionality, e.g., missing features, additional requirements, etc.
- Understand how the product integrates with and enhances existing systems or processes, e.g., compatibility checks, system improvements, etc.
- Assess customer support and service experiences related to the product, e.g., responsiveness, problem resolution, etc.
- Evaluate the ease of use and user-friendliness of the product, e.g., learning curve, intuitive design, etc.
- Determine the product’s reliability and consistency in performance, e.g., uptime, error rates, etc.
- Consider the product's scalability and adaptability to future needs, e.g., upgrade paths, modular features, etc.
- Assess the environmental and ethical impact of using the product, e.g., sustainability, ethical sourcing, etc.
- Evaluate the overall satisfaction and willingness to recommend the product to others, e.g., Net Promoter Score, testimonials, etc.
- Plan for ongoing or additional training if required for maximizing product use, e.g., advanced tutorials, expert consultations, etc.
- Analyze the product's impact on personal or organizational goals, e.g., KPIs, strategic objectives, etc.
- Avoid biased or inaccurate assessments due to limited data or perspectives, e.g., seeking diverse feedback, using objective metrics, etc.
- Identify opportunities for enhancing product use through additional features or accessories, e.g., add-ons, upgrades, etc.
- Plan for regular reviews of product satisfaction and performance, e.g., scheduled evaluations, periodic check-ins, etc.
- Understand the process for escalating concerns or dissatisfaction with the product, e.g., customer service channels, warranty claims, etc.
- Assess the financial implications of continuing, expanding, or discontinuing product use, e.g., budget impact, cost of alternatives, etc.
Test Fit Structure
Apply this to Customer Success Statements only. Everything should fit together nicely. Here’s an article where I introduced the concept. Feel free to devise your own version for Desired Outcome Statements as this does not apply to their format directly.
As a(n) [end user] + who is + [Job] you're trying to [success statement] + "faster and more accurately" so that you can successfully [Job Step]