HA515 · Unit 9

HA515 Unit 9 cross-department change plan example

Leadership and Management in Health Care Purdue University Global Free custom sample in 24 to 48h

Inpatients at a composite 320-bed hospital wait a median of [three] hours between a CT order and the scan, and no single department owns that wait: imaging schedules, transport moves, nursing prepares. In the HA515 Unit 9 cross-department change plan shown here, the three managers get eight weeks, one shared measure and a short list of coordinating routines, drawing on Gittell's relational coordination research.

What this page holds

Eight weeks, three departments and one shared clock for inpatient CT: managerial and short by design, HA515's Unit 9 change plan rests on Gittell's relational coordination. Searches like "ha 515 unit 9 assignment example", "ha515 unit 9 sample" and "ha515 unit 9 example" land here.

What a finished HA515 Unit 9 cross-department change plan looks like

Four pages with a timeline and a responsibility table. The situation section maps the CT wait into four segments, order to scheduled slot, slot to transport request, request to arrival and arrival to scan, with the department controlling each. The plan section proposes four changes: a shared definition of the wait and a daily report all three managers receive, a transport request triggered automatically when imaging confirms a slot, a nurse readiness checklist completed before transport arrives, and a ten-minute joint review twice a week. A responsibility table assigns each change to a manager with a start week. The timeline runs eight weeks. Measurement closes the plan: the median wait by segment, weekly, with a balancing measure for outpatient CT delays.

How a HA515 Unit 9 example is structured

The plan is deliberately short in horizon and modest in ambition, and it says why: three peer managers can change routines within their own authority in weeks, without restructuring or a system-wide initiative. Gittell's relational coordination research, developed partly in surgical care, supplies the diagnosis. Coordination fails when departments lack shared goals, shared knowledge of one another's work and mutual respect, and when their communication is infrequent, late, inaccurate or aimed at blame. Each proposed change targets one of those dimensions: the shared measure creates a shared goal, the joint review builds shared knowledge, and the automatic trigger makes communication timely. Change-model stages and culture language are left out on purpose. What remains is a managerial core: named owners, start weeks, a measure reviewed on a set day and a week-eight decision to keep, adjust or drop each change.

One wait, four segments

The order-to-scan interval split into pieces, each with its owning department and a bracketed median, so that no manager is asked to fix time they do not control.

Seven dimensions of coordination

Gittell's shared goals, shared knowledge, mutual respect and frequent, timely, accurate, problem-solving communication, each rated for the three departments from interviews.

Four changes, four owners

A shared report, an automatic transport trigger, a readiness checklist and a twice-weekly review, each assigned to the manager whose department it alters.

Eight weeks on one page

Start weeks staggered so the measure exists before any routine changes, with the automatic trigger tested on two units first.

Keep, adjust or drop

At week eight each change is judged against its segment's median, while outpatient CT waits are watched so inpatient gains are not borrowed from them.

Where marks go in HA515 Unit 9

Cross-department change plans in this unit tend to go wrong in two opposite directions. Some propose sweeping transformation, new structures or culture change, that a department head could never authorize, and read as wishful. Others list tasks with no reasoning about why coordination failed. Credit generally follows a plan scaled to the authority of the people carrying it out, grounded in a diagnosis, and assigned to named owners with dates and measures. A framework applied to the coordination problem specifically, rather than a generic change model recited, is what many instructors want to see. A balancing measure, showing that one department's improvement does not simply move delay elsewhere, marks a well-considered plan. Evaluation points and decision rules tend to lift the strongest submissions.

Get a HA515 Unit 9 example written to your instructions

List the departments your case or workplace involves and where the handoff breaks down, then add the Unit 9 prompt and rubric. The free first plan returns in 24-48h, scaled to what the managers involved can authorize, with owners, start weeks and a measure for every change.

HA515 Unit 9 questions, answered

Should a change plan use Kotter or Lewin?

If the prompt requires a change model, yes, applied to the plan's actual steps. Many cross-department problems, though, are coordination failures rather than transformation efforts, and a framework built for coordination fits them better. Explaining why the chosen framework suits the problem earns more credit than reciting stages that do not match it.

How long should the plan's timeline be?

Long enough to see an effect and short enough to hold attention, which for routine changes is often six to twelve weeks. Staggered start dates help, so the measure is in place before changes begin. A long timeline with vague phases usually signals that the plan's scope exceeds what its owners control.

What makes a good balancing measure?

A figure that would reveal whether improvement in one place caused harm elsewhere. If inpatient scans get faster, outpatient waits might grow; if transport arrives sooner, nurses might be rushed. Choosing one balancing measure and tracking it on the same schedule shows the plan was designed with the whole hospital in view rather than one department's figures.