Lore

Tiny Core Product Strategy

Overview

Products should orient around one small, exceptionally executed "tiny core" rather than accumulating features. Doing one thing extremely well beats doing many things adequately.

Cautionary story: polishing the wrong layer

A 2014 Notion-competing startup lost a term sheet the same week Notion pivoted, then over-invested in polishing markdown-editing niceties — while Notion won with a deliberately bare-bones editor. The source argues that working diligently on the wrong layer of a product for too long is a distinct, serious failure mode from simply not working hard enough: agency and effort don't help if they're spent perfecting a part of the product that isn't the core.

Related: The First 10% Are Free, the Last 10% Are 90%, narrow-audience-product-focus, Agency as the AI-Era Differentiator.

Concrete Examples and Path to a Tiny Core

Named examples of a single, exceptionally executed core feature carrying a product: Heroku's git push heroku master, GitHub's pull request, Notion's blocks and slash commands.

Getting there is rarely a straight line: Notion has deliberately tolerated roughly six overlapping automation primitives (including multiple agent surfaces) inside its product rather than prematurely consolidating them, treating the redundancy as raw material to later fuse into one simplified core — contrasted with a competitor (Claude's desktop app) leaving three separate, unreconciled tabs in place instead of converging on one.