| Course | GM543 Strategic Organizational Design and Architecture |
|---|---|
| Unit | Unit 8 |
| Paper type | Span and layers review |
| Length | About 1,170 words, 7 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MS in Management |
| Updated | October 2026 |
Free sample paper for GM543 Unit 8
Half the Managers Supervise Three or Fewer: A Unit 8 Span and Layers Review of a Furniture Maker
[Student Name]
Purdue University Global
GM543: Strategic Organizational Design and Architecture
Unit 8 Span and Layers Review
[Instructor Name]
[Date]
Harrow Contract Furniture, its chart and every figure are composite and illustrative; the frameworks and studies cited are real.
How the Figures Were Produced
The review starts from Harrow Contract Furniture's current chart and payroll list, which together show every employee and the person each reports to. A manager is anyone with at least one direct report. Span of control is the number of direct reports a manager has. A layer is one level of reporting, counted from the CEO at layer one.
One choice changes the results more than any other. The plants have 30 team leads who work on the line for most of each shift, assign tasks and cover absences, but who cannot hire, discipline or approve time off. They can be counted as managers or as lead operators. The review computes every figure both ways. The method follows the logic of span studies such as Meier and Bohte's, which show that how a span is counted shapes what it seems to show (Meier & Bohte, 2003).
Headcount, Managers and Spans by Function
Counting team leads as managers, Harrow has 94 managers and a mean span of 5.3, with a median of 4. Counting them as lead operators, it has 64 managers and a mean span of 7.8, but a median of only 3.5, and 32 of the 64 managers supervise three people or fewer. The mean is pulled up by the ten area supervisors, whose span becomes 30 when team leads are counted as operators, and by the coordination supervisor with 19.
By function, counting team leads as lead operators, the picture is uneven.
Operations has 341 people and 23 managers. Its mean span is high, about 15, because area supervisors oversee whole production areas. Counting team leads as managers, the mean falls to about 6.4.
Sales has 37 people and 7 managers, a mean span of about 5. The four regional directors supervise 22 territory managers between them.
Engineering has 40 people and 13 managers, a mean span of 3. Nine engineering group managers each supervise three engineers, and three directors each supervise three group managers.
Customer operations has 41 people and 8 managers, a mean of 5, but the figure hides the widest range in the company: the vice president has one direct report, the director and the customer operations manager each have two, and the coordination supervisor has nineteen.
Supply chain has 22 people and 5 managers, finance 13 people and 4 managers, and human resources 7 people and 3 managers. Each has a mean span of about 2 to 4.
Layers From the CEO to the Front Line
The plants have seven layers: the CEO, the vice president of operations, a plant manager, a production manager, an area supervisor, a team lead and an operator. Customer operations has six: the CEO, the vice president, a director, the customer operations manager, the coordination supervisor and a coordinator. Sales has four: the CEO, the vice president of sales, a regional director and a territory manager.
For a company of 502 people, seven layers is a tall structure. Raghuram Rajan and Julie Wulf found that large United States firms removed layers between the CEO and division heads through the 1990s and widened the CEO's span (Rajan & Wulf, 2006). Harrow's layers sit lower in the structure, in the plants and customer operations.
The question for each layer is not whether it has a manager in it but what work it does that the layer above and below cannot.
Finding One: Production Managers With Two Reports
Each of the five production managers supervises two area supervisors. Each area supervisor runs a production area with three team leads and about 27 operators. Interviews with three production managers found that most of their time goes to collecting reports from area supervisors and passing them to the plant manager, and to attending the Tuesday order review. Area supervisors already plan the work and handle staff issues; plant managers already set targets.
This layer does little distinct work. Removing it would let each plant manager supervise five or six area supervisors directly, a span well within the range Lyndall Urwick suggested for managers whose reports' work interlocks (Urwick, 1956). The plants would drop from seven layers to six.
Finding Two: Three Managers With One Report
Three managers have a single direct report: the vice president of customer operations, who supervises only the director; the planning and analysis manager in finance, who supervises one analyst; and the HR manager, who supervises one specialist. A manager with one report is usually doing the same work as that report or is checking it. In customer operations, the vice president and director attend the same meetings and approve the same exceptions. In finance and HR, the single reports could move to the controller and the vice president of HR.
Finding Three: Nineteen Coordinators Under One Supervisor
The coordination supervisor carries the widest span outside the plants. Wide spans suit routine work, where a supervisor needs little contact with each person. Coordinators' work is the least routine in the company: every large project raises new questions about fabric, dates or installation. The supervisor reports spending most days answering escalations and has not held regular one-on-one meetings in a year.
This finding runs the other way from the first two. Harrow does not have too many managers in customer operations so much as managers in the wrong places: two layers above the coordinators supervising one or two people each, and one supervisor below them stretched across nineteen. Julie Wulf's later study found that flattening often moved decisions up to the top rather than pushing them down (Wulf, 2012). At Harrow, removing a customer operations layer should come with more supervision close to the coordinators, not less.
What the Three Findings Add Up To
Taken together, the findings suggest about eight manager roles that add little distinct work: the five production manager roles and the three single-report roles. Removing them would save roughly $900,000 a year in salary and benefits, but the review recommends spending part of that saving on a second coordination supervisor, so that coordinators have a manager with time for them. The plants would lose a layer, customer operations would lose one at the top and gain supervision at the bottom, and the company would have fewer managers placed closer to the work.
Appendix: Calculation Notes
Total direct reporting links equal headcount minus one, or 501. Mean span is 501 divided by the number of managers: 501 over 94 gives 5.3, and 501 over 64 gives 7.8. The median is taken from the list of every manager's span. When team leads are counted as operators, each area supervisor's span is three team leads plus their 27 operators, or 30. Function counts include each function's vice president.
References
Meier, K. J., & Bohte, J. (2003). Span of control and public organizations: Implementing Luther Gulick's research design. Public Administration Review, 63(1), 61-70. https://doi.org/10.1111/1540-6210.00264
Rajan, R. G., & Wulf, J. (2006). The flattening firm: Evidence from panel data on the changing nature of corporate hierarchies. Review of Economics and Statistics, 88(4), 759-773. https://doi.org/10.1162/rest.88.4.759
Urwick, L. F. (1956). The manager's span of control. Harvard Business Review, 34(3), 39-47.
Wulf, J. (2012). The flattened firm: Not as advertised. California Management Review, 55(1), 5-23. https://doi.org/10.1525/cmr.2012.55.1.5
The Purdue Global GM543 Unit 8 instructions
GM543 Unit 8 asks you to review an organization's spans of control and layers. Define a manager, a span and a layer before you count, and decide how to treat roles such as working team leads, which can change the results sharply; computing both ways is often the honest answer. Report headcount, managers and spans by function, with the mean and the median, since a few wide spans can hide many narrow ones. List the layers from the top to the front line in each part of the organization. Then test each layer and each unusual span against the work it supervises: routine work tolerates wide spans, complex work needs narrower ones. Present findings with their costs and a short recommendation. Expect about five pages with an appendix explaining your calculations, citing research on span and hierarchy in APA 7.
How the GM 543 Unit 8 example is put together
The method defines manager, span and layer and explains why team leads are counted both ways, citing Meier and Bohte. Spans by function show operations at about 15 with team leads treated as operators, engineering at 3 with nine group managers, and customer operations ranging from one report for the vice president to nineteen for the coordination supervisor. Layers run seven in the plants, six in customer operations and four in sales, compared with Rajan and Wulf's flattening evidence. The highlighted sentence sets the test of distinct work. Finding one removes the production manager layer, citing Urwick. Finding two questions three single-report managers. Finding three argues for more supervision near the coordinators, citing Wulf's caution about flattening. A summary estimates about $900,000 in savings, part spent on a second supervisor, and an appendix shows the arithmetic.
Reading the GM543 Unit 8 grading rubric
GM543 rubric credit for this review depends on clear definitions and correct arithmetic. Instructors check that manager, span and layer are defined before counting and that ambiguous roles are handled openly, ideally both ways. Reporting both mean and median earns credit, since a few wide spans can distort the average badly. Spans and layers should be judged against the work supervised rather than a single benchmark. Findings earn more when each names a role, its cost and a reason it adds or lacks distinct work. Recognizing that some parts need more supervision, not less, shows balance. An appendix that lets the reader repeat the figures carries weight. Meier and Bohte, Rajan and Wulf, Wulf's California Management Review article and Urwick in Harvard Business Review supply the citations in APA 7.
GM543 Unit 8 help: mistakes that cost points
Many GM543 Unit 8 reviews report a single average span and stop there, which hides the narrow spans a median would reveal. Others count team leads one way without saying so, which changes every figure. A common gap is the test of distinct work: counting layers without asking what each decides gives the reader numbers but no finding. Some writers recommend flattening everywhere, ignoring parts of the organization where supervision is already too thin. Define the terms, count both ways where roles are ambiguous, report the mean and median, list the layers in each function, ask what each layer and span adds, show where you would remove managers and where you would add one, and include your calculations.
Get a GM543 Unit 8 example written to your instructions
Share a chart of the organization or unit named in the Unit 8 prompt, even a rough one, with approximate headcounts under each manager and a sentence on what each group does. Add the instructions and rubric. A first review is free and returned in 24-48h, counting rules shown and every layer tested against the work it supervises. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More GM543 papers and MS in Management samples
- GM543 Unit 1: Functional Structure Discussion Post
- GM543 Unit 2: Star Model Organization Profile
- GM543 Unit 3: Functional vs Divisional Comparison
- GM543 Unit 4: Coordination Mechanism Analysis
- GM543 Unit 5: RAPID Decision Rights Map
- GM543 Unit 6: Reorganization Swings Reflection
- GM543 Unit 7: Matrix Dispute Case Analysis
- GM543 Unit 9: Fit Assessment Memo
- GM543 Unit 10: Organization Design Recommendation
- GM541 Unit 8: Fair Process Change Communication
- GM506 Unit 8: Second Plant Sensitivity Analysis
- GM505 Unit 8: Aid Pilot Data Gathering Plan
- GM504 Unit 8: Scanning Cost and Benefit Analysis
GM543 Unit 8 questions, answered
Is there an ideal span of control?
Not one number. Research and practice both point to the work: routine, similar and colocated tasks allow wide spans, while complex, varied or dispersed work needs narrower ones. Figures of six to eight appear in consulting benchmarks but should not be applied without that context. A review is stronger when it explains why each span fits or fails its particular work.
Where does Jaques's time-span idea come from?
From Elliott Jaques's research on managerial work, summarized for a general audience in his 1990 Harvard Business Review article, In Praise of Hierarchy. He argued that each layer should carry a longer horizon of discretion than the one below, with boundaries around three months, one year, two years, five years and ten. It gives a review a test for layers that goes beyond headcount.
Where can I find a free GM543 Unit 8 sample paper?
This page carries a full GM543 Unit 8 span and layers review of a 502 person furniture maker, with spans counted two ways, layers by function, three findings and APA 7 references.
Why report both the mean and the median span?
A few very wide spans pull the mean up and hide many narrow ones. Counting team leads as operators, the mean span is 7.8 while the median is 3.5, and half the managers supervise three people or fewer.
Why add a supervisor while removing managers?
The nineteen coordinators do the least routine work in the company and have had no regular one-on-one meetings in a year. Wide spans suit routine work, so the review removes layers above them and spends part of the saving on supervision closer to them.