AIThis post was created with the assistance of artificial intelligence (AI).

📊 Full opportunity report: Outcome-First Decisions: Keep, Change, or Kill on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

TL;DR

The Outcome-First Decisions framework offers a structured way to evaluate ongoing initiatives based on current outcomes, guiding whether to keep, change, or kill. It aims to improve portfolio health by emphasizing results over sunk costs.

The Outcome-First Decisions framework has been introduced as a method to help organizations evaluate ongoing projects based solely on their current outcomes, rather than past investments or emotional attachments. This approach aims to improve portfolio management by encouraging deliberate pruning of underperforming initiatives, thereby freeing capacity for new opportunities. You can learn more about Outcome-First Decisions.

The framework, developed by Thorsten Meyer, centers on a simple question: given the current state, is the outcome worth its ongoing cost? It returns one of three verdicts: keep, change, or kill. The process is supported by a mechanism called the Worth Filter, which eliminates backward-looking biases such as sunk costs and emotional attachment, focusing instead on forward-looking results.

Designed to be provider-agnostic and local-first, the framework runs on owned compute, allowing frequent reviews without additional cost. Its open-source license (AGPL-3.0) ensures transparency and encourages community-driven development. The approach aims to address the common problem of long tail projects that drain attention and resources without producing meaningful results, often defended by sunk costs or identity.

While the framework promotes straightforward decision-making, experts caution that outcomes can be mismeasured or gamed, and that emotional resistance remains a challenge. Nonetheless, it formalizes the critical discipline of stopping, which is often overlooked but crucial for maintaining a healthy portfolio.

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 provides organizations with a clear, repeatable process to prune ineffective projects and focus on high-impact initiatives. By emphasizing results over effort and sunk costs, it helps prevent resource drain and accelerates strategic agility. Adopting Outcome-First Decisions can lead to more efficient use of capital, better focus, and a culture that values honest evaluation over emotional attachment.

Solutions for Agile Governance in the Enterprise (SAGE): Agile Project, Program, and Portfolio Management for Development of Hardware and Software Products

Solutions for Agile Governance in the Enterprise (SAGE): Agile Project, Program, and Portfolio Management for Development of Hardware and Software Products

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

The Challenge of Managing Long-Tail Projects and Commitments

Many organizations accumulate a long tail of projects and commitments that continue consuming resources without delivering proportional value. These initiatives are often kept alive due to sunk costs, organizational identity, or effort justification, creating hidden costs in focus, capital, and opportunity. Traditional decision-making processes tend to favor starting new initiatives rather than stopping existing ones, leading to portfolio bloat and reduced agility. For a deeper understanding, see the article on Outcome-First Decisions.

The concept of Outcome-First Decisions builds on the need for a disciplined approach to pruning, aligning decision-making with current results rather than past investments. It reflects a broader shift toward outcome-oriented management, emphasizing the importance of regular review and decisive action.

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

— Thorsten Meyer

Accounting: Tools for Business Decision Making

Accounting: Tools for Business Decision Making

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Potential Risks of Outcome-First Decision Framework

It is not yet clear how organizations will accurately measure outcomes, especially for slow-start projects or those with intangible benefits. There is also concern that the framework could lead to premature termination of initiatives that require longer time horizons to succeed. Additionally, emotional resistance and cultural factors may limit adoption, and the framework cannot fully eliminate subjective judgment or emotional bias.

UNDISRUPT - Artificial Intelligence led Digital Transformation: 5 stages to decode: Business Outcomes, Data, Culture, Boardroom & Risk

UNDISRUPT – Artificial Intelligence led Digital Transformation: 5 stages to decode: Business Outcomes, Data, Culture, Boardroom & Risk

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Implementing Outcome-First Decisions

Organizations interested in this approach should pilot the framework within select portfolios to evaluate its effectiveness and refine their outcome metrics. More guidance can be found in Outcome-First Decisions. Developing clear, measurable outcomes and training decision-makers will be critical. Over time, broader adoption could formalize regular review cycles focused on outcome-based pruning, ultimately integrating the framework into standard portfolio management practices.

Evaluation Planning Book of Templates

Evaluation Planning Book of Templates

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 project evaluation?

It focuses exclusively on current outcomes and future results, rather than past investments or effort, enabling more objective and decisive pruning of initiatives.

Can this framework be applied to all types of projects?

While designed to be provider-agnostic, its effectiveness depends on the ability to measure outcomes clearly. Slow-start or intangible projects may require tailored metrics.

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

Measuring outcomes accurately, overcoming emotional resistance, and avoiding premature termination of valuable initiatives are key challenges.

Is the framework open source?

Yes, it is available under the AGPL-3.0 license on GitHub, encouraging community contributions and transparency.

Source: ThorstenMeyerAI.com

You May Also Like

Agent Skill To Force Docs In ASD-STE100 Simplified Technical English

A new agent skill now allows users to force documentation compliance within ASD-STE100 Simplified Technical English, enhancing control and consistency.

Saturation. The ten-essay framework, closed.

The ten-essay European sovereign-LLM framework has reached a comprehensive saturation point, with no further structural insights expected before August 2026.

Alibaba to ban employees from using Anthropic’s coding tool, source says

Alibaba has instructed employees to stop using Anthropic’s coding AI, citing internal policy changes. The move impacts AI tool adoption within the company.

AI Model Ownership Demystified: Tinker, Forge, Vs Frontier Tuning

An analysis of three approaches to AI model ownership—Tinker, Forge, and Frontier Tuning—highlighting their differences, benefits, and implications for regulated industries.