Outcome-First Decisions: Keep, Change, or Kill

📊 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 is a framework that guides organizations to evaluate ongoing initiatives based on current outcomes, leading to decisions to keep, change, or kill. It aims to improve portfolio health by focusing on results rather than sunk costs.

The Outcome-First Decisions framework is gaining attention as a practical approach for organizations to evaluate and prune their project portfolios based on current outcomes rather than past investments or emotional attachment.

The framework, developed by Thorsten Meyer, emphasizes judging initiatives solely on their present and future results, not on past effort or sunk costs. It introduces the Worth Filter, a decision mechanism that categorizes projects into three verdicts: keep, change, or kill, with a bias toward making kill decisions straightforward. This process is designed to prevent organizations from continuing unproductive initiatives that drain resources and attention.

Built as an open-source tool under the AGPL-3.0 license, it operates locally and provider-agnostically, allowing organizations to regularly review their portfolios without additional costs. The process is positioned as the final step in a portfolio management cycle, closing the loop that often leads to accumulation of dead or unproductive projects. While the framework aims to promote discipline in stopping initiatives that no longer produce value, it also recognizes the risks of misjudging outcomes, premature killing, and emotional resistance to ending projects.

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 matters because it offers a structured method to address the common problem of portfolio bloat, where organizations continue supporting projects that no longer deliver value. By focusing on current outcomes, it encourages more disciplined resource allocation, freeing capacity for new initiatives or improvements. The bias toward making kill decisions easier aims to prevent organizations from being trapped by sunk cost fallacies, ultimately leading to more efficient and adaptive operations.

Amazon

portfolio management decision software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background of Outcome-First Decision Framework

Traditional portfolio management often struggles with the ‘continuation bias,’ where projects persist due to past investments, effort justification, or emotional attachment. Thorsten Meyer’s Outcome-First Decisions framework addresses this issue by shifting the evaluation focus to current and projected results. It builds on existing principles of lean management and decision science, emphasizing the importance of stopping unproductive initiatives to optimize overall portfolio health. The framework is part of a broader movement toward outcome-oriented management practices that seek to maximize value and reduce waste.

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

— Thorsten Meyer

Amazon

project evaluation tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Uncertainties Around Outcome Measurement and Application

It remains unclear how organizations will accurately measure and interpret outcomes, especially for slow-start or long-term initiatives. There is also concern about potential misuse of the framework to prematurely kill projects that require more time to demonstrate value. Additionally, the framework’s effectiveness relies heavily on honest and consistent outcome evaluation, which can be challenging in complex or subjective contexts.

Amazon

outcome-based project prioritization software

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 adopting Outcome-First Decisions are likely to pilot the framework within specific portfolios, refine outcome metrics, and develop internal guidelines to mitigate risks of misjudgment. Further development may include integrating the framework with existing project management tools and establishing regular review cycles. Broader adoption will depend on case studies demonstrating its impact on portfolio efficiency and resource optimization.

Amazon

portfolio pruning 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?

Traditional reviews often focus on past investments, effort, or emotional attachment, whereas Outcome-First Decisions evaluate ongoing initiatives based solely on current and projected results, encouraging decisive action to stop unproductive projects.

What are the main risks of using this framework?

The key risks include mismeasuring outcomes, prematurely killing projects that are still valuable, and relying on subjective judgment. Proper outcome metrics and cautious application are essential to mitigate these risks.

Can Outcome-First Decisions be applied to all types of projects?

While designed to be provider-agnostic and flexible, its effectiveness depends on the ability to measure outcomes accurately. Complex or long-term projects may require careful adaptation of outcome metrics and review processes.

Is this framework suitable for small organizations or only for large portfolios?

The framework can be scaled to fit organizations of different sizes. Smaller organizations may find it easier to implement frequent reviews, while larger ones might integrate it into existing portfolio management systems.

Source: ThorstenMeyerAI.com

You May Also Like

Change-order risk detector for landscaping contractors

A new change-order risk detector for landscaping contractors is set for initial testing, aiming to improve margin control amid project scope uncertainties.

The Nordics: Protect the Worker, Not the Job

An analysis of the Nordic model’s focus on safeguarding workers through flexible labor policies and social support, contrasting with traditional job protection strategies.

Incident postmortem builder for managed service providers

A new incident postmortem builder tailored for small managed service providers is being tested to streamline post-incident reporting and client communication.

Board packet generator for HOA managers

A new board packet generator for HOA managers is in testing, aiming to streamline monthly meeting preparations and improve transparency for small associations.