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 track and confirm the delivery status of the purchased solution, e.g., shipping updates, delivery confirmations, etc.
- Minimize the time it takes to ensure the solution is implemented according to the planned schedule and specifications, e.g., installation milestones, compliance with design plans, etc.
- Minimize the time it takes to verify the solution's integration with existing systems and processes, e.g., software compatibility checks, workflow integration, etc.
- Minimize the time it takes to conduct initial quality assurance and functionality testing of the solution, e.g., performance tests, user acceptance tests, etc.
- Minimize the time it takes to identify and address any issues or discrepancies during implementation, e.g., technical faults, performance gaps, etc.
- Minimize the time it takes to coordinate with vendors or suppliers for any necessary adjustments or support, e.g., technical assistance, parts replacement, etc.
- Minimize the time it takes to train internal teams on the use and maintenance of the new solution, e.g., operational training, troubleshooting guides, etc.
- Minimize the time it takes to collect and analyze feedback from users during the initial phase of implementation, e.g., satisfaction surveys, usage data, etc.
- Minimize the time it takes to establish monitoring protocols for ongoing performance and maintenance of the solution, e.g., regular check-ups, performance metrics, etc.
- Minimize the time it takes to document all aspects of the delivery and implementation process, e.g., implementation reports, change logs, etc.
- Minimize the time it takes to assess the impact of the new solution on current business operations, e.g., productivity analysis, workflow efficiency, etc.
- Minimize the time it takes to adjust and refine the implementation process based on initial outcomes and feedback, e.g., process optimization, feature enhancements, etc.
- Minimize the time it takes to ensure compliance with all relevant health, safety, and environmental regulations during implementation, e.g., safety audits, environmental impact assessments, etc.
- Minimize the time it takes to facilitate effective communication between all parties involved in the implementation, e.g., project teams, stakeholders, vendors, etc.
- Minimize the time it takes to establish a clear escalation process for addressing implementation challenges, e.g., issue reporting, resolution pathways, etc.
- Minimize the likelihood of delays or disruptions in the delivery and implementation process, e.g., supply chain issues, scheduling conflicts, etc.
- Minimize the likelihood of implementation failure due to inadequate planning or resource allocation, e.g., insufficient staffing, lack of technical expertise, etc.
- Minimize the likelihood of user resistance or lack of adoption of the new solution, e.g., through user involvement, effective communication, etc.
- Minimize the likelihood of cost overruns or budget mismanagement during implementation, e.g., unforeseen expenses, inaccurate cost estimates, etc.
- Minimize the time it takes to achieve full operational functionality and integration of the new solution, e.g., system stabilization, full-scale deployment, etc.
Customer Success Statements (PJTBD)
- Track and confirm the delivery status of the purchased solution, e.g., shipping updates, delivery confirmations, etc.
- Ensure the solution is implemented according to the planned schedule and specifications, e.g., installation milestones, compliance with design plans, etc.
- Verify the solution's integration with existing systems and processes, e.g., software compatibility checks, workflow integration, etc.
- Conduct initial quality assurance and functionality testing of the solution, e.g., performance tests, user acceptance tests, etc.
- Identify and address any issues or discrepancies during implementation, e.g., technical faults, performance gaps, etc.
- Coordinate with vendors or suppliers for any necessary adjustments or support, e.g., technical assistance, parts replacement, etc.
- Train internal teams on the use and maintenance of the new solution, e.g., operational training, troubleshooting guides, etc.
- Collect and analyze feedback from users during the initial phase of implementation, e.g., satisfaction surveys, usage data, etc.
- Establish monitoring protocols for ongoing performance and maintenance of the solution, e.g., regular check-ups, performance metrics, etc.
- Document all aspects of the delivery and implementation process, e.g., implementation reports, change logs, etc.
- Assess the impact of the new solution on current business operations, e.g., productivity analysis, workflow efficiency, etc.
- Adjust and refine the implementation process based on initial outcomes and feedback, e.g., process optimization, feature enhancements, etc.
- Ensure compliance with all relevant health, safety, and environmental regulations during implementation, e.g., safety audits, environmental impact assessments, etc.
- Facilitate effective communication between all parties involved in the implementation, e.g., project teams, stakeholders, vendors, etc.
- Establish a clear escalation process for addressing implementation challenges, e.g., issue reporting, resolution pathways, etc.
- Avoid delays or disruptions in the delivery and implementation process, e.g., supply chain issues, scheduling conflicts, etc.
- Avoid implementation failure due to inadequate planning or resource allocation, e.g., insufficient staffing, lack of technical expertise, etc.
- Avoid user resistance or lack of adoption of the new solution, e.g., through user involvement, effective communication, etc.
- Avoid cost overruns or budget mismanagement during implementation, e.g., unforeseen expenses, inaccurate cost estimates, etc.
- Achieve full operational functionality and integration of the new solution, e.g., system stabilization, full-scale deployment, 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]