Famous Feature Bloat Examples
Feature bloat isn't theoretical. These are real products where unused features created maintenance nightmares, drove users away, or cost billions in wasted engineering.
| Product | Feature Count | % Used | Notable Bloat | Outcome |
|---|---|---|---|---|
| Microsoft Word | ~1,500 | ~10% | Most users use fewer than 150 features. Ribbon UI redesign was partly to surface buried functionality. | Power users stay, average users migrated to Google Docs for simplicity. |
| Salesforce | Hundreds of settings | ~20-30% | "Shelfware" problem — companies pay for modules they never configure or use. | Spawned an entire Salesforce consulting industry just to configure it. |
| SAP ERP | Thousands | <15% | Massive customization surface means most deployments use a fraction. Implementation costs 3-5x license cost. | Multi-year implementations, many abandoned mid-project. |
| Jira | 250+ | ~30% | Workflow complexity, custom fields, and configuration sprawl. "Jira admin" became a full-time role. | Teams migrating to Linear, Shortcut, and Height for simplicity. |
| Slack | 150+ | ~40% | Huddles, Canvas, Lists, Clips — features that duplicate tools teams already use. | Rising complaints about resource usage and notification overload. |
| Adobe Photoshop | 500+ | ~10% | 90% of features unused by 90% of users. 3D tools, video editing, measurement tools buried in menus. | Canva and Figma captured casual users who found Photoshop overwhelming. |
| Oracle ERP | Thousands | <10% | Implementation costs routinely exceed license fees by 3-5x. Customization creates untestable surface area. | Cloud migration projects regularly fail or run years over schedule. |
| Zoom | 100+ | ~30% | Expanded from video calls into email, calendar, docs, whiteboard, and phone — duplicating existing tools. | Market confusion about what Zoom actually is. Stock declined from pandemic highs. |
| WordPress | 50K+ plugins | ~5-10 plugins avg | Plugin bloat causes performance, security, and compatibility nightmares. Average site has 20+ plugins. | Performance issues, security vulnerabilities from abandoned plugins. |
| HubSpot | 200+ | ~25% | Feature creep across marketing, sales, service, CMS, and operations hubs. Overlapping tools within hubs. | Customers pay for full suite but only use 1-2 hubs effectively. |
| Notion | 100+ | ~35% | Everything-app approach: docs, wikis, databases, projects, AI. Steep learning curve for new users. | Power users love it, casual users churn to simpler alternatives. |
| Figma | 80+ | ~50% | Post-Adobe acquisition concerns about feature velocity adding complexity (Dev Mode, Slides, AI features). | Community pushback on features that complicate the core design workflow. |
| Google Workspace | 15+ products | ~5-6 products avg | Overlapping products: Chat vs Meet, Docs vs Sites, Spaces vs Groups, Currents (killed). | Google regularly kills overlapping products, confusing users. |
| Atlassian Suite | 8+ products | ~2-3 products avg | Jira, Confluence, Trello, Bitbucket — significant feature overlap. Trello acquisition created internal competition. | Forced migration to cloud, sunset of Server products angered customers. |
| IBM Notes (Lotus) | 200+ | <20% | Email + calendar + database + app platform. Legendary for being impossible to replace because of custom apps. | Became the textbook example of bloatware. Companies spent years migrating away. |