Recover Enterprise Adoption Stalled by Roadmap Doubts on a Two-Engineer Team

You are the PM for a product built by a team of two engineers. Enterprise customers are holding back from adopting it, and the reason they give is that the roadmap is unclear. Both engineers are already fully occupied with a task that was planned earlier. What do you do? ```hint Two problems, not one Ask whether the roadmap is unclear inside the team or only to customers. The answer decides how much of the fix needs engineering time and how much falls on you. ``` ### Clarifying Questions - Does an internal roadmap exist that customers simply cannot see, or is the plan itself unsettled? - Are the blocked customers prospects stuck before signing, or signed accounts that are not rolling the product out? - Is the engineers' current task something enterprise customers asked for, and how close is it to done? - Is there a sales or account team talking to these customers, or is the PM their main contact? ### What a Strong Answer Covers - A diagnosis of what "unclear roadmap" stands for and which customers it blocks, based on evidence from deals and accounts. - A reasoned decision on whether the engineers' current task continues, pauses or changes, rather than a reflexive switch. - A roadmap and set of commitments that two engineers can actually keep, and a plan to communicate them consistently. - How the PM protects the engineers' focus while engaging customers, sales and leadership. - Measures that show adoption is moving, and a cadence that keeps the roadmap current. ### Follow-up Questions - A large prospect will sign only if you commit to a feature by a fixed date, and two engineers cannot build it alongside current work. What do you do? - Your leadership does not want the roadmap shared outside the company. How do you still unblock these customers? - Two months after you share the roadmap, adoption has not moved. What do you look at next?