MGT 805 Topic 3 coordination cost quantification example

Designing Organizational Structures Grand Canyon University Free custom sample in 24 to 48h

This MGT 805 Topic 3 sample paper puts numbers on the coordination costs a functional structure creates at a composite agricultural equipment manufacturer. It was prepared for GCU MGT 805, Designing Organizational Structures, catalog code MGT-805, a DBA seminar on how firms divide and join their work. Fourteen standing cross-functional meetings a month use about 308 manager-hours. Thirty-eight decisions a quarter rise to the chief executive. A revised irrigation controller took 43 days to approve, 9 of them engineering work and 34 spent waiting for signatures. Galbraith's information-processing view explains the overload, lateral mechanisms are priced, and the paper recommends three product integrators with a defined decision range.

CourseMGT 805 Designing Organizational Structures
TopicTopic 3
Paper typeCoordination cost analysis
LengthAbout 1,230 words, 5 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramDBA
UpdatedOctober 2026

Free sample paper for MGT 805 Topic 3

1

The Bill Nobody Has Added Up: Quantifying the Coordination Costs of a Functional Structure in Meetings, Escalations and Waiting Days, and Pricing Galbraith's Lateral Remedies Against Them

[Author Name]

College of Doctoral Studies, Grand Canyon University

MGT-805: Designing Organizational Structures

Topic 3 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.

What this page is doingThe title claims the cost has never been measured and promises the measures and the remedies in turn. Coldwater Implement Company and every figure are an illustrative composite; the sources are real.
2

The Bill Nobody Has Added Up: Quantifying the Coordination Costs of a Functional Structure in Meetings, Escalations and Waiting Days, and Pricing Galbraith's Lateral Remedies Against Them

The Claim

Coldwater Implement Company is organized by function: engineering, manufacturing, sales and aftermarket service each report to the chief executive, and each serves three product lines. Every boundary in that structure creates coordination work, because decisions about a product require agreement among functions that answer to different heads. Managers at Coldwater describe this work as heavy and slow, but nobody has measured it. This paper argues that coordination is a cost the current structure incurs every month, measures three parts of that cost, and compares it with the cost of the mechanisms that could reduce it.

What this page is doingThe claim is stated as something measurable, which commits the paper to numbers instead of adjectives.
3

Measures and Sources

Three measures were chosen because each can be checked against a record. Manager-hours in standing cross-functional meetings come from the shared calendar system for the last six months. Escalations come from the chief executive's decision log, which the executive assistant has kept since last year and which records every item brought to the chief executive for a ruling and the functions involved. Elapsed time comes from the approval records for engineering change proposals, which show when each signature was given. Hours in informal coordination, such as hallway conversations and email, were not measured, so the totals below understate the cost.

The Totals

Table 1

Three Measured Coordination Costs Under the Functional Structure, Illustrative

MeasureAmountSource
Standing cross-functional meetings14 a month, about 308 manager-hoursCalendar system
Escalations to the chief executive38 a quarterDecision log
Cross-functional change approvalsMedian 31 days, 7 of them working timeApproval records

Table 1 summarizes the results. Fourteen standing cross-functional meetings are held each month, averaging two hours and eleven managers, for about 308 manager-hours a month, or roughly 3,700 a year. Thirty-eight decisions a quarter rise to the chief executive because no one below that level can settle a disagreement between functions. Engineering change proposals that need approval from more than one function took a median of 31 days from proposal to approval, of which a median of 7 days was engineering work.

What the Totals Mean in Money and Attention

The meeting hours can be priced. At an illustrative loaded cost of 95 dollars an hour for the managers involved, 3,700 hours a year cost about 350,000 dollars, before any preparation time is counted. The escalations cost a scarcer resource. If each of the 38 quarterly rulings takes the chief executive about two hours, including the briefings that precede it, roughly 300 hours a year of the most senior attention in the firm go to settling disputes between functions, many of them about engineering details the chief executive is poorly placed to judge. The waiting days are the largest cost and the hardest to price, because their effect appears as orders lost while a change waits. Dealers in two states reported losing irrigation orders to a rival with sensor-ready controllers, and every week of approval delay extended that exposure.

These three costs behave differently. Meeting hours are spread across many managers and are partly productive. Escalations concentrate the burden on one person. Waiting days fall on customers and dealers, outside the firm's own accounts, which is why the structure has never registered them.

One Decision Traced: The Irrigation Controller

A single case shows where the time goes. Last spring an irrigation engineer proposed revising the pivot controller so it could accept readings from soil-moisture sensors, a feature dealers said they were losing orders without. The engineering work took 9 days. The proposal then needed four signatures. Manufacturing signed after 11 days, having waited for its monthly change review. Sales signed after another 6 days, once the regional managers had been consulted. Aftermarket service took 9 days to confirm that field technicians could support the new part. Finally, the head of engineering, who signs every change that alters a part's cost, took a further 8 days after the others had signed. In all, 43 days passed from proposal to approval, 34 of them waiting. The signatures were obtained one at a time because each function's process assumed the others had already agreed.

No one acted badly. Each function followed a reasonable procedure. The delay came from the structure, which gave no one below the chief executive the authority to decide for the irrigation line as a whole.

What this page is doingThe traced case turns a median into a concrete sequence and shows that the delay comes from the structure rather than from individuals.
4

Galbraith's Information-Processing View

Galbraith (1974) argued that information-processing demands rise with task uncertainty: the less predictable the work, the more information decision makers must exchange while it is under way. A hierarchy of rules, plans and referral upward handles routine work well, but as uncertainty rises, exceptions multiply and the hierarchy becomes overloaded. The organization then has two broad options. It can reduce the information it needs to process, for example by creating self-contained units or accepting slack resources such as longer deadlines. Or it can increase its capacity to process information, through vertical information systems or lateral relations that let decisions be made where the information is.

Coldwater's measures fit that account. The 38 escalations a quarter are the hierarchy's overload made visible: exceptions that the rules cannot settle travel upward to the one person with authority over all functions. The uncertainty is uneven, however. Most escalations and most of the waiting involve irrigation and precision guidance, where products change in response to sensors, software and competitors. Grain handling, which changes slowly, generated few.

Lateral Mechanisms Ranked by Cost

Table 2

Lateral Mechanisms Against the Measured Coordination Costs

MechanismAdded cost (illustrative)Effect on measured costs
Direct contact rulesNegligibleLittle; already attempted informally
Liaison roles in each functionAbout 1.5 positionsFaster information, no added authority
Task force per major changeMeeting time onlyHelps single projects, not the flow
Product integrators with a defined decision rangeThree senior positions, about $570,000 a yearRemoves most escalations and waiting
MatrixDual reporting for about 60 staffHigh capacity, high conflict risk

Galbraith (1973) described a sequence of lateral mechanisms in increasing order of cost and capacity: direct contact between managers, liaison roles, temporary task forces, permanent teams, integrating roles and, at the extreme, a matrix. Table 2 compares the options most relevant to Coldwater.

The Understanding Objection

A fair objection is that coordinating time is not all waste: meetings build shared understanding across functions, and a structure without them might make faster decisions that are worse. The paper accepts this for meeting hours, which may well buy understanding and are not the main target. It does not accept it for escalations and waiting days. A decision referred to the chief executive because no one else can make it, and a proposal that waits 34 days for four sequential signatures, buy nothing that a decision made closer to the work would not also buy.

Recommendation

Coldwater should appoint three product integrators, one for each line, with a defined range of disputes they may settle without escalation, such as engineering changes within an agreed cost limit and the sequencing of product releases across functions. Lawrence and Lorsch (1967) found that high-performing firms in uncertain industries relied on integrating roles of this kind, staffed by people whose influence came from knowledge as much as from formal authority. On the measured costs, the integrators would be justified if they removed about half the escalations and cut median approval time below two weeks; the irrigation and guidance lines would be the place to test that first.

What this page is doingThe integrators come with a decision range and a test of success, so the remedy cannot become another meeting.
5

References

Galbraith, J. R. (1973). Designing complex organizations. Addison-Wesley.

Galbraith, J. R. (1974). Organization design: An information processing view. Interfaces, 4(3), 28-36. https://doi.org/10.1287/inte.4.3.28

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

MGT 805 Topic 3 instructions, in plain terms

Topic 3 in MGT-805 asks doctoral learners to examine the coordination that organizational boundaries require and to treat it as a cost. A paper meets the brief when it defines measurable proxies for coordination, gathers evidence from records, and analyzes the results through a recognized framework, most often Galbraith's information-processing view. Learners should trace at least one decision in detail to show where time is lost, compare remedies by cost and capacity, and recommend one with a clear scope. At doctoral level the paper should acknowledge what its measures miss, connect the remedy to research on integrating roles and answer the practitioner's objection that coordination time also builds understanding between departments.

Inside the MGT 805 Topic 3 example

Numbers stand in the finished paper where most papers put adjectives, all of them composite. Fourteen standing cross-functional meetings a month, averaging two hours and eleven managers each, consume about 308 manager-hours. Thirty-eight decisions a quarter rise to the chief executive because no one below can settle a dispute between functions. One case is traced in full: a revised irrigation controller took 43 days from proposal to approval, 9 of them engineering work and 34 spent waiting for four function heads to sign. The paper reads these figures through Galbraith's information-processing view, in which rising task uncertainty overloads the hierarchy and an organization must either reduce the information it needs or build lateral capacity. Lateral mechanisms are then ranked by cost, and the paper recommends product integrators of the kind Lawrence and Lorsch found in high-performing firms.

Where the marks sit in the MGT 805 Topic 3 rubric

Doctoral faculty reward a paper that measures rather than describes. An Excellent analysis defines each measure with its source, so meeting hours, escalations and waiting days can all be checked. Credit goes to tracing a single decision step by step and showing that the delay comes from the structure, not from individuals. The rubric values applying Galbraith's argument about uncertainty and processing capacity to the case, including which product lines generate the overload. Strong papers rank lateral mechanisms by cost before recommending one and avoid jumping to a matrix. The highest band separates the coordination costs that may buy understanding from those that buy nothing and gives integrators a defined decision range and a test.

Common MGT 805 Topic 3 mistakes, and how to avoid them

Coordination papers lose standing with doctoral readers when the burden is called heavy or slow and never counted, because an unmeasured cost cannot be weighed against a redesign. Counting meeting hours alone misses the larger costs in this case, the escalations and the waiting days, which a reader will look for. Invoking Galbraith only to say that information matters leaves the framework idle, since his argument ties task uncertainty to the processing capacity a structure must supply. Recommending a matrix as the first response skips cheaper lateral mechanisms that Galbraith places below it. Integrators proposed without any defined decision range become another meeting rather than a remedy. The understanding objection is the one a practitioner raises first, and a quantification that never answers it treats every coordinating hour as waste.

Get an MGT-805 Topic 3 example written to your instructions

Send the MGT-805 Topic 3 instructions and the rubric posted in your classroom, with any organization, data or case the assignment supplies. A custom example is written to those criteria, with coordination measured from named sources, one decision traced in full, Galbraith's mechanisms priced and the understanding objection answered, returned in 24 to 48 hours. The first one is free.

More MGT 805 papers and DBA samples

MGT 805 Topic 3 questions, answered

What is Galbraith's information-processing view?

Jay Galbraith argued that the greater the uncertainty in a task, the more information must be processed while doing it, and that rules, hierarchy and goals become overloaded as uncertainty rises. Organizations then either reduce the need for information, through slack resources or self-contained units, or increase their capacity to process it, through vertical information systems or lateral relations. The example prices both routes.

How can coordination cost be measured?

Through proxies that leave records: hours in cross-unit meetings, decisions escalated beyond the level where the work sits, and elapsed time between a proposal and its approval. None is complete alone. Hours capture effort, escalations capture overload at the top, and elapsed time captures the delay customers eventually feel. The example uses all three and states the source of each.

What were Lawrence and Lorsch's integrators?

In their study of firms in plastics, food and container industries, Paul Lawrence and Jay Lorsch found that high performers in uncertain environments combined high differentiation among departments with strong integration, often through individuals or departments whose job was to link them. Effective integrators drew influence from expertise and a balanced orientation rather than from rank alone. The example models its product integrators on that finding.

Where can I find a free MGT 805 Topic 3 sample paper?

This page holds the complete coordination cost paper: measures and sources, the totals table, the money and attention estimates, the irrigation controller trace, Galbraith's framework, the mechanism table and the integrator recommendation. Share your organization's records and a free analysis can be built from them.

Where did the 43 days go in MGT 805 Topic 3?

Engineering work took 9 days. The remaining 34 were spent waiting for four signatures obtained one at a time: manufacturing, sales, aftermarket service and finally the head of engineering.