the startups.com platform about startups.comCheck out the new Startups.com - A Comprehensive Startup University
Education
Planning
Mentors
Funding
Customers
Assistants
Clarity
Categories
Business
Sales & Marketing
Funding
Product & Design
Technology
Skills & Management
Industries
Other
Business
Career Advice
Branding
Financial Consulting
Customer Engagement
Strategy
Sectors
Getting Started
Human Resources
Business Development
Legal
Other
Sales & Marketing
Social Media Marketing
Search Engine Optimization
Public Relations
Branding
Publishing
Inbound Marketing
Email Marketing
Copywriting
Growth Strategy
Search Engine Marketing
Sales & Lead Generation
Advertising
Other
Funding
Crowdfunding
Kickstarter
Venture Capital
Finance
Bootstrapping
Nonprofit
Other
Product & Design
Identity
User Experience
Lean Startup
Product Management
Metrics & Analytics
Other
Technology
WordPress
Software Development
Mobile
Ruby
CRM
Innovation
Cloud
Other
Skills & Management
Productivity
Entrepreneurship
Public Speaking
Leadership
Coaching
Other
Industries
SaaS
E-commerce
Education
Real Estate
Restaurant & Retail
Marketplaces
Nonprofit
Other
Dashboard
Browse Search
Answers
Calls
Inbox
Sign Up Log In

Loading...

Share Answer

Menu
Product Management: Which technique is the most used to prioritize features and what's the best tool to use to do that?
KP
KP
Keith Pieper, Startup Product Bootstrapper, Maker, Hacker answered:

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.

Talk to Keith Upvote • Share
•••
Share Report

Answer URL

Share Question

  • Share on Twitter
  • Share on LinkedIn
  • Share on Facebook
  • Share on Google+
  • Share by email
About
  • How it Works
  • Success Stories
Experts
  • Become an Expert
  • Find an Expert
Answers
  • Ask a Question
  • Recent Answers
Support
  • Help
  • Terms of Service
Follow

the startups.com platform

Startups Education
Startup Planning
Access Mentors
Secure Funding
Reach Customers
Virtual Assistants

Copyright © 2025 Startups.com. All rights reserved.