| Course | BUSI 504 Leading Organizational Change (BUSI504) |
|---|---|
| Module/Week | 2 |
| Assignment | Case Study 1 |
| Paper type | Case study analysis |
| Length | about 1,369 words, 5 double-spaced pages plus title page and references. Course guide: a case study of 4 to 5 pages in current APA format, not counting the cover page, abstract or references, with introductory and concluding paragraphs, headings and a biblical perspective with Scripture |
| Format | APA 7 student paper |
| Points | 100 |
| School | Liberty University Online |
| Program | MBA |
| Where it sits | Module/Week 2 in Liberty's published BUSI 504 course guide; current sections can differ |
| Updated | October 2026 |
Free sample paper for BUSI 504 Week 2
Refreshing a Culture: Theories of Change Implementation and Microsoft Under Satya Nadella
[Student Name]
School of Business, Liberty University
BUSI 504: Leading Organizational Change
Case Study 1
[Instructor Name]
[Date]
The textbook's end-of-chapter case is not public, so this sample applies the chapter's theories to a real, documented change, Microsoft after 2014, under guiding questions written to match the assignment; every source and the Scripture cited are real, and the requirements follow Liberty's public course guide for BUSI 504.
Refreshing a Culture: Theories of Change Implementation and Microsoft Under Satya Nadella
Introduction
When Satya Nadella became Microsoft's third chief executive in February 2014, the company was profitable but widely seen as having missed the shift to mobile computing, and its culture had a reputation for internal rivalry. Over the following five years Microsoft rebuilt its strategy around cloud services, opened itself to partners it had once treated as enemies and, by its leaders' account, changed how its people worked together (Nadella, 2017). In April 2019 its market value passed one trillion dollars. This paper analyzes the change using the theories of change implementation that Spector (2013) surveys in chapter 2. It argues that Microsoft's transformation is better explained by task-aligned, culture-first theories than by top-down, step-by-step models, and that its central lever was a change in how employees thought about learning.
What Created Dissatisfaction
Spector (2013) treats dissatisfaction with the status quo as the starting point of change, building on Lewin (1947), who argued that a group must be unfrozen before it can move. At Microsoft, the external facts were plain. The company's mobile phone strategy had failed; the Nokia handset business acquired in 2014 was written down by about $7.6 billion the following year, and thousands of jobs were cut. Competitors in cloud computing were growing quickly. Internally, employees and observers described a culture in which teams competed against one another and protected their own products.
Nadella (2017) describes his first months as a period of listening, meeting with employees, customers and partners to understand what had gone wrong before announcing a plan. That choice matters theoretically. Armenakis et al. (1993) argued that readiness depends on a clear discrepancy message; Nadella's listening tour gave him evidence that the discrepancy was felt inside the company, not only by analysts. He framed it as a question of the company's purpose, rewriting the mission as empowering every person and every organization on the planet to achieve more, which gave employees a reason to change that went beyond financial results.
Which Theory of Implementation Fits
Three theories from the chapter can be tested against the case. Lewin (1947) offers the simplest frame: unfreeze, move, refreeze. Microsoft clearly unfroze, but it never refroze in Lewin's sense; Nadella's message was that the company should keep learning permanently. Weick and Quinn (1999) distinguish episodic change, which happens in discrete breaks, from continuous change, an unbroken series of modest shifts whose effects accumulate, and Microsoft's leaders explicitly sought the second.
Kotter (1995) proposed an eight-step sequence beginning with a sense of urgency and ending with anchoring change in the culture. Several steps are visible at Microsoft, including a new vision and visible short-term wins such as releasing Office for the iPad in March 2014. But Kotter places culture at the end of the process, whereas Microsoft began with it. Nadella (2017) describes culture as the first priority, not the last.
The contrast with the period just before Nadella is instructive. In 2013, under Steve Ballmer, Microsoft announced a reorganization branded One Microsoft that redrew the company around functions from the top. The structure changed, but by most accounts the rivalry between product groups did not, which is the pattern Beer et al. (1990) predicted for programmatic change: a new chart and a new slogan, with behavior largely untouched. That earlier effort is not a failure so much as an incomplete step, since it left a structure Nadella could later fill with new working relationships.
The best fit is the task-alignment approach of Beer et al. (1990), co-written by the textbook's author. They argued that company-wide change programs launched from headquarters usually fail, and that successful change starts with the real work of units, redefining roles, responsibilities and relationships around specific business problems, with leaders creating a climate for change rather than dictating it. Microsoft's shift to the cloud forced exactly this kind of realignment: product groups that had once competed now had to build services that worked together on the Azure platform and across rival operating systems. The culture change was not a separate program; it was the way the new strategy was carried out.
Leadership and the Growth Mindset
Nadella (2017) credits much of the change to an idea from psychology, the distinction in Dweck (2006) between a fixed mindset, which treats ability as given, and a growth mindset, which treats ability as developed through effort and learning. He asked Microsoft to become a learn-it-all organization rather than a know-it-all one.
Research supports the idea that organizations, not only individuals, have mindsets. Murphy and Dweck (2010) found that when organizations signaled that they valued fixed talent, people presented themselves as naturally brilliant, whereas organizations that valued growth drew out effort and learning. Canning et al. (2020) surveyed employees at Fortune 1000 companies and found that employees who saw their companies as holding a growth mindset reported more collaboration, innovation and integrity, and greater trust in and commitment to their organizations. Those findings suggest why Nadella's emphasis was more than a slogan. A culture that rewards appearing smart discourages employees from admitting mistakes or sharing credit across teams, precisely the behaviors Microsoft's new strategy required.
Schein (2010) identified the strongest tools leaders have for embedding culture as the things they consistently notice and measure, their behavior in critical incidents and the way they allocate rewards and status. Nadella's public apology after an awkward remark about women's pay in 2014, and his use of the episode as a learning example, is a small but telling case of a leader modeling the mindset he asked others to adopt.
A Biblical Perspective on Renewal
Paul urged the Roman believers not to be shaped by the pattern of the world around them but to be transformed through the renewal of their minds (English Standard Version Bible, 2001/2016, Romans 12:2). The verse locates lasting change inside, in how people think, not only in external rules. Microsoft's leaders reached a similar conclusion in organizational terms: structure and strategy changed, but the change held because employees were asked to think differently about learning and failure. For a Christian manager, the parallel has limits, since Paul speaks of a spiritual renewal that no corporate program can produce. But the principle that behavior follows belief applies, and it warns leaders that changing an organization chart without changing how people understand their work rarely lasts. Scripture also speaks to the humility a growth mindset requires. Proverbs repeatedly contrasts the person who accepts correction with the one who despises it, and treats the willingness to learn as a mark of wisdom (Proverbs 12:1). A leader who admits error publicly, as Nadella did, gives employees permission to do the same.
Lessons for Other Organizations
Three lessons stand out. First, listening before announcing creates both the evidence for the discrepancy message and the trust needed to deliver it. Second, culture change succeeds more often when it is anchored in a concrete business problem, as Beer et al. (1990) argued, rather than launched as a standalone program. Third, leaders' own behavior, including how they respond to their mistakes, teaches the culture more effectively than any statement of values.
A fourth lesson is a caution. Microsoft had advantages most organizations lack: enormous cash reserves, a profitable core business that bought time, and a new market, cloud computing, large enough to absorb the company's ambitions. A smaller firm attempting the same culture-first change while losing money might not survive long enough for the culture to shift. Managers borrowing from the case should ask how much time their own organization has and plan accordingly, perhaps by pairing the culture message with faster, more visible wins than Microsoft needed.
Conclusion
Microsoft's transformation after 2014 shows the strengths and limits of the theories in Spector's second chapter. Lewin's model explains the unfreezing but not the continuous learning that followed, and Kotter's steps appear but in a different order. The task-alignment approach, which ties culture change to the real work of units, explains the case best, and research on organizational mindsets explains why the cultural lever mattered. The case also supports a biblical insight: durable change begins with a renewed mind. For managers studying the case, the most transferable idea is the least glamorous one, that a leader who spends the first months listening, and then ties a new way of thinking to a concrete business problem, has a better chance of lasting change than one who opens with a reorganization.
References
Armenakis, A. A., Harris, S. G., & Mossholder, K. W. (1993). Creating readiness for organizational change. Human Relations, 46(6), 681-703. https://doi.org/10.1177/001872679304600601
Beer, M., Eisenstat, R. A., & Spector, B. (1990). Why change programs don't produce change. Harvard Business Review, 68(6), 158-166.
Canning, E. A., Murphy, M. C., Emerson, K. T. U., Chatman, J. A., Dweck, C. S., & Kray, L. J. (2020). Cultures of genius at work: Organizational mindsets predict cultural norms, trust, and commitment. Personality and Social Psychology Bulletin, 46(4), 626-642. https://doi.org/10.1177/0146167219872473
Dweck, C. S. (2006). Mindset: The new psychology of success. Random House.
English Standard Version Bible. (2016). Crossway. (Original work published 2001)
Kotter, J. P. (1995). Leading change: Why transformation efforts fail. Harvard Business Review, 73(2), 59-67.
Lewin, K. (1947). Frontiers in group dynamics: Concept, method and reality in social science; social equilibria and social change. Human Relations, 1(1), 5-41. https://doi.org/10.1177/001872674700100103
Murphy, M. C., & Dweck, C. S. (2010). A culture of genius: How an organization's lay theory shapes people's cognition, affect, and behavior. Personality and Social Psychology Bulletin, 36(3), 283-296. https://doi.org/10.1177/0146167209347380
Nadella, S. (2017). Hit refresh: The quest to rediscover Microsoft's soul and imagine a better future for everyone. Harper Business.
Schein, E. H. (2010). Organizational culture and leadership (4th ed.). Jossey-Bass.
Spector, B. (2013). Implementing organizational change: Theory into practice (3rd ed.). Pearson.
Weick, K. E., & Quinn, R. E. (1999). Organizational change and development. Annual Review of Psychology, 50, 361-386. https://doi.org/10.1146/annurev.psych.50.1.361
What the BUSI 504 Week 2 instructions ask
Week two of BUSI 504 pairs the case discussion at the end of Spector's second chapter with a presentation, Quiz 1 and Case Study 1, worth 100 points. Students read the assigned case discussion and use its questions as a guideline. Every case study needs an introductory paragraph, a concluding paragraph and headings, plus a biblical perspective with Scripture relevant to the case. Case Studies 1 through 3 each run 4 to 5 pages of APA-formatted text, with the cover page, abstract and reference list excluded from that count. Chapter 2 surveys theories of effective change implementation, so the analysis should test the case against named theories rather than narrate it.
How this BUSI 504 Week 2 example is built
The paper opens with a short introduction that states its thesis, then answers each guiding question under its own heading. The first section identifies the sources of dissatisfaction at Microsoft in 2014 and connects them to unfreezing. The second compares the case with Lewin, Kotter and the task-alignment approach of Beer, Eisenstat and Spector, and argues the third fits best. The third section treats Nadella's leadership through research on organizational mindsets. A biblical perspective section on renewal of the mind follows, then lessons and a short conclusion. Each section cites research, and the case facts come from documented sources. The paper fits inside the 4- to 5-page range. A caution about how far the case can be generalized keeps the lessons honest.
BUSI 504 Week 2 grading rubric: where the points go
Each BUSI 504 case study is scored on its answers to the case discussion questions, apply the chapter's concepts, integrate a relevant biblical perspective with Scripture and follow the structural requirements: an introduction, headings, a conclusion and 4 to 5 pages of current APA format. Graders look for Spector's vocabulary used with care, theories of change implementation, programmatic versus task-aligned change, dissatisfaction, diagnosis and reinforcement, and that support claims with sources rather than general impressions. A biblical perspective tied to the case's specific challenge earns more than a verse added at the end. Clear organization under headings matters too.
BUSI 504 Week 2 help: mistakes that cost points
Read the case twice and list the facts that bear on each question before writing. Choose two or three theories from the chapter and test the case against each, saying where the fit is good and where it is weak. Use the theory's own vocabulary. Find two or three journal articles to support your analysis, and pick Scripture that speaks to the kind of change the organization faced. Write the introduction last, once you know your argument, and keep to 4 to 5 pages excluding the cover page and references. Leave time for Quiz 1, due the same week. A last pass pairing citations with references catches the most common APA deduction.
Related BUSI 504 sample papers
Other BUSI 504 weeks
- BUSI 504 Week 1: Forum 1: Readiness for Change
- BUSI 504 Week 3: Forum 2: Shared Diagnosis
- BUSI 504 Week 4: Case Study 2: Zappos and Holacracy
- BUSI 504 Week 5: Forum 3: Rewards and Reinforcement
- BUSI 504 Week 6: Case Study 3: Wells Fargo Sales
- BUSI 504 Week 7: Case Study 4: Interface Goes Green
- BUSI 504 Week 8: Forum 4: Greenwashing and Decoupling
More MBA sample papers
- BUSI 502 Week 2: Forum 2: Feedback and Succession
- BUSI 503 Week 2: Leadership Journal 1: Credibility
- BUSI 520 Week 2: MMGP Background: Liquid Death
- BUSI 530 Week 1: Forum 1: Shareholder Value Debate
BUSI 504 Week 2 questions, answered
What is BUSI 504 Case Study 1?
The first of four case studies, worth 100 points in Module/Week 2, answering the questions from the case discussion at the end of Spector's second chapter in 4 to 5 APA pages with Scripture.
Where can I find a free BUSI 504 Week 2 sample paper?
The full BUSI 504 Week 2 case study is on this page, analyzing Microsoft's culture change under Satya Nadella through theories of change implementation.
What is the difference between programmatic and task-aligned change?
Programmatic change rolls out company-wide programs from the top, while task-aligned change starts with the real work of units, redefining roles and relationships around specific business problems.
Why is Microsoft under Satya Nadella used as a change case?
It is a well-documented example of a large company changing its culture and strategy at once, moving from a competitive, internally divided culture toward a learning culture built around cloud services.
What else is due in BUSI 504 Module/Week 2?
Quiz 1, a timed open-book quiz of 50 multiple-choice questions on the first readings, worth 50 points and completed in 90 minutes.
Use it as a model, or ask for your own
This paper is an original model written by our desk for study. It is not a submitted student paper and not an official Liberty University document. Read it for structure and reasoning, then write your own to the instructions in your Canvas course. If you want a version built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
Ask for a custom BUSI 504 Week 2 sample · All BUSI 504 weeks · All courses