Deadly Sins of Project Management. Well at least my favorites!

We all make mistakes. Project managers are certainly no exception – though, as a profession, we tend to be placed under much scrutiny at times. Therefore those mistakes may become big news and can be, depending on the mistake, quite damaging and costly to the projects we are running. In the world of project management, so many things need to be done; when they aren’t done, they can damage our project engagements. Or things that we do or actions that we actually do take, that can really mess things up, too. Sometimes we dip into our past or into our professional past, where we witnessed someone else’s project go south to gain this type of insight. Either way, it makes an impression, likely because of the chaos and destruction it caused on our projects.

I have worked with, for, and hired many project managers throughout my career. Along the way, I have noticed that many challenges PMs face are shared across the industry, vertical, professional services, and in-house PMO organizations. A project manager is supposed to be a leader, a facilitator, an advisor, and an advocate, not only for the project but also for the team, the business, and the cause. However, clients and stakeholders see project managers as utility people rather than leaders. This led me to wonder how we got into this situation in the first place.

On Time, On Budget, and On Scope

I interview a lot of people for project management positions, and one question I always ask is: “How do you define project success?” Eight times out of ten I get “on time, on budget, and on scope.” This is a canned answer that in the heads of most project managers who have gone through PMI or any othwer Project Managemnt certification. I would argue that it is not about on time, on budget and on scope. It is about managing expectations, delivering on business outcomes, and ensuring both client and team satisfaction. The reality is that things change. Very rarely is anything delivered on time, on budget and on scope. The business climate changes, the details are revealed, complexity increases, priorities shift and new stakeholders are introduced (to name a few). A great project manager understands the business objectives and drives the project to deliver on those objectives, all the while proactively anticipating needs, managing expectations, facilitating engagement, and fostering satisfaction. It is about driving results and making people feel good about the results.

The Journalist

I recently read a book that portrayed project managers as Journalists. Journalists are people who detach the goal of accurate reporting from the goal of project success. We all know these project managers. They are so focused on accurately reporting the news (the report’s detail, the report’s cadence, the report, the color of the report) that they completely lose sight of the why, why are we doing this project, and how success is defined. Project Managers know that they have to understand their projects’ true state and report accurately on them. Sometimes, however, they lose sight of the reason for all this attention to detail: making sure the project achieves its objectives. They adopt, as their goal, the accurate portrayal of the state of the project at all times. They become, in effect, journalists. Like film critics, project journalists believe — if only subconsciously — that they can succeed even if their project fails. Great project managers don’t just report on the news, they drive the news. They drive the direction of the project toward a successful outcome. They are active participants in the process and not innocent bystanders. Next time you write a status report, make sure you are reporting the news and taking an active role in making the news. Be a leader who helps solve tomorrow’s problems, versus just reporting on yesterday’s problems, and take accountability for outcomes.

Say No

No one likes to be told no. Project managers have a tough job; sometimes, a “no” answer is the most reasonable response. After all, they are stewards of budget, time, scope, quality, and experiences for their clients (or internal stakeholders) and their teams. They constantly toe the line, managing expectations and trying to make everyone happy. So when life happens — there are hiccups on a project, changes are made, new stakeholders become involved, etc. — the “no” answer that was once expedient becomes a killing word in a world that is always in flux. The dialogue ends, collaboration falters, and innovation is stifled. Instead of managing expectations by saying “no,” think about using the “yes, and…” principle. For example, a stakeholder says, “I’ve done some research, and I would like to add a new module to the system.” The answer should be, “Yes, I understand how that can help you achieve your business outcomes sooner… and we may be able to de-scope some additional functionality that may not have as much impact on your goals. As a result, we would need to increase the budget by only 100K,” versus the normal freak out: “What? Do you want to add scope? No, we can’t do that. It will make us go over budget, impact our timelines and introduce an additional scope.” The idea is to get people to collaborate and understand that any idea brought to the table can be accepted, added upon, and made better. “No” shuts people down; “Yes, and…” gets people to collaborate and build upon an idea, suggestion, or request to improve it.

Flying High

Effective project managers cannot get stuck in orbit, hovering over the project like an observer and a reporter. When they do, they never truly understand the drivers behind a project and never truly understand the intricacies. I always say the devil is in the details, and project managers who don’t dive in and get their hands dirty shouldn’t be surprised when things go haywire. An effective project manager has to be able to go micro and then elevate to macro. You have to understand the ins and outs of the project, however, you can’t get stuck there. You also have to be able to elevate yourself above the project, staying ahead of your team, anticipating your client’s or stakeholder’s needs and addressing them proactively, versus reactively. You have to keep the team connected to business outcomes and drive decision-making to align and support those outcomes. When you “fly high” and are not really connected to outcomes and don’t understand the details, your team doesn’t need you and your client doesn’t need you either. You become an administrative artifact, just reporting the news (as mentioned above). Get connected. Get engaged. Submerse yourself. Elevate yourself. Don’t get tangled in the web of details, but don’t skip out of orbit either. It is a careful balance and one that is mastered through artistry and experience, not science.

Make it big: The Problem

Your team is miserable. You are up against tight timelines. Your client or stakeholders have unrealistic expectations. Everyone is complaining, including you. You are not doing anyone any favors, but rather you are contributing to the misery. As a project manager, you are seen as a leader (whether you are one or not), and you are held to those expectations. Leaders do not sit on problems; they are problem solvers. They help contribute to the solution. You may listen, you may sympathize, and you want to develop empathy for your team, but at some point you have shift your team away from problems and toward a solution. You are empowered and should have the skills of influence and persuasion to help shift your team’s thinking and mindset. Next time your team is sitting around and complaining, elevate yourself and drive them to take accountability of the situation. Ask your team, “What is one small step we can take to change the current situation?” When all is said and done, perhaps the problem lies in the title. Perhaps “manager” is the wrong word. After all, “manager” has had centuries of connotative and pejorative meaning attached to it. Could it be that simply changing the title could change the way others perceive the position? Advisor maybe? Facilitator? These things might be a start, but I think the most effective and immediate answer is for project managers to change the way they think of themselves and start to change their behaviors. They should cultivate the habits, attitudes, mannerisms and leadership qualities that will make them valuable assets to the team and not mere artifacts.

The secretary

I once had a project manager on my team complain to me about how business stakeholders only saw him as a note taker, and treated him as an administrator. My advice to him was to stop taking notes. His eyes widened, and he looked at me in shock. I imagine this reaction was because he’d been taught throughout his career that one of the major responsibilities of a project manager is to take notes, capture decisions and document, document, document. I don’t disagree that creating alignment and visibility to decisions is critical, but in today’s world there are better mechanisms for capturing this information than to waste the time of a highly paid project manager taking notes. Rather, I always give my project managers this simple advice: do things that empower you; do not do the things that relegate you. When you are taking notes in a meeting, you are not actively engaged in discussion nor are you actively listening. You are not seen as a leader, you are not offering insights and opinions, and you are not being strategic. You are being tactical and administrative. Project managers need to elevate their game and start driving value for their customers, whether internal or external. Think about your clients, stakeholders and users, and make them the center of your story. Do they get value from your notes, or are your notes only valuable to you ? Your value stems from your voice, your experience, your ideas, your planning, and your ability to lead a team. That is what drives value, not taking notes.