A Project Manager's Power: What You Actually Run On When Nobody Reports to You
Here is the org-chart truth of most project management jobs: the engineers building your project report to an engineering manager, the vendor answers to their own company, the platform partner answers to nobody you can reach, and you are accountable for all of them hitting a date. Whatever gets the work moving in that setup, it is not command. PMP study formalizes this with French and Raven's power bases, and for once the exam material describes real life accurately. What it undersells is the ranking: which powers hold up under load, and which ones are borrowed money.
Legitimate power: the title opens doors, once
Positional power is real: a charter naming you PM means people attend your meetings and answer your emails, at least initially. But in matrix organizations it is shallow. The title gets you the first meeting; it does not get you the engineer's honest estimate or the extra effort in a hard week. I think of legitimate power as an introduction, not an engine. PMs who lean on it repeatedly, "as the project manager, I need you to", teach everyone exactly how little is behind the phrase.
Reward and coercive power: usually not yours, and it shows
The textbook lists rewarding and punishing as power bases, and for most PMs both are on loan. You rarely set salaries or write reviews; at most you influence them through someone else. Coercion is worse than weak, it is corrosive: I have watched escalation-happy PMs get technically compliant teams that share exactly zero early warnings, which means the PM trades away the one thing they need most, the truth arriving early. What I have instead of formal reward power is small and surprisingly effective: making good work visible to the people who do set rewards, accurately and by name. Done consistently, that is a real currency.
Expert power: the one that compounds
Expert power is authority earned from demonstrated competence, and in technical delivery it is the strongest sustainable base there is. Not because the PM out-engineers the engineers, but because the PM who can read the integration diagram, ask the right question about the retry logic, and not need the problem explained twice gets a different conversation entirely. Estimates get more honest, risks get raised earlier, and pushback, when it comes, comes with reasons instead of silence.
My own path ran from full-stack engineering into delivery, and I can testify that the technical background pays rent daily, in credibility. But expert power has a maintenance cost: technology moves, and expertise from five years ago slowly converts into confident wrongness. Staying close enough to the code to keep the expert base current is, for a technical PM, a genuine professional investment, not nostalgia.
Referent power: slow to build, fatal to fake
Referent power is people cooperating because they trust you and want to work with you. It is built in small, boring transactions: taking the blame you own instead of routing it, defending the team's estimate to a sponsor, doing the thing you said by the day you said. Across cultures and companies I have found it the most portable power of all, and the slowest, which is why new PMs cannot skip ahead to it. The counterfeit version, being agreeable to be liked, collapses at the first hard call. Real referent power survives your unpopular decisions; it is trust, not popularity.
The practical mix, by situation
Day to day, I run on expert and referent power almost exclusively, with legitimate power as the doorway and the reward channel used honestly through visibility. But situations reorder the list. In a live incident, someone must decide now, and that is legitimate power exercised without apology, argued about later in the retrospective, as I described in the conflict post. With a brand-new team that has no history with me, the title and the charter carry the first weeks while expertise and trust get demonstrated, which connects to why forming-stage teams need explicit structure early.
The self-audit I recommend to any PM: for one week, notice which power you reach for when things get hard. If the honest answer is title and escalation, that is the profile of a PM one reorg away from having nothing. Expertise and trust are the only two bases that travel with you, project to project, company to company. Build the portable ones.
Nguyễn Hải Nam
Project Management Lead. 16+ years from code to delivery. PMP®. Writing here about project management and engineering.