The Discovery Gap
Many organizations believe that digital transformation is a technical problem. That’s not the case. Technology is the easy part. It grows rapidly. It works cleanly. It looks impressive on dashboards. What doesn’t match the same speed is behavior. And that’s where the transition quietly slips: the adoption gap.
The Time When Things Begin to Slip
There is a general timeline for most digital transformations:
- The forum is now live.
- Dashboards are available.
- The leadership team has visibility that it has never had before.
On paper, everything looks like progress. However, there is something tangible. Decisions are still made outside the system. Groups export data to spreadsheets. Workarounds started to appear—small at first, then common.
No one calls you a failure. But the promised value is never fully realized. This is not a technical problem. Failure to be found. And often, it’s a management gap.
When Revolution Really Fails
In digital and AI-led transformations, the real gap is not between strategy and execution. It is between distribution and acquisition. Organizations invest a lot of money
- Platforms.
- Tools.
- Infrastructure.
But very little intensity is used
- How will people use them.
- How decisions will change.
- How behavior will change at scale.
There is a vague idea: If we build it well, people will use it. They don’t. Not consistently. Not in the way the strategy aims. Because technology changes rapidly, behavior does not.
Questions We Keep Asking (And Why They Don’t Help)
Most of the top reviews still sound like this:
Are we on track with performance?
Have we finished the release?
What does the usage data show?
These are not bad questions. It’s not just questions that determine success.
They measure activity, not acquisition; progress, not impact. So, organizations are moving forward—sure, but not really succeeding.
What Changes When You Ask Better Questions
Change in any change is not a new tool or a new process. It is a change of question. When leaders start asking different questions, attention shifts. When attention changes, behavior follows. Because questions do more than gather information:
- They show what’s important.
- They make decisions.
- They define accountability.
Framework: Four Layers of Inquiry That Drive Discovery
Not all questions are equal. In the digital version, I find it helpful to think in four categories:
1. Operational Questions: Are We Sending?
These are the most common:
- Are we live?
- Are milestones being met?
- Is the system stable?
They are necessary. But they only tell you whether the technology exists—not whether it’s being used meaningfully.
2. Diagnostic Questions: What’s Really Happening?
This is where the truth begins to emerge:
- Where are the people who passed the program?
- What features are underutilized—and why?
- What patterns emerge in decision-making?
These questions go beyond dashboards to behavior. But they are often asked too late—when adoption issues have already taken hold.
3. Discovery Questions: Are We Changing Behavior at Scale?
This is a layer that many organizations miss.
- What decisions are now being made differently because of this technology?
- Do teams rely on the system in critical moments—or do they back down under pressure?
- How are new ways of working implemented consistently throughout the organization?
These questions are difficult. They need to look beyond usage data to decision quality, consistency, and system trust. They are the closest indicators of whether a change is working.
4. Governance Questions: Are We Protecting the Value of This Change?
This is where leadership maturity is shown.
- What are the leading indicators that tell us whether the acquisition will succeed (or not)—six months from now?
- Do our operating systems reinforce the behavior we expect from this change?
- Do we have visibility into where power gaps are limiting adoption?
- Who is responsible for the acquisition (not just the shipment)?
And perhaps the most uncomfortable question: Do we govern adoption as tightly as we govern financial performance?
Because in most organizations, the answer is no.
Adoption Is Not a Result. It’s a program.
One of the biggest misconceptions in digital transformation is this: acquisition is considered a phase, something that happens after deployment. In fact, adoption is a process. It is composed as follows:
- Leadership behavior.
- Motivation and performance metrics.
- Ease of use and workflow integration.
- Confidence and competence.
If these elements are not aligned, discovery will remain partial—no matter how advanced the technology.
The Role of Learning—Often Misunderstood
Learning is often referred to as “acquisition support.” It’s usually late. Usually as a release. But learning, in this context, is not about training people in skills. It’s about enabling them
- Make better decisions using the system.
- Trust new data sources.
- Abandon legacy work methods.
But that requires a different approach. Learning should be
- Embedded in workflow.
- It is focused on real decisions.
- Reinforced by usage—not events.
People don’t change just because someone understands them. They change when they find a better way of working—and see it work.
What Mature Organizations Should Do Differently
Some organizations bridge the gap between deployment and acquisition more effectively than others, not because they invest more in technology, but because they invest differently in acquisition management.
- Track key behavioral indicators, not just system usage
- Integrate acquisitions into business updates
- Hold leaders accountable for skills and not just results
- Identify and address resistance early
Most importantly, they recognize this: Transformation is not complete when technology is used. It is perfect when the behavior changes on the scale. And that requires governance.
A Simple Change That Changes Everything
For leaders, change doesn’t have to be complicated. It can start with one change:
In your next review, instead of asking, “Are we on track with performance?”
Ask: “What exactly has changed in the way decisions are made using this system?”
Instead of, “What does the usage data show?”
Ask: “Where do we still rely on old ways of working—and why?”
Instead of saying, “Should we train everyone?”
Ask: “Who is confident in using this to make critical decisions—and who doesn’t know?”
These are not major changes. But they changed what was available. And what is expressed is what is spoken.
A Silent Risk in All Changes
There are risks that rarely make it into formal negotiations: not technical risks; not financial risk, but something more subtle: The risk that an organization appears to have changed—while continuing to operate fundamentally the same. This is where value is quietly eroded. Where systems exist, but cannot be trusted. Where data is available, but not used. Where a plan is announced, but not lived.
Digital transformation is often framed as a technology journey. In fact, it is a discipline of leadership. The discipline of
- Asking better questions.
- Paying attention to different signs.
- Making the organization accountable for what really matters.
Because in the end, the success of a revolution is not determined by what is built; it determines what is used, trusted, and supported. And that depends on the questions leaders choose to ask—consistently, intentionally, and over time.
