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
-
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
-
What product should I build?
You can only solve a big problem that changes the world if you solve a problem that is deeply personal to you. Two great examples and why they worked: Roy Raymond was a sad pervert. He'd buy bras and panties at the department store and all the clerks thought their thoughts about him. Roy felt embarrassed. He wasn't really a pervert. He just wanted to buy lingerie for his girlfriend. So he solved this major problem he was having. He created a space where men could feel comfortable coming in and buying sexy lingerie for their partners. He called it Victoria's Secret. But Roy, by solving this important personal issue for himself, apparently solved the same issue for many other men. First year sales were over $500,000 and he quickly opened up three more stores. In 1982 he sold Victoria's Secret for one million dollars before trying multiple other businesses that ended up failing. One MILLION Dollars. A decade later Victoria's Secret was worth over a billion dollars but Roy Raymund was nearly bankrupt and had missed the huge run-up in it's value. -- Picture New York City in the late 1800s on a rainy day. It was disgusting beyond belief. 150,000 horses transported people up and down the busy streets. Each of those horses, according to Super Freakonomics, dropped down about 15-30 pounds of manure. That's up to 4.5 million pounds of manure A DAY on the streets of NYC. And now imagine it raining. Would you cross the street? How long could this last? How long would the city survive without being infested with crap and all the diseases brought with it. What would happen as population of both men and horses increased? Was someone working on inventing a gigantic manure scooper? How would this problem get solved? It never got solved. Instead, Henry Ford invented the assembly line to mass produce cars. Every horse lost their job. People began to drive cars. Manure problem solved. -- In both cases there is a common theme. Someone outside the industry solved a problem that was personal to them that then changed an industry forever. Roy Raymund wasn't a fashion designer or a retailer. He worked in the marketing department of Vicks, which makes over the counter medications. Henry Ford, I don't think, ever worked in the manure industry. Instead, each person focused on a problem that was important to them. A problem that excited them at that moment in time. Raymund wanted to avoid being embarrassed in the future. Ford wanted an efficient way to make cars. The ONLY way to change the world is to solve a problem that is important to YOU. They had to choose themselves for success before they could save the world. Raymund had to convince himself that he didn't belong in the marketing department of a division of Procter & Gamble. He borrowed $80,000 and took the big risk of starting a business. Ford had to survive numerous failures and bankruptcies in order to find a cheap way to make cars. He would abandon investors, people who supported him, and even companies named after him, in his quest to solve his problem in his own way. Nobody gave them permission. And neither of them set out to change the world. They only wanted to solve a problem that was personally important to them. It's unfortunate that often we forget that choosing ourselves is not something that happens once. It has to happen every single day. Else we lose track of that core inside of us that solves problems and is able to share them in a way that makes the world a better place. Ford forgot this and became obsessed with Jews. Ford is the only American that Hitler mentions in Mein Kampf: "only a single great man, Ford, [who], to [the Jews'] fury, still maintains full independence...[from] the controlling masters of the producers in a nation of one hundred and twenty millions." And what happened to our embarrassed marketing manager that has ignited the passions of men and women for the past 30 years? Roy Raymund saw the value of Victoria's Secret jump from the one million he sold it for in 1982 to over a billion dollars a decade later. He failed in business after business. He got divorced. Then at the age of 46, my age, he drove to Golden Gate Bridge, jumped off it and killed himself. Before you can save the world you have to save yourself. But you have to relentlessly do it every day. Sometimes the train wakes me up at night and I feel scared. What will the world be like for my children? I won't always be able to help them. I don't even know if I do enough to help them now. And then I remember. I'm alive for another day.JA
-
What is the best way to find full stack mobile developers who are willing to work with me for equity, and what is fair compensation?
It's highly unlikely that you will be able to find competent full-stack mobile developers willing to work with you for equity, but if you do, "fair" compensation would be 50% or more of the equity in the Company. Approaching any developer with just an idea, diminishes your credibility as a potential co-founder. Here's why: If you're non-technical, you must show a "relentless resourcefulness" in moving your idea forward. This means finding the money necessary to get an MVP or even click-able prototype completed to show that while you might not be technical, you have the ability to raise money, and have enough product sense that you can articulate that into a prototype. If you can't raise or spend the relatively small amount of money required to successfully build a prototype, what evidence are you providing that developer that you are going to be able to create value for the business long-term? Full-stack mobile developers (although this is often quite a misnomer) are one of the most in-demand skill-sets of all Silicon Valley companies. That means that you're competing against established companies that can pay top dollar, and still provide meaningful equity incentives as well as recently funded startups who have further along the road in turning their idea into reality. I would suggest that you look at hiring contractors (I know of some great mobile dev shops that are reasonable) to build your first version. Expect to go solo at least until you have some form of early prototype. Then, you're in a much better position to attract a technical co-founder. Happy to talk you through any of this at any point.TW
-
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
-
I've been working on an app concept for 6 months and built an MVP. Is it better to pay a development firm to build or hire a developer as a cofounder?
I have built two software companies by hiring out the development work. I sold one for a decent sum during the dot com era (circa 1999). I remain a shareholder in the other one. I currently work with amazing development company on behalf of one of my clients. Here are some things to consider. 1. Do you really want to give up equity? If not outsource. 2. How fast do you want to get to market? If sooner than later, outsource. 3. How capitalized are you? If undercapitalized, either outsource offshore (which runs about 20% of US rates), or bring on an equity development partner. I offer a free call to first time clients. Let's chat and I'll give you some great advice from three decades of experience. Just use this link to schedule the free call: https://clarity.fm/kevinmccarthy/FreeConsult Best regards, Kevin McCarthy Www.kevinmccarthy.comKM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.