Reduce fear, clarify priorities, and guide change through focused pilots, plain language, and disciplined learning.
By Project Brilliant Team
Featuring John Mergy, Co-Founder & CEO, M0dus Innovation — as heard on the Unlocking Momentum Podcast.
AI transformation is no longer a side issue for technology teams. Leaders are being asked to decide what is safe, what is useful, and what deserves attention while the tools keep changing.
The pressure persists because AI comes with hype, fear, technical language, and real operational risk. Teams still have to protect quality, manage sensitive information, and keep daily work moving.
This article summarizes a recent episode of the Unlocking Momentum Podcast featuring John Mergy, co-founder and CEO of M0dus Innovation, whose work includes AI transformation, alignment, and fractional CIO-related support. His background spans 38 years in technology and business, including nearly seven years as CIO at Do It Best Group.
The sections below break down how leaders can reduce uncertainty, reset complex initiatives, make AI easier to adopt, and build a steady operating rhythm for practical progress.
Large technology efforts rarely stall because of one tool alone. Momentum usually slows when scope expands, assumptions pile up, and teams lose sight of the next clear decision.
A useful reset begins with the reason the work exists. When leaders return to the why, teams can separate essential outcomes from old assumptions, added preferences, and technical noise.
Pressure grows when programs stretch across too many processes, people, and dependencies. Narrowing the next piece of work can protect quality while helping the team make visible progress again.
John describes initiatives of this scale as roughly 80 percent change management and 20 percent technology. That view matters because fear, ownership, culture, and clarity often determine whether a tool is adopted well.
This checklist gives teams a release valve without pretending the pressure is gone. It turns a sprawling effort into a shorter cycle with a clearer path forward.
Momentum returns when leaders make the work smaller, clearer, and more human. AI transformation needs that discipline before it needs another tool decision.
Fear grows when AI stays abstract. Leaders can reduce that fear by replacing vague claims with plain definitions, clear boundaries, and a realistic view of what the tools can and cannot do.
Many employees hear conflicting stories about job displacement, productivity, and risk. A basic shared vocabulary removes some of the mystery and gives people a safer way to ask practical questions.
Companies are asking whether AI tools are safe to use, especially when intellectual property and internal know-how are involved. That concern should be addressed directly before experimentation spreads across the organization.
Training should connect tools to work people already understand. Early use cases may focus on efficiency, but stronger adoption comes when teams see how AI supports better decisions, not just faster tasks.
These questions keep early AI use grounded in governance and purpose. They also prevent experimentation from becoming scattered activity with no clear owner or learning loop.
Safe adoption does not require leaders to remove every unknown. It requires enough clarity for people to try the right things in the right way.
AI changes the role of technology leadership because it touches operating models, workflows, information flow, and team structure. CIOs and IT leaders are positioned to lead beyond support if they build trust and speak clearly.
Technology teams often move through a maturity curve, from support function to trusted advisor to strategic partner. AI gives leaders a chance to move up that curve by shaping what the business could become.
Technical detail has its place, but it can lose a room when leaders need balanced guidance. Strong CIOs translate AI into outcomes, risks, tradeoffs, and decisions that other leaders can act on.
Strategic leadership is not only asking what the business wants next. It includes research, experimentation, and presenting practical use cases that show how work might change.
This posture helps reduce the old separation between technology and the rest of the company. It also gives executives a clearer basis for deciding where AI belongs in strategy.
The CIO opportunity is not to chase every new tool. It is to guide the organization toward better decisions with enough vision, credibility, and restraint.
AI progress needs a repeatable rhythm because normal operations can consume every available hour. Without protected time, leaders may understand the need to learn but never create the space to act.
Busy leaders cannot rely on leftover time for AI. Calendar blocks, learning groups, and intentional research habits create a practical way to keep pace without abandoning current responsibilities.
Pilots help teams test value, safety, and adoption before a larger commitment. The goal is to choose focused experiments that connect to a material, objective benefit for the company.
Trusted peers, support teams, and specialized partners can help leaders see options they would not see alone. Industry events and business directories can also point teams toward people with relevant AI experience.
A rhythm like this prevents AI work from depending on urgency alone. It gives leaders a way to learn, test, and adjust while daily operations continue.
The organizations that keep moving will be the ones that make learning part of the operating rhythm. A small, steady practice is easier to sustain than a burst of unfocused activity.
AI transformation works best when leaders treat it as disciplined change, not a race to adopt every new tool. Clear purpose, practical boundaries, and steady learning make progress easier to sustain.
The first lesson is to reset complexity before it overwhelms the team. A shorter milestone, a sharper why, and fewer assumptions can restore momentum without lowering standards.
The second lesson is to reduce fear with plain language and safe experimentation. People need to know what AI is, where the boundaries are, and how the work may affect them.
The third lesson is that CIOs and IT leaders have a strategic opening. Their value grows when they connect technology choices to business outcomes and help others see practical options.
For leaders facing uncertainty, the next step can be simple: protect time, choose one meaningful pilot, define the guardrails, and review what the team learns. That is how a broad AI problem becomes a manageable path forward.
Project Brilliant helps leaders move from AI adoption to measurable business impact through strategy, readiness, and disciplined execution.
Let's Talk