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

How Your Rollout in Waves Can End in a Tsunami

14. November 2022

Many multinational organizations are bringing larger system implementations to a screeching halt because they misunderstand what it means to do a rollout in waves.  We’re probably all familiar with the “phased rollout”. A phased rollout means you roll a project out to all targeted users at once but don’t deploy all of its planned functionality.

Weiterlesen

My Talk «Why Big Technology Projects Fail» @ Synergy DevPartner Conference

12. November 2022

In September I was invited by Synergex to give a talk at their 2022 Synergy DevPartner Conference.  The title of my talk was «Why Big Technology Projects Fail« and it covers my personal top ten reasons why this happens so often. Many executives and organisations have challenges with bringing large and complex technology projects to

Weiterlesen

Case Study 16: Nike’s 100 Million Dollar Supply Chain «Speed bump»

16. Oktober 2022

“This is what you get for 400 million, huh?”  Nike President and CEO Phil Knight famously raised the question in a conference call days before announcing the company would miss its third-quarter earnings by at least 28% due to a glitch in the new supply chain management software. The announcement would then send Nike’s stock

Weiterlesen

White Elephant Stampede: Case Studies in Policy and Project Management Failures

15. Oktober 2022

This month one of the book projects I have been part of has been published by Connor Court Publishing in Australia.  The book is titled «White Elephant Stampede: Case Studies in Policy and Project Management Failures«, and it examines the seemingly endless cavalcade of projects that fail to meet their objectives, cost more than expected and

Weiterlesen

Project Complexity Reduction – (Non)-Executive Workshop

19. September 2022

«Complexity is the enemy of execution» is a quote from Tony Robbins, the famous coach, and he is absolutely right.   One of the main reasons technology and other transformation projects fail so often is their (underestimated) complexity.   Managing and reducing complexity in projects should be an urgent concern for any organization.   But

Weiterlesen

(Non)-Executive Workshops

19. September 2022

Currently I offer two high impact workshops for C-level executives, partners at a professional service firm, board members, and business unit leaders in the role of Project Sponsor or Steering Committee Member of large and complex technology projects.  > Project Success Definition > Project Complexity Reduction Both workshops are designed for the Project Sponsor, the

Weiterlesen

Portfolio Review

16. August 2022

 Coming soon…

Weiterlesen

New Project Audit

16. August 2022

Audit means compliant with standards. In this case not PMI or Hermes, but with my standards. It is how I would set up a new project based on my 20+ years of experience with large technology projects.    If you are in the early phase of a large and complex technology project my New Project

Weiterlesen

Doing Something That’s Never Been Done

14. August 2022

Executives, project sponsors, project managers, and steering committee members can learn a lot from how some deep technology startups approach their projects. This isn’t true for all kinds of projects, but it is for every project that involves doing something that hasn’t been done before and has a high risk-reward profile. This isn’t another lean

Weiterlesen

Project Failure Database

8. August 2022

As part of writing Project Failure Case Studies I do a lot of research on failed projects.  Not every project I encounter in court documents and/or news papers is suitable for a case study. Nor do I have time to write a case study on each suitable project failure I encounter. But this research has

Weiterlesen