/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)
How important is it that you… and How satisfied are you with your ability to…
- Minimize the time it takes to assess the condition of the solution or product after storage, e.g., checking for damage, expiration, etc.
- Minimize the time it takes to determine the efficiency of the storage method, e.g., space utilization, ease of access, etc.
- Minimize the likelihood of overlooking any damage or degradation to the solution or product due to storage, e.g., rust, spoilage, etc.
- Minimize the time it takes to compare the actual condition of the solution or product with expected condition after storage, e.g., quality, functionality, etc.
- Minimize the likelihood of misjudging the effectiveness of the storage method, e.g., due to bias, lack of data, etc.
- Minimize the time it takes to gather data for evaluating storage effectiveness, e.g., condition reports, inventory logs, etc.
- Minimize the likelihood of using inaccurate or outdated data for evaluating storage effectiveness, e.g., old reports, incorrect logs, etc.
- Minimize the time it takes to analyze the data gathered for evaluating storage effectiveness, e.g., trend analysis, statistical methods, etc.
- Minimize the likelihood of making errors during the analysis of storage effectiveness data, e.g., calculation errors, misinterpretation, etc.
- Minimize the time it takes to formulate conclusions about the effectiveness of the storage method, e.g., writing reports, making presentations, etc.
- Minimize the likelihood of drawing incorrect conclusions about the effectiveness of the storage method, e.g., due to bias, lack of understanding, etc.
- Minimize the time it takes to communicate the results of the storage effectiveness evaluation to relevant parties, e.g., team members, supervisors, etc.
- Minimize the likelihood of miscommunicating the results of the storage effectiveness evaluation, e.g., unclear reports, technical jargon, etc.
- Minimize the time it takes to plan improvements to the storage method based on the evaluation results, e.g., reorganizing storage, changing storage materials, etc.
- Minimize the likelihood of overlooking potential improvements to the storage method based on the evaluation results, e.g., due to resistance to change, lack of resources, etc.
- Minimize the time it takes to implement improvements to the storage method based on the evaluation results, e.g., reorganizing storage, changing storage materials, etc.
- Minimize the likelihood of failing to implement improvements to the storage method based on the evaluation results, e.g., due to resistance to change, lack of resources, etc.
- Minimize the time it takes to monitor the effects of implemented improvements to the storage method, e.g., regular checks, data collection, etc.
- Minimize the likelihood of overlooking the effects of implemented improvements to the storage method, e.g., due to lack of monitoring, complacency, etc.
- Minimize the time it takes to adjust the improvements to the storage method based on observed effects, e.g., fine-tuning, additional changes, etc.
Customer Success Statements (PJTBD)
How important is it that you can quickly and accurately… and How difficult is it for you to…
- Assess the condition of the solution or product after storage, e.g., checking for damage, expiration, etc.
- Determine the efficiency of the storage method, e.g., space utilization, ease of access, etc.
- Avoid overlooking any damage or degradation to the solution or product due to storage, e.g., rust, spoilage, etc.
- Compare the actual condition of the solution or product with expected condition after storage, e.g., quality, functionality, etc.
- Avoid misjudging the effectiveness of the storage method, e.g., due to bias, lack of data, etc.
- Gather data for evaluating storage effectiveness, e.g., condition reports, inventory logs, etc.
- Avoid using inaccurate or outdated data for evaluating storage effectiveness, e.g., old reports, incorrect logs, etc.
- Analyze the data gathered for evaluating storage effectiveness, e.g., trend analysis, statistical methods, etc.
- Avoid making errors during the analysis of storage effectiveness data, e.g., calculation errors, misinterpretation, etc.
- Formulate conclusions about the effectiveness of the storage method, e.g., writing reports, making presentations, etc.
- Avoid drawing incorrect conclusions about the effectiveness of the storage method, e.g., due to bias, lack of understanding, etc.
- Communicate the results of the storage effectiveness evaluation to relevant parties, e.g., team members, supervisors, etc.
- Avoid miscommunicating the results of the storage effectiveness evaluation, e.g., unclear reports, technical jargon, etc.
- Plan improvements to the storage method based on the evaluation results, e.g., reorganizing storage, changing storage materials, etc.
- Avoid overlooking potential improvements to the storage method based on the evaluation results, e.g., due to resistance to change, lack of resources, etc.
- Implement improvements to the storage method based on the evaluation results, e.g., reorganizing storage, changing storage materials, etc.
- Avoid failing to implement improvements to the storage method based on the evaluation results, e.g., due to resistance to change, lack of resources, etc.
- Monitor the effects of implemented improvements to the storage method, e.g., regular checks, data collection, etc.
- Avoid overlooking the effects of implemented improvements to the storage method, e.g., due to lack of monitoring, complacency, etc.
- Adjust the improvements to the storage method based on observed effects, e.g., fine-tuning, additional changes, 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]