A project leader cannot be held rationally accountable for outcomes while the organisation withholds the authority, resources and decision pathways needed to produce them.
Many project reviews focus on schedule discipline, reporting quality, risk registers and the competence of the project manager. Those things matter. But they can distract from a more fundamental question: what operating conditions has the organisation created around the project?
The supplied PMBOK® Sixth Edition material and associated study notes treat organisational structure as an enterprise environmental factor. The accompanying table shows why this matters. Across functional, weak matrix, balanced matrix, strong matrix, project-oriented, virtual, hybrid and PMO arrangements, the project manager's authority, resource access, budget control, staffing and administrative support vary materially.
That means organisational structure is not merely a reporting-line decision. It changes the conditions under which projects are expected to perform.
The Strategic Context
Projects rarely operate as self-contained entities. They sit inside organisations with pre-existing functions, incentives, budgets, systems and power structures.
A functional organisation may concentrate authority in engineering, finance, operations or other departments. A strong matrix may give a project manager materially greater control over resources and decisions. A project-oriented model may place most delivery authority inside the project itself. A hybrid model may mix several of these arrangements.
None of these structures is automatically superior.
The strategic question is whether the structure matches the type of work the organisation is asking the project to perform.
A repetitive internal upgrade may not require extensive project authority. A multi-year transformation crossing technology, operations, procurement, people and customer processes may require stronger integration mechanisms. A major capital project may require functional expertise to remain deeply embedded while also needing clear project authority over schedule, interfaces and trade-offs.
The structure therefore affects more than efficiency. It affects how quickly conflicts are resolved, how scarce resources are allocated, who can commit funds, who decides between functional and project priorities, and whether accountability is matched by control.
The supplied historical PwC material makes the same broader point: some causes of poor project results are organisational rather than directly within the project manager's control, and project performance is influenced by how well organisational structure aligns with business needs.
What Leaders Commonly Misread
The first misreading is to equate formal accountability with actual authority.
A project manager may be named as accountable for delivery while still needing approval from functional managers for people, finance for expenditure, procurement for suppliers, operations for access, and executives for scope trade-offs. In such a system, the project manager coordinates but does not truly control many of the variables that determine outcomes.
That is not necessarily wrong. Many organisations need functional control for good reasons. The problem arises when leaders ignore the gap between expected accountability and available authority.
The second misreading is to assume that stronger project authority always improves delivery.
It can create other costs. Functions may lose consistency, technical standards can fragment, duplicated specialist capability can emerge, and people may become detached from their professional disciplines.
The third misreading is to treat the organisation chart as the complete description of how work gets done.
Informal influence, escalation pathways, budgeting authority, committee practices, shared systems and cultural norms can override the formal structure.
The fourth misreading is to blame individuals for behaviour that the structure itself encourages.
If a functional manager is rewarded for local utilisation while the project needs scarce specialists released at short notice, conflict is predictable. If the project manager is measured on schedule but cannot prioritise the resources needed to protect it, delay is structurally likely.
Reframing the Issue
Organisational structure should be treated as a project delivery design decision.
The useful question is not:
Which organisational structure do we have?
It is:
Does our structure provide the right balance of functional integrity, project authority and enterprise control for this initiative?
That reframing changes the leadership conversation.
A project with weak authority may need stronger escalation rights, dedicated resources or clearer delegation.
A project-oriented environment may need stronger technical assurance and functional standards.
A hybrid organisation may need explicit interface rules because ambiguity is the price it pays for flexibility.
The structure should therefore be designed around the work, not defended because it is already familiar.
Authority, Resources and the Real Delivery System
The supplied organisational-structure table highlights several variables that executives should examine together.
Project-manager authority
Authority shapes the ability to make trade-offs without waiting for repeated escalation.
Low authority may be appropriate where the project is narrow and functionally contained. It becomes problematic where speed and cross-functional integration are critical.
Resource availability
A project can have an approved budget and still fail because the people it needs are not actually available.
This is especially common when specialists are shared across many initiatives.
Budget control
Who manages the project budget matters because budget ownership influences decision speed and trade-off authority.
A project manager accountable for cost but unable to approve expenditure is operating under a different governance model from one who directly controls the budget.
Project-management role
Part-time project coordination may be sufficient for low-complexity work. It becomes fragile when the project requires continuous integration across contractors, functions, regulatory issues and operational change.
Administrative support
Governance often fails through administrative overload. Scheduling, reporting, change control, documentation and financial tracking require capacity. If these functions are absent, project leaders spend time operating the system rather than directing the work.
The Cost of Structural Misalignment
Structural misalignment creates predictable patterns.
A functional structure can create delayed cross-functional decisions because each function optimises its own priorities.
A weak matrix can produce accountability without enough control.
A projectised structure can create speed but risk duplication and disconnection from enterprise standards.
A hybrid can provide flexibility while creating uncertainty about who has final authority.
The problem is therefore not the label attached to the structure. It is the mismatch between the structure and the demands of the work.
A project that depends on rapid trade-offs, scarce resources and tight integration will struggle in a structure where every decision must travel through multiple functional chains.
Conversely, a technically specialised project may be weakened if project autonomy strips away the functional oversight needed to protect quality and safety.
The structure must fit the decision architecture of the work.
Related article: Program Governance Begins With Decision Rights, Not Committees
Decision Framework
Before launching or materially restructuring a major project, leaders should test six dimensions.
| Dimension | Leadership question |
|---|---|
| Authority | Which decisions can the project manager make without escalation? |
| Resources | Are critical resources committed or merely assumed to be available? |
| Budget | Who controls expenditure and who carries financial accountability? |
| Functional integrity | Which standards and technical decisions must remain with functional owners? |
| Escalation | How quickly can cross-functional conflict be resolved? |
| Support | Does the project have sufficient planning, controls and administrative capacity? |
Three further tests improve the design.
Match authority to consequence. High-consequence decisions may require enterprise control even when speed is important.
Match integration to complexity. The more cross-functional the initiative, the stronger the need for clear integration authority.
Match accountability to control. Do not make one role accountable for variables it cannot reasonably influence.
From Strategy to Execution
Immediate action
Map the actual decision rights of each major project.
Do not rely on the organisation chart. Identify who controls people, budget, scope, technical standards, procurement, risk acceptance and change.
Where accountability and authority are materially misaligned, correct the mismatch or make the constraint explicit.
Medium-term capability building
Create standard governance patterns for different classes of work.
A small internal improvement project should not need the same governance as a major transformation. Equally, a strategic program should not inherit the weak authority designed for routine departmental work.
Develop escalation service levels so projects know how long major decisions should take and who resolves deadlock.
Long-term strategic positioning
Treat organisational design as part of portfolio design.
If the enterprise repeatedly chooses projects that depend on cross-functional integration, it may need to evolve its structure, PMO role, resource model or delegation framework rather than solving the same coordination problem project by project.
Signals to Monitor
Structural problems are likely when:
- project managers are repeatedly blamed for delays caused by resource unavailability;
- functional managers can override project priorities without transparent portfolio trade-offs;
- budget ownership and delivery accountability sit in different parts of the organisation with no clear mechanism between them;
- critical decisions require repeated executive intervention;
- part-time project leadership persists despite rising complexity;
- projects create duplicate specialist teams because enterprise functions cannot respond quickly enough;
- or governance committees accumulate because basic decision rights remain unclear.
These signals indicate that project performance is being treated as an individual issue when the underlying cause may be organisational design.
Questions for the Leadership Team
- Which outcomes do we hold project leaders accountable for that they do not actually control?
- Where do functional priorities routinely override strategic project priorities?
- Which decisions take too long because authority is structurally ambiguous?
- Are scarce resources genuinely allocated to projects or merely promised to them?
- Which projects require a different governance structure from our standard model?
- If our current structure is appropriate, what evidence shows that it supports the kind of work our strategy now requires?
Closing Perspective
Organisational structure is often treated as context around project management.
It is more consequential than that.
Structure determines where authority resides, how resources move, who controls budgets, how conflicts are resolved and whether accountability is credible.
A capable project leader can compensate for some structural friction. No project leader can permanently overcome a system that withholds the conditions required for delivery.
The executive responsibility is therefore not simply to appoint good project managers. It is to build an organisational system in which good project management can actually work.