I'm the product manager for a B2B SaaS platform in the project management space, and we're at a critical juncture with our flagship offering. Over the past two years, we've aggressively added features based on enterprise client requests, resulting in a powerful but increasingly complex and intimidating interface for our core user base of small to mid-sized teams. Our user analytics show a clear drop-off in feature adoption beyond the basic task and timeline functions, and support tickets are increasingly about navigation confusion rather than technical bugs. We've just concluded a series of user interviews, and the feedback is unanimous: the product feels "bloated" and "overwhelming." The executive team is divided; one faction wants to double down on the enterprise path with even more advanced customization and reporting, while my team believes we need a major usability overhaul, potentially even creating a simplified "Essentials" mode or a parallel, streamlined version. I'm tasked with building the business case for our recommended direction. For other PMs who have steered a product through this "featuritis" phase, how did you approach prioritizing simplicity without alienating power users? What strategies did you use to validate the financial impact of improved usability versus adding more enterprise-grade functionality, and how did you structure a rollout plan that managed the risk of disrupting existing, satisfied clients?
Great challenge. My approach would be to build an 'Essentials' mode—a pared-down UI with the core task/timeline features, common reports, and safe defaults. Do a MoSCoW exercise to decide what stays, what goes, what’s nice to have. Then run a 4-week pilot with a couple of your client segments and collect real usage data. Important: keep the enterprise features behind an opt-in toggle or separate tab so you don’t disrupt current users.
Quantify the value of simplicity before you cut scope. Create a simple ROI model: onboarding time saved, time-to-value for new teams, support ticket reductions, potential expansion by lower friction. Compare that to potential revenue from additional enterprise modules. Build a dual-roadmap: Essentials now, more advanced features later if the data justifies. Also ensure a clean migration path for teams who rely on current workflows.
Implement a disciplined discovery and testing plan: create a lightweight usability study with tasks mapped to core workflows, track task success, time on task, and cognitive load (SUS or similar). Use a 'shadow' product approach where you launch the Essentials UI to a subset behind a feature flag while telemetry tracks behavior. Roll out to more teams only after solid improvements in engagement and task success.
When selling this internally, frame it as risk management: reduce cognitive load now, preserve revenue retention from existing enterprise customers, and avoid a risky full rewrite. Use stage-gated rollout, with a clear rollback plan. Keep an evergreen 'portfolio' of modules that can be added as needed, but ensure a modular architecture that won’t lock you in or explode config management.
Consider progressive disclosure and toggles. Power users often want depth, so provide an Advanced/Expert mode or 'Power User' workspace that exposes hidden features, keyboard shortcuts, and customization once basics are mastered. Essentials becomes the default for new users. Measure conversion to the advanced mode to see if it adds value.
Happy to sketch a two-page business case or a 6-week rollout plan if you share rough numbers and current pain points. I can tailor a simple scoring rubric for prioritization and a recommended rollout timeline with milestones.