Leadership transitions are almost always framed as transformation opportunities. And while transformation may be the ultimate goal, that's not where you start.

I've stepped into organizations at some of their most uncertain moments — colleges, universities, manufacturing operations — and the pattern is remarkably consistent. Processes are broken or inconsistent, priorities are unclear, employees are anxious, and leadership is looking for immediate answers from someone who just walked in the door.

The biggest mistake organizations make is expecting new leadership to arrive with a list of changes. That's the wrong instinct. The first ninety days aren't about moving fast. They're about listening, assessing, and understanding how the organization actually operates before you touch anything.

When I take on an interim assignment, I start with three questions: What's working and needs to be protected? Where are the operational risks? And what's getting in the way of results? You don't find those answers in reports. You find them in conversations — with employees, managers, front-line staff, faculty, leadership. How work actually gets done rarely matches what's on the org chart.

Stabilization is about creating clarity. Employees need to know what's expected of them. Leaders need to trust the information they're getting. Processes need to work consistently. Without that foundation, transformation efforts stall — not because the vision was wrong, but because the organization didn't have the operational discipline to sustain change.

Build the foundation first. The transformation follows.

Most technology implementations don't fail because of the software. They fail because of process design, communication, accountability, and change management. The technology gets the blame, but the root cause is almost always operational.

I saw this firsthand when I stepped into a higher education institution after a troubled Workday implementation. Payroll errors were mounting, employee confidence was eroding, and leadership needed answers fast.

When I dug in, the software wasn't the problem. What had happened was fairly common — existing processes were migrated into the new system without being evaluated first. Bad processes in a new system don't become good processes. They become more expensive, more complicated, and harder to fix.

Working with consultants and institutional stakeholders, we went back to basics. We reviewed workflows, simplified processes, clarified who owned what, and tightened controls. Payroll errors dropped significantly and trust in the system was restored.

Organizations consistently overinvest in technical readiness and underinvest in operational readiness. Before any major implementation, leadership needs honest answers to a few questions: Are our current processes actually effective? Do employees understand what the future state looks like and what's expected of them? Have we defined accountability clearly? Have we invested enough in training and communication?

Technology should make work simpler, not harder. The organizations that get this right aren't necessarily the ones with the best systems — they're the ones that treat people, process, and change management as seriously as the technology itself.

The system is just the tool. Leadership determines the outcome.

AI is no longer a future consideration. It's already part of everyday work, and the question has shifted from whether organizations will use it to how they'll use it responsibly and effectively.

As someone who has spent years helping organizations navigate change, I think HR leaders are uniquely positioned — and frankly, uniquely responsible — for shaping how AI gets introduced into the workplace. That doesn't mean HR needs to be the technology expert. It means HR needs to be the advocate for people, process, and governance while the organization figures out where AI fits.

Before adopting new tools, I encourage leaders to work through five honest questions.

What problem are we actually trying to solve? Too many organizations start with the technology and work backward. AI should support a real business need, not become the objective itself.

Are employees prepared? Adoption doesn't happen because a tool gets deployed. It happens because people understand what's changing, why it matters, and what's expected of them. Training and communication aren't optional steps.

Do we have governance in place? Privacy, security, ethical use, accountability — these aren't IT concerns alone. Organizations need clear policies before problems surface, not after.

How will we measure success? Without defined outcomes, you can't distinguish between AI that's creating real value and AI that's just creating activity.

Are leaders modeling the behavior? Employees watch what leadership does. Leaders who use AI thoughtfully set the tone for the rest of the organization.

AI has real potential to improve efficiency, communication, and decision-making. But organizations that chase the technology while ignoring people and governance tend to create new problems rather than solve existing ones.

The goal was never to replace people. It's to help people do their best work.

Most organizations don't pay attention to employee relations until something goes visibly wrong. By then, the damage is usually already done.

When a backlog of investigations, complaints, grievances, or workplace concerns builds up quietly, trust starts eroding before leadership even recognizes there's a problem. Employees who believe their concerns won't be addressed stop reporting them. Managers grow frustrated with inconsistent support. Leaders lose visibility into risks that are accumulating beneath the surface.

What starts as an administrative challenge becomes a cultural one.

I've seen this pattern more than once, and the most important reframe I can offer is this: employee relations is not a reactive function. It's a strategic one. Done well, it helps organizations identify emerging issues early, improve workplace culture, reduce legal exposure, and strengthen the relationship between employees and leadership.

When backlogs develop, the instinct is often to just close cases faster. That's the wrong focus. The real work is examining how cases flow through the system — workflow design, accountability structures, communication practices, resource allocation. Speed matters, but so does consistency and fairness. Employees don't expect perfection. They expect responsiveness.

Organizations that treat employee relations as a priority — not a back-office function — are consistently better positioned to maintain engagement, protect culture, and manage risk.

The longer issues sit unresolved, the harder they are to fix. That's why a backlog isn't an HR metric to manage. It's a business risk that leadership needs to own.

The workforce challenge facing higher education right now goes well beyond filling open positions.

Institutions across the country are dealing with retirements, leadership turnover, shifting employee expectations, enrollment pressures, budget constraints, and intensifying competition for talent — all at the same time. Any one of those issues is manageable. Together, they create a level of complexity most institutions haven't faced before and aren't structurally prepared to handle.

The hiring problem gets the most attention, but it's not the core issue. The deeper challenges are retention, leadership pipeline development, and building workforce strategies that can actually sustain the institution over time.

There's also a knowledge transfer risk that doesn't get nearly enough attention. Experienced employees are retiring and taking decades of institutional knowledge with them. That loss is hard to quantify and even harder to recover from once it's gone.

At the same time, the employees institutions are trying to attract and retain have different expectations than previous generations — flexibility, real career development opportunities, and a workplace culture that demonstrates investment in their growth. Offering a job isn't enough anymore.

The institutions that navigate this well will be the ones that treat workforce planning as a strategic function, not an HR administrative task. That means workforce strategy has a seat at the table alongside enrollment planning, financial planning, and institutional leadership — not as a downstream consideration, but as a core input.

People are still the most important asset in higher education. The institutions that invest in workforce planning now will be far better positioned for what's coming.

Most change initiatives fail for a surprisingly simple reason: organizations focus on changing processes while underestimating the people responsible for executing them.

Leaders often assume that once a decision is made, employees will follow. That's rarely how it works. Employees need to understand why the change is happening, how it affects them specifically, and what success actually looks like on the other side. Without that clarity, even well-designed changes stall.

Communication helps, but it's not enough on its own. Employees need real opportunities to ask questions, raise concerns, and feel like participants in the process rather than recipients of a decision that was made without them.

What I've seen work consistently is this: visible leadership commitment, honest and consistent communication, and clear accountability at every level of the organization. And patience — which is the part most organizations underestimate.

The most common mistake I see is declaring victory too early. The new process is live, the rollout is complete, and leadership moves on. But adoption is still incomplete, old habits resurface, and the results that were expected never fully materialize. That's not a technology problem or a process problem. It's a reinforcement problem.

Sustainable change requires as much attention after implementation as before it. The work doesn't end at go-live.

Change is ultimately about people. The organizations that treat it that way — that invest in helping employees navigate transition rather than simply managing a project plan — are the ones that actually get to the outcomes they were after.

The goal isn't to manage change. It's to bring people through it successfully.