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

View Posts By:

Cameron McGaughy
Marian Haus
Lynda Bourne
Lung-Hung Chou
Bernadine Douglas
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Roberto Toledo
Vivek Prakash
Cyndee Miller
Shobhna Raghupathy
Joanna Newman
Christian Bisson
Linda Agyapong
Jess Tayel
Rex Holmlin
Ramiro Rodrigues
Taralyn Frasqueri-Molina
Wanda Curlee

Past Contributers:

Jorge Vald├ęs Garciatorres
Hajar Hamid
Dan Goldfischer
Saira Karim
Jim De Piante
Geoff Mattie
sanjay saini
Judy Umlas
Abdiel Ledesma
Michael Hatfield
Deanna Landers
Alfonso Bucero
Kelley Hunsberger
William Krebs
Peter Taylor
Rebecca Braglio
Dmitri Ivanenko PMP ITIL

Recent Posts

Do You Understand the Critical Path Method?

Find Purpose to Unlock Exceptional Performance

What is project success?

Predicting Performance: There Must Be a Better Way

Driving Diversity of Perspective

What is project success?

by Christian Bisson, PMP

 

Project success is typically defined as being completed within budget, schedule, and scope, and that has been imprinted so much in project managers’ mind that it blinds them to other important aspects that defines a project’s success.

Client Satisfaction

This aspect of project success seem to be more and more popular, and with reason, if clients are not happy, they will shutdown the projects, or proceed with another organization. If your project is on budget, delivered on time, and does exactly what it should be doing, but the client is so unhappy that they ceases to work with the organization, can you consider the project a success?

For example, if you focus so much on being on budget/schedule/scope, that you decline everything the client asks for without a second thought, chances are the client will not want to work with you long term. On the opposite side, giving everything the client wants and ending up late or 200% above budget is not an acceptable alternative. You or the team will often need to be creative to find ways to balance things out, and properly managing the client’s expectations is also key top this.

Project value

Another very important aspect of project success is the value it’s adding. A project that is doing what was planned, but ends up being useless, is not a success.

For example, if you create a great website, the client loves the design, the development phase had only few minor issues that were fixed rapidly so the team is happy, the project is delivered on time, on budget, and does what it’s supposed to do, however, users that go on the website are completely incapable of finding the information they need, and they end up always calling customer service instead, then is that really a success?

It’s important to identify right from the start what metrics will be used to calculate the project’s success, and tie those metrics to features of the website as you go to make sure a feature is not useless or solves an issue that has nothing to do with the project’s objectives..

Organization Satisfaction

The organization that has provided the services needed to make the project happen is also a key aspect to look at to define the project success, and unfortunately often due to lack of transparency from management, can be a challenge.

For example, there are projects that the organization’s management know they will lose money on, but for them it is considered a long-term investment to bring more business. If that’s not communicated, the project manager will see the project as a failure because it’s over budget.

It’s important to have visibility on the organization’s goals and expectations around the project in question.

 

 

What are your thoughts on the matter? Do you use other aspects to define project success?

Posted by Christian Bisson on: September 11, 2018 08:27 PM | Permalink | Comments (11)

The Worst Project Manager I Ever Worked For Was Me

 

by Kevin Korterud

 

I always enjoy hearing about the early careers of the project managers I meet. In almost every conversation, the subject turns to when they were team members being led by a highly capable senior project manager who provided guidance in starting up, executing and sometimes turning around projects.

 

It’s also not uncommon to hear stories of the worst project manager they ever worked for. These stories, while not as glowing, also influenced their careers around what not to do. By probing a bit deeper, they offered up observations of certain behaviors that created havoc, dissatisfaction and quite often failed projects.

 

From these observations of the worst-ever project manager, I started to put together my own thoughts on who I would select for this inglorious label. After careful consideration, I arrived at the only logical choice: me. In my early years as a project manager I managed to consistently demonstrate all of the behaviors of poor project managers.   

 

Here are my votes for the most significant behaviors that led to consistently poor performance as a project manager early in my career:

 

 

  1. I Wanted the Title of “Project Manager”

 

When I was a project team member I relished the thought of one day having a business card with an impressive title of project manager. My thought being once I received that lofty title, it would allow me to be successful at whatever project I was assigned to lead. In addition, the acquisition of that title would instantly garner respect from other project managers.

 

I failed to realize that most project managers are already quite proficient at leading teams and producing results. The title comes with a heavy burden of responsibility that was exponentially greater than what I had as a project team member. As a team member, I didn’t realize how much my project manager shielded me from the sometimes unpleasant realities of projects.

 

The satisfaction of acquiring the title of project manager can be very short-lived if you’re not adequately prepared. My goal became to perform at the level at or above what the title that project manager reflected.

 

 

2. I Talked Too Much

 

Perhaps I was wrongly influenced by theater or movies where great leaders are often portrayed in time of need as delivering impressive speeches that motivate people to outstanding results. I remember quite clearly some of the meetings I led as a new project manager that quite honestly should have won me an award for impersonating a project manager.

 

Meetings were dominated by my overconfident and ill-formed views on what was going right and wrong. In addition, I also had the false notion that I had the best approach to all of the risks and issues on the project. No surprise that this mode of interaction greatly limited the size of projects I could effectively lead. Essentially, it was a project team of one.

 

After a while, I started to observe that senior project managers spent a fair portion of the time in their meetings practicing active listening. In addition, they would pause, ponder the dialogue and pose simple but effective probing questions. When I started to emulate some of these practices, it resulted in better performance that created opportunities to lead larger projects. “Less is more” became a theme that allowed me to understand the true problems and work with the team to arrive at effective mitigations.

 

  1. I Tried to Make Everyone Happy  

One of the most critical components of any project is the people that comprise the team members and stakeholders. As a new project manager, I tended to over-engage with stakeholders and team members by attempting to instantly resolve every issue, whether real or perceived. My logic was that if I removed any opportunity for dissatisfaction then project success would be assured.

I failed to realize this desire to completely please everyone quite often resulted in pleasing nobody. In addition, I also managed to pay insufficient attention to the key operational facets of a project: estimates, forecasts, metrics and other essentials needed to keep a project on track. Furthermore, the business case for the project gathered almost no consideration as I was busy trying to make everyone happy as a path to results.

Over time I began to adopt a more balanced approach that allowed me to spend the proper level of engagement with people, processes and the project business case. This balanced approach allowed me to have a broader span of control for factors that could adversely affect a project.

For all the things we have learned over the years as project managers, it sometimes causes me to wish for a time machine to go back and avoid all of the mistakes we made. But then, we would not have had the benefit of the sometimes-traumatic learning experiences that have made us the project managers that we are today.  

Did you ever consider yourself to be the worst project manager you ever worked for? I think we all were at one point in our careers.

Posted by Kevin Korterud on: August 10, 2018 06:43 PM | Permalink | Comments (28)

3 Signs Your Project Is Headed For An Accident

 

by Kevin Korterud

 

The technology found in today’s automobiles is simply amazing. Front and side traffic radar units, anti-dozing head movement detectors, driving timers that alert drivers when they should stop for a break­ — all good examples of accident prevention mechanisms.

 

Projects to some degree are like automobiles: They are on a journey to deliver passengers (the project team and stakeholders) to a pre-determined destination. However, despite the introduction of many modern project management technologies, research shows that we continue to experience project accidents. These accidents result in extensive and costly rework to get a project back on track. 

 

I think part of the solution to avoid these potential problems is to borrow from recent automobile technologies as a way to detect troublesome signals. These signals are not readily perceivable from traditional project management methods.

 

Here are a few examples of anticipatory signals that portend the onset of a skid that often leads to a project accident.

 

 

  1. Forecast Volatility

 

A core competency of a project manager is to determine the schedule, budget and progress trajectory of a project. The project forecast is essential to determine where the project will finish for these measurements. Schedule, budget and progress forecasts from team members that exhibit great degrees of change over prior reporting periods are indicative of trending to an accident. This downward spiral is exacerbated when the forecast measurements come with great uncertainty; e.g., “I don’t know what this will take to finish.”

 

Several techniques can be employed to reduce the volatility of forecasting. Some of these techniques include initiating a peer review of the forecast with another project manager or supplier subject matter expert, as well as pausing the project to recalibrate the forecast in a dedicated working session. Taking time to implement these and other techniques to mitigate forecast volatility will get the project back on track before an accident.

 

 

2. Static Project Status

 

Project status reports can offer a tremendous amount of value to a project manager. They accumulate both qualitative and quantitative data that sheds light on the current project state. But, despite the visibility status reports provide, they’re just a snapshot. That limits their ability to show progress trends. In addition, a project status report that does not show content changes week over week indicates that the project is likely stalled and headed toward an accident.

 

To increase the anticipatory value of a project status report, introduce trending and predictive data for risks, issues, deliverables and milestones. This allows the project team to determine what level of progress has been achieved, as well as what progress to expect. It also better positions the project manager to escalate mitigations to avoid an impending project accident.

 

  1. Diminishing Stakeholder Engagement

At the beginning of a project, stakeholder engagement and enthusiasm is typically high. This is not unlike the start of a road trip. But, as time passes on a project, the level of enthusiasm and engagement can begin to wane. Stakeholder engagement over time will face tough tests from project risks to resource challenges to dependency conflicts. Each can sap the energy levels of stakeholders. This leads to passive engagement at best and complete disengagement and absenteeism at worst.

To keep stakeholder engagement at the proper level, stakeholders need to be treated like any other resource on a project. Their time needs to be managed in work plans to avoid oversubscribing their capacity. In addition, their work should be focused on higher value activities that promote project progress. Providing the team access to project support staff to maximize productivity also helps further stakeholder engagement and leads to persistent engagement.

Perhaps one day in the future there will be technology solutions that provide anticipatory signals for projects headed for an accident. Until that day comes, however, project managers still need to think organically and look for hidden signals of dangers to project budgets, schedules and progress.  

What do you see as the leading indicators that a project is trending toward disaster?

Posted by Kevin Korterud on: May 03, 2018 06:18 PM | Permalink | Comments (18)

High-Performance Teams Are Purpose-Driven

By Peter Tarhanidis, Ph.D., M.B.A.

Program teams should collaborate like a world-class orchestra.

This ideal state of team engagement and performance requires the presence of several key elements, including an engaged sponsor, a governance committee, a project manager and a status dashboard to communicate performance.

However, maximizing this level of performance is especially challenging when working with cross-functional groups, external stakeholders and shareholders. This increases the complexity of the human performance aspects of team management.

I recall one assignment I worked on that required the team to design and build a new centralized model to bring together three different operations. The team was given two additional challenges. The first challenge was to consolidate disparate teams into two geographic centers. They also had to reduce the overall timeline from 18 months to 10 months.

These challenges exacerbated how teams were not working well with their counterparts. They quickly became dysfunctional and lost their purpose. The project was crashing.

Stepping into this situation I decided to conduct a stakeholder analysis. I used this approach as an intervention method to understand the underlying themes. The analysis revealed the team:

  1. Lacked shared values: Members did not have a sense of purpose on the intent of the program.
  2. Were not being heard: Members felt they had no control over the program’s major activities or tasks.
  3. Lacked trust: Members felt they could not rely or confide in their fellow team members, sponsors or peers to accomplish tasks on the program.

After reflecting on the team’s feedback, I realized that most members wanted to find meaning in their work. It seemed no one was developing their sense of shared purpose and putting their strengths to work toward this program.

I decided I needed to re-invest them as members of the team. To get the team back to performing well, I:

  1. Built rapport with various team members
  2. Gained their trust by delivering on my commitments
  3. Integrated their perspectives into decision making
  4. Recruited new members to build up gaps in team capabilities
  5. Focused the conversation on our individual purposes and aligned them to a shared value

This approach strengthened the program and delivered on the challenges.  

The lesson learned is, do not simply apply methods and approaches in complex program delivery. Manage the team’s purpose and establish shared values as an important driver of overall delivery.

How do you manage that purpose and invest in high-performing teams?

Posted by Peter Tarhanidis on: April 18, 2018 08:10 PM | Permalink | Comments (14)

Influencing for Results

by Conrado Morlan

When I started working for a leading global logistics company, I had to wait about three months to get my first regional program assigned. The program, which is still in the works, includes the deployment of a new centralized billing system — including changes to processes and reporting — across 50 countries and territories.

I did not dread the wait. Instead, I made the most of my time and began networking. I started to meet — in person or via teleconference — with people across the regions in which the system would be deployed.

This helped me build a strong foundation with cross-functional stakeholders across the region. I also got information in advance that helped me to draft my stakeholder engagement plan.

When the billing system inevitably changed, I had to perform support for each individual country’s CEO, CFO, CIO and human resources team to help them understand the new features, the improved processes, the consolidated reports and ultimately the benefits.

The program plans and benefits were discussed and approved during an annual strategy meeting with all of the individual country CEOs, CFOs, CIOs and human resources teams in attendance. However, I still faced difficulties with the deployment in those first few countries.  

In the pre-implementation meetings, I had to reiterate the benefits of the program and why it was needed. I had to answer questions and provide solid arguments to justify the tradeoffs between the new and old billing system.

But I used these difficulties to refine my stakeholder engagement plan as I moved to the next country. Understanding the source of change and the stakeholders’ motivations helped me become a better change agent and provide better support during the program implementation.

For the early adopters, it took about three to four months to mature their operation and fully adopt the new system. It was a rough start. But after two months of having the new billing system running, country executives have started to accept the new way of operating.

To build credibility and engage executives from the remaining countries, I asked early adopting executives to share their story and the benefits of the new system.

With this program, I learned how important it is to be an influencer and to build strong arguments that will convince stakeholders to accept projects and programs that change their business-as-usual practices.

What difficulties have you faced when implementing significant change? How did you get buy-in?

Posted by Conrado Morlan on: February 01, 2018 12:40 PM | Permalink | Comments (16)
ADVERTISEMENTS

"I'm glad I did it, partly because it was worth it, but mostly because I shall never have to do it again."

- Mark Twain

ADVERTISEMENT

Sponsors