How Organisational Planning & Structure Shape Every Project
From Boardroom to Building Site
Why This Matters: Projects Don't Exist in a Vacuum
Here's a question that separates competent project managers from exceptional ones: Where does your project actually come from?
Most PMs can rattle off scope, schedule, and budget. Far fewer can trace a clean line from their project's deliverables back to the boardroom strategy that justified its existence. Yet this connection — between corporate intent and project execution — is the invisible architecture that determines whether a project is a strategic asset or an expensive distraction.
Understanding organisational planning isn't an academic exercise. It's the difference between managing a project that has executive air cover, clear funding rationale, and aligned stakeholders — and one that's quietly orphaned mid-flight because nobody can explain why it exists.
Core Principle: To be considered successful, all projects must ultimately serve one or more of the organisation's strategic objectives. A project without strategic alignment is a project without a future.
What Is an Organisation (in Project Management Terms)?
In a business context, an organisation is a unit of people structured to meet collective goals on a continued basis. The management structure — the hierarchy of roles, responsibilities, delegation, and control — forms the skeleton on which all project work hangs.
Every organisation operates within a decision-making hierarchy:
- Strategic decisions are made by the board and/or executive leadership
- Business unit strategies are developed by divisions to achieve corporate goals
- Programs are assembled by business units to deliver groups of related outcomes
- Projects contribute individual deliverables as components of programs
- Operations sustain the ongoing, repetitive activities of the total organisation
The critical distinction: operations are ongoing and repetitive; projects are temporary and unique. Projects exist precisely because strategic objectives often demand change that normal operations cannot deliver.
The Strategic Planning Hierarchy: Five Levels of Alignment
Planning and goal setting must occur at every level of the organisation. The following five-level model illustrates how strategic intent cascades downward — and how project management connects at every tier.
Level 1 — Corporate Management
- Horizon: 5–10 years aligned with vision and mission
- Scope: Development of strategic business directions, organisational goals, and objectives
- Project connection: Oversight of major programs
Three foundational elements anchor this level:
| Element | Purpose |
|---|---|
| Mission | The organisation's reason for being. Asks: "What business are we in?" |
| Vision | Defines the desired future state. Asks: "Where do we want to be in X years?" |
| Strategic Plan | Identifies how the organisation will achieve the vision given the objectives defined in the mission |
Level 2 — Divisional Management
- Horizon: 3–5 years aligned with Strategic Plan objectives
- Scope: Goals, strategies, and actions with significant budget and resource allocation
- Project connection: Major programs with multiple start and end dates
Level 3 — Departmental Planning
- Horizon: 1–3 years aligned with financial cycles
- Scope: Goals, actions, broad resource and time constraints
- Project connection: Complex projects with moderate impact; minor programs
Level 4 — Team Management
- Horizon: 12-month plans aligned to financial year
- Scope: Tasks and actions with identified resource and time constraints
- Project connection: Mini-projects with defined start and end dates
Level 5 — Individual Planning (Self-Management)
- Scope: Tasks and short-term personal goals
- Project connection: Engaged in ongoing processes; contributing to team project deliverables
Strategic Management Terminology: The Language of Alignment
Before you can connect projects to strategy, you need to speak the language fluently. These terms form a cascade — each one more specific than the last:
| Term | Definition |
|---|---|
| Mission | Overriding premise in line with stakeholder values — the organisation's purpose, scope, and boundaries |
| Vision | Defines the field of endeavour; answers "Where do we want to be?" |
| Goal(s) | General statements of aim or purpose in line with the mission; may be qualitative |
| Objective(s) | Quantified (where possible) or more precise statements of the goal |
| Strategies | Broad statements of intent showing the types of action required to achieve objectives |
| Actions/Tasks | Individual steps to implement strategies — linking broad direction to specific operational issues and individuals |
The Golden Rule of Alignment: Every project objective should trace upward through this cascade to at least one strategic objective. If it can't, challenge why the project exists.
Worked Example: Five-Level Strategic Plan in Action
Consider a commercial property developer and how strategy cascades to individual project delivery:
Notice the clean traceability: the individual PM's performance target (deliver early, under budget) directly serves the program profit margin, which feeds the business growth goal, which achieves the corporate strategy. This is strategic alignment in practice.
Organisational Structures: The Framework That Shapes Project Authority
The hierarchy and reporting structure in every organisation forms a framework — the organisational structure — that determines how roles and responsibilities are delegated and managed, and how information flows between levels of management.
Most organisations fall into one of three structural archetypes, each with profoundly different implications for project managers:
1. Functional (Traditional) Structure
The traditional organisation has been the dominant form for over a century. People with similar skills are grouped together under a similarly skilled manager. Employees become specialists — deeply proficient in their function.
How projects work here: Project work cuts across functional silos. Staff are "borrowed" from departments, and the functional manager retains authority. The project manager — if one is formally appointed at all — has minimal direct authority.
| Advantage | Disadvantage |
|---|---|
| Deep technical expertise within functions | Projects compete with functional priorities |
| Clear career paths for specialists | Slow cross-functional communication |
| Efficient resource utilisation within departments | PM has little to no formal authority |
| Stable, predictable structure | Resistance to change and innovation |
Best suited for: Organisations with routine operations and few or small projects. Examples include traditional automotive manufacturing and public sector agencies.
2. Matrix Structure
Emerging in the 1970s, the matrix was an attempt to combine the best of both projectised and functional worlds. All employees still report to a functional manager (organised by skill), but project managers direct the project work performed by those employees.
The functional manager handles staffing and administration. The project manager handles the work itself. This allows project teams to focus on stakeholders and deliverables without being bogged down in HR administration.
The Matrix Balancing Act: The critical challenge is maintaining equilibrium between project managers and functional managers. If one group dominates, you get either a disguised functional structure or a disguised projectised one — losing the benefits of both.
| Matrix Variant | PM Authority | Functional Manager Authority |
|---|---|---|
| Weak Matrix | Low — PM acts as coordinator | High — FM controls resources |
| Balanced Matrix | Moderate — shared authority | Moderate — shared authority |
| Strong Matrix | High — PM controls budget & assignments | Low — FM provides expertise only |
Best suited for: Organisations running multiple concurrent projects that require diverse specialist skills. Common in consulting, IT, and medium-to-large engineering firms.
3. Projectised Structure
The oldest and most direct approach: the project manager has total authority. All questions regarding the project are directed to the PM as the ultimate decision-maker. Team focus is clear, project goals are visible, and client communication is direct.
Think of it as the structure that built the pyramids — and it still works today for organisations where projects are the business.
| Advantage | Disadvantage |
|---|---|
| Clear authority and accountability for PM | Duplication of resources across projects |
| Strong team identity and loyalty | Specialists may lack a "home" between projects |
| Fast decision-making | Knowledge silos between project teams |
| Direct client relationship | Less efficient resource utilisation overall |
Best suited for: Organisations where the primary business is project delivery. Examples include defence contractors, major construction firms, and large consultancies.
Comparative Summary: Choosing the Right Structure
| Factor | Functional | Matrix | Projectised |
|---|---|---|---|
| PM Authority | Little to none | Low to high (depends on variant) | Full |
| Resource Availability | Low for projects | Low to high | High |
| Budget Control | Functional manager | Shared | Project manager |
| PM Role | Part-time / coordinator | Part-time to full-time | Full-time |
| Admin Staff | Functional departments | Shared | Dedicated to project |
| Best For | Routine operations, few projects | Multiple concurrent projects | Project-driven organisations |
The Pitfalls: Where Organisations Get This Wrong
1. Strategic Orphans: Launching projects that cannot be traced to any strategic objective. These consume resources without delivering organisational value and are typically the first casualties during budget cuts.
2. Structure Mismatch: Attempting to run large, complex projects inside a rigid functional structure. The PM has no authority, resources are constantly pulled back to "real work," and the project dies by a thousand cuts.
3. Matrix Without Rules: Implementing a matrix structure without clearly defining the boundary between project manager and functional manager authority. The result is confusion, conflict, and finger-pointing when things go wrong.
4. Ignoring the Strategy Cascade: Project managers who focus exclusively on scope-schedule-cost without understanding the business case and strategic rationale behind their project. When priorities shift, these PMs are blindsided.
5. Assuming One Size Fits All: Different projects within the same organisation may require different structural approaches. A small internal process improvement doesn't need a projectised structure; a $50M capital program probably does.
Key Takeaways
- All projects serve strategy — directly or indirectly. A project without strategic alignment is a project at risk.
- The five-level planning hierarchy (Corporate → Divisional → Departmental → Team → Individual) creates the cascade through which strategy becomes action.
- Three organisational structures dominate: Functional, Matrix, and Projectised. Each trades off PM authority against resource efficiency.
- The matrix structure is the most common but also the most fragile — it requires deliberate balance between functional and project authority.
- Structure shapes authority. Before accepting a project, understand where you sit in the org structure and what power you actually have.
