You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 4: Strategy for One — Portfolio Triage and the Kill Decision #

When the decision matrix forces kills out of your portfolio, your first instinct will be to game the matrix to keep everything alive. I want to name that move before you make it, because it is a specific, predictable, deeply human response to a forced kill, and it is the entire reason most engineer-founders end up with portfolios instead of products. The gaming will sound like reasonable hedging. Run it on the worked example and listen to the voices: "ShelfLife might catch fire if I just spend a weekend on it." "CartTrends has the best long-term TAM if I think about it right." "EchoScribe is too far along to kill." Each sentence is a hedge against the discomfort of committing, and the hedge is also the reason none of the four is shipping at the rate one of them could ship if you killed two and concentrated. In the worked portfolio, ShelfLife and CartTrends do not survive an honest pass — both sit at "status unclear," and the unclear status is itself the diagnosis. If you knew, you would have written it down. Unclear status is a kill decision you haven't admitted to yourself yet.

Here is the unflattering truth at full volume: engineer-founders accumulate pipeline products as a hedge against the discomfort of committing to one. A four-product pipeline is not an asset; it is an emotional risk-management strategy that produces the same shape of failure across the entire portfolio. If product one doesn't work out, product two is the fallback; if product two stalls, product three is "still there." The diversification feels safe and is, in fact, the leak. The math does not work — one engineer plus a day job plus family plus recovery cannot ship four products — and the math has never worked. The hedge produces the appearance of optionality and the reality of nothing shipping. If you are the engineer with 3-5 side projects and no paying customers, this paragraph is about you, and you already knew that before I wrote it.

There is a disposition underneath the portfolio worth naming with respect before naming its cost. You are probably a starter — very good at beginning things, with the repos to prove it — and the capacity to start is real and rare. The shadow of a strong starting capacity is a finishing capacity that's weak in proportion to the start rate. Project the current trajectory forward: if you keep starting at this pace and finishing at this pace, the portfolio in three years has twice as many products in various states of partial completion, none at the standard you want.

The cure is not "make better roadmaps." It is the strategy-as-capacity-planning frame, which is the engineer's lens that makes M4 click: you have sized servers, calculated connection pools, reasoned about queue throughput under load. Strategy for one is the same discipline applied to your own hours, channels, and attention — given finite inputs, what is the highest expected-value-per-hour path to a paying customer for each product? The matrix forces the comparison. The comparison forces the kill. Most founder-strategy content avoids this clean computation because in the corporate context the capacity is shared and the constraints are soft. Yours are hard, and the math is honest.

The two earlier drafts of this module disagreed in an instructive way. One trusted the matrix: fill the cells honestly and the kills fall out for legible reasons, not arbitrary ones. The other said the matrix is almost decorative — you already know which product belongs in the KILL column, you knew before the module started, and the work is making yourself face a decision that was already obvious. I think both are true and the order matters: the knowing comes first, the matrix is how you make the knowing undeniable, and the second pass — after you catch yourself adjusting cells on the first — is where the honest answer lands. One more prediction from the second draft worth carrying: when you finally write a product into the KILL column, you will feel relief, and the relief is the proof the decision was overdue. The comparison hurts precisely because you have been spending equal-feeling time on products with unequal expected value, and the not-comparing has been more expensive than the hurt.

I cannot make the kill decision for you. I can hold the matrix, predict the gaming attempts, and refuse to let "pause" substitute for "kill" — M13 is where the kill actually ships, with a README update, a post-mortem, and a reallocated time budget. What M4 must produce is the decision and the kill criterion for the survivors: the threshold below which you'd stop. Committing to build is easy. Committing to a stopping condition is the discipline.

Conclusion #

The matrix is honest if you let it be honest. Some of your products do not deserve continued effort against your real capacity, and the ones with "unclear" status are the diagnosis wearing a label. Gaming the matrix to keep everything alive is the predictable failure mode and produces a portfolio of half-built things. Concentration is the strategy; the relief you feel at the kill decision is the evidence; M13 is where the decision becomes an act.

Predictions #

  • Your first matrix pass will keep every product alive by adjusting the cells. The honest second pass will force at least one kill, more likely two.
  • The kills will be the products whose status you'd describe with the word "unclear" or "paused." The matrix will produce this answer for legible reasons, not arbitrary ones.
  • You'll feel a small grief about the kills, and underneath it a distinct relief. The grief is sunk cost protesting; the relief is the signal the decision was overdue.
  • The kill-criterion field for the surviving products will be the hardest to fill in honestly. You'll want to leave it "TBD." Write a number anyway and revise quarterly.
  • You'll be tempted to reclassify a kill as a "pause." Pause is denial dressed as optionality; M13 calls this out and forces the formal retirement.
  • Within a month of the triage, a new product idea will arrive and feel like inspiration. Apply the test: would you put a current survivor on the kill list to make room for it? If no, write the idea down and keep building.