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 finalize the selection based on comprehensive evaluation, e.g., cost-benefit analysis, strategic fit, etc.
- Minimize the time it takes to ensure chosen solution aligns with organizational goals and values, e.g., long-term objectives, ethical standards, etc.
- Minimize the time it takes to verify the solution's feasibility in terms of resources and capabilities, e.g., technical requirements, manpower, etc.
- Minimize the time it takes to confirm stakeholder buy-in and support for the chosen solution, e.g., employees, customers, partners, etc.
- Minimize the time it takes to validate the solution against market needs and trends, e.g., customer demand, industry developments, etc.
- Minimize the time it takes to ensure the solution's scalability for future growth and change, e.g., adaptability, expansion potential, etc.
- Minimize the time it takes to evaluate the long-term sustainability of the solution, e.g., environmental impact, social responsibility, etc.
- Minimize the time it takes to assess the solution's competitive advantage and uniqueness, e.g., market differentiation, innovation, etc.
- Minimize the time it takes to confirm compliance with regulatory and legal requirements, e.g., industry standards, legal constraints, etc.
- Minimize the time it takes to evaluate the potential risks and mitigation strategies, e.g., operational risks, market uncertainties, etc.
- Minimize the time it takes to determine the solution's integration with existing systems and processes, e.g., compatibility, implementation ease, etc.
- Minimize the time it takes to assess the impact of the solution on internal operations and culture, e.g., workflow changes, employee morale, etc.
- Minimize the time it takes to evaluate the required training and support for successful implementation, e.g., staff training, customer education, etc.
- Minimize the time it takes to forecast the return on investment and financial impact, e.g., cost savings, revenue growth, etc.
- Minimize the time it takes to assess the customer reception and satisfaction potential, e.g., user experience, customer feedback, etc.
- Minimize the time it takes to ensure the solution's adaptability to technological advancements, e.g., future tech integration, upgradability, etc.
- Minimize the time it takes to confirm the solution's alignment with market positioning and branding, e.g., brand image, market perception, etc.
- Minimize the time it takes to evaluate the solution's impact on partnerships and external relationships, e.g., supplier relations, collaborative opportunities, etc.
- Minimize the time it takes to assess the ease of monitoring and measuring the solution's effectiveness, e.g., performance metrics, success indicators, etc.
- Minimize the likelihood of selecting a solution that overlooks long-term implications for short-term gains, e.g., sacrificing sustainability for immediate results, etc.
Customer Success Statements (PJTBD)
- Finalize the selection based on comprehensive evaluation, e.g., cost-benefit analysis, strategic fit, etc.
- Ensure chosen solution aligns with organizational goals and values, e.g., long-term objectives, ethical standards, etc.
- Verify the solution's feasibility in terms of resources and capabilities, e.g., technical requirements, manpower, etc.
- Confirm stakeholder buy-in and support for the chosen solution, e.g., employees, customers, partners, etc.
- Validate the solution against market needs and trends, e.g., customer demand, industry developments, etc.
- Ensure the solution's scalability for future growth and change, e.g., adaptability, expansion potential, etc.
- Evaluate the long-term sustainability of the solution, e.g., environmental impact, social responsibility, etc.
- Assess the solution's competitive advantage and uniqueness, e.g., market differentiation, innovation, etc.
- Confirm compliance with regulatory and legal requirements, e.g., industry standards, legal constraints, etc.
- Evaluate the potential risks and mitigation strategies, e.g., operational risks, market uncertainties, etc.
- Determine the solution's integration with existing systems and processes, e.g., compatibility, implementation ease, etc.
- Assess the impact of the solution on internal operations and culture, e.g., workflow changes, employee morale, etc.
- Evaluate the required training and support for successful implementation, e.g., staff training, customer education, etc.
- Forecast *the return on investment and financial impact*, e.g., cost savings, revenue growth, etc.
- Assess the customer reception and satisfaction potential, e.g., user experience, customer feedback, etc.
- Ensure the solution's adaptability to technological advancements, e.g., future tech integration, upgradability, etc.
- Confirm the solution's alignment with market positioning and branding, e.g., brand image, market perception, etc.
- Evaluate the solution's impact on partnerships and external relationships, e.g., supplier relations, collaborative opportunities, etc.
- Assess the ease of monitoring and measuring the solution's effectiveness, e.g., performance metrics, success indicators, etc.
- Avoid selecting a solution that overlooks long-term implications for short-term gains, e.g., sacrificing sustainability for immediate results, 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]