| Course | MGT 805 Designing Organizational Structures |
|---|---|
| Topic | Topic 4 |
| Paper type | Matrix analysis paper |
| Length | About 1,170 words, 5 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for MGT 805 Topic 4
Twenty-Nine Disputes at One Intersection: A Matrix Strain Analysis at an Agricultural Equipment Manufacturer, Tested Against Davis and Lawrence's Three Conditions
[Author Name]
College of Doctoral Studies, Grand Canyon University
MGT-805: Designing Organizational Structures
Topic 4 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.
Twenty-Nine Disputes at One Intersection: A Matrix Strain Analysis at an Agricultural Equipment Manufacturer, Tested Against Davis and Lawrence's Three Conditions
The Strain in Figures
Table 1
Escalated Priority Conflicts in the Matrix's Second Year, Illustrative
| Manager pair | Disputes | Median days to resolve |
|---|---|---|
| Precision guidance and engineering | 19 | 13 |
| Irrigation and engineering | 6 | 10 |
| Product managers and sales | 4 | 9 |
| Total | 29 | 12 |
Two years ago Coldwater Implement Company, which builds grain dryers and bins, center-pivot irrigation and satellite steering systems, placed 64 engineers and sales staff under two managers each: their function head and a product line manager. The aim was to weigh technical and product priorities against each other rather than leave product results to the chief executive alone. The design is now under pressure. In its second year the matrix sent 29 priority conflicts to the chief operating officer, who took a median of 12 days to resolve each. Several managers have proposed returning to single reporting lines.
The conflict log shows where the strain sits. Of the 29 disputes, 19 involved the precision guidance product manager and the head of engineering, and most concerned engineers claimed at the same time by a guidance software release and by work for another line, such as a warranty fix on grain dryer controls. Six involved irrigation and engineering, and four involved sales. Grain handling's product manager was party to only three. The strain is concentrated at one intersection rather than spread across the grid.
Davis and Lawrence's Three Conditions
Table 2
Davis and Lawrence's Conditions by Product Line
| Condition | Precision guidance | Irrigation | Grain handling |
|---|---|---|---|
| Dual focus: technical and product pressures equally strong | Holds: fast software and hardware change, competing on features | Weak: product changes slowly | Absent: mature products |
| High information-processing load | Holds: frequent releases, field faults, sensor integration | Partial: some sensor work | Absent: annual model changes |
| Shared scarce resources | Holds: electronics engineers shared | Holds | Holds |
Davis and Lawrence (1977) argued that a matrix is justified only when three conditions hold together. First, there must be outside pressure for a dual focus, so that the organization must give equal weight to two dimensions, such as technical excellence and product results. Second, there must be pressure for high information-processing capacity, typically because the environment is uncertain and the work complex and interdependent. Third, there must be pressure to share scarce resources, so that dedicating people to each product would be too costly. Where any condition is missing, they argued, a simpler structure will usually do the job at lower cost.
Table 2 tests each condition for each product line.
What the Conditions Show
All three conditions hold for precision guidance. Its software and hardware change quickly, competitors win on features, field faults require rapid joint work between support and engineering, and it depends on electronics engineers the firm cannot afford to duplicate. For grain handling and irrigation, whose products change slowly, only the shared-resource condition clearly holds. The matrix therefore has a strong reason to exist for one product line and a weak one for the other two. That explains the conflict pattern. The intersection where the conditions are strongest is where the demands on the same engineers are most intense and most uncertain, so it generates the most conflict.
What the Strain Costs
The conflicts have costs beyond the chief operating officer's time. Interviews with 14 of the engineers caught in disputes found the same pattern: while a conflict waited for a ruling, they split their week between the two claims, so both the release and the warranty fix slipped. Two guidance releases in the second year shipped more than three weeks late, and in each case the delay began with an unresolved dispute over the same three engineers. Engineers also reported that they had learned to delay starting any task that might be contested, which protected them from wasted work but added a few days to almost every assignment. Turnover among the 64 matrix staff was 14 percent in the second year against 9 percent elsewhere in engineering, and exit interviews named conflicting instructions as a reason more often than pay. None of these costs proves the matrix wrong. They show what an unmanaged collision costs, and they set the baseline against which any remedy should be judged.
The Tension Is the Design
The matrix was adopted so that product and technical priorities would collide openly, and they do. A precision guidance release and a grain dryer warranty fix are both legitimate claims on an electronics engineer's week, and the matrix was designed so that neither the product manager nor the engineering head could settle such a question alone. Conflict at that intersection is the design working as intended, not a sign of poor execution. Recommendations to clarify reporting lines would remove the dual authority the design exists to create, and with it the reason for adopting the matrix.
A Collision With Nowhere to Happen
The problem lies elsewhere. The paired managers have no scheduled forum in which to settle priorities, no rule for breaking a tie and no shared goal that would make one outcome better for both. Each dispute therefore follows the only route available, upward to the chief operating officer, who must learn the details before ruling. Twelve days later, the engineer has often already been pulled in both directions. Galbraith (2009) argues that matrix designs succeed when the organization supplies the processes that make dual authority workable, including joint planning, shared metrics and clear decision rules, and that structure without them produces exactly this kind of escalation.
The Abolition Objection
The strongest objection holds that inherent conflict is a reason to abandon the matrix altogether. If the design produces disputes by construction, why keep it? The answer lies in Table 2. Removing the matrix entirely would also remove the dual focus precision guidance needs. Its product manager would lose any claim on engineering time, and the competing software features that drive guidance sales would again depend on the engineering head's judgment of priorities across all three lines. The conditions argue for narrowing the matrix, not ending it.
Remedy
Coldwater should keep dual reporting only for the engineers and sales staff who work on precision guidance, about 25 of the 64, and return irrigation and grain handling staff to single functional reporting, with product integrators coordinating those lines. For the remaining matrix, three changes are recommended. The guidance product manager and the head of engineering should meet weekly to settle engineer assignments for the coming two weeks, with the chief operating officer attending only when they cannot agree. They should share one goal, the guidance line's on-time release rate combined with engineering's defect rate. And a written tie-break rule should state that customer-facing faults take priority over planned releases.
Bartlett and Ghoshal (1990) argued that a matrix depends less on the chart than on managers who share a frame of mind, a common understanding of the organization's purpose and the habit of resolving differences directly. The forum, the shared goal and the rule are ways of building that frame between two specific managers, and the conflict log will show within two quarters whether they are working.
References
Bartlett, C. A., & Ghoshal, S. (1990). Matrix management: Not a structure, a frame of mind. Harvard Business Review, 68(4), 138-145.
Davis, S. M., & Lawrence, P. R. (1977). Matrix. Addison-Wesley.
Galbraith, J. R. (2009). Designing matrix organizations that actually work: How IBM, Procter & Gamble, and others design for success. Jossey-Bass.
The MGT-805 Topic 4 assignment instructions
In Topic 4, MGT-805 asks doctoral learners to evaluate a matrix structure in operation. Describing dual reporting and listing its known problems does not meet the brief. A paper should gather evidence of where strain occurs, test the design against the conditions the literature sets for a matrix, and explain whether conflict reflects failure or the design working as intended. Learners are expected to apply Davis and Lawrence's conditions unit by unit, draw on later work about what makes a matrix workable, and consider the argument for abandoning it. The recommendation should address both the scope of the matrix and the forums, goals and rules that let the paired managers resolve disputes without escalating them.
How the MGT-805 Topic 4 example is put together
The finished analysis opens with the strain in figures, all composite: in its second year the matrix sent 29 priority conflicts to the chief operating officer, a median of 12 days each, most of them engineers claimed at once by a precision guidance release and a grain handling warranty fix. Davis and Lawrence's three conditions are then checked: outside pressure for a dual focus, pressure for high information-processing capacity, and pressure to share scarce resources. All three hold for precision guidance engineering. For grain handling and irrigation, whose products change slowly, only the shared-resource condition holds. The tension, the analysis argues, is how two legitimate priorities meet, and the fault lies in giving it no forum. Bartlett and Ghoshal's argument that a matrix depends on managers' capability more than on the chart shapes the remedy.
Where the marks sit in the MGT 805 Topic 4 rubric
An Excellent matrix analysis starts from evidence of strain and locates it. The rubric rewards papers that group conflicts by manager pair and find where they concentrate, rather than treating the whole grid as troubled. Credit goes to applying the three Davis and Lawrence conditions to each product line in turn and using the result to decide where the matrix belongs. Faculty look for the argument that conflict between two legitimate priorities is the design's purpose, and for a diagnosis that points to the missing forum, goal and tie-break rule. Strong papers answer the abolition objection from the conditions table, and top marks go to remedies that narrow the matrix and equip its managers.
MGT 805 Topic 4 help before you submit
Matrix analyses cost themselves the most by blaming the strain on execution and recommending clearer reporting lines, which removes the dual authority the design exists to create. A paper asking whether the matrix is good or bad, with no test of the conditions that justify one, cannot say where it belongs. Citing Davis and Lawrence without applying their three conditions unit by unit leaves the citation decorative, and a doctoral reader checks it against the argument. Treating the whole grid as uniformly strained misses that the conflict log concentrates at one intersection. Some analyses end by abolishing the matrix and never answer why a dual focus was sought in the first place. Remedies limited to the chart, with no forum, goal or rule for the paired managers, leave the conflicts traveling upward exactly as before.
Get an MGT-805 Topic 4 example written to your instructions
Send the MGT-805 Topic 4 instructions, the rubric for your section and the organization or case the assignment names. We write a custom example to those criteria, with strain measured, the conditions for a matrix tested unit by unit, the tension read as design and the abandonment 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 5: Structural Blind Spot Dq Post
- 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 4: Analytics Routines Assessment
- DBA 965 Topic 4: Unsettled Questions Section
- MGT 825 Topic 4: Routine Decision Exposure Brief
- DBA 960 Topic 4: Fieldwork Departure Log
MGT 805 Topic 4 questions, answered
When is a matrix structure justified?
Stanley Davis and Paul Lawrence argued that a matrix makes sense when three conditions hold together: outside pressure for a dual focus, such as product and technical excellence; pressure for high information-processing capacity, usually from uncertain and complex tasks; and pressure to share scarce resources across units. Where only one holds, simpler structures usually serve. The example tests all three for each product line separately.
Why did Bartlett and Ghoshal call the matrix a frame of mind?
Christopher Bartlett and Sumantra Ghoshal observed multinationals whose formal matrices produced conflict, confusion and slow decisions, and argued that the capability to balance competing priorities had to be built into managers' shared vision, relationships and judgment rather than imposed through dual reporting. The example borrows that argument for its remedy, investing in the paired managers rather than redrawing lines.
Is matrix conflict a sign of failure?
Not by itself. A matrix is adopted so that two legitimate priorities are weighed against each other by the people responsible for each, and some conflict is evidence that the weighing is happening. Failure shows in how conflict gets resolved: slowly, by escalation, or by one side quietly winning every time. The example measures resolution time and asks where disputes are settled.
Where can I find a free MGT 805 Topic 4 sample paper?
You can read the whole matrix strain analysis here, including the conflict log, the conditions table, the cost of the strain, the abolition objection and the remedy that narrows the matrix. Tell us about the matrix in your case and a free analysis can be prepared for it.
Which product line meets all three matrix conditions in MGT 805 Topic 4?
Precision guidance. It faces strong technical and product pressures together, a high information-processing load from releases and field faults, and shares scarce electronics engineers. Grain handling and irrigation clearly meet only the shared-resource condition.