Change management strategies, communicating change vision, overcoming resistance, and sustaining change. Covers managing transitions during reorganizations and technology implementations.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
Change management strategies, communicating change vision, overcoming resistance, and sustaining change. Covers managing transitions during reorganizations and technology implementations.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamDevelop and communicate clear change vision and goals
Change arrives in a building department in recognizable forms: a new permitting system replaces the one staff have used for fifteen years; plan review moves from paper sets to electronic submittals and on-screen markup; a new code edition makes every inspector's tabbed, annotated book last cycle's book; a reorganization merges the building division with fire prevention; remote video inspections arrive. Building Department Administration (5th Edition) treats this as the normal condition of the job — change is now a constant, and change management is an important aspect of supervision. The same text is blunt about the human starting point: employees dread and resent changes in familiar and satisfying routines, even when the changes will result in improvements. Changes are perceived as threats, and obsolete routines are often adhered to because they provide a sense of security. A leader who expects staff to greet an improvement as an improvement has misread the audience.
The work begins before the announcement, with a case for change staff can examine. It has two components. The first is data: plan-review turnaround against published service goals, re-inspection rates, the growing counter queue. The BDA text notes that departmental performance is measured in quality (error rate), timeliness, and customer satisfaction — frame the case in those terms, the terms the department already uses to judge itself. The second is the problem made concrete: the addition permit that sat three weeks because the one paper set was on someone's desk. Data proves the problem exists; the story makes people feel it. This is the logic behind what John Kotter called a sense of urgency: a shared, honest recognition — established before any solution is on the table — that the current way of working cannot continue.
The second early move is assembling the people who will carry the change — a guiding coalition, in Kotter's language. The instinct is to staff a project team with supervisors and technology enthusiasts; that team lacks the one thing a change effort cannot do without, credibility with the people who must actually change. Every department has informal leaders — the senior inspector others call with hard questions, the examiner the counter staff trust — whose standing does not depend on title. A respected front-line skeptic invited in early, asked to poke holes in the plan, and visibly listened to leaves fingerprints on the eventual rollout. The BDA text makes the parallel point about decisions generally: prepare interested parties before announcing policy decisions, and discuss them with affected parties beforehand, because they may hold facts and advice that improve the decision itself.
Only then is the vision worth writing, and it should be a picture, not a slogan. "Modernize the department" commits no one to anything. "Twelve months from now, a contractor submits plans from their office, checks status without calling, and our ten-day residential turnaround target is met nine cycles out of ten" is a vision staff can see themselves inside, with goals measurable in the department's own currency: turnaround days, error rates, counter wait times. A vision stated this way also defines the boundary of the change — the beginning of answering the question every employee silently asks: what does this mean for me?
A building official preparing to replace a legacy permit system spends a month building the case before saying the word "software." She pulls two years of turnaround data against the department's service goals, documents the hours staff spend retrieving paper files, and collects three incidents where a lost file delayed an approval. She asks the most experienced permit technician — a known skeptic after the last failed upgrade — to join the selection team and write the list of everything the old system does that the new one must not break. The announcement opens with the data, the stories, and the technician's requirements list, and closes with a one-paragraph picture of the working day eighteen months out. The first question from the floor is "when do we start," not "why are we doing this."
The most common error is announcing the solution before establishing the problem — staff hear a verdict, not a proposal, and the BDA text observes that professionals detest having a new policy shoved down their throats without consultation. A second is a vision that is only a slogan, with no measurable goals. A third is a coalition made entirely of managers and enthusiasts, which guarantees the skeptics organize themselves informally instead. The corrections: build the case from the department's own performance data plus concrete stories; write the vision as an observable, measurable future state; and recruit respected front-line skeptics early enough that their input can still change the plan.
Address employee concerns and resistance to change
Resistance in a building department has specific, rational roots, and each calls for a different response. The most important is that expertise feels devalued. A plans examiner with twenty-five years of paper review has mastered things a new system makes irrelevant — the tabbed code books, the markup conventions, the ability to fan out four sheets at once. Electronic review does not just change the tools; it appears to erase the visible difference between twenty-five years of experience and two. The leader's answer: the judgment is the expertise, the tools only the container — and the rollout must let senior staff demonstrate that judgment quickly. A second root is workload fear: staff must learn a new system while the permit queue keeps arriving. A third is history: a rollout announced with fanfare, half-implemented, and quietly abandoned taught staff that waiting out change is a winning strategy. None of these is insubordination; each is a concern that can be answered — or ignored until it hardens into opposition.
An organization does not change; individuals do, one at a time. Prosci's ADKAR model captures this: each person must become aware of why the change is needed, develop their own desire to take part, acquire knowledge of how to work the new way, build the practiced ability to actually do it, and receive reinforcement so it holds. The value of the framing is diagnostic. An examiner who understands the reasons but refuses has a desire problem — more explanation will not fix it, but involvement might. An inspector who is enthusiastic but reverts under deadline pressure has an ability problem, and needs practice time, not persuasion. A leader who applies one remedy — usually another all-staff email — to every form of resistance will watch it fail.
Communication through the change is a discipline, not an event. The BDA text is direct: employees resent being kept in the dark and want the whys as well as the whats — with accurate, timely notice and reasons, they have time to adjust and adapt. State plainly what is changing and what is not; most anxiety attaches to imagined losses, and "no positions are being eliminated; inspection districts do not change" removes more fear than any enthusiasm about the new system. Give honest timelines — a firmly promised date that slips costs more credibility than an honest range. Repeat the message in multiple channels — staff meetings, one-on-ones, written summaries — because a message delivered once was effectively not delivered. Build listening loops: communication, the BDA text notes, is by definition a two-way process, and feedback loops confirm the message received is the one sent. The grapevine will be active regardless; address rumors openly and candidly — countering gossip with facts is the single best way to defeat it.
Finally, convert concern into ownership. The BDA text offers a telling example: plans examiners who resist being told to review plans over the counter may, when asked instead to brainstorm ways of expediting reviews for customers, arrive at over-the-counter review as their own solution — and if they own the solution, they are more likely to embrace it. The same mechanism applies to any rollout: let staff design the intake checklist, choose the training sequence, decide which permit types convert first. People rarely sabotage what they helped build.
A department's transition from paper to electronic plan review nearly fails in its second month. The two most senior examiners — who between them train every new hire — review on-screen slowly, grumble audibly, and print submittals to review on paper "for accuracy," and younger staff begin following their lead. Rather than issue a directive, the official meets each examiner privately, acknowledges the change has been hardest on the people with the deepest paper expertise, and asks one of them to lead the pilot: define the on-screen markup standards, identify what the old process did better, and present findings to the staff. Her report is candid — two real software-configuration deficiencies get fixed at her insistence — and her name is on the markup standard the department adopts. Within a quarter, the printing stops, not because it was forbidden, but because the department's most credible skeptic now owns part of the system.
The classic error is treating resistance as a discipline problem — an attitude to correct rather than a concern to diagnose — which drives it underground. A second is one-time communication: a single memo or kickoff meeting, followed by silence the rumor mill happily fills. A third is overselling — promising the system will be easier from day one, trading short-term calm for credibility when the learning curve arrives. A fourth is excluding the strongest skeptics, leaving them nothing to do but organize the opposition. The corrections: diagnose which concern is in play before responding; communicate repeatedly, with honest timelines and explicit statements of what is not changing; answer rumors with facts promptly; and give influential skeptics real responsibility inside the change.
Sustain improvements after organizational transitions
Implementation is where change efforts are won or lost, and the winning pattern is disciplined rather than dramatic. Pilot before full rollout: convert one permit type or one review team first, where problems are cheap to fix and lessons are real. A pilot also manufactures the effort's most persuasive asset — a visible early win. When the pilot team's turnaround improves, publish the result immediately and credit it by name to the staff who produced it; early wins convert the watchful middle of the department. Train on real work, not demonstrations: an inspector who watched a projected demo has seen the system; one who processed ten of their own inspections in it, with help in the room, can use it. Keep a safety net — a parallel-run period for defined cases — with an explicit end date, because an open-ended fallback quietly becomes the primary system again. Treat early feedback as design input: the BDA text advises managers to be honest about what is working and what needs improvement and, where within their power, to alter what is not working. Visibly fixing the first three legitimate complaints buys goodwill for the complaints that cannot be fixed.
Leaders must also plan for the dip. Productivity falls before it recovers — reviews take longer in month one, because old-way competence was built over years and new-way competence is weeks old. The dip is where changes die: staff read the slowdown as proof the change was a mistake, and supervisors, squeezed by backlog, quietly permit reversion "just to catch up." Every tolerated reversion announces that the change is optional. The leader's job is to predict the dip out loud — the slowdown is normal and temporary — and adjust output expectations for a defined period while holding the direction firmly. The BDA text describes the posture: managers must be vigilant in managing major changes, particularly for tenured staff, and must continue to be positive about and cheerlead the changes while staying honest about what still needs work.
Sustaining the change afterward is its own body of work, routinely skipped because the project feels finished. The mechanics are unglamorous and essential. The procedures manual is updated so the new process is the documented process, not a verbal overlay on obsolete instructions. New-hire onboarding teaches only the new way, so the next generation never learns the old routine. Remaining paths back are deliberately closed — the paper intake window is retired, the old forms come off the counter — because as long as reverting is easy, some staff will revert under pressure. Metrics keep score in public: the same measures that built the original case — turnaround, error rate, customer satisfaction — are tracked and shared after the transition, proving the change delivered and catching backsliding while it is small. A change has stuck when it stops being "the new system" and becomes simply how the department works. And the credit goes where it belongs: the BDA text urges the building official to be the department's cheerleader and biggest promoter, celebrating its achievements — a rollout that succeeded because staff carried it should be publicly celebrated as the staff's achievement — the surest way to make the next change easier. As the text puts it, the profession that regulates safety has a responsibility to embrace new technology.
Six months after the electronic plan-review rollout from Module 2, the building official notices slippage: counter staff have resumed accepting paper submittals for "simple" projects, and paper is creeping back toward a third of two examiners' queues. The official treats it as a sustainment failure with specific mechanics. The intake procedure in the manual still described paper as an accepted alternative — it is rewritten, and the counter checklist replaced. Paper intake for converted permit types is formally retired with thirty days' public notice. The quarterly staff meeting adds a standing slide — electronic turnaround versus the old paper baseline, four days faster on average — and the official credits the examiners by name in the report to the city manager. New-hire training materials still referencing paper routing are corrected. A year later, no one in the department calls it the new system.
The defining mistake of this phase is declaring victory at go-live — treating the launch date as the finish line when it is the start of the most fragile period. Related errors: skipping the pilot, so every problem is discovered at full scale; training with demonstrations instead of real work; leaving the parallel-run fallback open indefinitely; failing to warn staff about the productivity dip, so the dip reads as failure; and letting supervisors quietly tolerate reversion under backlog pressure. The corrections: pilot first and publicize the win; train on live work; end the fallback on a stated date; predict the dip and adjust expectations for a defined period; update procedures, onboarding, and forms so the new way is the only documented way; and keep publishing the metrics.
Building department change succeeds when leaders build an honest, data-grounded case before announcing solutions; recruit respected front-line skeptics into the effort; communicate the whys as well as the whats, repeatedly and in both directions; convert resistance into ownership; implement with pilots, real-work training, and visible early wins; lead staff through the temporary productivity dip; and institutionalize the change through procedures, onboarding, closed fallbacks, and public metrics — crediting staff for the result.