/w=256,quality=90,fit=scale-down)
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 the technical requirements of the new solution, e.g., system specifications, software compatibility, etc.
- Minimize the time it takes to confirm the new solution's compatibility with existing infrastructure, e.g., hardware, software, network, etc.
- Minimize the likelihood of encountering compatibility issues during the implementation process, e.g., software conflicts, hardware incompatibility, etc.
- Minimize the time it takes to understand the operational requirements of the new solution, e.g., power consumption, environmental conditions, etc.
- Minimize the time it takes to verify the new solution's compliance with industry standards and regulations, e.g., safety standards, data privacy regulations, etc.
- Minimize the likelihood of overlooking key compatibility factors during the verification process, e.g., system requirements, operational conditions, etc.
- Minimize the time it takes to confirm the new solution's compatibility with existing workflows and processes, e.g., production processes, data workflows, etc.
- Minimize the time it takes to determine the impact of the new solution on existing system performance, e.g., system speed, data processing, etc.
- Minimize the likelihood of experiencing performance degradation due to the new solution, e.g., slower processing speed, increased system load, etc.
- Minimize the time it takes to verify the new solution's interoperability with other systems and applications, e.g., data exchange, system integration, etc.
- Minimize the likelihood of encountering interoperability issues with the new solution, e.g., data exchange problems, integration challenges, etc.
- Minimize the time it takes to confirm the new solution's compatibility with user roles and permissions, e.g., access control, user privileges, etc.
- Minimize the likelihood of encountering user access issues due to the new solution, e.g., permission conflicts, access control problems, etc.
- Minimize the time it takes to verify the new solution's compatibility with existing data formats and structures, e.g., data types, database schemas, etc.
- Minimize the likelihood of experiencing data compatibility issues with the new solution, e.g., data corruption, data loss, etc.
- Minimize the time it takes to confirm the new solution's compatibility with existing security measures, e.g., firewalls, encryption, etc.
- Minimize the likelihood of compromising system security due to the new solution, e.g., security vulnerabilities, data breaches, etc.
- Minimize the time it takes to verify the new solution's compatibility with existing backup and recovery procedures, e.g., data backup, system recovery, etc.
- Minimize the likelihood of disrupting backup and recovery procedures due to the new solution, e.g., backup failures, recovery issues, etc.
- Minimize the time it takes to confirm the new solution's compatibility with existing maintenance and support procedures, e.g., system updates, technical support, etc.
Customer Success Statements (PJTBD)
How important is it that you can quickly and accurately… and How difficult is it for you to…
- Identify the technical requirements of the new solution, e.g., system specifications, software compatibility, etc.
- Confirm the new solution's compatibility with existing infrastructure, e.g., hardware, software, network, etc.
- Avoid encountering compatibility issues during the implementation process, e.g., software conflicts, hardware incompatibility, etc.
- Understand the operational requirements of the new solution, e.g., power consumption, environmental conditions, etc.
- Verify the new solution's compliance with industry standards and regulations, e.g., safety standards, data privacy regulations, etc.
- Avoid overlooking key compatibility factors during the verification process, e.g., system requirements, operational conditions, etc.
- Confirm the new solution's compatibility with existing workflows and processes, e.g., production processes, data workflows, etc.
- Determine the impact of the new solution on existing system performance, e.g., system speed, data processing, etc.
- Avoid experiencing performance degradation due to the new solution, e.g., slower processing speed, increased system load, etc.
- Verify the new solution's interoperability with other systems and applications, e.g., data exchange, system integration, etc.
- Avoid encountering interoperability issues with the new solution, e.g., data exchange problems, integration challenges, etc.
- Confirm the new solution's compatibility with user roles and permissions, e.g., access control, user privileges, etc.
- Avoid encountering user access issues due to the new solution, e.g., permission conflicts, access control problems, etc.
- Verify the new solution's compatibility with existing data formats and structures, e.g., data types, database schemas, etc.
- Avoid experiencing data compatibility issues with the new solution, e.g., data corruption, data loss, etc.
- Confirm the new solution's compatibility with existing security measures, e.g., firewalls, encryption, etc.
- Avoid compromising system security due to the new solution, e.g., security vulnerabilities, data breaches, etc.
- Verify the new solution's compatibility with existing backup and recovery procedures, e.g., data backup, system recovery, etc.
- Avoid disrupting backup and recovery procedures due to the new solution, e.g., backup failures, recovery issues, etc.
- Confirm the new solution's compatibility with existing maintenance and support procedures, e.g., system updates, technical support, 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]