MCO 7400 Module 6 Stakeholder Communication in the CrowdStrike Outage Example

Reviewed by Edgar Pennington, MBA Thomas Edison State University Updated October 2026

This MCO 7400 Module 6 sample paper deals with communication strategies for stakeholder issues in managerial report form for Management Communications. Prepared for TESU's Master of Business Administration (MBA), it examines CrowdStrike's July 19, 2024 faulty software update, which Microsoft estimated crashed about 8.5 million Windows devices and which Delta Air Lines blamed for about 7,000 canceled flights. Using situational crisis communication theory, it judges the apology, technical bulletins, root cause report, customer commitment packages and the public dispute with Delta, assesses communication with each stakeholder group in a table, and recommends a four-part plan for software vendors, with trade-offs. MCO-7400 is the code to look for.

CourseMCO-7400 Management Communications
ModuleModule 6
Paper typeWritten assignment: communication strategies for stakeholder issues
LengthAbout 878 words, 6 pages
FormatAPA 7 student paper
SchoolThomas Edison State University
ProgramMaster of Business Administration
UpdatedOctober 2026

Free sample paper for MCO 7400 Module 6

1

Eight and a Half Million Blue Screens: Stakeholder Communication After the CrowdStrike Outage

Student Name

Master of Business Administration, Thomas Edison State University

MCO-7400: Management Communications

Mentor Name

Month Day, Year

What this page is doingThe title refers to Microsoft's estimate of Windows devices affected on July 19, 2024. Facts come from government, company and SEC sources.
2

Eight and a Half Million Blue Screens: Stakeholder Communication After the CrowdStrike Outage

Purpose

This report analyzes how CrowdStrike, a cybersecurity company, communicated with its stakeholders after a faulty software update caused a global computer outage on July 19, 2024. It applies situational crisis communication theory and the course text's guidance on stakeholder issues to judge what worked and what did not, and it recommends a stakeholder communication plan that any software vendor could prepare in advance.

What Happened

Early on July 19, CrowdStrike released a content configuration update for its Falcon sensor that caused certain Windows systems to crash (CrowdStrike Holdings, 2025). Microsoft estimated that about 8.5 million Windows devices were affected, under 1 percent of all Windows machines, but the concentration of CrowdStrike's software among large organizations meant that airlines, hospitals, banks, emergency services and retailers were disrupted worldwide (Congressional Research Service, 2024). Delta Air Lines canceled about 7,000 flights over several days and later sued CrowdStrike, estimating its losses at more than $500 million. CrowdStrike's annual report describes lawsuits, government inquiries, longer sales cycles and customer commitment packages offering discounts and additional modules, while noting that it maintained high gross retention.

A Framework for Crisis Response

Coombs (2007) developed situational crisis communication theory to match responses to the threat a crisis poses to reputation. The theory first classifies crises by how much responsibility stakeholders attribute to the organization: victim crises, such as natural disasters, carry little; accidental crises, such as technical errors, carry some; and preventable crises, such as known risks ignored, carry the most. Crisis history and a poor prior reputation intensify attributions. Response strategies range from denial through diminishment, which minimizes responsibility or harm, to rebuilding, which includes apology and compensation. The theory advises that every response begin with instructing information, guidance on staying safe or fixing the problem, and adjusting information, which addresses their concerns.

Clampitt (2016) adds that stakeholder issues are rarely managed with a single message. Different groups need different information through different channels, and the organization's credibility depends on consistency across all of them.

Applying the Framework

Although the cause was a technical error, the scale of harm and the fact that the update came from CrowdStrike's own release process pushed stakeholders toward seeing the crisis as preventable, which calls for a rebuilding response. CrowdStrike's response contained several elements the theory recommends. It identified the faulty update quickly and published remediation steps the same day, which served as instructing information for the information technology staff who had to repair machines one by one. Its chief executive apologized publicly. It later published a technical root cause analysis and described changes to its testing and release practices, and it offered customers commitment packages, a form of compensation.

Other elements fit the theory less well. Fixing affected machines often required manual work at each device, so instructing information alone could not end the harm quickly, and many end users saw only blue screens and news reports. The public dispute with Delta, in which the companies traded accusations through lawyers' letters and the press, shifted part of the message toward diminishment at the moment the company sought to rebuild trust. A rebuilding strategy is weakened when it appears selective.

Stakeholder by Stakeholder

A stakeholder view shows where communication succeeded and where it was thin.

StakeholderMain concernChannel usedAssessment
IT teams at customersHow to restore systems nowTechnical bulletins, support portalStrong: fast, specific, updated
Customer executivesWill this happen again; what will you doExecutive calls, root cause report, commitment packagesAdequate: substantive but slower
Affected publicWhy services failedMedia interviews, social postsThin: little direct communication
InvestorsFinancial and legal exposureEarnings calls, SEC filingsAdequate: risks disclosed
GovernmentCritical infrastructure riskCongressional testimony, agency contactAdequate: engaged when called

Recommendations for a Vendor's Stakeholder Plan

A software vendor whose product runs inside other organizations' critical systems should prepare four things before a crisis. First, prewritten instructing templates for technical staff, ready to publish within an hour with remediation steps, and a status page updated on a fixed schedule. Second, an executive message and briefing for customer leaders within 24 hours that takes responsibility, explains what is known and states when the root cause will be published. Third, a principle for disputes: when a large customer seeks damages, communicate through private channels while the incident is still being resolved, and keep public statements focused on fixing harm. Fourth, a commitment to publish a root cause analysis and the changes made to prevent recurrence, followed by a progress update months later.

Trade-offs

Taking responsibility quickly can increase legal exposure, and lawyers often advise caution. Restraint in public disputes may look weak to investors when a customer makes large claims. Coombs's theory and the evidence of reputational harm suggest that for a firm whose product is trust, the cost of appearing defensive is greater.

Conclusion

CrowdStrike's technical communication with the people repairing systems was strong, and its apology and root cause report followed the rebuilding strategy that situational crisis communication theory recommends. The public dispute with a major customer and thin communication with the broader public weakened that strategy. A plan prepared in advance, stakeholder by stakeholder, would help any vendor respond consistently when its own error becomes everyone's problem.

References

Clampitt, P. G. (2016). Communicating for managerial effectiveness: Challenges, strategies, solutions (6th ed.). SAGE.

Congressional Research Service. (2024). The July 19th global IT outages (CRS Insight No. IN12392).

Coombs, W. T. (2007). Protecting organization reputations during a crisis: The development and application of situational crisis communication theory. Corporate Reputation Review, 10(3), 163-176. https://doi.org/10.1057/palgrave.crr.1550049

CrowdStrike Holdings. (2025). Annual report on Form 10-K for the fiscal year ended January 31, 2025. U.S. Securities and Exchange Commission.

Reading the MCO 7400 Module 6 assignment instructions

Stakeholder communication is Module 6's subject in MCO-7400, and this managerial report applies it; the public syllabus does not fix which modules carry the three written assignments. Expect a scenario or real case in which an organization must communicate with several groups at once. Identify the stakeholders and what each needs, apply a framework such as situational crisis communication theory, and judge the organization's actual messages with evidence. Recommend a plan that assigns messages and channels to each group, and explain its trade-offs. Use credible sources, such as government reports and company filings, for facts, and cite them in APA style. Organize the plan by stakeholder or by phase so a reader can find each group quickly.

How this MCO 7400 Module 6 example is built

The report establishes the facts from government and company sources before analyzing anything, which keeps the critique fair. The framework is explained in enough detail to be applied, including crisis types and response strategies, and the application credits what worked before identifying what did not. A table evaluates communication with each stakeholder group, which shows the course's point that stakeholder issues require several coordinated messages. The recommendations are specific enough to prepare in advance, with timelines, and the trade-offs section addresses legal caution honestly. The conclusion balances strengths and weaknesses in three sentences. Each judgment points back to a documented statement or filing.

Reading the MCO 7400 Module 6 grading rubric

A rubric score out of a hundred applies to stakeholder reports. They look for a clear identification of stakeholders and their concerns, accurate application of a crisis or stakeholder framework, and evaluation grounded in documented messages rather than impressions. Balanced judgment, noting both strengths and weaknesses, earns credit. Recommendations should be specific, organized by stakeholder or phase, and realistic about legal and business constraints. Managerial format with headings and a table, accurate facts from credible sources, correct APA citations and concise prose complete the grade. Reports that only summarize news coverage of a crisis tend to lose points on analysis. Fairness in judging a real company, with evidence for each claim, also earns credit from mentors.

MCO 7400 Module 6 help: mistakes that cost marks

Students often retell a crisis in detail but analyze the communication only briefly. Others criticize a company's response without a framework, so the judgment reads as opinion. Our writers can prepare MCO 7400 stakeholder and crisis communication reports on the case or scenario your module assigns. Start by listing every stakeholder group and what each needed to know in the first day, week and month. Classify the crisis using situational crisis communication theory and identify the recommended response. Then compare that with what the organization actually said, using its own statements and filings, and plan what it should have prepared in advance. Keep the timeline of the crisis short so the analysis has room.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official Thomas Edison State University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.

More MCO 7400 and Master of Business Administration sample papers

MCO 7400 Module 6 questions, answered

Where can I find a free MCO 7400 Module 6 sample paper?

The report above analyzes CrowdStrike's stakeholder communication after the July 2024 outage using situational crisis communication theory, with a stakeholder table and a vendor plan.

What is situational crisis communication theory?

Coombs's framework for matching crisis responses to how much responsibility stakeholders attribute to an organization, from denial and diminishment to rebuilding through apology and compensation.

What is instructing information?

Information that tells stakeholders how to protect themselves or fix a problem during a crisis, which every response should provide first.

How many devices did the CrowdStrike outage affect?

Microsoft estimated about 8.5 million Windows devices, less than 1 percent of all Windows machines, but many were in critical services.

Why tailor messages to each stakeholder group?

Different groups need different information through different channels, and consistency across all of them protects credibility.