Monitor Solution Implementation

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 identify potential issues during solution implementation, e.g., software bugs, hardware malfunctions, etc.
Minimize the time it takes to track the progress of solution implementation, e.g., milestones reached, tasks completed, etc.
Minimize the likelihood of missing critical updates during solution implementation, e.g., software updates, hardware upgrades, etc.
Minimize the time it takes to communicate with all stakeholders about the status of solution implementation, e.g., project managers, clients, team members, etc.
Minimize the likelihood of miscommunication leading to errors during solution implementation, e.g., incorrect task execution, missed deadlines, etc.
Minimize the time it takes to resolve any issues that arise during solution implementation, e.g., software bugs, hardware malfunctions, etc.
Minimize the likelihood of overlooking important details during solution implementation, e.g., specific client requirements, regulatory compliance, etc.
Minimize the time it takes to verify the functionality of the implemented solution, e.g., system tests, user acceptance tests, etc.
Minimize the likelihood of implementation delays affecting the project timeline, e.g., late deliveries, extended testing periods, etc.
Minimize the time it takes to document all aspects of the solution implementation, e.g., configuration details, user manuals, etc.
Minimize the likelihood of unplanned downtime during solution implementation, e.g., system crashes, network outages, etc.
Minimize the time it takes to coordinate with different teams involved in the solution implementation, e.g., development team, testing team, etc.
Minimize the likelihood of conflicts between different solutions being implemented, e.g., software incompatibility, hardware conflicts, etc.
Minimize the time it takes to train end-users on the implemented solution, e.g., software training, hardware usage, etc.
Minimize the likelihood of security breaches during solution implementation, e.g., data leaks, unauthorized access, etc.
Minimize the time it takes to evaluate the performance of the implemented solution, e.g., speed tests, load tests, etc.
Minimize the likelihood of budget overruns during solution implementation, e.g., unexpected costs, resource overuse, etc.
Minimize the time it takes to gather feedback from end-users about the implemented solution, e.g., surveys, interviews, etc.
Minimize the likelihood of user dissatisfaction with the implemented solution, e.g., poor usability, lack of features, etc.
Minimize the time it takes to make necessary adjustments to the implemented solution based on feedback, e.g., software patches, hardware upgrades, etc.

Customer Success Statements (PJTBD)

❓

How important is it that you can quickly and accurately… and How difficult is it for you to…

Identify potential issues during solution implementation, e.g., software bugs, hardware malfunctions, etc.
Track the progress of solution implementation, e.g., milestones reached, tasks completed, etc.
Avoid missing critical updates during solution implementation, e.g., software updates, hardware upgrades, etc.
Communicate with all stakeholders about the status of solution implementation, e.g., project managers, clients, team members, etc.
Avoid miscommunication leading to errors during solution implementation, e.g., incorrect task execution, missed deadlines, etc.
Resolve any issues that arise during solution implementation, e.g., software bugs, hardware malfunctions, etc.
Avoid overlooking important details during solution implementation, e.g., specific client requirements, regulatory compliance, etc.
Verify the functionality of the implemented solution, e.g., system tests, user acceptance tests, etc.
Avoid implementation delays affecting the project timeline, e.g., late deliveries, extended testing periods, etc.
Document all aspects of the solution implementation, e.g., configuration details, user manuals, etc.
Avoid unplanned downtime during solution implementation, e.g., system crashes, network outages, etc.
Coordinate with different teams involved in the solution implementation, e.g., development team, testing team, etc.
Avoid conflicts between different solutions being implemented, e.g., software incompatibility, hardware conflicts, etc.
Train end-users on the implemented solution, e.g., software training, hardware usage, etc.
Avoid security breaches during solution implementation, e.g., data leaks, unauthorized access, etc.
Evaluate the performance of the implemented solution, e.g., speed tests, load tests, etc.
Avoid budget overruns during solution implementation, e.g., unexpected costs, resource overuse, etc.
Gather feedback from end-users about the implemented solution, e.g., surveys, interviews, etc.
Avoid user dissatisfaction with the implemented solution, e.g., poor usability, lack of features, etc.
Make necessary adjustments to the implemented solution based on feedback, e.g., software patches, hardware upgrades, 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]