The 2024 Microsoft outage is an unscheduled reminder to use best practices in technology change.

The repercussions of the CrowdStrike update have us shook. The 2024 Microsoft outage is a timely reminder that rushed or mismanaged system changes can lead to chaos. How can you avoid the pitfalls of poorly planned technology changes?

Invite folks to the table.

First, consider the scope and implications of your change. Then ensure the right people are involved in planning, testing, and adoption. Identify and engage every group who might be affected by the change; solicit their input, identify impacts, and make sure you’re aligned.

• System Interdependencies: What other systems are involved with the system that is changing? Consider both upstream and downstream applications.
• Stakeholder Impact: How will this change affect the lives of employees, partners, and customers? How will they react? Ask questions, investigate thoroughly, and avoid making assumptions.

Consider the scope and implications of your change.

Test early, often, and thoroughly.

Experimenting and evaluating are crucial components of any change implementation. Test early, when it’s less painful to fix things. Test often, so you catch errors at each stage. Test thoroughly, so there are no surprises. Here are some essential testing strategies:

• Functionality Tests: Ensure the program/system is functioning as designed within the Sandbox environment.
• Platform Tests: Verify that the published program/system operates correctly in various live environments.
• Blind Individual Tests: Have individuals outside of the project team test the program/system to ensure usability and functionality from an unbiased perspective. Studies show that the closer you are to something, the less objective you are. Your brain automatically sees it the “right” way rather than the way it actually is.
• Stress Tests: Conduct stress tests to catch any defects early and minimize their impact on the organization and other stakeholders.

These protocols help identify and rectify defects early, ensuring a smooth and reliable implementation with minimal disruptions to your operations..

Timing is everything.

There is a long-running adage in the programming world – “Don’t deploy on Friday.” Some view it as a joke, others a jinx, but many consider it a must.

Risk management exists for a reason; no system is perfect, no team is perfect, so it’s prudent to plan accordingly. Not only do Friday deployments reduce the margin for error to fix an issue, but key stakeholders are often less available. This has implications for your team, but also your stakeholders, who might not see any communications or troubleshooting materials you share on a Saturday. Finding the right time to launch your change mitigates risk and improves adoption.

By incorporating these practices, organizations can better manage changes and prevent the type of widespread issues that resulted from the recent CrowdStrike update.

Enterprise Resource Planning. The software that touches every single part of your business takes, on average, 18.4 months and roughly 3-5% of your revenue to implement.

Companies make these big investments because ERP can deliver efficiency, productivity, visibility, better forecasting, and data security, all while reducing costs. In fact, many companies consider ERP essential to their future. Nem Fontanilla, who has spent 27 years enabling global transformations, recommends that organizations “Design the ERP with the vision in mind and leverage it to accelerate the achievement of your team’s vision, not to enable the current reality.”

Unfortunately, most companies experience a rough ride on the way to those benefits. A friend of mine is CEO of a midsized company, and is in the the second year of a promised six-month cutover. When he described the team’s difficulties closing the books due to the cutover, and the accounting teams increasing frustration, another friend chimed in. His team had a similar issue with their ERP implementation. He described their reaction as “organ rejection.”

Is your organization fighting off the ERP implementation? Here are some of the reasons.

“No time for that.” It’s more than enough to get the day-to-day work done. Adopting a new system demands attention and energy that equates to another full-time job.

“The best person for this project already has a job.” If you want the new system to work well, you need your best people on the ERP team – the folks who know your business best. So who is running day-to-day operations while they’re focused on your company’s future? The irony is that they’re so essential to the business that they can’t be spared, yet they’re probably worried they won’t have a job when the project ends. You have two obstacles to staffing your ERP team right.

“It’s good enough.” The old system and process works well enough. The team works on auto-pilot – they know what to input and where to send it. They find it hard to imagine the benefits of an operational overhaul outweighing the urgency of the moment. And frankly, some departments might be right about that. They might find the new system is worse for them even though it benefits the company as a whole.

Feeling a little defeated? You’re not alone. It’s chaotic enough to run a business. Now you’re intentionally introducing something that might break it.

Here’s what to do.

Embrace the suck. Assume employees will hate it. It’s a big change. Every living person is here because our ancestors were paranoid enough to anticipate danger and survive. Your new system is an intruder.

Resist cliché communications. Do not create a basic elevator speech. Do not create “talking head” videos of your executives saying how important this is. You will reinforce every cynical assumption your people have about this effort. Instead, create a consistent message frame that is customized by the speaker based on the audience. For more on how to communicate, go here.

Communicate based on impact. Employees care about when they will be affected and how. If you communicate too much, people tune out. You’re just teaching people to ignore you. For each person or team, communicate just what matters, just enough, and just in time.

Say the thing. There’s a natural tendency to hold back information that’s unpleasant or undefined. But fight that urge; the more more explicit you are, the more you dispel confusion and build trust. Spell out your scope and your timelines. If there will be layoffs, say so. Identify who is impacted and how.

Show them this time is different. Sometimes employees resist a change because they equate it to another change that “failed.” So highlight the differences between this project and others in the past. Differences might include:

• New Approach
• Different Team
• Different Budget
• Tighter or Expanded Scope
• Different Focus
• New Code
• Different Timing

Create fresh starts. A long ERP initiative can feel like a slog. Psychologically, we respond better to beginnings and ends. Seize on any arbitrary beginning that feels real: a new quarter, a new phase, hitting a milestone, or new metrics (like testing or training numbers). Help the team and the organization feel the progress and success by celebrating those starts and ends.

Focus on one small win. For each job role, think of only one thing an employee can do to use the new system, even if it’s as trival as logging in. Have them do it, and have them do it often. Make sure it’s easy, and that the experience is positive – for example, that the screen they’re on actually works. This gives them a sense that they can be successful and it makes the new system feel more familiar.

Double-down on From-To. Nem Fontanilla, who has spent 27 years in change and transformation, recommends that teams “(design) end-user readiness activities with (the user’s) day in the life in mind. Help them contextualize and see the change from their vantage point.” Where do your current fields appear in the new system? It’s that level of detail employees will want. Where is the data people used to use – where is it now? Document that, and train that. The more specific you are, the easier you make it for your people.

Prepare to invest in cutover twice. You’re working toward an end state. But in between here and there is a transition state. The support materials you develop differ for each state. You need temporary processes and training for employees who have the context of how they work now. These transition materials will be irrelevant once you complete the cutover. The second set, your steady state materials, are for new employees who have never known your old processes. They live on going forward. Some people try to skip the transition investment and only invest in the end state. However, that forces employees to figure it out on their own, which is a bit like interrupting a line of ants – they find a new path, but you have no way to control or predict it.

Nem Fontanilla says, “Turning on the ERP is the beginning…The functional teams need support to fully realize the value. It does not just happen because the new capabilities are available.”

Getting past the organ rejection takes focus and preparation, but it can be done. The huge investment in your ERP requires no less.

Think differently about your investment in user performance.

Companies continue to invest in technology. Digital, artificial intelligence, and cyber security are all over the headlines. Cloud and ERP also continue to be big. In fact, the global ERP software market is expected to reach $78 billion by 2026.

Most of these investments come with expectations for a large return on investment. Seasoned IT leaders know that the integration of people, process, and technology is what drives ROI. The business case is rarely realized if human behaviors and processes don’t change.

Despite IT’s decades-long focus on change management, budgeting for the “people side of change” is a mystery to many. And it doesn’t help that project budget numbers must be submitted and approved long before all the implications of the change are clear.

The traditional way is to estimate 15-25% of project spend for the people side of change. A quick google search will show firms like Gartner promoting this ratio. While the old school “percentage of IT investment” is a starting point, it can lead to under-budgeting.

Seasoned IT leaders know that the integration of people, process, and technology is what drives ROI.

Why? First, technology has never been cheaper. Sometimes it’s even free. So you’re using a percentage of a shrinking number. People, however, remain consistently expensive and require things like new organization structures, process changes, work changes, training, and communications. Technology cost is irrelevant to what’s required to equip people to support the organization’s success.

Here’s a better way to estimate:

Technology-focused projects and budgets have evolved. Planning for change management on these projects should evolve as well. Go beyond the traditional “percentage of project funding” when budgeting for the people side of change.

Three considerations before launching your tech pilot.

Smart teams think about people during their digital transformation pilots. They know that the employee’s digital experience is where the IT investment is realized. The most fantastical tech is worthless if no one is using it — or using it right.

How do you get the most from your pilot? Put change management in the cockpit.

Here are three things to think about:

Don’t wait to start change management.

Before the pilot, you should have conducted a change impact assessment. This will tell you which stakeholders are affected and how. Select your pilot testers and construct test cases based on those real-life impacts.

Smart teams know that the employee’s digital experience is where the IT investment is realized.

Also, be thoughtful about the messages you’re sending as you test. The impact assessment will tell you what certain user groups will gain and what they will lose. Use the key points of the overall project message — the problem, solution, approach, and results — then customize those messages for your testers. It’s a great opportunity; they will report back to their work teams and set the tone for your go-live.

Test as much as you can.

Don’t just test the tech. Try out your communications and training on the pilot group. As you do, keep the focus on testing assets and assumptions. Don’t let perfection get in the way; a pilot is for gathering information to make things better.

And measure! Collect data on users’ readiness for the new technology and how well they adopted new ways of working. Your exposure is limited in the pilot, but you can learn so much that will inform the rollout.

Create your go-live playbook.

Record your results, tester feedback, and your lessons learned. Assemble the change management tools you tested, like the communications and training assets. Create an updated set, incorporating what you learned, to guide the team for your go-live. Package your roadmap and recommendations for the rollout.

Your digital transformation pilot will test whether your technology is ready.

It’s also the perfect setting to learn what will “fly or die” with your impacted audiences. Don’t take off without change management in your pilot’s cockpit.

You Really Need These Answers Before Day One

Your new system and processes are going live pretty soon. You have solid training and communications in place. So you’re ready, right?

Not necessarily. There are organizational dynamics that can scuttle your smooth transition plans. Ask yourself these questions, and plan to go live with no unpleasant surprises.

1. What message is the boss sending? If he or she does not support the change, the team will not buy in. Ensure executive leadership visibly and vocally supports the change.
2. Is the old way faster? People might revert to doing what they know to get the job done. Think of ways to ensure workers do their work in the new way, with the new tools.
3. What are the consequences for not working the new way? If there are no consequences, expect noncompliance. Prepare to demonstrate the business impact of not doing it the new way.
4. How “real” is the training? Without realistic scenarios and simulations, you can’t expect good performance on the job.
5. Are you training roles or tools? The tool is simply the means for executing job functions. Effective training is role-based and teaches to day-to-day business processes.
6. Will they learn to handle mistakes? If you only teach people what to do when everything works perfectly, that is not realistic. Train people on what to do when things go wrong.
7. Where do people turn when they need help on the job? Do they turn to peers, their boss, procedure manuals, or online help? Create a post-training support system that makes sense for these users.

We insist that our clients answer these questions early in any technology implementation. Addressing them is essential to your readiness to go live, run your business, and get the benefits you expect. And if you need help with solutions, reach out to us by using the chatbot or our Contact Us form.

First, we have to agree on what AI is. Then, we can help employees adopt it.

In March, tech gurus including Steve Wosniak and Elon Musk signed an open letter calling for a pause in AI development, citing “human-competitive intelligence (that might) post profound risks to society and humanity.”

More recently, Geoffrey Hinton, hailed as the godfather of AI, quit Google so he could air his concerns independently. In a 2021 commencement address, Hinton said, “I believe that the rapid progress of AI is going to transform society in ways we do not fully understand and not all of the effects are going to be good.” For Hinton, the downsides seem to outweigh the benefits, like improvements in healthcare. The risks he envisions range from job elimination to lethal autonomous weapons. He also says AI might create a world where we will “not be able to know what is true anymore.”

Speaking of misinformation…these stories made it to the table at The View, where hosts weighed in. They talked about the pros and cons of AI, but couldn’t even agree on what AI is. Notably, Whoopi Goldberg said that she defines AI as something “sentient” that “can think for itself.”

Whoa. I’m not saying a robot boyfriend is not in my future, but sentience is NOT what the scientists are talking about. There’s a big difference between smart or fast or autonomous and self-aware.

The lesson for those of us who help the workforce deal with change is this: AI is scary to some people, and possibly for the wrong reasons.

Let’s say your organization is adopting AI to gain efficiencies, reduce costs, or deliver better customer value. How should you approach employees about it?

1. Mind your language.

Maybe don’t call it “artificial intelligence.” I’m not suggesting lying to people; just the opposite. Explain exactly what the new technology will do.

The term “AI” can be triggering. Moreover, “AI” is too broad a term to be useful when talking to employees. AI is a huge category; labeling a new tool “AI” gives very little information to the people who are desperate to know how it’s going to change their work lives.

Think of it this way — will your AI solution detect and prevent dangers in the workplace? Say that! Call it Safety Software. Is AI going to supply customer service agents with better, faster answers to help customers? Say that! Call it Your Customer Service Assistant.

2. Get real.

Approaching any change, what do employees want to know? They want to know how it will affect them – their job responsibilities, their daily tasks, their compensation, their team performance, and their job security.

Get ahead of the resistance by answering questions honestly and thoroughly. Yes, even the bad news. If your new AI… sorry, Customer Service Assistant…will eliminate jobs, be up-front about it.

Most important: document and communicate the day-to-day work that will be different after implementation.

If you don’t tell people the story, they will fill the gap with their own.

3. Reframe AI.

Is the anxiety warranted? Maybe some of it. But AI can also benefit workers — sometimes in big ways. In fact, some employees have already adopted the positive mindset you’re hoping for. A Pew Research study shows 37% of workers are “purely excited” about AI.

And there’s plenty of evidence to back their enthusiasm. AI solutions, like tech before it, can take mundane, focus-intensive tasks off employees’ plates, freeing them up for more analytical and creative work.

One real-world study showed that AI offered big benefits for inexperienced or less-skilled workers by raising the quality of their work and productivity to be on par with their best-performing colleagues.

Armed with facts, examples, and those 37% already excited about it (your “early adopters”), you can – with authenticity — frame your AI adoption as a win-win.

When we need to worry about killer robots, we’ll worry about killer robots. In the present day, lead the change by taking these three steps. You can definitely make AI work for both your bottom line and your human workforce.

A global retailer once hired me to help install PeopleSoft—it was their 3rd attempt. Their pain is not uncommon. Enterprise resource planning, or ERP, is a vital management tool, but its implementation can often be a nightmare.

For example, the average cost of an ERP implementation is $4.5 million or 6% of revenue. The average time to implement is 1-3 years. (!) With these painful stats in mind, it makes sense the Wall Street Journal once described SAP implementation as a “corporate root canal.”

Here are five questions you need to ask and answer before implementing an ERP.

1. Who is on the team? The most common mistake is to assign responsibility to IT and whichever department will use the system the most. Those two silos typically don’t appreciate the implications of their decisions on the groups who will input, maintain or receive outputs from the system. This can scuttle your ERP. Instead, get a cross-section of expertise on your team. Every group interacting with the system should be there.
   

   Your ERP team should be made of your best employees—their decisions will impact how this system (and your business) will run for years.

2. What one behavior drives the business case? If your team is serious about the business case, they must articulate what they need people to do in clear, tactical terms. Then focus, focus, focus; focus relentlessly on that. An IT firm spent millions on enterprise resource planning to help them make money on license renewals. The one activity they needed most from their sales team was to call clients the month before their contracts expired. Because they didn’t make that specific request, sales people didn’t do it consistently. The firm could not hit the business case; it was wholly based on “license renewals”—a lovely concept that no one acted upon.
3. How are we managing first impressions of the system? Shteingart, Neiman & Lowenstein’s 2013 research, published in the Journal of Experimental Psychology, shows that “first experience has a disproportionately large effect on subsequent actions,” something they labeled “outcome primacy.” In other words, first impressions matter. So the first employees who touch the system—starting with requirements definition—had better be wowed. Only someone in marketing should be giving the project a name. And if user acceptance testing sucks, stop implementation. As Kahneman and Tversky found, we feel the pain of loss more acutely than the pleasure of gain. We compulsively avoid anything that smacks of failure. Manage the employee experience as rigorously as you manage the project itself.
4. Who will be our first users? In the 1960s, Everett Rogers published a book called the Diffusion of Innovations, which analyzed why certain ideas and products capture the public’s imagination. He mapped those who adopt the idea against a bell curve, showing that 3.5% of the target group are eager early adopters, and 13.5% are positively predisposed to change. You can use this to create momentum. If you want your ERP to look like a winner, find the early adopters. Enlist the 3.5% for system test, and the 13.5% for UAT. Pilot with these employees intentionally. They’ll make the system seem safe and successful to everyone else.
5. How are we ensuring the system is employee-centric? Employees don’t think about the system. They think about their jobs. Training must be about how to use the system in the context of their jobs. What will they do, day to day? Where will new tasks and handoffs take place? Where are the data and tools they relied upon—which will stay and which will be replaced?

Generic ERP training is a waste of time and money. Train people to do their jobs, not use a system.

Enterprise resource planning is one of the most invasive and expensive undertakings your company will ever face – even if it’s “cloud-based” and “intuitive.” If you get these five things right, you’re ahead of the game and on your way to a return on your investment.

Tasha Leverette was sitting in the drive-through of her neighborhood Starbucks in Atlanta, jonesing for her usual drink. They told her they couldn’t make it; they didn’t have any peach juice. So she drove to another store. And another. And another.

“I said to them, ‘This is the Peach State, right?’ … It’s surprising because Starbucks always seems like it has anything and everything you need.”

Across the country, customers and baristas are taking to social media to bemoan not only shortages of key ingredients for popular Starbucks drinks, like peach and guava juices, but also a lack of iced and cold-brew coffee, breakfast foods and cake pops, and even cups, lids and straws.

A video on TikTok this week featured what appeared to be a group of employees screaming in frustration over a list of ingredients that the shop had run out of—including sweet cream, white mocha, mango dragon fruit and “every food item.” The caption also said they were low on cold brew and the “will to live.”

Starbucks is hardly the only company struggling with supply issues. Earlier this spring, ketchup packets became hotter than GameStop stock. Automakers have slowed production because there are not enough computer chips for their vehicles. And homeowners are waiting weeks, if not months, for major kitchen appliances.

Starbucks, Flush With Customers, Is Running Low on Ingredients, New York Times

It’s not just Starbucks. From computer chips to ketchup packets, business bounce-back has been stalled by supply chain issues.

Phil Knight, the legendary founder of Nike, said “supply and demand is always the root problem in business.” Weak demand for a product is a bitter pill for any company to swallow. But inability to meet booming demand based on supply problems is maddening.

Coronavirus has highlighted just how fragile our supply chain has become.

In some cases, the chain is very complex. Even seemingly basic products like disinfectants, not to mention higher-end products like automobiles, can have many links in the chain of component ingredients or parts. Other times, there are too few links. For example, grocery stores may not able to meet the consumer demand for meat because there are relatively few animal processing plants. Production disruption at only a handful of major plants can leave meat displays nearly empty.

A global pandemic is a black swan event, but large-scale supply disruptions are becoming more common due to events like natural disasters, changing economic policies, and geopolitical disruption. Managing risk differently is a must. Tactics include:

• Identifying alternative sources of origins of component materials
• Diversifying suppliers
• Moving to nearshore or even onshore suppliers.

New solutions often mean new processes and digital technologies, and they always require people to perform differently. Change management—the people-centered interventions—are crucial.

The Case for Change Management

Transformation

Coronavirus is a trigger event for supply chain transformation and transformation is complex. Digital technologies like analytics and artificial intelligence are part of the solution. New processes are part of the solution. Employee behavior change is part of the solution.

In the face of a big, complex change, employees might be confused and fearful—they might disengage or actively resist the new way of working. But you need that behavioral system to work just as well as your processes and technology. Managing this change is crucial.

Messages must be clear and concise in times of complex change. We help clients boil down their message to four words—one to describe the problem, the solution, the approach, and the result. Together, the four words anchor the message. Leaders and other advocates need only remember these four words to ensure a consistent message. To make each communication compelling, add supporting details that are relevant to the audience.

To guide the organization through a change you need to understand who is impacted and how.

Any change management novice knows how to identify stakeholders. We typically define them by team or department and design custom communications, training, and performance support for each group. But this type of analysis is incomplete. Teams and individuals should be categorized based on their disposition to change. Some stakeholders emerge as early adopters, who are pre-disposed to embracing new concepts. They make the change safe for the next segment of adopters: the early majority. The early majority makes the change feel like “this is how we’ve always done business” to yet another segment of the population: the late majority. Identifying, enlisting, and deploying the right people creates a bandwagon effect, until you have the momentum you need to engage the entire organization.

Behaviors, Habits, and Culture

Peter Drucker said “culture eats strategy for breakfast.” It’s true. Results are marginal if your supply chain strategy doesn’t fit your culture.

How do we know whether a strategy aligns with culture? The sum of organizational habits form a culture. Habits are regularly repeated behaviors. We have to identify the behaviors that enable the desired business outcomes, and then decide whether those behaviors do or could align with the dominant culture. New behaviors can become part of the culture if they turn into habits.

Assess where you are today vs. where you need to be.

• Identify the behaviors that drive the to-be state.
• Consider what triggers or prompts each behavior.
• Make sure there is a positive consequence to reinforce the behavior.
• Ensure that employees have the ability to execute the behavior.
• Develop a plan to practice the behaviors and start creating habits.

Reinforcement

We’ve heard the phrase “What gets measured gets rewarded, and what gets rewarded gets done.” Consider this when engineering behavior change. Are employees rewarded for managing risk? Probably not—at least not yet. Cost control or cost reduction has typically been king in the decades-long quest for efficiency. But performance ratings or bonuses tied to cost savings may not reinforce risk management behavior. It’s pretty basic: leaders must ensure that KPIs and employee reward structures match the business outcomes they want.

Conclusion

The global pandemic and other natural disasters may be changing the business landscape for good. But one thing that will never change is our need for a venti caramel latte with an extra shot. Business leaders need to get it together —we have no choice but to change supply chains to be more nimble. Mastering the change might  be the difference between good and great outcomes.

Sources

https://25iq.com/2018/01/27/lessons-from-phil-knight-about-business-and-being-an-entrepreneur/

https://hbr.org/2020/03/coronavirus-is-a-wake-up-call-for-supply-chain-management

https://www.industryweek.com/leadership/companies-executives/article/21956400/are-your-supply-chain-strategies-and-reward-structures-aligned

Fogg, B.J. Tiny Habits,

Rogers, Everett. Diffusion of Innovations

Everyone has heard of Sully Sullenberger, the hero who landed US Airways Flight 1549 on the Hudson. At the time, he was serving as chairman of a pilots’ association safety committee. Some might say it was luck such a pilot was at the controls when a flock of birds struck Flight 1549. Sully said the many hours of training all pilots receive allowed him to assess the situation and make a timely adjustment.

In stressful, highly complex situations, like flying a plane, it is easy to see the value of training. What we might underappreciate, is the type of training pilots receive.

Picture this scenario: It’s a cloudy winter evening in San Diego, 1977. A plane is taxiing to the runway. All the pre-flight checks appear to be in order. The flight engineer has given the go-ahead to take off. As the plane accelerates down the runway, it begins to pitch upward and lift off the ground before reaching the standard takeoff speed. It’s an odd situation, but not alarming. Unfortunately, it immediately gets worse. The nose of the plane continues to rise while adjustments to the control stick do nothing. It’s a dire situation that requires immediate reaction to avoid a crash.

Captain Jack McMahon knew what to do in this situation. On that evening in San Diego, Delta Flight 1080 was in trouble. With the nose up and airspeed dropping, the plane was critically close to stalling and crashing. When none of the standard fixes stopped the climb, Captain Jack masterfully adjusted his throttles to take advantage of a feature his plane. The engines were arranged so that the wing engines point slightly down, their thrust making the plane pitch up slightly. The tail engine, however, is pointed slightly up. The thrust from the tail engine makes the plane pitch slightly down. By decreasing power to the wing engines and increasing power to the tail engine, he was able to bring the nose down and avoid a stall. More creative problem solving enabled the plane to make a safe emergency landing in Los Angeles. An investigation soon identified the problem was a tail stabilizer stuck in the up position, constantly trying to lift the nose of the plane. Investigators would note that comprehensive training played a critical role in preventing a crash that day.

So what is it about pilot training that makes them so good in a crisis? It is true they spend many hours in training, but it is not just the amount of training that is important. The type of training, and the types of scenarios they practice are just as important. They train for situations where everything seems to be going wrong. The airline industry creates moments of controlled failure in training, to the benefit of pilots and passengers.

What is controlled failure and why is it important? When we design courses, it is common to create scenarios trainees will encounter in real life. In controlled failure scenarios, trainees are set up for trouble, allowing them to solve the problem, learn, and grow. Using only predictable scenarios geared for simple wins gives learners early successes, but it might not prepare them for real-world performance.

The real world doesn’t always give us easy scenarios and quick wins. In The Hobbit, J.R.R. Tolkien captures a more common new hire’s experience: “Out of the frying pan and into the fire.” In any job, issues come up force employees to think on their feet. This is where controlled failure training is important. By mixing difficult scenarios with easy ones, we build both small wins and adaptability into a training course. The result is employees who have the confidence to manage any real-life situation that comes along.

If captains Sully and Jack had practiced only takeoffs and landings in normal conditions, they would have been ill-prepared to handle the situations that threatened the lives of their passengers. The results might have been disastrous. Controlled failure pilot training probably saved many lives.

Most of the training we design doesn’t prepare people for life or death situations. But controlled failure makes for a workforce ready to adapt to difficult situations and keep your business in the air.

You need new technology and processes. You know how you want your organization to use them. So you choose a system and start designing the way you want to do business in the future. What’s wrong with that?

You’re wasting time and money.

Organizations are naturally impatient to describe and document their futures. But it’s sometimes hard to convince them to carefully document where they are right now. I mean, everyone knows what you do now. Isn’t it a waste of time?

No. You must carefully document the current state—of your systems, processes, and work.

Think of it this way. Planning to implement a new system is like planning a road trip. Typically, you have a clear start and end point; with that information you can pick the route, identify sites to hit along the way, and estimate the cost of gas, snacks, and hotel stays. But what if you didn’t know your start location? Now you don’t know any of your routes, what supplies you might need, or even how long it will take to get to your destination.

You might be thinking, this is silly. Of course you know where to start your road trip; it’s right where you’re sitting! And you’d be right, except on this particular trip, you’re not the only one on the road. You’re traveling with everyone in your organization; you all have to end up in the same place. Say everyone agrees to meet at the Starbucks parking lot, but no one clarifies which one; now the wheels are falling off, and you haven’t even left yet. You need to get in touch with everyone, figure out where they are, and tell them where to go…you’re spending time, and maybe money, rounding everyone up. And when you’re finally together, everyone might not agree to follow your original plan.

Sounds pointlessly exhausting, right? Well it’s nothing compared to a system implementation without a properly documented current state.

Documenting the current state isn’t just about avoiding pitfalls on the road. There are significant advantages as well.

Knowing the “as-is” enables you to pick or design the system properly, analyze the impacts, and design employee engagement and good training.

So what does it take?

• Leadership must align on where the organization stands. What are the current assets and liabilities, and what are the obstacles to success? To figure that out, establish a common vocabulary and confirm current workflows. This identifies the current dependencies and interfaces to maintain, and illuminates gaps the new system must fill if you want to reach your goals.
• Concurrently, identify repetitive processes and cut down on customization where it’s not necessary. Get the right amount of technology to reach your goals, don’t pay for fancy features you don’t need!
• Speaking choosing technology, make sure all decision-makers understand something: the system is NOT the destination; it is the car. This is important. Technology is a tool that helps you achieve the business outcomes you want. Make sure you pick the right tool for the job.
• After identifying your start and end locations and selecting your vehicle, you’re ready to plot a course. This includes assessing the gaps between current and future states and conducting an impact analysis. Studying who is impacted and how gives you a blueprint for the employee transition—engagement activities, communications, and training. In other words, you’ll deliver the right solutions for the right people at the right times. (Check out our three key principles of organization change: familiar, controlled, and successful.)

Documenting your current state is a critical investment in the success of your implementation. Give it the time and effort it needs, and your journey to those business outcomes will be a lot more rewarding.