📊 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 new framework that helps organizations evaluate ongoing initiatives based on current outcomes, recommending whether to keep, change, or kill them. It aims to improve portfolio efficiency by promoting disciplined pruning.

The Outcome-First Decisions framework was introduced as a method for organizations to evaluate ongoing initiatives based solely on their current outcomes, rather than past investments or emotional attachment. This approach aims to help operators make clearer decisions about what to continue, modify, or terminate, thereby improving overall portfolio health and capacity.

The framework, developed by Thorsten Meyer, centers on a decision-making process called the Worth Filter, which assesses whether an initiative’s current outcome justifies its ongoing cost. It returns one of three verdicts: keep, change, or kill. The core principle is to judge initiatives by their present performance, not past efforts, encouraging disciplined pruning of unproductive projects. The framework is open source under the AGPL-3.0 license and designed to be provider-agnostic and local-first, enabling frequent, cost-free reviews. It aims to address the common problem of long tail projects that consume resources without delivering value, often defended by sunk costs and emotional attachment.

While the framework promotes objective decision-making, experts warn that outcomes can be mismeasured or gamed, and that the tool cannot replace human judgment regarding slow-starting but valuable initiatives or emotional resistance to killing projects. Nonetheless, it is seen as a critical step toward establishing a sustainable discipline of stopping efforts that no longer produce value.

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 tackles the often-overlooked challenge of stopping initiatives that drain resources without delivering value. By focusing on current outcomes, organizations can free capacity, reduce maintenance costs, and redirect efforts toward more promising projects. It institutionalizes the difficult discipline of pruning, which is essential for long-term agility and efficiency, especially in complex portfolios where emotional and sunk-cost biases tend to keep unproductive initiatives alive.

Mastering Project Portfolio Management: A Systems Approach to Achieving Strategic Objectives

Mastering Project Portfolio Management: A Systems Approach to Achieving Strategic Objectives

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

The Need for Disciplined Portfolio Pruning

Many organizations struggle with long tail projects that persist despite underperformance, often justified by past investments or organizational identity. Traditional decision-making processes tend to favor continuation over termination, leading to resource drain and reduced capacity for innovation. The Outcome-First framework responds to this by providing a structured, objective method for evaluating ongoing efforts based on their current outcomes, not historical effort. This approach aligns with recent industry discussions emphasizing lean management and operational discipline.

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

— Thorsten Meyer

Limitations and Risks of Outcome-Based Judgments

It remains unclear how accurately organizations can measure and interpret outcomes, especially for slow-starting or complex initiatives. There is a risk that outcome metrics can be gamed or misrepresented, leading to premature termination of valuable efforts. Additionally, the framework cannot replace human judgment regarding emotional resistance or strategic considerations. The effectiveness of the approach depends heavily on honest, consistent outcome measurement and organizational discipline, which are challenging to maintain.

Next Steps for Adopting Outcome-First Decision Frameworks

Organizations interested in this approach should consider piloting the framework within specific portfolios to evaluate its practicality and impact. Further development may include integrating outcome measurement tools and training decision-makers to interpret results objectively. Broader adoption will likely depend on success stories and refinement of metrics, with ongoing emphasis on balancing objective evaluation with strategic judgment.

Key Questions

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

It focuses solely on current outcomes to determine whether initiatives should continue, change, or be terminated, rather than relying on past investments or emotional attachments.

Can this framework be applied to all types of projects?

While designed to be provider-agnostic and flexible, its effectiveness depends on the ability to measure relevant outcomes accurately, which may vary by project type.

What are the main risks of using Outcome-First Decisions?

The primary risks include outcome mismeasurement, premature killing of slow-starting but valuable initiatives, and organizational resistance due to emotional or strategic reasons.

Is the framework open source?

Yes, it is released under the AGPL-3.0 license, allowing organizations to adapt and implement it freely.

What is the next step for organizations interested in this approach?

They should consider piloting the framework within specific portfolios, refining outcome metrics, and training decision-makers on its use.

Source: ThorstenMeyerAI.com

You May Also Like

The Delegation Ladder: The Four Agentic Loops, And What Each One Lets You Stop Doing

An analysis of the four agentic loops in AI design, explaining what each enables and how they influence automation and control.

The Question No To-Do App Can Answer

A new productivity tool, Threlmark, introduces a unique approach to prioritizing work, but it cannot answer the fundamental question of what to do next.

The European Union: Rules First, Cushion Always

The EU is enforcing strict AI regulations and social protections, shaping the future of work and economic gains through rules rather than ownership.

IdeaClyst: The Engine That Decides What’s Worth Building

IdeaClyst, a new idea engine, automatically generates validated product ideas by analyzing roadmaps and web opportunities, helping founders prioritize valuable work.