CDT505 Chap.2 Strategy, Structure and Project Culture
Strategy, Structure and Project Culture
Read authority before assigning responsibility
Strategy explains why resources should be committed, structure distributes decision rights and culture influences how people use those rights under pressure. Functional structures protect specialist depth, project structures concentrate delivery authority and matrix structures share control at the cost of coordination.
The useful analysis maps authority over scope, budget, staffing and appraisal rather than relying on labels. Stakeholder management then turns interests and influence into a route for decisions, evidence and escalation.
Make governance specific to the conflict
When a project and a department claim the same specialist, communication alone cannot settle the trade.
The plan needs evidence about schedule effect, technical obligations and displaced work, then an authorised role that can decide. Culture shapes whether that evidence travels early or only after a milestone slips. A practical recommendation therefore pairs a decision right with a trigger and an escalation route.
It also names the cost accepted, because every structure exchanges some combination of speed, specialisation, resource efficiency and clarity.
What this chapter covers
- 01
Strategic alignment and project categories
- 02
Functional, matrix and project structures
- 03
Scope, budget, staffing and appraisal rights
- 04
Stakeholder power and implementation knowledge
- 05
Project management office mandates
- 06
Culture through incentives and escalation behaviour
Worked example · free
Resolve a matrix resource conflict
- 2Locate the two authority claims.
- 2Compare schedule and technical consequences.
- 2Use the authorised escalation route and record the decision.
Key terms
- Functional Structure
- An arrangement in which specialists and authority remain grouped by discipline.
- Matrix Structure
- An arrangement where project and functional authority are shared across the same work.
- Project Structure
- An arrangement that concentrates people and authority around a temporary project.
- Stakeholder
- A person or group that can affect, is affected by or perceives itself affected by the project.
- Project Management Office
- An organisational unit that may support, assure, coordinate or direct project management activities.
Strategy, Structure and Project Culture FAQ
How can a governance recommendation be tested?
Introduce a conflict between technical quality and a milestone, then write the decision required, evidence, consequence of delay and authorised decider. A usable structure must resolve that case without relying on vague collaboration. The test also reveals whether culture carries unwelcome evidence early enough for the formal authority to act.
Which organisational structure is best for projects?
No structure is universally best. Functional structures protect scarce expertise, project structures support rapid coordination, and matrix structures share capability across work. The choice depends on resource scarcity, uncertainty, strategic priority and whether decision rights can be made explicit.
What should a stakeholder analysis produce?
It should produce more than a power-interest label. For each important stakeholder, identify the decision they can make, evidence they require, their implementation knowledge, the communication route and the threshold for escalation. That converts a map into working governance.
How can culture be analysed without vague labels?
Use repeated behaviour and incentives. Examine whether bad news travels early, whether cross-unit work is rewarded, whether baselines are changed informally and whether meetings act on risk. These observations support a targeted control such as a trigger or approval rule.
Assessment move
Build a comparison sheet with functional, matrix and project structures as columns and scope authority, budget authority, staffing, appraisal, specialist quality, resource efficiency and coordination speed as rows. Do not write best or worst; describe the trade each arrangement creates. Add a short case in which two managers claim the same specialist.
For each structure, state who can decide, which evidence should be presented and where unresolved conflict escalates. This makes the structure operational rather than descriptive. Create a stakeholder register for the same case. Include decision power, implementation knowledge, interest, evidence needs, communication route and escalation threshold.
Pay special attention to a low-power stakeholder whose knowledge is necessary for delivery. Then examine culture through three observable behaviours: when bad news is reported, what happens to someone who reports it and whether a governance meeting acts on the evidence. Replace vague recommendations such as improve collaboration with a concrete decision rule, joint approval or reporting trigger.
Finish by taking a project management office and specifying whether it supports methods, assures compliance, coordinates portfolio information or directs projects. The title alone does not settle its mandate. Review by explaining the difference between responsibility and accountability without using either word in the definition.
Finally, answer both practice cards in a short chain: authority claim, evidence, authorised decision and accepted trade-off. If your recommendation could fit any organisation, add the specific resource scarcity, uncertainty or strategic priority that makes it appropriate here.
Working through Strategy, Structure and Project Culture in CDT505? Sia is AskSia’s AI Project Management tutor — ask any CDT505 Strategy, Structure and Project Culture question and get a clear, step-by-step explanation grounded in how CDT505 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
