Chapter Three – Organization Structure & Culture

Learning Objectives

• 03-01 Identify project‐management structures; explain relative strengths & weaknesses.
• 03-02 Distinguish weak, balanced, strong matrix forms; appraise pros & cons.
• 03-03 Explain how Project Management Offices (PMOs) support & improve execution.
• 03-04 List organizational / project considerations used in choosing a structure.
• 03-05 Recognize the pivotal role of organizational culture in managing projects.
• 03-06 Diagnose an organization’s culture from observable artefacts & stories.
• 03-07 Clarify how structure and culture interact during project execution.

Chapter Outline (Road-Map)

• 3.1 Project Management Structures
• 3.2 Project Management Office (PMO)
• 3.3 Selecting the Right Structure
• 3.4 Organizational Culture
• 3.5 Culture–Structure Implications for Projects

3.1 Project Management Structures

Three generic ways to embed projects inside firms (each scalable to programs/portfolios):

Functional Organization (Pure Functional)

• Top management authorises project; work is parceled out to existing functional units.
• Coordination flows through normal hierarchy (no separate project line).
• Common when one function is clearly dominant (e.g., IT upgrade run by IT department).

Advantages

1. No structural upheaval — firm keeps familiar hierarchy.

2. High flexibility in staff sharing & depth of functional expertise.

3. Technical continuity and career paths remain intact.

4. Smooth post-project transition (people never left home base).

Disadvantages

1. Lack of project focus; employees juggle functional and project work.

2. Poor cross-functional integration (silos).

3. Slow response and decision cycles (vertical escalation).

4. Diffused responsibility — “ownership” unclear.

Dedicated Project Teams (Projectized / Tiger Teams)

• Projects run as self-contained mini-organizations outside the functional ladder.
• Full-time project manager recruits a core, cross-functional team (internal + external).
• In a projectized organization the entire company is a constellation of such teams.

Strengths

1. Structural simplicity; single authority = fast decisions.

2. Speed — minimal coordination latency.

3. High team cohesion, clear identity.

4. Strong cross-functional integration; innovation thrives.

Weaknesses

1. Expensive (duplicate resources, specialists sequestered).

2. “Projectitis”: we-they separation from parent organization; potential internal strife.

3. Limited access to broader technological depth (specialists locked in other projects).

4. Difficult post-project transition — where do people go afterwards?

Matrix Organization (Hybrid)

• Superimposes a horizontal project dimension on vertical functional dimension ⇒ dual authority.
• Employees (and sometimes PM) report to both a functional manager (FM) and a project manager (PM).
• Goal: optimise scarce resources, foster integration, yet preserve technical excellence.

Typical Role Split (see Table 3-1)

Project Manager — WHAT, WHEN, , overall quality.
Functional Manager — HOW, WHICH people/tech, effect on functional commitments.
Negotiated — WHO exactly, WHERE performed, WHY rationale, acceptance criteria.

Three Matrix Intensities

1. Weak Matrix
   • Close to functional; PM acts as coordinator/staff assistant (draws schedules, collects status).
   • FM retains power over people & technical decisions.

2. Balanced Matrix
   • PM defines scope, master plan, schedule, integrates disciplines, monitors progress.
   • FM decides methods, assigns personnel, ensures standards.
   • Power roughly equal.

3. Strong Matrix
   • PM controls scope, trade-offs, and most resource assignments; FM consulted as “sub-contractor.”
   • PM has final say on major decisions; functional title remains for administrative home.

Advantages

1. Resource efficiency (people can work part-time on several projects).

2. Strong project focus compared with pure functional.

3. Easier post-project transition — people never left functions.

4. Flexible; can scale up/down without major reorg.

Disadvantages

1. Possibility of dysfunctional conflict (two bosses, mixed priorities).

2. Power struggles & hidden agendas (infighting).

3. Stressful for personnel forced to juggle competing demands.

4. Potentially slower than dedicated teams (consensus building).

3.2 Project Management Office (PMO)

Centralised entity that standardises governance, processes & talent for projects; maturity accelerator, especially in matrix settings.

PMO Archetypes (in ascending order of control):
• Weather Station — monitors, tracks, reports (no authority).
• Control Tower — defines methodologies, provides training & auditing, intervenes to improve execution.
• Resource Pool — houses trained PMs, dispatches them to BUs; builds career ladder.
• Command & Control Centre — owns the projects, allocates budgets & personnel; operates like an internal contractor.

3.3 Selecting the Right Structure

Decision lens must span BOTH organizational and project variables.

Organizational Factors
• Importance of PM competence to firm success.
• % of core work that is project based.
• Resource availability & elasticity.

Project Factors
• Size & complexity.
• Strategic importance.
• Novelty/innovation requirement.
• Degree of integration (number of functions involved).
• Environmental complexity (external interfaces).
• Budget & schedule tightness.
• Stability/volatility of resource needs.

Rule-of-thumb continuum:
\text{Functional} \rightarrow \text{Weak Matrix} \rightarrow \text{Balanced} \rightarrow \text{Strong} \rightarrow \text{Dedicated}$$
Move rightward as projects become larger, more strategic, novel, integrated, time-critical, and resource-volatile.

3.4 Organizational Culture

• Defined as a system of shared norms, values, beliefs, & assumptions binding people and giving meaning — the company’s "personality."
• Functions: identity, legitimacy, behavioural norms, social order.

10 Key Cultural Dimensions (Figure 3-5)

1. Member identity — role vs organization.

2. Team emphasis — individual vs group.

3. Management focus — task vs people.

4. Unit integration — independent vs interdependent.

5. Control — loose vs tight.

6. Risk tolerance — low vs high.

7. Reward criteria — performance vs other (e.g., seniority).

8. Conflict tolerance — low vs high.

9. Means-ends orientation — means vs ends.

10. Open-system focus — internal vs external.

Diagnosing Culture

1. Physical artefacts — architecture, office layout, dress code.

2. Public documents — annual reports, vision statements.

3. Behavioural observations — pace, language, meetings, rituals.

4. Folklore — stories of heroes, villains, critical incidents.

(Example in Figure 3-6: Power Corp. where power increases by floor height; young PM fired for escalation; ritual boat cruise for top units.)

3.5 Culture–Structure Implications for Projects

• PM must navigate multiple cultures: parent org, functional subcultures, client org, suppliers, regulators, community groups.
• Metaphor: project = boat, culture = river. Understanding the river’s currents, depth, & hazards lets the boat reach destination faster and safer.
• Ideal project-supportive culture (Figure 3-7) leans toward:
– Organization member identity over narrow job identity.
– Group/team emphasis.
– People focus (balanced with task).
– Interdependent units.
– Loose but adequate control (empowerment).
– High risk tolerance & conflict tolerance.
– Ends orientation & external focus.
– Performance-based rewards.

Key Terms Recap

• Balanced matrix
• Dedicated project team
• Matrix
• Organizational culture
• Projectitis
• Projectized organization
• Project Management Office (PMO)
• Strong matrix
• Weak matrix

Quick Reference: Comparative Snapshot

(Use table only as study aid; not explicitly in transcript, synthesized from pros/cons.)

Practical Tips for Exam & Real World

• Quote examples (Delta Manufacturing functional chart, Zeus Electronics dedicated team, Zeta Manufacturing matrix) to illustrate each structure.
• For case analysis, map project characteristics to structure choice using the continuum rule.
• Watch for "projectitis" symptoms: us-vs-them language, resistance to sharing resources.
• When asked to improve matrix friction, propose PMO interventions (training, common processes, dispute escalation path).
• To assess culture quickly in interviews, observe office layout, dress, meeting punctuality, and ask for typical success stories.
• Remember ethical angle: culture legitimizes management system; misalignment can erode integrity (e.g., overlooking cost overruns).