Prepare Evaluation Criteria

Success Metrics

There are two formatting options available. The tradition 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 utilitarian 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 establish clear criteria for evaluating solutions, e.g., performance metrics, cost, scalability, etc.
Minimize the time it takes to define the priority of each evaluation criterion, e.g., essential vs. desirable features, etc.
Minimize the time it takes to develop a standardized scoring system for assessment, e.g., rating scales, weighted factors, etc.
Minimize the time it takes to identify the key performance indicators relevant to the solution, e.g., efficiency, reliability, user satisfaction, etc.
Minimize the time it takes to establish benchmarks for comparison with industry standards or competitors, e.g., market averages, best practices, etc.
Minimize the time it takes to align evaluation criteria with organizational goals and objectives, e.g., strategic alignment, business impact, etc.
Minimize the time it takes to identify regulatory and compliance requirements for the solution, e.g., legal standards, industry regulations, etc.
Minimize the time it takes to determine the importance of vendor reputation and history in the evaluation, e.g., past performance, client testimonials, etc.
Minimize the time it takes to assess the scalability and future-proofing of the solutions, e.g., upgrade paths, adaptability, etc.
Minimize the time it takes to evaluate the ease of implementation and integration of the solution, e.g., compatibility with existing systems, required training, etc.
Minimize the time it takes to consider the total cost of ownership in the evaluation, e.g., initial costs, ongoing maintenance, upgrades, etc.
Minimize the time it takes to understand the potential impact of the solution on existing workflows and processes, e.g., disruption, efficiency gains, etc.
Minimize the time it takes to assess the solution’s impact on customer experience and satisfaction, e.g., user feedback, service improvement, etc.
Minimize the time it takes to evaluate the environmental and social impacts of the solution, e.g., sustainability, ethical considerations, etc.
Minimize the time it takes to determine the flexibility of the solution to accommodate changing needs, e.g., modularity, customization, etc.
Minimize the likelihood of overlooking key evaluation criteria relevant to the solution, e.g., security features, data privacy, etc.
Minimize the likelihood of misjudging the relative importance of different criteria, e.g., prioritizing cost over quality, etc.
Minimize the likelihood of neglecting long-term implications in the evaluation process, e.g., future compatibility, obsolescence risks, etc.
Minimize the likelihood of underestimating the complexity or difficulty of solution implementation, e.g., technical challenges, resource needs, etc.
Minimize the likelihood of basing evaluation on biased or incomplete information, e.g., vendor claims, limited data sources, etc.

Customer Success Statements (PJTBD)

❓

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

Establish clear criteria for evaluating solutions, e.g., performance metrics, cost, scalability, etc.
Define the priority of each evaluation criterion, e.g., essential vs. desirable features, etc.
Develop a standardized scoring system for assessment, e.g., rating scales, weighted factors, etc.
Identify the key performance indicators relevant to the solution, e.g., efficiency, reliability, user satisfaction, etc.
Establish benchmarks for comparison with industry standards or competitors, e.g., market averages, best practices, etc.
Align evaluation criteria with organizational goals and objectives, e.g., strategic alignment, business impact, etc.
Identify regulatory and compliance requirements for the solution, e.g., legal standards, industry regulations, etc.
Determine the importance of vendor reputation and history in the evaluation, e.g., past performance, client testimonials, etc.
Assess the scalability and future-proofing of the solutions, e.g., upgrade paths, adaptability, etc.
Evaluate the ease of implementation and integration of the solution, e.g., compatibility with existing systems, required training, etc.
Consider the total cost of ownership in the evaluation, e.g., initial costs, ongoing maintenance, upgrades, etc.
Understand the potential impact of the solution on existing workflows and processes, e.g., disruption, efficiency gains, etc.
Assess the solution’s impact on customer experience and satisfaction, e.g., user feedback, service improvement, etc.
Evaluate the environmental and social impacts of the solution, e.g., sustainability, ethical considerations, etc.
Determine the flexibility of the solution to accommodate changing needs, e.g., modularity, customization, etc.
Avoid overlooking key evaluation criteria relevant to the solution, e.g., security features, data privacy, etc.
Avoid misjudging the relative importance of different criteria, e.g., prioritizing cost over quality, etc.
Avoid neglecting long-term implications in the evaluation process, e.g., future compatibility, obsolescence risks, etc.
Avoid underestimating the complexity or difficulty of solution implementation, e.g., technical challenges, resource needs, etc.
Avoid basing evaluation on biased or incomplete information, e.g., vendor claims, limited data sources, 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]