/w=256,quality=90,fit=scale-down)
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)
How important is it that you… and How satisfied are you with your ability to…
- Minimize the time it takes to evaluate the technical viability of each solution, e.g., required technology, expertise, etc.
- Minimize the time it takes to analyze the financial sustainability of solutions, e.g., cost analysis, funding sources, ROI, etc.
- Minimize the time it takes to assess the operational implications of implementing solutions, e.g., workflow impact, process changes, etc.
- Minimize the time it takes to understand regulatory and compliance requirements, e.g., industry standards, legal constraints, etc.
- Minimize the time it takes to identify potential risks and mitigation strategies, e.g., market risks, operational risks, contingency plans, etc.
- Minimize the time it takes to gauge the scalability of solutions for future needs, e.g., expansion potential, adaptability, etc.
- Minimize the time it takes to evaluate the impact of solutions on stakeholders, e.g., employees, customers, partners, etc.
- Minimize the time it takes to determine resource requirements, e.g., manpower, equipment, technology, etc.
- Minimize the time it takes to assess the cultural fit of solutions within the organization, e.g., alignment with company values, employee acceptance, etc.
- Minimize the time it takes to understand the time frame for implementation and results, e.g., project timelines, milestones, etc.
- Minimize the likelihood of underestimating the complexity or challenges in implementing solutions, e.g., technical difficulties, unanticipated obstacles, etc.
- Minimize the time it takes to evaluate the environmental and social impact of solutions, e.g., sustainability, ethical considerations, etc.
- Minimize the time it takes to analyze the compatibility of solutions with existing systems and processes, e.g., integration challenges, process adaptation, etc.
- Minimize the time it takes to determine the adaptability of solutions to changing market conditions, e.g., market trends, competitor actions, etc.
- Minimize the time it takes to assess the training and support needs for implementing solutions, e.g., staff training, customer support, etc.
- Minimize the likelihood of overlooking key stakeholders in the feasibility assessment, e.g., customers, suppliers, regulatory bodies, etc.
- Minimize the time it takes to evaluate potential long-term benefits and drawbacks, e.g., strategic advantages, maintenance requirements, etc.
- Minimize the time it takes to assess the return on investment and payback period, e.g., financial returns, break-even point, etc.
- Minimize the time it takes to understand the impact of solutions on competitive advantage, e.g., market differentiation, innovation lead, etc.
- Minimize the likelihood of bias in favoring certain solutions due to familiarity or ease, e.g., status quo bias, path of least resistance, etc.
Customer Success Statements (PJTBD)
How important is it that you can quickly and accurately… and How difficult is it for you to…
- Evaluate the technical viability of each solution, e.g., required technology, expertise, etc.
- Analyze the financial sustainability of solutions, e.g., cost analysis, funding sources, ROI, etc.
- Assess the operational implications of implementing solutions, e.g., workflow impact, process changes, etc.
- Understand regulatory and compliance requirements, e.g., industry standards, legal constraints, etc.
- Identify potential risks and mitigation strategies, e.g., market risks, operational risks, contingency plans, etc.
- Gauge the scalability of solutions for future needs, e.g., expansion potential, adaptability, etc.
- Evaluate the impact of solutions on stakeholders, e.g., employees, customers, partners, etc.
- Determine resource requirements, e.g., manpower, equipment, technology, etc.
- Assess the cultural fit of solutions within the organization, e.g., alignment with company values, employee acceptance, etc.
- Understand the time frame for implementation and results, e.g., project timelines, milestones, etc.
- Avoid underestimating the complexity or challenges in implementing solutions, e.g., technical difficulties, unanticipated obstacles, etc.
- Evaluate the environmental and social impact of solutions, e.g., sustainability, ethical considerations, etc.
- Analyze the compatibility of solutions with existing systems and processes, e.g., integration challenges, process adaptation, etc.
- Determine the adaptability of solutions to changing market conditions, e.g., market trends, competitor actions, etc.
- Assess *the training and support needs for implementing solutions*, e.g., staff training, customer support, etc.
- Avoid overlooking key stakeholders in the feasibility assessment, e.g., customers, suppliers, regulatory bodies, etc.
- Evaluate potential long-term benefits and drawbacks, e.g., strategic advantages, maintenance requirements, etc.
- Assess the return on investment and payback period, e.g., financial returns, break-even point, etc.
- Understand the impact of solutions on competitive advantage, e.g., market differentiation, innovation lead, etc.
- Avoid bias in favoring certain solutions due to familiarity or ease, e.g., status quo bias, path of least resistance, 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]