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 identify and document any issues or problems with the solution, e.g., performance glitches, user complaints, etc.
- Minimize the time it takes to develop and implement effective solutions to identified issues, e.g., software patches, process adjustments, etc.
- Minimize the time it takes to gather comprehensive feedback from all user groups, e.g., surveys, focus groups, interviews, etc.
- Minimize the time it takes to analyze feedback for actionable insights and improvements, e.g., trend analysis, user experience improvements, etc.
- Minimize the time it takes to communicate issues and resolutions clearly to all stakeholders, e.g., regular updates, transparent reporting, etc.
- Minimize the time it takes to coordinate with vendors or technical support for issue resolution, e.g., troubleshooting, expert consultations, etc.
- Minimize the time it takes to train or retrain users based on feedback and solution updates, e.g., refresher courses, new feature demonstrations, etc.
- Minimize the time it takes to implement changes or enhancements based on user feedback, e.g., feature upgrades, user interface adjustments, etc.
- Minimize the time it takes to monitor the effectiveness of implemented changes or fixes, e.g., follow-up surveys, performance monitoring, etc.
- Minimize the time it takes to ensure continuous improvement in the solution through regular feedback cycles, e.g., ongoing assessment, iterative development, etc.
- Minimize the time it takes to maintain a feedback repository for future reference and learning, e.g., feedback databases, lesson learned logs, etc.
- Minimize the time it takes to assess the impact of changes on overall solution performance and user satisfaction, e.g., satisfaction metrics, performance benchmarks, etc.
- Minimize the time it takes to identify trends in issues or feedback for long-term strategic improvements, e.g., pattern analysis, strategic planning, etc.
- Minimize the time it takes to facilitate open and constructive feedback channels between users and solution providers, e.g., forums, help desks, etc.
- Minimize the time it takes to integrate feedback mechanisms into the solution for real-time user insights, e.g., in-app feedback tools, analytics, etc.
- Minimize the likelihood of recurring issues due to inadequate resolution or follow-up, e.g., through rigorous testing, continuous monitoring, etc.
- Minimize the likelihood of user frustration or disengagement due to unresolved issues, e.g., by prioritizing user experience, swift problem-solving, etc.
- Minimize the likelihood of missed opportunities for improvement due to ignored or unanalyzed feedback, e.g., through systematic feedback review processes, stakeholder involvement, etc.
- Minimize the likelihood of inefficient or ineffective issue resolution processes, e.g., by streamlining resolution protocols, leveraging expert support, etc.
- Minimize the time it takes to build a culture of continuous improvement and responsiveness to feedback, e.g., reward systems, team training, leadership endorsement, etc.
Customer Success Statements (PJTBD)
- Identify and document any issues or problems with the solution, e.g., performance glitches, user complaints, etc.
- Develop and implement effective solutions to identified issues, e.g., software patches, process adjustments, etc.
- Gather comprehensive feedback from all user groups, e.g., surveys, focus groups, interviews, etc.
- Analyze feedback for actionable insights and improvements, e.g., trend analysis, user experience improvements, etc.
- Communicate issues and resolutions clearly to all stakeholders, e.g., regular updates, transparent reporting, etc.
- Coordinate with vendors or technical support for issue resolution, e.g., troubleshooting, expert consultations, etc.
- Train or retrain users based on feedback and solution updates, e.g., refresher courses, new feature demonstrations, etc.
- Implement changes or enhancements based on user feedback, e.g., feature upgrades, user interface adjustments, etc.
- Monitor the effectiveness of implemented changes or fixes, e.g., follow-up surveys, performance monitoring, etc.
- Ensure continuous improvement in the solution through regular feedback cycles, e.g., ongoing assessment, iterative development, etc.
- Maintain a feedback repository for future reference and learning, e.g., feedback databases, lesson learned logs, etc.
- Assess the impact of changes on overall solution performance and user satisfaction, e.g., satisfaction metrics, performance benchmarks, etc.
- Identify trends in issues or feedback for long-term strategic improvements, e.g., pattern analysis, strategic planning, etc.
- Facilitate open and constructive feedback channels between users and solution providers, e.g., forums, help desks, etc.
- Integrate feedback mechanisms into the solution for real-time user insights, e.g., in-app feedback tools, analytics, etc.
- Avoid recurring issues due to inadequate resolution or follow-up, e.g., through rigorous testing, continuous monitoring, etc.
- Avoid user frustration or disengagement due to unresolved issues, e.g., by prioritizing user experience, swift problem-solving, etc.
- Avoid missed opportunities for improvement due to ignored or unanalyzed feedback, e.g., through systematic feedback review processes, stakeholder involvement, etc.
- Avoid inefficient or ineffective issue resolution processes, e.g., by streamlining resolution protocols, leveraging expert support, etc.
- Build a culture of continuous improvement and responsiveness to feedback, e.g., reward systems, team training, leadership endorsement, 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]