Sunday, 29 August 2010 00:00

The Failure in Gating Processes

Rate this item
(0 votes)

Gate with a stop sign

The policy reads, "Before you can proceed, the PMO needs to approve the design gate." So, you begrudgingly wind down the project so the slowest members of the design team can catch up. A week, maybe two, sometimes even more flash by. The rest of the project team starts finding work on other projects. Once the PMO finally gives the project the green light, you will need to wait for people to complete those other tasks before they can focus on your project. Precious time is lost.

Why Are We Using Gates?

I am not claiming to have done an anthropological study, but I can make an educated guess into origins of this practice. I can imagine a project team making a decision to start building some part of a product prior to completion of the entire design. They felt comfortable that designs were complete enough to start building and they accepted the risk of some rework. Unfortunately, there was a fundamental design flaw and the rework was significant. Senior managers or the customer got upset and required their review and approval prior any major work proceeding. Voilà, the gate was born.

Poor Management

Often justified as being a method to ensure management is engaged with the project, I see gates as a way to ensure that management is anything but engaged. It creates a mentality that management does not need to monitor progress, drop in on meetings, talk to team project team members, or any of the practices that good leaders and managers do to ensure they can spot problems early. Instead, gate processes create an atmosphere where managers feel justified in ignoring the project, since every couple of months the project will stop and wait for them.

Gate review meetings then become a game where project managers try to get their projects to pass the gate without any hassle—minimizing troubles as to avoid management attention. Attention brings "help" from people unfamiliar with the intricacies, interrelationships, and individuals in the project.

Now, besides trying to reassemble the team, the project manager needs to assign them work from task force assigned to fix the project. A task force that assigns works instead of doing work.

Hurry Up And Wait

The effect on the project team is immense. Stopping work to wait for a bureaucratic process destroys the team's sense of urgency. If the project can wait for a group of managers to approve its progress, especially if they have little background in the project's domain, then the project can wait for the team members to do other work. The project team loses interest in completing tasks quickly as the energy and excitement slowly dwindles. Any concept of urgency is lost and team members take a lackadaisical approach to completing their tasks.

What Was I Doing?

To make matters worse the team needs to remain billable, so they are assigned to new tasks. These are necessarily off the project, since it is waiting for gate approval. Besides the inherent slowing of the project brought on by multitasking, the break in the project means that people need to refocus repeatedly on various tasks. The distraction and lack of continuity removes people's ability to concentrate on the product and mistakes increase. Worse, fine points in the product are lost. The quality decreases and the customer gets frustrated.

Missed Opportunity

Gates prohibit work in the follow-on phases until all other work catches up. Yet, allowing some work to proceed shows areas of weakness long before other groups have wasted time with a faulty design. This is the concept behind prototypes, mock-ups, wire frames, and iterative processes, such as agile. By allowing given areas to move ahead, designers, builders, and customers can judge the validity of a concept and use semifunctional tangible product to determine its usefulness. Therefore, gates remove valuable exposure of the product to the customer.

Stakeholder Engagement

The solution is better stakeholder engagement. Monitoring and experiencing the project, its progress, risks, and challenges as they appear, rather than quarterly, removes the need for gates processes. This is one of the powerful advantages of an agile methodology. Management is continuously apprised. The update does not even wait for the end of the iteration, it happens in the daily scrums.

However, I am not simply being an agile bigot (although I am one). I am highlighting one of the many ways that senior management causes more problems for projects than they have solved. The process of managing and the art of leadership are lost as people struggle climb the ladder and promote themselves.

Read 12856 times

Related items

  • People vs Process Track Session/Keynote Example

    If you want educational keynote many of our presentations can be keynotes or track sessions. In the example below, the presentation People or Process: Which Impacts Project Success More? is given as a track session.  

    Example People vs Process keynote as a track session

    This session was given at the PMI Sioux Empire Professions Development Day help in Sioux Falls SD on September 9, 2014.

  • Transform Your Project Leadership: For Professionals Leading Projects or Company Initiatives

    Todd Williams contributed Chapter 7, "Leaders Listen." You can buy it on Amazon.

    More coming soon!

  • Filling Execution Gaps: How Executives and Project Managers Turn Corporate Strategy into Successful Projects
    What Filling Execution Gaps Covers

    Filling Execution Gaps

    by Todd C. Williams
    ISBN: 978-1-5015-0640-6
    De G Press (DeGruyter), September 2017

    Project alignment, executive sponsorship, change management, governance, leadership, and common understanding. These six business issues are topics of daily discussions between executives, middle management, and project managers; they are the pivotal problems plaguing transformational leadership. Any one of these six, when improperly addressed, will hex a project's chances for success. And, they do—daily—destroying the ability companies to turn vision into value.

    Check it out on Amazon or the Filling Execution Gaps website

    Without the foundation of a common understanding of goals and core concepts, such as value being critical to success, communication stops and projects fail.

    Without change management, users fail to adopt project deliverables, value is lost, and projects fail.

    Without maintaining alignment between corporate goals and projects, projects miss their value targets and projects fail.

    Without an engaged executive sponsor, scope increases, goals drift, chaos reigns, value is lost, and projects fail.

    Without enough governance, critical connections are not made, steps are ignored, value is overlooked, and projects fail.

    Too much governance slows progress, companies cannot respond to business pressures, value drowns in bureaucracy, and projects fail.

    Without strong leadership defining the vision and value, goals are not set, essential relationships do not form, teams do not develop, essential decisions are not made, and projects fail.

  • Filling Execution Gaps: Building Success-Focused Organizations

    Executives define vision, strategy, and goals to advance the business. Projects enable companies to meet those goals. Between strategy and projects, there is a lot of work to be done—work that lays the foundation for project and operational success. Through experience and research, six common gaps exist in organizations that inhibit project success—an absence of common understanding, disengaged executive sponsors, misalignment with goals, poor change management, ineffective governance, and lackluster leadership.

  • Get Recognized as a Leader: Four Core Leadership Actions

    Leaders make decisions. This requires a core set of actions to gather the best information, hear out the concerns of others, and making a decision that everyone will follow—even if there is not unanimous agreement with the decision. Although there are hundreds of actions leaders must take, there are four core actions that all great leaders do—listening, dialog and discussion, selling a vision, and eliminating blame. This session will discuss those actions in a roundtable format that we call a "What Would You Do?" session. In these sessions, the presenter acts as a moderator spending 10 to 15 minutes per topic working with the audience talking about what the action is, how to best do it, and hearing from the group on how they have carried out the action. This brings significant audience interaction, involvement, and broader education. 

Leave a comment

Filling Execution Gaps

Available Worldwide

Filling Exectution Gaps cover

Filling Execution Gaps is available worldwide. Below are some options.


PG DirectLogo
Limited Time Price $20.99
Amazon logo
Book or Kindle
Flag of the United States Canadian Flag Flag of the United Kingdom Irish Flag Deutsche Flagge
Drapeau Français Bandiera Italiana PRC flag
Japanese flag
Bandera de España
Flag of India
Bandera de México
Bandeira do Brasil
Flag of Australia
Vlag van Nederland
DeG Press Logo
Barnes and Noble Logo
Books a Million Logo
Booktopia Logo
Worldwide: Many other
book sellers worldwide.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.