Planning a Near-Term Roadmap Amid Incidents, Deal Pressure and Customer Asks

Production issues, pressure from sales and requests from existing customers are all pulling your team in different directions. How would you put together a short-term roadmap? ```hint Do they belong in one list? These demands arrive differently: some interrupt you without warning, some come with a deal date, some repeat across many accounts. Think about whether ranking them all against each other is the right first move. ``` ### Clarifying Questions - How short is short-term here: the next sprint, the next month or the next quarter? - How serious are the production issues: occasional bugs, or repeated outages and quality failures that customers are already escalating? - Is the sales pressure tied to named deals waiting on specific features, or to a general push for more to sell? - How large is the team, and have any of the requests already been promised to customers with dates? ### What a Strong Answer Covers - A single view of all three kinds of demand, framed as problems with their impact, deadline, confidence and effort - A clear rule for which production issues interrupt the plan immediately, and when repeated incidents earn planned reliability work - How sales requests are qualified (real deals, true blockers, whether the feature generalizes) instead of being accepted or dismissed by default - A capacity allocation or scoring approach that yields a sequenced plan and makes the trade-offs visible - Alignment with engineering, sales and customer-facing teams, and a cadence for revisiting the plan when things change ### Follow-up Questions - Two weeks in, a severe outage takes most of the team's time. What drops out of the roadmap, and who hears about it first? - Sales insists a large deal will be lost without a feature only that prospect needs. How do you decide, and what would make you say yes? - After a quarter, how would you tell whether this way of building the roadmap is working?