Stratechery (with Ben Thompson)

The episode opens with a joke about Federal Reserve chair Jerome Powell and the damage left by an era of rising markets and easy money, then introduces Stratechery as Ben Thompson's attempt to explain the strategy behind technology products and the business models behind their financial results. The hosts frame its reach through the executives Thompson has interviewed and the readership his work has attracted. That framing is also personal: Ben Gilbert and David Rosenthal trace their own friendship to exchanging Thompson's writing in 2014, when Stratechery was still a new site. The discussion therefore treats the publication both as a business and as an intellectual reference point for other creators.

Thompson's account of publishing begins with accumulation. He had launched several blogs and imported older Tumblr posts so a new visitor would find a substantial archive rather than a single introductory post. He makes the same argument about podcasts: a back catalog lets someone who likes the first episode continue immediately, and demonstrates that the creator can sustain the work. He distinguishes a one-off good article from the harder ability to produce worthwhile work consistently; the archive is evidence for that ability, not just a promise.

That emphasis on consistency informs Thompson's disagreement with the idea that creators sell individual pieces. A reader may enjoy free content in the short run, but a creator who cannot fund the work will not keep producing it. Microtransactions also mismatch the timing of labor and payment: the writer invests heavily before knowing whether a particular article will find an audience. Subscription revenue instead funds ongoing work in advance. Thompson says his product is a reliable cadence and a quality bar, together with the assurance that readers will get his perspective when something important happens. This is a claim about the relationship a subscription supports, not a guarantee that every article will meet the same standard; he says a piece he dislikes can trouble him for a day.

The business model grew out of an editorial gap Thompson saw between product coverage and financial reporting: he wanted to explain the strategy and economics underneath products, including the role of company culture and organizational limits. His previous jobs made that perspective concrete. At Microsoft he worked across social media, publishing, and lifestyle applications, learning how industry structure and developer relationships shape products. Before that, he had been an Apple enthusiast and interned at Apple University, where he saw how culture can coordinate a large company without spelling out every decision. But culture can also constrain change, and writing it down may turn a flexible shared understanding into a rigid rulebook. The episode presents this as a tension rather than a settled formula.

Thompson's preferred question about a company is not simply whether a product was a mistake, but why a capable organization made that choice. Calling decision makers stupid ends the analysis; understanding their incentives, organizational limits, and existing strengths can reveal both what went wrong and what strategy might work. He points to Microsoft as a case where diagnosing its problems also helped him identify a path forward that the company later adopted. This approach depends on separating reporting, analysis, and opinion: reporting establishes what happened, analysis asks why, and opinion argues what should happen. Thompson says he deliberately avoided breaking news because his early work had no privileged access and was built from his own reasoning.

His time inside large companies explains why organizational structure matters so much to that analysis. A company is not a single actor: thousands of people have different views, and coordination is costly. Shared culture can help employees make compatible decisions without communicating every detail. Yet the same culture can become a constraint when a company needs to change direction. Writing culture down may help define it, but it can also make a flexible practice feel permanent. The conversation does not resolve this trade-off; it emphasizes that culture is powerful precisely because it coordinates what cannot be specified, and dangerous when the organization treats yesterday's norms as rules for tomorrow.