The Human Work of Transformation

Every major technology wave promises transformation. After living through several of them, I have come to expect something else entirely.

Enterprise systems promised integration. Analytics promised better decisions. Cloud technology promised agility, and digital transformation promised reinvention. Today, artificial intelligence is being introduced with equally ambitious expectations around productivity, innovation, and competitive advantage.

Each of these advances has expanded what organizations are capable of doing. Yet every one of them has also reinforced a lesson I encountered surprisingly early in my career: technology can change a process without changing the experience of the people responsible for carrying it forward.

As a young software developer, I worked on a project designed to modernize a cumbersome IMS green-screen application that employees had relied on for many years. Their work required them to move through several disconnected systems, follow a complicated series of steps, produce reports, cross-check information, communicate with colleagues, and return to other systems to complete the process. It was inefficient, difficult to navigate, and heavily dependent on institutional knowledge.

The new solution appeared to offer an obvious improvement. It simplified the interface, reduced unnecessary steps, and made information easier to access. From a technical perspective, the value seemed clear.

The response from the employees was far more complicated.

These were experienced professionals who had spent years learning how to navigate the existing environment. They knew every shortcut, every exception, and every person who could help move something forward when the normal process broke down. Their expertise extended far beyond operating the system. They had built relationships, developed judgment, and become trusted resources for colleagues who depended on them to make sense of a difficult process.

The new technology made much of that knowledge more visible and accessible. Work that once required their specialized understanding could now be completed more easily by others. Although the system simplified the process, the employees experienced the change as a potential loss of expertise, influence, and professional identity.

At the time, I thought we were asking people to learn a better system. In reality, we were asking them to reconsider how they created value.

That experience stayed with me because it revealed how much can be missed when a transformation is viewed primarily through the lens of implementation. A system may function exactly as designed and still fail to produce the outcome the organization expected. A project may be completed on time and within budget while the people closest to the work remain uncertain, disengaged, or quietly committed to preserving the old way of doing things.

Over the years, I began to see this pattern repeat across increasingly complex initiatives. Organizations invested significant amounts of time, money, and leadership attention in selecting platforms, building capabilities, and managing implementation plans. The strongest outcomes emerged when leaders also examined how the work needed to evolve, how decisions would be made, how teams would collaborate, and how people would continue to experience meaning and value in their roles.

Organizations are often capable of implementing technology. The more difficult work is redesigning the environment around it.

That environment includes far more than workflows and operating procedures. It includes relationships, decision rights, informal networks, incentives, expertise, trust, and the unwritten ways people learn to get things done. These elements may not appear on a process map, but they shape whether a new capability becomes integrated into the organization or remains something employees use because they have been mandated to do so.

This distinction feels especially important as organizations accelerate their investments in artificial intelligence.

Much of the current conversation focuses on models, platforms, agents, automation, and measurable productivity gains. Those questions matter, but they represent only one part of the transformation. Leaders must also consider how AI will reshape the nature of work, how responsibilities will shift, what knowledge will become more valuable, and how people will work alongside technology in ways that strengthen rather than diminish their contribution.

When employees are treated primarily as users, adoption can become a narrow exercise in training, access, compliance, and usage statistics. Organizations may count logins, clicks, prompts, or completed workflows and conclude that the technology has taken hold. Those measures can show activity, but they do not necessarily show confidence, commitment, or meaningful integration into the work.

A person can use a system without trusting it. A team can comply with a mandate without believing the technology improves the way they operate. An organization can report strong adoption while employees continue to rely on familiar processes, duplicate work outside the system, or wait for the initiative to lose momentum.

The deeper opportunity is to engage people as active participants in shaping a new way of working.

That requires leaders to understand the work closely enough to recognize where technology can genuinely help. It requires honest conversations about what people may gain, what they may lose, and how their contribution will continue to matter. It also requires involvement early enough for employees to influence the design, develop confidence in the direction, and become advocates before the technology is fully deployed.

The goal should extend beyond acceptance. Leaders should be building understanding, curiosity, capability, and ownership.

I see the importance of this human dimension in my coaching work today. Senior leaders understand that AI will affect their organizations, but many of their most pressing questions have little to do with selecting a tool. They are thinking about how to lead through uncertainty, preserve trust, prepare people for changing expectations, and make responsible decisions while the technology continues to evolve.

These are familiar leadership questions arising in a new technological context.

Every major technology wave introduces new possibilities, but possibility alone does not create transformation. Technology can expand capacity, improve access to information, and make work faster or more efficient. Lasting change depends on whether leaders are willing to examine the organization surrounding the technology and help people understand how they will contribute within it.

Technology expands what an organization can do. Leaders determine what the organization becomes.

---

About the Author

Karen R. Edwards is an executive coach, leadership advisor, and former Fortune 50 technology executive with more than three decades of leadership experience. She is the Founder of KE Speaks, where she publishes thoughtful perspectives on leadership, organizational transformation, and how leadership, people, and technology shape organizational outcomes.

Let's Continue the conversation on LinkedIn