Across industries, AI agents are already taking on tasks that used to belong to analysts, coordinators, specialists, and even managers. They write code, resolve customer issues, generate reports, reconcile financials, schedule meetings, and run multi-step workflows with little or no human involvement. This is not a future scenario. It is happening inside organizations right now.

The impact is not limited to tools or systems. It reaches into roles, workflows, decision rights, staffing models, and the basic structure of how teams operate. Leaders who treat AI agents as a simple technology rollout will miss the true challenge, rebuilding the organization for this new reality.

AI Agents Change the Operating Model, Not Just the Tools

When an organization deploys AI agents, the biggest impact is not the technology. It is the redistribution of work.

Tasks that once required human judgment or coordination are suddenly automated. Job families shift from doing work to supervising, validating, or escalating it. Decision rights move. Workflows compress. Bottlenecks disappear. New ones appear.

This is not a communication and training problem. It is an operating model problem.

This is where modern change management earns its place at the table.

The New Mandate for Change Management

Redesigning Work Instead of Teaching New Tools

AI agents force leaders to answer questions that go far beyond adoption.

• What work becomes agent owned
• What work remains human owned
• What work becomes hybrid
• What work disappears
• What new work emerges

This is structured work redesign. It requires clarity, alignment, and leadership decisions that cannot be delegated.

Rebuilding Roles and Career Paths

When agents take over procedural work, human roles shift toward higher value activities.

• Exception handling
• Relationship management
• Creative problem solving
• Oversight and governance
• Decision making

Employees need to understand what their job becomes, not just how to use a new system.

Addressing Identity, Status, and Fear

AI agents do not only automate tasks. They challenge identity.

People who built careers on expertise now watch agents perform that expertise in seconds. People who once held organizational power see that power redistributed.

Ignoring this creates resistance, disengagement, and quiet attrition. Addressing it builds trust and stability.

Supporting Workforce Transitions

Some roles will shrink. Some will disappear. Some will evolve.

Modern change management helps leaders:

• Redeploy talent
• Build reskilling pathways
• Communicate with honesty
• Make humane decisions
• Maintain trust during disruption

This is where change management becomes a strategic partner to HR and the business.

Establishing Governance for Agent Driven Workflows

AI agents introduce new risks.

• Incorrect actions
• Over automation
• Compliance gaps
• Accountability confusion

Organizations need clear guardrails, decision rights, and human checkpoints. Change management helps build the operational readiness that keeps the business safe.

Why Leaders Need Change Management More Than Ever

Executives deploying AI agents face three pressures at the same time.

1. Productivity expectations from the C suite
2. Workforce anxiety from employees
3. Operational risk from untested automation

Change management is the only discipline that sits at the intersection of all three.

It helps leaders:

• Redesign the work
• Prepare the workforce
• Protect the business
• Maintain trust
• Deliver outcomes

In short, change management becomes the strategy for navigating the human side of automation.

Who Owns Change Management for AI Agent Work

The leaders who feel the impact first are the ones who bring in OCM support.

CIOs and CTOs

They are integrating agents into systems and workflows and need clarity on how people will interact with those systems.

COOs and Operations Leaders

They own the work being automated and must redesign processes and roles.

CHROs and Talent Leaders

They are responsible for roles, skills, workforce planning, and reskilling.

CFOs

They are reshaping cost structures, staffing models, and productivity expectations.

PMOs and Transformation Offices

They manage enterprise change and need a structured approach to agent-driven transformation.

Business Unit Executives

They own the outcomes, the people, and the disruption.

These leaders do not need communications and training. They need organizational redesign, workforce transition strategy, and operational readiness.

The Bottom Line

AI agents are not a technology change. They are a workforce change, a process change, and a shift in how value is created.

Organizations that treat agent deployment as an IT rollout will struggle. Organizations that treat it as an operating model transformation will move ahead.

The professionals who can guide that transformation are the change leaders who understand both the human and structural implications of AI driven work.

The post AI Agents Are Changing Work. Leaders Need a Plan for the People Side. appeared first on LaForce Teamwork.

This level of automation creates real disruption. It affects roles, identity, staffing models, and the basic structure of how teams operate. Leaders cannot avoid these impacts, but they can manage them with clarity and respect. This article outlines a practical playbook for navigating workforce disruption in a way that protects the business and treats people with dignity.

Tell the Truth Early

People can handle reality. They do not like surprises. When AI agents begin to reshape work, leaders should communicate early and directly.

Share what is changing, why it is changing, what decisions are still open, and what support will be available. Silence creates fear and speculation. Straight talk builds trust, even when the message is difficult.

Define the New Work Before Talking About Jobs

Never announce job impacts before the work redesign is complete. People need to understand the future state before they can understand their place in it.

Leaders should first define how work will flow, what tasks become agent owned, what tasks remain human owned, and what new responsibilities emerge. Only then can job impacts be communicated with accuracy and fairness.

Give People a Path, Not a Promise

Vague reassurances do more harm than good. Instead of promising that everyone will be fine, leaders should provide clear pathways.

These pathways may include reskilling, upskilling, internal mobility, or transitions to new roles. They may also include honest conversations about fit. People respect clarity more than false comfort.

Support Managers Relentlessly

Managers carry the emotional load of change. They answer the questions, absorb the frustration, and guide their teams through uncertainty. They need support.

Provide talking points, FAQs, coaching, and guidance on difficult conversations. Give managers space to process their own reactions. When managers feel steady, teams feel steady.

Treat Exits With Dignity

If roles are eliminated, the organization must handle exits with care. Communicate clearly. Avoid euphemisms. Provide transition support, coaching, and placement assistance.

How an organization handles exits defines its culture more than how it handles promotions. People remember how they were treated when the news was hard.

Monitor the System and Adjust

AI agents improve quickly. Operating models must evolve with them. Leaders should review workflows regularly, update role definitions, adjust governance, and track outcomes.

This is not a one-time change. It is a continuous cycle. Organizations that monitor and adjust will stay ahead of disruption instead of reacting to it.

The Bottom Line

AI agents create real workforce disruption. Leaders cannot avoid it, but they can manage it with clarity, honesty, and respect. When organizations tell the truth early, define the new work, support managers, provide real pathways, and treat exits with dignity, they create stability during a period of rapid change.

This is the work that protects both the business and the people who make it run.

The post Managing Workforce Disruption in the Age of AI Agents appeared first on LaForce Teamwork.

I get it. You have a tough topic, a cross functional group, and a long list of competing priorities. You probably have several places you would rather be. ERP work is hard enough without adding a chaotic meeting on top of it.

If you knew the meeting was going to be difficult, you might have been better off handing the facilitation duties to someone with more experience leading high stakes project conversations.

When a meeting goes off the rails, I usually see three explanations.

1. Your facilitation inexperience.
2. The lack of a meeting plan.
3. The meeting should never have happened in the first place.

For this article, I’d like to tackle them in reverse order.

Weak Meeting Purpose

Meetings are expensive. During an ERP implementation, they are even more expensive. Every hour you pull people away from testing, design, data cleanup, or training has a real cost.

If you are going to ask people to attend a meeting, you need a clear and meaningful reason. If you do not have one, people will avoid the meeting if they can or resent being there if they cannot.

Let me share a story.

I once attended a community meeting about redesigning a major road. The purpose was never clear, and that should have been my warning. We spent ninety minutes developing a vision for improvements. At the end, the leaders told us there was no funding for any of the ideas we had just created. Instead, we needed to focus on crosswalk design at three intersections.

Seriously. They waited until the end to tell us the real purpose.

Everyone I talked with afterward felt the same way. We had wasted our time.

The same thing happens in ERP projects. Even the best facilitator cannot rescue a meeting built on a weak or misleading purpose.

Two meeting types are especially vulnerable: staff meetings and project update meetings.

People defend them with reasons like these:

• Staff meetings keep everyone on the same page.
• Everyone should know what their teammates are doing.
• This meeting forces people to complete their work.
• We need meetings to build teamwork.

Maybe there are good reasons to bring people together, but you will need stronger arguments than these.

And sometimes the real reasons are not so noble.

• Make people think they had a say in a decision that is already made.
• Ask for input to look like I care, even though I will not use it.
• Run meetings because it makes me look important.

If any of these sound familiar, promise me you will never use them again.

No Facilitation Plan

Let’s suppose you do have a good reason to meet. You have clear goals and a real need to bring people together.

If you succeed, people will walk away feeling the meeting was worth their time.

The first step in planning is to identify the goal.

Next, think about the strategies you will use to work toward that goal.

Then work through the details.

• Who should attend and why.
• How much time you need.
• When and where the meeting will happen.
• What activities will occur and in what order.
• What trouble you expect and how you will prevent it.

You may have created an agenda, but do you have a real plan behind it? If not, your chances of success have gone way down.

Ineffective Facilitation

Running meetings requires skill. You may not have those skills yet, or you may not be using what you know.

I cannot guarantee every meeting will be a success once you improve your facilitation skills, but I can promise your batting average will go up.

Here are a few things you should be able to do.

• Set the stage for the meeting.
• Tee up a topic.
• Involve everyone in the conversation.
• Keep the group focused.
• Help the group develop options.
• Help the group make a decision.
• Address conflict.
• Manage the clock.
• Deal with troublemakers.
• Keep the environment safe and friendly.
• Sum up the results.
• Develop next steps.
• Evaluate the meeting.

And that is just the big list. You can drill down and find a hundred more.

Bad meetings aren’t an accident

You can set most meetings up for success by doing three things:

1. Make sure there’s a darn good reason for the meeting.
2. Build a plan that leads towards your objectives.
3. Let a strong facilitator run the meeting.

To learn more, I suggest you download a copy of my book, Meeting Hero.

If you want to tackle the problem of bad meetings throughout the organization, then we ought to talk.

The post This Is Why Your Meeting Went Off the Rails appeared first on LaForce Teamwork.

But teamwork during a D365 implementation is a different story. The idea of a single weak link does not hold up. The person you think is slowing things down may not be the real issue at all.

In ERP projects, the so‑called weak link is almost never obvious. You might be quick to point to one person, but would that person agree. Would the rest of the project team agree? And what criteria are you using? Your view of what strong looks like may not match what the project actually needs.

Two perspectives

Here are a few examples I see all the time on D365 projects. Take a look at these potential weak links and tell me which deserve the label:

People who do the least because they don’t do their fair share
OR
People who do the most because they cover for the slackers

People who are cranky because they bring everyone down
OR
People who are sunny because they aren’t realistic

People who are loud and opinionated because they make everyone uncomfortable
OR
People who are quiet and timid because they don’t contribute their insights

People who have the least knowledge because they don’t catch on quickly enough
OR
People who have the most knowledge because they don’t examine basic assumptions

Then there are the folks who sit in the middle. They are pleasant and steady, but they do not push the project forward. In an ERP implementation, that can be its own kind of weak spot.

Whenever we try to identify the weakest link, we bring our own preferences and working styles into the judgment. On a D365 project, that is risky. The real issue is often not a person at all. It is unclear roles, missing processes, poor communication, or a lack of readiness.

When problems surface, the easy move is to blame the people who are not doing things the way we would. Instead, I look at the whole system. Everyone’s contribution, including my own, is part of the picture. That is where the real insight lives.

Capitalize on the differences

A better approach is to examine the differences on the team and figure out how to use them to strengthen the implementation. D365 projects need a mix of perspectives. Super users, end users, functional leads, and technical experts all see the system differently. That diversity becomes a strength only when we appreciate it and find creative ways to put it to work.

When we stop hunting for the weakest link and start looking at how the team fits together, we build a stronger project and a smoother path to adoption.

The post Identify Your Team’s Weakest Link—If You Can appeared first on LaForce Teamwork.

Collaboration is not a mindset or an attitude. It is action. It is the way you behave with others on your team, especially when the organization is changing processes, roles, and technology at the same time.

Here are eight behaviors your teammates should see from you if you want to be known as collaborative during an ERP project.

Share information

ERP implementations fall apart when people keep information to themselves. Transparency helps others anticipate issues, coordinate work, and offer support. Your teammates cannot help you if they do not know what you are working on.

Consider sharing information about your availability, goals, current priorities, project progress, ideas for improving processes, concerns, questions, and reactions.

If openness is not your normal approach, it may feel risky. Work through the discomfort. ERP projects require visibility, alignment, and shared understanding.

Openness is the foundation for effective collaboration.

Ask for feedback

ERP success depends on continuous improvement. No one has the full picture, and everyone sees different risks and opportunities.

Invite feedback from others. Ask for input after you run a meeting. Share a draft communication before sending it. When you have a big idea, ask your team what you might be missing.

Collaborative team members seek feedback because they want better outcomes, not because they want praise.

Provide feedback

Some teammates may not ask for feedback. Offer it anyway when you believe it will help them succeed.

There are two reasons to provide feedback. First, you want your teammate to understand what they did well so they can repeat it. Second, you want them to understand where a different approach might be more effective.

Make your feedback timely, specific, and supportive. ERP projects move quickly, and people need real-time guidance to stay aligned.

Receive feedback well

This is the behavior that makes a feedback culture possible.

Show people that you appreciate their willingness to share their thoughts. If the feedback is helpful, say so. If you disagree, thank them anyway. A simple response like, “Thanks for sharing your perspective. You’ve given me something to think about,” keeps the door open.

ERP projects require trust. How you receive feedback determines whether people will speak up again.

Problem-solve with others

You do not need to solve every ERP-related problem on your own. Collaboration means bringing other brains into the process.

This might involve a formal problem-solving session or a quick one-on-one conversation to explore ideas. ERP work is interconnected. Solving problems together leads to better decisions and fewer unintended consequences.

Look out for stakeholders

Collaborative people think beyond their own tasks. ERP changes affect many groups, and a decision that helps one team may create problems for another.

Identify stakeholders who might be affected by your actions. Talk to them. Adjust your approach if the impact on others is too great.

ERP success depends on cross-functional awareness. Silos are the enemy of adoption.

Offer support whenever you see an opportunity

Collaboration means recognizing that you and your teammates share a common goal. Even if someone else owns a task, they do not need to carry it alone.

Offer emotional support when the work gets stressful. Offer practical support when workloads spike. ERP projects are demanding, and small acts of help make a big difference.

Engage in healthy debate

ERP decisions are complex. People see issues differently. Healthy debate helps teams vet ideas and choose the best path forward.

This is not fighting. It is working together to find the strongest solution. Engage fully. Be kind. Stay focused on the problem, not the person.

Healthy debate is a hallmark of collaborative teams.

Are you collaborative?

Collaboration is about better ideas and mutual support. It is expressed through specific behaviors. Now that you have seen what they are, your next step is to determine whether you are behaving in these ways.

If not, choose one behavior to strengthen. Make a plan. Practice. Ask for feedback. When you have mastered it, choose another.

ERP upgrades succeed when teams collaborate well. Strengthening these behaviors will help you contribute to a highly collaborative, highly successful implementation.

The post Collaboration During an ERP Upgrade: Eight Behaviors That Make the Difference appeared first on LaForce Teamwork.

Every organization has a culture. If you ask employees how things work around here or what behaviors get rewarded, you will quickly hear the truth about the culture’s dominant characteristics.

During an ERP upgrade, these cultural patterns matter more than ever. Technology changes are easy compared to the behavioral shifts required for people to adopt new processes, new roles, and new ways of working. If the culture is not aligned with the goals of the ERP implementation, the project will struggle no matter how strong the software is.

Culture is a collection of habits

It can help to think about culture the same way you think about individual habits. Habits develop over time. Some help. Some do not. Some are visible. Others operate quietly in the background and cause problems without anyone realizing it.

Culture works the same way. Your company, division, or department may operate in a manner that slows progress or creates unnecessary friction. The pattern might be obvious or it might be hidden. Either way, an ERP upgrade will expose it.

ERP projects require people to change how they work. If the culture resists change, avoids accountability, or tolerates workarounds, the system will never deliver the value you expect.

Cultures can change

Individuals can change their habits, and organizations can change their cultures. It is not easy, but it is possible.

Sometimes culture shifts when a new leader arrives with different expectations. Other times, leaders intentionally identify cultural characteristics that need to change and take action to make that shift happen. ERP upgrades often require this kind of purposeful cultural reset. The organization must adopt new behaviors to keep up with market demands, regulatory requirements, or the operational improvements the new system is designed to support.

The change might involve strengthening a positive behavior or eliminating a problematic one. The most effective cultural transformations do both.

If you want help with this work, visit our culture change service page.

Ten cultural shifts that support a successful ERP upgrade

A culture change begins by identifying the shift you want to make. If you already have ideas, choose the one that will have the greatest impact and start there. If you need inspiration, here are ten cultural characteristics that often need attention during ERP and digital transformation projects.

1. Data driven

ERP systems are built on data. If your organization relies on opinions, instincts, or persuasive personalities instead of evidence, decision quality will suffer. A data-driven culture values measurement, analysis, and fact-based decisions. This shift is essential for organizations that want to use their ERP system to improve performance.

2. Customer focused

ERP upgrades often disrupt workflows that affect both internal and external customers. A customer-focused culture keeps the purpose of the work front and center. Employees understand who they serve, what those customers need, and how the new system helps deliver better outcomes.

3. Proactive

Many organizations reward firefighting. ERP systems require the opposite. A proactive culture values planning, prevention, and early problem solving. This reduces drama, improves stability, and helps the system operate as intended.

4. Responsible

ERP implementations expose gaps in ownership. When employees say it is not my job, progress slows. A responsible culture encourages people to take action when something needs attention, regardless of whose job description it falls under.

5. Action oriented

ERP projects involve decisions, testing, and continuous improvement. Organizations that overthink, overmeet, or delay decisions struggle. An action-oriented culture values progress over perfection and keeps the project moving.

6. Transparent

ERP upgrades require clear communication. Closed doors and secrecy create confusion and rumors. A transparent culture shares information openly unless there is a compelling reason not to. This builds trust and reduces resistance.

7. Assertive

Assertiveness is the ability to say what needs to be said in a direct, honest, and respectful manner. ERP projects fail when people stay silent about risks or concerns. They also fail when communication becomes aggressive or political. Assertiveness creates healthy dialogue and better decisions.

8. Process minded

ERP systems depend on standardized processes. If everyone does the work in their own way, the system will not function properly. A process-minded culture values consistency, clarity, and continuous improvement. This shift is especially important for fast-growth organizations that have outgrown their informal ways of working.

9. Improvisational

Some organizations are so rigid that employees freeze when something unexpected happens. ERP systems cannot anticipate every scenario. An improvisational culture teaches people how to adapt when needed and use good judgment when the process does not fit the situation.

10. Respectful

Some organizations get results but create a tough environment in the process. ERP upgrades add stress, deadlines, and pressure. A respectful culture helps people navigate the change without burning out or turning on each other. If you need evidence, check your turnover numbers.

Go to work

Changing culture takes a plan, persistence, and patience. Like any successful change initiative, it requires a compelling reason for the shift, involvement from employees, two-way communication, flexibility, and aligned incentives.

I can help by offering guidance and hands-on support. I would love to hear which cultural characteristic you want to change and work with you to build and implement a plan that makes it happen.

The post Culture Change During an ERP Upgrade: What Leaders Need to Understand appeared first on LaForce Teamwork.

You can build great materials, design hands‑on exercises, and schedule sessions at all the right times. But if employees don’t attend, none of it matters. And when people skip training, the consequences show up fast—confusion at go‑live, resistance, rework, and a support queue that never seems to shrink.

The good news is that training attendance isn’t random. It’s predictable. And with the right strategies, you can dramatically increase participation.

Here are ten ways to get employees into the room and ready to learn.

1. Communicate early, often, and through multiple channels

Training announcements get lost in the noise of an ERP project. You need a communication plan that includes email, manager talking points, intranet posts, team meeting reminders, and project champions spreading the word.

People rarely act on the first message. They act on the fifth.

2. Make managers accountable for attendance

Employees take their cues from their leaders. If managers say nothing, employees assume training is optional.

Give managers a clear message to deliver, a list of who on their team needs which sessions, and expectations for follow‑up. When managers reinforce the importance of training, attendance jumps.

3. Position training as essential, not optional

If training is framed as “nice to have,” people treat it that way. Your messaging should sound more like:

“This is required to do your job after go‑live.”
“You won’t be able to complete your tasks without this training.”
“This is part of our transition plan.”

Clarity drives action.

4. Make the relevance obvious

Adults show up when they understand why something matters. Spell out what tasks will change, what they’ll be able to do after training, and what problems the training will help them avoid.

If relevance isn’t clear, attendance will always lag.

5. Schedule training at times that work

Avoid month‑end, peak workload periods, lunch hours, and late afternoons when energy is low. Offer multiple options, including virtual sessions. Flexibility removes barriers.

6. Put training on the clock

If employees have to attend on their own time, they won’t. Training must be treated as part of the workday.

This sends a clear message: “This matters enough for us to make space for it.”

7. Create training that’s practical and hands‑on

People show up when they know the session will be useful. Design training that uses real scenarios, mirrors actual workflows, lets employees practice in the system, and focuses on what they’ll do on day one.

If training feels relevant and engaging, word spreads fast.

8. Use champions to promote training

Champions are your secret weapon. They can encourage peers, answer questions, reduce anxiety, and share their own positive experiences.

People trust colleagues more than project emails.

9. Close the loop with employees

Tell people what to expect:
“You’ll get hands‑on practice.”
“You’ll leave knowing how to complete your daily tasks.”
“We’ll support you after go‑live.”

And after training, ask for feedback and act on it. When employees feel heard, they stay engaged.

10. Track attendance and follow up

Don’t assume people will attend. Monitor sign‑ups and completions. If someone misses training, notify their manager, offer alternative sessions, and escalate if needed.

ERP readiness is too important to leave to chance.

Training Attendance Isn’t a Mystery—It’s a Leadership Strategy

When employees skip training, it’s rarely about the training itself. It’s about communication, culture, relevance, and leadership support.

When you address those factors, attendance rises. When attendance rises, adoption improves. And when adoption improves, your ERP implementation has a much better chance of succeeding.

The post How to Increase ERP Training Attendance: 10 Strategies That Actually Work appeared first on LaForce Teamwork.

As a leader, your job is to help your team stay focused, confident, and productive while everything around them is shifting. That requires clarity, empathy, and a steady hand.

Here is how I help leaders think about guiding their teams through disruptive organizational change.

Acknowledge the disruption

People know when things are changing. They feel the uncertainty long before the first announcement. Ignoring it does not make it go away. Acknowledge what is happening and give people space to react. When you name the disruption, you reduce anxiety and build trust.

Explain the reason for the change

Employees want to understand why the organization is making a shift. During an ERP upgrade, the reasons are often tied to process improvement, better data, stronger controls, or the need to scale. Share the purpose behind the change so people can connect their work to the bigger picture.

Clarify what is changing and what is not

Ambiguity fuels stress. Be clear about what will be different, whether it is roles, workflows, systems, or expectations. Just as important, tell people what is staying the same. Stability helps people stay grounded while they adjust to new realities.

Set clear expectations

When change hits, people want to know what you expect from them. Spell it out. Describe the behaviors, priorities, and responsibilities that matter most during the transition. When expectations are clear, people can focus their energy in the right direction.

Communicate early and often

One announcement is never enough. People need repetition, reinforcement, and updates as the change unfolds. Share what you know, even if you do not have all the answers. Silence creates confusion. Frequent communication builds confidence.

Listen to concerns

Change brings questions, frustrations, and fears. Make it easy for people to share what they are thinking. Listen without judgment. Sometimes people simply need to be heard. Other times they raise issues you need to address. Either way, listening strengthens your leadership.

Support people through the transition

Disruptive change requires emotional and practical support. Some employees will adapt quickly. Others will struggle. Provide coaching, training, and encouragement. Celebrate progress. Recognize effort. Help people build the skills they need to succeed in the new environment.

Model the behavior you want to see

Your team watches how you respond to change. If you stay calm, curious, and solution focused, they will follow your lead. If you resist or complain, they will too. Model the mindset and behaviors that will help the team move forward.

Keep people focused on the future

Change is easier when people can see where they are headed. Paint a clear picture of the future state. Describe how the team will operate once the dust settles. Help people imagine the benefits of the new system or structure. A compelling vision pulls people through the discomfort.

Moving forward

Disruptive change is challenging, but it is also an opportunity to strengthen your team. When you lead with clarity, empathy, and consistency, people stay engaged and ready to support the transition.

If you want help preparing your team for an ERP upgrade or navigating the disruption you are already experiencing, let’s talk. I have spent more than 30 years helping leaders guide their teams through complex organizational change.

The post Leading Your Team Through Disruptive Organizational Change appeared first on LaForce Teamwork.