After the First Success: Leading the Second Wave of AI Transformation
Created on 2026-02-06 09:45
Published on 2026-03-17 10:00
Why organizations that succeed with AI often fail to capitalize on that success
Congratulations.
You did it. You deployed AI. You achieved adoption. You measured results. The initiative worked.
You are in the 5%.
MIT’s research found that 95% of organizations get zero return from AI investments. You beat those odds. You built the Human Layer. You navigated the J-Curve. You reached the summit.
Now comes the harder part.
The second wave.
Most organizations that succeed with their first AI initiative fail to capitalize on that success. They treat the first success as an ending rather than a beginning. They assume the hard work is done. They return to business as usual.
And they watch their advantage erode as competitors catch up.
This article is for organizations that have achieved initial AI success and want to build on it. The first success was hard. The second wave is harder. But the second wave is where sustainable competitive advantage lives.
The First Success Trap
Let me name a pattern I observe repeatedly.
Organizations achieve AI success. They celebrate. They move on. They treat the initiative as complete.
And then nothing happens.
The successful AI remains in place. It continues to deliver value. But it does not expand. It does not deepen. It does not become the foundation for broader transformation.
I call this the First Success Trap.
Why organizations fall into the trap:
The initiative was exhausting. Resources were stretched. Attention was consumed. People are relieved it is over.
The organization wants to return to normal. Other priorities have been waiting. The AI initiative was a project, and projects end.
Leadership attention moves elsewhere. The sponsor who drove the first success moves to the next challenge. The initiative enters “maintenance mode.”
The urgency is gone. The fear of falling behind that drove the first initiative no longer applies. You have AI now. You succeeded.
What happens in the trap:
The first success becomes isolated. AI works in one area. Other areas continue without AI.
Capability does not spread. The people who developed AI fluency remain specialized. Others never develop.
The Context Graph does not deepen. The institutional knowledge captured for the first initiative does not expand.
Competitors catch up. While you rest on first success, others are building. The advantage you created begins to erode.
The trap’s logic:
The First Success Trap makes sense in the moment. The organization is tired. Other priorities are real. The initiative did succeed.
But the trap destroys the compound advantage that AI creates. Each month of delay is a month that competitors are building while you are resting.
The 18-month window does not pause because you succeeded once.
What the Second Wave Requires
The second wave is not more of the same. It is qualitatively different from the first initiative.
Institutionalization:
The first initiative created AI capability in specific people, in a specific domain, for a specific use case.
The second wave institutionalizes capability. It makes AI fluency organizational rather than individual. It embeds AI into how the organization works, not just into specific projects.
Institutionalization means new employees learn AI as part of onboarding. It means AI considerations are part of every process design. It means AI capability is assumed, not exceptional.
Expansion:
The first initiative operated in limited scope. One use case. One function. One process.
The second wave expands scope. It applies AI to additional use cases, functions, processes. It leverages what was learned in the first initiative to accelerate new initiatives.
Expansion is not simply replication. Each new domain has its own context, its own challenges, its own requirements. But the foundation built in the first initiative makes expansion possible.
Deepening:
The first initiative created initial AI capability. Basic usage. Initial adoption. Measurable but limited value.
The second wave deepens capability. Advanced usage. Sophisticated adoption. Transformative value.
Deepening means moving from AI that assists to AI that transforms. From AI that makes existing work faster to AI that enables new work. From AI that optimizes to AI that creates.
Integration:
The first initiative was likely separate. An AI project distinct from normal work. A special initiative with special attention.
The second wave integrates AI into normal work. AI is no longer a project. It is how things are done.
Integration means AI considerations are part of every decision. AI capabilities are part of every role. AI thinking is part of organizational culture.
The Gilman’s Point Risk
Let me return to a metaphor I used in an earlier article.
In 1993, I became the first Malaysian to summit Mount Kilimanjaro. At Gilman’s Point, 5,681 meters, five of my companions stopped. They had certificates. They had photos. They had achieved something real.
But they had not reached the summit.
Uhuru Peak, the true summit, was another 200 meters up. Another hour of climbing when every cell in the body wants to stop.
They got the certificate. I got the summit.
The First Success Trap is Gilman’s Point for AI transformation.
You have achieved something real. You have the certificate. You can point to success.
But you have not reached the summit. The true transformation, where AI becomes invisible because it is so integrated into work, where the Context Graph creates genuine competitive moat, where capability is institutional rather than individual, that summit remains.
96% of the climb is complete at Gilman’s Point. Most organizations stop there.
The 4% that remains is where the transformation actually happens.
Building on the Context Graph
The Context Graph is the accumulated record of how your organization understands and operates in your specific context.
The first initiative began building your Context Graph. The second wave must deepen it.
What deepening the Context Graph means:
More domains. The first initiative captured context for one area. Expand to additional areas. Each domain adds to organizational understanding.
More history. The Context Graph accumulates over time. Each month of operation adds learning. Protect this accumulation.
More reasoning. Capture not just what decisions are made, but why. The reasoning is what makes the Context Graph valuable.
More connections. Connect context across domains. How does customer context connect to operational context? How does market context connect to product context?
Why the Context Graph matters for competitive advantage:
Your Context Graph is uniquely yours. Competitors cannot replicate it. Vendors cannot provide it.
As your Context Graph deepens, your AI becomes more relevant, more accurate, more valuable. The gap between your AI and generic AI widens.
This is the compound advantage that justifies sustained investment. The Context Graph creates moat that grows over time.
Practical steps for deepening:
Document reasoning systematically. When decisions are made, capture why.
Capture institutional knowledge before it leaves. Experienced employees hold context that is not written anywhere. Extract it.
Connect AI systems to each other. Context in one system should inform context in others.
Review and refine continuously. The Context Graph is not built once. It is cultivated continuously.
Institutionalizing Capability
The first initiative developed capability in specific people. The second wave must institutionalize capability across the organization.
What institutional capability means:
Every employee has baseline AI fluency. They understand what AI can do. They can use AI tools effectively. They can evaluate AI outputs.
AI usage is normal, not exceptional. People do not think about “using AI.” They think about doing their work. AI is part of how work gets done.
New employees acquire AI capability as part of joining. Onboarding includes AI training. AI fluency is expected, not developed later.
The organization can deploy AI to new domains without heroic effort. The capability exists. New deployments leverage existing capability.
How to institutionalize:
Embed AI into training. Not just specialized AI training. AI elements in all training.
Embed AI into processes. Not AI as separate tool. AI as integrated element of how processes work.
Embed AI into evaluation. Performance criteria that include AI effectiveness. Recognition for AI contribution.
Embed AI into culture. Stories about AI success. Leaders who model AI usage. Norms that expect AI fluency.
The capability flywheel:
Institutional capability creates a flywheel.
Capable people create AI success. Success creates resources for more capability development. More capability enables more success.
This flywheel accelerates over time. Organizations that start it early create advantages that late starters cannot easily overcome.
Expanding to New Domains
The first initiative succeeded in a specific domain. The second wave expands to additional domains.
The expansion challenge:
Each domain is different. Customer service is not operations. Finance is not marketing. What worked in one domain may not work in another.
Expansion is not replication. It is adaptation. The principles transfer. The specifics must be developed.
How to expand effectively:
Prioritize by value and readiness. Not all domains are equally valuable. Not all domains are equally ready. Focus where value is high and readiness is sufficient.
Transfer people, not just knowledge. People who succeeded in the first initiative can accelerate new initiatives. Move them to new domains, at least temporarily.
Apply the same methodology. The 90-Day Sprint works for new domains as it worked for the first. Do not abandon methodology because you succeeded once.
Expect the J-Curve again. Each new domain will have its own J-Curve. Set expectations accordingly.
Build domain-specific Context Graphs. Each domain has its own context. The Context Graph must be built for each domain, not just imported from other domains.
Common expansion mistakes:
Assuming success will transfer automatically. It will not. Each domain requires work.
Stretching resources too thin. Better to succeed in two new domains than to struggle in five.
Neglecting the first domain. While expanding, do not let the original domain degrade.
Moving too slowly. Expansion should be deliberate, not glacial. The window is closing.
The Continuous Transformation Mindset
The first initiative was a project with a beginning and an end.
The second wave is not a project. It is a continuous capability.
What continuous transformation means:
There is no “done.” AI capability continuously develops. New applications emerge. New opportunities appear.
Transformation is the normal state. Change is not an exception to be managed. Change is how the organization operates.
Learning is continuous. Each deployment teaches something. Each failure teaches something. The organization continuously improves.
How to sustain continuous transformation:
Maintain dedicated capacity. Not project resources that come and go. Permanent capacity for AI development.
Create feedback loops. How do you know if AI is working? How does that information reach people who can act on it?
Celebrate learning, not just success. Success is celebrated. Failure should also be celebrated when it produces learning.
Keep leadership engaged. Continuous transformation requires continuous leadership attention. Leaders who declare victory and move on doom the transformation.
The organizational identity shift:
Continuous transformation requires an identity shift.
From “we use AI” to “we are an AI-enabled organization.”
From “we have an AI initiative” to “AI is how we work.”
From “we succeeded with AI” to “we continuously develop AI capability.”
This identity shift is what separates the 5% from the others. It is not a project they completed. It is who they have become.
The Leadership Challenge
The second wave creates specific leadership challenges.
Maintaining attention:
The first initiative had urgency. The fear of falling behind. The competitive pressure. The board questions.
After success, urgency fades. Other priorities assert themselves. Leadership attention naturally moves elsewhere.
The second wave requires leaders to maintain attention without the urgency that drove the first wave.
This is difficult. It requires discipline to keep focusing on what is important when what is urgent has passed.
Resisting satisfaction:
Success creates satisfaction. You did it. You can relax.
This satisfaction is the enemy of the second wave. Satisfaction leads to complacency. Complacency leads to the First Success Trap.
Leaders must resist satisfaction. Celebrate success, yes. But immediately ask: What is next? How do we build on this?
Sustaining resources:
The first initiative had resources because it was a priority. Budget was allocated. People were assigned. Attention was directed.
Sustaining resources for the second wave requires ongoing advocacy. The initiative is no longer new. It no longer has the novelty that attracted support.
Leaders must make the case for continued investment. The compound advantage argument. The competitive necessity argument. The cost of stopping.
Modeling the behavior:
In the first wave, leaders may have personally adopted AI to model behavior.
In the second wave, leaders must continue modeling more sophisticated AI usage. Not just basic adoption. Advanced application. Continuous development.
Leaders who stop developing their own AI capability signal that development is optional. The organization follows.
The DBS Example
Let me return to an example I mentioned earlier.
DBS Bank was once known as “Damn Bloody Slow.” The nickname was deserved.
Their transformation did not happen through a single initiative. It happened through sustained effort over years. Wave after wave of development. Continuous deepening of capability. Persistent investment in becoming something different.
Today, DBS is recognized as “World’s Best Digital Bank.”
The lesson is not about what they did in year one. It is about what they continued to do in years two, three, four, and beyond.
They did not stop at Gilman’s Point. They kept climbing.
The first success was necessary but not sufficient. What made DBS exceptional was the sustained effort that followed.
What Comes After the Second Wave
The second wave is not the final wave. It is the beginning of continuous capability.
The third wave and beyond:
As AI capability matures, new opportunities emerge.
AI that does not just assist work but enables new work. New products and services that AI makes possible. New business models that AI enables.
These opportunities are not visible from the first wave. They become visible as capability deepens.
The organizations that sustain transformation through second wave and beyond will see opportunities that others cannot see.
AI that learns:
Current AI is largely static. Deploy it and it operates as deployed.
Future AI will learn continuously. It will improve from every interaction. It will adapt to changing context.
Organizations with deep Context Graphs and strong Human Layers will be positioned to leverage learning AI. Organizations without these foundations will not.
The compound advantage realized:
Over time, the compound advantage of continuous AI development becomes decisive.
Your Context Graph is deeper than competitors’. Your capability is more sophisticated. Your integration is more complete.
The gap widens. What was advantage becomes dominance.
This is why the second wave matters. It is not just about incremental improvement. It is about creating advantages that compound over time into positions that are difficult to challenge.
Practical Steps for the Second Wave
Let me provide concrete guidance for organizations ready for the second wave.
In the next 30 days:
Conduct a post-first-initiative review. What worked? What did not? What did you learn?
Identify expansion opportunities. Which additional domains have highest value and sufficient readiness?
Assess current capability. Is capability institutional or concentrated in individuals?
Secure continued resources. Make the case for sustained investment.
In the next 90 days:
Begin expanding to one or two new domains. Apply the same methodology that worked in the first initiative.
Develop institutionalization plan. How will AI capability become organizational rather than individual?
Deepen the Context Graph. Capture reasoning and context that was not captured in the first initiative.
Maintain the first domain. Ensure it continues to deliver value while you expand.
In the next year:
Achieve AI operation in multiple domains.
Develop institutional capability where AI fluency is normal, not exceptional.
Create the continuous transformation capability for ongoing development.
Build the compound advantage that separates you from competitors.
The first success was hard. The second wave is harder. But the second wave is where sustainable advantage lives.
Most organizations stop at Gilman’s Point. They have the certificate. They have proved they can do AI. They return to normal.
The 5% who truly transform do not stop. They keep climbing. They build institutional capability. They deepen the Context Graph. They expand to new domains. They sustain continuous transformation.
The summit is not the first success. The summit is what you build on that success.
Where is your organization after first AI success? What will you do with the advantage you have created?
The AI Readiness Scorecard can help you assess readiness for the second wave, not just the first initiative. It takes ten minutes and shows where your organization stands across all six dimensions.
Comment “SCORECARD” below and I will send you access.
You beat the 95%. Now build on that success. The second wave is waiting.