Ch7 — Organizational Structure — Lesson & Tracker
Progress Tracker
| Concept | Attempts | Correct | Last Tested | Status |
|---|---|---|---|---|
| AuthorityDelegation | 1 | 1 | 2026-04-19 | 🟢 |
| OrganizationalDesigns | 1 | 1 | 2026-04-19 | 🟢 |
| CentralizedVsDecentralized | 1 | 1 | 2026-04-19 | 🟢 |
Your Weak Points
| Gap | History | Status |
|---|---|---|
| No gaps identified yet | — | — |
Error Notes
(none yet)
Concept Map — Weak → Strong Connections
graph TD OS["Organizational Structure<br/>Blueprint: jobs + relationships"] OS --> BB["Building Blocks<br/>Specialization + Departmentalization"] OS --> AUTH["Authority System<br/>Responsibility · Authority · Delegation · Accountability"] OS --> DES["Formal Designs<br/>Functional · Divisional · Matrix · Project · International"] OS --> CD["Decision-Making<br/>Centralized vs. Decentralized"] AUTH --> LINE["Line Authority<br/>Direct chain of command"] AUTH --> STAFF["Staff Authority<br/>Advisory / Expertise-based"] CD --> CENT["Centralized<br/>Top managers decide<br/>Slow · Consistent"] CD --> DECENT["Decentralized<br/>Lower managers decide<br/>Fast · Empowering"] DES --> MATRIX["⚠️ Matrix Structure<br/>TWO bosses — most exam-distinct"]
Organizational Structure — Lesson
Source: OrganizationalStructure, AuthorityDelegation, OrganizationalDesigns
What Structure Defines
Organizational structure = the specification of jobs to be done and how those jobs relate to one another. It is the company’s official blueprint: who does what, who reports to whom, how authority flows, and how decisions get made.
The organizational chart is the visual representation of the formal structure — but it only shows the official hierarchy. The informal organization always co-exists alongside it.
Authority and Delegation — Lesson
Source: AuthorityDelegation
The Four Terms — Know Every Distinction
| Term | Definition | Who Holds It |
|---|---|---|
| Responsibility | The duty to perform an assigned task | Subordinate |
| Authority | The power to make decisions needed to complete the task | Subordinate (granted by manager) |
| Delegation | The manager’s act of assigning task + responsibility + authority downward | Manager |
| Accountability | The subordinate’s obligation to justify results to their manager | Subordinate |
The critical rule: Responsibility and authority must be paired. Giving someone a task without the power to make the necessary decisions sets them up to fail.
How they flow: Manager delegates → Subordinate receives responsibility + authority → Subordinate is accountable for results
Types of Authority
| Type | Definition | Example |
|---|---|---|
| Line Authority | Direct chain of command — flows top to bottom | CEO → VP → Manager → Supervisor |
| Staff Authority | Advisory — based on expertise, not command | Legal counsel advising the CEO |
| Committee/Team Authority | Granted to committees involved in daily operations | Cross-functional project team |
Line vs. Staff: Line = command. Staff = advice. A legal department advises — it does not command the finance team.
Span of Control
- Narrow span → fewer direct reports, more management layers (tall structure)
- Wide span → more direct reports, fewer layers (flat structure)
Centralized vs. Decentralized
| Centralized | Decentralized | |
|---|---|---|
| Who decides | Top managers retain most decisions | Middle and lower managers make significant decisions |
| Speed | Slower — decisions travel up the hierarchy | Faster — made closer to the action |
| Consistency | High | Variable |
| Empowerment | Low at lower levels | High at lower levels |
| Best for | Stable, routine environments | Dynamic, fast-changing environments |
Organizational Designs — Lesson
Source: OrganizationalDesigns
The Five Structures — Know All Five
| Structure | Defining Feature | Exam Giveaway | Key Weakness |
|---|---|---|---|
| Functional | Groups employees by shared activity | ”All marketing in one dept” | Departmental silos |
| Divisional | Semi-autonomous units by product/region/customer | ”Each division has its own HR and finance” | Duplication of resources |
| Matrix | Employees report to two supervisors simultaneously | ”Reports to both a project manager and a department head” | Conflicting priorities, unclear accountability |
| Project | Temporary teams assembled for one objective | ”Team disbands when the project ends” | No continuity after project |
| International | Designed for cross-border operations | ”Separate regional divisions for North America and Europe” | Cultural and coordination complexity |
The Matrix Structure — Most Exam-Distinct
An employee in a matrix org reports to:
- A functional manager (their specialty’s head — e.g., Engineering Director)
- A project manager (running the initiative they’re assigned to)
This “two boss” design maximizes flexibility and cross-functional expertise — but creates potential for conflicting instructions and accountability gaps.
Scenario tip: If a question describes “employees with two reporting relationships” or “dual accountability” → Matrix.
Exam Scenario Recognition
| Scenario | Structure |
|---|---|
| ”All engineers in one department, all marketers in another” | Functional |
| ”North America division and Asia-Pacific division each run independently” | Divisional |
| ”An employee’s performance review involves both their department head and their project lead” | Matrix |
| ”A team was assembled to launch a product; it will be dissolved after launch” | Project |
| ”An international department handles all cross-border sales separately” | International |