Managing work and leading people are two different jobs that happen to sit with the same person. Managing work means sequencing it, funding it, tracking it and deciding what happens when it slips. Leading people means getting a group to want the outcome enough to make good decisions about it when nobody is watching. A project manager who does only the first ends up with a schedule that is accurate and a team that waits to be told.
Where the two jobs separate
The test is what happens to the work in your absence. Managed work stops or drifts, because the coordination lived in one head and that head is not in the room. Led work carries on, because the team understands the outcome well enough to make the small calls the plan never anticipated. Every project generates far more of those small calls than any plan can hold, which is why leadership on delivery work is the thing that makes management survivable.
The style follows the team, not the leader
Situational leadership says the right style is a function of the person in front of you and the task in front of them, rather than of the leader's temperament. It turns on two variables. Competence is whether somebody can actually do this particular task, and confidence is whether they believe they can and will commit to it. The two move independently, which is the part most often missed. An engineer who has done this ten times may still hesitate because the last attempt went badly, and a new joiner may be enthusiastic and completely wrong.
The unit of assessment is the task rather than the person. The same developer may need close direction on a regulatory reporting change and none at all on the service they wrote. Treating somebody as senior or junior across the board is the common error, because it fixes a style to a job title instead of to the work in hand.
Four positions on one scale
Competence decides how much of the method the leader supplies. Confidence decides whether the leader has to stay in the room while it is used. The same person occupies different cells on different tasks in the same week.
| Style | Competence on this task | Confidence on this task | What the leader actually does |
|---|---|---|---|
| Directing | Low | Anywhere, often high | Sets the goal, specifies the method, checks the work at short intervals and corrects it in the moment |
| Coaching | Growing, still partial | Low, momentum lost | Keeps deciding the approach, explains why it was chosen, invites the objection and hands back part of the next decision |
| Supporting | High | Low or uneven | Puts the decision to them, asks what they would do, stays available while they do it and backs the answer they gave |
| Delegating | High | High | Agrees the outcome and the boundaries, hands over the authority to reach it, and reads the result rather than the method |
Placing somebody takes two questions rather than an impression. Ask them to describe how they would do the task, and the answer shows competence. Ask what would make them hesitate to start on Monday morning, and the answer shows confidence. The two errors that follow from guessing cost differently. Directing somebody who is entirely capable reads as distrust and is repaid with the minimum, while delegating to somebody who is out of their depth surfaces weeks later as a missed date nobody flagged.
These are positions on a continuum, and movement runs in both directions. A team that has been delegated to for a year will need directing again the week the technology changes underneath it. Reading that as a regression, or as a personal failure, is how people end up delegating to somebody who is quietly drowning.
Leading without line authority
The people a project manager leads are usually hired, appraised and promoted by somebody else, whose priorities overlap with the project's without matching them. That is the ordinary shape of the role rather than an unfortunate accident of it.
What it changes is where compliance comes from. Instruction works on people who report to you and slides off people who do not, so the working currencies become clarity about the outcome, reciprocity, and a reputation for being right about what matters and honest about what does not. It also makes the functional manager a stakeholder to be negotiated with, and going around one costs a great deal more than the single decision it wins.
A vision people can act on
A vision is only useful if somebody two levels away can use it to settle an argument without asking. That is a much higher bar than a statement everyone agrees with, and most project visions fail it by being unopposable. Nobody argues with faster and better.
An actionable vision names what the project is for, who it is for, and what it is willing to give up in order to get there. The last part is what makes it usable, because a vision that sacrifices nothing offers no guidance when the trade off arrives late on a Friday and the person holding it cannot reach you.