/w=256,quality=90,fit=scale-down)
Success Metrics
There are two formatting options available. The traditional 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 awkward 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 relevant new technologies and methods, e.g., industry publications, technology blogs, etc.
- Minimize the time it takes to understand the capabilities and limitations of new technologies and methods, e.g., technical specifications, case studies, etc.
- Minimize the likelihood of overlooking potentially beneficial technologies or methods, e.g., emerging trends, niche solutions, etc.
- Minimize the time it takes to compare new technologies and methods with current ones, e.g., performance benchmarks, cost analysis, etc.
- Minimize the likelihood of adopting technologies or methods that are not compatible with existing systems, e.g., software incompatibilities, hardware requirements, etc.
- Minimize the time it takes to evaluate the potential impact of new technologies and methods on the solution, e.g., improved performance, enhanced features, etc.
- Minimize the likelihood of investing in technologies or methods that become quickly outdated, e.g., short-lived trends, unsupported technologies, etc.
- Minimize the time it takes to plan for the integration of new technologies and methods into the solution, e.g., project planning, resource allocation, etc.
- Minimize the likelihood of encountering resistance to change when introducing new technologies or methods, e.g., user acceptance, stakeholder buy-in, etc.
- Minimize the time it takes to monitor the performance and effectiveness of newly adopted technologies and methods, e.g., performance metrics, user feedback, etc.
Customer Success Statements (PJTBD)
- Identify relevant new technologies and methods, e.g., industry publications, technology blogs, etc.
- Understand the capabilities and limitations of new technologies and methods, e.g., technical specifications, case studies, etc.
- Avoid overlooking potentially beneficial technologies or methods, e.g., emerging trends, niche solutions, etc.
- Compare new technologies and methods with current ones, e.g., performance benchmarks, cost analysis, etc.
- Avoid adopting technologies or methods that are not compatible with existing systems, e.g., software incompatibilities, hardware requirements, etc.
- Evaluate the potential impact of new technologies and methods on the solution, e.g., improved performance, enhanced features, etc.
- Avoid investing in technologies or methods that become quickly outdated, e.g., short-lived trends, unsupported technologies, etc.
- Plan for the integration of new technologies and methods into the solution, e.g., project planning, resource allocation, etc.
- Avoid encountering resistance to change when introducing new technologies or methods, e.g., user acceptance, stakeholder buy-in, etc.
- Monitor the performance and effectiveness of newly adopted technologies and methods, e.g., performance metrics, user feedback, 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]