{"id":9224,"date":"2021-01-13T09:37:10","date_gmt":"2021-01-13T09:37:10","guid":{"rendered":"https:\/\/www.prodpad.com\/?p=9224"},"modified":"2025-01-13T16:26:17","modified_gmt":"2025-01-13T16:26:17","slug":"outcome-focused-product-management","status":"publish","type":"post","link":"https:\/\/www.prodpad.com\/blog\/outcome-focused-product-management\/","title":{"rendered":"Outcome-Focused Product Management vs Feature-Focused Product Management"},"content":{"rendered":"\n

I received the below question from someone who was looking to embrace outcome-focused product management. They were thinking of moving away from that feature-focused approach by adopting a mindset that allowed them to focus on customer problems and to ensure their product\u2019s features were actually worth being built. <\/p>\n\n\n\n

Here’s what my advice was:<\/p>\n\n\n\n

Question: What are some resources for pivoting from an execution\/features\/roadmap PM to a vision\/strategy\/metrics PM?<\/strong><\/p>\n\n\n\n

First of all, congratulations on making a huge change. Going from a feature-focused product manager to an outcome-focused product manager can be a really difficult transformation, so good job! Below I\u2019ve outlined the key points to making the move over to an outcome-focused approach and linked out to some handy resources. <\/p>\n\n\n\n

Outcome-Focused Product Management Starts With a Product Vision<\/strong><\/h3>\n\n\n\n

First things first, start with mapping out your product vision. You can do this on a canvas of some sort, there are plenty of those going around. Some to consider are lean UX canvas or business canvas. This template<\/a> is a good place to get started too.<\/p>\n\n\n\n

Once you have your vision outlined, you can start outlining your objectives. For example, if part of your vision is to be the number one downloaded app in the Apple Store x weeks running, perhaps one of your objectives might be \u201cIncrease User Growth\u201d. The important thing here is to remember objectives are to be quantitative and measurable. Here is a nice piece<\/a> on writing objectives and key results to align your team.<\/p>\n\n\n\n

\"Outcome-focused
Set clear objectives in ProdPad to keep outcome-focused.<\/figcaption><\/figure><\/div>\n\n\n\n

Prioritizing Problems Not Features<\/strong><\/h3>\n\n\n\n

The next part of outcome-focused product management can be achieved bottom up or top down<\/a>, depending on how you wish to prioritize. This means you could start looking at potential problems to solve and then map ideas and feedback, or you could look at feedback first and define which best fit your objectives. It doesn’t really matter to be honest, as long as whatever work you choose to do actually maps back to those objectives. Remember, objectives are there to keep you aligned. This means that instead of working on random stuff, you’re working on stuff that aligns to what you’re trying to impact.<\/p>\n\n\n\n

My next piece of advice would be, make sure that whatever projects you choose to work on are written down as potential problems to solve, not as features. That is, instead of writing that you’ll work on a “Slack integration,” instead write: “How can we best support users that work on Slack in order to integrate and collaborate with our app more closely?” This gives you the space to actually understand how you might solve the problem better. We’ve got a really good example of what good OKRs and initiatives look like in our Sandbox<\/a>. <\/p>\n\n\n\n

Learning From Each Outcome To Get Better Results<\/strong><\/h3>\n\n\n\n

When it comes to writing down outcomes and looking back at your work, remember there is no such thing as failure<\/a>. I mean, yes, you might fail – but that’s ok. The whole point behind outcome-focused product management is to allow yourself to fail, and to use this failure (or likewise, potential success) as an opportunity to learn.<\/p>\n\n\n\n