Sunday, 13 May 2012 00:00

Projects Need Leadership, Not Management

Rate this item
(0 votes)
¿Le gustaría leer este artículo en Español?

Acceda al PDF aquí
O... léalo en el sitio web de http://www.projectcharter.com

"Project management is easy. We have been managing people for hundreds of years. Just take any manager, give them a project, and tell them to get it done." Experienced project managers will accurately predict the end of this story—there is a disproportionate chance this project will fail. Rather than "manager" being the key noun, a leader is required to deliver project value on time and within budget. To distinguish the project manager further—functional managers need only manage subordinates, while successful project managers lead extended project teams. This fundamental difference drastically increases the project manager's scope of the responsibility, since the project team includes an entire flock of stakeholders.

The Project Managers Purview

Scope of Functional and Project Managers Functional managers are primarily responsible for their direct reports—the classical organization chart (refer to lower portion of the figure to the right). On regular occasions, they coordinate with their peers or a boss, but their focus is on their staff. Project managers, on the other hand, must align a much larger array of people. Besides their project team and peers, they have an entire organization chart above them consisting of the project's stakeholders. In actuality, this loosely knit collection could be a significantly larger population than their well-organized subordinate project team.

Where I currently live, near Portland, Oregon, there has been a twenty-year long effort to build a new bridge across the Columbia River. The two, currently steel, structures, one constructed in 1917 and the other in 1958, were built long before seismic design and construction techniques entered into the mainstream. They are arguably the weakest link in the 1400-mile long freeway and only draw-bridges in the interstate highway that traverses Washington, Oregon, and California. There is a legitimate concern about their ability to sustain a reasonably sized trembler. Without a doubt, it will be a massive project building this multimodal, dual-decked, mile-long bridge. It will take thousands of designers, managers, and construction workers. However, consider the stakeholders involved. They include: the federal transportation agencies, the US military (a reserve airbase is nearby), the Coast Guard, two state and two city governments, two transit agencies, light-rail proponents and opponents, bicyclists, pedestrians, local toll-paying citizenry, state tax payers (many hundreds of miles away wondering why they need to pay anything), boaters, businesses, truckers, commuters, environmentalists, and Native Americans, just to name a few. All have special interests; all can muck up the best project plan. Few of them know anything about project management; none of them care about the woes of the project manager. Without a doubt, the project manager will need to navigate more obstacles from the stakeholders than from the team actually building the bridge.

Want to read more?

Strategy, alignment, communication of goals is not easy. Our Vision To Value white paper talks about focusing your team on the key strategic corporate goals and ensuring everyone in your organization knows the direction.

Training Superiors and Stakeholders

Your projects may be much smaller, but they still need project managers that can lead without authority and can train leaders and stakeholders who are ignorant of their project management deficiencies. Never expect executives and sponsors to know what project managers need to properly execute their jobs. It is paramount that project managers use these people as tools to get the project completed, which means training them on their jobs. Project managers must unapologetically assign them tasks just like everyone else on the project. They work for the project manager. The sooner everyone realizes this, the better the project will run.

To underscore the point, think back on the last few sponsors you saw assigned to projects. Did they want to be in that role? Had they done the job before? Did they ask for reports on progress or did they request assignments to help the project? Too often, projects inherit project sponsors as an afterthought—assigned under duress. Sponsors need the project manager's help in delineating what is required of them to make the project successful. This includes clarifying and constraining the project's scope, acquiring subject matter experts, finding the extra money when it is obvious that the project is bigger than anyone thought.

The executives? They should be mentoring project managers, helping with costs, and cutting through the politics. If they are not doing this, the project manager must teach them to do so. Most likely, the project team members understand their project roles; I doubt the leaders and stakeholders do.

Delegating Up

Of course, a project managers' job is to run the project; however, if they are confounded by a problem, it is better to ask for guidance than to flail and fail.

A few years ago, I was called in to fix a project that was going to be 200% over budget and schedule. Yes, 200%. That means three times the cost and three times as long. Sad but true. The product would benefit two departments; only one was funding it. My investigation showed that nearly all of problems were "above" the project in the management hierarchy. The leadership was dysfunctional. A Vice President for the non-funding department requested that one of the project's team members blind-copy her on all emails and communications regarding scope. The VP would then use this information to have her team bias the requirements in her department's favor. Upon discovering this, I bundled up the evidence and trudged into her boss' office—an executive three layers above me in the organization and second-in-command for the multi-billion dollar company. I made my case in a logical and dispassionate manner asking him to stop the covert action. By the time I returned to my desk (three blocks from the executive's office), the reverberations had hit the project team, with a memo reprimanding the use of the blind copy feature. He took care of the situation as I left his office. He wanted to help, he was unaware of the problem, and when he became aware, helped me regain command and control over my project by removing the meddling manager. Less than a month later, I had to invoke the assistance of another executive, this time the VP of Information Technology, asking him to stop the drone of negativism from one manager regarding my recovered project's team. The offender apologized for hindering our progress. Executives want to help; we simply need us to tell them what to do.

Success is Contagious

Stepping up and being a leader, helps you, your peers, and the entire organization. Leadership begets success and success is contagious. Peers mimic the victories. Your actions will improve the company's culture and the change sticks because everyone benefits. Change that helps does not meet the same apathetic demise of other change efforts. It only requires that you focus on three directives that lead your leaders:

  • I need you to help me by...
  • I need mentoring on ...
  • I need you to clarify...
Read 20653 times

Related items

  • Process Mapping

    Process is at the core of any business. It makes work predictable, repeatable, and transferable. Without it we cannot scale our businesses. However, process can be a bane to making progress. Processes that work for a $10 million company have difficulties supporting a $30 million company. Trying to scale them to a $300 million company will not only fail but not address the issues that larger companies have that were never dreamt of in a smaller organization. Processes need to be discarded, revamped, and built—all of that without creating an overburdening bureaucracy.

    Anytime you need to go someplace, you first have to know where you are. Processes are never static and your company's current state is probably far from where you think it is. Hence, the first step is mapping out you company's current state followed by defining the future state. This is more than a logical map of the process; it must also include physical maps. Whether your process is solely to provide a service (say, website development) or physical (say, manufacturing) there are logistical issues that complicate the process flow. Without fully understanding those nuances, future state processes will not reach the desired efficiencies.

    For more information about process mapping fill out the form to the left and we will get in touch with you.

  • Success vs Culture

    The other day a Latvian student contacted me for my views the connection between culture and success criteria—an important and intriguing topic. After working in Taiwan, Singapore, Korea, Japan, Israel, United States, and Canada, I wear many scars of both blatant and subtle cultural violations. I also know that within a culture one person's success is often another person's failure. So, after dispelling concerns about clicking on some random email link, I completed her survey (please feel free to take it yourself). In the process, I struck up a friendship with the student, Kristine Briežkalne, who is studying at Riga International School of Economics and Business Administration . She has some interesting views and presented me with a Venn diagram showing four frames to a project (business, client, project management, and growth perspectives) and how they intersected. As the diagram is part of her Master's thesis, I will let you ponder the how to label the overlapping areas (an eye-opening exercise).

  • Kill The White Knight

    There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.

  • Comparing Organizational Change Management Models

    A few weeks ago, I set out to write a post on the comparison of various organizational change management (OCM) methodologies and realized that would be a disservice to my readers. It would simply drag you down the path of implementation while failing to focus you on building the foundation. The pressure was too much and I have relented to numerous requests on making that comparison. The caveat is that juxtaposing these models is not comparing different varieties of oranges or even apples and oranges; we are surely comparing the peel to the fruit they contain. Hence, comparing methodologies like Kotter's model (the peel), Prosci's ADKAR (the core), and General Electric's Change Acceleration Process (the whole fruit) need a different approach.

  • The Executive-Project Manager Gap

    It was such an innocuous question, "Working on an article; what is the biggest problem you see with project governance at orgs? Can you comment?" Can I comment? Really? That is like cheese to a mouse. Where could I start—bureaucracy, draconian process, poor executive sponsorship, disengaged leaders? Plenty of fodder, because they all lead to project failure. I fired off, "Creating an over bureaucratic morass stifling innovation & implementing process instead of cultivating leaders." Then the maelstrom started and it went directly to the gap between the executives and projects managers. Naomi Caietti, Robert Kelly and I had a great conversation. Most of the thread is below.

Leave a comment

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

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

Sitemap