{"id":343,"date":"2019-01-01T12:48:56","date_gmt":"2019-01-01T12:48:56","guid":{"rendered":"http:\/\/321-growth-academy-2023.local\/beyond-feature-requests\/"},"modified":"2023-11-06T23:55:26","modified_gmt":"2023-11-06T23:55:26","slug":"beyond-feature-requests","status":"publish","type":"post","link":"https:\/\/321growthacademy.com\/beyond-feature-requests\/","title":{"rendered":"Beyond feature requests"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

A Broader Approach to Product Roadmap Input<\/h2>\n\n\n\n

Let\u2019s be clear: we\u2019re all for feature requests. They\u2019re definitely imperative. Managing feature requests and prioritizing new features based on client feedback and other market research and insight is key, key, key to evolving products that people need and want to use. We love the lean startup way so learning and iterating based on input is right up our alley\u2026<\/p>\n\n\n\n

But\u2026  (You knew there was a but, right?!) But, when feature requests are the only thing that you\u2019re thinking about and considering when you look forward and build out your product roadmap, well, that\u2019s where we say, hang on a sec, there\u2019s more to this\u2026<\/p>\n\n\n\n

Product Management as One (Integrated!) Pillar of Growth<\/h3>\n\n\n\n

There\u2019s more to Product Management than roadmaps based on feature requests. Why?  Product is one of the key growth areas for startups and scaleups, so it\u2019s key for Product to be aligned with the other key growth areas: Sales, Marketing and People.  Really what we\u2019re saying here is that growth is most likely when your whole team and company is aligned around the same vision of growth. So before thinking about specific feature requests (even if they are relayed urgently from your top customer, and, yes, we get it!), think about the overall moonshot of what you\u2019re trying to achieve and ensure that everyone has an understanding of and buys in to the big picture. Planning with the moonshot in mind is paramount to moving toward your overall \u201cwhy.\u201d  (And we\u2019d be remiss to not mention that, of course, Product is ultimately all about solving a need for your ideal customers \u2013 a real need that resolves real pain and that they\u2019re willing to pay for\u2026)<\/p>\n\n\n\n

The Feature Request Game<\/h3>\n\n\n\n

Whether you\u2019re early days with a few early (maybe even pilot) customers, just gearing up with a few early adopter clients, or really rocketing up into the scale-up stage, if you have people using your product or solution, you\u2019re going to hear about their ideas for how to make it better.  Like we said, that\u2019s a good thing.  It\u2019s just that sometimes it\u2019s the only thing.  And so what if it is?<\/p>\n\n\n\n

FOMO: <\/strong>The trouble is, if you\u2019re only evolving your product forward based on specific feature requests from certain clients or users, then you may be missing out on considering features or product ideas that might come to light by exploring other sources.<\/p>\n\n\n\n

Bias (your roadmap): <\/strong>Plus, you could be inadvertently biasing product development to the current clients (the largest revenue clients or the clients that provide the most input) at the cost of building a product that other clients, prospects or markets might desire, and which could be integral to the future of your company.<\/p>\n\n\n\n

Last, you risk having a short-term focus<\/strong> and be constantly \u201cchasing user happiness\u201d. By the time you build that feature one user has requested, they\u2019ve moved on to a new shiny feature request. And you risk missing the potential for big leaps in functionality or surfing the wave of market trends when you are responding to feature requests only from existing users.<\/p>\n\n\n\n

Moving Beyond: There\u2019s More Out There<\/h3>\n\n\n\n

Ok, if you want to consider moving beyond feature requests, what are some additional things to think about?  Here\u2019s a few:<\/p>\n\n\n\n