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
Wanda Curlee
Rebecca Braglio
Rex Holmlin
Christian Bisson

Recent Posts

How to Spot a Top-Shelf Project Manager

3 Lessons From My First Project Manager Job

3 Strategic Resolutions For The New Year

Knowledge Management: More Than Simply Learning Lessons

Want to Start a PMO? Make Sure You Answer These Questions First

3 Lessons From My First Project Manager Job

By Jen Skrabak, PMP, PfMP

Fifteen years ago, I transitioned from being an IT manager to a project manager for the first time. With this month’s theme at projectmanagement.com being “new practitioner PM,” here are three key lessons I learned while managing my first projects.

When I was an IT manager, I always had projects that were assigned to my department. I loved being part of large projects so much I realized I wanted to do it full-time. So I made a conscious decision to transition to being a dedicated project manager.

Managing a project is truly like being a CEO of your own company—you have authority over budget, resource and key decision-making responsibilities. However, it’s an art, and mastery takes time. These are the three fundamental lessons I learned:

1) Communication is about simplifying and personalizing.

Although we may hear that 90 percent of a project manager’s job is to communicate, the best communication is one that doesn’t contain acronyms, special terminology or techno-speak.

Remember that key stakeholders are often involved in multiple projects. To get their attention, you need to make your communications concise and personal while clearly specifying the action desired.

Avoid lengthy mass emails, and tailor the frequency and channel according to the person. One sponsor told me she gets so many emails that I should schedule a meeting if it’s important. Another sponsor told me he works best with instant messaging if I needed something immediately.

The key is to know your audience and adapt accordingly. My first sponsor meeting always includes finding out how and when he or she would like to be communicated with.

2) Project management is about knowing which tools to use when.

Yes, project management is about processes, knowledge areas and ITTOs (inputs, tools and techniques, outputs), according to the PMBOK Guide. But, most importantly, it’s a menu of available options.

Trying to do everything by the book or insisting on adherence to every single template and tool is setting yourself up for disaster. Assess the needs of the project, and don’t ignore the culture of the organization. You can’t go from zero processes to textbook processes overnight. You may need to start slow by introducing concepts and build from there.

3) Build relationships.

Trust is key. When you’re starting out as a project manager, you’re an unknown, so you need to work extra hard to establish the relationships. It’s important to come across as professional, yet approachable and flexible in order to build confidence with your team, and most importantly, your sponsors and key stakeholders. Regular, relaxed one-on-one meetings, such as getting coffee or grabbing lunch, help to build cohesive partnerships that will pay dividends when the going gets tough on the project.

Posted by Jen Skrabak on: January 23, 2016 07:29 PM | Permalink | Comments (10)

3 Strategic Resolutions For The New Year

by Dave Wakeman

 

The new year is a good time for every project manager to take a moment to pause and reflect on what has worked and what hasn’t worked during the last 12 months. Many of my blog posts last year (like this one, and this one) focused on the intersection of strategy and project management. So I thought it could be valuable to suggest three ways you can propel yourself, your projects and your organization forward in 2016.

1. Set clear goals and objectives. As a project manager, you’re usually like the CEO of your project. So even if you’re in an environment where most determinants of success and failure are laid out by others, you still have the opportunity to set goals and objectives that will set your team up for success.

Imagine a project that is stuck. If you’re in the middle of this situation, it’s a good time to sit down and look at the project holistically and try to define some goals and objectives to get the project moving again.

This might require more than just saying what you hope to achieve over the next month, quarter or year—it could involve ways that you can give your team some short-term wins to create new forward momentum. The important thing is to take the opportunity to stop, think carefully, and decide with intention which way you want to move.

2. Simplify communications and decision-making. One of the supreme challenges for all project managers is the constant need to juggle information and communicate to various stakeholders effectively. Being the filter for most communications can hamper and complicate the communication process. As a strategic-minded practitioner, you’re going to have to simplify processes to avoid becoming a bottleneck.

You may find it easy to streamline your communications and decision-making processes by taking the following three steps:

First, set clear expectations for communication.

Second, empower your teams to use their best judgment and to take action within certain well-defined parameters.

Third, regularly review these processes to reinforce what’s working and change things that aren’t working.

3. Always return to the outcomes you need to produce. I’m guilty of belaboring this point, because it’s essential. The end results are what you need to be working toward. You have to be clear on expected outcomes and what you are trying to achieve. This will inform every action, tactic and process you roll out in your projects.

Get started by clarifying the desired results of your project, and then break them down by each piece of work that you need to produce to make them reality.

If you do this in combination with the items in #2, you’re on your way to becoming even more of a strategic partner in your organization’s success. 

By the way, I write a weekly newsletter that focuses on strategy, value, and performance. If you enjoyed this piece, you will really enjoy the weekly newsletter. Make sure you never miss it! Sign up here or send me an email at dave@davewakeman.com! 

Posted by David Wakeman on: January 15, 2016 12:28 PM | Permalink | Comments (9)

4 Tips for Delivering the Desired Business Results  

When I started as a project manager, the focus of my attention was on the mechanics of project management. This involved becoming very involved in work plans, risk/issue trackers, status reports, progress metrics and all those artifacts that form the means by which one manages a project.

What I realized after a number of years (as well as after a few hard learning experiences) was that while the mechanics of project management are important, they are merely enablers for the core activities that truly create a successful project.

I needed to think more about the successful direct and indirect business outcomes that could be created from a project. The attainment of successful business outcomes was what my stakeholders were really looking for, not necessarily the most impressive work plan or status report. This shift in focus become one of the turning points in my project management career.

So how does a project manager, in particular one early in his or her career, make the transition from executing the linear mechanics of project management to producing desired business outcomes? Well, they need to acquire the skills and behaviors that enable business success from projects— hopefully without harmful learning experiences along the way.

Here are four tips for making this transition.

1. Don’t Be Afraid of Business Processes

When I was a relatively new project manager, I spent a lot of time at my desk. This desk time was occupied with working on project management artifacts that if created perfectly would, in my mind, automatically lead to a successful project.   

A senior project manager noticed this and encouraged me to spend a fixed amount of time creating project management artifacts, with the remainder of my workweek interacting with stakeholders in the business areas. In fact, this senior project manager arranged for me to work for a few days with some of the employees that were actually executing the business processes that were to be impacted by my project. Those few days of immersion were a great learning experience that it completely changed my outlook on how to run the project.

Today, I still employ the same technique for both myself as well as fellow project managers and team members. Whether it’s working in a retail outlet helping to stock shelves, processing billing exceptions in a call center or spending time in an airliner simulator, the immersion experience is essential to understanding what makes for successful business outcomes from projects.

2.  Define Business Success Criteria

Very early in my career, I took what my stakeholders initially shared with me as business success criteria without any subsequent qualification. No surprise that some of the success criteria entailed—“just make it easy to use,” “finish testing by the end of the year” or “do whatever the senior vice president says”—didn’t really indicate a clear path to business success. 

As I grew as a project manager, I began to spend more time in the beginning of projects articulating in detail with stakeholders clear criteria for business success. This involved not only understanding current processes by immersion, but also challenging stakeholders on the methods we would use to objectively measure business success. If something cannot be objectively measured, it would be difficult to determine the success of the project.

I also allocated time in the project to build and execute the processes to measure success. By doing so, I had the capacity to create evidence of how the project benefited the business.  

3. Understand Your Industry

In my first few years as a project manager at an insurance company, I took every course on project management I could find (this pre-dated the creation of PMP certification). While I became adept at the mechanics of project management, I had no real foundation of business knowledge for the projects I was leading. 

On a recommendation of a senior project manager, I took a course on the principles of the insurance business. This course covered the terminology, core business processes and emerging industry trends. I left the course wondering how all of this was going to apply to running projects.

Within two weeks of taking this course, my supervisor passed along a compliment from my stakeholders how much more effective and efficient I was in running their project. This newfound productivity came from the ability to more easily understand the challenges that the project was intended to address. Little did I know that the industry training was a form of business process immersion.

4.  Get Comfortable With ‘Design Thinking’    

The concept of “design thinking” originated with companies finding out that while project managers thought they were achieving the desired delivery success criteria of being on time and budget, they were not really producing the desired level of business success from projects. These companies began to explore ways of changing the approach in determining business success for a project. 

Design thinking gives project managers several approaches to fully qualify the path to business success by techniques such as charting a customer journey, business process brainstorming, business case creation and creative reframing.

All of this opened my mind to going beyond the traditional boundaries of a project to ensure I was going to both define and execute to true business success.

I sometimes long for the days when I ran smaller, simpler and shorter projects whose goal was typically to finish on time and budget. I could afford to relax a bit and strive to achieve a high professional standard in the mechanics of running a project.

But as our projects become larger, more complex and longer in duration, we as project managers have to delegate some of these activities to other people, so we can get on with the business at hand of producing successful business results from projects.

These four things helped me make the transition to achieving business results on projects. What are some of the things that allow you to do the same? 

Posted by Kevin Korterud on: December 26, 2015 08:31 PM | Permalink | Comments (14)

The Right Way to Implement Portfolio Management: Baby Steps

By Wanda Curlee

Why do organizations implement portfolio management? There is no right or wrong answer. However, there is a right and wrong way to implement it. Sometimes organizations become so excited by the possibilities of portfolio management, they take the big bang approach. In other words, they implement everything at one time. This is definitely the wrong approach for almost all organizations.

A more desirable approach is what I like to call baby steps. With baby steps, there’s less to lose if something needs to be abandoned or tweaked to better meet the demands of the company. The first step of this approach is to develop the portfolio management methodology the company wants to eventually adopt. This helps leadership see the full value and builds buy-in.

For some, determining what to adopt first is very painful. My suggestion for deciding what aspects of portfolio management to implement first has to do with resources. Today, organizations usually lack all the resources needed to deliver everything desired. So start with your most in-demand resource—the type that gives you the most trouble—whether it’s human, capital, hardware or something else. Then take all your projects and programs and decide the order in which you’d like to deliver them. This is your portfolio roadmap. Are the in-demand resources in collision? In other words, would a scarcity of resources cause bottlenecks in project or program execution? Most likely the answer is yes.

Next, you might want to roughly determine the cost of each component (e.g., a project or program), the highest two risks on each one, and the perceived value of delivery. Cost is normally quantitative, but perceived value and risks may be qualitative. That’s okay. Just try to have four or five factors for each and assign a numeric value for low, medium and high. This makes it easier to come to consensus.

For each component, have concentric circles with value at the center, cost surrounding the value and finally a red circle to describe risk. For example:

The first set of circles has a relatively small value, but large cost and risk. For the amount of benefit received from this component, it might make sense to cancel.

The second set of circles shows a large value, a smaller cost and a large risk. Since the value is so large compared to the cost, it might be worthwhile to see if the risks can be reduced.

Finally, the last set of circles has a moderate value, a large cost and a fairly low risk. This may be a good one to keep, especially if the costs can be negotiated down.

Once each component has three circles, then the portfolio roadmap can be looked at again with each of these concentric circles. Does it match what you had before? Probably not. Based on the circles, you will probably make changes to the portfolio roadmap. Some portfolio components may be canceled and others will change priorities.

Yes, the resource that causes bottlenecks or collisions still needs to be evaluated, because most likely there are still some issues. However, you may have more resources because some components were canceled or delayed. With a better handle on what components can and should be executed when, you’re on your way to a successful rollout of portfolio management at your organization.

Have you ever done this kind of resource audit and prioritizing at your organization? If so, has it helped?

 

Posted by Wanda Curlee on: December 22, 2015 07:21 AM | Permalink | Comments (6)

Don’t Shout the Loudest—Think Ahead

communications comic

Have you been in situations where it seems that only shouting generates results? Or has your team been pressured to complete tasks that don’t appear to benefit your project? Maybe as the project manager, you have been in the middle of confusion and agitation that seem to undermine your project management abilities.

Could it be that many of the scenarios you encounter have their roots in conflicting stakeholder requests and misunderstandings? Well, it’s possible to avoid these types of predicaments. Consider utilizing the following three tools that allow you to have better control of your project and your project team:

1) Communications Plan. Outline a plan with names, contact information, and details on when and what messages need to be delivered to and from you. This tool allows you to know the frequency of message exchanges and the media required for specific contacts. 

It also lets you know what level of detail the message should have, i.e., if it is going to a senior manager vs. a member of the supporting team.

2) Stakeholder Analysis. Prepare an analysis of your stakeholders to understand what their roles are and what area of your project is impacted by their involvement. This tool can help you with the department that has the biggest impact all the way down to the departments that have even a small effect.

Additionally, this tool can show how those who are directly or indirectly connected to your project may have an influence that can be detrimental.

3) Project Plan. Develop a plan with the focus on your project objectives and what the project will entail. Organize the plan for what needs to be done and when. The tool should show ownership and timings that you can share with stakeholders to also make them aware of the potential influence of their requests. 

Sometimes, we get can get distracted when trying so hard to make sure our projects meet every need. There are many voices, conflicts, risks and events that affect the success of our project. Leaning on these tools may make your stakeholder management process smoother.


What tools do you leverage to ease stakeholder management issues?

 

 

Posted by Bernadine Douglas on: November 25, 2015 06:30 PM | Permalink | Comments (12)
ADVERTISEMENTS

"A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools."

- Douglas Adams

ADVERTISEMENT

Sponsors