About featurebloat.com
An independent editorial reference on feature bloat in software products. Anti-patterns, named case studies, decision frameworks, role-specific playbooks, and the books and research that anchor each position. No vendor relationships, no paid placements, no consulting funnel.
Reviewed against primary sources May 2026
01. Why this site exists
The serious work on feature bloat lives in books and research, not in vendor glossaries
Search for “feature bloat” or “how to prevent feature bloat” and the first page returns product-management vendor glossaries. Each entry is roughly 800 words, takes no position, names few products, and recommends the vendor’s own software at the end. That is a useful first definition. It is not a useful working reference.
The serious work on feature bloat lives in books and research that vendor glossaries do not surface: Leidy Klotz’s Subtract on the addition bias in human cognition (Flatiron, 2021); Marty Cagan’s Inspired and its naming of the feature factory (SVPG / Wiley); Teresa Torres’s Continuous Discovery Habits on opportunity solution trees; Nielsen Norman Group on progressive disclosure and complexity costs; Steve Krug’s Don’t Make Me Think on usability heuristic foundations; Don Norman’s The Design of Everyday Thingson perceived complexity and affordances; and the Pendo and Mixpanel Product Benchmarks reports on what feature adoption actually looks like in shipping software.
This site is the synthesis: editorial positions on what causes feature bloat, what to do about it, and when the analysis says the bloat is actually the right call. The decision framework, anti-pattern taxonomy, and named case studies are all derived from these source materials and cited inline. The audit goal is traceability: every claim on the site should be re-checkable against a named, dated source.
02. Who builds this
Built and maintained by Oliver Wakefield-Smith at Digital Signet
featurebloat.com is built and maintained by Oliver Wakefield-Smith at Digital Signet, an independent editorial studio that publishes reference properties on software-economics topics. The studio has no product-management software to sell, no PM consulting offer attached, and no commercial relationship with any of the vendors or products named on this site.
Other Digital Signet reference sites in adjacent surfaces:
Project cost overrun statistics, EVM calculator, case studies and prevention frameworks.
Software rework economics, the true cost of bug fixes, requirements churn and refactor budgets.
SaaS churn economics, retention models, gross-vs-net revenue retention reference.
Operations monitoring noise: alert fatigue, on-call cost, signal-to-noise reference for SRE teams.
03. Editorial position
Independent reference, no consulting funnel, no PM-software resale
This site is editorial. There is no product-management software being sold here, no audit service being funnelled, no enterprise sales motion. Outbound book links do not carry affiliate parameters. Mentioned products (Notion, Slack, Microsoft Word, Zoom, Salesforce, Evernote, Atlassian, Basecamp, Linear, Apple, Google) are named because they are the relevant editorial entities, not because of any commercial relationship.
Where the editorial position disagrees with a named author or source, the page says so. Where a case-study interpretation is contested in public commentary, both sides are surfaced rather than the convenient one picked silently. The site is willing to take positions; it is also willing to be wrong in public and correct itself when a reader points out a substantive error.
04. What this site covers
15 pages, organised by argument, playbook, and role
What feature bloat is, why products default to adding, and the editorial position. Five-question FAQ on definitions.
Scope creep, feature factory, kitchen sink UX, parity paranoia, no sunsetting, configuration overload, feature-flag forever, CEO pet feature, sales-led customisation, enterprise exception default.
Microsoft Word's 1,500 commands, Evernote's death spiral, Zoom's everything-but-meetings expansion, Slack vs Teams, Notion's everything-is-a-block trade-off, iOS Settings.
RICE / Kano / MoSCoW / Shape Up reviewed honestly with the bloat-specific question each one omits. 10-question diagnostic quiz.
Tactical playbook for sunsetting, deprecating, and removing features. Pre-flight checks, the 4 cut modes by risk, communication template, revenue-risk math, the 4 failure modes.
The honest counterpoint: 4 situations where adding is the right call (platform, enterprise, network effect, late-category differentiation).
Feature usage rate, active feature count per user, time-to-interactive, retention cohorts by feature adoption.
Four scripts for the hard conversations: the CEO pet feature, the sales-led customisation, the loud customer, the engineer who wants to refactor.
Three templates that resist bloat: Shape Up betting table, problem-framed opportunity tree, sunset-lane roadmap.
Eight books with honest capsule reviews. Subtract, Inspired, Shape Up, Rework, Getting Real, It Doesn't Have to Be Crazy at Work, Empowered, The Design of Everyday Things.
4 stages of founder-driven bloat, warning signs, the 90-day founder feature moratorium, the if-I-had-to-rebuild exercise, the 2-week audit.
Diagnosing the feature-factory role, frameworks that change it, scripts for stakeholders, and the metrics that prove outcome over output.
The maintenance tax math, feature-flag rot, test-suite bloat, incident frequency, what CTOs should measure.
Progressive disclosure, strong defaults, the Jobs-to-be-Done reframe, the design audit checklist.
20 most-asked questions about feature bloat: definitions, causes, fixes, measurement, and what to do next.
05. Editorial principles
Six rules that govern what ships
Every claim on this site traces back to a named source: a book (Inspired by Cagan, Subtract by Klotz, Shape Up by Singer, Don't Make Me Think by Krug, The Design of Everyday Things by Norman), peer-reviewed research, Nielsen Norman Group research, Pendo or Mixpanel product benchmarks, or a public press / community post for case studies (Hacker News, Reddit threads, Daring Fireball, Thurrott, public earnings calls).
There are no sponsored slots on this site, no premium positioning for any vendor, no pay-to-rank in any list or table. Where a product is named in a case study or recommendation, the inclusion reflects editorial judgement, not commercial relationship.
Outbound book links go to publisher or author pages without affiliate tracking. Book recommendations are uncoupled from any referral economics so the recommendation can be honestly retracted if our position on a book changes.
This is editorial content. We take positions, including positions that disagree with named authors we otherwise cite. Where we disagree with a source, we say so on the page rather than silently omit the source.
One constant (LAST_VERIFIED_DATE) drives every visible date on the site: the footer "Last verified" stamp, every Article schema dateModified, and the visible review-date badge on /about and /methodology. The label currently reads May 2026. Cosmetic date refreshes are structurally impossible.
Where this site quotes a published benchmark (Pendo Product Benchmarks feature-adoption ranges, Mixpanel activation cohort medians, NN Group usability heuristic outcomes), the claim is bounded by the source's own publication date and methodology. Vendor-published research that lacks methodology disclosure is flagged in /methodology and treated as a directional signal, not a point estimate.
06. Methodology in brief
Sources, in-scope and out-of-scope, refresh cadence, and corrections
Anti-patterns are derived from a synthesis of Cagan’s Inspired, Singer’s Shape Up, Fried’s Rework and It Doesn’t Have to Be Crazy at Work, Klotz’s Subtract, and the NN Group complexity-cost research base. Case studies cite Hacker News and Reddit threads, Daring Fireball, Thurrott, public earnings calls, and product changelogs. Metric ranges cite Pendo and Mixpanel Product Benchmarks where the source publishes its own methodology.
For full source provenance, the calculation framework, in-scope / out-of-scope coverage, and the refresh cadence, see the methodology page.
07. Contact and corrections
Spotted a missed source or a case-study correction?
Email [email protected] with the page URL and the source you would like cited. Substantive corrections (case-study facts, misattributed quotes, named-author position misstatements) are typically actioned within five business days. Non-substantive corrections (typos, link rot, structural edits) batch into the next monthly verification pass.
Disclosures
- ●Not affiliated with any product company named on this site (Microsoft, Notion, Slack, Salesforce, Atlassian, Apple, Google, Zoom, Evernote, 37signals / Basecamp).
- ●Not affiliated with any author cited on this site (Marty Cagan, Teresa Torres, Leidy Klotz, Don Norman, Steve Krug, Jason Fried, DHH, Ryan Singer).
- ●No affiliate links or referral fees on any outbound book, publisher, or vendor URL.
- ●No email-gated downloads, quote forms, or sales redirects. The site is editorial; there is no consulting funnel attached.
- ●Opinion content. Positions on this site are editorial judgements supported by named sources; readers should test the positions against their own product context.