| Course | MGT 805 Designing Organizational Structures |
|---|---|
| Topic | Topic 5 |
| Paper type | Discussion post and reply |
| Length | About 500 words, 3 pages |
| Format | Discussion post, APA 7 citations |
| School | Grand Canyon University (GCU) |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for MGT 805 Topic 5
Topic 5 DQ 1: Initial Post and Reply
Eleven Days of Harvest Downtime That No Function Owns: The Blind Spot in an Equipment Manufacturer's Functional Structure
Initial Post
The structure of my composite manufacturer, Coldwater Implement Company, cannot see harvest downtime, because downtime belongs to no function. Every step in a repair is owned; the elapsed time across the steps is not.
Here is one case, with illustrative figures. A farmer's grain dryer fails on day zero, in the middle of corn harvest. A dealer technician arrives and diagnoses a failed burner control on day two. The warranty claim is approved on day eight. The part is on backorder and arrives on day eleven. Now look at the reports. Field service met its two-day response target. Warranty decided within its six-day standard. Parts reported a 94 percent fill rate for the month, so this backorder was one of the few misses, and it shipped as soon as stock came in. Every function passed. The farmer lost eleven days of drying capacity at the one time of year it mattered, and probably some of the crop.
Lawrence and Lorsch (1967) found that departments organized around different tasks develop different goals and time horizons. That explains why each measure is sensible on its own terms: service thinks in response hours, warranty in claim cycles and parts in monthly fill rates. None of them is designed to watch the handoffs between steps, and no one above them sees the case until the dealer complains. Kerr (1975) adds the uncomfortable part. The firm rewards each function for its own number while hoping for fast recovery for the farmer, and people reliably deliver what they are rewarded for.
The usual reply is that better data would fix this, perhaps a dashboard that tracks each repair from failure to fix. I doubt it. A dashboard would make the eleven days visible, but a number nobody answers for tends to be noticed and then left alone. Visibility without ownership rarely changes what anyone does on Monday morning.
So my question for the class is this: if Coldwater created a downtime owner, which authority would that person need to change the result, control over parts allocation during harvest, the power to approve warranty claims on the spot, or a say in dealer scheduling? And which of those would the existing function heads resist most?
Reply to Daniel
Daniel, you argued that the problem is the parts function's fill rate target and that raising it to 98 percent would solve most harvest delays. It would help, and I agree the target is part of the story. But a higher fill rate still averages across the year, and harvest demand for dryer controls is concentrated in about six weeks. The function could hit 98 percent and still run short in October. That is the same pattern at a finer grain: a functional measure improving while the cross-functional outcome stays unowned. Would you pair your fill rate change with a harvest-season measure that the parts head shares with service?
References
Kerr, S. (1975). On the folly of rewarding A, while hoping for B. Academy of Management Journal, 18(4), 769-783. https://doi.org/10.5465/255378
Lawrence, P. R., & Lorsch, J. W. (1967). Differentiation and integration in complex organizations. Administrative Science Quarterly, 12(1), 1-47. https://doi.org/10.2307/2391211
What the MGT 805 Topic 5 instructions ask for
The Topic 5 discussion question in MGT-805 asks doctoral learners to identify something an organization's structure would fail to register. Learners post an initial response and reply to peers. A post fits the brief when it names the blind spot precisely, shows it passing through the structure with a concrete sequence of steps, and explains with theory why each unit misses it. Doctoral posts should cite sources for specific claims, anticipate the obvious remedy and test it, and finish by asking peers something that forces them to say who would have to change what. Replies should engage a classmate's argument directly, recognize what it gets right and show where it repeats the problem in a new form.
How the MGT-805 Topic 5 example is put together
Its claim comes first in the post: the manufacturer cannot see harvest downtime, because the problem belongs to no function. One composite case supplies the evidence. A dryer fails on day zero, a dealer technician diagnoses it on day two, the warranty claim is approved on day eight, and the part, backordered, arrives on day eleven. Each function reports success: field service met its two-day response target, warranty decided within its six-day standard, and parts kept a 94 percent fill rate, every figure illustrative. The farmer lost eleven days of harvest. The post cites Lawrence and Lorsch for the finding that differentiated departments develop their own goals and time horizons, which explains why each measure is locally sensible. It rejects the reply that better data would fix this and asks classmates what a downtime owner would need authority over.
Where the marks sit in the MGT 805 Topic 5 rubric
Instructors grading the post look for a blind spot demonstrated, not asserted. An Excellent post sets each function's own measure beside its step, so the reader sees every unit passing while the outcome fails. Credit goes to using Lawrence and Lorsch for their finding about differing goals and time horizons rather than a general claim that departments disagree. The rubric values engaging the likeliest remedy, here a dashboard, and explaining why visibility without ownership rarely changes behavior. Strong posts close with a question about authority that classmates must think through. Replies earn credit when they take a peer's proposal seriously and show how it improves a functional measure while leaving the cross-functional outcome unowned.
Common MGT 805 Topic 5 mistakes, and how to avoid them
A blind spot named in vague terms, such as communication or silos, gives no reader anything to check against a case. A strong answer shows the problem passing through the structure undetected, and a post without a sequence of steps asserts the blindness rather than demonstrating it. Blaming individual functions for poor performance misreads a case in which every function met its standard. Using Lawrence and Lorsch to say merely that departments disagree wastes the source, whose finding ties differences in goal and time orientation to each department's task. Posts that treat the blind spot as a reporting gap, closed by a dashboard, miss that visibility without ownership rarely changes what anyone does. A closing question that asks only whether classmates agree invites assent instead of argument, and a doctoral thread expects the harder question.
Get an MGT-805 Topic 5 example written to your instructions
Send the MGT-805 Topic 5 discussion question, the participation rubric for your section and any organization or case the prompt names. A custom example is written to those requirements, with the blind spot stated first, a case traced step by step, one source used precisely, the dashboard objection answered and a question left for classmates, 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 6: Strategy-structure Lag Analysis
- MGT 805 Topic 7: Divisional Redesign Proposal
- MGT 805 Topic 8: Structural Choice Defense
- MGT 820 Topic 5: Rival Imitation Timeline
- DBA 965 Topic 5: Absent Effect Dq Post
- MGT 825 Topic 5: Counsel Threshold Dq Post
- DBA 960 Topic 5: Collection Shortfall Dq Post
MGT 805 Topic 5 questions, answered
What is a structural blind spot?
A problem the organization's design gives no one reason or means to notice. It usually lies between units, where each unit's measures and goals stop, rather than inside any of them. Blind spots differ from failures of effort: every unit can perform well while the problem grows. The example shows one by setting each function's healthy measure beside a customer outcome none of them tracks.
Why not solve the problem with an integrated dashboard?
A dashboard makes a problem visible, which helps, but visibility is not the same as responsibility. If nobody's goals, budget or authority depend on the downtime figure, it tends to be noted and passed over, since each function still has its own targets to meet. The post argues that the blind spot closes only when someone owns the outcome and has the authority to act on it.
How is a blind spot different from a known problem nobody fixes?
A known problem has been noticed and set aside, often because fixing it seems to cost more than it is worth. A blind spot has not been noticed at the level where it could be acted on, because no unit's measures or goals capture it. The distinction matters for the remedy: a known problem needs a decision, while a blind spot first needs a place in the structure where it can be seen and owned.
Where can I find a free MGT 805 Topic 5 sample paper?
The blind spot post and the reply to Daniel are printed here in full, with the day-by-day dryer case, each function's own standard and the authority question. Share the prompt from your section, and we will draft a free doctoral post and peer response around it.
Why does every function pass in MGT 805 Topic 5?
Service met its two-day response target, warranty decided within its six-day standard and parts kept a 94 percent fill rate. Each measure covers one step, so none captures the eleven days the farmer waited across all of them.