Eye on the Workforce

Workforce management is a key part of project success, but project managers often find it difficult to get trustworthy information on what really works. From interpersonal interactions to big workforce issues we'll look the latest research and proven techniques to find the most effective solutions for your projects.

About this Blog


Recent Posts

The Trick to Persuasion

Turning Stress Into Success

Why Project Stress Can Be Positive

Generations & Work Ethic

The "Hidden" Effort You Should Really Manage Better

The Trick to Persuasion

When was the last time you had to be persuasive? Maybe it was to convince someone to start  something right away. Maye it was to overcome resistance to doing something at all. Whatever the case, it was a time when you had to use a "tool" project managers need: The ability to persuade.

I'll also wager that you used a tactic to persuade that you are comfortable with, maybe even out of habit, without considering whether it was the most effective method. You may have used a tactic that is common in your workplace. We mimic what we see in the workplace. We may even use a persuasion technique that would work on us.

The problem is that none of these reasons for choosing a method of persuasion are good. They do not guarantee that the most effective method is chose. If persuasion is an important project management tool, then care must be taken how it is used.

Researchers actually do studies to determine what techniques are effective. You should pay attention to what has been learned to make yourself a better project manager, able to get work done through others.   Today's post is the start of a series called "Friendly Persuasion" that will cover many aspects of persuasion relevant to project managers. It's actually a broad topic!

Recently in Inc.com, Christina DesMarais talked to Clinical Psychologist Jeptha Tausig-Edwards about what research has shown actually works when persuading others. There are particular points that apply to project managers.

Don't Bury the Headline In Your Request

This was in a topic in a previous post in this blog. When you are in a conversation where you are going to make your request, state request first. This generally increases your chance of being accepted.

This tactic can be applied to stakeholder interactions, where, for example, you need the individual's approval or you need to use the individual's resources for a period of time to keep your project on track.

  • Get your pitch ready in advance of the conversation. Start with an effective concise request that includes a benefit or avoidance of a problem.
  • Be ready with bullet points for the rationale.

This tactic works because studies found the reality is that those who you target with your request have other things on their mind or may simply be worn out. They appreciate you getting to the point.

Be Beneficial

In your pitch, be specific as to benefits of the made of your target. For example, you can say:

  • "I'm requesting that you approve a change request that will add one month to the schedule due to resources being temporarily assigned to other work. The advantage for you is that this will allow us to be able to keep system function you desired rather than putting it at risk."

Have a Back-up Plan

OK, so even if you have a good pitch, you may get rejected. Don't take "No" for an answer all the time, though. Be ready with a particular response tactic that may keep your options open so that you are not dead in the water.

Researchers have determined that the words you use in your reaction to "No" are critical to success. You have to use the alternative option format as shown in these examples:

  • If the sponsor cannot give you a decision by the deadline you have in mind, respond with "OK, can you get to it to me by Friday next week?"
  • If a stakeholder cannot release resources to your project as planned, respond with an option you have previously found to be the next best thing: "I understand the problem. So will you approve our project using contractors instead of your resources?"

The reason is to keep the individual from responding based on their preference and get them to respond based on their character. The work has to get done, you are asking your target decision-maker to help you with how the work is going to get done. 

As you can see, when you know what works, you can prepare for the interaction. You can even grab success from the jaws of failure. Perhaps more importantly, the tactic may be different in tone and content than a less effective method that you would have used without knowledge of research.

This topic is so important that I'll post additional proven tactics this month (and in the future) to start you off in the new year with better interaction skills.

Until then…Where have you had to apply your powers of persuasion? How did it go? Have you experienced bad attempts at persuading you?

Posted on: January 05, 2017 08:57 AM | Permalink | Comments (2)

Turning Stress Into Success

Teams are more successful dealing with stress when they have a shared purpose. That was the conclusion reached by studies and reported in my last post. So the question remaining is: How can this information be translated into success tactics for you as a project manager? You have to continuously foster a particular line of communication related to challenges. Here are tactics you can use:

From the beginning of the project, promote its business benefits. The shared purpose will be to complete the project so those benefits are realized.

  • Don't just focus on the deliverables in your communications. Communicate key points from the project charter or equivalent document.
  • Promote who will appreciate the benefits:  executives, user groups, stakeholders, customers.
  • Put a number on the amount of users and financial improvements. Communicate these data points early and often to enable the project workforce to rally around these as a shared, higher purpose.

When hiring workers, start building a high-performance team by selecting people who see project obstacles and challenges as opportunities.

Later in the project, as obstacles appear and work teams are put under stress, remind the team that the benefits depend on successfully completing the project together.

  • Be focused on quality of deliverables, but keep everyone mindful of the higher purpose, the benefits of the project.

Discuss the challenges the project team is facing. Bring the conversation around to what the project team can do to meet the challenge. Determine how to work together to meet challenges, surmount obstacles and reduce stress. For example:

  • Be better at handing-off work from one team to another
  • Create a vacation schedule to help team members work together better
  • Adjust standard meeting times to better accommodate one group so that the entire project benefits
  • Improve quality of completed deliverables so that the team who receives it can also do better work
  • Communicate a controversial risk to the schedule that affects the entire team
  • Work together across functional (work) teams to resolve an issue
  • Attend a meeting together as a cohesive project team to deal with a challenge

Do not mistakenly communicate an attitude that appears you want to avoid stress during the project. And don't imply that stress is something individuals will have endure on their own. This does not work. The team must expect to work to meet challenges together, and that will reduce stress overall.

Set up new deliverables like the requirements document as a key part of getting business benefits. Make sure the deliverables mention or link back to the business benefits desired. This not only good practice but helps to link team members together throughout the project.

If key points from the project charter change at any time, use that as a trigger to update the project team on adjustments to the shared purpose.

At the end of the project, as part of Closing, communicate to everyone who participated  that the benefits will be achieved because of their participation to complete. This will cement in their minds that working together as a team is superior to other methods. And you will be remembered as the project manager who runs projects this way.

Notice how all these tactics lead to regular discussions about obstacles and challenges. Build up a habit to think in this way. Project managers regularly talk about risks and issues, so this is not a foreign concept. The trick is to communicate that project challenges are not stressful threats, but opportunities for the team to succeed.

Posted on: November 27, 2016 09:57 PM | Permalink | Comments (0)

Why Project Stress Can Be Positive

Have a stressful project work environment? Worried that the stress is putting the team in conflict, making the team  less productive? Do you see friction among the team members or individuals suffering stress?
Do you know how to respond as a project manager?

Stress can lead to team failure, but it does not have to do so. At least not according to  a happiness researcher.

Now you are probably thinking:  Happiness, you say? What does project management have to do with happiness? Doesn't being in a project mean constantly feeling the walls closing in from your "aggressive" schedule, tight budget, changing requirements and scarce resources?

You could not be blamed for thinking that way.

By the way happiness research is a thing. Check out this TED talk by Shawn Achor, the Harvard (!) happiness researcher whose work is behind this post. We should all probably be spending more time thinking about it than we do. Maybe this is a good place to start.

Achor studied NFL teams and elite military units, looking at situations where some teams perform at a high-level in high-pressure situations and other teams fail. A key success factor was the way teams handled stress. That sounds like something that project managers need to understand then, doesn't it?

There are two parts to being successful here. First, you have to understand that successful teams need a common purpose. This has been established and reported in this blog previously. Achor clarified the second part: that successful teams use their common purpose to better manage stress.

In an article, Achor describes one CEO who changes stressful situations (for example significant barriers and constraints) into meaningful group challenge. NFL winning teams were able to overcome tremendous competition by overcoming the challenges together. Elite military units trained by stamping out a feeling of individual stress, redirecting that feeling to the team for solution.

Managed in this way, stress actually helped bond team members to their organizations. For readers of Eye on the Workforce, you should recognize this as employee engagement, the powerful cultural factor that creates a workforce that is committed and driven.

There has never been a time with more constraints for project managers and their teams. The best project managers will know how to

  • select the best people who will be able to deal with stress
  • manage the team to create a better way to deal with stress and
  • close out a project so that everyone will understand that they have succeeded.

In this way, you will build a reputation for being an effective leader and have more successful projects.

In my next post, I'll continue with this concept, listing specific tactics useful for project managers. In the meantime, check out the links and post your own ideas and thoughts....and be happy. 

Posted on: November 20, 2016 10:52 PM | Permalink | Comments (6)

Generations & Work Ethic

Do you think that one  generation has a better work ethic than others? What have you seen in your workplace? Are you frustrated by those in other generations?

Choose an answer to this question. Which generation has a stronger work ethic?

  • Millennials  (born between 1981 and 1999)
  • Gen X  (born between 1965 and 1980)
  • Baby Boomers  (born between 1946 and 1964)

A recent study looked into this topic with a statistical study. They went into the study stipulating that evidence was mixed from previous studies. And I'm sure you have your own anecdotes from your experiences.

We try not do have stereotypes about generations, our own and others, but sometimes it is difficult to avoid. And the generations have differences in what the researchers note has been called "significant life events at critical development stages". The point that beliefs and attitudes have been shaped by these shared histories is well proven.

For Boomers the influences include the Viet Nam War, civil rights for African-Americans and assassinations of prominent leaders. Boomers have been loyal to their employers and place work as central to their lives.

Members of Generation X were influenced by the first Iraq War, the President Bill Clinton sex scandal, school shootings, the HIV epidemic and reality television. There was a tendency for them to leave home and come back. They hesitated to commit to long-term relationships, perhaps because of the high divorce rate from their collective parents. They strive for work-family balance. The tend to want to work autonomously.

Millennials have been influenced by the 9/11 terrorist attacks, the second Iraq War, and the election of the first African-American president. There has not been that much research about their work experience and preferences because they are new to the workplace, but the researchers mention these traits among others:  confident, team-oriented, and achievement-oriented.

That's a lot of diversity in the workplace, so this basic an understanding will help you manage the potential conflicts in the workplace. Members of any generation can look at the others in the workplace and be annoyed or frustrated. My favorite generational bias is Gen Xers feeling that Boomers have a feeling of entitlement while Boomers feel that Millennials have a feeling of entitlement. Awareness of this kind of thing will help you develop ways to get individuals and groups to work together better.

But does either group have a better work ethic than the others? That's a pretty basic value. The researchers looked very carefully at this in a way that allowed them to put statistics to the analysis. They found that there was not really a difference between the generations when it comes to work ethic.  

So how do you use this information?

  • Do not assume that one generation works less hard than another. They may tend to work differently, and you need to know that. It helps you be a better manager of people. It helps you understand individuals so that you can place them in a role where they fit and can excel.
  • Be aware of your own biases and use your knowledge of generations to help you avoid negative stereotyping by age or generation. This will get you in trouble as much as stereotyping by gender, race or national origin.
  • Use your knowledge of generational influences and tendencies to help you build rapport with others. Connect with and appreciate their interests, values and priorities. Find out about them as individuals. You manage individuals, not generalizations.

Have you been stereotyped because of your generation? What have you experienced with these differing generations in the same workplace?

Posted on: October 20, 2016 11:43 PM | Permalink | Comments (2)

The "Hidden" Effort You Should Really Manage Better

Every once in a while, I am reminded that  there is an important chunk of work that occurs at predictable times and is rarely accounted for properly. That's sad, because if this effort can be accounted for, there is significant benefit for a project manager.

Why is this hidden work such a big deal? It can be substantial, but it is often treated like it is nothing. So those who do the work feel like their efforts are perceived as trivial. And they could blame you, the project manager.

And you don't want that.

It all starts when your project requires a formal change. Remember, this situation is predictable. It could be additional scope, schedule update or need for more money - doesn't matter. You then, of course, request estimates from various resources/teams in your project for their portion of the change. And you need these estimates quickly...the change control presentation is imminent!!

People spend a significant amount of time estimating the impact of a change. Take a common example, new requirements being added midstream during a waterfall PM process. Various teams must stop what they are doing, or add hours to their day, to calculate having to restart the requirements, design and development steps (among others). They have to make sure new requirements trace through to testing. There are dependencies to consider. This estimation work interferes with other work they planned to do and if they have to add hours, all their work suffers from lower productivity and even quality.  

It can be seen as a distraction or due to someone else's incompetence and not be given the attention it deserves. It can be seen as something you as project manager should have avoided.

That's not good.

And then you can be frustrated that it takes so long to complete. You wonder, how can this take so long? It's just a quick estimate! Meanwhile, estimators remember all the times that they rushed estimates and underestimated the work, only to be chastised later for going over budget.

That's certainly not helpful.

Put in this light, it should be clear that you should account for the estimation work to be handled in a more sophisticated manner.
How do you do this?

First, define a separate project activity to represent the analysis and estimation effort. It should have a set duration, agreed to by estimators.

Next, include a task in the activity to actually estimate the effort of estimation. OK, that sounds pretty bureaucratic, but follow me here. You just need to show something like number of estimators and hours for each to do their analysis and estimate. Add in time and resources for administrative work, along with production and delivery of the change request presentation. You are involved in that, right? And it is time-consuming in your experience, right?

Now you will have activity duration, resources and hours involved. Believe me that this will show you, stakeholders and decision-makers an objective picture of the surprising hidden impact of the change control process.

But, also, this will show respect for the pitiful lot who has to complete the analysis and estimates. Get them involved from the beginning, as this starts at a predictable time. Have them track all change request analysis work separately. You will win over some fans. They will very quickly see your genius.

Posted on: September 28, 2016 11:01 PM | Permalink | Comments (1)

"In Italy for thirty years under the Borgias they had warfare, terror, murder, bloodshed - but they produced Michelangelo, Leonardo da Vinci, and the Renaissance. In Switzerland they had brotherly love, 500 years of democracy and peace, and what did that produce? The cuckoo clock."

- Orson Welles, The Third Man

Test your PM knowledge



Vendor Events

See all Vendor Events