Many Decisions Are No Decisions (And This Makes Projects Difficult)

13. Juni 2018
Kategorien
Newsletter abonnieren

Effective decision making

Again and again, I am confronted with the situation during projects that I ask for a decision on something and as an answer I get «Oh, that has been already decided…».

No, it is not. A decision has NOT been made until people know:

> the name of the person accountable for carrying it out;

> the deadline;

> the names of the people who will be affected by the decision and therefore have to know about, understand, and approve it—or at least not be strongly opposed to it; and   

> the names of the people who have to be informed of the decision, even if they are not directly affected by it.

An extraordinary number of organizational decisions run into trouble because these bases aren’t covered.

It’s just as important to review decisions periodically—at a time that’s been agreed on in advance—as it is to make them carefully in the first place. That way, a poor decision can be corrected before it does real damage.

These reviews can cover anything from the results to the assumptions underlying the decision. Such a review is especially important for the most crucial and most difficult of all decisions, the ones about hiring, firing and promoting people.

When it comes to making decisions I am of the opinion that people and organizations should use a simple decision-making process in order to make them effective.

Personally, I use the one outlined by Peter F. Drucker. In 1967, he wrote his famous article on effective decision making in The Harvard Business Review that still stands the test of time.

Drucker defines the following six steps for effective decisions.

1) Classifying the problem. Is it generic? Is it exceptional and unique? Or is it the first manifestation of a new genus for which a rule has yet to be developed?

2) Defining the problem. What are we dealing with?

3) Specifying the answer to the problem. What are the “boundary conditions”?

4) Deciding what is “right,” rather than what is acceptable, in order to meet the boundary conditions. What will fully satisfy the specifications before attention is given to the compromises, adaptations, and concessions needed to make the decision acceptable?

5) Building into the decision the action to carry it out. What does the action commitment have to be? Who has to know about it?

6) Testing the validity and effectiveness of the decision against the actual course of events. How is the decision being carried out? Are the assumptions on which it is based appropriate or obsolete?

Tags

Das könnte Sie auch interessieren

Scaling Agile: SAFe

2. November 2015

This is the fourth of six articles on approaches that try to help to scale Agile. For the introduction to this series please read the first article Scaling Agile: Nexus Framework. The second article is about Disciplined Agile Delivery (DAD) and the third about Large Scale Scrum (LeSS). This article will present the Scaled Agile

Weiterlesen

Scaling Agile: LeSS

29. Oktober 2015

This is the third of six articles on approaches that try to help scaling Agile. For the introduction to this series please read the first article Scaling Agile: Nexus Framework. The second article is about Disciplined Agile Delivery (DAD). This article will present Large Scale Scrum, or LeSS. The creators of LeSS, Bas Vodde and

Weiterlesen

Product Backlog Stories …

26. Oktober 2015

Last few weeks I had a few experiences around Product Backlog Items and user stories that made me write this article. Let’s start with a simple observation: many teams I have worked with and people I have met still have the notion that every Product Backlog Item should be in the form of a user

Weiterlesen

Scaling Agile: DAD

21. Oktober 2015

This is the second of six articles on approaches that try to help scaling Agile. For the introduction to this series please read the first article Scaling Agile: Nexus Framework. This article will present Disciplined Agile Delivery, or DAD. Contrary to for example Nexus or LeSS, DAD is not Scrum, it wants to be far

Weiterlesen

Scaling Agile: Nexus Framework

19. Oktober 2015

This is the first of six articles on approaches that try to help to scale Agile. One of the most popular Agile methods is Scrum. Scrum is a very simple framework that describes an one iteration, one increment, one team product development effort. The framework leaves the more complex application of Scrum to the user.

Weiterlesen

Estimating with Wideband Delphi and Monte Carlo Simulation

18. Oktober 2015

During the LeSS training in Berlin last week with Craig Larman he mentioned the best estimating method he knows for any big software project. Wideband Delphi with Monte Carlo Simulation. I agree with him on this one hundred percent. This article will explain what Wideband Delphi and Monte Carlo Simulation is (Part 1 & 2),

Weiterlesen

Budgeting a Scrum Project

11. August 2015

A few weeks ago, I took the training for «Agile Estimating and Planning» with Mike Cohn on FrontRowAgile.com. The training was very good and I think it’s an excellent start for all estimation and planning-related questions. But even after this training, it is still unclear for many on how to make the leap from estimations

Weiterlesen

Scrum Project Success Metrics

30. Juli 2015

Last week I was reading „The 2015 State of Scrum Report“ from Scrum Alliance. In February 2015, Scrum Alliance surveyed almost 5000 people about their use of Scrum. The survey respondents make up a diverse group, representing 108 countries and 14 industries. They reflect a range of functional areas, including IT software development, product development,

Weiterlesen
Previous