| Course | BUS FPX 4802 Change Management |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Change case diagnosis |
| Length | About 1,080 words, 6 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Business |
| Updated | September 2026 |
Free sample paper for BUS FPX 4802 Assessment 1
Diagnosing a Change at an HVAC Service Company: Evidence Before the Proposal, Workarounds Read as Evidence, Who Loses Named Early, Readiness Assessed Honestly, and the Last Attempt Accounted For
Student Name
Capella University
BUS FPX 4802: Change Management
Instructor Name
Month Day, Year
The Organization
Summit Comfort Services, a composite heating and air conditioning service company, employs 46 field technicians, 4 dispatchers, 3 billing clerks, and a small management team, and serves about 9,000 residential and light commercial customers in one metropolitan area. Technicians receive their daily jobs from dispatchers by phone and text, fill out paper work orders at each job, and turn in the paper at the office at the end of the day or, often, the end of the week. Billing clerks type the work orders into the billing system. The owner, Greg Thompson, wants to adopt a mobile field service app that would put jobs, customer history, parts, and invoicing on each technician's phone.
Evidence Before Proposal
Before proposing anything, the diagnosis gathered evidence of what is actually wrong. Records for the last six months show that the average time from job completion to invoice is 9.4 days, and 6% of completed jobs were never billed at all, which the controller estimates at about 210,000 dollars of lost revenue a year. Parts used on jobs are recorded on paper and often missing, so the parts inventory is counted as short by about 38,000 dollars at each quarterly count. Customer complaints about technicians arriving without knowing the equipment history averaged 22 a month. Dispatchers handle about 140 calls and texts a day from technicians asking for addresses, codes, and customer notes. Armenakis et al. (1993) argue that readiness begins with a discrepancy people recognize between where the organization is and where it needs to be; these figures make the discrepancy concrete. The case for change is the unbilled jobs and missing parts, not the app.
Workarounds Treated as Evidence
Workarounds are treated as evidence, because they show what people need and where the current process fails. Many technicians already photograph their paper work orders and text the photos to a dispatcher so billing can start before the paper arrives. Several senior technicians keep personal notebooks of customer equipment details, because the office's paper files are hard to reach from the field. Dispatchers have built a shared spreadsheet of gate codes and pet warnings. Billing clerks call technicians to read unclear handwriting. Each workaround points to a need the new system should meet: fast billing, equipment history in the field, customer notes, and legible records. They also show that staff are already trying to solve the problem, which is a strength to build on.
Who Loses Named Early
Some people will lose something, and naming them early allows the change to address their losses instead of discovering them as resistance. Dispatchers lose some of their role as the information hub, since technicians will look up details themselves, and they may fear for their jobs. Senior technicians lose the advantage of their private notebooks, which made them valuable and hard to replace, and some will lose the flexibility of turning in paperwork at the end of the week. Billing clerks lose most of their data entry work. Technicians may feel monitored if the app records job times and locations. Naming these losses does not mean the change should stop; it means the plan must say what happens to each group.
Readiness Assessed Honestly
Readiness is assessed honestly, not assumed. Weiner (2009) describes organizational readiness as shared commitment to the change and shared belief in the capacity to carry it out. Commitment is mixed. A short survey of all 46 technicians found that 70% agreed billing and parts tracking were serious problems, but only 41% believed an app would help, and technicians over 50 were much less likely to agree. Capacity is also mixed. All technicians have smartphones, but 11 use basic phones for work that cannot run the app, and cellular coverage is poor in two outlying areas. The office has no staff member with experience configuring software. Management has not set aside time for training during the summer peak, when technicians work long hours. On balance, Summit is ready to act on billing and parts but not yet ready for a full rollout in summer.
Previous Attempts Accounted For
Summit tried this once before. In 2021, it bought tablets for technicians to use with a different app. The rollout happened in July, training was one hour at a Saturday meeting, the tablets were fragile and several broke in the first month, and the app required a signal to save work, so jobs in basements and rural areas were lost. Within three months most technicians had returned to paper, and management quietly dropped the project. Technicians remember this, and several said in the survey that "this will go the same way." No one ever explained to them why the project ended, which left the impression that management had simply lost interest. The diagnosis treats that history as a central fact. Any new attempt must show what is different: the season chosen, the training offered, phones instead of tablets, and an app that works offline and syncs later. The last failed rollout is the first thing technicians will think of, so it must be the first thing the plan answers.
What the Diagnosis Supports
The evidence supports a change focused on the problems staff already recognize: faster billing, complete parts records, and customer history in the field. It supports a rollout outside the summer peak, starting in late fall with a pilot group that includes skeptical senior technicians. It requires an app with offline mode, company-provided phones for the 11 technicians who need them, and redefined roles for dispatchers and billing clerks that are stated before rollout, not after. It does not support the owner's original plan to switch everyone over in June. The diagnosis recommends that the owner meet with dispatchers and billing clerks first, before any announcement, to explain what their redefined roles will be.
Conclusion
At Summit, unbilled jobs, missing parts, and constant calls to dispatch show a real problem, and existing workarounds show what technicians need. Dispatchers, senior technicians, and billing clerks each stand to lose something, readiness is mixed, and the failed 2021 tablet attempt shapes how staff will receive a new one. The diagnosis supports a fall pilot with an offline-capable app, provided phones, and roles redefined in advance.
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
Weiner, B. J. (2009). A theory of organizational readiness for change. Implementation Science, 4, Article 67.
Reading the BUS-FPX4802 Assessment 1 instructions
The first assessment in BUS FPX 4802 asks you to diagnose the need for change in an organization before designing it. You describe the organization and the current way of working, present evidence of the problem with figures and sources, identify the root cause rather than the symptom, name the groups affected and what each would gain or lose, assess readiness for change using a model such as Kotter's or Lewin's and learn from previous change attempts. The diagnosis should come before any solution, since a change proposed without evidence is hard to defend. Change management research and the organization's own data support the diagnosis.
Inside the BUS FPX 4802 Assessment 1 example
Evidence, current state, affected groups, readiness. The opening states what is failing with figures and where they came from, since a change proposed without evidence cannot be defended to anybody who liked the old way. A current state block describes how the work is done now, including any workaround people invented, which is usually the most honest evidence available. An affected groups block names who does what differently afterward and what each gains or loses. A readiness block assesses whether the organization can absorb this now, given what else is happening. A short block covers what has been tried before and why it failed, since a second attempt inherits the first one's reputation. The closing states the case for changing now rather than later.
BUS FPX 4802 Assessment 1 scoring guide: what Distinguished looks like
Capella's scoring guide rates the evidence, the description of current practice, the root cause, the affected groups, the readiness assessment and the use of history. Evidence reaches Distinguished when the problem is shown in figures with sources, such as missed appointments per week. Current practice scores higher when workarounds are described and treated as information. The root cause earns credit when separated from symptoms. Affected groups are judged on whether losers are named along with winners, since resistance comes from real losses. Readiness should be assessed honestly with evidence, not assumed. The previous attempt should be explained, including why it failed. Proficient diagnoses identify a problem; Distinguished ones show why the organization has not solved it yet and what that means for the change.
Common BUS FPX 4802 Assessment 1 mistakes, and how to avoid them
Change diagnoses often jump straight to a solution, such as buying new software, and then describe the problem to fit it. Another weakness is treating workarounds as bad habits rather than signs of where the system fails. Only the benefits of change are described, so the people who stand to lose status or convenience are invisible until they resist. Readiness is declared high without evidence. The last attempt at change is ignored, though staff remember it well and will judge the new one by it. Figures are missing, so the problem rests on anecdotes. Interviewing or observing the people doing the work, and recording each workaround with the gap it covers, gives the diagnosis evidence that managers and staff will both accept.
Get a BUS FPX 4802 Assessment 1 example written to your instructions
Send the Assessment 1 instructions and the scoring guide from your BUS FPX 4802 courseroom, plus the organization and change your version specifies. We write a custom example against those exact criteria and return it in 24 to 48 hours. The first custom sample is free, and naming who loses at the diagnosis stage is what makes everything after it credible. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More BUS FPX 4802 papers and BS in Business samples
- BUS FPX 4802 Assessment 2: Transition and Communication Plan
- BUS FPX 4802 Assessment 3: Adoption Measurement Plan
- BUS FPX 4993 Assessment 1: Problem Definition and Scope
- BUS FPX 4801 Assessment 1: Ethical Dilemma Case
- ECO FPX 1150 Assessment 1: Budget Analysis
- BUS FPX 4070 Assessment 1: Cost of Capital Working
BUS FPX 4802 Assessment 1 questions, answered
How do I diagnose a cause rather than restate a symptom?
Ask what has to be the case for the symptom to keep occurring, then go and check whether it is. Delays might come from a queue, from an approval nobody is available to give, or from work arriving in batches. Each leaves a different trace in the records, and the trace is what separates a diagnosis from a hunch.
What if nobody loses anything?
Look harder, because somebody usually does. Even a clearly beneficial change costs people the competence they had built in the old system, which is a real loss and a real source of resistance. A diagnosis finding no cost anywhere has generally not talked to the people doing the work.
How much evidence is enough?
Enough that somebody defending the current arrangement would have to engage with it. One clear figure with a source beats several impressions. Where hard data does not exist, describe what you observed and how, since a stated method turns an observation into evidence a reader can weigh.
Where can I find a free BUS FPX 4802 Assessment 1 sample paper?
The full diagnosis of the HVAC company's dispatch problem is on this page, with evidence before the proposal, workarounds read as evidence, who loses named early, honest readiness and the last attempt accounted for.
Why study workarounds in BUS FPX 4802 Assessment 1?
Workarounds show where the official process fails and what people need. They also warn that a change removing them without meeting the need will be resisted.