3.1 Functional, Matrix and Projectised Structures
Key Takeaways
- Governance is the framework of authority and accountability for delivering a project so that it aligns with organisational practice and decision rights.
- Permanent structures own people, budgets, and corporate rules; temporary project structures exist only while the project needs coordinated cross-unit effort.
- In a functional structure the project manager has low formal authority and negotiates for time against business-as-usual priorities.
- In a matrix structure staff report to both a functional manager and a project, so dual reporting makes clear roles, RACI, and escalation essential.
- In a projectised structure the project manager usually controls team and budget, but staff reassignment and corporate standards need deliberate attention.
What Governance Means on the APM PMQ
The APM PMQ syllabus defines governance arrangements as the framework of authority and accountability for delivering a project in a way that aligns with organisational practice. Governance is not the same as day-to-day project management. The project manager plans, directs, and controls delivery work; governance decides who is allowed to decide what, how investment is released, which standards must be followed, and when the organisation should continue, change, or stop the project.
On long-response questions, weak answers list controls without purpose. Strong answers link structure → decision rights → control of benefits, risk, and spend. Always ask: who is accountable, who has authority, and how does this project fit the host organisation’s way of working?
Permanent vs Temporary Organisation Structures
Most organisations are permanent: they exist to run ongoing operations (business-as-usual). Projects are usually temporary: they have a start, an end, and unique outputs. Governance must bridge both worlds.
| Dimension | Permanent organisation | Temporary project structure |
|---|---|---|
| Purpose | Sustain products, services, and operations | Deliver a defined change or unique output |
| Duration | Ongoing | Finite (closed when objectives are met or work stops) |
| Authority base | Line management, functional heads, corporate policies | Sponsor, steering group/board, delegated project roles |
| Resource model | Staff sit in departments with stable reporting lines | People are assigned (full-time or part-time) for the project’s life |
| Success measure | Operational performance, service levels, BAU KPIs | Project objectives, benefits case, agreed tolerances |
The permanent structure owns people, budgets, and corporate rules. The temporary structure exists only while the project needs coordinated effort across those permanent units. When the project closes, temporary roles dissolve and outputs, risks, and benefits ownership transfer into business-as-usual.
Exam trap: Treating the project team as a permanent department. On the PMQ, projects remain temporary even when they last years; governance still plans for closure, handover, and dissolution of the temporary structure.
Functional, Matrix, and Projectised Structures
The syllabus expects knowledge of three classic permanent (or semi-permanent) structural types and their features. In practice many organisations are hybrids, but exam scenarios usually map cleanly to one dominant form.
| Structure | How work is organised | Project manager authority | Typical strengths | Typical tensions for the PM |
|---|---|---|---|---|
| Functional | People and budgets sit in specialist departments (engineering, finance, operations) | Low — PM often coordinates across functions with limited formal power | Deep specialist expertise; clear career paths; efficient for routine BAU | Resource priority fights with BAU; slow cross-functional decisions; PM may lack budget/people authority |
| Matrix | Staff report to functional managers and contribute to projects | Medium — shared authority with functional heads | Flexible use of scarce skills; visibility of project vs BAU demand | Dual reporting, role ambiguity, contested priorities; needs strong RACI and escalation paths |
| Project (projectised) | People and resources are organised primarily around projects | High — PM usually controls team and budget for the project | Clear focus, fast decisions, strong team identity | Specialist silos may weaken after project ends; under-use of corporate standards if not enforced |
Functional structures
In a functional organisation, departments own their people. A project may be run within one function (for example, an IT upgrade led by the IT director) or coordinated across several functions by a project manager who has little formal power. Governance often flows through existing line management. Stage decisions may sit with a departmental head rather than a dedicated project board unless the investment is large enough to justify one.
Advantage for the organisation: specialist quality and efficient utilisation of experts when project demand is occasional.
Tension for the PM: negotiating time from busy line managers, resolving conflicts when BAU work trumps project tasks, and escalating when no single senior owner has enterprise-level accountability.
Matrix structures
Matrix structures are common for organisations that run many projects alongside operations. People keep a functional home (for career, competence, and often appraisal) while allocating a percentage of time to projects. Matrix forms range from weak (functional managers dominate) through balanced to strong (project managers hold more power over priorities and performance input).
Advantage: scarce specialists can serve multiple initiatives without permanent reorganisation.
Tension: dual reporting creates ambiguity. Without clear governance, team members receive conflicting instructions from a functional head and a project manager. The PMQ expects you to recognise that governance — role definitions, RACI, escalation routes, and priority rules set by senior management — is what makes a matrix workable.
Projectised structures
In a projectised (project-based) organisation, the primary unit of work is the project. Teams form around initiatives; the project manager typically has direct authority over people and budget for that work. Consulting firms, construction delivery units, and product delivery organisations often lean this way.
Advantage: speed, focus, and clear day-to-day authority for the PM.
Tension: when the project ends, staff need reassignment; corporate governance must still ensure standards, assurance, and strategic alignment so individual projects do not optimise locally while harming the portfolio.
Scenario: same project, three structures
A hospital is implementing a new electronic patient-record system.
- Functional: IT leads technical work; clinical departments second staff ad hoc. The PM spends most of their time securing clinician time and may lack power to stop clinical BAU from delaying testing.
- Matrix: clinicians are allocated 40% to the programme; functional heads and the programme board jointly set priorities. Conflicts go to a steering group that owns both clinical safety and investment.
- Projectised: a dedicated delivery team is seconded full-time under a programme director with budget control. Decisions are faster, but the organisation must plan how clinical specialists return to wards after go-live.
In each case the technical work may be similar; the governance challenge (authority, escalation, resource priority) differs.
In a matrix organisation, why is clear project governance especially important for the project manager?
A specialist engineering firm runs occasional internal improvement projects. Staff sit permanently in discipline departments, budgets are held by department heads, and project managers coordinate across those departments without formal authority over people. Which structure is described, and what is the project manager’s main governance challenge?