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 recognize core concepts relevant to the solution, e.g., key principles, foundational theories, etc.
- Minimize the time it takes to understand the scope and boundaries of the solution's application, e.g., industry-specific usage, general vs. specialized functions, etc.
- Minimize the time it takes to identify specific skills or knowledge gaps related to the solution, e.g., technical skills, theoretical knowledge, etc.
- Minimize the time it takes to determine the desired proficiency level in using the solution, e.g., basic understanding, expert mastery, etc.
- Minimize the time it takes to establish clear and measurable learning goals, e.g., performance benchmarks, skill acquisition targets, etc.
- Minimize the time it takes to prioritize learning objectives based on relevance and urgency, e.g., immediate application needs, long-term skill development, etc.
- Minimize the time it takes to align learning objectives with personal or organizational goals, e.g., career advancement, operational efficiency, etc.
- Minimize the time it takes to identify resources and tools necessary for achieving learning objectives, e.g., educational materials, software tools, etc.
- Minimize the time it takes to establish a timeline for achieving each learning objective, e.g., short-term milestones, long-term goals, etc.
- Minimize the time it takes to identify potential obstacles to learning, e.g., time constraints, resource limitations, etc.
- Minimize the time it takes to assess the relevance of each learning objective to current and future roles, e.g., immediate job requirements, career progression, etc.
- Minimize the time it takes to differentiate between essential and supplementary learning objectives, e.g., core competencies, nice-to-have skills, etc.
- Minimize the time it takes to evaluate the feasibility of achieving each learning objective, e.g., availability of resources, time investment required, etc.
- Minimize the time it takes to identify external factors that may impact the learning process, e.g., industry trends, technological advancements, etc.
- Minimize the time it takes to determine the adaptability of learning objectives to different contexts, e.g., application in various job roles, scalability to larger projects, etc.
- Minimize the likelihood of overlooking interdependencies between learning objectives, e.g., sequential learning requirements, complementary skills, etc.
- Minimize the likelihood of setting unrealistic or unattainable learning objectives, e.g., overly ambitious goals, insufficient time frames, etc.
- Minimize the time it takes to identify opportunities for practical application of learning objectives, e.g., real-world projects, hands-on experiences, etc.
- Minimize the time it takes to establish criteria for evaluating the success of each learning objective, e.g., proficiency tests, practical application, etc.
- Minimize the likelihood of neglecting the need for continuous learning and adaptation of objectives, e.g., ongoing skill development, updating objectives as needed, etc.
Customer Success Statements (PJTBD)
- Recognize core concepts relevant to the solution, e.g., key principles, foundational theories, etc.
- Understand the scope and boundaries of the solution's application, e.g., industry-specific usage, general vs. specialized functions, etc.
- Identify specific skills or knowledge gaps related to the solution, e.g., technical skills, theoretical knowledge, etc.
- Determine the desired proficiency level in using the solution, e.g., basic understanding, expert mastery, etc.
- Establish clear and measurable learning goals, e.g., performance benchmarks, skill acquisition targets, etc.
- Prioritize learning objectives based on relevance and urgency, e.g., immediate application needs, long-term skill development, etc.
- Align learning objectives with personal or organizational goals, e.g., career advancement, operational efficiency, etc.
- Identify resources and tools necessary for achieving learning objectives, e.g., educational materials, software tools, etc.
- Establish a timeline for achieving each learning objective, e.g., short-term milestones, long-term goals, etc.
- Identify potential obstacles to learning, e.g., time constraints, resource limitations, etc.
- Assess the relevance of each learning objective to current and future roles, e.g., immediate job requirements, career progression, etc.
- Differentiate between essential and supplementary learning objectives, e.g., core competencies, nice-to-have skills, etc.
- Evaluate the feasibility of achieving each learning objective, e.g., availability of resources, time investment required, etc.
- Identify external factors that may impact the learning process, e.g., industry trends, technological advancements, etc.
- Determine the adaptability of learning objectives to different contexts, e.g., application in various job roles, scalability to larger projects, etc.
- Avoid overlooking interdependencies between learning objectives, e.g., sequential learning requirements, complementary skills, etc.
- Avoid setting unrealistic or unattainable learning objectives, e.g., overly ambitious goals, insufficient time frames, etc.
- Identify opportunities for practical application of learning objectives, e.g., real-world projects, hands-on experiences, etc.
- Establish criteria for evaluating the success of each learning objective, e.g., proficiency tests, practical application, etc.
- Avoid neglecting the need for continuous learning and adaptation of objectives, e.g., ongoing skill development, updating objectives as needed, 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]