Proof of Concept - My product prioritization framework
People fantasize about the ideal experience of working on product—blue sky 0-to-1 work. The reality is this only possible when starting a new company. From that moment on, you are accruing debt: technical, design, and business debt. The reality of joining a company to lead product is the equivalent of getting on a train at its full speed. You can’t simply hit the brakes because so many dependencies are in motion. I’ll share with you my framework for product prioritization and triage when starting somewhere with a lot of existing momentum. Product frameworksLike JavaScript libraries and Land Before Time sequels, there are an abundant amount of product frameworks that exists: MoSCoW, Kano Model, RICE Scoring, Buy a Feature, Eisenhower Matrix, Hypothesis-Driven Development, etc. Though these frameworks are effective and best practices, it can be overwhelming and lead to unnecessary debate on which to use. My hypothesis is the more mature a framework is it feels like a process decision vs. getting value out of it. Because of this, it feels simpler to use a framework when you make one up. Even with a non-standard name it feels less of a weight in adopting it. The product prioritization framework I like to run with people focuses on four core areas: Invest, Ignore, De-emphasize, and Deprecate. The goal of this framework is to orient the moving train and get people oriented in the right direction. The intention of it is to be ephemeral and provide a triage list of priorities. I’ll break down the four areas in more detail. InvestWhether it’s product or people, I’m a believer of doubling down on strengths and what’s working. Focusing on that provides continued value as you refine the weaker areas. Identify the areas in the product that are working well—where customers love and it generates revenue to scale the business. Once you do, pump the gas. This can also mean investing in areas that don’t exist or need additional attention to scale. It should have signals of potential through feedback and data to make a well-informed investment. IgnoreWhen I say ignore, it’s not a bad thing. In fact, things are working well enough where it doesn’t require top attention. This might be a product feature that is flat in growth. Despite having potential, it may not be the top of the priorities you’d invest in. Keep the lights on, monitor, maintain, and support these items. As you make progress on investment areas, it’s typical to see things that were once in the ignore bucket become investment areas. De-emphasizeThis is when you have house guests coming over in an hour and you shove things in the closet to get it out of sight. You need them, but they are detractors from the experience. These are the eyesores that you can’t get rid of just yet. It may be a service you don’t want to scale but it’s important to keep for existing customers. De-emphasize applies to bloated information architecture to improve navigation of your site. There are more things de-emphasized in product experiences than you might imagine. Join any startup and ask how many product SKUs they have. DeprecateAs you go through the first three areas, this is the end of the line. It’s clear there are features or services you need to deprecate and say goodbye to. The saying that it’s harder to remove features than add them is completely true, but you still have to do it from time-to-time if it means the right priority for the business and the product. These features get pruned and should never return. Using this frameworkThe beauty of this framework is you can use it whenever you need to triage a massive initiative. It's not a detailed roadmap of what to do. It's like drawing a map in the sand in the battle field to get people oriented to the new strategy. You could use this as a personal audit as you plan the first 30 days of a new role; share your point of view. It might be in a cross-functional workshop to get other experts in the company to weigh in. Give this a try and let me know what you think, or create your own! Hype linksCollection of what I read and related to this week's post Job opportunitiesInvite your friends and earn rewardsIf you enjoy Proof of Concept, share it with your friends and earn rewards when they subscribe. |
Older messages
What makes a great seed stage founder
Sunday, April 21, 2024
Issue 191: What to look for (and avoid) in early builders ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Success for consumer mobile software
Sunday, April 14, 2024
Issue 190: Traction and adoption for the toughest category ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Managing towards outcomes
Sunday, April 7, 2024
Issue 189: Results over resource management ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
IDDE: The infusion of design and dev tools
Sunday, March 31, 2024
Issue 188: It's time to kill design handoff and create software differently ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
The oil and water problem
Sunday, March 24, 2024
Issue 187: Old and new guards at startups ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
You Might Also Like
🏡 Superb Real Estate Web Designs + 🏆 Challenge Updates
Monday, May 13, 2024
Find out what's new in the UpLabs community this week 👇 Firstly, let's congratulate Rahul Parmar, the winner of our latest 📧 E-mail Client Challenge! Congratulations!! Secondly, don't
Accessibility Weekly #396: Global Accessibility Awareness Day 2024
Monday, May 13, 2024
May 13, 2024 • Issue #396 View this issue online or browse the full issue archive. Featured: Global Accessibility Awareness Day is Thursday "Thursday, May 16, 2024, help us celebrate the 13th
Concept to keynote with Figma and Google Docs
Sunday, May 12, 2024
Issue 194: Taking a keynote presentation from concept to production ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
CSS Queries, Agentic UX, Legibility, Flowfields, Endless Tools
Friday, May 10, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar May 10 2024 Popover API lands in Baseline web.dev The popover
Popover API, AI for Data Journalism, Emission and Bloom, Basic JavaScript, AI Safety
Friday, May 10, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar May 9 2024 Popover API lands in Baseline web.dev The popover
New York Wakes Up
Thursday, May 9, 2024
View in your browser | Update your preferences ADPro Design Month Kicks Off May in New York is a magical time—and it isn't just because our sad, black puffer coats have finally (finally) gone back
Highlighted Text, Generative AI, Cicadas, Devtools Patterns, Serra Case Study
Wednesday, May 8, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar May 8 2024 A Brief Note on Highlighted Text adrianroselli.com
The Problem With Using Social Media as Design Education
Tuesday, May 7, 2024
View in your browser | Update your preferences ADPro Image may contain: People, Person, Accessories, Bag, Handbag, Food, Meal, Adult, Clothing, Hat, Glasses, Fun, and Party Twenty-five days were left
#455: CSS
Tuesday, May 7, 2024
CSS Masonry Layout, Self-Modifying CSS Variables and Hanging Punctuation Issue #455 • May 7, 2024 • View in the browser Smashing Newsletter Dobryi vechir Smashing Friends, When I first encountered CSS
🤯 Immersive Admin Dashboard Designs + 🏆 Challenge Updates
Tuesday, May 7, 2024
Stay Up-to-Date With UpLabs' Latest Design News 🎨 Firstly, let's congratulate Rahul Parmar, the winner of our latest 👾 ChatGPT Redesign Challenge! Congratulations!! Secondly, the end of April