How to Get Rapid Decision Making to Work in Your Projects

In last week’s article, we looked at how to make robust project decisions. This week, I want to turn up the pressure to look at rapid decision making in projects.

What can you do to maintain the rigor, transparency, and reliability of your decision making, but also turn up the speed?

How can you make good decisions in a hurry?

Rapid decision making in projects boils down to two principal strategies. In this article, we will look at each of them, and how to make them as effective as possible, in balancing the need for speed with the requirement for rigor.

Rapid Decision Making in Projects

The Two Strategies for Rapid Decision Making

In the previous article we saw that there are two processes for evaluating a decision: logical and intuitive.

The logical process is rational, deliberate, and takes a lot of effort. The intuitive process is faster and relies on our innate pattern-forming abilities.

However, we can only form reliable patterns that form the basis of sound gut-instinct decisions where we have a strong base of experience to call upon.

So, the two strategies for rapid decision making are clear:

• Strategy 1: Speeding up the logical process
• Strategy 2: Using the intuitive process appropriately

Before we Start: The Precursor to Rapid Decision Making

If you need to make a rapid project decision, your first priority must be to get right to the heart of what the decision is about. What is at stake, and what matters most? There is a wonderful quote from Roman emperor and philosopher, Marcus Aurelius:

“This thing, what is it fundamentally? What is its own constitution? What is its substance and material?”

Understanding what your decision is really about will help you to assess which process to use. And it will also allow you to test your decision before committing to it. Look beneath the surface of the either/or choice that many decisions offer. Fist of all, what is at stake? Therefore, ask yourself: ‘what matters most here? Often there is a fundamental principle, which underpins your choice.

Another element her is to understand what the decision is about, in terms of technical matters. If it is intimately about something for which you are a true expert, a rapid gut-instinct decision may be a safe approach. But if you don’t have deep expertise and substantial experience, even a strong gut instinct can lead you in the wrong direction, and you need to set it aside.

Speeding up the Logical Decision Making Process

There will be plenty of times when you will not have the experience to rely on your gut for rapid decision making in a project. This is especially true at the start of your career. So how can you speed up rational decision making?

Waigaya – hear the babble

Making rapid decisions alone is a recipe for failure. Compelling yourself to hear lots of other people’s views in a short time can open you to the best decision. This is the basis of an approach that started at Honda, called Waigaya. It is one I think many project managers could adopt, with much benefit. In Waigaya, as soon as there is a problem arises and you need a decision, you call together a group of workers. And Waigaya has four guiding rules.

1. Everybody is equal in waigaya. So you can all express your thoughts and not fear criticism for them.
2. The group must discuss all ideas until they are either proven valid or rejected.
3. Once someone shares an idea, they don’t own it anymore. It belongs to group, which can do whatever it wants with the idea.
4. At the end of a Waigaya session, there are decisions. Form this, you can set responsibilities for who will do what, and by when.

This works well, because you can get two things: the chance to listen and reflect on different perspectives, plus a sense of how a group of people feel about different decision options. In a relatively short discussion, a sound decision can emerge organically. Learn more about Waigaya from an excellent article: For Honda, Waigaya is the Way.

Experiments, Pilots, and Prototypes

One way to make a rapid decision that has little risk attached to it is to decide on an experiment. Pilots and prototypes are a way to learn and inform a strong decision. So, if in doubt, commission a test. You will be moving your project forward. And, at the same time, you will also be managing your risks and establishing the basis for good decisions down the line.

What if…

Decisions often fail because what we expected to happen did. But so too did an unexpected consequence. Do a rapid survey of how your decision could affect every aspect of your project: each stakeholder, every risk, all the work packages, any deliverable. Use a simple checklist approach of everything your choice could impact upon. So for example, use a list like this:

• Team members
• Data integrity or security
• Stakeholders
• Schedule
• Costs
• Availability of resources (people, materials or assets)
• Technology
• Regulated activities
• Health & Safety
• Public perceptions or reputation
• The environment
• Physical security
• Error rates
• Stress

Fail-safe

Is there a way that you can cast your decision so that, if it is wrong, the outcome is a safe one with minimal damage. For example, what procedures can you put in place that will catch problems quickly and halt the effects?

Using the Intuitive Decision Making Process Effectively

The alternative approach to rapid decision making is to rely on your gut instinct; your intuition. This is only going to be reliable when you have a great depth of knowledge and experience to call upon. But if you conclude that this is the case, what can you do to optimize the process?

We’ll answer this from two points of view. First, I’ll offer some suggestions for how to access your intuition. And second, I will mention how to protect against a faulty intuition.

Immersion and Incubation

This may not sound like speeding things up, but your intuition needs two things, to process a decison. First, it needs to be immersed in all of the details of the problem. Malcolm Gladwell* evocatively labels the process your intuitive mind goes through as ‘Thin Slicing’. When your brain absorbs a whole raft of detail in a complex situation, it is able to extract the salient elements from the rest, using your accumulated experience to see what really matters.

Sometimes the process of sifting and sorting the patterns can take time. So allow your brain some incubation space. Soak up the facts and then go for a walk.

* In his book, Blink (US, UK).

The Ground Truth: Going to the Gemba

One way to immerse yourself effectively is to lace yourself physically where your project decision will impact. The military call this ‘the ground truth’. They recognize that maps and charts, and second-hand reports represent only a part of the reality. The truth is on the ground. In Japanese manufactiuring, there is a similar concept. To solve a problem or make a decision, the team will ‘go to the Gemba’. The Gemba is the place where it happens.

Who knows what you will spot at the Gemba, that you may not have become aware of from behind a desk?

How to Hear your Gut: Pausing and A Trial Solution

But now you face a different – and difficult – challenge. Projects are busy affairs. And that makes it very hard, sometimes, for a Project Manager to hear that quiet voice of your intuition. So how can you know what your gut is telling you?

I have two approaches that I use frequently.

Approach 1: Pausing
In fact, I do more than pause. After immersion and incubation, I need the space to hear what my intuition is trying to say to me. So i will stop doing any busy-thinking, or active-doing. Two ways that work particularly well as deliberate approaches are my preferred habits. Firstly, just going for a walk. And second, going for a coffee (rather than taking one at my desk). Anything that separates you from what is going on, will give your mind a chance to calm down, and for your intuition to emerge. Of course, I often get the answer in the shower, for just the same reason.

Approach 2: Trial Solution
If you don’t know what your gut wants you to do, make a random choice. And then ask yourself how you feel about it. There is nothing like a coin-toss to reveal which option is best. You might make a random choice and then feel ‘yes, okay, that’s good’. Yet this is very different to making a random selection and feeling ‘hmmm. I’m not sure about that.’

Monitor and Review Cycle

Any rapid decision making needs a protection against error. And the simplest is the cycle of monitoring the effects of your decision, reviewing them, and taking control if you need to. As we discovered in an earlier article about Boyd’s OODA Loop, a more rapid cycle time gives you greater control. As a result, your decision caries less risk. So it is a better decision, because of the rigor you place around how you implement it.

What are your Tips for Rapid Decision Making in Projects?

Add your own tips and experiences to the comments section below.