DDBA 8521 Week 2 Rejected Change Diagnostic Example

Seminar in Change Management Walden University Free custom sample in 24 to 48h

This DDBA 8521 Week 2 rejected change diagnostic example reads a refusal back into the organization that suffered it. Walden DDBA 8521 treats rejection as informative, and the case follows a composite Midwest transit agency of about 380 bus operators whose optimized scheduling program drew 61 grievances and a union vote to refuse its assignments within two months. The diagnosis shows that operators, not managers, effectively controlled work assignments through the quarterly seniority pick; that the contract's work selection article required operators to select runs, which the program's limited swaps did not satisfy; and that operators' objections were ambivalent, welcoming less overtime for juniors. Ford and colleagues, Piderit and Weick and Quinn guide a DBA diagnosis that points toward offering optimized runs within the pick.

CourseDDBA 8521 Seminar in Change Management
WeekWeek 2
Paper typeDiagnostic case
LengthAbout 800 words, 5 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramDoctor of Business Administration (DBA)
UpdatedOctober 2026

Free sample paper for DDBA 8521 Week 2

1

What the Operators' Refusal Reveals: A Diagnostic Case Reading a Transit Agency's Rejected Bus Scheduling Program Back Into the Agency, Showing Who Really Controls Work Assignments and Which Contract Clause the Program Ignored

Student Name

Walden University

DDBA 8521: Seminar in Change Management

Instructor Name

Month Day, Year

What this page is doingThe title treats the refusal as evidence about the agency rather than as a failure to be overcome, which is the stance of the case.
2

What the Operators' Refusal Reveals: A Diagnostic Case Reading a Transit Agency's Rejected Bus Scheduling Program Back Into the Agency, Showing Who Really Controls Work Assignments and Which Contract Clause the Program Ignored

The Rejection

In 2025, a composite regional transit agency in the Midwest with about 380 bus operators introduced a software program that builds operators' weekly work assignments, called runs, by optimizing for fewer split shifts and lower overtime. Under the old process, operators chose runs four times a year in order of seniority, a process called the pick. The new program proposed assignments and allowed operators to swap within limits. After two months, operators had filed 61 grievances, the union local voted to refuse program-built assignments and management suspended the program. The agency's leadership described the outcome as resistance to change. This case reads the refusal back into the agency to ask what it reveals about how the agency actually runs.

What this page is doingThe case states what was rejected and how, before reading the rejection for what it reveals.
3

Who Actually Controls Work Assignments

The agency's organization chart places scheduling under the director of operations, who reports to the general manager. On paper, management assigns work. In practice, the pick gave operators substantial control: a 20-year operator could choose a straight eight-hour daytime run on a single route, while newer operators took split shifts, nights and weekends. Seniority choice was the main reward for years of service. The program shifted control from operators' choices to an optimization the scheduling office ran. Operators did not object to software; they objected to losing a right they had earned. Ford et al. (2008) argued that what change agents call resistance often reflects legitimate concerns and the relationship between agents and recipients, and that labeling it resistance can hide useful information. Here the information was about where control over work really sat.

The Clause the Program Ignored

The union contract's article on work selection states that runs "shall be selected by operators in seniority order" at each pick. The program's swap feature allowed choice only among assignments the program had already built. The union's grievance argued that this replaced selection with assignment, contrary to the article. The agency's legal counsel had reviewed the program for compliance with federal rules on hours of service, but not against the contract's work selection article. The program was designed around the formal authority shown on the organization chart, not the contractual authority operators held.

What this page is doingThe case identifies the specific rule the change collided with, because a diagnosis that names only attitudes cannot be acted on.
4

What the Operators' Stated Objections Reveal

The grievances and a union newsletter named three objections: loss of seniority choice, unpredictable split shifts for senior operators and the sense that "the computer" now decided their lives. Piderit (2000) showed that people's reactions to a change can pull in several directions at once, in what they think, feel and intend, rather than amounting to plain opposition. Several operators wrote that the program's assignments reduced overtime for junior colleagues, which they supported, while objecting to losing their own choice. That ambivalence suggests a redesign that kept seniority choice among program-built runs, with the program constructing better runs for operators to pick from, might have been accepted.

What the Refusal Says About the Agency

The refusal reveals three things. Authority over work is shared between management and operators through the contract, not held by management alone. The seniority pick is a central part of the agency's reward system, and changing it changes what a long career at the agency is worth. And the agency's change process reviewed technical and regulatory compliance but not labor agreements, a gap that will matter for any future change touching work rules. Weick and Quinn (1999) observed that changes introduced as discrete episodes often collide with the continuous, embedded arrangements through which an organization actually works; the quarterly pick is one of those arrangements.

How the Diagnosis Was Built

The diagnosis draws on four sources. The first is the 61 grievances, read in full and coded by the objection each raised. The second is the union contract, especially its article on work selection and the side letters that interpret it. The third is the project file for the scheduling program, including the legal review memo and the vendor's configuration notes. The fourth is interviews with the director of operations, two dispatchers, the union local's vice president and five operators chosen across seniority levels. Each claim in the case rests on at least two of these sources. Where they disagreed, for example on whether operators had been consulted before launch, the case reports both accounts: management recalled two information sessions, while the union recalled being told of the program after the vendor was chosen.

Implications

Before reintroducing the program, the agency should negotiate with the union over how optimized runs could be offered within the pick. The diagnosis suggests that operators might accept a program that builds runs if they still choose among them.

References

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

Piderit, S. K. (2000). Rethinking resistance and recognizing ambivalence: A multidimensional view of attitudes toward an organizational change. Academy of Management Review, 25(4), 783-794. https://doi.org/10.5465/amr.2000.3707722

Weick, K. E., & Quinn, R. E. (1999). Organizational change and development. Annual Review of Psychology, 50(1), 361-386. https://doi.org/10.1146/annurev.psych.50.1.361

The Walden DDBA 8521 Week 2 instructions

Week 2 asks you to diagnose an organization through a change that it rejected. Describe the change and how it was rejected, with evidence such as grievances, votes or withdrawal. Then read the rejection back into the organization: who actually controls the work the change affected, which formal rules or agreements the change collided with and what the stated objections reveal about how the organization really runs. Distinguish the organization chart from actual authority. Treat objections as information rather than as resistance to be overcome, and look for ambivalence within them. Explain how you built the diagnosis from multiple sources. Close with implications for any future attempt at the change. Cite research on resistance and on how change meets established routines. Four to five pages is typical.

How this DDBA 8521 Week 2 example is built

The case describes the program's optimization, the old quarterly seniority pick, the grievances and the suspension. A section on control contrasts the organization chart with the pick, which let senior operators choose straight daytime runs and made choice the reward for long service, drawing on Ford and colleagues' point that what looks like resistance carries information. A section on the contract quotes the work selection article and notes that legal review covered federal hours rules but not the contract. Piderit's ambivalence explains operators who supported less overtime for juniors while objecting to losing their choice. A methods section names grievances, contract, project file and interviews, with disagreements reported. Weick and Quinn frame the pick as an embedded routine, and the case suggests negotiating optimized runs into the pick.

DDBA 8521 Week 2 rubric: what earns full marks

Instructors judge the diagnosis by what it reveals about the organization, not by how thoroughly it recounts the rejection. Distinguishing formal authority from actual control over work earns substantial credit. Naming the specific rule or agreement the change ignored, with its wording, turns a vague account of resistance into an actionable finding. Reading objections for ambivalence, rather than treating them as uniform opposition, shows depth. A diagnosis built from several sources, with disagreements between them reported, is more credible than one built from management's account. Implications should follow directly from the diagnosis. Sources should support the reframing of resistance as information.

DDBA 8521 Week 2 help from the desk

The trap in this assignment is writing about why people resist change in general. Focus on this organization: who decides the work the change touched, what written rules govern it and what objections people actually raised. Read grievances and complaints in full and sort them by what they object to. Look for objections that support part of the change; they point to a redesign. Check whether the change was reviewed against labor agreements or other binding rules. Collect at least two sources for each claim. A tutor can help you organize grievances or complaints into categories. Quote the exact clause or rule the change collided with.

Get a DDBA 8521 Week 2 example written to your instructions

Include the Week 2 case prompt and rubric, and name the program if the instructor assigned one. A diagnostic case that reads one refusal back into the organization is ready in 24 to 48 hours, with nothing to pay for the first. Grievance files or personnel records stay with you; public sources and described events suffice.

More DDBA 8521 papers and DBA samples

DDBA 8521 Week 2 questions, answered

Where can I find a free DDBA 8521 Week 2 sample paper?

The full rejected change diagnostic for Week 2 can be read further down this page at no cost.

What change does the DDBA 8521 Week 2 case examine?

A transit agency's software program that built bus operators' weekly work assignments instead of letting them choose by seniority.

Who actually controlled work assignments?

Operators, through a quarterly seniority pick that made choosing runs the reward for long service.

Which contract clause did the program ignore?

The article requiring that runs be selected by operators in seniority order at each pick.

What do the operators' objections reveal?

Ambivalence: many supported less overtime for junior colleagues while objecting to losing their own choice.