Motivation and recognition on projects

Project managers rarely control salaries, promotions or job titles, yet they are expected to keep teams motivated through long, demanding projects. The good news is that the most powerful motivators for knowledge work are within a project manager's reach: meaningful work, autonomy, growth, recognition and a sense of progress. This lesson applies motivation theory to the project setting. The theories themselves are covered in more depth in BUS-130 Organizational Behaviour; here the focus is on what a project manager can do on Monday morning.

Motivation theories at a glance

Several theories appear repeatedly in PMP preparation. You should be able to recognize each and apply it to a scenario.

The theories converge. Herzberg's motivators, Pink's autonomy, mastery and purpose, and self-determination theory's autonomy, competence and relatedness all point the same way: once basic needs and fair treatment are in place, people are most motivated by work that matters, control over how they do it, the chance to get better and good relationships with colleagues. A project manager can influence every one of these.

Expectancy theory in practice

Vroom's expectancy theory is the most useful for diagnosing motivation problems because it breaks motivation into three links that can each fail. It is often written as a product:

Here \(E\) (expectancy) is the person's belief, from 0 to 1, that effort will lead to the required performance; \(I\) (instrumentality) is the belief, from 0 to 1, that performance will lead to the outcome; and \(V\) (valence) is how much the person values the outcome, often scored from −1 to +1. Because the terms multiply, a zero in any one of them produces zero motivation, however strong the others are.

The lesson for project managers is that offering a bigger reward rarely fixes a motivation problem if people do not believe the goal is achievable or do not trust that the reward will materialize. Involving the team in estimating and planning raises expectancy. Keeping promises, and not making promises you cannot keep, protects instrumentality. Asking people what they value improves valence.

What project managers can and cannot control

In a matrix organization, the project manager usually cannot change pay, grant promotions or redesign job descriptions. These belong to functional managers and human resources. But a project manager controls or strongly influences much of what research shows matters most.

One of the most powerful factors is a sense of progress. Teresa Amabile and Steven Kramer studied thousands of diary entries from knowledge workers and found that the single most important event in a good workday was making progress in meaningful work, even small progress. Setbacks had an even larger negative effect. Project managers can harness this "progress principle" by breaking work into visible chunks, celebrating milestones, making progress visible on boards and burn-up charts, and, above all, removing the obstacles that cause setbacks.

Recognition and rewards

Recognition acknowledges people's contributions; rewards add something of value, such as a gift card, a day off or a training opportunity. Both are most effective when they are timely, specific, sincere and matched to what the person values. Some people love public praise at an all-hands meeting; others would rather receive a private note or a word to their manager. Ask.

A recurring PMP theme is the danger of win-lose rewards. A "team member of the month" award given to one person can damage collaboration on a team whose success depends on cooperation, because it turns colleagues into competitors. PMI material generally favours win-win rewards that recognize team accomplishments or that everyone can earn by meeting clear criteria. Individual recognition still matters, but it should reward behaviour the team values, such as helping others, rather than pitting people against each other.

Motivation across the project life cycle

Motivation tends to follow a pattern. Energy is often high at the start, when the project is new and full of possibility. It can sag in the long middle, when work is hard, the end is far away and early enthusiasm fades. It may rise again near the end as delivery approaches, or collapse if the team is exhausted or the project is in trouble. Project managers can plan for this: build in visible milestones and celebrations during the middle, rotate challenging assignments, refresh the connection to purpose (for example, by inviting a user to describe how the product will help them), and watch for signs of burnout.

Burnout deserves particular attention. The World Health Organization describes burnout as an occupational phenomenon resulting from chronic workplace stress that has not been successfully managed, characterized by exhaustion, increased mental distance from or cynicism about one's job, and reduced professional efficacy. On projects, burnout is often caused by sustained overtime, unclear priorities, constant change and lack of control. Agile's principle of a sustainable pace, which says sponsors, developers and users should be able to maintain a constant pace indefinitely, exists for this reason. Repeated overtime is a planning problem to be fixed, not a motivation tool.

Workload also has legal limits. Provincial employment standards and, for federally regulated workplaces, the Canada Labour Code set maximum hours, overtime pay and rest periods for employees who are covered, although many managers and some professionals are exempt. Ontario and some other jurisdictions also require certain employers to have a written policy on disconnecting from work. Occupational health and safety laws increasingly treat psychological hazards such as excessive workload as workplace risks.

Motivating different people

Motivation is individual. A useful habit is to have a short conversation with each team member early in the project about what they hope to get from it: new skills, visibility, a particular kind of work, flexibility, or simply a calm project after a stressful one. Record it privately and use it when assigning work, giving recognition and writing feedback. People notice when their manager remembers what matters to them.

Watch also for demotivators, which often matter more than motivators. Common ones on projects include unclear or changing priorities, decisions made without consultation, recognition that goes to the wrong people, broken promises, useless meetings and reporting, poor tools, and unresolved conflict. Removing a demotivator is often cheaper and more effective than adding a reward.