📊 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 for organizations to assess ongoing initiatives by their current outcomes, enabling more disciplined pruning. It emphasizes judging based on results rather than sunk costs. The approach aims to prevent portfolio clutter and improve resource allocation.

A new decision-making framework called Outcome-First Decisions has been launched as open-source, offering organizations a disciplined way to evaluate whether to keep, change, or kill ongoing initiatives based solely on their current outcomes. This approach aims to address the common problem of portfolio clutter caused by projects that continue consuming resources without delivering value.

The Outcome-First Decisions framework centers around a simple yet powerful question: given the current state and outcomes of an initiative, is it worth its ongoing cost? It introduces the Worth Filter, which forces decision-makers to focus on forward-looking results rather than past investments or emotional attachments. The framework produces three verdicts: keep, change, or kill, with a bias toward making kill decisions easier to justify.

Developed by Thorsten Meyer, the framework is designed to be provider-agnostic and runs locally on owned infrastructure, ensuring privacy and cost-effectiveness. It is licensed under AGPL-3.0, emphasizing openness and community collaboration. The method aims to help organizations avoid the trap of continuing dead projects that drain focus and capital, thereby freeing capacity for more valuable work.

While the framework promotes rigorous evaluation, experts caution that outcomes can be mismeasured or gamed, and emotional biases may still influence decisions. It does not replace judgment but provides a structured approach to facilitate difficult pruning choices.

Outcome-First Decisions — Keep, Change, or Kill · Built in Public Day 8/19
Built in Public · Day 8 / 19 ThorstenMeyerAI.com · the operator portfolio
The Decision Layer · Day 08 Dispatch

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.

01 The Worth Filter
The Worth Filter
is the outcome worth the ongoing cost?
judged forward (outcome) — not backward. Ignored: sunk cost · effort spent · identity
✓ Keep
Affiliate cluster A
compounding revenue
Channel E
reach still growing
↻ Change
Product C
right problem, wrong shape
alter deliberately — don’t drift
✕ Kill
Experiment B
flat · high upkeep
Side project D
zero traction · sunk cost
3verdicts: keep · change · kill outcomesthe only input that counts AGPLopen source · local-first
02 Why stopping is the leverage
kill
the verdict everything in human nature avoids — made normal, not a failure.
forward
judge what it will produce next, not what you’ve already spent. Sunk cost is gone either way.
capacity
killing dead work reclaims the focus and capital trapped in it — the cheapest growth there is.
03 The thesis the whole series inherits
01
Local-first
Reviews run on owned compute — cheap enough to run as often as honesty requires.
02
Provider-agnostic
The reasoning isn’t welded to one model. Swap freely; no lock-in.
03
Non-developer build
A small, opinionated framework — AGPL-3.0, open so the method stays inspectable.
04
Edit by subtraction
The whole product is subtraction — killing what no longer earns its place.
04 The operator constellation
18 products · one foundation
Today: Outcome-First lit — the keep/change/kill review that closes the loop. The Decision layer is complete: validate → plan → review.
Content
DojoClaw
RoundupForge
Stenvrik
ChannelHelm
IdeaNavigator
Decision
IdeaClyst
Threlmark
Outcome-First
Platform
Grimfaste
Delvasta
Open / Reg
Glasspane
QAtrial
Markets
Polybot
TradingAgents
Defense / Intel
Argus
VigilSAR
VigilSAR-Bench
Diagnostic
World Model Readiness
Local-first · Provider-agnostic foundation

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.

ThorstenMeyerAI.com · Built in Public · Day 8 of 19 · © 2026 Thorsten Meyer

Why Outcome-First Decisions Reshape Portfolio Management

This framework offers a systematic way to improve resource allocation by encouraging organizations to regularly prune initiatives that no longer produce valuable outcomes. It addresses a common organizational blind spot: the tendency to keep projects alive due to sunk costs or emotional attachment, which can lead to inefficiencies and opportunity costs. By making kill decisions more straightforward, organizations can become more agile and focused on high-impact work, ultimately improving overall performance and strategic alignment.

Amazon

project portfolio management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

The Challenge of Maintaining Healthy Portfolios

Many organizations struggle with long tail of ongoing projects that neither succeed nor end, often due to emotional investment, sunk costs, or organizational inertia. Traditional decision-making processes tend to focus on starting new initiatives rather than systematically pruning existing ones. The concept of outcome-based evaluation has gained traction as a way to address this issue, but practical tools have been limited until now.

The release of the Outcome-First Decisions framework builds on earlier discussions about the importance of disciplined portfolio management and the need for transparent, outcome-focused evaluation methods. Its open-source nature aims to foster community adoption and iterative improvement.

“The hardest decision in any portfolio isn’t what to start. It’s what to stop.”

— Thorsten Meyer

Amazon

decision analysis tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Limitations and Risks of Outcome-First Evaluation

While the framework is designed to improve decision-making, concerns remain about accurately measuring outcomes and avoiding gaming the system. It is unclear how well the Worth Filter performs in complex or slow-start projects, and whether organizations will adopt it consistently. The framework also cannot replace the emotional and cultural factors influencing decisions, which may hinder its effectiveness.

Amazon

outcome evaluation templates

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Refinement

Organizations interested in Outcome-First Decisions can access the open-source framework on GitHub and begin applying it to their portfolios. Further development and case studies are expected to emerge, providing insights into best practices and potential pitfalls. Industry groups may also incorporate the framework into broader portfolio management standards, encouraging more disciplined pruning practices across sectors.

Amazon

resource allocation tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does Outcome-First Decisions differ from traditional portfolio reviews?

It emphasizes evaluating initiatives based solely on their current outcomes and forward-looking value, rather than past investments or emotional attachment, and promotes easier kill decisions.

Can the framework be applied to all types of projects?

While designed to be provider-agnostic, its effectiveness depends on accurately measuring outcomes, which may vary across project types. Slow-start or long-term projects may require careful outcome assessment.

Is this framework suitable for large organizations?

Yes, especially as it is designed to run locally and be integrated into existing decision cycles, helping large portfolios stay lean and focused.

What are the main challenges in implementing Outcome-First Decisions?

Accurately measuring outcomes, overcoming emotional biases, and ensuring consistent application across teams are key challenges.

Source: ThorstenMeyerAI.com

You May Also Like

EuroHPC. The compute substrate.

An analysis of EuroHPC’s compute substrate, its current capabilities, structural challenges, and implications for Europe’s AI ambitions.

A successful Japanese trial of a ramjet engine designed for Mach‑5 aircraft

Japan’s aerospace agency successfully tested a ramjet engine for Mach-5 aircraft, marking a key step toward ultra-fast hypersonic travel by the 2040s.

The calendar technicality. Why Elon Musk’s lawsuit against Sam Altman and OpenAI lost on timing, not on substance.

A California jury dismissed Musk’s lawsuit against OpenAI on procedural grounds, clearing the IPO path but leaving underlying legal issues unresolved.

Apertus. The architectural template.

Apertus, developed by Swiss research institutions, introduces an open, multilingual, compliance-focused AI model as a new European sovereign-AI blueprint.