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 locate the stored solution or product, e.g., in a warehouse, storage room, etc.
- Minimize the time it takes to access the stored solution or product, e.g., unlocking storage, moving other items, etc.
- Minimize the time it takes to verify the condition of the stored solution or product, e.g., checking for damage, expiration, etc.
- Minimize the likelihood of damaging the solution or product during removal, e.g., dropping, scratching, etc.
- Minimize the time it takes to transport the solution or product from storage to its intended location, e.g., using a cart, carrying by hand, etc.
- Minimize the likelihood of misplacing or losing the solution or product after removal from storage, e.g., leaving it unattended, forgetting where it was placed, etc.
- Minimize the time it takes to record the removal of the solution or product from storage, e.g., updating inventory logs, notifying relevant parties, etc.
- Minimize the likelihood of removing the wrong solution or product from storage, e.g., similar packaging, mislabeling, etc.
- Minimize the time it takes to prepare the solution or product for use after removal from storage, e.g., assembly, charging, etc.
- Minimize the likelihood of contaminating the solution or product during removal from storage, e.g., dirty hands, unclean environment, etc.
- Minimize the time it takes to confirm the solution or product is ready for use after removal from storage, e.g., functionality tests, safety checks, etc.
- Minimize the likelihood of exposing the solution or product to harmful conditions after removal from storage, e.g., extreme temperatures, moisture, etc.
- Minimize the time it takes to replace the solution or product in storage if not used immediately, e.g., re-locking storage, moving other items, etc.
- Minimize the likelihood of forgetting to replace the solution or product in storage if not used immediately, e.g., distractions, lack of reminders, etc.
- Minimize the time it takes to clean up the storage area after removal of the solution or product, e.g., disposing of packaging, reorganizing, etc.
- Minimize the likelihood of leaving the storage area in disarray after removal of the solution or product, e.g., clutter, misplaced items, etc.
- Minimize the time it takes to document any issues or concerns with the solution or product after removal from storage, e.g., reporting defects, noting discrepancies, etc.
- Minimize the likelihood of overlooking any issues or concerns with the solution or product after removal from storage, e.g., rush, lack of attention to detail, etc.
- Minimize the time it takes to communicate the removal of the solution or product from storage to relevant parties, e.g., team members, supervisors, etc.
- Minimize the likelihood of failing to communicate the removal of the solution or product from storage to relevant parties, e.g., forgetting, miscommunication, etc.
Customer Success Statements (PJTBD)
- Locate the stored solution or product, e.g., in a warehouse, storage room, etc.
- Access the stored solution or product, e.g., unlocking storage, moving other items, etc.
- Verify the condition of the stored solution or product, e.g., checking for damage, expiration, etc.
- Avoid damaging the solution or product during removal, e.g., dropping, scratching, etc.
- Transport the solution or product from storage to its intended location, e.g., using a cart, carrying by hand, etc.
- Avoid misplacing or losing the solution or product after removal from storage, e.g., leaving it unattended, forgetting where it was placed, etc.
- Record the removal of the solution or product from storage, e.g., updating inventory logs, notifying relevant parties, etc.
- Avoid removing the wrong solution or product from storage, e.g., similar packaging, mislabeling, etc.
- Prepare the solution or product for use after removal from storage, e.g., assembly, charging, etc.
- Avoid contaminating the solution or product during removal from storage, e.g., dirty hands, unclean environment, etc.
- Confirm the solution or product is ready for use after removal from storage, e.g., functionality tests, safety checks, etc.
- Avoid exposing the solution or product to harmful conditions after removal from storage, e.g., extreme temperatures, moisture, etc.
- Replace the solution or product in storage if not used immediately, e.g., re-locking storage, moving other items, etc.
- Avoid forgetting to replace the solution or product in storage if not used immediately, e.g., distractions, lack of reminders, etc.
- Clean up the storage area after removal of the solution or product, e.g., disposing of packaging, reorganizing, etc.
- Avoid leaving the storage area in disarray after removal of the solution or product, e.g., clutter, misplaced items, etc.
- Document any issues or concerns with the solution or product after removal from storage, e.g., reporting defects, noting discrepancies, etc.
- Avoid overlooking any issues or concerns with the solution or product after removal from storage, e.g., rush, lack of attention to detail, etc.
- Communicate the removal of the solution or product from storage to relevant parties, e.g., team members, supervisors, etc.
- Avoid failing to communicate the removal of the solution or product from storage to relevant parties, e.g., forgetting, miscommunication, 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]