Problem-Opportunity Scoring Model

Problem-Opportunity Scoring Model

Needs can come from different users of your product, or from different internal stakeholders who sometimes may conflict with each other. For example, one stakeholder may want you to incorporate in your product the ability to snap photos and post them on social media. Another stakeholder may want an Artificial Intelligence (AI) system that is able to understand human language

The product manager is the monkey in the middle – interview with Suman Sarkar

The product manager is the monkey in the middle – interview with Suman Sarkar

In this episode of Product Bytes we interview Suman Sarkar, Head of Digital Product Management at OneMain Financial (NYSE: OMF), who shares product leadership lessons managing teams of product managers at large and small companies. This is an excerpt from the interview, published in our Product Bytes channel. Suman: I am Suman Sarkar. How do I introduce? So, most of

The four pillars of great product teams – interview with Toby Russell

Man looking for car

In this episode of Product Bytes we interview Toby Russell, co-CEO of Shift (NASDAQ: SFT), who shares product leadership lessons from building Shift. This is an excerpt from the interview, published in our Product Bytes channel. Toby: I am Toby Russell. I am the co-CEO of Shift. We run a company that essentially sells cars online and we are the

User Stories are not requirements

User Stories are not requirements

I always struggle with the word “requirements”. This is how specifications and functionalities are normally called when working on a project. Requirements create a blanket of necessity and limit the empowerment of product managers to be effective at solving problems. The word requirement, and its verb counterpart to require, in their essence define something that is “required”, “needed”, “expected”. The