Voices on Project Management

by , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with - or even disagree with - leave a comment.

About this Blog

RSS

Recent Posts

End a Business Relationship and Keep Your Cred

Fair's Fair

Give Your Project a Home

A Hollywood-Style Move From PM to Scrum Master

To Have and To Hold

End a Business Relationship and Keep Your Cred

As much as we wish these things didn’t occur, we sometimes find ourselves having to leave a project early or terminate a business engagement. This is always difficult to do, and how you do it can help you maintain your integrity and credibility throughout the transition.

 

Recently, I had to terminate a business relationship myself. Here are a few lessons that I learned that you can apply the next time you are in a similar situation.

 

1.   Place the blame on yourself. I know you wouldn’t be leaving a project or quitting a business relationship if it were all your fault, but the key thing here is that you need to buck up and take responsibility for the business arrangement ending. There are several ways you can frame it to take the emphasis for the decision away from the other party. For example: “I’m sorry, but I just don’t have the ability to deliver the work to you in a manner that you have grown accustomed to” or “I find myself at a point where I don’t feel my presence best serves the project, and I think a new set of eyes is going to be helpful to getting things back on track.” Or, you can come up with your own. The point is that you take a little of the emphasis off the party that you are ending the relationship with and place it on yourself. This will lessen any bad blood or negativity from the decision. It is important to note that you must cast the decision in terms of your inability to continue to serve the client in a manner that he or she deserves.

2.   If possible, present options for replacements.If you find yourself at a point of no return and need out of a business relationship, you can soften the blow even more if you provide alternatives. The question you are probably asking yourself is, “If I can’t work with this person or on this project, why would I refer them to someone else?” But the truth is, we are all in different businesses and at different stages of our career — and while your threshold for some clients may be zero, someone just starting out or looking to find a different focus may be more than willing to accept a challenge that you consider unnecessary. This goes back to the first point: If you can’t serve the client in the way that he or she deserves, you are doing the client a favor by removing yourself from the project and helping him or her find someone who can do better.  

3.   Be prepared for blowback.Even when these things go great, there will be some sort of blowback or negative impact. You might have spelled everything out with as much tact as a veteran diplomat, but you are still leaving the business relationship with a jilted partner who may lash out to other members of your organization or other potential business partners. In this instance, you can try to contain any negative feedback or impact on you and your career by preparing a standard statement that you give to everyone that explains your role in the dissolution of the relationship. It should cast a bad situation in the most favorable light for you. One I have used is: “I am sorry the project didn’t work out, but I made a series of unwise choices that made my effectiveness impossible, and to best serve the project, I felt it was best for me to step away.” That’s it — it isn’t perfect, but neither is the situation you find yourself in.

 

How have you found success in ending business relationships?

 

Join meon December 4, 2014, in my upcoming seminar on leadership in project management.

Posted by David Wakeman on: October 22, 2014 05:30 PM | Permalink | Comments (2)

Getting Out of Trouble

Project trouble can hit from a blind spot, even though you tried as much as possible to prepare for issues. You did a risk analysis when you took the project on, and even tried to be ready to mitigate unknown issues.   

As I advised in my previous post, do an assessment to determine the problem. Figure out what needs to be fixed, or if the situation is even fixable. If the project seems to have reached a point of no return, here are some tips on how to pull it out of trouble:

  1. Seek out your sponsors. They should be the source to go to when trouble arises. Not only is it likely they will have encountered something similar in the past, but they can also provide additional budget funds, more resources or reinforcement for areas in conflict.
  2. Consult with your team. Bring everyone together, discuss the problems surrounding the project, and begin to discuss counteraction and next steps. Steer away from blame and trying to determine who is at fault. Beware especially of ganging up on the customer. Team members may want to take the position that it's the customer's problem, not the team's. But be clear that the point of getting together is to determine how to solve a problem project, not pass it off as someone else's fault. Instead, gear questions toward possible solutions and the support needed to achieve them. 
  3. Rely on backup and supporting information. Most likely, you will have monitored risks and issues all along and kept a good repository on your project. If so, you will be able to locate the exact information that helps address your problem. For example, you may be over budget because equipment purchases ate even beyond what your contingency allowed, and now a project sponsor or customer may be questioning the overrun. You should be able to pinpoint the authorization you received to make that purchase. 
  4. Enlist outside resources, if needed. Lessons learned or a fellow project manager could be consulted for knowledge transfer and experience. You could even call in an outside contractor for a specific need. 
  5. Remember that a halt is an option as well. Most times, this is seen as negative, and the project is considered a failure. But that is not necessarily the case. Sometimes, halting the project is the necessary solution, and it doesn't have to have horrific implications. If it isn't halted, the project could accumulate astronomical costs. The trouble could consume the project to the point where it would need to be shut down. A halt can also help you assess if the project is still meeting objectives (which could be the source of the problem). Stopping the project in its tracks could help you to determine if you need to redirect funds and/or resources. 

Finally, keep in mind that not all trouble devours all. Before panicking, calmly look to areas that will guide you to a solution. You may even find your project is more sound than it seems.

How do you confront trouble on your project?

Posted by Bernadine Douglas on: October 15, 2013 10:25 AM | Permalink | Comments (3)

If Project Managers Had Life Tenure...

I recently heard an interview with Antonin Scalia, an associate justice of the Supreme Court of the United States, regarding the rulings he has handed down over the years. The reporter wondered if Mr. Scalia ever worried about public backlash or the opinions of his fellow justices.

Mr. Scalia simply replied that he didn't worry about that. He has life tenure, given to him by the U.S. government. He believes that tenure allows him to do and say what he thinks is right and not worry about how it will affect his career or colleagues.

This answer had a profound effect on me.  I often wonder if I am "doing the right thing" when I make decisions at work. I try, but I would not be honest if I did not admit that the career survival instinct hasn't kicked in once in a while. Perhaps sometimes I compromise on issues that I know are not good for my projects or my team. But I'll give the client the answer they want to hear, or perhaps tone down the weekly status report to avoid stirring the pot when there are real issues to discuss.

I've now started applying what I will refer to as the "life tenure" rule to all of my decisions and activities. I try to look at a decision or situation through the lens of "If I did not have to worry about politics or personalities or self-promotion, would I still make this move?" I have to say, thankfully, that I appear to achieve that about 90 percent of the time. But clearly I think that can improve.

I know it is naive to think that someone could or should perform their job as if they could not get fired.  Or to think that if we all had that freedom, that we would always make the right decision. But it is an interesting concept to ponder, and a fascinating test to apply.

Think about it: How would your professional life change if you had life tenure as a project manager?

Posted by Geoff Mattie on: September 04, 2012 09:00 AM | Permalink | Comments (10)

Guidelines for Project Clients to Enable Success

Categories: PM Think About It

I recently witnessed two projects executed within weeks of each other. Both projects were related to the rollout of major technology solutions for significant, well-established corporations.
 
What was different about the projects were the dynamics between the client and the project team -- specifically, the way the client engaged and worked with the project team. One project was successful, and the other was not.

In my opinion, the success as well as the failure was largely because of the dynamics between the client and project team.
 
I am definitely not implying that any project gone awry is the client's fault. In fact, I believe it's the project manager's primary responsibility to facilitate all points below. But unless the client is willing to observe and adhere to these guidelines, the project is already in jeopardy.

Think about it.

Here is a working list of guidelines that can help clients and other stakeholders work with a project team and deliver a successful project:
 
1. Be transparent. A good project team realizes there are going to be unique variables and circumstances it will need to address. Be upfront and candid with the project team about the challenges or risks in accomplishing the project goals. It is much more productive to get everything on the table upfront versus waiting for it to be discovered while executing the project.

2. Stay engaged and responsive. One school of thought says a good client stays out of the way of a project team and without too much micromanagement. This can be true to some extent.
 
However, clients must work with the project team to ensure there are open channels of communication. Information or clarification must be provided quickly and concisely, and preferably in writing.
 
Ideally, one or two people on the client side have the knowledge and authority to speak for the entire client team. This is especially important when providing critical input such as requirements, milestone approvals and strategic guidance. Without this representation, the project team has to chase down information, and there is greater risk of them getting it wrong.

The project manager must facilitate these activities and provide the framework in which they occur, but this is a two-way street. 

As a client, if you cannot make the time and emotional commitment to communicate, then postpone the project until the time is better. Otherwise, we all risk having to do it over again.

3. Be decisive and time sensitive. Recognize that there are going to be hard decisions to be made in terms of requirements, tradeoffs, budget, timing and resources. If a decision cannot be made on the spot, define a window of time in which you will get back to the team with an answer and respect that commitment. As noted above, if it's going to take time to get an answer, let the project team know this ahead of time.

4. The laws of physics still apply. As nice as it would be to bend the laws of physics, project teams are not capable of making three-day tasks in just two. Project managers do sometimes pad their timelines to allow for project creep or addressing other unseen emergencies. But recognize that this is done due to experience from previous projects and is an effort to account for the "unseen" challenges that inevitably crop up in your efforts.
 
Forcing a team to schedule its project activities in exacting increments for the sake of impressing company executives, for example, introduces a risk that some unforeseen event will cause that project to run late.
 
What other guidelines would you add to this list?

Read more from Geoff.

Posted by Geoff Mattie on: April 03, 2012 10:42 AM | Permalink | Comments (1)

Are You Sure Your Project Information is Secure?

Categories: PM Think About It

Fellow blogger V. Srivinasa Rao recently wrote an interesting post about the Global Distribution Model 2.0 that is launching soon. The model holds a lot of promise and is a great framework for implementing mobile global communications tools.  

Today, the fastest rising communications and computing technology is mobile. And while this development provides exciting possibilities for improved project efficiency, it does not come without risks. I'm focusing specifically on devices with a mobile operating system, such as iOS, Android, Windows Phone 7, Blackberry or Nokia.

The reason for my concern is the speed of adoption for the devices. They now play a role in every project I manage. It may be simple communications such as email between team members, text messaging and calendar functionality, or more sophisticated uses such as remote access to project data, project management software or even video conferencing. Yet 90 percent of the time, I find that no one is really thinking through the implications of using this technology.

Think about it: With this expanded communication comes an increased risk that your project's confidential or critical information could be exposed, intentionally or unintentionally.

This information can be controlled fairly easily by IT departments on laptops, but mobile operating systems don't allow for the same kind of security just yet. You must be wary of how information may be getting communicated over your mobile device.

Information "attacks" can come in several forms. At an event where "free wireless access" is offered, for example, someone who wants to gather data illegally can set up a US$50 wireless router, name it "[Event Name] Wireless" and watch as attendees innocently connect their devices to communicate with the rest of the team. Simply leaving your Bluetooth enabled in public locations can open you up to attacks.

It doesn't even need to be something that devious. All that needs to happen is for one of your team members to lose a device that has regulated data on it. In the United States, you'll have to officially report the incident to the Federal Government.

The key takeaway here is that as our world expands, we are being given exciting new ways to coordinate and communicate with our team members across the planet. We should take full advantage of this. But we should do it with our eyes open.

How do you protect your data on a mobile device?
Posted by Geoff Mattie on: January 05, 2012 11:14 AM | Permalink | Comments (2)
ADVERTISEMENTS

"Education is an admirable thing. But it is well to remember from time to time that nothing that is worth knowing can be taught."

- Oscar Wilde

ADVERTISEMENT

Sponsors