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 necessary modifications based on feedback and results, e.g., customer reviews, performance metrics, etc.
- Minimize the time it takes to evaluate the impact of proposed changes on the overall solution, e.g., cost implications, timeline adjustments, etc.
- Minimize the time it takes to assess the feasibility of integrating new features or improvements, e.g., technical capability, resource availability, etc.
- Minimize the time it takes to update stakeholders on changes and gather their input, e.g., employees, customers, partners, etc.
- Minimize the time it takes to ensure modifications align with original goals and objectives, e.g., strategic fit, target outcomes, etc.
- Minimize the time it takes to re-evaluate the solution's impact on user experience and satisfaction, e.g., usability, customer feedback, etc.
- Minimize the time it takes to monitor the ongoing performance and effectiveness of the solution, e.g., key performance indicators, success metrics, etc.
- Minimize the time it takes to incorporate new technologies or innovations into the solution, e.g., latest advancements, market trends, etc.
- Minimize the time it takes to assess the scalability and future-proofing of modified solutions, e.g., growth potential, adaptability, etc.
- Minimize the time it takes to evaluate compliance with regulatory and legal standards post-modification, e.g., industry regulations, legal requirements, etc.
- Minimize the time it takes to identify potential risks associated with the changes, e.g., operational risks, market risks, etc.
- Minimize the time it takes to assess the resource implications of the adaptations, e.g., budget adjustments, additional manpower, etc.
- Minimize the time it takes to evaluate the need for additional training or support due to changes, e.g., staff training, customer education, etc.
- Minimize the time it takes to ensure modified solutions maintain or enhance competitive advantage, e.g., market positioning, differentiation, etc.
- Minimize the time it takes to monitor the long-term sustainability and environmental impact of adaptations, e.g., eco-friendliness, social responsibility, etc.
- Minimize the time it takes to assess the impact of changes on internal operations and culture, e.g., workflow alterations, employee morale, etc.
- Minimize the time it takes to evaluate the adaptability of the solution to future market or industry changes, e.g., emerging trends, shifting demands, etc.
- Minimize the time it takes to update and refine risk mitigation strategies following adaptations, e.g., contingency planning, risk assessment, etc.
- Minimize the time it takes to ensure ongoing alignment with customer needs and expectations, e.g., market feedback, customer surveys, etc.
- Minimize the likelihood of overcomplicating the solution or deviating from core objectives through excessive changes, e.g., feature creep, goal misalignment, etc.
Customer Success Statements (PJTBD)
- Identify necessary modifications based on feedback and results, e.g., customer reviews, performance metrics, etc.
- Evaluate the impact of proposed changes on the overall solution, e.g., cost implications, timeline adjustments, etc.
- Assess the feasibility of integrating new features or improvements, e.g., technical capability, resource availability, etc.
- Update stakeholders on changes and gather their input, e.g., employees, customers, partners, etc.
- Ensure modifications align with original goals and objectives, e.g., strategic fit, target outcomes, etc.
- Re-evaluate the solution's impact on user experience and satisfaction, e.g., usability, customer feedback, etc.
- Monitor the ongoing performance and effectiveness of the solution, e.g., key performance indicators, success metrics, etc.
- Incorporate new technologies or innovations into the solution, e.g., latest advancements, market trends, etc.
- Assess the scalability and future-proofing of modified solutions, e.g., growth potential, adaptability, etc.
- Evaluate compliance with regulatory and legal standards post-modification, e.g., industry regulations, legal requirements, etc.
- Identify potential risks associated with the changes, e.g., operational risks, market risks, etc.
- Assess the resource implications of the adaptations, e.g., budget adjustments, additional manpower, etc.
- Evaluate the need for additional training or support due to changes, e.g., staff training, customer education, etc.
- Ensure modified solutions maintain or enhance competitive advantage, e.g., market positioning, differentiation, etc.
- Monitor the long-term sustainability and environmental impact of adaptations, e.g., eco-friendliness, social responsibility, etc.
- Assess the impact of changes on internal operations and culture, e.g., workflow alterations, employee morale, etc.
- Evaluate the adaptability of the solution to future market or industry changes, e.g., emerging trends, shifting demands, etc.
- Update and refine risk mitigation strategies following adaptations, e.g., contingency planning, risk assessment, etc.
- Ensure ongoing alignment with customer needs and expectations, e.g., market feedback, customer surveys, etc.
- Avoid overcomplicating the solution or deviating from core objectives through excessive changes, e.g., feature creep, goal misalignment, 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]