5.1Leading a project team & motivation
The essentials in 30 seconds
- No formal authority: the project team is cross-functional, borrowed from departments — you manage through influence, not orders.
- Leadership = meaning + trust: unite people around the objective, empower and trust rather than command.
- Motivation beyond salary: clear roles, recognition, autonomy, growth, belonging.
Threaded mini-case — Bilal runs a cross-functional project in Algiers
Bilal, a project manager in an SME in Algiers, must deliver a project with a team of 5 people who do not report to him: each answers to their own manager. When he tries to “command”, availability melts away. This section tells how he shifts to leadership: clarifying roles, giving meaning, securing availability with managers and the sponsor, and engaging through recognition.
This same case returns in the lesson, diagram, script and 48h challenge — and continues in 5.2, 5.3, 5.4 and 5.5.
1. Managing without formal power
The project manager must get the best from a team over which they often have no hierarchical authority: the team is cross-functional, borrowed from different departments. Bilal discovers that an order given to someone reporting to another manager only produces avoidance.
Managing without formal “power” rests on leadership: giving meaning, uniting people around a shared objective, motivating and empowering rather than commanding. Bilal also secures availability upstream with line managers and the sponsor: without that frame, even the best leadership runs dry.
2. Human levers
The levers are human: clear roles and expectations, recognition, autonomy, trust, constant communication. Bilal clarifies role, responsibilities and expectations for each person: fuzziness demotivates faster than workload.
Understanding what motivates each person — beyond salary: meaning, growth, belonging — turns a group of individuals into a committed team. That is often what distinguishes successful projects: you engage durably by inspiring, not by constraining.
🔎 Concrete example — 🔎 Concrete example — Involving people who don't report to you
Influence, not orders.
Give meaning, show the interest in contributing, involve in decisions.
Secure availability with line managers and the sponsor.
→ you engage durably by inspiring, not constraining.Outcome: a group of individuals turned committed team.
Reflex: listen to understand what motivates each person.
Section vocabulary
- Cross-functional project team
- A team bringing together people from different departments, with no direct hierarchical link to the project manager.
Simple example: Bilal's 5 team members, each reporting to their own department.
What it is not: a hierarchical team where everyone reports to the same manager.
Reflex: have I secured each person's availability with their manager?
- Leadership
- The ability to influence, unite and motivate without relying on formal authority: making people want to follow.
Simple example: Bilal unites people around the objective instead of giving orders.
What it is not: commanding and punishing without explaining or listening.
Reflex: is each instruction linked to the project's meaning?
- Motivation
- What drives commitment: meaning, recognition, autonomy, growth, belonging — beyond salary.
Simple example: Bilal spots that one wants to learn, another to be recognized.
What it is not: believing only salary motivates the team.
Reflex: what concretely motivates each of my team members?
- Empowerment
- Entrusting responsibilities and trusting people, to engage rather than control.
Simple example: Bilal delegates a work package with expected outcome and room to maneuver.
What it is not: controlling every detail while keeping every decision.
Reflex: what did I delegate this week, and with what frame?
- Recognition
- Valuing contributions and successes: a powerful, often underused engagement driver.
Simple example: Bilal names each contribution in the weekly review.
What it is not: flagging only mistakes and never successes.
Reflex: whom did I explicitly recognize this week?
In practice — In practice — Mobilizing a team with no hierarchical authority
- Clarify for each person their role, responsibilities and what is expected of them: fuzziness demotivates.
- Give meaning: link each person's work to the project objective and its real usefulness.
- Identify what motivates each member (autonomy? learning? recognition?) and pull these levers.
- Practice regular recognition and empower (trust, delegate) rather than controlling everything.
Ready-to-say script — framing the cross-functional team (1 min)
“I have no hierarchical authority over you, so let us be clear: here is the project goal, each person's role and what is expected at each milestone. I am securing your availability with your managers. In return, you can expect meaning, autonomy and recognition from me — and I will decide fast when needed.”
Say at the kickoff meeting; write down roles, expectations and validated availability.
Copy-paste template — cross-functional mobilization sheet
MEMBER: _______________
ROLE + EXPECTATIONS (milestone, quality): _______________
AVAILABILITY VALIDATED WITH (manager / sponsor): _______________
MOTIVATION LEVER (meaning, autonomy, growth, recognition): _______________
PLANNED RECOGNITION (when, how): _______________Small team
Bilal wears several hats: a 20-minute weekly check-in is enough — roles restated, blockers lifted, one named recognition.
Remote / hybrid
At a distance, meaning gets lost: write down roles and expectations, and recognize in writing (nominative message) so everyone sees each other's input.
Algeria SME
Availability shared across departments plus travel: validate slots with each manager and the sponsor before promising a milestone.
Demotivated team member
Listen first for the cause (overload, meaning, recognition) without judging, act on the identified lever, then involve their manager if it persists.
✓ Best practices
- Clarify roles and expectations (fuzziness demotivates).
- Link each person's work to the project's meaning.
- Recognize and empower rather than controlling everything.
✗ Common pitfalls
- Wanting to command a team you have no authority over.
- Letting fuzziness settle over roles and expectations.
- Neglecting recognition (a powerful, underused driver).
Key takeaways
- Project managers often lead with no hierarchical authority.
- Leadership (meaning, uniting, trust) replaces formal power.
- Motivation goes beyond salary: meaning, autonomy, growth, recognition.
- Empowering and recognizing engages more than controlling.
48h challenge — apply tomorrow
Fill the mobilization sheet (template above) for 2 members of your team: role, expectations, motivation lever. Give 1 explicit recognition to each within 48 hours. Note the observed effect.
- I can explain why orders are not enough with no formal authority.
- I can name 4 motivation levers beyond salary.
- I have explicitly recognized 1 contribution this week.
Frequently asked questions
How to get commitment from people who don't report to me?
Through influence rather than orders: give meaning, show their interest in contributing, involve them in decisions concerning them, and recognize their inputs. Also secure their availability upstream with their line managers and the sponsor. You engage durably by inspiring, not constraining — which is anyway impossible with no hierarchical link. Meaning and recognition are your true levers.
How to handle a demotivated team member?
First seek the cause by listening (overload? lack of meaning? conflict? feeling unrecognized?), without judging. Then act on the identified lever: clarify, value, adjust load, restore autonomy. Often, feeling heard and considered already restarts engagement. If the problem persists, involve their line manager. A demotivated member left unanswered quickly contaminates the whole team's mood.
Bilal must mobilize 5 people reporting to other managers. What is his best lever?