| Course | MLDR 6905 Capstone: A Case for Leaders as Change Agents |
|---|---|
| Week | Week 4 |
| Paper type | Organizational context |
| Length | About 820 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | MS in Leadership |
| Updated | October 2026 |
Free sample paper for MLDR 6905 Week 4
Where This Change Would Succeed or Fail: Formal Authority, a Self-Funding Budget, the Memory of an Abandoned Consolidation and the Informal Network at a Four-Campus Community College
Student Name
Walden University
MLDR 6905: Capstone: A Case for Leaders as Change Agents
Instructor Name
Month Day, Year
Where This Change Would Succeed or Fail: Formal Authority, a Self-Funding Budget, the Memory of an Abandoned Consolidation and the Informal Network at a Four-Campus Community College
Formal Authority
Continuing education at Cedar Hollow Community College sits under a district dean of workforce and continuing education, who reports to the college's vice president for academic affairs. Each of the four campuses has a continuing education director. The directors report to the dean for budget and programs, but they also report to their own campus presidents for space, staffing and local priorities. This dual line means that the dean can propose consolidation, but a campus president can slow it by withholding space or objecting to staff transfers. The author, a program manager on the Main campus, reports to the Main campus director and has no formal authority over the other three offices.
Money
The division funds itself. Last year fees and employer training contracts together produced roughly $6.2 million, and any surplus supports new programs; any shortfall comes out of next year's offerings. This has a direct consequence for consolidation: a change that slows registration or delays employer invoices costs revenue within weeks, not years. The earlier attempt at centralization coincided with a drop in fall noncredit enrollment that staff still connect to it, whether or not it caused the drop. Any shared-services unit would need to keep registration turnaround and invoice timing at least as good as now from its first week.
History
Six years ago, the college moved noncredit registration for all campuses to the Main campus office over a single summer. In the first fall term, learners were placed in wrong sections, several employer cohorts were split across two invoices and the Linden campus's walk-in learners were told to call a number on the Main campus. The change was reversed after one term. The official explanation at the time was a software problem. Staff remember it differently. Clerks on the other campuses describe being told about the change two weeks before it happened, and two directors describe it as a Main campus decision made without them. Ford et al. (2008) argue that resistance is partly a response to how change agents behave, including broken agreements and poor communication; the memory of the earlier attempt is less about centralization than about how it was done.
The Informal Network
The formal chart does not show who staff turn to when something goes wrong. Based on the author's own observation over four years, and on a short set of questions asked of eleven staff across the four offices about whom they ask for help with registration and billing problems, the informal network looks quite different from the formal one.
Two features stand out. The Main campus registration specialist, a clerk with no supervisory role, is the person every office calls when the system fails; she is the most central person in the network. And the Linden director, who opposes consolidation, is trusted beyond her own campus. Battilana and Casciaro (2012) found that change agents who bridge disconnected groups are better placed to push through changes that depart from established practice. The author's position is only a partial bridge. The registration specialist and the Linden director are the people whose support or opposition would carry most weight.
Table 1
Who Staff Ask for Help With Registration and Billing Problems
| Person | Formal role | Asked by staff at | Position in network | |
|---|---|---|---|
| Registration specialist, Main campus | Clerk | All four campuses | Central; the person everyone calls | |
| Linden campus director | Director | Linden, one suburban campus | Trusted by rural and some suburban staff | |
| Suburban campus director (opposed) | Director | Own campus only | Cohesive local group | |
| Business office liaison | Finance staff | Main, both suburban campuses | Bridges continuing education and finance | |
| Author | Program manager | Main campus, one suburban campus | Partial bridge | |
Composite college. Based on the author's observation and informal questions to eleven staff; not a formal network survey.
Conditions Any Shared-Services Unit Would Have to Meet
The context implies five conditions for the change to last. First, registration turnaround and invoice timing must not worsen in the first term, because the division's budget cannot absorb a drop in revenue. Second, the change must be built with the campus directors, not announced to them, because the earlier failure is remembered as a Main campus decision. Third, every campus must keep a staffed place where learners can get help in person, especially Linden. Fourth, the Main campus registration specialist must be involved early, because staff will judge the unit by whether she trusts it. Fifth, the change must proceed in visible steps, each of which can be stopped, so that no single failure repeats the earlier collapse. Oreg et al. (2011), reviewing six decades of research on reactions to change, found that how change is introduced, including participation and communication, consistently shaped how people responded to it. These conditions become tests for the stakeholder case and the implementation plan.
References
Battilana, J., & Casciaro, T. (2012). Change agents, networks, and institutions: A contingency theory of organizational change. Academy of Management Journal, 55(2), 381-398. https://doi.org/10.5465/amj.2009.0891
Ford, J. D., Ford, L. W., & D'Amelio, A. (2008). Resistance to change: The rest of the story. Academy of Management Review, 33(2), 362-377. https://doi.org/10.5465/amr.2008.31193235
Oreg, S., Vakola, M., & Armenakis, A. (2011). Change recipients' reactions to organizational change: A 60-year review of quantitative studies. Journal of Applied Behavioral Science, 47(4), 461-524. https://doi.org/10.1177/0021886310396550
The Walden MLDR 6905 Week 4 instructions
Week 4 asks you to describe the organizational context in which your change would happen. Chart the formal lines of authority and show who can approve or block the change. Explain how money works in the unit affected and how the change could disrupt it. Recount any history of similar changes and how people remember it, which may differ from the official account. Sketch the informal network, based on whom people actually turn to for help, and be clear about how you gathered that information. Close with the conditions any version of the change would have to meet to last, since the rest of your capstone will be tested against them.
Inside the MLDR 6905 Week 4 example
The context opens with the formal structure and its dual reporting lines. A money section explains the self-funding budget and the speed at which slower registration costs revenue. A history section recounts the earlier centralization and staff memories of it, citing Ford and colleagues on how change agents' conduct produces resistance. A network section presents a table of five people, their formal roles, who asks them for help and their network position, with a note on method, citing Battilana and Casciaro. A closing section lists five conditions for a lasting change, citing Oreg and colleagues on how introduction shapes reactions. The network table's note explains that it reflects observation and informal questions, not a formal survey, which keeps the claim honest.
MLDR 6905 Week 4 rubric: what earns full marks
Context analyses score well when they show where the change could break. A clear account of formal authority, including who can block the change, earns credit. Attention to how money flows shows practical judgment. A history section that separates the official account from what people remember demonstrates insight. An informal network sketch, with its method stated honestly, is weighted heavily because it reveals influence the formal chart hides. Conditions for lasting change, derived from the analysis, connect the context to the rest of the capstone. Analyses that describe the organization in general terms, rely only on the organization chart or omit earlier failures tend to earn less. Faculty also look for conditions that the later plan can be tested against directly.
MLDR 6905 Week 4 help: mistakes that cost marks
Draw your organization's formal chart for the unit concerned, then mark everyone who could say no to your change. Find out how the unit is funded and ask what happens to that money if the change goes badly for a month. Ask a few long-serving colleagues what they remember about similar changes, and write down their words. For the informal network, ask several people whom they go to when something breaks, and note the names that keep coming up. Students often skip the informal network or present guesses as findings. Say how you gathered the information. When your notes on who-asks-whom feel too scattered to draw, our writers can help you shape them into a sketch.
Get a MLDR 6905 Week 4 example written to your instructions
Attach the organizational context prompt and rubric, with a general description of where your change would take hold; leave internal documents out. Authority lines, money, relevant history and an informal network sketched by role, ending in conditions the change must meet, come back within 24 to 48 hours, free the first time. Campuses and roles here are composite, drawn from no single college.
More MLDR 6905 papers and MS in Leadership samples
- MLDR 6905 Week 1: Capstone Topic Proposal
- MLDR 6905 Week 2: Capstone Position Statement
- MLDR 6905 Week 3: Question-Led Literature Section
- MLDR 6905 Week 5: Stakeholder Case
- MLDR 6905 Week 6: Ninety-Day Implementation Plan
- MLDR 6905 Week 7: Change Measurement Plan
- MLDR 6905 Week 8: Capstone Progress Post
- MLDR 6905 Week 9: Program Integration Pass
- MLDR 6905 Week 10: Capstone Coherence Edit
- MLDR 6905 Week 11: Leadership Change Capstone
- MLDR 6010 Week 4: Performance Appraisal Write-Up
- MLDR 6175 Week 4: Conflict Style Diagnosis
MLDR 6905 Week 4 questions, answered
Where can I find a free MLDR 6905 Week 4 sample paper?
The organizational context paper, network table included, is free to read below.
What four parts does the MLDR 6905 Week 4 context cover?
Formal authority, money, history and the informal network.
Who is most central in the informal network?
A Main campus registration clerk whom every office calls when registration fails.
How do staff remember the earlier centralization?
As a Main campus decision made without the other campuses, announced two weeks before it happened.
What does the section close with?
Five conditions any shared-services unit would have to meet to last.