Ask any design leader today whether their team uses artificial intelligence, and you will almost certainly hear yes. Pull back the curtain and look at what that actually means, and the answer becomes far more complicated.
This is the AI maturity mirage: the growing distance between what organisations claim about their AI adoption and what is actually happening inside their design workflows on a Tuesday afternoon.
The numbers make the gap embarrassingly visible. 65% of organisations now use generative AI in at least one business function, double the rate from just ten months earlier, according to McKinsey’s first quarter 2026 data. That headline sounds like a revolution in progress.
But then consider this: according to IBM’s 2026 Global CEO Study, 85% percent of employees now have access to AI tools at work, yet only 25% actually use them regularly. That 61-point gap is one of the most expensive problems in enterprise technology right now.
Design teams are not exempt from this pattern. They are, in many ways, its clearest illustration.
The Tool Collector Problem
According to the 2026 AI in Design Report, published by Designer Fund and Foundation Capital and based on over 900 responses and 25 interviews with leaders at Anthropic, Stripe, DoorDash, Miro, and others, the average designer’s toolstack went from 3 tools to 7 in a single year. Nearly half of all respondents say they are still searching for their go-to setup.
Read that again. Designers are using twice as many tools and still feel uncertain about which ones matter.
This is what AI adjacency looks like in practice. A team that has Figma AI, a subscribed ChatGPT account, a Midjourney workspace, and three other tools sitting in open browser tabs is not an AI-enabled team.
It is a team that has acquired the vocabulary of transformation without restructuring how decisions actually get made.
72% of designers now use generative AI tools, but only about a third report that their current toolstack actually saves more time than it costs in cleanup. The tools exist. The habits around them do not.
What Genuine AI Enablement Actually Requires
There is a version of AI adoption that changes nothing except the tools you open. You still frame problems the same way. You still run the same research rituals. You still review designs using the same criteria. The AI sits somewhere in the middle, generating options that you then manually filter with no real change to how you think or how long things take.
Then there is a version that rewires how a team operates. It shows up when AI is embedded into the problem-framing stage, not just the execution stage. When teams use it to stress-test assumptions before a single screen is designed, not just to produce variations of a screen that already exists.
When it informs what questions to ask during user research, not just tell what the report should look like afterwards.
Research from Modus Create found that 84% of product leaders claim AI is integrated across the product lifecycle, but only 28% use it for prototyping and 38% use it for coding production features. Many organisations are calling themselves AI-enabled while still treating AI as a set of disconnected tools rather than a capability embedded into how products are built.
The design discipline has its own version of this exact illusion.
Why This Matters More in Emerging Markets
For design teams operating across Africa, the stakes are higher, and the margin for performance theatre is thinner.
Access to AI tools in markets like Nigeria requires navigating payment infrastructure barriers, inconsistent internet reliability, and pricing models built for dollar-denominated budgets. When a team finally clears those hurdles and gains access, it cannot afford to treat that access as a status symbol. It needs to translate into measurable workflow improvement.
Workers with AI skills earn 56% more than peers without them, and senior user experience leaders working inside AI-augmented systems are commanding between 160,000 and 190,000 US dollars annually. Design skills are now listed as the number one most in-demand skill in AI job postings, ahead of coding and ahead of cloud infrastructure.
The opportunity is real. But it will not be captured by teams that simply add AI tools to their existing stack and call it a transformation.
The Honest Audit
The most useful thing a design leader can do right now is ask a blunt question: if every AI tool disappeared from our workflow tomorrow, how different would our output actually look?
If the honest answer is not very different, that is not a technology problem. If 2024 exposed the collaboration gap and 2025 was about AI disruption, 2026 is about operationalising AI. Teams are moving from trying new tools to asking how they govern and integrate AI into their stack, roles, and development process.
Claiming AI enablement is easy. Earning it requires redesigning how your team thinks, not just what it opens.
The mirage looks convincing from the outside. The work of closing the gap happens entirely on the inside.
