Change Management for BAs

Why Projects Fail (Hint: It Is Not the Technology)

Module 1 listed "change management advocacy" among the core BA skills and "drive successful change management" among the core BA activities. Here is why those made the list: successfully changing an organization involves far more than changing products, org charts, and processes. It involves helping people transition. In Peter Drucker's words, "management deals with the behavior of people and human institutions," and people are unlike any other resource: they ultimately control how hard and how well they work, so it is best to have them on board.

The uncomfortable field reality: some people will not recognize the need for change. Some will disagree with the proposal. Some will logically agree and still worry about how the change affects them personally or professionally. And some will passively, or actively, sabotage the effort. A perfectly built Salesforce org that people refuse to use is a failed project wearing a green status report. Change management is the discipline that prevents that, and on most projects, the BA is its most active practitioner: you are the person closest to both the solution and the people it lands on.

This module gives you three complementary lenses (Bridges for the individual, Kotter for the organization, Drucker for leadership and strategy), then a practical toolkit for the projects you will actually work.

The Bridges Transition Model: Change Is External, Transition Is Internal

The Bridges model draws the distinction this whole module rests on. Change is situational and comes from the outside: the new system goes live, the process is redesigned, the team is reorganized. Transition is the internal, psychological process people go through in response, and it takes longer than the change itself. The model describes people moving through stages that affect their performance, and its practical power is anticipation: people have unique reactions to change, but by anticipating those reactions, change managers help people transition as quickly and smoothly as possible, keeping the organization performing at a high level.

The three stages of transition:

1. Endings. Every transition begins with letting go of the old way, and letting go feels like loss: of competence ("I was fast in the old system"), of identity ("I'm the person who knows the spreadsheet"), of comfortable routine. Expect grief-shaped reactions: denial, frustration, nostalgia for the old tool's virtues, suddenly remembered. The change manager's job here is acknowledgment: name what is ending, honor what the old way accomplished, and be honest about what people are giving up.
2. The Neutral Zone. The in-between: the old way is gone, the new way is not yet natural. Productivity dips, anxiety rises, and people feel incompetent, which they hate. This is the riskiest stage (it is where quiet sabotage and workaround-building happen) and also the most creative one, because everything is unsettled. Support here looks like extra help, extra patience, short-term goals, and visible quick wins (your Module 13 office hours and hypercare structures from Module 14 live exactly here).
3. New Beginnings. People emerge with new energy, new identity, and acceptance of the new way, but only if the first two stages were managed. A new beginning cannot be scheduled; it can only be cultivated. Managed correctly, people arrive engaged and in a high-energy state.

For the BA, the model reframes resistance entirely: the person pushing back in training (Module 13) is usually not being difficult; they are in the Endings stage, mourning. You cannot argue someone out of a transition stage, but you can walk them through it.

Kotter's Eight Steps to Organizational Change

Harvard Business School professor John Kotter's eight-step model is the classic framework for leading an organization through change, and almost any organization can use it. Work the steps in order; most failed change efforts skipped or rushed one.

Step 1: Establish a sense of urgency. Overcome complacency by painting a vivid picture of a major opportunity, or a looming crisis, in a way that gets people moving. Leaders often send a series of communications over several weeks describing the conditions driving the change. Without urgency, change is a nice idea scheduled for later, forever.

Step 2: Form a powerful guiding coalition. Assemble people willing to implement the change, deliberately spanning departments and layers to improve cross-silo communication. Identify and engage the key managers and stakeholders who are able and willing to start working on the change. Getting key people on board early multiplies the odds of success. (Your Module 16 stakeholder-analysis skills tell you exactly who belongs in this coalition.)

Step 3: Create a vision. Craft a clear, compelling vision people can easily understand, accompanied by strategies and plans showing how it will be achieved. Audacious is fine; unbelievable is fatal: a vision nobody believes, or a plan that is not viable, actively hurts the effort.

Step 4: Communicate the vision. Repeatedly, everywhere, to anyone who will listen. Repetition ensures everyone is aware, gets people on board, and signals the change is not going away. Treat it like an internal marketing campaign: mix channels (videos, flyers, tailored posts in collaboration channels, team meetings), and remember actions speak louder: key people visibly modeling the desired behavior is the most powerful communication there is, and visibly not modeling it is too.

Step 5: Empower others to act on the vision. Find and remove the obstacles blocking people from acting: compensation plans and metrics that reward the old behavior, cumbersome approval processes, overly controlling managers, restrictive job descriptions. People rarely resist a vision they helped build and are actually free to pursue; they resist the leftover machinery punishing them for trying.

Step 6: Plan for and create short-term wins. Long change efforts die without visible progress. Deliberately engineer early, unambiguous wins, then celebrate them loudly. (This is the "quick wins build trust" principle from Module 5's process work, scaled up.)

Step 7: Build on the change. Do not declare victory at the first win: consolidate gains and use the credibility to tackle the next, bigger piece. Premature victory parties are where changes quietly die and old habits creep back.

Step 8: Institutionalize new approaches. Anchor the change in the culture: update processes, onboarding, metrics, and stories until the new way is simply "how we do things here." Until the change survives the departure of its champions, it is not done.

Notice how directly this maps to your project work: urgency is the business case from discovery; the coalition is your stakeholder and champion network; the vision is the future-state process map; communication is Module 13's craft; obstacles are the old metrics and processes your gap analysis found; short-term wins are early sprints demoed well; institutionalization is training, documentation, and the sustain phase from Module 14.

Drucker on Change: Create the Future

Management thinker Peter Drucker's work supplies the strategic backdrop, and it starts with his most famous line: "The best way to predict the future is to create it."

The Six Best Practices of Change-Leading Organizations

Drucker insisted that "every organization has to build the management of change into its very structure." Six best practices describe organizations that have:

1. Develop a compelling vision. A well-crafted vision describes the organization's purpose and paints a vivid picture of what it aspires to become for its customers: compelling to customers and workforce alike.
2. Commit to innovation. Systematically innovate products, services, processes, and business models. Truly disruptive innovations are rare; most change leaders aim for a stream of small, incremental innovations that compound into big gains (car makers' yearly model updates between full redesigns), while staying alert for the transformative leap.
3. Focus on customers and the market. Generate intelligence, analyze and disseminate it, act on it: detect early signs of change, predict change, drive change.
4. Dynamically manage capabilities and resources. Intentionally create, extend, modify, and use resources (capital and equipment, but also data, information, people, and knowledge) for advantage. "The enterprise, by definition, must be capable of producing more or better than all the resources that comprise it." CRM systems are a textbook example: customer data converted into process improvements and better decisions.
5. Practice abandonment. Free resources from activities that no longer contribute, by challenging everything with Drucker's question: "If we were not in it already, would we be going into it now?" IBM selling its iconic PC business is the classic case: painful, and right. (Every stale report, unused field, and zombie process your discovery work uncovers is a small abandonment candidate.)
6. Create a culture of change. Cultures that seek out and embrace change are nearly impossible for competitors to copy, which makes culture itself a competitive advantage. Change leaders hire, develop, and keep people who fit that culture.

A practical diagnostic: score your organization (or your client) honestly against each of the six, identify the weakest two, and you have a change-readiness assessment worth bringing to any transformation conversation.

Case Study: Transformation in Practice

The Practical Toolkit: Driving Change on Real Projects

Frameworks orient you; these tools are what you will actually use on a Salesforce project, drawn from the source material's admin-and-analyst-facing guidance.

The BA's Change Management Playbook

Synthesizing everything into the loop you will run on projects:

1. Diagnose the change. What is ending, for whom? (Bridges) Who wins, who fears loss? (Stakeholder analysis, Module 16)
2. Build urgency and coalition. Surface the business case from discovery; recruit champions across silos. (Kotter 1-2)
3. Anchor the vision in evidence. Future-state maps, benchmark data, and a believable plan. (Kotter 3, Modules 3-5)
4. Communicate relentlessly, WIIFM-first. Multi-channel, repeated, modeled by leaders. (Kotter 4, Module 13)
5. Remove obstacles and engineer quick wins. Old metrics, clunky approvals, missing permissions; then celebrate early value loudly. (Kotter 5-6)
6. Support the neutral zone. Training, office hours, hypercare, patience. (Bridges, Modules 13-14)
7. Institutionalize and improve. Documentation, onboarding, adoption metrics, continuous improvement: and keep 10-20 percent of attention on the future. (Kotter 7-8, Drucker, Module 14's sustain)

Run that loop with warmth and stamina, and you will be worth more to most projects than any amount of configuration skill.