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 forecast future storage needs, e.g., based on sales projections, production plans, etc.
- Minimize the likelihood of underestimating future storage needs, e.g., due to inaccurate forecasts, overlooked factors, etc.
- Minimize the time it takes to identify potential changes in storage requirements, e.g., new products, changes in regulations, etc.
- Minimize the likelihood of overlooking potential changes in storage requirements, e.g., due to lack of information, complacency, etc.
- Minimize the time it takes to evaluate the capacity of current storage facilities for future needs, e.g., space availability, suitability, etc.
- Minimize the likelihood of misjudging the capacity of current storage facilities for future needs, e.g., due to inaccurate measurements, overlooked constraints, etc.
- Minimize the time it takes to plan for expansion or modification of storage facilities if needed, e.g., construction plans, budgeting, etc.
- Minimize the likelihood of overlooking the need for expansion or modification of storage facilities, e.g., due to resistance to change, budget constraints, etc.
- Minimize the time it takes to identify potential alternative storage solutions for future needs, e.g., outsourcing, off-site storage, etc.
- Minimize the likelihood of overlooking potential alternative storage solutions for future needs, e.g., due to lack of information, bias, etc.
- Minimize the time it takes to evaluate the cost-effectiveness of future storage plans, e.g., cost-benefit analysis, return on investment, etc.
- Minimize the likelihood of misjudging the cost-effectiveness of future storage plans, e.g., due to inaccurate cost estimates, overlooked benefits, etc.
- Minimize the time it takes to communicate future storage plans to relevant parties, e.g., team members, management, etc.
- Minimize the likelihood of miscommunicating future storage plans to relevant parties, e.g., unclear messages, technical jargon, etc.
- Minimize the time it takes to incorporate feedback on future storage plans, e.g., revising plans, addressing concerns, etc.
- Minimize the likelihood of overlooking valuable feedback on future storage plans, e.g., due to lack of consultation, ignoring dissent, etc.
- Minimize the time it takes to finalize and approve future storage plans, e.g., decision-making process, obtaining approvals, etc.
- Minimize the likelihood of delaying the finalization and approval of future storage plans, e.g., due to indecision, bureaucratic hurdles, etc.
- Minimize the time it takes to prepare for the implementation of future storage plans, e.g., scheduling, resource allocation, etc.
- Minimize the likelihood of failing to adequately prepare for the implementation of future storage plans, e.g., due to poor planning, lack of resources, etc.
Customer Success Statements (PJTBD)
- Forecast future storage needs, e.g., based on sales projections, production plans, etc.
- Avoid underestimating future storage needs, e.g., due to inaccurate forecasts, overlooked factors, etc.
- Identify potential changes in storage requirements, e.g., new products, changes in regulations, etc.
- Avoid overlooking potential changes in storage requirements, e.g., due to lack of information, complacency, etc.
- Evaluate the capacity of current storage facilities for future needs, e.g., space availability, suitability, etc.
- Avoid misjudging the capacity of current storage facilities for future needs, e.g., due to inaccurate measurements, overlooked constraints, etc.
- Plan for expansion or modification of storage facilities if needed, e.g., construction plans, budgeting, etc.
- Avoid overlooking the need for expansion or modification of storage facilities, e.g., due to resistance to change, budget constraints, etc.
- Identify potential alternative storage solutions for future needs, e.g., outsourcing, off-site storage, etc.
- Avoid overlooking potential alternative storage solutions for future needs, e.g., due to lack of information, bias, etc.
- Evaluate the cost-effectiveness of future storage plans, e.g., cost-benefit analysis, return on investment, etc.
- Avoid misjudging the cost-effectiveness of future storage plans, e.g., due to inaccurate cost estimates, overlooked benefits, etc.
- Communicate future storage plans to relevant parties, e.g., team members, management, etc.
- Avoid miscommunicating future storage plans to relevant parties, e.g., unclear messages, technical jargon, etc.
- Incorporate feedback on future storage plans, e.g., revising plans, addressing concerns, etc.
- Avoid overlooking valuable feedback on future storage plans, e.g., due to lack of consultation, ignoring dissent, etc.
- Finalize and approve future storage plans, e.g., decision-making process, obtaining approvals, etc.
- Avoid delaying the finalization and approval of future storage plans, e.g., due to indecision, bureaucratic hurdles, etc.
- Prepare for the implementation of future storage plans, e.g., scheduling, resource allocation, etc.
- Avoid failing to adequately prepare for the implementation of future storage plans, e.g., due to poor planning, lack of resources, 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]