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 tool. Our user satisfaction scores for new adopters have been declining, and sales cycles are lengthening as prospects cite a steep learning curve. Internally, the engineering team is feeling the strain of maintaining this sprawling codebase. We're now debating a fundamental strategic shift: do we double down on the power-user, enterprise segment and continue adding depth, or do we invest in a significant simplification effort, potentially creating a streamlined, opinionated version of our product aimed at mid-market teams? This isn't just a UI refresh; it would involve rethinking default workflows, hiding advanced options, and possibly deprecating niche features. I'm tasked with building the business case for either path. For other PMs who have faced this "power vs. simplicity" dilemma with a mature product, how did you evaluate the trade-offs? What customer research methods or data points proved most decisive in understanding whether your complexity was a necessary evil for your core audience or an adoption barrier you could afford to remove? How did you manage the internal politics and potential backlash from existing power users if you chose to simplify?
You're not alone. In practice, many teams end up with a two-track approach: keep the existing platform, but deliberately ship a streamlined, 'mid-market' path for simpler adoption while preserving full features for power users behind an enterprise plan. Start with a small set of modules you’ll simplify, run a pilot with a handful of accounts, and measure onboarding time, activation rate, and satisfaction against your baseline.
Customer research plan: identify core jobs-to-be-done for new users, segment by company size and tool proficiency, and interview admins and end users. Build a value-vs-complexity map for features. Run a closed beta on the simplified path, track trial-to-paid conversion, and collect qualitative feedback on what feels easier or harder.
Decision framework: two options (A) deepen power-user with more depth, (B) simplify with an opinionated mid-market path. Build a simple scoring rubric: user impact, revenue impact, risk (retraining, migration friction), and delivery risk. Weight them by your business priorities and run rough simulations with a basic cost model.
Product approach specifics: if you go simplification, define a crisp default workflow and enforce it with guided tours, sensible defaults, and progressive disclosure for advanced options. If you pursue deeper capabilities, consider feature taxonomy, toggles, and modular architecture that can be rolled out incrementally. A strangler-like migration pattern can reduce risk if you replace hot paths piece by piece.
Managing internal politics: frame the choice as optimizing value for customers, not dumbing down. Create a transition plan with deprecation rules, clear milestones, and a sandbox for power users to voice concerns. Build cross-team sponsors and open channels for feedback to shape a shared roadmap.
Quick check-in questions you can use to tailor advice: what are your top three use cases in the next 12 months? what percentage of customers are mid-market vs enterprise? what’s your current churn and expansion signal? do you have rough estimates for the cost of complexity (engineering hours, support) to feed your ROI model?