What Operator's Memo Is (and Isn't)

Most product writing on the internet is tactics dressed as wisdom

This site is a body of work, not a blog. It exists to argue positions in public and let the arguments compound over time, which is the opposite of what most product writing on the internet is built to do.

Go look at what circulates. “5 lessons I learned shipping my first feature.” “10 frameworks every PM should know.” “The one metric that changed how I think about growth.” Every one of these is engineered for a scroll, not a shelf. They are optimized to be liked, not to be linked back to in three years. They collect reactions and then evaporate, because they were never meant to hold weight.

The problem is not that the advice is wrong. Some of it is fine. The problem is that it is unfalsifiable. “Talk to your customers” is true and useless. “Cut scope” is true and useless. Tactics without a position behind them are just anecdotes with a numbered list stapled on. You read them, nod, and change nothing, because there was nothing there to disagree with.

A tactic tells you what worked once. A position tells you what you believe and why, which means it can be tested, attacked, and proven wrong. That last part matters. A body of work you can’t be wrong about isn’t a body of work. It’s a mood board.

Operators need doctrine, not another framework

The people this is written for already have too many frameworks. They have RICE and ICE and the Kano model and a Miro board with 14 2x2s on it. What they don’t have is doctrine — a set of positions on the hard calls that a framework can’t make for them.

Doctrine is what you fall back on when the framework runs out. When the data is ambiguous, when the org is fighting, when the roadmap has 50 things on it and the CEO wants to know which one ships first. No 2x2 answers that. A position does.

My position: you ship 50, let 49 fail, and stop pretending you can pick the one winner in advance. You can disagree with that. Good. Now we have something to argue about.

Doctrine is portable across contexts in a way tactics are not. The tactic that grew NerdWallet’s insurance funnel does not transfer to a developer platform. The position underneath it — that distribution surfaces evolve, and any long-arc business has to build for the next one before it arrives — transfers everywhere. Organic to SEM to LLM-driven discovery is the same principle applied three times. Own the relationship, not just the click. That holds whether the click is a search result or an agent making a purchase on someone’s behalf.

Tactics answer “what do I do Monday.” Doctrine answers “what do I believe when Monday is a mess.” Operators drowning in the first are starving for the second.

A daily cadence is a forcing function for honesty

Writing every day is not a productivity flex. It is a constraint that makes lying to yourself expensive.

You cannot hide behind polish at this cadence. There is no time to sand a weak argument into something that sounds impressive. Either the position holds or it doesn’t, and if it doesn’t, you find out fast because you have to defend it again tomorrow with a fresh one. Volume exposes the fakes. A quarterly essay can be beautiful and hollow. A daily memo that is hollow reads as hollow by the third paragraph, and you know it while you’re writing it.

The cadence also builds the corpus. One memo is an opinion. 200 memos that cite each other, contradict each other where the thinking changed, and compound into a coherent view — that is a body of work. The internal links are not SEO decoration. They are the load-bearing structure. When a position here connects to a position there, the argument gets heavier, and heavy arguments are the ones that survive.

The corpus works because the same bet works in product. A portfolio of fast, cheap attempts beats one perfect swing. 50 memos where 49 are ordinary and one reframes how you think about trust in a product is a better trade than one flawless essay a quarter that nobody remembers. Ship fast, cut scope, let the corpus sort the winners. The method is the message.

Daily also kills the temptation to wait for the perfect take. There is no perfect take. There is the take you can defend today, published, and then revised in public when you learn you were wrong. That revision is the point. A blog hides its mistakes. A body of work leaves them in and shows the reader how the thinking moved.

This is for the operator who wants an argument, not applause

The reader this is for is not looking for reassurance. They are looking for something sharp enough to sharpen against.

If you want a numbered list to screenshot for your team’s Slack, this is the wrong site. If you want to be told your instincts are correct, wrong site. What is here will sometimes tell you the opposite of what you believe, on purpose, because a position that never disagrees with anyone is not a position. It is a horoscope.

The right reader is a builder-PM, a founder, an operator making calls with incomplete information and no one above them to blame. Someone who has shipped enough to know that the frameworks lie about how clean the work is. Someone who reads to argue back, not to nod along. If a memo here is wrong, that reader will know it before I do, and the best outcome is that they tell me and the corpus gets corrected in the open.

The obvious objection: taking hard positions in public means being wrong in public, repeatedly, in a searchable archive. True. That is the cost, and it is the whole point. A body of work that was right about everything was never risking anything, and writing that risks nothing teaches nothing. I would rather publish 100 positions and defend the 70 that hold than publish nothing falsifiable and call it thought leadership.

Every memo after this one is a bet placed in public, defended in prose, and left on the record to compound or collapse. That is the deal. Read accordingly.