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 evaluate the pros and cons of each potential solution, e.g., cost-benefit analysis, feature comparison, etc.
- Minimize the time it takes to identify viable solutions based on predefined criteria, e.g., budget constraints, technical requirements, etc.
- Minimize the time it takes to research and gather information about potential solutions, e.g., market reviews, user testimonials, etc.
- Minimize the time it takes to compare potential solutions against current market trends and forecasts, e.g., emerging technologies, industry shifts, etc.
- Minimize the time it takes to assess the scalability and future-proofing of each solution, e.g., upgrade paths, compatibility with future technologies, etc.
- Minimize the time it takes to determine the ease of integration of each solution with existing systems, e.g., software compatibility, hardware requirements, etc.
- Minimize the time it takes to analyze the potential ROI of each solution, e.g., cost savings, productivity gains, etc.
- Minimize the time it takes to evaluate the vendor reliability and support for each solution, e.g., customer service, maintenance agreements, etc.
- Minimize the time it takes to assess the user-friendliness and training requirements of each solution, e.g., learning curve, user interface, etc.
- Minimize the time it takes to understand the compliance and regulatory implications of each solution, e.g., data privacy laws, industry standards, etc.
- Minimize the time it takes to estimate the implementation time and resources required for each solution, e.g., installation time, staffing needs, etc.
- Minimize the time it takes to validate the compatibility of each solution with organizational goals and values, e.g., sustainability targets, corporate ethics, etc.
- Minimize the time it takes to consider the flexibility and customization options of each solution, e.g., modular features, add-ons, etc.
- Minimize the time it takes to forecast the long-term maintenance and operational costs of each solution, e.g., repair fees, software updates, etc.
- Minimize the time it takes to evaluate the security features and risks associated with each solution, e.g., data encryption, vulnerability assessments, etc.
- Minimize the time it takes to assess the potential impact of each solution on team productivity and morale, e.g., ease of use, workflow changes, etc.
- Minimize the likelihood of selecting a solution that fails to meet key requirements, e.g., performance benchmarks, capacity limits, etc.
- Minimize the likelihood of overlooking critical factors in the decision-making process, e.g., hidden costs, support limitations, etc.
- Minimize the likelihood of biased or uninformed decision-making in the selection process, e.g., vendor influence, incomplete data, etc.
- Minimize the time it takes to finalize the selection of the most suitable solution, e.g., decision-making meetings, approval processes, etc.
Customer Success Statements (PJTBD)
- Evaluate the pros and cons of each potential solution, e.g., cost-benefit analysis, feature comparison, etc.
- Identify viable solutions based on predefined criteria, e.g., budget constraints, technical requirements, etc.
- Research and gather information about potential solutions, e.g., market reviews, user testimonials, etc.
- Compare potential solutions against current market trends and forecasts, e.g., emerging technologies, industry shifts, etc.
- Assess the scalability and future-proofing of each solution, e.g., upgrade paths, compatibility with future technologies, etc.
- Determine the ease of integration of each solution with existing systems, e.g., software compatibility, hardware requirements, etc.
- Analyze the potential ROI of each solution, e.g., cost savings, productivity gains, etc.
- Evaluate the vendor reliability and support for each solution, e.g., customer service, maintenance agreements, etc.
- Assess the user-friendliness and training requirements of each solution, e.g., learning curve, user interface, etc.
- Understand the compliance and regulatory implications of each solution, e.g., data privacy laws, industry standards, etc.
- Estimate the implementation time and resources required for each solution, e.g., installation time, staffing needs, etc.
- Validate the compatibility of each solution with organizational goals and values, e.g., sustainability targets, corporate ethics, etc.
- Consider the flexibility and customization options of each solution, e.g., modular features, add-ons, etc.
- Forecast the long-term maintenance and operational costs of each solution, e.g., repair fees, software updates, etc.
- Evaluate the security features and risks associated with each solution, e.g., data encryption, vulnerability assessments, etc.
- Assess the potential impact of each solution on team productivity and morale, e.g., ease of use, workflow changes, etc.
- Avoid selecting a solution that fails to meet key requirements, e.g., performance benchmarks, capacity limits, etc.
- Avoid overlooking critical factors in the decision-making process, e.g., hidden costs, support limitations, etc.
- Avoid biased or uninformed decision-making in the selection process, e.g., vendor influence, incomplete data, etc.
- Finalize the selection of the most suitable solution, e.g., decision-making meetings, approval processes, 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]