
There's a million bad ways to prioritize what ideas to pursue. The worst—that is, least effective—involve some made-up formula usually consisting of things like business value, user value, and technical difficulty.
Just because this method is pervasive doesn't make it meaningful. It misses the point of prioritization entirely.
The job of a product company—and specifically product teams—is not to prioritize solutions. It's to create value for the cusotmer in a way that creates value for the business. Rarely does the business accomplish this goal through ranked ideas lists.
No matter how much you may believe it, your company is not a feature (or two or three) away from a radically better product. When we are output focused, we judge success based on what we deliver, and the emphasis is on what to build when.
But when we judge success based on what outcomes we drive for customers, it's less about what we deliver and more about how much of a customer problem we solve.
Opportunity maps provide a method for organizing our understanding of customer needs (e.g., users, admins, and buyers) and opportunities to deliver value to the customer and aligning those elements with the needs of the business.
The ROI calculation is variable to the pricing model of the product—subscription or transaction based, tier licensing, etc.
You can expect the following benefits from adopting an opportunity map in your product prioritization workflow: