How do you re-evaluate roadmap and communicate an enterprise-to-SMB pivot?

WHAT THIS TESTS: This question evaluates your ability to perform strategic roadmap surgery when the business model changes. The interviewer wants to see if you understand that a customer segment pivot from enterprise to SMB changes non-functional requirements, pricing architecture, support models, and feature priorities. They are looking for structured product thinking, stakeholder management, and the emotional intelligence to lead a team through uncertainty.

A GOOD ANSWER COVERS: four things in order. First, discovery and gap analysis: you compare enterprise requirements against SMB realities, identifying shifts like moving from SSO and custom SLAs to self-service signup, simplified UX, and multi-tenant efficiency. Second, portfolio triage: you audit in-flight projects against the new segment, categorizing work as accelerate, pivot, pause, or kill based on time-to-value and technical debt. Third, dependency and risk mapping: you surface architectural changes needed for lower contract values and higher volume, such as automated provisioning or reduced operational cost per tenant. Fourth, communication and change management: you explain the why using market data and leadership context, create space for the team to ask questions, and co-create a revised timeline rather than dictating it.

COMMON WRONG ANSWERS: include three patterns. One is the scorched earth approach where you cancel every enterprise project immediately, which wastes sunk cost and damages team trust. Another is purely bottom-up reasoning where you let engineers decide what to keep without business context, which produces misaligned priorities. The third is delaying communication until the perfect plan exists, which allows rumor and anxiety to fill the gap.

LIKELY FOLLOW-UPS: include asking how you would handle a critical enterprise feature that one large customer still demands, how you would rebalance the team if SMB requires faster iteration cycles, or what metrics you would track to validate the pivot is working within the first 90 days.

ONE CONCRETE EXAMPLE: imagine your team is building a bespoke data export tool for a Fortune 500 client. For SMBs, you might pivot that work into a standardized CSV self-service export, preserving the underlying ETL investment while changing the delivery model. You would present the customer acquisition cost data showing that custom engineering per deal makes the unit economics impossible at lower price points, then invite the team to propose the fastest path to a generic solution.