B2B product management doesn't have quite the same volume of usage or "want" being a driver, for example a SaaS platform about coordinating snow ploughs won't be able to gain much more usage during the summer months. With this in mind I am going to take a look at five things I've read this month and pick a key idea from each to build up a toolbox that can be applied.
- Ask the right questions, once we know we are solving the right problem then we are off to a good start. Keeping the bias out of questions and using techniques such as conjoint analysis to find relative preferences are two ways to get useful information from those questions.
- Take a step back and look at things logically. In The Most Powerful Lesson I’ve Ever Learned In Business Mike McCue talks about how he made the decision on a buy out offer where the initial response may not have been in his long term interests.
- Know the impact of your decisions, as discussed in Value-Based Technical Debt Model and Its Application this is often hard. Especially with impact such as technical debt.This quote from page 1 says it all for me
- No, really understand the impact of your decisions:
Product Managers that don’t care about non-functionals are losing you money: https://t.co/KY9y6K99h5 https://t.co/Nfyne8kCCn— Dan Creswell (@dancres) February 7, 2016
- Prioritizing Joy By Drew Colthorp at Atomic Object (Posted August 20, 2013) a slightly different look at building the "right product, instead of merely the most feature-complete product." including brand and emotional response.
- Nina Mehta talks about in What to do with a bullet-pointed list of features
- product insights from wechat
- Six Myths of Product Development - Fallacy 6 ties into why it's vital to know the impact of decisions
- Technical debt isn’t technical - why knowing the problem domain and correctly modelling it is important.
- Real Options Introduction
- Concurrent Engineering is best done Set-Based
- hard to find good article on this that isn't a sales ad, but good intro to narrowing choices in an efficient way.
- How we got rid of time reports The power of asking "Why?"
- On impact and behaviour - previous article on using impact mapping in decision making to meet business goals
- Taking first step with PDCA - what I've described above is very loosely based on the Plan-Do-Check-Act Cycle, find out more here.