100%

Module 1 - Program & Project Management

Day 4: Organizational Structures & Authority

19% of the exam - about 2.5 hours - 14 practice questions

0:00 / --:--

Reading

The organizational structure a CM operates within materially affects their authority. This is an often-missed area because candidates memorize definitions without connecting them to what actually happens when two departments want the same person on the same day.

Functional organization: authority stays with the department

Staff report through discipline-based departments (engineering, estimating, scheduling), each with its own manager. A CM working within a functional organization has low authority. They must negotiate for resources through functional managers who control staff assignments, priorities, and performance reviews. If a scenario says staff "report to their department head first" or must "get approval before committing time," that is functional or weak-matrix language, and the CM's unilateral authority is limited.

Projectized organization: authority moves to the CM

Staff report directly to the CM or project manager for the duration of the project; functional departments barely exist, if at all. The CM has high authority: full control over project resources and staff assignment, without having to negotiate for anyone's time. The tradeoff is that specialized staff may sit idle between projects, since there is no functional department to reassign them when project work slows.

Matrix organizations: a hybrid, and it comes in three strengths

In a matrix organization, staff have dual reporting lines: a functional manager and a project manager. Authority scales with the matrix's "strength."

  • Weak matrix: Authority favors the functional manager; the CM acts more as a coordinator or expediter, tracking and facilitating work without much power to direct it.
  • Balanced matrix: Authority is roughly shared. This sounds fair on paper and can produce friction in practice, because neither party can decide alone when the two disagree.
  • Strong matrix: Authority favors the CM, who resembles a projectized-organization PM, though functional departments still formally exist.
CM authority across organizational structures, low to high A spectrum from Functional (lowest CM authority) through Weak Matrix, Balanced Matrix, Strong Matrix, to Projectized (highest CM authority), with functional-manager authority decreasing in the same order. Functional manager authority high CM authority high Functional Dept. manager owns staff Weak Matrix CM = coordinator Balanced Matrix Authority roughly shared Strong Matrix CM leads; depts. still exist Projectized Staff report to CM Scenario clue: "must get approval from department head" points left; "reports directly to the CM" points right.
CM authority rises left to right as the organizational structure moves from Functional toward Projectized.

When formal authority is limited: leading through influence

In a weak or balanced matrix, a CM's formal authority alone often isn't enough to get disputed work done. Experienced CMs fall back on influence that doesn't depend on the org chart: expert credibility (being visibly right about the technical or schedule consequences), relationship trust built before the conflict happened, and simply making the tradeoffs and their cost visible to whoever does have the authority to decide. The exam sometimes frames this as "the CM has no formal authority to resolve X, so what should they do", and the best answer is usually to escalate with a clear, data-backed recommendation, not to act unilaterally as if authority existed that doesn't.

Organizational Breakdown Structure (OBS) and the responsibility assignment matrix

Where the Work Breakdown Structure (Day 3) decomposes what has to be done, the Organizational Breakdown Structure shows who the organization is, department by department or role by role. Overlaying the WBS against the OBS produces a responsibility assignment matrix, commonly built as a RACI chart, marking who is Responsible for doing the work, who is Accountable for its outcome, who must be Consulted before a decision, and who merely needs to be Informed after one. A scenario that describes confusion over "who actually signs off on this" is testing whether you recognize a missing or poorly defined RACI, not a scheduling problem.

Why this matters for the exam

Organizational structure questions test two things at once: can you name the structure from the clues in the scenario, and can you correctly predict how much unilateral authority the CM has inside it. A CM who acts as if they have projectized-level authority inside a functional organization is the wrong answer just as often as a CM who over-escalates inside a projectized one.

Practice Questions

1. In a projectized organization, the CM's authority over project staff is:

  1. Determined solely by the client, whatever the reporting lines
  2. Nonexistent
  3. High: staff report directly to the CM
  4. Low

2. A team member who must get approval from their department head before committing time to your project most likely operates in a:

  1. A pure projectized organization with a dedicated project team
  2. IPD structure
  3. Functional or weak matrix organization
  4. Strong matrix or projectized organization

3. In a balanced matrix, authority between the functional manager and the CM is generally:

  1. Roughly shared
  2. Undefined by design
  3. Entirely with the functional manager
  4. Entirely with the CM

4. A CM acting mostly as a "coordinator/expediter" without much unilateral authority likely operates in a:

  1. Balanced matrix
  2. Weak matrix
  3. Strong matrix
  4. Projectized organization

5. Which structure most resembles a projectized organization in terms of CM authority, while still retaining functional departments?

  1. Balanced matrix
  2. Purely functional
  3. Weak matrix
  4. Strong matrix

6. In a purely functional organization, who controls staff assignments to the project?

  1. Functional/department managers
  2. The contractor
  3. The CM
  4. The owner, through the project sponsor's approval of each assignment

7. A CM with limited formal authority in a weak matrix wants a disputed task prioritized. The best approach is generally to:

  1. Ignore the conflict and hope it resolves itself
  2. Assume projectized-level authority since the project needs it
  3. Direct the functional staff unilaterally, then inform the department head afterward and cite the project schedule as justification
  4. Escalate with a clear, data-backed recommendation to whoever holds the authority to decide

8. The Organizational Breakdown Structure (OBS) is best described as:

  1. A schedule of staff vacations
  2. A decomposition of project scope into work packages
  3. A representation of the organization's departments or roles, used to assign responsibility for WBS elements
  4. A synonym for the WBS

9. In a RACI chart, a person marked "A" for a task is:

  1. Accountable for the outcome, even if someone else performs the work
  2. Assigned to perform the work day to day, with no accountability for its outcome
  3. Merely informed after the decision is made
  4. Consulted before the decision, but not accountable for it

10. A scenario describes repeated confusion over "who actually signs off on this deliverable." This most directly points to:

  1. A scheduling delay
  2. A missing or poorly defined responsibility assignment matrix
  3. A cost overrun
  4. A quality control failure unrelated to organization

11. Which organizational structure trades higher CM authority for the risk that specialized staff sit idle between projects?

  1. Balanced matrix
  2. Functional
  3. Weak matrix
  4. Projectized

12. Which is the best description of a strong matrix organization?

  1. Functional departments are dissolved entirely and every staff member reports only to the CM
  2. Authority favors the CM, but functional departments still formally exist
  3. Authority is split exactly evenly with no exceptions
  4. The CM acts purely as a coordinator

13. Dual reporting lines, one functional and one to the project, are the defining feature of:

  1. Projectized organizations
  2. Matrix organizations of any strength
  3. Strong matrix organizations only, not weak or balanced ones
  4. Functional organizations

14. A CM who directs functional staff unilaterally inside a weak matrix, bypassing the department head, is most likely:

  1. Overstepping the authority the structure grants, which risks conflict and undermines the functional manager's role
  2. Required by the owner's contract whenever the project schedule is at risk and the department head is unavailable
  3. Improving efficiency with no downside
  4. Acting correctly, since the project's schedule and budget always outrank the department head's priorities

Micro-Assignment

Think of a team you've worked on (construction or otherwise). Identify its structure type (functional, weak/balanced/strong matrix, or projectized) and write 3-4 sentences describing one real resource conflict and how the structure's authority balance shaped how it got resolved. Then sketch a simple RACI for one deliverable from that project: who was Responsible, Accountable, Consulted, and Informed.

Glossary

Functional organization
Staff organized and managed by discipline department; low CM authority.
Projectized organization
Staff report directly to the CM for project duration; high CM authority.
Matrix organization
Dual reporting (functional and project); authority varies by matrix strength (weak, balanced, strong).
Organizational Breakdown Structure (OBS)
A representation of the organization's departments or roles, used alongside the WBS to assign responsibility.
Responsibility assignment matrix
A chart, commonly a RACI, mapping WBS elements against the OBS to clarify who does what.
RACI
Responsible, Accountable, Consulted, Informed: the four roles a responsibility assignment matrix typically assigns.
Coordinator/expediter
A limited-authority PM role, typical of a weak matrix, that tracks and facilitates work without directing it.

Progress

Previous: Day 3 Next: Day 5