By J. H. Irwin
Author | Content Creator | Technology Strategist
For more than thirty years, I have done two things most people treat as separate careers
I build enterprise technology, and I write about what technology does to people. It took me a long time to realize these are not separate pursuits. In many ways, they are the same job.
Organizations often describe digital transformation as a technology initiative. They select a platform, approve a budget, assemble a project team, and begin building. Success is measured by whether the system launches on time, stays within budget, and meets its technical requirements.
Those things matter, but they do not mean transformation has occurred. A system can launch successfully while employees continue maintaining private spreadsheets, forwarding information through email, and relying on personal workarounds because the new technology never earned their confidence.
I have spent more than twenty years working inside large financial institutions and other complex organizations. My home has largely been the Microsoft ecosystem, including Power BI, Power Apps, Power Automate, SharePoint, Dataverse, and Microsoft Fabric. Across different platforms and business problems, the pattern remains remarkably consistent. Critical processes are often living in spreadsheets, email chains, disconnected documents, and one person’s memory.
Turning those processes into governed systems can be technically demanding, especially when they must withstand security requirements, audits, and regulatory scrutiny. Yet building the technology is only part of the challenge. The system must also make sense to the people whose daily routines it will change.
People Are Not the Problem
When employees hesitate to adopt new technology, they are often described as resistant to change. That description is convenient, but frequently unfair. People do not resist simply because they are stubborn or unwilling to learn.
They resist when they do not understand why the change is necessary, when decisions affecting their work are made without their participation, or when training arrives after the important choices have already been made. They may also remember previous technology projects that promised greater efficiency but created more work and frustration.
A familiar process can also become part of someone’s professional identity. The employee who maintains the spreadsheet, understands every exception, and knows how to correct every error may have spent years becoming indispensable. When a new system appears, that person may not see efficiency. They may see their expertise being transferred into software and wonder whether the organization will still value them.
That is not irrational resistance. It is a human response to uncertainty.
Communication Is Part of the Technology
Successful adoption begins before the system is built. The people closest to the work understand where the current process breaks, which exceptions matter, and which workarounds exist because the existing tools failed them. Their knowledge should help shape the solution from the beginning.
Training must also involve more than demonstrating buttons, menus, and screens. Employees need to understand what problem the technology solves, how it will improve their work, what will change, and where they can find help when something goes wrong.
This is where my years as a writer have influenced my work in technology. Writing taught me how to explain complicated ideas to intelligent people who do not share my vocabulary. People should not need to become technologists to understand how technology will affect their lives.
Instead of explaining that a new solution uses Dataverse, automated workflows, or an advanced reporting model, tell people what those capabilities mean. Information will no longer need to be entered three times. Approvals will not disappear inside an inbox. Leaders and employees will finally be working from the same numbers.
Those are outcomes people can understand and evaluate.
Trust Cannot Be Installed
Organizations can install software, configure permissions, migrate data, and automate processes. They cannot install trust. Trust develops when the technology works consistently, the information is accurate, employees feel heard, and leadership treats adoption as a shared responsibility.
If the system is unreliable or promised support never arrives, people will return to the tools they know. The old spreadsheet may be inefficient, but it feels safe because they understand it. Familiarity often wins when confidence in the replacement has not been earned.
The most successful systems I have built were not necessarily the ones with the most features. They were the ones that gave underwriters, risk teams, project managers, and executives information they could finally trust. They replaced fragile processes with something that could withstand both an audit and an ordinary difficult day.
As artificial intelligence and automation become more deeply embedded in the workplace, the human factor will become even more important. These technologies will reshape roles, redistribute knowledge, and cause many employees to question what they contribute and where they belong.
Organizations that dismiss those concerns as resistance will struggle. Those that recognize them as legitimate human questions will be better prepared to create technology that augments people instead of alienating them.
The future of work will not be determined solely by what technology can do. It will also be determined by whether people understand it, trust it, and believe there is still a meaningful place for them in the future it is creating.
Technology is changing the world. Read about it → The Augmented Life