/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 potential compatibility issues between solutions, e.g., software versions, hardware requirements, etc.
- Minimize the time it takes to understand the technical specifications of each solution, e.g., operating system requirements, memory usage, etc.
- Minimize the time it takes to evaluate the interoperability of the solutions, e.g., data exchange, communication protocols, etc.
- Minimize the likelihood of overlooking critical compatibility factors, e.g., network bandwidth, storage capacity, etc.
- Minimize the time it takes to determine the impact of each solution on the overall system performance, e.g., processing speed, response time, etc.
- Minimize the time it takes to assess the scalability of the combined solutions, e.g., user load, data volume, etc.
- Minimize the likelihood of encountering unexpected integration challenges, e.g., conflicting configurations, incompatible formats, etc.
- Minimize the time it takes to verify the compliance of each solution with industry standards, e.g., security protocols, data privacy regulations, etc.
- Minimize the time it takes to evaluate the need for additional resources or infrastructure to support the solutions, e.g., servers, databases, etc.
- Minimize the likelihood of disrupting existing workflows due to incompatible solutions, e.g., user interfaces, process steps, etc.
- Minimize the time it takes to determine the potential risks associated with integrating the solutions, e.g., data loss, system downtime, etc.
- Minimize the time it takes to assess the potential benefits of the integrated solutions, e.g., increased efficiency, improved functionality, etc.
- Minimize the likelihood of overlooking potential synergies between the solutions, e.g., shared data, complementary features, etc.
- Minimize the time it takes to evaluate the feasibility of customizing solutions to enhance compatibility, e.g., modifying settings, developing plugins, etc.
- Minimize the likelihood of underestimating the complexity of the integration process, e.g., time required, technical expertise needed, etc.
- Minimize the time it takes to identify potential conflicts between the solutions' user requirements, e.g., access rights, user roles, etc.
- Minimize the time it takes to assess the impact of the solutions on the system's security posture, e.g., vulnerabilities, attack vectors, etc.
- Minimize the likelihood of failing to consider future upgrades or updates of the solutions, e.g., backward compatibility, support lifecycle, etc.
- Minimize the time it takes to evaluate the potential cost implications of integrating the solutions, e.g., licensing fees, maintenance costs, etc.
- Minimize the likelihood of overlooking the need for user training or support for the integrated solutions, e.g., user manuals, helpdesk 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 potential compatibility issues between solutions, e.g., software versions, hardware requirements, etc.
- Understand the technical specifications of each solution, e.g., operating system requirements, memory usage, etc.
- Evaluate the interoperability of the solutions, e.g., data exchange, communication protocols, etc.
- Avoid overlooking critical compatibility factors, e.g., network bandwidth, storage capacity, etc.
- Determine the impact of each solution on the overall system performance, e.g., processing speed, response time, etc.
- Assess the scalability of the combined solutions, e.g., user load, data volume, etc.
- Avoid encountering unexpected integration challenges, e.g., conflicting configurations, incompatible formats, etc.
- Verify the compliance of each solution with industry standards, e.g., security protocols, data privacy regulations, etc.
- Evaluate the need for additional resources or infrastructure to support the solutions, e.g., servers, databases, etc.
- Avoid disrupting existing workflows due to incompatible solutions, e.g., user interfaces, process steps, etc.
- Determine the potential risks associated with integrating the solutions, e.g., data loss, system downtime, etc.
- Assess the potential benefits of the integrated solutions, e.g., increased efficiency, improved functionality, etc.
- Avoid overlooking potential synergies between the solutions, e.g., shared data, complementary features, etc.
- Evaluate the feasibility of customizing solutions to enhance compatibility, e.g., modifying settings, developing plugins, etc.
- Avoid underestimating the complexity of the integration process, e.g., time required, technical expertise needed, etc.
- Identify potential conflicts between the solutions' user requirements, e.g., access rights, user roles, etc.
- Assess the impact of the solutions on the system's security posture, e.g., vulnerabilities, attack vectors, etc.
- Avoid failing to consider future upgrades or updates of the solutions, e.g., backward compatibility, support lifecycle, etc.
- Evaluate the potential cost implications of integrating the solutions, e.g., licensing fees, maintenance costs, etc.
- Avoid overlooking the need for user training or support for the integrated solutions, e.g., user manuals, helpdesk 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]