The wisdom of crowds helps us avoid stupid decisions. Unfortunately, it also prevents innovative, passionate, fantastic decisions. Collective Intelligence is collective insipidness. We need to keep the inputs of individuals in the mix.
Category Archives: Prioritization
Posted in Design, Prioritization, Product Management, Requirements, Requirements gathering
Tagged brainstorming, collective intelligence, dumbness of crowds, eliciting requirements, idea seeding, managing data, passion of individuals, Prioritization, prioritizing requirements, requirements elicitation, Requirements gathering, wisdom of crowds
Leave a comment
How To Not Suck At Design
topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2006%2F11%2F15%2Fhow-to-not-suck-at-design%2F”, “style”: “big”, “title”: “How To Not Suck At Design” }); Michael Shrivathsan just wrote an article presenting five tips for creating products with great design. Michael’s List Start with the user interface. [Roger Cauvin adds, start with a working first iteration] Work closely with UI designers. Pay attention to details. Simpler is [...]
Interrelation Digraphs As Prioritization Tool
Prioritization can be hard, especially when we’re dealing with a lot of variables. Peter Abilla, at shmula.com takes a fairly esoteric tool (interrelation digraphs) and applies it as a prioritization tool. Opthamologists have learned that they can’t show us a bunch of blurry images and have us tell them which one looks the best, and then prescribe a corrective lense. They have to ask us “Is it better like this? Or better like this?” Peter’s approach does the same thing, but with a quantitative edge.
Posted in Communication, Design, Prioritization, Product Management, ROI, Requirements, Software development, Usability, Writing
Tagged documentation, documenting upgrades, goal-driven documentation, managing data, passion threshold, prioritizing upgrades, software documentation, software upgrade, suck threshold, upgrade prioritization, upgrade priority, upgrades, user centric documentation
Leave a comment
Vote Early And Often – Getting Value From Brainstorming
Brainstorming can be a simultaneously fun and effective technique for identifying software features or requirements. We’ve written previously about how to facilitate a brainstorming session and how to leverage the results. Timothy Johnson shares another way to use the results effectively. His way is more fun, and maybe just as effective.
Posted in Prioritization, Requirements, Requirements gathering
Tagged brainstorming, brainstorming facilitation, brainstorming requirements, elicitation, eliciting requirements, facilitation, gathering requirements, managing data, Requirements, requirements elicitation, Requirements gathering
3 Comments
Product Managers Are Critical To Success
topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2006%2F05%2F19%2Fproduct-managers-are-critical-to-success%2F”, “style”: “big”, “title”: “Product Managers Are Critical To Success” }); The product manager role is strategic. Product managers identify valuable problems in the market and determine which of them should be solved with software. They create a vision and strategy for solving those problems. Everything else happens in that context. James Shore [...]
Epicenter software design – 37signals applies Kano
Jason at 37signals has started a discussion about feature prioritization with his recent post. He describes the epicenter of software as the most important, must-have feature. He argues that this feature should always be the one that is built first, since without it you don’t have an application. This is the same approach we reccommended in our recent post about prioritizing requirements with Kano analysis. The epicenter, while critically important, isn’t sufficient to drive success for the software.
Posted in Prioritization, Product Management, Requirements
Tagged differentiated innovation, innovation, innovative requirements, kano, Kano analysis, managing data, prioritizing features, prioritizing requirements, requirements prioritization, software feature priority, software prioritization
4 Comments
Latest Articles
Comments on all Articles
