📊 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 helps organizations evaluate whether to keep, change, or kill initiatives based solely on current outcomes. It aims to improve portfolio efficiency by encouraging disciplined pruning.

A new framework called Outcome-First Decisions has been introduced to help organizations determine whether to keep, modify, or terminate initiatives based on their current outcomes, rather than sunk costs or emotional attachment. This approach aims to address the persistent problem of organizations maintaining underperforming projects and commitments.

Outcome-First Decisions is a decision-making framework built around a simple question: what outcome is this initiative producing right now, and is it worth its ongoing cost? It introduces the Worth Filter, which forces evaluators to focus on forward-looking results rather than past investments or effort. The framework provides three verdicts: keep, change, or kill, with a bias toward making kill decisions easier. It is open source under the AGPL-3.0 license and designed to be provider-agnostic and local-first, allowing frequent reviews without additional costs.

The framework aims to close the decision loop in portfolio management by providing a final step that routinely prunes underperforming or dead projects, preventing portfolio silt-up. Its creators argue that this discipline is often neglected because emotional and sunk-cost biases hinder rational termination decisions. The tool is intended to be used as a routine part of portfolio review, helping organizations reclaim capacity and improve overall efficiency.

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 addresses a common organizational challenge: the tendency to continue supporting initiatives that no longer produce valuable outcomes. By focusing on current results, it encourages disciplined pruning, freeing resources for more effective projects. Implementing Outcome-First can lead to more agile organizations, reduce waste, and improve strategic focus. However, its success depends on accurate outcome measurement and organizational willingness to make tough termination decisions.

Amazon

portfolio review decision software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

The Problem of Unstopped Initiatives in Organizations

Many organizations accumulate a long tail of ongoing projects and commitments that neither succeed nor are actively terminated. These ‘zombie’ initiatives drain attention, capital, and opportunity, often justified by sunk costs, identity, or effort-justification. Traditional decision-making processes tend to focus on past investments, making it difficult to kill projects, even when they underperform. The Outcome-First framework seeks to address this by shifting the focus to present and future outcomes, providing a disciplined method for portfolio pruning.

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

— Thorsten Meyer, creator of Outcome-First

Amazon

outcome-based project evaluation tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Challenges in Measuring and Acting on Outcomes

It remains unclear how organizations will accurately measure outcomes, especially for long-term or slow-developing initiatives. There is also concern that the framework could be misused to justify premature killing or to ignore slow-starting but valuable projects. The effectiveness of Outcome-First depends heavily on honest outcome assessment and organizational courage to act on difficult decisions.

Amazon

project kill decision templates

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Testing

Organizations interested in Outcome-First are encouraged to review the open-source implementation on GitHub and pilot it within their portfolios. Further development may include refining outcome metrics and integrating the framework into existing portfolio management processes. Broader adoption will depend on case studies demonstrating its impact on reducing waste and improving decision discipline.

Amazon

portfolio management decision framework

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does Outcome-First differ from traditional portfolio reviews?

Unlike traditional reviews that often consider past investments and effort, Outcome-First focuses solely on current and projected outcomes to decide whether initiatives should continue, change, or be terminated.

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

The primary risks include mismeasuring outcomes, premature killing of slow-starting but valuable projects, and organizational reluctance to make hard termination decisions due to emotional or cultural biases.

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

While designed to be provider-agnostic and flexible, its effectiveness depends on the ability to measure outcomes meaningfully. It may be more suitable for ongoing initiatives with clear, measurable results.

Is Outcome-First open source?

Yes, the framework is available under the AGPL-3.0 license on GitHub, allowing organizations to adapt and implement it freely.

Source: ThorstenMeyerAI.com

You May Also Like

The Nordics: Protect the Worker, Not the Job

An analysis of how Nordic countries prioritize worker security over job preservation, fostering resilience amid automation and economic shifts.

The Quiet Audit: 55–75% of Your Week Is on Thin Ice. Here’s Which Part.

A detailed analysis reveals that 55–75% of knowledge workers’ weekly time is on thin ice, mostly in theatre, commodity, or on-the-line tasks. Here’s what to know.

Morale is so bad at Mark Zuckerberg’s Meta even the company’s own CTO admits it’s ‘probably the worst it’s ever been’

Meta’s CTO publicly acknowledges declining employee morale, highlighting internal concerns amid ongoing company challenges.

The United Kingdom: The Pragmatist’s Hedge

The UK adopts a flexible, moderate model post-Brexit, balancing welfare, labour market, and AI regulation while keeping options open.