Software product success.
Your company is building out a toolkit to support third-party developers. You’ll need a bunch of different types of widgets – combo-boxes, text entry fields, domain-specific controls, etc. You’ve got a long list of desired controls from your customers. You’re agile. What do you build first?
Perpetually intermediate (competent) users. Users who briefly exist as novice users and never become experts. Most of your users are competent, and you should design for them. Competent users have different needs and different expectations than novice or expert users. How do you know your user’s competency levels, so you […]
Steven Haines, author of The Product Manager’s Desk Reference, recently gave a webinar on effectively using product roadmaps for the Technology Product Management Council at Forrester Research. You should check it out.
Kano Analysis, while initially created to understand customer satisfaction with features, can be used by product managers to better understand customer problems. I gave a presentation last week for the Product Management View webinar series on Kano Analysis for product managers.
In the previous article on the Conversation Ecosystem, I introduced a hierarchy of increasingly valuable conversations. Some great feedback from you inspired a better visualization.
The previous article, The Conversation Economy, lays out a perspective of approaching the success of your business, and of your product, in light of the conversations that flow around them. You can view the ecology that defines your market in terms of the kinds of conversations you’re having with your […]
The industrial age is behind us. It was surpassed by the knowledge economy, rapidly evolved into the attention economy. Successful companies realize that attention comes as a result of conversation. We’re now in the conversation economy.
You website is not just a tool, it is a service, and therefore a product. Your prospects make buying decisions based on your website. Your customers make repeat-buying decisions based on your website. You risk losing future customers because of your website.
Concise requirements give your team a useful, easy to read and easy to change understanding of what must be done. Great requirements exist to do three things: Identify the problems that need to be solved. Explain why those problems are worth solving. Define when those problems are solved.