Search This Blog

Saturday, January 22, 2011

Project Customers

All projects must end.  Hopefully, they end with the customer and sponsor being happy with the project's deliverables.  A key thing to plan for on every project is how the customer will be managed after project implementation.


Many organizations rely on Customer Relationship Management (CRM) software to help them manage their customers. CRM systems have evolved to be must have tools for many organizations, and all project managers should be familiar with their capabilities and limitations.   Also, since many CRM systems are hosted in the cloud, the startup costs can be very reasonable.


Wikipedia defines Customer Relationship Management as "a widely-implemented strategy for managing a company’s interactions with customers, clients and sales prospects. It involves using technology to organize, automate, and synchronize business processes—principally sales activities, but also those for marketingcustomer service, and technical support. The overall goals are to find, attract, and win new clients, nurture and retain those the company already has, entice former clients back into the fold, and reduce the costs of marketing and client service.[1] Customer relationship management describes a company-wide business strategy including customer-interface departments as well as other departments".


If you are interested in learning more about CRM systems, one company I have looked at is Hosted CRM from Sherweb.  If you have done business with them in the past, let me know what you think by leaving a comment below.


Also, make sure you check out these great customer service jobs from Jobboom, a supporter of this blog.

Wednesday, January 19, 2011

You Have Issues

Issues are going to happen on your projects. What is an issue you may ask? I define a project issue as “any event or circumstance that could alter the project schedule, budget, scope, quality or otherwise impact a project in a negative way”.

To manage issues properly you must log them, and ensure they are resolved quickly so they don’t negatively affect your project. Managing project issues is a very simple process; however we need to follow a few guidelines. Steps to take include:

Identify the Issue

This should always be done in writing. Any project team member can submit an issue to the project manager, however the project manager may choose to ignore the issue or even alter the project scope depending on circumstances.

Review the Issue

Review the issue with all concerned. Prioritize the issue and access any risks.

Log the Issue and assign ownership

When creating an issues log include at a minimum:

Write a clear and concise issue description 

Prioritize the issue based upon potential impact(s) to the project or deliverables 

Capture the date the issue was opened, date issue is expected to be resolved, and actual resolved date

Note the person responsible for resolving the issue (don’t make this a group or team. Always specify a person here.)

Have a notes column to log updates about the issue

Issue Monitoring

Request that issue owners update the issues log (or send you updates) at least weekly. Review the issues list with all core team members on a regular basis.

Issue Closure

When an issue is resolved, update the issues log with any pertinent information and close the issue.

A good issue management process will let the project sponsor know when and where issues are occurring. Additionally, an issues list is a great way to communicate to the project stakeholders about problems or concerns that are being addressed by the team. Many times an issue can cause a Scope Change Request to be generated if the issue isn’t properly managed.

In closing, conduct regular reviews of all open issues with the team and review progress towards resolving the issues. Manage issues daily, and work to resolve them quickly so they don’t become major problems on your project.

Thursday, January 13, 2011

Great Article by Harold Kerzner, Ph.Dl, PMP

Click here to view the article entitled: Twenty Common Mistakes Made by New or Inexperienced Project Managers By Harold Kerzner, Ph.D., PMP

Links to the above post by Dr. Harold Kerzner have been published in several places, but I wanted to share it here too for those that haven't seen it.  This is an awesome document that will help both new and experience project managers.

I have a couple of Dr. Kerzner's books and they are all excellent.  One of his best books is listed below:

Monday, January 10, 2011

Do You Use Business Cases to Justify Your Projects?



Before a project is started, there should always be a business case. Without a business case that defines the problem(s) you are trying to solve and what success looks like, your project will start on very shaky ground.

Rule # 1 -  the business case is always written by the organization receiving the benefits.

A business case is nothing more than a story. As you begin to write your story one of the first things to define is the benefits (the value) the product(s) of the business case will bring. These value statements should be specific, brief, clear, and measurable.

Here are some basic questions that must always be answered when developing a business case. They are:

What is the problem you are trying to solve? What are the gaps between where you are and where you want to go? What are the assumptions? What will it cost?

What is the ROI (Return on Investment) and how long will it take to recoup the investment?

When did the problem first appear? How long has it been happening? What is it costing you?

Where is the problem occurring?

Who is impacted?

Why is there a problem? What is causing the problem and what is the effect? Why is a change needed now to address the problem? How big is the problem?

How will solving or minimizing the problem save money or add value? How will you measure the value?

Are the business case’s benefits worth it? Are they realistic?  Are there alternative solutions that would cost less?

There are many more questions to be answered when developing a business case, however answering the questions above will get you off to a good start.

Tuesday, January 04, 2011

Project Communications Planning

Project Communications Planning is a process that is continuous throughout a project. When building your initial Project Communications plan focus on the following:

Define Your Audiences - Who needs to know What, and When and How do they need to know it. Communication needs and audiences will change as the project moves forward. Plan for it.

Start from the Top and Work Your Way Down the Chain - Start your Communications with the highest levels of the organization first, then work your way down to the team members. Repeat this cycle.

Target Your Message to the Different Groups - Different groups (and sometimes individuals) may require different types of communications media (e-mail, status reports, web site, face-to-face, memo, etc.). Plan for these different types of communications vehicles up front.

Define Roles and Responsibilities - Ensure that your Project Communications Plan includes Roles and Responsibilities for key stakeholders.

Status Reports - Status Reports are a great form of Project Communication if kept short and to the point.

Repetitive Messages will be Required - The same message delivered using different mechanisms and sources will help to reinforce your message.

Anticipate Conflict - Tailor your communications to overcome Conflict before it occurs. Keep in mind that Conflict will always occur on a project. Conflict needs to be anticipated and managed continuously throughout the project.

Allow for Anonymous Feedback - Create a way for people to relay their positive and negative feedback anonymously.

Project Managers need to recognize that good communication is important because it helps to reduce conflict, increases information distribution, and helps to silence critics while reinforcing the positive aspects of your project.

Tuesday, December 21, 2010

Get the Right Talent on Your Team

Years ago I managed a large group of software engineers. At the time, it was very difficult to recruit software engineers from here in the United States, so we started sponsoring talent from overseas (China, Russia, India, etc.) and bringing them here to work.  When the economy recovers the IT sector may again have to look overseas to fill many software developer and IT vacancies. There just aren’t computer science majors coming out of American universities to satisfy the current and upcoming demand.

My point is corporations will either have to outsource IT jobs to other countries or look to bring in talent from other countries using an immigration lawyer if they can’t find the right talent within our own borders. The same principles apply to your project teams. If you don’t have the right talent in your company for your project team, consider looking to outside contractors or consultants to fill these roles.

I believe that outsourcing jobs overseas or bringing in workers from outside your borders shouldn’t occur except as a last resort. Having said that, I also realize that companies can’t grow if they can’t hire the right talent.  Never settle for what is available when staffing your project teams. If you can’t find what you need within your company don’t be afraid to look externally. The job you save may be your own.

Monday, December 13, 2010

Some Great Quotes!

“Do one thing every day that scares you.” —Eleanor Roosevelt

“Life is either a daring adventure, or nothing.”—Helen Keller

“Dream as if you’ll live forever. Live as if you’ll die today.”— James Dean

“The two most powerful things in existence: a kind word and a thoughtful gesture.”— Ken Langone, founder, Home Depot

“The deepest human need is the need to be appreciated.”— William James

“Don’t belittle!” — OD Consultant, on the essence of a well-functioning human community

“If you don’t listen, you don’t sell anything.”— Carolyn Marland/MD/Guardian Group

“It was much later that I realized Dad’s secret. He gained respect by giving it. He talked and listened to the fourth-grade kids in Spring Valley who shined shoes the same way he talked and listened to a bishop or a college president. He was seriously interested in who you were and what you had to say.” —Sara Lawrence-Lightfoot, Respect

“What creates trust, in the end, is the leader’s manifest respect for the followers.” — Jim O’Toole, Leading Change

“If you can’t state your position in eight words or less, you don’t have a position.” —Seth Godin

“Never doubt that a small group of committed people can change the world. Indeed it is the only thing that ever has.” —Margaret Mead

“Make your life itself a creative work of art.” —Mike Ray, The Highest Goal

“Have you invested as much this year in your career as in your car?” —Molly Sargent, OD consultant and trainer

“The most successful people are those who are good at plan B.” —James Yorke, Mathematician, on chaos theory in The New Scientist

“To live is the rarest thing in the world. Most people exist, that is all.” —Oscar Wilde

“People want to be part of something larger than themselves. They want to be part of something they’re really proud of, that they’ll fight for, sacrifice for, that they trust.”—Howard Schultz, Starbucks

“It is not the strongest of the species that survives, nor the most intelligent, but the one most responsive to change.” —Charles Darwin

“We may not be interested in chaos but chaos is interested in us.” —Robert Cooper, The Breaking of Nations: Order and Chaos in the Twenty-first Century

“If you don’t like change, you’re going to like irrelevance even less.”—General Eric Shinseki, retired Chief of Staff, U. S. Army

“You must be the change you wish to see in the world.”—Gandhi

“We eat change for breakfast!”—Harry Quadracci, founder, QuadGraphics

“If things seem under control, you’re just not going fast enough.” —Mario Andretti

“You can’t behave in a calm, rational manner. You’ve got to be out there on the lunatic fringe.” —Jack Welch, retired CEO, GE

“We have a ‘strategic’ plan. It’s called doing things.”—Herb Kelleher, founder, Southwest Airlines

“I guess it comes down to a simple choice, really. Get busy living, or get busy dying.” —The Shawshank Redemption (Tim Robbins)

“Stay Hungry. Stay Foolish.”—Steve Jobs, Apple

“Groups become great only when everyone in them, leaders and members alike, is free to do his or her absolute best.”—Warren Bennis and Patricia Ward Biederman, Organizing Genius

“The best thing a leader can do for a Great Group is to allow its members to discover their greatness.”—Warren Bennis and Patricia Ward Biederman, Organizing Genius

“You are the storyteller of your own life, and you can create your own legend or not.”—Isabel Allende

“Nobody can prevent you from choosing to be exceptional.” —Mark Sanborn, The Fred Factor

“A leader is a dealer in hope.”—Napoleon

“Nothing is so contagious as enthusiasm.” —Samuel Taylor Coleridge

"The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it". Michelangelo

“If you’re enthusiastic about the things you’re working on, people will come ask you to do interesting things.” —James Woolsey, former CIA director

“Before you can inspire with emotion, you must be swamped with it yourself. Before you can move their tears, your own must flow. To convince them, you must yourself believe.” —Winston Churchill

“If your actions inspire others to dream more, learn more, do more and become more, you are a leader."—John Quincy Adams

“A year from now you may wish you had started today.”—Karen Lamb

Wednesday, November 24, 2010

Jerks at Work (Revisited)

A book was written not long back entitled "The No A**holes Rule". In it, the author - Robert Sutton -discusses how "A**holes" a.k.a. "work jerks" can cause major disruptions in the workplace. The author  defines work jerks as "people who pick on those beneath them and leave others feeling belittled and sapped of energy. They use their power to schmooze those above them and beat down those beneath them. Much of the rest of their time can be spent bullying their peers".

My takeaway from the book is that jerks at work have a negative impact on the bottom line. They always cost organizations more than they are worth, and they cause upheaval that is harmful to individuals as well as the organization they work for.

What can we do when confronted with jerks on our projects? When possible we should avoid and ignore them. We can also look for ways to work around their influence and create partnerships with others that are willing to help. If somebody believes falsely that being a jerk will get them to the top quicker, there isn't much you and I can do about it. One thing is certain, we don't ever want to emulate their behavior. Jerks are poisonous, they are detrimental to project progress, and the value they sometimes create is erased by the disruption they cause.

Jerks almost always know they are jerks. They don't believe in Win/Win, they believe in Win/Lose (they must win, others must lose). Jerks are self centered, have large egos, and we aren't going to change them.

Project Management Rule: Project managers have to get the job done in spite of work jerks.

As project managers, we must learn to work with all types of people and get our projects completed on time and on budget in spite of them and their behaviors.  Remember, when confronted by a jerk be patient and respectful. Kill them with kindness. Don't forget that jerks can have influence over your project and career, and they occasionally have good ideas. There biggest flaw is they lack good character.

Project Management Rule: Work jerks don't subscribe to lofty ideas like fairness, cooperation, self-discipline, or integrity. 

They are reactive, many times "enemy-centered", and concerned about defending their desires and rights.

The bottom line is that work jerks lack emotional maturity. One definition of maturity is the balance between courage and consideration. Companies and organizations need to do a better job of screening for jerks during the hiring process. They need to know that studies have shown work jerks cost them more then they produce. Organizations don't need people in a leadership or any position for that matter that have questionable character, a win/lose work ethic, and a Scarcity Mentality.

Tuesday, November 16, 2010

Project Teams Members Need These Things

Project team members will perform at their peak when they:

Clearly understand and embrace the project's goals

Understand clearly the expectations put upon them

Understand how success will be measured

Understand the expectations of the project manager and sponsor

Believe their concerns will be listened to and addressed

Believe the project manager and sponsor are 100% committed to the success of the project

Understand that constructive, open, and free flowing communication is appreciated and welcome

Know they will be recognized and rewarded for their achievements

Tuesday, November 09, 2010

Don't Try to Please Everyone



As we manage our projects, we need to remember to spend the bulk of our time working with our advocates and supporters, not answering or arguing with our critics. If you say you don’t have critics on any of your projects than I say you probably aren't pushing hard enough, and that means you probably aren't a very good project manager. 

Monday, November 01, 2010

Trust and Leadership

I was reading the book "The Truth About Managing People" today and thought I would post a couple of excerpts from the book about leadership.  The link to the book is at the end of this posting.  I highly recommend this book, especially if you manage people, or are a project manager.

In regards to leadership, the book states, "When we trust someone, we assume they'll act honestly and truthfully and be reliable and predictable.  We also assume they won't take advantage of our trust.  Trust is the essence of leadership because it's impossible to lead people who don't trust you. "

Some quotes from the book to gain the trust from others....

Be open

Be fair

Speak your feelings

Tell the truth

Show consistency

Fulfill your promises

Maintain confidences

-----------------------------

I think this is a great book.  Enjoy!

Saturday, October 30, 2010

One Rule from the Nordstrom's Employee Handbook


Nordstrom's Employee Handbook

"For years, Nordstrom’s Employee Handbook was a single 5×8” gray card containing these 75 words:
Welcome to Nordstrom
We’re glad to have you with our Company. Our number one goal is to provide outstanding customer service. Set both your personal and professional goals high. We have great confidence in your ability to achieve them.
Nordstrom Rules: Rule #1: Use best judgment in all situations. There will be no additional rules.
Please feel free to ask your department manager, store manager, or division general manager any question at any time.
During this time, Nordstrom had the highest sales per square foot performance in the retail industry"
-----------------------------------------------------------
Does your company have a "Rule #1 for its employees?  


When you review your employee's performance does their employee appraisal include a review of his or her customer service strengths and weaknesses?  Regular formal appraisals (quarterly, or better yet monthly) will help your employees improve their skills.


Do you provide your employees with regular training to ensure they are providing the highest level of customer service?


Does your company survey its customers to find out their level of satisfaction?  


Are your customer survey results used as part of the employee's appraisal process?


Remember, you can't manage what you don't measure, and you probably aren't providing excellent customer service if you aren't surveying your customers and providing continuous customer service training to your employees.

Wednesday, October 27, 2010

Effective Project Teams


Teams are dynamic and always changing.  Teams work when the individual team members unite around a common goal and have a vested interest in each others successes.  Once team members begin to bicker and fight amongst themselves, the team begins to lose its effectiveness and the reputations of the each of the team members can suffer.

Once teams lose that "all for one and one for all" dynamic the whole team loses.  Win-lose relationships on teams are never an option.  There are only two options when working with another person on your team.  You either both win or you both lose.  The team leader and team members must openly discuss issues that hinder the team from performing at their highest level and work through the issues quickly.  Lingering problems between team members can only fester and worsen, which drags down the effectiveness of the whole team.

EMOTIONAL OUTBURST - team members that display a pattern of destructive or caustic behavior to others (inside or outside of the team) should be removed from the team immediately.

Remember, when working through team dysfunction, compromise doesn't satisfy anybody and doesn't solve problems.  Collaboration is key to working through team issues and getting team performance working at a high level.  Compromise and capitulation are flawed strategies for working through problems as they don't support a win-win outcome.

In closing, keep in mind that poor listeners are not good collaborators.  In order to be an effective team leader you must listen carefully and think win-win while working through problems with your team.

Tuesday, October 12, 2010

Your Estimates Are Wrong!


I have been burned more times than I can count by bad estimates. What can a project manager do to help ensure the accuracy of estimates?  First we should understand the basics behind the estimating process (there are many more than I have listed here). Some are:

• The more unique , complex, or larger the project, the more of a challenge it will be to get good estimates

• Estimates are only as good as the estimator is at predicting the future

• "Padded" estimates are not always bad as long as the padding is communicated (... and as long as the Project Manager is the one doing the "padding")

• An estimate is not a bid

• Estimates using sound estimating practices, performed by experienced estimators from clear specifications should never be negotiated

• Ballpark estimates are guesses and should be treated as much by the project team, management, and the project sponsor

Other items to consider when estimating are:

• Ensure the statement of work or contract is clear and understood by the person(s) doing the estimates

• Ensure that a schedule or mandated date doesn't drive the estimating thought process

• Include Risk Management in the estimating process

• Ensure that estimates take into account the skill level(s) of the person(s) that will do the work

• If your work breakdown structure (WBS) is flawed, your estimates will be inaccurate

Accurate estimating is an art and a science. The estimator (or team) must take into account historical data from past projects, the team's knowledge and experience, the project risks, the statement of work and other project information to make the best estimate possible.

Keep in mind when planning your project that estimates aren't hard and fast numbers. They are guesses, however they should be very good guesses if you have good estimators and are following tried and true estimating practices.

Tuesday, October 05, 2010

A Project Is...

Project managers get in trouble when we try to complicate things. In my career, I have worked for many different types and sizes of organizations. Some have embraced Project Management and others have made excuses so as not to be constrained by what they believe is a process that slows things down (adds cost and overhead). I have preached the same message for years. Project Management is designed to help reduce or eliminate rework and surprises at the end of a project.

So why don’t some organizations see the value of Project Management? Usually it is because they do not understand the benefits of Project Management, they do not trust the Project Managers they currently have, or the ones they have encountered in the past. OK, we can accept that, however, what we should never accept is the idea that Project Management just adds cost and overhead.

We need to educate those around us about the difference between projects and other organizational work. Senior management needs to realize the fact that work is basically broken down into two areas: Operations (focused on Maintaining) and Projects (focused on Change). Most organizations do an adequate job of managing their operations; however, my experience (limited as it is) has shown that projects and the support of project management vary greatly.

Every organization has projects; sometimes they are just too busy to realize it. As project managers, we need to keep fighting the good fight of educating the influencers in our organizations about the benefits of Project Management. In addition, we need to realize that the benefits of Project Management are demonstrated in the successful implementation of projects. Do not preach the benefits of Project Management; demonstrate them by walking the walk and talking the talk.

So, a project is:

A temporary endeavor to create a unique product or service

Constrained by a finite budget

Constrained by a finite timeline (defined start and end date)

Composed of interrelated activities

Focused on attaining one or more clearly defined objectives

The last point needs to be stressed. Without clearly defined and agreed upon objectives your project is doomed to fail from the start. I would also add that your project does not have a chance for success unless you have an engaged, influential, and respected executive in the role of project sponsor.

Tuesday, September 28, 2010

Project Management Requires Discipline


Discipline is the act of encouraging a desired pattern of behavior. George Washington said: "Discipline is the soul of an army. It makes small numbers formidable, procures success to the weak, and esteem to all". In other words, discipline is the glue that holds organizations together. 

We can't have agile and effective project methodologies or organizational processes without discipline. In short, effective discipline requires effective organizational oversight.  Finally, discipline begins at the top and works its way down. Organizations with poor discipline have weak, ineffective leaders at the top.  Weak, unengaged, ineffective leaders kill organizations. Can you say Enron?

Remember, the lack of project discipline is the fault of all project team members, but the cause of a lack of discipline lies at the top of the organization.

Sunday, September 19, 2010

Stages of Creating Major Change


The below was adapted from the book "Leading Change" by John P. Kotter (see more information at the end of the posting).

1. Establishing a Sense of Urgency
    a. Examining the market and competitive realities
    b. Identifying and discussing crises, potential crises, or major opportunities

2. Creating the Guiding Coalition
    a. Putting together a group with enough power to lead the change
    b. Getting the group to work together as a team

3. Developing a Vision and Strategy
    a. Creating a vision to help direct the change effort
    b. Developing strategies for achieving that vision

4. Communicating the Change Vision
    a. Using every vehicle possible to constantly communicate the new vision and strategies
    b. Having the guiding coalition role model the behavior expected of employees

5. Empowering Broad-Based Action
    a. Getting rid of obstacles
    b. Changing systems or structures that undermine the change vision
    c. Encouraging risk taking and non-traditional ideas, activities, and actions

6. Generating Short-Term Wins
    a. Planning for visible improvements in performance, or “wins”
    b. Creating those wins
    c. Visibly recognizing and rewarding people who made the wins possible

7. Consolidating Gains and Producing More Change
    a. Using increased credibility to change all systems, structures, and policies that don’t fit   together and don’t fit the transformation vision
    b. Hiring, promoting, and developing people who can implement the change vision
    c. Reinvigorating the process with new projects, themes, and change agents

8. Anchoring New Approaches in the Culture
    a. Creating better performance through customer and productivity-oriented behavior
    b. Articulating the connections between new behaviors and organizational success
    c. Developing means to ensure leadership development and succession

SOURCE: Adapted from John P. Kotter, “Leading Change,” Harvard Business School Press 1996

Sunday, September 12, 2010

Five Good Free Kindle Books (Non-Fiction)


The Truth About Personal Performance (Collection) - by Robert E. Gunther [amazon.com]

Three full books of proven solutions for supercharging personal performance! Prepare for any audience, negotiation, or decision-compel attention and motivate action-manage anxiety or anger-use nonverbal communication-negotiate with people you love (or hate)-build (or repair) trust-make decisions with imperfect data-and much more!

How McDonald's Got Its Groove Back - by New World City [amazon.com]
How did the lumbering fast-food giant McDonald's cure its own sclerosis and become a newly lean, hungry competitor? Its comeback offers lessons for leaders everywhere in focusing on what their customers really want. For example, don't react to competitors, react to customers. When you broaden your market appeal, don't abandon your first customers. Don't skimp on product development.

33 Million People in the Room: How to Create, Influence, and Run a Successful Business with Social Networking - by Juliette Powell[amazon.com]
Social networks are no fad. They’re a permanent reality: one that offers immense opportunities to smart, innovative businesses. Now, top social networking consultant Juliette Powell reveals how dozens of innovators are driving real ROI through
social networks–and how you can, too.
Powell’s wide-ranging research, including coverage on Barack Obama's successful online strategy in his bid for the presidency, focuses on technology, media and gaming companies, leaders in fashion, beauty, publishing, finance, retail, event planning, and beyond. These powerful narratives illuminate the reality of doing business on today’s social networks as never 


The Personal Credibility Factor: How to Get It, Keep It, and Get It Back (If You?ve Lost It) - by Sandy Allgeier [amazon.com]
Can you be trusted? Right now, someone is asking that question. If they decide to trust you, they’ll work with you, care about you, open up to you…help you live a more successful, more fulfilled, happier life. If not, you’re on your own…
Build the Strong Personal Credibility You Need to Live a Truly Great Life
*Learn the secrets of personal credibility that make trust possible
*Use the plan to earn trust and respect from those you encounter in your daily life
*Enable others to have confidence in you by following the 7 easy steps
*Follow the Personal Credibility Factor’s steps to repairing credibility when you’ve lost it


So What?: How to Communicate What Really Matters to Your Audience - by Mark Magnacca [amazon.com]
It’s tough, but true—the people you’re trying to communicate with, sell to, or convince don’t really care about you. Nor do they care what you’re offering them—until they understand exactly how it’ll benefit them. If you recognize that one hard, cold fact—and you know what to do about it—you’ll make more money, achieve greater success, and even have more fun!

In this book, world-renowned sales consultant Mark Magnacca shows you how to answer the “So What?” question brilliantly, every time—no matter who’s asking it or what you’re trying to achieve. This book will transform the way you communicate: You’ll use it every day to get what you want—in business and in life!


Overcoming Perfectionism: The Key to a Balanced Recovery - by Ann W. Smith[amazon.com]
Do you have to be perfect to lead a healthy life? Ann Smith discusses how perfectionism may have benefits but is ultimately an obstacle to quality living as it prevents intimacy and lowers self-esteem. This book offers practical hints to letting go of your superhuman syndrome and being imperfect. 

Wednesday, September 08, 2010

Poor Project Communications Can Hurt the Whole Team


When project teams are surveyed at the end of failed projects, poor communications is always cited as being one of the major causes. Why does this keep happening? Why is project communications so poorly executed so often. My short answer is that many project managers (and managers) are arrogant, inattentive, and oblivious to the feelings and needs of the project team.

Project managers are busy, and often they don't make time to manage project communications effectively. Also, the project manager may think they are doing a good job communicating, but that may not be the case.

Project managers must remember that the project team is made up of individuals. Each person on the team has a preference for the types of communication they like to receive, and each person processes communications differently.

Some things to monitor that may point to poor project communications are:

Trust - Does the team trust you (the project manager)? How do you know? Everybody will not trust you all the time. Team members that don't trust the project manager will not be open in their communications. They will tend to either shut down, gossip and spread rumors, or challenge the project manager at every turn

De-motivated - Where are we going? Is the team going where we said we were going when we started? Did we clearly state where we were going before we started?

Whining - Despair and anxiety take over the team or key team members. Infighting is prevalent and people are starting to talk openly about the project being a failure.

Incompetence - Team isn't sharing information and learning. Perhaps the team has had little to no training, or the training received was of poor quality.  Perhaps some team members should be fired from the team.

All the above can be overcome, however it requires that the project manager is listening and changing strategy when necessary to get the team back on track. Just because you are a project manager doesn't make you a good communicator, however ignoring problems like the ones mentioned above will make you a bad project manager.

My two cents are, be a leader. Lead through your communication and your ability to motivate your team to get the job done. Be on the lookout for the above warning signs. When you see the signs act quickly, follow-up, then continue to monitor.  Remember people may need to be removed from the team.

Poor project team synergy is the fault of the project manager. There are a lot of incompetent project managers that are hurting our profession because they either refuse to alter their communication styles or are too arrogant to change. My advice to them is to change their ways or leave the project management profession.