Focus on “why” in your roadmap instead of “what.” It communicates more clearly where you are headed, and what success looks like.
A “why,” outcome roadmap is about the product vision and the problems you think worth solving. It means your roadmap changes less often. Customer and business problems don’t actually change that much or that quickly. An outcome roadmap is more stable over time with only the tactics employed to reach those outcomes shifting as different approaches are tested. This will help you gain buy-in and leverage the creative problem-solving energies of your team. This is far better than a "what" list of feature promises you likely can’t keep. How often do you find you have to update features and dates on your roadmap? Discuss.
Jobs
My friend Beth Linker at SentryOne is hiring a Technical Product Manager in Boston or Charlotte. The ideal candidate world love databases and using PM skills to help SentryOne build a business. Interested? Ping me.
Street Address
City, State, Zip
Phone Number
Your Custom Text Here