/w=256,quality=90,fit=scale-down)
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 confirm the solution's adherence to industry standards and regulations, e.g., ISO certifications, GDPR compliance, etc.
- Minimize the time it takes to ensure compatibility with existing systems and infrastructure, e.g., software integration, hardware requirements, etc.
- Minimize the time it takes to verify the solution meets legal and ethical guidelines, e.g., licensing requirements, data privacy laws, etc.
- Minimize the time it takes to check for alignment with internal policies and procedures, e.g., corporate governance, HR policies, etc.
- Minimize the time it takes to validate that the solution adheres to security protocols and standards, e.g., encryption methods, cybersecurity measures, etc.
- Minimize the time it takes to ensure that the solution is accessible and inclusive, e.g., ADA compliance, multilingual support, etc.
- Minimize the time it takes to assess the solution's environmental impact and sustainability, e.g., carbon footprint, energy efficiency, etc.
- Minimize the time it takes to evaluate the solution's compatibility with future technology trends and updates, e.g., scalability, adaptability, etc.
- Minimize the time it takes to confirm the solution aligns with customer and stakeholder expectations, e.g., user experience, service levels, etc.
- Minimize the time it takes to verify the solution's alignment with organizational values and ethics, e.g., social responsibility, transparency, etc.
- Minimize the time it takes to ensure that the solution complies with international standards and laws, e.g., trade regulations, export controls, etc.
- Minimize the time it takes to validate interoperability with external systems and platforms, e.g., API integrations, cross-platform compatibility, etc.
- Minimize the time it takes to check for compatibility with specific industry requirements or certifications, e.g., healthcare regulations, financial compliance, etc.
- Minimize the time it takes to confirm the solution's compliance with data handling and storage regulations, e.g., cloud storage laws, data retention policies, etc.
- Minimize the time it takes to ensure the solution meets global accessibility and usability standards, e.g., WCAG guidelines, user-friendly interfaces, etc.
- Minimize the time it takes to verify solution alignment with risk management and mitigation strategies, e.g., disaster recovery plans, business continuity, etc.
- Minimize the likelihood of non-compliance with critical regulatory requirements, e.g., financial penalties, legal actions, etc.
- Minimize the likelihood of incompatibility issues causing operational disruptions, e.g., system downtime, process inefficiencies, etc.
- Minimize the likelihood of security vulnerabilities or breaches due to compliance oversights, e.g., data leaks, unauthorized access, etc.
- Minimize the time it takes to finalize documentation and proof of compliance and compatibility, e.g., audit reports, certification records, etc.
Customer Success Statements (PJTBD)
How important is it that you can quickly and accurately… and How difficult is it for you to…
- Confirm the solution's adherence to industry standards and regulations, e.g., ISO certifications, GDPR compliance, etc.
- Ensure compatibility with existing systems and infrastructure, e.g., software integration, hardware requirements, etc.
- Verify the solution meets legal and ethical guidelines, e.g., licensing requirements, data privacy laws, etc.
- Check for alignment with internal policies and procedures, e.g., corporate governance, HR policies, etc.
- Validate that the solution adheres to security protocols and standards, e.g., encryption methods, cybersecurity measures, etc.
- Ensure that the solution is accessible and inclusive, e.g., ADA compliance, multilingual support, etc.
- Assess the solution's environmental impact and sustainability, e.g., carbon footprint, energy efficiency, etc.
- Evaluate the solution's compatibility with future technology trends and updates, e.g., scalability, adaptability, etc.
- Confirm the solution aligns with customer and stakeholder expectations, e.g., user experience, service levels, etc.
- Verify the solution's alignment with organizational values and ethics, e.g., social responsibility, transparency, etc.
- Ensure that the solution complies with international standards and laws, e.g., trade regulations, export controls, etc.
- Validate interoperability with external systems and platforms, e.g., API integrations, cross-platform compatibility, etc.
- Check for compatibility with specific industry requirements or certifications, e.g., healthcare regulations, financial compliance, etc.
- Confirm the solution's compliance with data handling and storage regulations, e.g., cloud storage laws, data retention policies, etc.
- Ensure the solution meets global accessibility and usability standards, e.g., WCAG guidelines, user-friendly interfaces, etc.
- Verify solution alignment with risk management and mitigation strategies, e.g., disaster recovery plans, business continuity, etc.
- Avoid non-compliance with critical regulatory requirements, e.g., financial penalties, legal actions, etc.
- Avoid incompatibility issues causing operational disruptions, e.g., system downtime, process inefficiencies, etc.
- Avoid security vulnerabilities or breaches due to compliance oversights, e.g., data leaks, unauthorized access, etc.
- Finalize documentation and proof of compliance and compatibility, e.g., audit reports, certification records, 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]