Loading...
Answers
MenuWhich technique is the most used to prioritize features and what's the best tool to use to do that?
In order to prioritize features, there is many techniques and methods out there, which one(s) is/are the most used and what's the most used tool to do that ?
Answers
I've managed digital products (apps) from concept to maturity. My experience is with SaaS and apps, so it may or may not be relevant to your situation.
I think the best tool for prioritizing features is to create a features scorecard in a spreadsheet and use that tool to get alignment with your team as to what features get what priority.
Start with defining your business goals (e.g., get more revenue, increase word of mouth, reduce churn, increase retention, etc.). Then assess the resources you have (e.g., number of developers, designers, writers, customer support, sales, whatever your company has to "spend" to create any feature.)
In your spreadsheet, create a row for each potential feature and a column for each goal and each broad category of resource (engineering, marketing, support, for example). Use a small numeric scale (0 - 3) to "score" each feature in each column. For example, a feature may not move you toward goal #1, so you would put "0" in goal #1 column. For the resources, do the same. To the right of all these add a column that subtracts the sum of the resource or "effort" scores from the sum of all the goal column scores. You can multiply these scores by a confidence factor as well.
If you have a team, it's important to get their input on the scoring. This is not something you just show them and ask for approval. You have to involve them in a meaningful way. I can show you how to do that and point you to some examples you can use, if you'd like to give me a call.
At the end of the day, you want to build features with the highest ROI. The best way to determine ROI is to quantify the value of the RETURN (impact) and INVESTMENT (effort) needed. That means scoring.
You should attempt to define all of the variables that enter into the cost/benefit equation which can be assigned a numerical value. Fuzzier items you can still quantify with a scale. You can make this as simple or complex as you want.
I've tested and used many tools to manage this, including:
-ProdPad
-ProductBoard
-Jira
-ProductPlan
-Aha
-Excel spreadsheet
I've found they all vary considerably and none have hit exactly what I needed, such as:
-Complexity for me, developers and business users
-Self-serve stakeholder scoring and weighting (if you want customer or internal feedback)
-Customization for my unique needs
So I built my own which:
Captures ideas, challenges, bugs, any request
Allows users to submit and see their own in a UI
Places an impact score based on what was provided (strategic fit to company goals, subjective user importance, completeness of request, beneficiary is a customer vs internal, etc)
I receive the request and vet it - classify, categorizer, clarify, close it, add it the FAQ with an answer, send it back to the requester for more details or pass it along for developer estimation, etc
I work with engineering to give a point estimate which results in a priority score and estimated dev work hours
I can then build a scored and dated roadmap based on similarity, priority, effort, etc
I can create Kanban cards and push them to a board via Zapier
When things are completed, I close my initial request and the associated feature is added to our feature list
It's not perfect or pretty (not many visuals) but it keeps everything in one place to manage as the fluidity changes daily and I can easily manage and share with anyone in a consistent fashion - since what gets built is ultimately a negotiation where the priority is a subjective value to start from.
I'm a big fan of Pirate Metrics (AARRR), or:
A - Acquisition
A - Activation
R- Retention
R - Referral
R - Revenue
Some people throw another A on there for Awareness. Essentially you will create a spreadsheet with every product feature as a row, and each metric as a column. You then rank each feature against each metric with a 1-5 score.
In addition, I add a separate set of columns for Risk, Effort/Cost, and Impact. Score them the same way.
If you'd like, you can add a weight to each column, based on how important it is to your business at that time. For example, if you're focusing on growth, acquisition may be more important than revenue, so you'd give Acquisition a 5 and revenue a 2. You can then do a blended average, where you multiply each column score by the weight, and sum all the terms together. This will give you an overall score by which to rank all the features.
Hope this helps!
Related Questions
-
How do build a empowered and motivated engineering team?
I am assuming your question is more pertaining to empowering and motivating (rather than hiring). I can outline some of the practices I have seen really result in high motivation and sense of ownership among engineering teams: * Empathize - Your engineering team will work well and be more motivated if they see you as one of them rather than a person who doesn't understand their function. Show your geeky side to them, and show that you understand their thought process and drivers. * Pick their brain on big and small decisions (roadmap, usability, whatever it is) - Product teams value being heard. The more you position yourself as someone who is WANTS to listen, is keen to have their inputs, you will be surprised at how involved they can get, and also how you can actually tap into a lot of smart ideas/thoughts from them that you can develop on. * Take care to explain - show how you arrive at decisions. Share your research, competitive analysis, and even your thought process on arriving at a feature set or list of things for a release. Its stuff you would have worked on anyway - so no harm sharing with more eyes! * Share customer feedback - nothing motivates your engineers than a positive interaction with a customer. Get them to see customer feedback. Have them sit in and observe some of the usability studies. (B2B - have them see you do some demos or do a successful sales pitch) * Send out interesting articles, insights, business and tech articles with your comments/highlights to them on a regular basis (maybe twice a week?) - maybe even some analysis you did on competition or customer feedback * Engineers like working with people they feel are competent and complement the work they are doing to build a great product. So make sure they see how everyone else around them is also doing a good job and adding value and contributing to the success of the product. * Be transparent about the product/business - Make them feel they are responsible and involved in the business, not just technology. I've seen engineering teams happy about their annual goals having components relating to making revenues, keeping customers happy, or reducing costs. If they are enthused about the business as a whole, they will be more motivated with their engineering efforts * Have a mix of little experiments, R&D, attending to engineering debt, in addition to bug fixes and new features that each engineer gets to spend some time on (based on their interest) * Finally get to know each of your engineers personally, and be aware of what their priorities are. Each of us has different motivations in life, so there is no silver bullet to motivate people. When they know you care for them, they are more motivated :).SG
-
What is the best method for presenting minimum viable products to potential customers?
Whoa, start by reading the Lean book again; you're questions suggest you are making a classical mistake made by too many entrepreneurs who live and breath Lean Startup. An MVP is not the least you can show someone to evaluate whether or not building it is a good idea; an MVP is, by it's very definition, the Minimum Viable Product - not less than that. What is the minimum viable version of a professional collaboration network in which users create a professional profile visible to others? A website on which users can register, have a profile, and in some way collaborate with others: via QA, chat, content, etc. No? A minimum viable product is used not to validate if something is a good idea but that you can make it work; that you can acquire users through the means you think viable, you can monetize the business, and that you can learn from the users' experience and optimize that experience by improving the MVP. Now, that doesn't mean you just go build your MVP. I get the point of your question, but we should distinguish where you're at in the business and if you're ready for an MVP or you need to have more conversations with potential users. Worth noting, MOST entrepreneurs are ready to go right to an MVP. It's a bit of a misleading convention to think that entrepreneurs don't have a clue about the industry in which they work and what customers want; that is to say, you shouldn't be an entrepreneur trying to create this professional collaboration network if you don't know the market, have done some homework, talked to peers and friends, have some experience, etc. and already know that people DO want such a thing. Presuming you've done that, what would you present to potential users BEFORE actually building the MVP? For what do you need nothing more than some slides? It's not a trick question, you should show potential users slides and validate that what you intend to build is the best it can be. I call it "coffee shop testing" - build a slide of the homepage and the main screen used by registered users; sit in a coffee shop, and buy coffee for anyone who will give you 15 minutes. Show them the two slides and listen; don't explain, ONLY ask.... - For what is this a website? - Would you sign up for it? Why? - Would you tell your friends? Why? - What would you pay for it? Don't explain ANYTHING. If you have to explain something, verbally, you aren't ready to build your MVP - potential customers don't get it. Keep working with that slide alone until you get enough people who say they will sign up and know, roughly, what people will pay. THEN build your MVP and introduce it first to friends, family, peers, etc. to get your earliest adopters. At some point you're going to explore investors. There is no "ready" as the reaction from investors will entirely depend on who you're talking to, why, how much you need, etc. If you want to talk to investors with only the slides as you need capital to build the MVP, your investors are going to be banks, grants, crowdfunding, incubators, and MAYBE angels (banks are investors?! of course they are, don't think that startups only get money from people with cash to give you for equity). Know that it's VERY hard to raise money at this stage; why would I invest in your idea when all you've done is validate that people probably want it - you haven't built anything. A bank will give you a loan to do that, not many investors will take the risk. Still, know not that your MVP is "ready" but that at THAT stage, you have certain sources of capital with which you could have a conversation. When you build the MVP, those choices change. Now that you have something, don't talk to a bank, but a grant might still be viable. Certainly: angels, crowdfunding, accelerators, and maybe even VCs become interested. The extent to which they are depends on the traction you have relative to THEIR expectations - VCs are likely to want some significant adoption or revenue whereas Angels should be excited for your early adoption and validation and interested in helping you scale.PO
-
How do you get a product prototype developed in China sitting in the US?
It varies and it's very very specific to what you want to develop. The concrete design of your circuit matters. Also prototype building costs are usually a factor 10-100 higher than series. If you already have your prototype then you can shop around various manufacturing companies. To do that, you need Gerber files (your PCB design) and a bill of materials. You also need to think about casing: designing it and creating the mold is expensive. If you don't have your prototype yet, I recommend having it engineered in eastern Europe. Custom engineering is cheap there and high quality. IP protection is a problem. One thing to do is to distribute the work to different manufacturers. For the design phase you are safer if you design your prototype in Europe or the US where international patent laws apply. I could give you more specific advise in a phone call, getting to know a bit better what you are trying to build.GF
-
How do I become a mentor at 500 Startups?
As a 500 Startup mentor I would suggest the following 1) Blog about distribution, design and data. Those are the things that 500 values most and usually the fastest way to get on their radar. 2) Interact with @davemcclure (and all other partners) on Twitter 3) Attend geeks on a plane or other events they host. It's all about relationships and perception, so create opportunities to increase the probability of showing them that you have skills that are relevant to the companies they invest in. Hope that helps.DM
-
What is the process of productizing a service? Also what are some good examples of productized services that have scaled?
2 different categories come to mind. H&R Block or other tax preparation services. The second is restaurants. This may seem like a product more than a service but I think it truly falls into the category of service, especially if you look at the national chains. Think Applebee's, TGI Fridays etc. The reason people go to these places is because of the experience they receive. The franchisors have created a system that generates nearly identical results nationwide. The first thing you need to do is figure out what makes your service superior to others out there, then you need to figure out how and why this is the case. From there you need to document it and make sure that you have a mechanism in place to ensure compliance. Granted that is a huge amount of work, but the basic premise is quite simple. You want all of the people you hire to do things more or less the way you would do them.MF
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.