Decision-Making Strategies

Jeff Lash recently linked to a page from Marie McIntyre on decision-making strategies.

McIntyre argues that the decision-making strategy you use should depend on factors such as:

Availability of information.
Superiority of one decision.
Acceptance of the decision by others.
Amount of time to decide.

Jeff already covered them in his entry, but the different strategies are:

Make the decision by yourself.
Get information from others, then decide by yourself.
Before deciding, consult with others one-on-one to get their views.
Before deciding, have a group discussion to explore options.
Ask the group to reach a consensus independently.

Notwithstanding the point that the best strategy depends on the circumstances, I have found the third strategy to be under-utilitized and underrated. One-on-one consultation is a powerful facilitation technique. Group discussions can be helpful, but the likelihood of miscommunication is exponentially greater than for a series of one-on-one discussions, often rendering one-on-one discussions more efficient.

Comments

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Citizendium

You're probably familiar with Wikipedia , but have you checked out Citizendium ?

Cauvin

Search This Blog