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 review the repair report details, e.g., service performed, parts replaced, etc.
- Minimize the time it takes to confirm the repair outcomes match the initial complaint, e.g., functionality restored, error messages resolved, etc.
- Minimize the time it takes to verify warranty coverage for the repairs, e.g., parts warranty, labor warranty, etc.
- Minimize the time it takes to understand the future maintenance recommendations, e.g., upcoming service, preventive measures, etc.
- Minimize the time it takes to assess the cost breakdown of the repair, e.g., parts cost, labor cost, additional fees, etc.
- Minimize the time it takes to identify any discrepancies in the repair report, e.g., unauthorized services, incorrect parts listed, etc.
- Minimize the time it takes to confirm the repair timeline was adhered to, e.g., promised completion date, delays, etc.
- Minimize the time it takes to evaluate the quality of the repair work, e.g., craftsmanship, functionality, etc.
- Minimize the time it takes to determine if any follow-up service is required, e.g., additional repairs, adjustments, etc.
- Minimize the time it takes to understand the terms of service provided, e.g., guarantees, warranties, etc.
- Minimize the time it takes to confirm all initially reported problems have been addressed, e.g., operational issues, performance concerns, etc.
- Minimize the time it takes to verify the use of genuine or specified replacement parts, e.g., manufacturer-approved, aftermarket, etc.
- Minimize the time it takes to ensure the service report is easily accessible for future reference, e.g., digital copy, printed copy, etc.
- Minimize the time it takes to confirm the service provider's contact information is correct and easily accessible, e.g., phone number, email, etc.
- Minimize the time it takes to ensure clarity on any service limitations or exclusions mentioned in the report, e.g., conditions not covered, etc.
- Minimize the time it takes to determine the availability of a service follow-up or feedback mechanism, e.g., customer survey, direct contact, etc.
- Minimize the time it takes to understand any safety precautions or advisories issued post-repair, e.g., operational guidelines, usage restrictions, etc.
- Minimize the time it takes to ensure all personal data and settings are intact post-repair, e.g., device settings, saved preferences, etc.
- Minimize the time it takes to confirm the repair has not affected any unrelated system or component, e.g., secondary functions, peripheral devices, etc.
- Minimize the time it takes to ensure the repair documentation includes a detailed explanation of the problem and solution, e.g., diagnostic findings, repair actions taken, etc.
Customer Success Statements (PJTBD)
- Review the repair report details, e.g., service performed, parts replaced, etc.
- Confirm the repair outcomes match the initial complaint, e.g., functionality restored, error messages resolved, etc.
- Verify warranty coverage for the repairs, e.g., parts warranty, labor warranty, etc.
- Understand the future maintenance recommendations, e.g., upcoming service, preventive measures, etc.
- Assess the cost breakdown of the repair, e.g., parts cost, labor cost, additional fees, etc.
- Identify any discrepancies in the repair report, e.g., unauthorized services, incorrect parts listed, etc.
- Confirm the repair timeline was adhered to, e.g., promised completion date, delays, etc.
- Evaluate the quality of the repair work, e.g., craftsmanship, functionality, etc.
- Determine if any follow-up service is required, e.g., additional repairs, adjustments, etc.
- Understand the terms of service provided, e.g., guarantees, warranties, etc.
- Confirm all initially reported problems have been addressed, e.g., operational issues, performance concerns, etc.
- Verify the use of genuine or specified replacement parts, e.g., manufacturer-approved, aftermarket, etc.
- Ensure the service report is easily accessible for future reference, e.g., digital copy, printed copy, etc.
- Confirm the service provider's contact information is correct and easily accessible, e.g., phone number, email, etc.
- Ensure clarity on any service limitations or exclusions mentioned in the report, e.g., conditions not covered, etc.
- Determine the availability of a service follow-up or feedback mechanism, e.g., customer survey, direct contact, etc.
- Understand any safety precautions or advisories issued post-repair, e.g., operational guidelines, usage restrictions, etc.
- Ensure all personal data and settings are intact post-repair, e.g., device settings, saved preferences, etc.
- Confirm the repair has not affected any unrelated system or component, e.g., secondary functions, peripheral devices, etc.
- Ensure the repair documentation includes a detailed explanation of the problem and solution, e.g., diagnostic findings, repair actions taken, 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]