The Project Manager’s Role, Functions and Matrix Authority

"Don't tell people how to do things, tell them what to do and let them surprise you with their results." — a historic military commander

The "Why" — Why This Topic Matters to a Project Manager

Ask a newly promoted assistant project manager in any major delivery organisation what they thought the job would be. You'll almost always hear the same thing: "I thought I'd be planning the schedule and running the risk register." Ask them what the job actually is six months later, and the answer changes: "I spend my day in conversations I didn't book, putting out fires I didn't start, chasing decisions I can't make alone."

That gap — between the textbook image of management and the lived reality — is what this topic is about. The supplied sixth-edition process framework and formal project method describe the process groups and the themes. But neither tells you what a project leader's day looks like, why decisions rarely follow the rational model in the textbook, or why the long-standing observations in the supplied research still describe your inbox better than any modern framework.

For an aspiring PM in heavy engineering, defence, or manufacturing, understanding the functions, roles, and situational determinants of management is the difference between being a good administrator of a project and being an effective leader of one.

The "What" — Core Concepts

The Four Classical Functions

The orthodox starting point — taught in every business school since an early management theorist — is that managers do four things:

Planning · Organising · Leading · Controlling

This is the tidy model. It is also, by itself, misleading — because it implies managers spend their day moving sequentially through these functions like a process diagram. They don't.

What Research Actually Found

Studies of managerial behaviour — beginning with the supplied research observational work and reinforced by eight-step change sequence and management research — found something very different from the textbook image:

• The typical manager works long hours, takes work home, and seldom enjoys an uninterrupted block in the day.
• Most interactions are initiated by others; behaviour is reactive more often than proactive.
• Problems arrive in a largely random order; managers triage, react to some, postpone others, and deliberately ignore the rest.
• Decisions are frequently driven by emotion, intuition, and political negotiation — not the rational analysis assumed by classical decision theory.
• Information is often distorted or suppressed to serve pre-existing biases about the right course of action.

Core principle: The popular image of the manager as someone who "carefully plans and orchestrates events, then sits in the office waiting for exceptions" is empirically false. Real managerial work is fragmented, reactive, verbal, and political.

Important vs. Routine Decisions cluster into two very different categories, and confusing the two is a classic PM error.

A prolonged, highly political decision process is likely when problems are complex, parties have conflicting interests, and power is diffused across stakeholders — exactly the conditions of a major defence acquisition under applicable contract framework or a public-sector customer gate review.

Planning — The Myth and the Reality

Planning is described in textbooks as a "formal process of written objectives, strategies, policies and budgets, cascading from top management down the hierarchy."

The research tells a different story:

• The supplied research found that general managers develop agendas — loose collections of goals and plans, mixing short- and long-term issues — and implement them gradually and continuously, not in formal annual cycles.
• The supplied research found that many important strategic decisions were made outside the formal planning process, in an incremental, flexible, and intuitive manner — what he called logical incrementalism.

Key insight for PMs: Your project plan is a baseline, not a script. The real planning happens continuously, in corridor conversations, at the coffee machine, and in the quiet hour before everyone else arrives.

The "How" — Ten Managerial Roles

The supplied research's most enduring contribution was a taxonomy of ten roles, grouped into three categories, derived from observing what executives actually did minute by minute. For a Project Manager, these are not academic abstractions — they are the diary entries you'll write at the end of every day.

Interpersonal Roles — Providing Information and Ideas

• Figurehead — You carry social, ceremonial, and legal responsibilities. At a project kick-off, a sponsor briefing, or a tier-gate review, you are the project in the room.
• Leader — You manage performance, motivation, and accountability of the team. This is the role most PMs over-index on in self-image and under-deliver on in practice.
• Liaison — You build and maintain a network of internal and external contacts. In defence work this means acquisition authority, the prime, sub-contractors, DASA, and the customer end-user — often simultaneously.

Informational Roles — Processing Information

• Monitor — You continuously scan the project environment for changes: technical, commercial, political, and personal. The daily stand-up is monitoring; so is the quiet conversation with the lead engineer who looks tired.
• Disseminator — You push useful information down and across to your team. Filtering noise from signal is half the job.
• Spokesperson — You represent the project outward, to steering committees, external stakeholders, and regulators. Your words become the project's official position.

Decisional Roles — Using Information

• Entrepreneur — You initiate change: improving processes, championing new ideas, sponsoring innovation within the project.
• Disturbance Handler — When something breaks — a vendor fails, a critical resource resigns, a test article is damaged — you take charge and mediate disputes.
• Resource Allocator — You decide where money, people, and time go. Every budget reallocation and re-prioritisation is this role in action.
• Negotiator — You participate in and direct negotiations with vendors, sponsors, unions, and team members.

Situational Determinants — Why Context Changes Everything

The same Project Manager, doing the same job, will behave very differently depending on the situation they're operating in. The supplied research and later researchers identified four key situational determinants:

Organisational Unit Size

When a PM has a large number of subordinates, two things happen — and both are bad for cohesion:

1. Participative leadership becomes impractical. You cannot consult thirty people individually, so you fall back on an "executive committee" or a few trusted lieutenants. Information asymmetry grows.
2. Sub-groups form. Cliques and factions emerge, compete for power and resources, and threaten teamwork. This is a structural inevitability, not a personality failing.

External Dependencies

The greater the lateral interdependence between your sub-project and others — or with external groups — the more your role tilts toward coordination, mutual adjustment, and political brokerage. A systems integration PM at a major prime spends far more time on liaison than a self-contained R&D team lead.

Crisis Situations

When normal operations break down, role expectations flip. Research by the supplied research and management research found that in crises, stakeholders prefer leaders who are:

• More directive
• More problem-solving oriented
• Less supportive in tone

PM rule of thumb: In steady state, lead by coaching. In crisis, lead by command. Knowing which mode the moment demands is itself a senior-PM skill.

Organisational Life Cycle

Organisations — and projects — pass through stages analogous to biological ones:

The demands, constraints, and discretion available to a leader shift markedly across these stages. A start-up project in its birth stage needs an entrepreneurial figurehead; a mature programme in decline needs a disciplined disturbance handler and negotiator.

The Pitfalls — Where New PMs Go Wrong

Pitfall 1 — The Rationalist Trap. Believing that decisions follow analysis. They don't. They follow politics, emotion, and timing. Build your influence map before your decision matrix.

Pitfall 2 — Over-Indexing on Planning. Treating the baseline plan as the job. The plan is the artefact of planning; the activity of planning is continuous and conversational.

Pitfall 3 — Confusing Important and Routine Decisions. Burning weeks of stakeholder consultation on a routine call, or rushing an important decision because the deadline feels urgent. Categorise first, then choose your process.

Pitfall 4 — Single-Mode Leadership. Leading the same way in steady state and crisis. The role taxonomy isn't a personality test — they're a toolkit. Use the right tool for the situation.

Pitfall 5 — Ignoring Sub-Group Dynamics. Assuming a large team is one team. Above roughly 12–15 people, factions form. Plan for it structurally with sub-team leads and clear interface ownership.

Pitfall 6 — Mistaking Visibility for Productivity. The fragmented, interrupted day is not a sign you're doing it wrong. It's the job. The trick is to protect some deep-work time without pretending you can protect all of it.

Defence & Heavy Engineering Context

In an acquisition authority-administered applicable contract framework programme, every one of ten managerial roles is amplified by formal contractual constraints:

• Figurehead — You sign the contractual correspondence; your name is on the gate-review minutes.
• Liaison — Multi-party governance (acquisition authority, prime, sub-tier suppliers, DASA, end-user service) makes liaison the dominant time consumer.
• Resource Allocator — Constrained by public-sector customer budgeting cycles and approved Statement of Work scope.
• Negotiator — Variations, contract change proposals, and equitable adjustments are negotiated under tightly defined commercial frameworks.
• Discretion — Bounded by DEF(AUST) standards, export-control authorised, security classification, and the applicable contract framework terms themselves.

The aspiring defence PM should read the supplied role taxonomy not as history but as a diagnostic tool: at the end of each week, audit which roles consumed your time, and ask whether the distribution matched the situation you were actually in.

Knowledge Check

1. Why does management research's logical incrementalism contradict the textbook image of strategic planning, and what does that imply for how you should treat your project's baseline plan?
2. A vendor critical to your defence sustainment programme has just declared insolvency. Which two of the role taxonomy should dominate your next 48 hours, and why?
3. Your team has grown from 8 to 25 people in six months. What structural changes should you anticipate in team dynamics, and what is the standard mitigation?
4. Distinguish an important from a routine decision using the five criteria in this article. Give a defence-context example of each.

Key Takeaways

• The classical functions — plan, organise, lead, control — are real but incomplete. Real managerial work is fragmented, reactive, verbal, and political.
• ten managerial roles across Interpersonal, Informational, and Decisional categories remain the most accurate descriptive model of what managers actually do.
• Decisions split sharply into important (political, prolonged, multi-stakeholder) and routine (technical, quick, authorised) — and the process you use must match the type.
• Planning is a continuous, agenda-driven, incremental activity, not a once-a-year cascade.
• Situational determinants — relationships, work pattern, exposure, discretion, unit size, dependencies, crisis, life-cycle stage — reshape what good leadership looks like.
• In crisis, expectations shift toward directive and problem-solving behaviour and away from supportive behaviour.
• For defence and heavy-engineering PMs, the role taxonomy map directly onto the lived experience of working under applicable contract framework, acquisition authority governance, and public-sector customer oversight.

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 "What" — Functional Manager vs Project Manager

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

The first conceptual shift is recognising that you are no longer a functional manager. The two roles share a title but operate on opposing logic.

Core principle: A functional manager owns people. A project manager borrows them. Influence — not authority — is the project leader's primary currency.

Worked Example — The complex naval-platform programme Welding Cell

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

The Welding Production Cell at major shipyard is a permanent functional unit. It exists before, during, and after any single ship. Its functional manager is measured on:

• Welder utilisation
• First-pass yield
• Consumable cost per metre of weld

The complex naval-platform programme is a finite project. Its programme manager is measured on:

• Earned Value: $$CPI = \frac{EV}{AC}$$ and $$SPI = \frac{EV}{PV}$$
• Hull-by-hull milestone delivery
• public-sector customer Gate Review pass/fail

When Hull 1 enters the welding cell, the programme manager does not take over the cell. Instead, a Resource Commitment is negotiated that says: "Cell 3 will be allocated to complex naval-platform programme Hull 1 from 14 April to 22 June, delivering panels P-001 through P-247 to drawing revision C." The functional manager remains accountable for how welding is done; the project manager is accountable for when and to which design.

The Scientific Management Inheritance

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

Before we caricature an early management theorist and the supplied research as relics, remember this: every time you watch a high-volume service operation kitchen run a lunch rush, you are watching scientific management in action. The "one best way" school still underwrites modern industrial engineering.

Scientific Management: The use of scientific methods to define the single most efficient way for a job to be done — through time-and-motion study, work analysis, incentive design, and rigorous selection.

Why this matters to a defence PM: when you build a Work Breakdown Structure (WBS) for a vehicle assembly line, when you set takt times on a production cell, when you design an incentive scheme for sustainment technicians — you are standing on the supplied research shoulders, whether you cite him or not.

Psychological Resilience

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

Practice note: Resilience A learned set of skills — mental toughness — and the ability to adapt and find your way around, over, or through adversity. It is not a fixed trait. It is a practice.

Resilient PMs:

• Have the inner confidence to face whatever the project throws at them
• Rein in their emotions to focus on improving the situation
• "Roll with the punches" while continuing to make forward progress

Non-resilient PMs:

• Hold defeatist or pessimistic attitudes
• Fall apart under stress
• Dwell on problems and feel victimised
• Become overwhelmed by setbacks that resilient peers absorb

Practice note: Why this is non-negotiable on heavy engineering projects On a complex naval-platform programme work package, a single subcontractor delay can cascade through six dependent activities. The PM who absorbs that hit, re-baselines, briefs the customer transparently, and re-energises the team is the PM who survives the programme. The PM who blames the subcontractor and complains to their line manager does not.

Current Issues Every Modern PM Faces

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

The context has shifted. Contemporary project managers must navigate issues that would have baffled a 1970s-era manager:

• Globalisation — operations no longer stop at borders. A defence programme PM in an Australian delivery site routinely coordinates with primes in the UK, subcontractors in Canada, and certifiers in the US under export-control authorised and multinational defence partnership frameworks.
• Ethics — post-2002–04 corporate scandals raised the bar. Modern PMs work under stronger compliance regimes and more scrutiny. Applicable contracts, an applicable configuration-management standard, and public-sector procurement rules codify much of this.
• Workforce diversity — gender, generational, cultural. The PM who cannot work across four generations in the same team will struggle.
• Entrepreneurship and innovation — even inside a traditional prime contractor, the pressure to pursue new opportunities is rising.
• Digital transformation — e-business, Industry 4.0, digital twins, AI-assisted engineering. The PM must be literate in tools and methods that did not exist five years ago.
• Learning organisations — continuous adaptation, knowledge management, lessons-learned discipline.
• Total Quality Management — continuous improvement as a cultural baseline, not a programme.
• Workplace spirituality — recognising that people want meaningful work, not just a pay cheque.

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.