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 — Vision / Mission / Strategic Plan — 5–10 year horizon

Level 2: Divisional Management — Business Plans — 3–5 year horizon

Level 3: Senior Management — Departmental Plans — 1–3 year horizon

Level 4: Team Management — Team Plans — 12-month horizon

Level 5: Individual — Ongoing Processes — Tasks & personal goals

Relationship details

From	Relationship	To
Level 1: Corporate Management — Vision / Mission / Strategic Plan — 5–10 year horizon	leads to	Level 2: Divisional Management — Business Plans — 3–5 year horizon
Level 2: Divisional Management — Business Plans — 3–5 year horizon	leads to	Level 3: Senior Management — Departmental Plans — 1–3 year horizon
Level 3: Senior Management — Departmental Plans — 1–3 year horizon	leads to	Level 4: Team Management — Team Plans — 12-month horizon
Level 4: Team Management — Team Plans — 12-month horizon	leads to	Level 5: Individual — Ongoing Processes — Tasks & personal goals

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:

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:

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:

Corporate Goal — Grow the business by 5% — over the next 5 years

Business Goal — Complete 10 major developments — over 5 years at 7.5% avg. profit

Program Goal — Design, develop & sell a mixed development — (park, community centre, light industrial) — at 10% profit margin

Project A — Park: $90k / 6 months

Project B — Community Centre: $1.2M / 18 months

Project C — Light Industrial: $3.4M / 24 months

Individual Goal — PM1: Value manage Project A — to achieve $10k savings & — deliver 1 month early

Relationship details

From	Relationship	To
Corporate Goal — Grow the business by 5% — over the next 5 years	leads to	Business Goal — Complete 10 major developments — over 5 years at 7.5% avg. profit
Business Goal — Complete 10 major developments — over 5 years at 7.5% avg. profit	leads to	Program Goal — Design, develop & sell a mixed development — (park, community centre, light industrial) — at 10% profit margin
Program Goal — Design, develop & sell a mixed development — (park, community centre, light industrial) — at 10% profit margin	leads to	Project A — Park: $90k / 6 months
Program Goal — Design, develop & sell a mixed development — (park, community centre, light industrial) — at 10% profit margin	leads to	Project B — Community Centre: $1.2M / 18 months
Program Goal — Design, develop & sell a mixed development — (park, community centre, light industrial) — at 10% profit margin	leads to	Project C — Light Industrial: $3.4M / 24 months
Project A — Park: $90k / 6 months	leads to	Individual Goal — PM1: Value manage Project A — to achieve $10k savings & — deliver 1 month early

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

Executive Management

Finance

Engineering

Operations

Other Divisions

Staff

Staff

Staff

Staff

Staff

Staff

Staff

Staff

Relationship details

From	Relationship	To
Executive Management	leads to	Finance
Executive Management	leads to	Engineering
Executive Management	leads to	Operations
Executive Management	leads to	Other Divisions
Finance	leads to	Staff
Staff	leads to	Staff
Engineering	leads to	Staff
Operations	leads to	Staff
Other Divisions	leads to	Staff

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.

Best suited for: Organisations with routine operations and few or small projects. Examples include traditional automotive manufacturing and public sector agencies.

Engineering

Procurement

Finance

Operations

Cross‑Functional Project

X

X

X

X

Relationship details

From	Relationship	To
Engineering	leads to	Procurement
Procurement	leads to	Finance
Finance	leads to	Operations
Cross‑Functional Project	leads to	Engineering
Cross‑Functional Project	leads to	Procurement
Cross‑Functional Project	leads to	Finance
Cross‑Functional Project	leads to	Operations
Engineering	leads to	X
Procurement	leads to	X
Finance	leads to	X
Operations	leads to	X
X	leads to	X

---

2. Matrix Structure

Chief Executive

Project Director

Technical Director

Operations Director

Other Directors

PM X → 6.5 staff

PM Y → 6.0 staff

PM Z → 3.0 staff

Relationship details

From	Relationship	To
Chief Executive	leads to	Project Director
Chief Executive	leads to	Operations Director
Chief Executive	leads to	Other Directors
Project Director	leads to	PM X → 6.5 staff
Project Director	leads to	PM Y → 6.0 staff
Project Director	leads to	PM Z → 3.0 staff

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.

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

Chief Executive

Project Manager A

Project Manager B

Project Manager C

Staff

Staff

Staff

Staff

Staff

Staff

Staff

Staff

Staff

Relationship details

From	Relationship	To
Chief Executive	leads to	Project Manager A
Chief Executive	leads to	Project Manager B
Chief Executive	leads to	Project Manager C
Project Manager A	leads to	Staff
Staff	leads to	Staff
Project Manager B	leads to	Staff
Project Manager C	leads to	Staff

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.

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

---

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.