Power, Influence and Empowerment in Projects

"Leadership is getting people to work for you when they are not obligated."

That single sentence is the most honest definition of a Project Manager's job you will ever read. It is also the reason this topic — arguably more than any schedule, risk register, or earned-value curve — determines whether you will survive your first decade in heavy engineering or defence project management.

Here is the uncomfortable truth every aspiring PM must internalise early: on most matrixed projects, you do not own the people doing the work. The welders on the complex naval-platform programme hull belong to a production manager. The systems engineer tracing requirements for the complex capability programme turret reports to an engineering line manager. The subcontract lead at major shipyard reports into supply chain. You are accountable for their output, but they do not answer to you on the org chart.

So how do projects actually get delivered? Through power and influence — two concepts that sound interchangeable in casual conversation but are critically distinct in leadership theory. This article unpacks both, shows you the seven recognised sources of power, walks through the core influence tactics, and grounds every concept in the realities of Australian major defence and heavy engineering delivery.

The "Why": Authority Runs Out Long Before the Work Does

In a classical functional organisation, a supervisor tells a subordinate to do something, and they do it. Clean. Simple. Almost entirely irrelevant to modern project work.

Project Managers operate in environments where:

• Team members are matrixed from multiple functional departments
• Key stakeholders are more senior than the PM (customers, sponsors, acquisition authority officers, Chief Engineers)
• Critical contributors are external (subcontractors, OEMs, export-control authorised specialists)
• Success depends on peer cooperation across silos (engineering, supply chain, production, quality, ILS)

In this environment, a leadership author's observation cuts deep: "Leadership is the capacity to influence. Influencing is how leaders lead. Hence, there can be no leadership without influence."

If you cannot influence without formal authority, you cannot lead a project. Full stop. The PMs who rise into programme director roles at major delivery organisations are, without exception, people who mastered this domain early.

The "What": Power, Authority, and Influence Defined

These three terms are used loosely in practice, but precision matters. Get them wrong in an interview or a programme review and your credibility evaporates.

Power is the capacity of one party (the agent) to influence the behaviour or attitudes of another party (the target) at a given point in time. It is a latent asset — you either have it or you don't, whether or not you choose to use it.

Authority is the bundle of rights, prerogatives, obligations, and duties associated with a particular position in an organisation or social system. A Project Manager's authority is typically delineated in the Project Charter, Delegation of Financial Authority matrix, or Contract Authority Schedule.

Influence is the act of exercising power to produce a change in another person's behaviour, attitudes, or decisions. Power is potential energy; influence is kinetic energy.

Why the Distinction Matters on a Defence Project

Imagine you are the Integrated Logistics Support (ILS) Manager on a multinational defence partnership sustainment programme. The Project Charter gives you authority to chair the Supportability Working Group. But if the Principal Engineer from the platform OEM does not respect your technical judgement, your authority is an empty chair. You have the right to run the meeting; you do not have the power to make its outcomes stick. Decisions will be relitigated in hallway conversations you are not invited to.

Authority without power is bureaucracy. Power without authority is politics. Effective PMs need both — and they earn power sources that compound the authority granted by their position.

The Seven Sources of Power (the supplied research, and Beyond)

The 1959 power-bases typology originally identified five bases of power. Subsequent researchers — particularly later research — extended this to seven. This expanded model is what contemporary leadership curricula at an Australian university and elsewhere now teach, and it is the framework you should have fluent at your fingertips.

These seven sources split cleanly into two categories: Position Power (derived from your formal role) and Personal Power (derived from who you are and what you know).

Position Power in Practice

Legitimate Power flows from formal authority. Your power to approve a Variation Purchase Request up to $50k, your authority to chair the Engineering Change Board, your mandate to sign off a System Acceptance Test — these are all legitimate power. The catch: legitimate power only works when the target accepts your authority. Members of an organisation comply with direction in return for the benefits of membership; this is an implicit contract, not an absolute guarantee. The moment a senior engineer decides your authority is illegitimate (because you lack technical credibility, or because the request exceeds your scope), legitimate power evaporates. Reward Power rests on the target's perception — not the reality — that you control resources they value. On a defence project, rewards are rarely cash. They are far more often: career-defining assignments, visibility to senior executives, training budget, preferred shift rosters, access to classified work packages, or a quiet word to the target's functional manager at performance review time. A PM who can credibly promise and deliver such rewards has formidable influence over matrixed team members. Coercive Power is authority over punishments. In military and political contexts it is substantial. In corporate Australian project environments it is deliberately constrained — the worst a PM can usually do is escalate, document poor performance, or remove someone from the project. Coercive power is the most dangerous source in your toolkit. Overuse poisons trust, breeds retaliation, and destroys the referent power you have painstakingly built. Information Power is the access to and control over vital information. Do you have the real schedule slippage data? The true cost-to-complete? The customer's unspoken concerns from the last Programme Management Review? In complex programmes running supplied sixth-edition process framework-grade controls, the PM sits at a natural information nexus. Used well, this is legitimate influence. Used manipulatively — hoarding information to force dependency — it corrodes the project culture fast. Ecological Power — sometimes called situational engineering — is control over the physical environment, technology, and organisation of the work. The PM who chooses to co-locate the systems engineering team in a single war room rather than leave them scattered across three buildings is exercising ecological power. So is the PM who redesigns the daily stand-up format, changes the RAID log tooling, or rearranges desk layouts to put quality assurance next to production. It is subtle, indirect, and extraordinarily effective.

Personal Power in Practice

Expert Power comes from task-relevant knowledge and skill. On heavy engineering and defence programmes, this is the power source most respected by the technical workforce — and the one most aspiring PMs underestimate. An APM who can credibly discuss applicable technical framework hazard analysis, read a P6 schedule's critical path, or interpret an EVM variance calculation commands respect that no org chart can manufacture. Critically, expertise is only power if the target recognises it and perceives you as a reliable source. You must develop and maintain a reputation for technical credibility. This is why the career advice "write the status report yourself before you delegate it" matters so much early-career — you build expert power by visibly doing the work well. Referent Power is the most elusive and arguably the most durable. It is derived from the target's genuine desire to please you because they admire, respect, or like you. It is built through integrity, consistency, genuinely caring about the team, delivering on your commitments, and protecting your people from unreasonable demands. Referent power takes years to build and can be destroyed in a single act of perceived betrayal.

influence-process model Three Influence Processes

When an agent exerts power, what actually happens inside the target's head? Influence-process model proposed three distinct psychological mechanisms, and understanding them is the key to predicting the durability of the outcome you achieve.

The project leadership implication is profound. If you rely on reward and coercive power (driving instrumental compliance), you will spend the rest of the programme policing effort. If you build expert and referent power and influence through inspirational appeals and consultation (driving internalisation), your team will push the project forward when you are not in the room.

Influence Outcomes: The Traffic Light Model

Every influence attempt yields one of three outcomes. Think of them as a traffic light:

Resistance — the target is actively opposed to the request, not merely indifferent. They will push back, escalate, delay, or undermine.

Compliance — the target is willing to carry out the request but is apathetic. They will make the minimum effort required. The work will technically happen but will lack creativity, discretionary effort, or early warning of problems.

Commitment — the target makes a genuine effort to carry out the request or implement the decision effectively. They will problem-solve, surface risks early, and go beyond the literal instruction.

On a high-stakes defence programme — where the cost of a missed risk may run to tens of millions of dollars and where fifteen-year sustainment tails punish short-term thinking — compliance is not good enough. A PM who consistently achieves only compliance is running a project on the edge of failure without realising it. The team is doing exactly what was asked; nothing more. Commitment is the operational standard you must aim for.

Influence Tactics: The PM's Toolkit

Power is the latent capacity. Tactics are how you actually convert it into outcomes. The supplied research identifies eleven proactive influence tactics; three of them — the core tactics — are the most effective and the ones every PM must master.

The Three Core Tactics

1. Rational Persuasion — Explain in detail why the request or proposal is important. Use facts, logic, and evidence. Show that the proposal is feasible and better than the alternatives. On a defence programme, this means walking into a Technical Review Board with the trade study, the cost model, the schedule impact analysis, and the risk register. Engineers respect data; rational persuasion is the default tactic for technical decisions. 2. Inspirational Appeals — Frame the proposed change as an exciting, worthwhile opportunity. Link the activity to the target's ideals and values. Describe a clear, appealing vision of what will be accomplished. Use dramatic, expressive language. On the complex naval-platform programme, an inspirational appeal connects a junior engineer's daily grind on a hull block interface drawing to the reality that they are building the naval customer's next-generation anti-submarine warfare capability. Logic does not win hearts; inspiration does. 3. Consultation — State your objective and ask what the person can do to help attain it. Seek suggestions on how to improve a tentative proposal. Involve the person in planning the action steps. Respond positively to their concerns. Consultation is psychologically powerful because it transfers ownership — a proposal the target helped shape becomes their proposal, and they will fight for it.

Impression Management and Political Tactics

Two supporting categories deserve mention:

• Impression Management Tactics aim to shape how others perceive the agent — ingratiation (being likeable), self-promotion (advertising competence), exemplification (modelling desired behaviour). These flow in all directions: upward to sponsors, laterally to peers, downward to team members.
• Political Tactics aim to influence organisational decisions or gain benefits for an individual or group. Coalition building, upward appeals, and strategic information sharing all fall into this category. Political tactics are unavoidable in large defence primes. Ignoring them is naivety, not virtue.

Your Influencing Style

Every PM develops a dominant influencing style. Know yours — and know when it is failing you.

Great PMs are not locked into one style. They read the situation and shift fluidly — asserting when a safety risk demands it, bridging when a long-term coalition needs to be built, inspiring at the programme kick-off, convincing at the technical review.

Guidelines: How to Actually Use Each Power Source

Theory is cheap. Here is the operator's manual.

Using Legitimate Authority

• Make polite, clear requests. ("Could you…" always outperforms "I need you to…")
• Explain the reasons for the request. Authority plus rationale is far stronger than authority alone.
• Don't exceed your scope of authority. Overreach destroys legitimate power irreversibly.
• Verify authority if necessary; follow up to confirm compliance.

Using Reward Power

• Offer rewards people actually want, not what you assume they want.
• Keep the criteria fair, ethical, and transparent.
• Never promise what you cannot deliver. A single broken promise destroys reward power for years.
• Explain the criteria simply. Complex reward schemes feel manipulative.

Using Coercive Power (Use Sparingly)

• Make rules and consequences explicit in advance.
• Respond to infractions promptly and consistently. Favouritism destroys credibility.
• Get the facts before reprimanding. Never jump to conclusions.
• Except for the most serious breaches, provide warnings before punishment.
• Deliver reprimands in private. Never humiliate.
• Stay calm. Avoid the appearance of hostility or personal rejection.
• Invite the person to suggest ways to correct the problem.
• Follow through on warnings — an unenforced threat destroys coercive power permanently.
• Punishments must be legitimate, fair, and proportionate.
• Avoid coercion unless absolutely necessary. It reliably produces anger, resentment, and retaliation.

Using and Maintaining Expert Power

• Always explain why a request matters.
• Provide evidence the proposal will succeed.
• Never make rash, careless, or inconsistent statements.
• Never lie, exaggerate, or misrepresent the facts. A single caught exaggeration destroys expert power.
• Listen seriously to concerns and suggestions — expertise is a conversation, not a monologue.
• Act confident and decisive in a crisis.

The Pitfalls: How PMs Destroy Their Power Base

Common failures, ranked roughly in order of career damage:

1. Confusing authority with power. Believing your Project Charter is enough. It isn't. Power is earned, not assigned.
2. Over-reliance on coercive power. Every reprimand deposits a coin into a resentment account that will eventually be cashed in against you.
3. Using referent power dishonestly. Exploiting loyalty to extract sacrifices you would never ask of yourself is the fastest way to destroy it.
4. Letting expert power atrophy. Stopping learning the moment you become a PM. The technical world moves under your feet; stale expertise is worse than no expertise.
5. Hoarding information to create dependency. It works briefly and catastrophically backfires when the team realises what you are doing.
6. Mistaking compliance for commitment. Assuming that because the work is happening, the team is engaged. Compliance projects fail quietly, late, and expensively.
7. One-dimensional influencing style. Being a pure "Asserter" in a matrix environment. Being a pure "Bridger" in a schedule crisis. The style must match the situation.

Knowledge Check

Before you move on, test yourself:

1. A Project Manager has authority, but the project team has the power. What does this mean, and is it a healthy or unhealthy dynamic?
2. Give a concrete example of each of power-bases framework five original power sources, properly used by a PM on a major defence programme.
3. How does leading a functional team differ from leading a project team, and which power sources become disproportionately important in each context?
4. You are a new assistant project manager who has just inherited a team where the previous PM destroyed trust through heavy-handed coercive power. What is your 90-day plan to rebuild the power base?
5. Your lead systems engineer is resisting a design change you have been directed to implement by the customer. Walk through which influence tactic you would use, which power source you would draw on, and what outcome (resistance, compliance, or commitment) you are realistically targeting.

Key Takeaways

Authority is assigned. Power is earned. Influence is exercised. Confusing these three concepts is the single most common mistake made by new project managers.

There are seven sources of power, split between position power (legitimate, reward, coercive, information, ecological) and personal power (expert, referent). On matrixed defence programmes, personal power sources are the durable ones — position power evaporates the moment you change roles.

influence-process model influence processes — instrumental compliance, personal identification, internalisation — predict how long an outcome will last. Aim for internalisation. Always.

The traffic light outcomes are resistance, compliance, and commitment. Compliance is not good enough on high-stakes programmes. Commitment is the operational standard.

The three core influence tactics are rational persuasion, inspirational appeals, and consultation. Master these before worrying about the eight supporting tactics.

Use coercive power as sparingly as possible. Every use depletes your referent power account.

Your influencing style is not fixed. Great PMs shift between asserting, convincing, negotiating, bridging, and inspiring depending on the situation.

The PM's ultimate test: Can you get people to do excellent work for you when they are not obligated to? If yes, you are a leader. If no, you are a coordinator with a nice title.

Integrated Insights from the Supplied Source Set

The archive contains several overlapping treatments of this subject. The following sections retain the most distinct practical material while avoiding a second article that teaches the same core topic.

The "Why": Authority Without a Direct Report

Integrated source perspective — Source 35: This section preserves distinct material from an overlapping source treatment.

Walk onto the deck of a complex naval-platform programme under construction at major shipyard. The Project Manager coordinating combat system integration may have ninety engineers, forty technicians, six subcontractor leads, and a handful of public-sector customer representatives in their daily orbit. How many of them report directly to the PM on an organisational chart?

Almost none.

This is the defining paradox of modern project leadership: accountability is vertical, but authority is horizontal. The PM owns the schedule, the risk register, the cost baseline, and — ultimately — the deliverable. Yet the resources needed to produce that deliverable sit inside functional silos governed by engineering managers, discipline leads, and programme directors.

In this environment, the PM who relies solely on the authority of their job title is destined to fail. The PM who understands how power actually flows — and how to convert power into willing influence — is the one who ships the ship.

Practice note — supplied research: "Leaders can build trust by practicing openness, being fair, speaking their feelings, telling the truth, showing consistency, fulfilling their promises, maintaining confidences, and demonstrating competence."

The shift from command-and-control to empowerment is not a management fad. It is a structural response to three realities of heavy engineering and defence projects:

1. Technical complexity has outstripped any single person's ability to direct every decision from the top.
2. Self-managed teams (Integrated Product Teams, Agile squads, discipline pods) have become the delivery unit of choice.
3. Non-authority relationships — matrix peers, contractors, government clients — now dominate the project ecosystem.

Trust, not hierarchy, is the currency of delivery.

Things a leader shouldn't do

Integrated source perspective — Source 60: This section preserves distinct material from an overlapping source treatment.

• Don't set out to impress your new team
• Don't be a 'task master' boss — autocratic, results-driven, providing little feedback
• Don't keep people in the dark — share information with all team members
• Don't pretend you have all the answers
• Don't favour one team member over another
• Don't place being liked over being respected

Practice note: The single highest-leverage rule Stay visible and talk — and listen — face-to-face. Almost every other rule on both lists derives from this one. The PM who hides behind email and Teams chats has already lost the game.

The "How": Empowerment — The Modern Alternative

Integrated source perspective — Source 69: This section preserves distinct material from an overlapping source treatment.

Practice note — supplied research: It is a clear fact that managers are increasingly leading by empowering their employees.

Empowerment is being driven by two forces:

1. The need for quick decisions by those closest to the problem
2. Organisational downsizing which has left managers with larger spans of control and forced delegation

But empowerment is not a universal panacea. The anti-contingency view — that empowerment should always be maximised — is wrong. Empowerment works when:

• The workforce has the knowledge, skills, and experience to do jobs competently
• Employees seek autonomy
• Employees have an internal locus of control

Where these conditions are absent, empowerment without capability leads to failure; empowerment without desire leads to disengagement.

Applying the Guidance as a Controlled Practice

Use this subject as a decision aid, not as a label applied after the event. Start by defining the delivery problem, the people affected, the authority available and the consequences of a poor decision. Record assumptions before selecting an intervention. That simple discipline makes later review possible and prevents a preferred leadership style from being treated as the answer to every situation.

Six-Step Application Cycle

1. Define the trigger. State the decision, behaviour, team condition or delivery risk that requires attention. Separate observation from interpretation.
2. Map the context. Identify the project phase, task uncertainty, dependencies, stakeholder interests, time pressure, team capability and formal authority.
3. Choose a proportionate response. Select the smallest intervention capable of improving the condition. Explain why it fits the evidence and what alternatives were rejected.
4. Agree ownership and boundaries. Make decision rights, escalation points, review dates and non-negotiable safety or ethical limits visible to the people involved.
5. Act and observe. Monitor both delivery indicators and human signals such as challenge, information sharing, participation, trust and follow-through.
6. Review and adapt. Compare the result with the original intent. Retain, adjust or stop the intervention, and capture the learning for the next phase.

Evidence and Verification

Evidence should be proportionate to the project's risk and governance needs. A short decision note may be sufficient for a routine team adjustment; a high-consequence change may require sponsor approval, formal consultation, controlled records and a scheduled assurance review. Documentation must support judgement rather than replace it.

Review Questions

• What observable condition are we trying to change, and how will we know if it improves?
• Whose perspective is missing from the diagnosis or decision?
• Are authority, accountability and capability aligned, or are we asking someone to own an outcome they cannot control?
• Could the intervention suppress challenge, conceal risk or create dependency on one individual?
• What evidence will trigger escalation, adaptation or closure?

Practice boundary: Frameworks in this article organise thinking; they do not guarantee performance. Project context, contractual obligations, safety duties, workplace requirements and approved governance remain controlling.