| Course | MGMT 8009M Organizational Decision Making and Judgment |
|---|---|
| Week | Week 8 |
| Paper type | Information flow memo |
| Length | About 740 words, 4 pages |
| Format | Memo, APA 7 citations |
| School | Walden University |
| Program | PhD in Management |
| Updated | October 2026 |
Free sample paper for MGMT 8009M Week 8
Memorandum
To: Chief Operating Officer, Ashby Components
From: Quality Systems Analyst
Date: November 17, 2025
Re: How the rear caliper noise complaints lost their detail on the way to the executive committee, and a raw-count channel to fix it
The Finding
Between May and August 2025, dealers reported a grinding noise from the rear brake caliper we supply for two light truck programs. Our field engineer logged 43 complaints, most from vehicles under 6,000 miles. In September the executive committee's dashboard showed the caliper line as "warranty claims within normal range." Both statements were accurate. The memo explains how the first became the second, and argues that the loss came from our report formats rather than from any person's choice.
One Fact, Four Versions
[after]
Reading across the table, the mileage pattern disappears at the second level, the count at the third and the signal itself at the fourth, where the dashboard measured warranty cost paid rather than complaints received. Because most complaints were on vehicles still under dealer goodwill, few had become paid claims.
Table 1
The Same Complaint Data at Four Levels of Reporting
| Level | Document | What it showed | What was gone | |
|---|---|---|---|
| Field engineer | Case log, updated daily | 43 complaints with VIN, mileage, dealer and symptom; 31 under 6,000 miles | Nothing | |
| Quality manager | Weekly summary | "Caliper noise: 43 cases YTD, investigating" | Mileage pattern, dealer spread | |
| Operations vice president | Monthly operations slide | Caliper program rated amber, "noise issue under investigation" | Count, trend | |
| Executive committee | Monthly dashboard | Caliper warranty cost within plan, rated green | Complaint signal entirely; dashboard tracks paid claims, not complaints | |
Conclusions Travel, Evidence Stays
March and Simon (1958) described uncertainty absorption: when information passes through an organization, the people who see the raw evidence draw inferences from it and pass along the inferences, and those who receive them can no longer examine the evidence themselves. The receivers must rely on the summarizer's judgment. The first two losses fit this description closely. The quality manager had seen every case and summarized them as "investigating," a fair judgment. The vice president received the judgment, not the cases, and had no means to notice that early-mileage failures suggest a manufacturing or design cause rather than wear.
Bad News, Tested Hop by Hop
Tesser and Rosen (1975) reviewed evidence that people are reluctant to transmit bad news, even when they bear no responsibility for it. It would be easy to assume this explains the whole chain. The record does not support that at every level. At the first hop, the field engineer escalated within a day of the tenth complaint and wrote plainly. At the second, the weekly summary was brief but not softened. At the third, the evidence is stronger: the slide template allowed only green, amber or red with a six-word comment, and the operations vice president's earlier slides show amber used for issues expected to resolve within a quarter. Rating the caliper amber was consistent with that practice and avoided red, which triggers a review. The reluctance mechanism appears to operate where the format makes bad news costly to report.
Silence Without a Silencer
Morrison and Milliken (2000) described organizational silence as a collective condition in which employees withhold information about problems, shaped by shared beliefs and by structures that discourage upward communication. Their account fits this case only in its structural aspect. No one here decided to hold back. Each person reported what their format asked for, and each format had less room than the one before. The result, an executive committee unaware of a pattern that the field engineer had documented in detail, looks like silence even though everyone spoke.
A Channel That Skips the Summaries
The proposal is a raw-count appendix to the executive committee's dashboard: one page listing, for each product line, complaints received in the month, the share under 6,000 miles and the change from the prior month, generated directly from the field case log without editing. Quality engineering would own the appendix. It adds one page to the pack and, based on similar appendices elsewhere, about five minutes to the committee's review. The dashboard would also add complaints received beside warranty cost paid, so a gap between the two would be visible.
What the Memo Does Not Propose
It does not propose that managers escalate more aggressively or that the dashboard be rebuilt. Both would address people or formats in general. The appendix addresses the one fact, raw counts by mileage, that every summary in this case removed.
References
March, J. G., & Simon, H. A. (1958). Organizations. Wiley.
Morrison, E. W., & Milliken, F. J. (2000). Organizational silence: A barrier to change and development in a pluralistic world. Academy of Management Review, 25(4), 706-725. https://doi.org/10.5465/amr.2000.3707697
Tesser, A., & Rosen, S. (1975). The reluctance to transmit bad news. Advances in Experimental Social Psychology, 8, 193-232. https://doi.org/10.1016/S0065-2601(08)60251-8
MGMT 8009M Week 8 instructions, in plain terms
In Week 8 you write a memo tracing how information about a problem moved, or failed to move, through an organization. Expect to follow one fact through several levels of reporting and show what each version contained and lost. Then apply the readings on information flow, typically uncertainty absorption, reluctance to transmit bad news and organizational silence, testing each at the points where it fits rather than assuming one explains all. The memo should argue whether the loss was built into formats and incentives or chosen by individuals. Close with a proposal for a channel or format change, with an owner and a cost. Most of these memos run four or five pages.
Inside the MGMT 8009M Week 8 example
The memo is addressed to the chief operating officer. It opens with the complaints and the green dashboard line. A table shows the case log, the weekly summary, the monthly slide and the dashboard, with what each showed and what was gone. Uncertainty absorption explains the first two losses, as each author passed on a judgment and not the evidence. The bad-news mechanism is tested at each hop and found weak at the first, stronger where a slide template allowed only three colors and a short comment. Organizational silence frames the conclusion that everyone spoke and the signal still disappeared. A one-page raw-count appendix by product line, plus complaints beside paid claims on the dashboard, is proposed with ownership and timing.
Where the marks sit in the MGMT 8009M Week 8 rubric
Precision about each loss is what graders value most. Saying that bad news did not reach the top restates the premise; showing which detail vanished at which step, and in whose document, makes the analysis checkable. Credit concentrates in the exhibit and in matching each loss to a mechanism. Uncertainty absorption is credited when shown in a specific summary. The bad-news account earns when tested level by level and found stronger in some places than others. Concluding that one manager suppressed the data abandons the course's premise and forfeits synthesis credit. The proposal is assessed for ownership and its cost to the committee's attention, alongside memo form and APA for MGMT 8009M Week 8.
MGMT 8009M Week 8 help: mistakes that cost marks
Students often describe the chain in general terms and never show the documents. Collect the actual versions of the information at each level: logs, summaries, slides and dashboards. Put them side by side and note exactly what disappears where. For each loss, ask whether the format, the incentive or a person's choice explains it, and be willing to find different answers at different levels. Do not assume bad news was hidden; check. Keep the proposal narrow enough to adopt next month. If you lack access to the real documents, a composite can work if clearly labeled. The brake complaint memo above shows the full form, and a tutor can sketch the exhibit's columns with you.
Get a MGMT 8009M Week 8 example written to your instructions
Share the Week 8 memo prompt and rubric along with the reporting chain you want traced, described by level, and an information flow memo with its exhibit is delivered in 24-48h, free for a first request. Templates and report formats can be summarized by structure, which is usually all the argument needs.
More MGMT 8009M papers and PhD in Management samples
- MGMT 8009M Week 1: Process Critique
- MGMT 8009M Week 2: Bounded Rationality Memo
- MGMT 8009M Week 3: Framing Analysis
- MGMT 8009M Week 4: Heuristics Review
- MGMT 8009M Week 5: Decision Reconstruction
- MGMT 8009M Week 6: Group Process Case
- MGMT 8009M Week 7: Escalation Case
- MGMT 8009M Week 9: Incentive Analysis
- MGMT 8009M Week 10: Debiasing Design
- MGMT 8009M Week 11: Decision Audit
- MGMT 8003M Week 8: Program Orientation Paper
MGMT 8009M Week 8 questions, answered
Where can I find a free MGMT 8009M Week 8 sample paper?
The brake complaint information flow memo on this page is the complete Week 8 sample with its exhibit.
What is uncertainty absorption in MGMT 8009M?
March and Simon's term for how people pass on inferences from evidence rather than the evidence, so receivers cannot check it.
Where did the complaint signal disappear in the Week 8 case?
Mileage dropped at the weekly summary, the count at the monthly slide and the signal at the dashboard, which tracked paid claims.
Did anyone hide the bad news in the sample case?
The memo finds weak evidence of that at most levels; the formats removed detail even though everyone reported.
What does the Week 8 memo propose?
A monthly raw-count appendix taken directly from the field log, plus complaints received shown beside warranty cost.