| Course | MGT 805 Designing Organizational Structures |
|---|---|
| Topic | Topic 8 |
| Paper type | Structural choice defense |
| Length | About 1,200 words, 6 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for MGT 805 Topic 8
Chosen for What It Must See: Defending a Functional Core With Integrators and One Division Against Four Alternative Structures for a Farm Machinery Maker
[Author Name]
College of Doctoral Studies, Grand Canyon University
MGT-805: Designing Organizational Structures
Topic 8 Assignment
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Chosen for What It Must See: Defending a Functional Core With Integrators and One Division Against Four Alternative Structures for a Farm Machinery Maker
The Criterion
Coldwater Implement Company's leaders have debated their structure for a year. This paper settles the debate by choosing one design and defending it against the alternatives. The criterion comes from the problems earlier analysis found, not from the strengths of any design. A structure for Coldwater must make four things visible to people with authority to act: subscription renewals in precision guidance, a farmer's downtime as it crosses functions, the depth of the firm's shared engineering, especially in electronics, and the use of its two plants across seasonal demand. A design is chosen by the problems it must see, and the four are listed before any design is described so the list cannot be fitted to a favorite.
Five Designs Scored
Table 1
Five Designs Against the Four Problems Coldwater Must See
| Design | Renewals | Downtime across functions | Engineering depth | Plant utilization |
|---|---|---|---|---|
| Functional core, three integrators, guidance division (chosen) | Sees: division owns renewals | Misses unless owned | Protects: electronics stays mostly shared | Protects: plants remain shared |
| Full divisional form | Sees | Partly: each division owns its own repairs | Weakens: engineers split three ways | Weakens: plants divided |
| Firm-wide matrix | Partly: shared ownership | Partly | Protects | Protects, but reopens measured conflicts |
| Front-back design | Partly: front owns customers | Sees best: one customer-facing unit | Weakens: back split from field knowledge | Protects |
| Network with contract manufacturers | Sees | Weakens: repairs depend on outside firms | Weakens | Loses plant knowledge |
Table 1 scores five designs against the four problems. Each cell gives a judgment and its reason.
The Chosen Design and Its Admitted Gap
The chosen design keeps engineering, manufacturing, sales and aftermarket service as functions for grain handling and irrigation, with product integrators coordinating each line, and places precision guidance in a self-contained division that owns software, subscriptions and support. It sees renewals because the division owns them. It protects engineering depth because the electronics engineers for the two slower lines stay together, and plant utilization because both plants remain shared.
It still misses downtime. A farmer's broken dryer at harvest passes through service, warranty and parts, all functions, and the integrators coordinate product decisions rather than repairs. The design would leave that gap open unless someone owns it. The defense therefore adds a downtime owner inside aftermarket service, with authority to release harvest-season parts stock and approve warranty repairs below a set cost on the spot, and with elapsed days from failure to repair as the measure.
What Each Rejected Design Saw Better
Every alternative sees something better than the chosen design, and each deserves credit before its cost is stated. A full divisional form would give every product line the sharp ownership of results the guidance division gets, so irrigation's lost dealers would reach a responsible manager quickly. Its cost is the split of shared engineers and plants into three, which earlier analysis showed the slower lines cannot justify.
A firm-wide matrix would protect both engineering depth and product focus in principle. In practice the firm has already measured what it produces at Coldwater: 29 escalated disputes in a year, concentrated where conditions for a matrix were strongest. Extending it to all lines would spread that strain to places with less reason to bear it.
A front-back design, which Galbraith (2002) describes as a customer-facing front end linked to product-oriented back-end units, would see downtime better than any other option, since one front unit would own the farmer's experience across all products. Its cost is the separation of engineering from the field, where most of the knowledge about failures originates, and a second layer of coordination between front and back.
A network design that outsources manufacturing to contract builders would see renewals and cut fixed costs. It would also lose the plant knowledge that lets Coldwater shift capacity between grain and irrigation equipment as the seasons change, and make repair parts depend on outside schedules at harvest.
Why the Downtime Owner Sits in Service
The downtime owner could have been placed elsewhere, and the choice deserves a reason. Placing the role in the guidance division would cover only guidance products, while most harvest downtime involves dryers and grain carts. Placing it with the chief operating officer would repeat the escalation pattern the firm is trying to escape, sending repair decisions upward. Aftermarket service already employs the people who arrive at the farm, and its dealer technicians are the first to know when a repair is stalled. The role gives that function authority it does not have today, over harvest-season parts stock and small warranty approvals, so that the person who sees the stall can act on it. The cost is some friction with the parts and warranty managers, who will lose a share of their discretion for six weeks a year, and the design accepts that friction because the farmer's lost harvest days are the larger cost.
Galbraith's Star Model as an Alignment Test
Galbraith (2014) argues that structure is only one of five design elements, alongside strategy, processes, rewards and people, and that the elements must fit together. A chart changed alone changes little. The chosen design is tested against each element. Planning processes must change so that the guidance division sets its own release schedule while the integrators keep a joint plan for the other two lines. Rewards must change so that integrators are measured on their lines' results and the division head on renewals, with part of each bonus tied to firm-wide results to protect shared engineering. People must change too: integrators need product knowledge and the respect of function heads, and the downtime owner needs field service experience and the confidence to override a warranty standard. If those elements are not aligned, the structure will be adopted on paper and bypassed in practice.
The Coherence Objection
Mintzberg (1979) offers the strongest objection to any hybrid. He argued that effective structures tend to be configurations, internally consistent combinations of design parameters, and that organizations mixing elements from different configurations risk pulling themselves apart. A functional core and a division under one chief executive might seem to be such a mix.
The answer is that the hybrid is confined to one boundary. The functional core is coherent on its own terms: standardized work, shared specialists and coordination through integrators. The division is coherent on its own terms: a self-contained unit controlled by results. Each side follows one logic, and the points where they meet, the shared plants, the dealer relationship and the electronics reviews, are named and governed. Mintzberg's warning applies most to designs that blend logics within the same unit, which this design avoids.
What the Organization Accepts It Will Not See Well
No structure sees everything, and this one will see some things poorly. Irrigation and grain handling results will reach senior managers more slowly than they would under full divisions. Guidance hardware choices will be weighed against plant schedules the division does not control. And transfer disputes over receivers will absorb some executive time each year. Coldwater should accept these costs knowingly, review the watch measures each quarter and revisit the design if the slower lines begin to change as quickly as guidance does.
References
Galbraith, J. R. (2002). Organizing to deliver solutions. Organizational Dynamics, 31(2), 194-207. https://doi.org/10.1016/S0090-2616(02)00101-8
Galbraith, J. R. (2014). Designing organizations: Strategy, structure, and process at the business unit and enterprise levels (3rd ed.). Jossey-Bass.
Mintzberg, H. (1979). The structuring of organizations: A synthesis of the research. Prentice-Hall.
What the MGT 805 Topic 8 instructions ask for
MGT-805 ends with Topic 8, where doctoral learners choose a structure for an organization and defend it against the alternatives. The brief asks for a criterion set before the options are compared, a fair assessment of each option and an honest account of what the chosen design will miss. A paper meets it when the criterion comes from evidence about the organization's problems, every alternative is credited with what it does better, and the chosen design is tested for alignment with processes, rewards and people. Doctoral learners should draw on Galbraith's star model and Mintzberg's configurations, answer the objection that a hybrid lacks coherence, and close by stating what the organization accepts it will not see well.
Inside the MGT 805 Topic 8 example
A short list of what the manufacturer's structure must see opens the finished defense, taken from earlier analysis: subscription renewals, a farmer's downtime across functions, engineering depth and plant utilization. Each of five designs is scored on those four, each judgment reasoned. The chosen design, a functional core with three product integrators plus a precision guidance division, sees renewals and protects engineering depth and plant scale, but misses downtime unless someone owns it, so the defense adds a downtime owner inside aftermarket service. A full divisional form would see product results and split the shared plant. A firm-wide matrix would reopen the conflicts measured earlier. A front-back design would see downtime best and fracture engineering. A flatter network relying on contract manufacturers would lose plant knowledge. Galbraith's star model then tests whether processes, rewards and people follow the choice.
MGT 805 Topic 8 rubric: what Excellent looks like
An Excellent defense earns its marks by letting the alternatives compete fairly. The rubric rewards a criterion drawn from earlier findings, not from the preferred design's strengths, and a scoring table with reasons in every cell. Credit goes to admitting the chosen design's gap and covering it with a specific role, here a downtime owner in aftermarket service. Faculty look for each rejected design credited with what it sees better before its cost is stated. Strong papers use the star model to test whether planning, rewards and people support the structure. The highest band answers Mintzberg's coherence objection by confining the hybrid to one boundary and lists the costs the organization accepts.
Common MGT 805 Topic 8 mistakes, and how to avoid them
Structural defenses fall hardest when they compare alternatives on their weaknesses only, which lets the chosen design win a contest nobody else was allowed to enter. A defense whose criterion is taken from the preferred design's strengths has decided before comparing anything. Papers that choose a hybrid without admitting what it misses repeat the error the course was built to correct, and the downtime gap here is where a reader looks first. Recommending a structure with no attention to processes, rewards and people treats the chart as the whole design, which Galbraith's star model argues against. Dismissing the flat or network option in a sentence suggests it was never examined. Without Mintzberg's coherence objection, the defense leaves its hybrid untested against the literature's strongest case for consistent forms.
Get an MGT-805 Topic 8 example written to your instructions
Send the MGT-805 Topic 8 instructions and the rubric from your classroom, with the organization, prior analyses or case the assignment names. We write a custom example to those criteria, with a criterion drawn from evidence, five designs scored with reasons, the chosen one's gap admitted, alignment tested and the coherence objection answered, in 24 to 48 hours. The first one is free.
More MGT 805 papers and DBA samples
- MGT 805 Topic 1: Structural Trade-off Essay
- MGT 805 Topic 2: Grouping Basis Comparison
- MGT 805 Topic 3: Coordination Cost Quantification
- MGT 805 Topic 4: Matrix Strain Analysis
- MGT 805 Topic 5: Structural Blind Spot Dq Post
- MGT 805 Topic 6: Strategy-structure Lag Analysis
- MGT 805 Topic 7: Divisional Redesign Proposal
- MGT 820 Topic 8: Advantage Durability Assessment
- DBA 965 Topic 8: Final Defense Question Bank
- MGT 825 Topic 8: Disclosure Policy Position Paper
- DBA 960 Topic 8: Achieved Sample Description
MGT 805 Topic 8 questions, answered
What is Galbraith's star model?
Jay Galbraith's framework for organization design, which treats structure as one of five linked policy areas: strategy, structure, processes, rewards and people. Its central claim is that the areas must align, so a new structure without matching planning processes, incentives and staffing tends to be undermined by the parts left unchanged. The example uses it to test whether the chosen structure could work in practice.
Why not choose a front-back structure if it sees downtime best?
Because downtime is one of four problems the structure must see, and a front-back design would split engineering between customer-facing and product-facing units, weakening the depth the manufacturer's products rely on. The defense credits front-back with the clearest view of the customer, then covers the downtime gap in the chosen design with a dedicated owner. The trade is stated openly rather than hidden.
Is a hybrid structure a compromise that avoids choosing?
It can be, when a hybrid mixes forms everywhere to avoid offending anyone. The example uses one only at a single boundary, where evidence showed one product line meets the conditions for a self-contained unit and two do not. Each side stays internally consistent, the reason for the boundary is stated, and the defense lists what the arrangement will still miss.
Where can I find a free MGT 805 Topic 8 sample paper?
This page holds the whole structural choice defense: the four-problem criterion, the five-design scoring table, the chosen design and its gap, each rejected design, the star model test and the coherence reply. Tell us which organization and options you are weighing and a free defense can be prepared.
Why is the downtime owner placed in aftermarket service in MGT 805 Topic 8?
Service employs the people who reach the farm first and see a stalled repair. Giving that role authority over harvest parts stock and small warranty approvals lets the person who sees the problem act on it without escalation.