Design-Free requirements are important for two reasons, and hard for two other reasons.
Design-free requirements are hard because you “know what you want” when you should be documenting “why you want it.” Writing design-free requirements can be hard when you don’t trust your development team to “do the right thing” even though it is not your job to design the solution.
(2 votes, average: 5.00 out of 5)
Loading ...
You have an eCommerce site. You sell products online. Do you cross-sell additional products? Do you upsell to better products? This article explains the difference between cross-sell and upsell, and looks at some real-world data about the effectiveness of both.
(1 votes, average: 5.00 out of 5) Loading ...
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?
(4 votes, average: 5.00 out of 5) Loading ...
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 can design for them?
(9 votes, average: 4.89 out of 5) Loading ...
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.
(2 votes, average: 5.00 out of 5) Loading ...
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.
(1 votes, average: 5.00 out of 5) Loading ...
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.
(1 votes, average: 5.00 out of 5) Loading ...
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 customers, users, and prospects. This article explores that ecosystem in more depth – categorizing the types of conversations that are critical to the success of your product.
(5 votes, average: 5.00 out of 5) Loading ...
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.
(3 votes, average: 5.00 out of 5) Loading ...
(1 votes, average: 5.00 out of 5) Loading ...
Free RSS subscription
(more...)
Subscribe to comments RSS for free
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Feb | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | 31 | ||||
 |
These articles are written primarily for business analysts and product managers. Hopefully they help with thinking, doing, and training. Welcome aboard and let us know what you think!
