Projects do not fail in an organisational vacuum; structure changes the authority, resources and decision speed available to delivery.
When a major initiative slips, attention quickly turns to the project manager, schedule, risk register or supplier. Sometimes that is appropriate. But some delivery problems are produced by the organisational environment long before a project manager has the authority to correct them.
The supplied PMI-based study notes treat organisational structure as an enterprise environmental factor. The accompanying table shows why: different structures change the project manager's authority, resource availability, budget control, administrative support and relationship with functional management. The supplied PwC material also associates organisational alignment with project-management performance, although the full bibliographic details of that 2004 survey are not present in the source set. [SOURCE DETAILS REQUIRED]
The strategic implication is straightforward: organisational structure is not merely an internal reporting design. It changes the conditions under which investment is converted into outcomes.
The Strategic Context
Projects are temporary organisations embedded inside permanent ones. They depend on functions that own people, systems, standards, technical knowledge and operational assets. The balance of power between the temporary project and the permanent organisation varies substantially.
In a functional organisation, specialists are grouped by discipline and functional managers retain significant authority. That can protect technical standards and professional depth, but project priorities may compete with functional priorities.
In a strong matrix, project managers generally have greater authority and access to resources, while functions still provide disciplinary capability. In a project-oriented structure, authority and resources may be concentrated around the project. Hybrid and virtual structures combine features and can be effective, but also create ambiguity if decision rights are not designed explicitly.
No structure is universally superior. The issue is fit between the work, the operating model and the risk being undertaken.
What Leaders Commonly Misread
The first misreading is to assume that assigning accountability creates authority. A project manager can be held responsible for schedule and cost while functional managers control the people and technical decisions required to achieve both.
The second is to solve every difficult initiative by giving the project more authority. Centralising power around a project can accelerate decisions, but it can also disconnect delivery from functional knowledge, operational ownership or enterprise standards.
The third is to treat matrix tension as a behavioural problem. Some conflict is structural. A functional manager is expected to protect capability and operational performance. A project manager is expected to deliver a temporary outcome. When the same engineer is critical to both, goodwill alone cannot resolve the competing accountabilities.
The fourth is to focus on the organisation chart rather than the decision system. Two firms can have similar charts but very different escalation paths, delegation levels, funding rules and cultures. Structure on paper is only one layer of structure in practice.
Reframing the Issue
Instead of asking, 'Which organisational structure should we use?', leaders should ask, 'What decision rights, resource flows and interfaces does this initiative require to succeed, and can the current organisation provide them?'
That question avoids a false search for the perfect model. It makes structure contingent on the work.
A complex product-development program may require strong cross-functional integration and fast trade-off decisions. A highly regulated infrastructure project may require clear technical authority and independent assurance. A small process-improvement project may work efficiently within a functional structure. A strategic transformation may need a temporary program structure with authority crossing several business units.
Strategic Analysis: Four Structural Failure Modes
Authority without resources
The project manager can decide what should happen but does not control the people or assets required to make it happen. Delivery becomes negotiation. Escalation replaces direct management.
Resources without integration
The project has access to specialists but no effective mechanism for resolving cross-functional trade-offs. Each function optimises its own component while system-level performance deteriorates.
Central control without local knowledge
Senior committees make detailed project decisions far from the technical reality. The Rio Tinto case in the supplied HBR material offers a useful counterpoint: Sam Walsh argued that people closer to projects should make more decisions, with the investment committee operating as a final safeguard rather than the sole decision-maker.
Temporary success without operational ownership
A project-oriented team delivers the output, but the permanent organisation has not accepted accountability for operating, maintaining or realising benefits. Delivery is declared complete while enterprise value remains uncertain.
Decision Framework
For every material project or program, define the structure through five design tests.
| Structural test | Question |
|---|---|
| Decision authority | Which decisions must the project/program make directly, and which remain functional or executive? |
| Resource authority | Who can commit and reprioritise scarce people and assets? |
| Technical authority | Who owns standards, design integrity and acceptance? |
| Financial authority | Who controls budget, contingency and changes to funding? |
| Benefit authority | Who owns the operational outcome after delivery? |
Then define escalation by decision type, not merely by monetary threshold. A low-cost design decision can create high safety or lifecycle consequences. A high-cost purchase can be routine if it sits within an approved investment envelope.
The right structure should also reflect uncertainty. Where the work is novel and interdependent, faster integrated decision-making may be more valuable. Where the work is repeatable and standards-driven, functional control may provide better efficiency and assurance.
Related article: Who Can Say Yes? How Financial Authority Shapes Project Outcomes
From Strategy to Execution
Immediately, map the top ten decisions that determine project success and identify who currently holds each decision right. Ambiguity will often become visible quickly.
In the medium term, create explicit agreements between project and functional leaders covering resource commitments, priorities, technical authority and escalation. These should be reviewed when portfolio priorities change rather than assumed fixed for the entire project.
For programs spanning multiple business units, establish benefit owners inside the permanent organisation before delivery is complete. A program director can coordinate transition, but lasting benefits require operational ownership.
Longer term, organisations should use recurring project friction as data about the operating model. If every major initiative struggles with the same approval bottleneck, resource conflict or interface, the problem may justify structural redesign rather than project-by-project escalation.
Signals to Monitor
Warning signs include project managers accountable for outcomes but unable to commit resources; frequent escalation of routine decisions; specialists receiving contradictory priorities from project and functional managers; executive committees making detailed technical choices; late operational involvement; and repeated delays caused by unclear approval authority.
A subtler signal is a project that appears to succeed only because one senior sponsor personally resolves every conflict. That may deliver the immediate outcome, but it indicates an organisational system that does not scale.
Questions for the Leadership Team
- Does each major project have authority proportionate to the outcome for which it is accountable?
- Which decisions are repeatedly escalated because ownership is structurally unclear?
- Where do functional and project incentives legitimately conflict?
- Which technical decisions should remain independent of schedule and budget pressure?
- Who owns benefits after the temporary project organisation dissolves?
- What recurring project problem is actually evidence of an operating-model problem?
Closing Perspective
Organisational structure is often treated as context that project teams must simply work around. That is too passive for material investments.
Structure allocates authority, resources and information. Those allocations influence decision speed, technical quality and accountability. Leaders who ignore structure during investment design are accepting project risk without explicitly pricing or governing it. The task is not to choose a fashionable structure; it is to create the conditions the work actually requires.
Source Foundations
- Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 6th ed., 2017, as cited in the supplied study material.
- PricewaterhouseCoopers, 2004 organisational/project-management survey excerpt reproduced in supplied course material. [SOURCE DETAILS REQUIRED]