Spans are computed two ways, layers counted by function and each layer tested on Jaques's time-span logic in this span and layers review for GM543 Unit 8. Searches like "gm 543 unit 8 assignment example", "gm543 unit 8 sample" and "gm543 unit 8 example" land here.
What a finished GM543 Unit 8 span and layers review looks like
Two tables carry about five pages, with a short appendix showing how the numbers were produced. The first table gives headcount, managers and average span by function, computed twice: once counting the 30 working team leads in the plants as managers, which yields 93 managers and a mean span of 5.4, and once treating them as lead operators, which yields 63 managers, a mean of 4.3 and a median of 3. The second table lists layers from the CEO to the front line: seven in the plants, six in customer operations, four in sales. Commentary follows on three findings: five production managers each supervising two area supervisors, three managers with a single direct report, and a coordination supervisor holding nineteen people whose work is the least routine in the company.
How a GM543 Unit 8 example is structured
The review separates arithmetic from judgment and keeps the arithmetic checkable. Counting rules come first, since spans change with what counts as a manager, and the paper reports both versions instead of choosing the flattering one. The layer count follows, function by function, because a company average hides the plants' seven layers behind sales' four. Judgment then works through Jaques's argument that each managerial layer should carry a distinctly longer time horizon than the one below it. Area supervisors plan the week; the production managers above them, on the evidence of their calendars, also plan the week, so one of those layers adds no new horizon. Span is judged against the work rather than a benchmark: team leads with eight operators on standardized tasks is reasonable, while nineteen coordinators handling custom projects under one supervisor is not.
Counting rules, stated first
Who counts as a manager, how vacancies are treated, and why working team leads are shown both ways. The appendix gives the counts by role so a reader can repeat the arithmetic from the chart.
Spans by function, twice
With team leads as managers: 93 managers, mean span 5.4, median 6. Without them: 63 managers, mean 4.3, median 3, and 35 with three or fewer reports. The difference is reported rather than resolved away.
Seven layers in the plants
CEO, operations vice president, plant manager, production manager, area supervisor, team lead, operator. Sales reaches its territory managers in four. Of each plant layer the review asks what decision it holds that the layer beneath cannot.
Two layers planning the same week
Jaques's test applied to calendars and meeting notes: production managers and area supervisors both work a horizon of days to a week. Removing production managers in the smaller tables plant first is proposed, with their decisions reassigned by name.
Nineteen coordinators, one supervisor
The widest span sits over the least standardized work, custom projects that each cross five groups. Splitting it into two teams of about ten, aligned to project type, is proposed alongside the integrator role an earlier unit recommended.
Where marks go in GM543 Unit 8
Span and layers reviews in GM543 are marked on whether the numbers are tied to the work. Comparing an average span with a textbook ideal of six or eight earns little, because the course treats the right span as a product of how standardized, dispersed and interdependent the supervised work is. Arithmetic nobody can reproduce also costs marks; stating counting rules and showing the count is expected. Reviews recommending that a layer be removed without saying what it currently decides tend to lose the judgment credit, since a thin layer can still hold a real decision. What scores is a clear count, one test applied consistently to each layer, and spans judged against specific work, with every proposed change naming who absorbs the removed layer's decisions and what that person stops doing.
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.
GM543 Unit 8 questions, answered
Should working team leads count as managers?
It depends on what they do, and the honest answer is often to show both. A lead who assigns work, trains and handles first-level problems but does not hire, rate or discipline sits between the two definitions. The sample reports spans both ways because the choice moves the median from six to three, and a reader deserves to see that before any conclusion is drawn.
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.