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)
- Minimize the time it takes to compile comprehensive reports on the decision's outcomes, e.g., performance data, financial results, etc.
- Minimize the time it takes to detail the decision-making process and rationale for future reference, e.g., criteria used, alternatives considered, etc.
- Minimize the time it takes to record stakeholder feedback and reactions to the decision, e.g., customer surveys, employee input, etc.
- Minimize the time it takes to document any challenges or obstacles encountered and how they were addressed, e.g., implementation issues, problem-solving steps, etc.
- Minimize the time it takes to outline the benefits and drawbacks of the chosen solution, e.g., advantages gained, limitations observed, etc.
- Minimize the time it takes to track and record the timeline and phases of decision implementation, e.g., key milestones, project stages, etc.
- Minimize the time it takes to create a repository of all relevant documents and data related to the decision, e.g., data files, reports, correspondence, etc.
- Minimize the time it takes to summarize lessons learned and insights gained for continuous improvement, e.g., best practices, areas for development, etc.
- Minimize the time it takes to detail the ongoing monitoring and evaluation mechanisms for the decision, e.g., performance metrics, review schedules, etc.
- Minimize the time it takes to record the financial implications of the decision, e.g., budget impacts, cost savings, ROI, etc.
- Minimize the time it takes to document compliance with legal and regulatory requirements, e.g., standards met, audits passed, etc.
- Minimize the time it takes to outline the decision's impact on company policies and procedures, e.g., policy updates, procedural changes, etc.
- Minimize the time it takes to detail the technology or systems used in the decision process and outcome, e.g., software tools, data platforms, etc.
- Minimize the time it takes to capture the impact of the decision on organizational culture and employee morale, e.g., staff attitudes, cultural shifts, etc.
- Minimize the time it takes to summarize the decision's effect on customer satisfaction and market position, e.g., customer feedback, competitive analysis, etc.
- Minimize the time it takes to record adjustments or changes made during the decision process, e.g., strategy pivots, plan modifications, etc.
- Minimize the time it takes to detail the contribution of each team or department in the decision-making process, e.g., roles played, responsibilities held, etc.
- Minimize the time it takes to document the external factors influencing the decision, e.g., market trends, economic conditions, etc.
- Minimize the time it takes to record the sustainability and environmental considerations of the decision, e.g., eco-friendly initiatives, green practices, etc.
- Minimize the likelihood of omitting critical information or insights in the documentation process, e.g., key data points, important observations, etc.
Customer Success Statements (PJTBD)
- Compile comprehensive reports on the decision's outcomes, e.g., performance data, financial results, etc.
- Detail the decision-making process and rationale for future reference, e.g., criteria used, alternatives considered, etc.
- Record stakeholder feedback and reactions to the decision, e.g., customer surveys, employee input, etc.
- Document any challenges or obstacles encountered and how they were addressed, e.g., implementation issues, problem-solving steps, etc.
- Outline the benefits and drawbacks of the chosen solution, e.g., advantages gained, limitations observed, etc.
- Track and record the timeline and phases of decision implementation, e.g., key milestones, project stages, etc.
- Create a repository of all relevant documents and data related to the decision, e.g., data files, reports, correspondence, etc.
- Summarize lessons learned and insights gained for continuous improvement, e.g., best practices, areas for development, etc.
- Detail the ongoing monitoring and evaluation mechanisms for the decision, e.g., performance metrics, review schedules, etc.
- Record the financial implications of the decision, e.g., budget impacts, cost savings, ROI, etc.
- Document compliance with legal and regulatory requirements, e.g., standards met, audits passed, etc.
- Outline the decision's impact on company policies and procedures, e.g., policy updates, procedural changes, etc.
- Detail *the technology orsystems used in the decision process and outcome*, e.g., software tools, data platforms, etc.
- Capture the impact of the decision on organizational culture and employee morale, e.g., staff attitudes, cultural shifts, etc.
- Summarize the decision's effect on customer satisfaction and market position, e.g., customer feedback, competitive analysis, etc.
- Record adjustments or changes made during the decision process, e.g., strategy pivots, plan modifications, etc.
- Detail the contribution of each team or department in the decision-making process, e.g., roles played, responsibilities held, etc.
- Document the external factors influencing the decision, e.g., market trends, economic conditions, etc.
- Record the sustainability and environmental considerations of the decision, e.g., eco-friendly initiatives, green practices, etc.
- Avoid omitting critical information or insights in the documentation process, e.g., key data points, important observations, 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]