In last week’s article (and the GrandView webinar) I talked about using models of customer behavior as a method of understanding and investing in your markets. One example I used is what I call a trust pyramid – representing how people have different levels of trust in the assertions of others. This article explores the idea of the trust pyramid in more detail.
Category Archives: Product Management

The Value of Insights
Intellectual Property. The legal jargon definition of this term has come to effectively mean “something I’ve patented, copyrighted, or hold as a trade secret.” A more general interpretation is “an idea.” For product managers, the most valuable ideas are insights.

Product Managers & Innovation
Thanks everyone for the great conversation in the most recent #prodmgmttalk chat session! This week, Roger Cauvin inspired us to think about product managers as innovators – or enablers of innovation. Each week, I find myself thinking about at least one of the #prodmgmttalk questions long after the hour is over. This week’s thought – organizations prevent product managers from innovating.

Nokia’s Smartphone Strategy – Maximin
Nokia, the Finnish mobile phone manufacturer, is getting clobbered as their market rapidly moves away from them. Recent analyst reports show that Android and iOS (Apple’s platform) based phones are rapidly gaining market share. Nokia sells neither. Nokia has a major press event in a few hours, where they will announce their smartphone strategy. I think a maximin strategy is both likely and correct.

Market Insights and Collaboration
In this week’s #ProdMgmtTalk, one of the livelier discussion topics was around gaining insights into your market – and what does that mean (to you)? Steven Haines was the speaker for this session who prompted us to think, and pushed us to rethink our views on market insights. What a great example of collaboration among product managers!

Don’t Prioritize Features!
Estimating the “value” of features is a waste of time. I was in a JAD session once where people argued about if the annoying beeping (audible on the conference line) was a smoke alarm or a fire alarm. Yes, you can get to an answer, but so what?! The important thing is to solve the problem.

Provocateurs Gather the Best Requirements
Ask someone what they want, and they’ll tell you they want a faster horse. Provoke them, and they’ll tell you they have a ‘get there faster’ problem, an ‘equine waste disposal’ problem, and issues with total cost of ownership.
Read the rest of the article …

A Prototype is Worth a Thousand Lines of Code
A picture is worth a thousand words. A prototype is worth a thousand lines of code. Two key elements of product management – and of agile development are elicitation and feedback. Low fidelity artifacts can significantly improve both. Polished, codified prototypes can create problems that prevent you from getting the benefits of communication.

Cadence Versus Risk
I’ve been thinking about the software development process. Big, upfront, design and requirements. User research and analysis. Market insights, gained on exploration or over time. Release cadence – how quickly you get, and incorporate, feedback from your customers about your product. How quickly you react to your competitors’ reactions to your actions.



