Sometimes great ideas, customer needs, product priorities, and engineering resources just align perfectly. Sometimes a feature is so simple that it makes more sense to just implement than to take the time to prioritize or sequence it. In my experience, those features represent the vast minority of features, and in a world of near-endless possibilities (and limited developer hours), the hardest part of software development is not coming up with features to build, but instead, deciding what features will have the biggest impact. Here are seven anti-patterns I’ve seen both in open and closed source, for prioritizing feature requests:
1. Someone is willing to build it
In less formal organizations (open source projects included), the biggest barrier to entry is finding someone with the skills necessary to solve an identified problem. Open source issue trackers are replete with “this is a great idea if anyone willing to submit a pull request”-type issues. The same is true of non-developer stakeholders and closed source projects, with lawyers, support reps, and marketers shopping around ideas internally in hopes of finding someone willing to implement them.
Maybe the idea comes from a developer who’s experienced the problem themselves. Maybe the external issue or internal ask makes its way in front of a sympathetic engineer willing to dedicate a few cycles. Granted, there will always be no-brainers and quick wins, but in most cases, “someone is willing to do this”, should not necessarily translate to “we should do this”.
2. Sales says a lot of/a big/a potential customer is asking for it
Your Sales team is one of your most robust means of getting feedback from customers. If an existing or potential customer has a suggestion, it’s in everyone’s best interest for that idea to be communicated via the sales rep to those who are in a position to implement it. But it’s all too easy to confuse that which you hear from an important customer, with that which is most important. Sure, there may occasionally be overriding business concerns, but in general, product development and project management are neither a democracy nor a pure customer oligarchy.
Your users are experts at using your product, not building, supporting, or maintaining it. Feedback via your sales channels should be one of your primary means of understanding user challenges, and it may make sense to take logos or seats into account, but it should not be your primary means of feature definition or prioritization, nor should it be your only means of feedback.
3. Your friend is asking for it
People in technology tend to have friends in technology. It’s not uncommon for friends to be users, and for conversations at meetups, over dinner, or during happy hour to turn to talking shop. Nobody wants to disappoint someone they respect, and showing that you listened to their advice or were in a position to implement their suggestion is a proven recipe to garner admiration.
Unless you’re building a product for developers, it’s unlikely that your friends are your target audience, and even if you are, they’re not going to be representative of the full range of both current and potential users. Friends can be the source of some of your most honest, direct, and immediate critical feedback, but keep in mind that one data point does not create a pattern.
4. It’s easy to do it
There are always going to be a certain number of no-brainer, quick wins that are trivial to implement and serve as “quality of life” improvements for users. When you’re looking at adding a toggle to turn off a feature or supporting a one-off workflow, it can be tempting to just click merge, especially when the depth of discussion becomes disproportionate to the technical lift.
Just because something’s easy to implement, doesn’t mean that you necessarily should. For one, every feature you add creates an implicit and perpetual contract with your users, a contract that obligates you to maintain, support, and build around that feature in every subsequent release. For another, a well-curated project is a feature in itself. Sometimes taking the time to implement the technically more complex solution will ultimately be better for users and maintainers.
5. Our competitor does it
Any sufficiently complex choice between two pieces of software will at least partially hinge on a feature bake off in which you create a matrix comparing the offerings of two or more alternatives. If you know this is how you’re going to be evaluated, it can be tempting to try to stack the deck in your favor by checking every box you can so that you objectively win on arithmetic alone.
Ultimately, a single feature may make or break a deal, but in the long run, if that feature’s not part of your core value proposition, users are going to choose you over your competitor based on taste, vision, and direction, not on your ability to export to PDF, especially if you give them the means to build a workaround. Instead of cramming for the midterm exam, focus on what you do best overall, not on what your competitor does today.
6. A squeaky wheel is asking for it
There’s always that user. There’s a pet feature they want. Maybe they’re the only one experiencing it. Maybe it’s something you’ve deprioritized for other reasons. Whatever the reason, they’re not taking “no” for an answer, and they use every opportunity they can to remind you of it. Whether it’s emailing weekly, using hyperbolic language with support or sales, or threatening to move to a competitor, you know you’re going to continue to be bombarded by requests until you give in.
Product development is not a shouting match. Just because someone shouts an idea loudly or frequently doesn’t mean it’s a good one. You may be tempted to fulfill the request to please the customer (or end the request DoS), but more often than not, as soon as you do, they’ll have another equally critical feature to fixate on next. Sometimes there are truly take-it-or-leave-it features that may make business sense to implement, but I’ve found often in these cases it’s the customer, not the product, and it may be worth taking the risk that they realize it’s just not the right fit. Everyone will ultimately be better off.
7. A handful of power users are asking for it
Most products have three broad classes of users: new users, mainstream users, and power users. New users need your product to be as simple and intuitive as possible. They are also often the metric by which you measure growth. As they go deeper and deeper into your product, power users want to implement increasingly complex and custom workflows. Power users have the most invested in your product, and can be your strongest advocates. You want a product that encourages growth, but you don’t want to force users out as they mature or cannibalize one group to make things more sticky for the other.
It can be hard to balance two seemingly diametrically opposed use cases, but keep in mind that for every power user that writes in asking for a feature, there’s one new user (and ten potential users) that felt the opposite way, but are still onboarding and didn’t have enough at stake to warrant letting you know. If you’re just trying out an app and see something you don’t like, you move on to the next app. That’s not the case if you’ve been using it for years and have a high switching cost. When you’re evaluating potential features, part of your role is to be an advocate for the long tail of users that won’t yet advocate for themselves.
Prioritizing features that will have the biggest impact
What features should you build then? In short, you should be focusing on themes that support a more unified product vision, and the individual features that build towards them. Before a feature request comes in, you should know who your target users are, the use cases you’d like to support, and roughly the direction you want your product heading towards in six months or a year.
Great product ideas come from unexpected sources and at unexpected times. Software is more art than science, and sometimes it takes getting one feature into the hands of users to realize you need another. While it may be tempting to shortsightedly tackle features that are easy to implement or loudly requested, when ideas do come in, they should be evaluated against established product themes, not what requests make sense in isolation or at the moment.
If you enjoyed this post, you might enjoy:
- Towards a More Agile Government
- Why open source
- Twelve tips for growing communities around your open source project
- Ten ways to make a product great
- Securing the Status Quo
- 15 rules for communicating at GitHub
- Five best practices in open source: external engagement
- 19 reasons why technologists don't want to work at your government agency
- Twelve things a product manager does
- Why you probably shouldn't add a CLA to your open source project
- Removing a feature is a feature
Ben Balter is a Senior Technical Program Manager at GitHub, the world’s largest software development network. Previously, as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →