📊 Full opportunity report: Outcome-First Decisions: Keep, Change, or Kill on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Outcome-First Decisions introduces a framework that guides organizations to evaluate and decide whether to keep, change, or kill initiatives based on current outcomes. It emphasizes pruning to optimize portfolios and reduce wasted effort.
Thorsten Meyer has released the Outcome-First Decisions framework as open-source software, providing organizations with a structured method to evaluate ongoing initiatives based solely on current outcomes to decide whether to keep, change, or kill them.
The framework introduces the Worth Filter, a decision mechanism that assesses initiatives by their present results rather than past investments or effort. This approach aims to address the common problem of organizations maintaining projects that no longer deliver value, often due to emotional or sunk cost biases.
Outcome-First Decisions is designed to be provider-agnostic and runs on local compute, making it accessible for regular portfolio reviews without additional cost. Its open-source license (AGPL-3.0) ensures transparency and encourages community development.
The framework emphasizes that the decision to kill is often the most difficult but necessary to free up capacity for more valuable work. It also seeks to prevent premature termination of slow-start projects by focusing on outcomes rather than effort or time invested.
Outcome-First Decisions — keep, change, or kill
The hardest decision isn’t what to start — it’s what to stop. Judge every initiative by the outcome it produces now, not the effort already spent.
Independent commentary, produced with AI assistance under human editorial oversight. The views are the author’s own and may change. Outcome-First Decisions is open source under AGPL-3.0, provided “as is” without warranty; see the repository LICENSE. The framework’s verdicts are reasoning aids based on the inputs given and may be wrong — decision support, not decisions; verify independently before acting. Product and company names are trademarks of their respective owners; mention does not imply endorsement.
Implications for Portfolio Management and Organizational Efficiency
This framework could significantly improve how organizations manage their portfolios by promoting disciplined pruning. By making the decision to stop projects based on current outcomes, organizations can free resources, reduce focus dilution, and accelerate progress on truly valuable initiatives. It addresses a key challenge in operational management: stopping the wrong projects often costs more than starting new ones.
Adopting Outcome-First Decisions may lead to cultural shifts, encouraging more honest assessments and reducing emotional attachments to ongoing projects. However, the framework’s success depends on accurate outcome measurement and honest application, which remains a challenge.
Left Holding: A Field Guide to Private Equity-Owned Software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The Challenge of Continuing Dead Projects in Organizations
Many organizations accumulate a long tail of ongoing projects and initiatives that neither succeed nor are formally terminated. These ‘zombie’ projects consume attention, resources, and opportunity cost, often justified by sunk costs, identity, or effort justification. Traditional decision-making processes tend to favor continuation due to emotional biases and reluctance to admit failure.
Thorsten Meyer’s framework builds on the recognized need for systematic pruning, emphasizing outcome-based evaluation over effort or past investment. It aligns with broader management trends advocating for leaner, more adaptable portfolios.
“The hardest decision in any portfolio isn’t what to start. It’s what to stop.”
— Thorsten Meyer
Limitations of Outcome-Based Evaluation and Potential Risks
While the framework emphasizes outcomes, it relies heavily on accurate measurement, which can be subjective or gamed. There is a risk of premature killing of slow-start projects that may eventually yield high value. Additionally, the framework does not provide judgment or courage to make these tough decisions, leaving emotional or political factors unaddressed.
It is not yet clear how well organizations will adopt and integrate this approach into their existing decision processes or how it will perform in complex, multi-stakeholder environments.
Next Steps for Adoption and Validation in Organizations
Organizations interested in Outcome-First Decisions are expected to pilot the framework in their portfolio reviews and share feedback on its effectiveness. Community-driven development and case studies will likely emerge to refine best practices.
Further validation and research may explore how outcome measurement impacts decision quality and how to mitigate biases or inaccuracies in evaluation.
Key Questions
How does Outcome-First Decisions differ from traditional portfolio reviews?
It focuses exclusively on current outcomes to decide whether initiatives should continue, change, or be terminated, rather than relying on past effort, investment, or emotional attachment.
Can this framework help prevent organizations from prematurely killing promising projects?
Yes, by emphasizing outcome measurement, it encourages careful assessment of slow-start projects before making termination decisions, reducing the risk of premature killing.
Is the framework suitable for all types of projects and organizations?
It is designed to be provider-agnostic and flexible, but its effectiveness depends on the quality of outcome metrics and honest application within specific organizational contexts.
Will implementing this framework require significant cultural change?
Potentially, as it promotes disciplined pruning and honest assessment, which may challenge existing biases and emotional attachments in decision-making processes.
Source: ThorstenMeyerAI.com
