Decision-making is an important everyday process. When making important choices we need to be aware of and avoid decision-making biases like Outcome Bias, Cognitive Bias and Confirmation Bias. To be able to do that we can employ the WRAP model for decision-making.

Widen Your Frame

Consider alternative solutions for the problem to avoid narrow framing. Think about opportunity costs, multitrack, explore analogies or good practices.

Reality Test Your Assumptions

Fight confirmation bias by testing and running experiments. Look into details, consider outside and inside views, seek additional data, play the devil’s advocate.

Attain distance Before Deciding

Eliminate short-term emotions by shifting perspective. Postpone the decision, pretend to give advice to a friend, or use the 10 minutes/ 10 months / 10 years rule.

Prepare to Be Wrong

Expect both to be wrong or right, considering the VUCA world. Do not overestimate your ability to predict the future, be prepared to explore the outcomes as they are.

WRAP Decision-Making Process Overview

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.