Project managers often need people to act without having direct managerial authority over them. Influence is the ability to gain cooperation, change a decision or mobilize resources, while formal authority is the right to make specified decisions. Confusing the two creates problems in matrix organizations, where engineers may report to line managers but deliver work across several projects.

A longstanding framework associated with French and Raven describes five sources of interpersonal power: legitimate, reward, coercive, expert and referent. PMI’s project-management literature applies those categories to collaboration with project personnel. The categories are useful lenses, not a license to manipulate colleagues or assume the strongest formal title always wins.

Legitimate power: authority from a defined role

Legitimate power arises when people recognize that a role has properly delegated decision rights. A project charter, governance policy or signed agreement may allow a project manager to coordinate approved scope, sequence work and escalate deviations. The relevant question is what the authorization actually covers.

Suppose a manager leads a new warehouse automation project. The charter may permit spending up to an agreed limit and approving routine schedule adjustments. It does not necessarily permit overruling safety inspectors, disciplining staff employed by another department or increasing overall funding without sponsor approval.

When a conflict arises, distinguish the task request from the authority behind it. A project manager may require a team member to report an accepted milestone but still need the functional manager to approve permanent role changes. The project and line-management relationship shows why the source and limits of formal power vary by structure.

Reward power: access to valued recognition and opportunity

Reward power comes from the perceived ability to provide something a person values: recognition, a challenging assignment, learning opportunities or other benefits. A project manager can sometimes recommend performance recognition or offer meaningful work, but often does not control salary or promotion decisions.

Recognition should reflect genuine contributions and transparent criteria. A manager who praises only those who agree publicly can suppress honest defect reporting. A useful reward system acknowledges early risk identification, quality evidence and effective cooperation rather than just apparent speed.

Imagine a difficult integration task completed with exceptional documentation and safe testing. A project leader can ensure the effort is visible to the functional manager and sponsor. That support may be more ethically defensible and operationally valuable than promising a promotion that the project manager cannot authorize.

Coercive power: sanctions and why it is risky

Coercive power is influence based on feared negative consequences such as penalties or undesirable assignments. It may exist where formal rules allow discipline or contractual sanctions, but habitual threats often damage trust, conceal problems and reduce the willingness to raise uncertainty.

A safety-critical team needs clear consequences for deliberate violation of mandatory controls. That is different from threatening a specialist because an approved dependency shifted. Appropriate escalation protects compliance and due process; inappropriate intimidation makes the dashboard look calm while the underlying risk grows.

If a supplier repeatedly fails a contractual obligation, a project manager should document acceptance evidence, use procurement procedures and invoke the correct authority. Inventing a personal punishment outside those rules is not effective governance. Formal consequences should be fair, proportionate and supported by records.

Expert power: credibility through demonstrable knowledge

Expert power grows when colleagues believe the manager understands the project, can interpret constraints and offers sound technical or organizational judgment. It is not limited to a specialized engineering credential: integration knowledge, clear risk reasoning and accurate stakeholder information can make a manager’s advice valuable.

Expertise has boundaries. A project manager with deep scheduling skills should not overrule a structural engineer’s safety analysis on the strength of being a good planner. Acknowledging where independent expertise is required strengthens credibility instead of weakening it.

In a hospital system rollout, the project lead might explain how a failed interface test changes dependency sequencing and cost exposure. A security specialist retains responsibility for interpreting the control defect. Combining both perspectives produces a stronger recommendation than pretending one person’s expertise covers every field.

Referent power: trust and relationships

Referent power comes from respect, identification and the quality of a leader’s relationships. People may cooperate because a manager consistently listens, follows through and treats conflicts fairly. It cannot simply be granted by a new job title.

Trust matters in temporary cross-functional teams. A project manager who admits a forecasting error, credits the people who raised it and transparently revises the plan may have greater influence than one who demands optimistic status. Such behavior encourages early warning and constructive disagreement.

Referent influence must not become favoritism. A manager can build productive relationships while documenting decisions, respecting professional boundaries and offering equivalent opportunities for input to people who are less socially connected.

Information and networks can extend the model

Some project-management authors discuss additional influence bases such as information, persuasion and connections. These categories extend or refine the original five rather than replacing them with a universally agreed new count. Access to reliable information and the ability to explain it persuasively can be powerful when formal authority is limited.

A clear dependency map, supplier forecast and stakeholder-impact analysis can change a sponsor’s decision more responsibly than a personal appeal. Information becomes useful when it is accurate, shared with the right participants and open to challenge—not when a leader hoards it as leverage.

The stakeholder engagement process can help identify who holds relevant evidence, who has authority and whose interests will be affected by an action. Using the framework to understand relationships is different from labeling people as targets for persuasion.

Applying influence in a real resource conflict

A security engineer is reassigned to an incident just as a migration project approaches release. The project manager cannot order the engineer to return because staffing authority belongs to a functional manager. The security expert has the professional knowledge to judge residual risk, while the sponsor controls the commercial decision. Influence begins by making those boundaries explicit, not by issuing a command the project role cannot enforce.

Identify which review tasks remain, the amount of qualified time required and the consequence of delay. Present possible options—alternate qualified reviewer, staged delivery or revised release date—to the line manager and sponsor. A trusted relationship helps people discuss trade-offs, but it does not allow the manager to waive a mandatory security control. If the conflict persists, escalate the decision with evidence rather than implying that one department is obstructing the project.

Suppose a software release and an infrastructure upgrade both require the same database specialist. The project manager’s legitimate authority covers the software project’s agreed work, but the specialist’s line manager controls department staffing. The sponsor can help determine organizational priority if a conflict exceeds the managers’ delegated limits.

Expert influence helps explain what will happen if a data migration is interrupted; referent influence helps build a candid discussion; information supports an evidence-based priority decision. Reward power may support meaningful recognition for the specialist. Coercive threats would likely make the conflict worse and may exceed the manager’s authority.

The responsibility without authority problem becomes manageable when decision rights, escalation and mutual commitments are explicit. The practical goal is coordinated work that meets the business objective, not a contest over who can issue the most forceful order.

Develop influence without losing accountability

Reward and referent power have limits. Promising public recognition in return for skipping a control confuses motivation with governance; personal trust does not create authorization. Record who approves the option, the conditions attached to it and the effects on operations. Influence that protects the decision process is more durable than pressure that wins a meeting and leaves an undocumented exposure.

At initiation, learn the formal mandate and the professional limits of key roles. During planning, earn confidence by making assumptions and dependencies visible. During execution, follow through on decisions, recognize evidence, and handle mistakes without assigning arbitrary blame.

Review the effect of your influence strategy. Are people raising risks earlier? Do sponsors decide on material trade-offs before they block work? Are technical experts willing to challenge assumptions? The project leadership approaches can provide context for choosing how to communicate under different circumstances.

Power in project management is best used to create clarity and protect outcomes. Legitimate authority establishes boundaries, expertise and information improve decisions, and earned trust enables cooperation. When managers rely on fear or unearned personal promises, they risk losing the evidence and goodwill needed to deliver a temporary project successfully.