| Course | HCS 370 Organizational Behavior (HCS/370) |
|---|---|
| Week | 5 |
| Paper type | Organizational change plan |
| Length | about 1,011 words, 4 double-spaced pages plus title page and references |
| Format | APA 7 student paper |
| School | University of Phoenix |
| Program | BS in Health Administration |
| Updated | September 2026 |
Free sample paper for HCS 370 Week 5
When a Robot Joins the Clean Room: Leading a Hospital Pharmacy Through the Change to Automated IV Compounding
[Student Name]
University of Phoenix
HCS/370: Organizational Behavior
Week 5 Assignment
[Instructor Name]
[Date]
The hospital, the pharmacy department and the automation project are composites written for a model paper; change models come from the sources listed.
The composite hospital pharmacy department prepares about 1,100 IV doses a day. Most are routine: standard antibiotics, electrolyte bags and syringes for the intensive care unit. The hospital has approved a compounding robot that will prepare many of these batch doses, using barcode and weight checks at each step. Technicians heard about it through a rumor before any announcement. This paper plans how to lead the department through the change.
The Change
Within a year, the robot will prepare about 40% of IV doses. Technicians will still prepare patient-specific and complex doses, load and supervise the robot and handle exceptions. Pharmacists will verify the robot's work through its records.
Forces for Change
Safety: automated weight checks catch errors that visual checks can miss. Drug shortages: the robot can use vials efficiently. Workload: the department is short of technicians. Consistency: batch doses will be prepared the same way every time.
Forces Against Change
Fear of job loss among technicians. Distrust of the machine among some pharmacists. The cost, $1.2 million, which some leaders think could fund staff instead. The disruption of installation in a clean room that cannot close.
Lewin's Model
Lewin (1947) described change as moving a group from one quasi-stationary equilibrium to another, and his work is often summarized as three steps: unfreezing the current situation, moving to a new level and refreezing so the new behavior holds. The plan follows these phases.
Why Transformations Fail
Kotter (1995) identified errors that doom change efforts, among them too little urgency, a weak guiding coalition, a vision communicated too rarely, obstacles left standing, no early wins, celebrating before the work is finished and changes never rooted in the culture. Each phase of the plan guards against these errors.
Unfreezing
The director will share the department's own data: two dosing errors last year that reached patients, rising overtime and doses delayed by shortages. The message is not that technicians are failing but that the current system asks too much of them. A guiding coalition, including two respected senior technicians, a pharmacist skeptic, the IV room supervisor and the director, will shape the plan.
Addressing the Fear Directly
The biggest restraining force is fear of job loss. The hospital has committed that no technician will lose a job because of the robot; reductions will come only through attrition, which, with current turnover, will not be needed. Saying this plainly and in writing, before anything else, removes the fear that would otherwise turn every later message into a threat.
New Roles
Technicians will be trained as robot operators, a new step on the career ladder with a pay differential. Those who prefer manual compounding will focus on complex patient-specific doses, which require more skill.
Moving: Implementation
Installation in phases so the clean room keeps running. Training for all technicians in the robot's operation. A pilot with three dose types for six weeks, then expansion. The senior technicians on the coalition will be the first operators and trainers.
Short-Term Wins
The pilot will track errors caught by the robot's checks and minutes saved. Early results will be shared at huddles, with credit to the operators.
Communication Plan
Announcement by the director in person at all three shift meetings, followed by a written summary with the job security commitment. Monthly updates at huddles. A question box and open sessions with the vendor. Messages to nursing leaders about any changes in dose delivery times.
Resistance as Information
The pharmacist skeptic raised a real concern: what happens when the robot fails at 2 a.m.? The plan now includes a downtime procedure and cross-training so manual preparation can resume at once. Resistance improved the plan.
Connecting to Culture
The department's culture work matters here, because the assumptions a group has learned decide how it reads any new tool (Schein, 1990). A team that trusts leaders and feels safe speaking up will report robot problems instead of working around them.
Refreezing
New procedures replace old ones in policy. Robot operation is added to competency checks and performance reviews. Operators are recognized at the annual department meeting. Old manual batch processes are retired.
Involving Technicians in Design
Technicians will help decide which doses the robot prepares first, how exception doses are flagged and where the robot sits in the clean room. People support what they help create, and the technicians know the workflow's weak points better than the vendor. Two technicians will visit a hospital already using the same robot and report back to their peers.
Supporting People Through the Transition
Change creates stress even when it is welcome. Supervisors will check in individually with each technician during the first month of operation, and the department will add a temporary extra technician on each day shift during the pilot so no one is learning the robot while short-staffed.
Measures
Doses prepared by the robot, target 40% within a year. Compounding errors caught and reaching patients. Technician overtime. Technician satisfaction and turnover. Robot downtime and recovery time.
Budget and Resources
The robot's $1.2 million cost includes installation and a first year of service. The plan adds about $60,000 for training time, the temporary extra technician and the operator pay differential. Leaders who questioned the purchase will receive a one-year report comparing overtime savings, reduced vial waste and error trends against these costs.
What Could Go Wrong
If the robot underperforms, technicians may conclude that leaders chose a machine over them. The coalition will report problems honestly rather than defending the purchase, and the downtime procedure ensures patients are never waiting on a machine.
Avoiding Victory Too Soon
The director will not declare success at go-live. Measures will be reviewed at six and twelve months, and the coalition will stay together for a year.
Conclusion
Automation could have been announced as a cost-saving machine and met with fear. Led through unfreezing, moving and refreezing, with job security guaranteed, new roles created, resistance heard and early wins shared, the change becomes one technicians help shape and own.
References
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
Schein, E. H. (1990). Organizational culture. American Psychologist, 45(2), 109-119. https://doi.org/10.1037/0003-066X.45.2.109
What the HCS 370 Week 5 instructions ask
HCS 370 Week 5 usually asks students to analyze and plan an organizational change in health care. Some sections have used a worksheet on managing change. Prompts may cover types of change, forces for and against change, models such as Lewin's or Kotter's, resistance and how to address it, communication, the leader's role and sustaining change. Students may analyze a change in their own organization or a scenario. Length depends on the format, and worksheets often ask for short answers under set headings. Strong work names a specific change, identifies the forces and stakeholders involved, applies a change model step by step, addresses resistance respectfully and explains how the change will be sustained and measured.
How this HCS 370 Week 5 example is built
The sample begins with the announcement: a compounding robot will prepare most batch IV doses within a year. It lists forces for change, such as safety, drug shortages and technician turnover, and forces against, such as fear of job loss, distrust of the machine and cost. The three-step model structures the plan, and an eight-step account of why transformations fail adds detail to each phase. The resistance section treats technicians' fears as legitimate and responds with a no-layoff commitment and new roles. The communication plan names messages, messengers and timing. Anchoring the change through training, recognition and measures closes the paper, tying back to the department's culture work.
HCS 370 Week 5 grading rubric: where the points go
The change week is typically graded on the quality of the change plan. Faculty look for a clearly described change, analysis of driving and restraining forces, correct application of a change model, thoughtful treatment of resistance, a communication plan and measures for sustaining the change. Connecting the change to earlier course topics, such as motivation, teams and culture, shows integration. Evidence and recognized models strengthen the plan. Clear structure helps, and APA formatting and writing complete the grade. Plans that announce a change and expect compliance, treat resistance as a character flaw or stop at implementation without anchoring usually earn less than plans that bring people along and make the change stick.
HCS 370 Week 5 help: mistakes to avoid
A frequent weakness in HCS 370 Week 5 is treating resistance as a problem people have rather than information about the change. Ask what the resisters are worried about and whether they are right. Another is naming Lewin or Kotter without applying each step. Students also skip communication details; name the message, who delivers it and when. Address job security honestly if technology is involved. Link the change to what the course has covered: motivation, teams and culture all affect whether people accept change. Plan how the change will be anchored, since many changes fade within a year. Finally, include measures for both the change's goals and people's experience of it.
Related HCS 370 sample papers
Other HCS 370 week samples
- HCS 370 Week 1: Organizational Behavior Foundations
- HCS 370 Week 2: Perception and Motivation
- HCS 370 Week 3: Team Building
- HCS 370 Week 4: Positive Organizational Culture
More BS in Health Administration sample papers
- HCS 335 Week 5: Emerging Ethical Issues
- HCS 341 Week 5: Compensation, Benefits and Retention
- HCS 380 Week 5: Internal Controls and Accounting Ethics
- HCS 385 Week 5: Business Operations Presentation
HCS 370 Week 5 questions, answered
What does HCS/370 Week 5 usually ask for?
Many sections ask students to analyze and plan an organizational change in health care, including forces for and against change, a change model, resistance, communication and sustaining the change.
Where can I find a free HCS 370 Week 5 sample paper?
The pharmacy automation change plan above is free with margin notes. Tell us about your own change and a first paper on it is written free.
What is Lewin's three-step change model?
A model describing change as unfreezing existing behavior, moving to new behavior and refreezing it so the new way becomes stable.
Why do change efforts fail?
Leaders often underplay urgency, build too weak a coalition, rarely communicate the vision, leave obstacles in place, skip early wins, celebrate too soon and never root the change in the culture.
How should managers handle resistance to change?
By listening to concerns, explaining the reasons for change, involving people in design, addressing legitimate fears such as job security, providing training and recognizing early adopters.
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 University of Phoenix 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.
Request this one custom, free · All HCS 370 week samples · All courses