Business & Strategy
Section 1
Core Idea
Incremental augmentation is improving a product, process, or system in small, additive steps rather than big rewrites. Each step builds on the last; you augment what exists instead of replacing it. The core idea: compound progress through many small upgrades reduces risk and keeps the system usable while it evolves.
Free playbook
Get The Business Model Playbook
58 business models, one visual page each: how the money flows, the metrics that matter, and who runs it. Free when you join the Faster Than Normal email.
Free. No spam. Unsubscribe anytime.
Section 2
How to See It
Product
You're seeing Incremental Augmentation when a roadmap is a sequence of “add X,” “improve Y,” “integrate Z” on top of the current product, and each release ships without a full redesign.
Process
You're seeing Incremental Augmentation when teams improve one part of a workflow (e.g. handoff, review, tool) each sprint instead of redesigning the whole process at once.
Section 3
How to Use It
Choose the highest-leverage dimension (performance, UX, integration, coverage) and add one improvement per cycle. Avoid “version 2.0” rewrites unless the base is broken; prefer augmentation so users and the business keep continuity.
Decision filter
"Can we get 80% of the benefit by augmenting what we have instead of rebuilding? If yes, ship the augmentation and iterate; if the foundation is wrong, fix that first, then augment."
As a founder
Prioritise a pipeline of small, shippable augmentations — one capability, one integration, one UX improvement per release. Resist the urge to “do it right” with a big bang; measure progress by cumulative improvement over time.
Section 5
Founders & Leaders
Satya NadellaCEO, Microsoft
Nadella shifted Microsoft from big, multi-year releases to continuous incremental augmentation: cloud, open source, and product updates in smaller, frequent steps. He kept the core assets and augmented with new capabilities and culture. Founders can apply this by treating the product as a living system that improves in small steps, and by measuring momentum in shipped improvements rather than one-off launches.
Section 7
Connected Models
Reinforces
Marginal Gains
Marginal gains are small improvements that add up. Incremental augmentation is the practice: each release is a marginal gain on the existing base. Both favour continuous improvement over occasional big bets.
Tension
MVP
MVP is the minimal first version; incremental augmentation is what comes after. The tension: don’t over-augment before validating the core. Get to MVP, then augment based on feedback and data.
Leads-to
Compounding
Many small augmentations compound: the product gets better every cycle. Compounding is the result; incremental augmentation is the mechanism. Design the pipeline so each cycle adds to the next.
Section 8
One Key Quote
— Satya Nadella, Hit Refresh (2017)"Growth mindset is the belief that everyone can improve. That’s why we ship, learn, and improve — not wait for the perfect release."
Section 11
Summary & Further Reading
Incremental augmentation is improving by small, additive steps on top of what exists. Prefer augmentation over rewrites; ship one improvement per cycle and let progress compound.
01
Book
Microsoft’s shift to continuous improvement and cloud; incremental culture.
02
Book
Build–measure–learn; incremental learning and product evolution.
03
Book
Shipping small changes frequently; technical basis for incremental augmentation.