

|
Some of the most challenging problems on a project can often be “people problems.” “People problems” are the social and cultural barriers that project managers face, such as resistance to change, departmental “silos,” lack of cooperation and teamwork, inadequate communication, lack of leadership support, and politics and infighting. This article is the first in a two-part series that will offer some practical approaches for dealing with “people” issues on projects. In this first article, we suggest preventive actions you can take prior to the start of a project. In the sequel article, we will present contingent actions you can take if problems of this sort occur during the project. Part I: Preventive ActionsTo reduce the likelihood of “people problems" on your projects, we will share four major preventive actions along with eleven planning tools that we have used with our clients successfully. The four critical preventive actions include:
The remainder of this article will describe the eleven specific planning tools that you can use to carry out the four preventive actions listed above. 1. Include Cultural Issues as Part of Project PlanningWe have developed three tools that project managers use to formally include people and cultural issues in the project planning process. These tools include: 1) the Change Impact Analysis; 2) the Potential Problem Analysis; and 3) a formal cultural assessment that we call the “Readiness” Assessment.
Tool 1. Change Impact Analysis Tool 2. Potential Problem
Analysis One
popular risk analysis tool is the Potential Problem Analysis (PPA). The
purpose of this tool is to identify potential problems that could affect
project success and then help develop preventive and contingent actions.
The project manager enters the identified preventive actions into the
project plan along with “triggers,” or precipitating events that would
indicate the need for implementation of the contingent actions.
Tool 3. A Cultural “Readiness”
Assessment
Organizations use the “Readiness” Assessment to identify their strengths
and weaknesses as they relate to implementing the project. The
organization then uses this information to design and plan the project in
a way that will increase the likelihood of success. This tool focuses on
leadership, teamwork, politics, staffing, attitudes, and other cultural
factors. 2. Create a Project Structure That Takes Into Account Cultural IssuesWe provide project managers three tools they can use to build a project structure that helps reduce people problems on projects. These tools include: 1) a carefully designed project organization; 2) careful selection of the key project personnel; and 3) a clear definition and description of project roles during the project initialization phase. Tool 4.
Guide for Structuring Your Project Organization Tool 5.
Criteria for Selecting and Assigning the Right People to the Right Roles
Tool 6. Roles and Responsibilities Table 3. Build in a Strong Communication and Involvement StrategyPoor communication and lack of stakeholder involvement is a recipe for misunderstanding, suspicion, and lack of “buy-in” and ownership by the very people who are affected the most by the project. These problems are surprisingly easy to prevent. We suggest that all project managers use the following two tools during the initiation phase. Tool 7. Critical Issues
Sessions Tool 8.
Communication Table
|
|
Back to June Index for
Impact: Proven Concepts for High Performance |
|
Click
here to see an index of all articles
|
| Home | Teamwork | Project Management | Leadership Development | Who We Are | Our Speakers | Our People | Our Clients | Our Products & Training Courses | Articles | What's New |
|
|
||||||||||||
|
|
||||||||||||
Preventive
Tool 2: Potential Problem Analysis
|
Tool Name |
Potential Problem Analysis
|
|
When to Use |
Feasibility stage or project planning stage
|
|
Purpose |
Identify potential problems that could affect project success, and then develop preventive and contingent actions. This tool does not directly address resistance to change, politics, teamwork or other cultural issues; however these cultural issues almost always surface during the exercise.
|
|
Process Steps |
First assemble a cross-functional group of stakeholders. Then facilitate this team as follows: 1. Generate a list of potential problems that could hamper project success. 2. Evaluate each problem on likelihood that the problem will occur. 3. Evaluate each problem on the seriousness of consequences to the project if it did occur. 4. Prioritize the list by selecting those problems that are both likely to occur and would have serious project consequences if they did occur. For each prioritized problem: 5. Develop action steps to prevent the problem from occurring. 6. Enter the action steps into the project plan, making sure to assign task duration, responsibilities, and timing. 7. Develop a contingency plan of action if the problem occurs anyway. 8. Identify the event or metric that will “trigger” the implementation of the contingency plan.
|
|
Time Investment |
Half-day workshop |
Tool Name |
Cultural “Readiness” Assessment |
|
When to Use |
Project Planning Stage |
|
|
This tool focuses on leadership, teamwork, politics, staffing, attitudes, awareness of resources and other factors that will have an impact on how “ready” the organization is to carry out the project. Due to the sensitive issues dealt with, this assessment is best carried out by an outside party. This tool is used only for mission-critical, high visibility projects that will require a large investment in resources. |
|
|
|
|
|
|
|
|
|
Tool Name |
Guide for Structuring Your Project Organization |
|
When to Use |
Project Planning Stage |
|
Purpose |
Provide guidelines for structuring a project organization that will
help overcome possible resistance, politics, and silo effects (lack of
teamwork). |
|
Principles we Use in Coming up with a Project Structure |
|
Tool Name |
Criteria for Selecting and Assigning the Right People to the Right Roles
|
|
When to Use |
Project Planning Stage
|
|
Purpose |
Help overcome possible resistance, politics, and "silo" effects (lack of teamwork) by providing criteria for carefully assigning the right kinds of people for key project roles.
|
|
Criteria for Selecting People for Key Project Roles |
Project Sponsor - Political clout,
willingness to make a decision and positive (enthusiastic) toward the
project. |
|
Criteria for Leaders of the Various Project Focus Teams (Sub-teams) |
|
|
Criteria for Team Members |
|
Tool Name |
Roles and Responsibilities Table |
|
When to Use |
Project Planning Stage |
|
Purpose |
Clearly define project roles in order to avoid later confusions or disagreements.
A
way to settle turf battles ahead of time by agreeing and making
explicit each person’s role on the project, each person’s
responsibilities, as well as limits to authority. |
|
Description |
A Roles and Responsibilities Table is simply a list of the key players that are involved on the project, followed by succinct statements of the duties and responsibilities they will have on the project. This is usually arranged in Table. For typical projects, the “key players” would be:
|
|
Process Steps |
|
|
Tool Name |
Critical Issues Sessions |
|
When to Use |
Project Planning Stage |
|
Purpose |
Involve all stakeholder groups in the planning stage of the project in order to identify all possible issues prior to the start of the project.
Data collected with this tool are used in project planning , project
communication planning, and to possibly make changes in the project
structure.. |
|
Process Steps |
|
Tool Name |
Communication Table |
|
When to Use |
Project Planning Stage |
|
Purpose |
Produce a communication plan that is simple in
format, easy to execute, and that will help alleviate the typical
communication breakdowns that occur on projects. |
|
Process Steps |
|
|
Time Investment |
The communication table can be completed in a
half-day session with key project players. |
|
Note |
It is sometimes helpful to have the focus teams
(sub-teams) put together their own communication table, consistent
with the Communication Table for the project. |
Tool Name |
Guide to Ongoing Leadership Development |
|
When to Use |
This tool is not related to a particular project,
but instead to the organization’s overall development. |
|
Purpose |
To continuously develop leadership potential in
the organization in general, thus increasing the likelihood that there
will be strong leaders available for any specific project. |
|
Rationale |
It is known that the “healthier” the organization
is (e.g., fewer silos, better history of teamwork, better leaders,
less politics) the less likely there will be a risk to a project due
to “people problems.” |
|
Examples of Leadership Development Topics and interventions
|
|
Tool Name |
Guide to
Ongoing Teamwork Development |
|
When to Use |
This tool is not related to a particular project, but instead to the
organization’s overall development. |
|
Purpose |
To
continuously develop teamwork in the organization in general, thus
increasing the likelihood that there will be less politics and more
teamwork on any specific project. |
|
Rationale |
It
is known that the “healthier” the organization is (e.g., fewer silos,
better history of teamwork, better leaders, less politics) the less
likely there will be a risk to a project due to “people problems.” |
|
Examples of Teamwork Development Programs |
|
Tool Name |
Guide to
Ongoing Business Literacy |
|
When to Use |
This tool is not related to a particular project, but instead to the
organization’s overall development. |
|
Purpose |
To
continuously educate organization members about business goals,
strategies, and direction, thus increasing the likelihood that there
will be an understanding of the strategic importance of
mission-critical projects, and therefore less resistance to change.
|
|
Rationale |
The more business literate the workforce is, the less resistance to
change, and the more job involvement and motivation |
|
Business Literacy Factors |
The organization should strive to ensure that everyone understands the following on an ongoing basis: Strategic goals of the organization (what the organization is trying to accomplish)
And for each job incumbent:
|