A front-back design for a furniture maker, checked against the fit criteria and priced through its transition: the organization design recommendation that closes GM543 in Unit 10. Searches like "gm 543 unit 10 assignment example", "gm543 unit 10 sample" and "gm543 unit 10 example" land here.
What a finished GM543 Unit 10 organization design recommendation looks like
Eight to nine pages with an executive summary, two charts and a transition timeline. Its summary gives the recommendation, its price and the one condition that would change it. The current and proposed charts face each other: in the proposal, a Workplace Projects unit and a Healthcare unit own customers, pricing and project management, while the plants, engineering platforms and supply chain serve both under written service terms. Three alternatives considered and rejected share a page, a full divisional split among them. Each fit criterion from the previous memo then becomes a row showing how the design meets it. The second half prices the transition: one-time costs in brackets, a productivity dip estimated from the company's last reorganization, a three-phase sequence, and the measures that would show the design working after a year.
How a GM543 Unit 10 example is structured
The recommendation argues in the order a board would ask its questions: what, why this rather than something else, what it costs, and how anyone will know it worked. Galbraith's front-back model supplies the design logic, since the strategy needs customer focus on two markets while the plants still need scale; the paper names that as a hybrid and states the cost that comes with it, a permanent negotiation between front and back over priorities and transfer prices. Alternatives are rejected on the criteria, not on preference. The transition section borrows evidence from earlier units: decision rights from the RAPID map are rewritten for the new units, the integrator role becomes the project owner, and the plant layer found redundant is removed in phase one. Costs appear as ranges, and the last section lists what would count as failure after four quarters.
Recommendation, price and the condition
Two front-end units, a shared back end, one owner per large project. A one-time cost of [a stated range], [two] quarters of lower output, and a reversal condition: healthcare volume below [a set level] after a year.
Why not a full divisional split
Splitting the plants by market would duplicate tooling and halve the seating plant's run lengths. A matrix everywhere was tried in the pilot and stalled. Staying functional fails the fit criteria. Each rejection cites the criterion it fails.
Front and back, with the seam priced
Front units own customers, pricing and project delivery; the back end owns plants, engineering platforms and supply. Quarterly capacity allocation and a transfer price govern the seam, and the paper admits that negotiation never ends.
Decision rights rewritten
Ship dates move to the project owner, with the plant scheduler holding an agree; customer's own material goes to the front unit's product manager; discounts stay with sales leaders inside a margin floor finance sets.
Three phases and their costs
Phase one removes the redundant plant layer and appoints project owners; phase two stands up the healthcare unit; phase three moves rewards to delivered margin and on-time projects. Each phase carries a cost range and a start date.
What failure would look like
Project lead times unchanged after four quarters, healthcare quotes still crossing three groups, or plant cost per unit up more than [a set percentage]. Any one of these triggers a review of the design rather than another standing meeting.
Where marks go in GM543 Unit 10
Design recommendations in GM543 are marked on the transition as much as on the design. A new chart with a paragraph on implementation, typically an announcement date and a communication plan, tends to forfeit the marks the course reserves for pricing change. Recommendations that answer no stated criteria read as preference, and many graders look for the link back to the fit assessment. Omitting what the new design makes harder costs ground too, since every structure trades one kind of coordination for another. The stronger papers reject named alternatives for stated reasons, rewrite decision rights rather than only boxes, show one-time costs and the productivity dip as ranges, and define in advance what evidence would show the design failing. Admitting the permanent seam between front and back earns more than presenting the hybrid as free.
Get a GM543 Unit 10 example written to your instructions
Bring the organization and strategy that Unit 10 focuses on, along with anything earlier units produced: profile, maps, fit results. Include the prompt and rubric. A first recommendation is drafted without charge and returned in 24-48h, alternatives rejected on stated grounds and the transition priced in ranges your section can check.
GM543 Unit 10 questions, answered
How can transition costs be estimated without company data?
From ranges and analogies, labeled as such. Severance, recruiting, systems changes and training can be estimated from public benchmarks or from the organization's own past changes. The productivity dip is best estimated from the last reorganization anyone remembers. Brackets and ranges are expected; false precision is not. The sample shows every cost as a range with its basis stated.
What is a front-back design?
A hybrid in which customer-facing units are organized around markets or segments while the back end stays organized around products, technology or operations, serving every front unit. Galbraith describes it as a way to gain customer focus without giving up scale. Its cost is the seam: priorities and prices between front and back must be negotiated continually, which the recommendation should say plainly.
Does the recommendation have to use earlier units' work?
Many prompts expect it, and it makes the paper stronger even where not required. Earlier analyses supply evidence the recommendation would otherwise have to assert, such as decision rights gaps or a redundant layer. Revising earlier findings in view, where later units showed something new, usually reads as better judgment than repeating them unchanged.