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.

Are you a super communicator? No? Are you familiar with Supercommunicators by Charles Duhigg? No?! This best-selling book is our latest book club pick. All of us at Emerson Human Capital are reading it, section by section, and meeting to discuss our takeaways.

As consultants in the world of Learning & Development and Change Management, we have to be good listeners and ask thoughtful, appropriate questions. It’s how we ensure we deliver on the real needs of our clients. So, we’d like to think we are already super communicators – but are we?

Here’s what we’ve learned so far by reading and discussing the book.

A Few Key Ideas

Three Types of Conversations

Duhigg organizes his book around three main types of conversations:

1. What is this really about?
2. How do we feel?
3. Who are we?

Understanding the answers to each of these questions ensures participants are engaging in the same type of conversation.

Think about how often you or your team have jumped into a discussion out of habit or urgency (with or without an agenda), only to walk away wondering, “What just happened?” or feeling that you didn’t get your needs met. Recognizing and acknowledging the type of conversation helps avoid confusion and inefficiency.

Four Rules of a Learning Conversation

1. Pay attention to what kind of conversation is happening.
2. Share your goals and ask what others are seeking.
3. Ask about others’ feelings and share your own.
4. Explore whether identities are important to this discussion.

Quiet Negotiations

Duhigg tells us, “Within every conversation there is a quiet negotiation, where the prize is not winning, but rather determining what everyone wants, so that something meaningful can occur.” This quiet negotiation focuses both on what everyone wants and on the rules for making decisions together. He frames negotiation as a “subtle give-and-take” to ensure everyone wins, rather than the more common understanding of negotiation as a zero-sum game.

Neural Entrainment

It seems at our cores, Emersonians are kind of nerds. One of our loves is neuroscience. So, imagine our fascination when Duhigg introduced the concept of “neural entrainment.” He says, “At the heart of every conversation is the potential for neural synchronization,” which is an alignment between speaker and listener that is a key to the effectiveness of the communication.

Our Questions and Challenges

Sharing to Connect vs. Shifting Focus

At Emerson, we love to use the power of storytelling. Duhigg uses real-life stories to teach his concepts. Early in the book, he describes how a CIA agent learned to build and recruit key resources through sharing personal feelings and vulnerabilities.

When our team met, we paused to debate this further. After all, it seems every active listening principle tells us to keep the focus on the speaker and not grab the spotlight. We were left wondering how these concepts peacefully co-existed. (Spoiler alert: Duhigg dives into this further in section two of his book.)

The Post-Pandemic Problem

How do we overcome the challenges of connecting in a post-pandemic, more remote culture? Supercommunicating is about connecting. However, to our team it feels even harder than ever to make connections. One of us said, “Things seem so much more transactional.”

We had a few ideas to help overcome this challenge:

• Go to meetings a bit earlier and chat with those early to join.
• Turn your cameras on. See and be seen.
• Use humor. Share laughs, person to person. Be human together.

Manipulation?

Duhigg uses a case study to demonstrate the concepts of super communicating. The example is based on a jury in deliberations. As we read how one jury member applied super communicating principles, we could see how the minds of other jurors were changed.

We wondered whether supercommunicating was simply a form of masterful manipulation. As we talked, we decided it’s more about drawing out what really matters to other people — uncovering what they value and want. Duhigg helps us see past a “zero sum game” to a negotiation experience in which the pie gets bigger and everyone wins.

Simple Ways We’re Becoming Super Communicators

Get past: “I have an agenda and I need to get X, Y, and Z out of this meeting.” This doesn’t create strong relationships. Let go of your agenda and thoughts and be mindful and present, so you can actually read the people and what they need. It is important to get to the objective, but strong connections better in long-run for project.

Ask upfront: “What do you want to get out of this meeting? Use this with internal teams and with clients. Co-create a plan for the agenda. Even start with yourself to prepare for conversations. Duhigg suggests answering these questions first:

• What are two topics you most want to discuss?
• What is one thing you hope to say that shows what you want to talk about?
• What is one question you will ask that reveals what others want?

Adopt: Help, Hear, Hug? Clarifying the conversation means recognizing what each participant needs. As Duhigg says, “Different needs require different types of communication, and those different kinds of interaction – helping, hugging, hearing – each correspond to a different kind of conversation.” Is it a practical conversation (helped)? Emotional (hugged)? Or social (heard)?

Establish the shared language to help define what kind of conversation is really happening. Get aligned right away. As our team said, “Why not? That way, we’re having the same conversation!”

Intrigued by some of these concepts? Stay tuned for Are You a Super Communicator? Part 2 to find out what we learned from the rest of the book.

Consider a multi-directional development model.

In the consulting world—and certainly not limited to this field—it is all too common for organizations to adopt a “move up or move out” culture. In other words, individuals must get themselves promoted to a higher rung of the org chart; if they’re not promoted within a pre-set timeframe, they’re considered unredeemable or fired.

In its worst form, it is survival of the fittest. In its best form, it operationalizes a growth mindset, supporting individuals as they develop and advance along their chosen career path.

But is “up or out” the only direction?

What about side-to-side? Or even forward and back? Does your organization have a plan for someone to opt out of an “upward” path? Can they do so with emotional and professional safety?

When Trish Emerson founded Emerson Human Capital Consulting, she knew firsthand the up-or-out culture that many of us have experienced. She wanted to build an organization with a “multi-directional” culture.

As I consider how this has played out within Emerson, I can cite real examples of current team members who have moved “up” into leadership roles then “back” to more client-focused roles. Others have transitioned from full-time employees to contractors. Others are clients turned employees turned contractors. And still others have been contractors and then joined us as full-time employees.

Our philosophy—doing meaningful work with people we love—isn’t limited to linear career paths. We want those people we love—the talented, creative, relational, impactful people—to find a sweet spot where they can thrive. In turn, this nurtures the culture and the well-being of our overall organization by retaining team members in ways that allow them to be their best, high-performing selves.

I experienced this firsthand recently. I spent decades in up-or-out and “in order to grow you have to go (somewhere else)” career scenarios. A year ago, I accepted a promotion at Emerson. At the time, the role was new. There were aspects of the role presented to me that I knew I would love. Other aspects I knew would be challenging or less energizing than my other work.  We collectively agreed to try it; if it didn’t work, we’d figure it out. In other words, there was an “opt out” card on the table.

Over the course of the year, I found myself questioning whether this role was the right thing at the right time.

I decided to talk to Trish, our CEO, about shifting back to the role I had loved. I recently worked on a client project focused on empathy, belonging, and trust, so I was very tuned-in to these dynamics as I approached her to discuss what a move would mean.

How remarkable to be able to say, “She made it so easy!” She secured my sense of belonging by quickly confirming that all team members need to be in roles that help them thrive. She sees how that feeds the well-being of the organization. She empathized with the factors at play for me as a whole person – not just “Workplace Lisa.” She created psychological safety by allowing me to own the message about my decision – what got said, by whom, and when. And I had every reason to trust my employment was never at risk, nor did I sense there would be hidden political implications or surprise consequences. In fact, this decision doesn’t preclude me from future promotions.

What is your workplace culture like when it comes to career mobility?

Is “up” the only direction? Do you lose team members because they need to go to grow? Or do you have an opt-out path, framed in safety and belonging? Are there alternative paths that still reflect success and embrace an individual’s experiences, strengths, and skills? How do you make these options more than just words?

I’d love to hear from you. Use the form below to share your thoughts.

Do your design and delivery create the right environment?

Psychological safety is a hot topic in discussions about organizational culture. Moreover, business leaders seem to understand that safety, empathy, trust, and belonging are critical to the well-being of both employees and organizations.

Recently, I had the opportunity to develop a course on these four components of culture. Our client believed that teaching leaders how to foster empathy, belonging, psychological safety, and trust would improve employee engagement, retention, DEI, and civility issues, helping the organization achieve its goals.

But simply talking about these four components wasn’t enough.

We needed to demonstrate them throughout the entire learning experience. This meant choosing words, imagery, and a course structure that allowed our audience to feel safe and stay engaged while they worked through vulnerable and challenging topics.

How did we do this?

1. We chose language that avoided direct reference to gender identification, race or ethnicity, age, or disability status. For example, we would refer to “team members” and “supervisors” without specific demographic references.
2. We used stories to make the concepts relatable. Storytelling engages our minds and hearts. It taps into our capacity for empathy. We didn’t just want to teach about these concepts, we wanted the learners to experience them. For example, we used stories and scenarios that featured the “whole person” at work. We also used videos from recognized experts like Simon Sinek, who taught about trust through a story. We relied on powerful Ted Talks to teach about assumptions.
   

   We use “paper people” and stick figure imagery with no race, age, or gender.

3. We carefully selected visuals that were inclusive but not specific. What does this mean? For example, we used pictures of hands coming together in a group; the hands represented different skin tones and different genders. We avoided images with faces that might reinforce the assumptions our brains already create. We used “paper people” and stick figure imagery with no race, age, or gender.
4. We used visuals that were inclusive and specific. Sometimes we just needed to include faces. So, we made sure the faces in our imagery and case studies were representative of the team members in our client’s organization.
5. We called attention to our brains’ tendencies toward assumptions and biases. We made a lesson out of this very real human function, and then taught how awareness can help us set those stories aside to be replaced by openness, curiosity, and empathy.
6. We set a group agreement to protect confidentiality. We made it ok to share what participants learned in the workshop but agreed not to share what other participants said.
7. We started and ended with “your one word.” This workshop was delivered virtually, so we needed to intentionally build a sense of connection. We started with introductions that included name, team, location, and “your one word.” Each person shared a word to describe how they were feeling coming into the workshop that day. We heard everything from “excited” and “motivated” to “stretched” and vulnerable.”
8. We included group and individual activities. Not everything has to be shared to be learned. Particularly for topics like these, the learners needed time to reflect and apply at an individual level. They did this through self-assessments, confidence checks, and application activities focused on specific members of their teams. They also worked in groups on case studies so they could benefit from ideas and takeaways from their peers. Whenever appropriate, we did whole group debriefs so participants could benefit from different thinking and ideas.

Most importantly, we reviewed the concepts, the content, and the visuals with our client advisory team to make sure each aspect would land well. We had to check our own stories and assumptions about what would be effective and open ourselves to the feelings and experiences of the advisors. In other words, we had to practice what we were preaching in our own course.

Do your design and delivery create the right environment? Tell us about it using the form below.

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.

Make your training sound as good as it looks.

One of the best compliments I’ve ever received about a course I developed was “Hey! Completing that module wasn’t too bad!”

Victory!

Breaking news: most people find eLearning monotonous. We can create effective eLearning solutions that satisfy all learning objectives, but there’s a difference between doing the job correctly and doing the job well.

eLearning primarily engages two, maybe three senses: sight, hearing, and touch. Touch is typically limited to mouse, keyboard, and touchscreen interaction. Sight dominates the big three; designers focus most of their brilliance on satisfying the learner’s eye. Visuals are often meticulously crafted with careful attention to organization-approved palette, font, and imagery,

The sense of hearing is often neglected. It is often…dare I say…an afterthought. But it shouldn’t be.

Through careful integration of audio, we can rebalance the engagement of our senses, enhancing the immersive nature of our eLearning solutions.

Here are three recommendations.

1. Use audio strategically.

Recognize that there is no one-size-fits-all approach. Different courses benefit from specific audio enhancements.

• Technical eLearning: Use voiceover narration to break down complex topics and reduce on-screen text.
• Gamified eLearning: Use subtle background music to create a more immersive and enjoyable atmosphere. Integrate intentional sound effects (object entrances, etc.) to further enhance the experience.

Have you ever watched an instructional video that has loud background music blaring in the background? Avoid overuse of audio to prevent distraction.

Select audio elements that complement the content. Sound effects such as button clicks can engage the learner but be mindful of the context. In many cases, subtlety is key.

Consider the learner and their environment.

Recognize the diverse needs and environments of learners. Give learners control over audio features, such as volume and playback options, so they can tailor their experience.

• Optimize audio features to accommodate varying learner needs and environments. Where will they be completing this eLearning? For example, if the setting is a noisy office, narration may have to take a back seat.
• Offer closed captions. For learners who are hearing impaired, this is crucial to ensure equal access to content.
• You get bonus points for allowing adjustment of individual audio components (background music, narration, sound effects).

Create high-quality and purposeful audio content to maximize impact.

Consider alternatives to narration, like insights, explanations, or immersive storytelling.

2. Ensure high-quality audio.

• Use good audio files. For example, wav files are higher quality than mp3 files (though wav files are bigger).
• Select great narrators. If you’re using AI, make sure inflections and pronunciations are carefully adjusted.
• Recording in a conducive environment (if you’re not using AI).

3. Tailor audio to the course content.

• If it’s a scenario-based eLearning module that simulates on-the-job experiences, replicate relevant environmental sounds.
• If it’s a software simulation, use the exact button clicks sound effects that one would experience when using the software.

If you give equal enthusiasm to auditory and visual elements, consider the learner’s surroundings, and guarantee high-quality and purpose-driven audio content, you’ll level up your eLearning from a monotonous task to a more effective, engaging experience.

Our advice: consider welcoming back this old new trend.

In just the last week, I’ve read several articles heralding the arrival of a new trend among office workers: Chronoworking. The term refers to the practice of adjusting your work schedule to align with those times of the day you’re most productive.

The only problem with this new trend? It’s not new.

In ages past, individual workers naturally gravitated toward work schedules that were most productive.  It was only as we entered the Industrial Revolution (with synchronized looms and mills) followed by the Information Age (with its cube farm/corner office dichotomy) that rigid scheduling became the norm.

But even then, there were notable exceptions. Thomas Edison famously took up to three naps a day; he found that the breaks in work allowed for new thoughts or solutions to a problem, and he had a pen nearby to capture thoughts upon waking.

Chronoworking: the practice of adjusting your work schedule to align with the times you’re most productive.

Growing up, I often watched my mom unpack files and manuals on government procurement from her bag and set them on our kitchen table to work on; she tended to do her best work in the evening hours. (With three boys at home, I can’t imagine how our house was conducive to work, but she found a way).

When I worked in an office, I would arrive an hour or more before the workday began; I found that I could accomplish more focused work in those first two hours of deep concentration than I could in the next nine hours.  Working from home, it’s not unusual for me to tackle one or two tasks between 4:30 and 5:30 am, go to the gym, and then return home to “begin” my workday.

Chronoworking is at a new point of inflection. Though working outside traditional office hours has been a “trend” for as long as people could carry home a briefcase, it’s gotten a boost from recent world events and innovations. VPN connections and cloud platforms make it easier. Covid made it normal; the abrupt work-from-home transition necessitated some work hour flexibility that people aren’t keen to relinquish during the return-to-office wave.

It’s now so ubiquitous that we feel we can say it out loud: We don’t all work well at the same times. That’s okay.

So, if you are a leader in your organization and you see this “trend” on the horizon, what do you do?

• Think about your own work patterns. I struggle to think of one executive or entrepreneur who does not (instinctively or intentionally) structure their work patterns to leverage their most productive times of the day. In fact, most leaders get to where they are in large part because they optimize their work patterns. If you have benefited from work flexibility, shouldn’t your employees?
• Foster trust and ownership. You hired great people, right? So let them be great. Give them some choice in the way they deliver on their mission. Working at the right times doesn’t just make people more productive, offering choices makes them feel in control and trusted, which is motivating. If you really need team members to hold down the pneumatic lift on an office chair between 8 AM and 5 PM to feel they’re productive, are they really the best people for your organization anyway?

We don’t all work well at the same times. That’s okay.

• Communicate clearly and intentionally. Employees using flexible work schedules must have stated expectations and accountability. And they need to understand the purposes and benefits of work flexibility. Be intentional in the balance between flexibility and cohesion. For example, create common times when the team comes together, virtually or physically. This sends an important message: While we all work differently, we are one team working toward a goal together.

Allowing chronoworking is a change for many teams, and we know that change is hard. We also know that the most successful organizations embrace change.

Leading change management in your organization? These are signs you don’t want to see.

Any organization can go from Point A to Point B on a project, but if you want to get there in one piece and ready to reap the benefits, you need great change management. If your organization is on a change journey and you’re feeling uneasy, look for these signs you might be doing change management wrong.

1. People are telling different stories about what’s happening.

If there’s confusion surrounding the change, its progression, or the future state, it’s a clear indicator that something’s wrong. Clear and consistent communication is crucial at every stage of the change process to ensure that everyone understands what’s happening and why.

Make sure you have:

• A simple message framework that outlines why the change is happening, what the change is, how you’ll move forward, and what the result will be.
• Executives aligned on that framework, so they don’t need emails or PowerPoint decks to speak authentically on the change.
• A change network of key people embedded in stakeholder groups.
• Communication assets and channels to arm your change network as they spread the right information.

2. Employees are avoiding project activities.

Resistance often arises because employees simply fear what they don’t understand. They might worry about job security, lack of confidence in new skills or behaviors, or how their roles might change.

• First, be as transparent as possible. If you don’t tell people what’s happening, they will fill those gaps on their own.
• Second, allay those fears by building the right comparisons into your communications. Creating connections between your change and other experiences makes people feel it’s familiar, which turns off fear, makes the change feel valuable, and helps people remember it.

3. Employees are less happy.

A decline in employee morale and productivity is a big red flag that your change management approach is not hitting home with your staff. They might feel that they have no control over what’s happening, and they won’t be able to perform. Those in managerial positions might resist a change that takes away responsibilities or decisions.

Even a big, challenging project shouldn’t leave people down in the dumps. One cure for the slump is to create a sense of optimism for the future. That means two things: success and control.

• Engineer small wins early in the project. Look for ways to make stakeholders think “I was successful with that. I can do something like this again.”
• Then let them take the wheel for a bit. Involve stakeholders in decisions, mapping out the journey, and framing the new possibilities for their teams. Give them choices between solutions, locations, timeframes, etc. Having input into one’s future is a powerful boost. Adding choice, structure, and predictability makes a big difference.

4. Employees are saying it’s not right for their team.

If everything about your project just feels wrong to employees, or worse, directly conflicts with how employees work and succeed day to day, you’ll fail.

• First, seek to understand your organizational or team culture. If you haven’t already, put it into words. List the unwritten rules for success in your workplace – things like values, norms, and communication styles.
• Then, intentionally build them into the change management strategy and activities. If project communications and activities just feel right to people, you’ll foster acceptance and adoption.

5. You’re getting déjà vu.

Are you seeing or hearing about some of the same problems over and over throughout your project? Or are they similar to issues you faced during other projects? Maybe you’re not getting enough intelligence to act on. You need ways to capture and address feedback and lessons learned.

• Early in the project, assess your change readiness in key areas. That will give you a chance to get ahead of issues.
• During the project and after implementation, conduct pulse checks and gather stakeholder feedback through your change agent network.
• Document lessons learned from the project team and stakeholder groups at the end of the project. Then make sure you store, share, and socialize them. Better yet, build “change history check” into your organization’s methodology.

Change is hard…

An organization’s change journey can make everyone feel uneasy, but it doesn’t have to be that way. Look for the signs discussed in this post to avoid doing change management wrong. If (and more realistically, when) problems pop up, turn them into opportunities. See these valuable signs for what they are, correct course and get your change management right.

Use your organizational values as a compass in an automated world.

Imagine walking into a workplace where decisions are made at the speed of light, tasks are completed with superhuman precision, and innovation is not just a buzzword but a daily reality.

This is the vision many organizations are chasing as they adopt artificial intelligence (AI). But as the AI landscape continues to evolve, some organizations are simply running to keep up, with no clear destination.

How do you know if you’re headed in the right direction? Our tip — check each milestone against your organizational values.

Why Values Matter in the Age of Automation

Without a strong set of values guiding AI, organizations find themselves in a maze of ethical difficulties and impersonal interactions.

For instance, what if an organization deployed AI chatbots for customer service without adequately addressing their limitations? This could frustrate customers and badly damage the brand.

Don’t automate processes without considering the implications and checking them against your values. Automation should enhance, not replace, the human touch. Every outcome should be aligned with the organization’s mission, vision, and values.

Without a strong set of values guiding AI, organizations find themselves in a maze of ethical difficulties and impersonal interactions.

The Role of Values in Decision-Making

Just because we can, does it mean we should? What guides our organizational decisions?

AI systems learn from historical data, which can contain biases. If the data are biased, the AI model might spread those biases. Imagine an AI-powered hiring tool that inadvertently discriminates against certain demographics due to biased historical hiring data. This could lead to unfair employment practices and even legal repercussions.

If, instead, the organization embeds its values into decision-making, it creates a culture of consistency and trust. Employees and other stakeholders understand that company actions are founded on those values.

Values and ethical rules should guide our decisions, not software features. Values ensure that as we delegate tasks to machines, we’re not also outsourcing our ethical responsibilities.

Just because we can, does it mean we should?

Protecting the Human Heart in a Digital World

As we embrace the incredible potential of advanced automation, let’s not forget the human heart beating at the core of our organizations. It’s the passion of the people, guided by clear and compassionate values, that will ensure technology enhances our work rather than defines it.

For instance, a hospital may have AI-driven diagnostic tools that are incredibly accurate, even revolutionary. But healthcare workers know that delivering a diagnosis without empathy will cause patients anxiety and distress. The most successful organizations will be those that harness the power of automation without discarding human insight.

Automation should enhance, not replace, the human touch.

So, let’s program our future with not only intelligence, but with wisdom and foresight. As our capabilities grow, so can our humanity.

Three Takeaways for Optimizing AI

Values are the compass. In a world steered by automation, clear organizational values provide direction and purpose, ensuring that every technological advancement serves the greater mission.

Ethics determine the heading. As automation becomes more prevalent, the temptation to prioritize efficiency over ethics can grow. Maintaining clear values helps resist this temptation and fosters a culture of integrity.

Advanced automation is a crew member, not the captain. While automation can greatly enhance efficiency and decision-making, it should not inhibit the passion and judgment of the people that make up the organization.

As the lines between human intuition and AI are blurring, clear organizational values have never been more crucial. As we sail into the uncharted waters of AI, these values are the stars by which we navigate, ensuring we don’t get distracted by shiny new software and lose sight of our humanity.

Our government is apparently not a fan of TikTok, but they seem to love other innovative technology — especially AI. US federal agencies are starting to harness the power of generative artificial intelligence (AI) to improve efficiency, decision-making, and service delivery.

For instance, the Department of Health and Human Services (HHS) could use generative AI to model complex public health scenarios, helping them form policies and response strategies. Similarly, the Department of Defense (DoD) is exploring generative AI for simulation and training purposes, to give personnel realistic and varied practice scenarios.

AI promises big benefits, but beware — there are three pitfalls government teams should consider as they approach AI projects.

Consider ethics and policy.

As federal agencies adopt generative AI, they must keep ethics and policy implications at the forefront. They need clear guidelines on data usage, privacy, and security. They must also ensure that AI-generated content is unbiased and equitable; government decisions based on AI outputs can have significant impacts on the lives of US citizens.

As federal agencies adopt generative AI, they must keep ethics and policy implications at the forefront.

Hire and train for the AI-enabled agency.

Generative AI will change the work performed within federal agencies. This is a good thing; AI can take over repetitive tasks, freeing up human workers for more complex and creative work. But that workforce must be prepared to get all the benefits of AI. Agencies should consider AI technology skills as they recruit and hire. They must also invest in training to help employees perform in an AI-augmented workplace.

Generative AI will change the work performed within federal agencies. This is a good thing.

Manage it like any other change.

Integrating AI technology into federal agencies is an organizational change, like any other. Agencies will not see the workforce adoption they need – and the benefits they expect – without effective change management. Dedicated change management teams help federal organizations navigate the complexities of the new technology, address resistance, and promote employee engagement and adoption. The right communication, training, and support minimizes disruption and maximizes the benefits of generative AI, fostering an environment where innovative tools like AI enhance employee performance and service delivery.

Dedicated change management teams help federal organizations navigate the complexities of new technology.

Generative AI offers federal agencies exciting opportunities to innovate and improve their operations. But each opportunity comes with the responsibility to implement AI ethically and support the workforce. As generative AI continues to evolve, it will be fascinating to see how federal agencies leverage this technology to serve the public better.