Most AI readiness tests skip the one layer that decides whether AI sticks: your people.
They go straight to data and process readiness. Important, yes. But I have watched plenty of transformations stall long before data or process ever became th...
They go straight to data and process readiness. Important, yes. But I have watched plenty of transformations stall long before data or process ever became the problem.
I wrote about this after a conversation with Shang How Tan, CEO of Sequoia Group. Most failed AI rollouts are technically sound. What is missing is acceptance from the people meant to use them. He framed it as Q × A = E. Quality of solution times Acceptance by people equals Effectiveness. High Q, low A, and you still get low E.
Read the earlier article: https://lnkd.in/gF2zrc9R
Here is what I keep hearing on the ground.
When I talk to CEOs and business leaders, the two problems that surface are rarely about tech:
- Fear
Their employees resist AI because they worry they will be replaced the moment they prove it works.
- Expectation
The ones who do try it are not impressed with the output, so they fall back to the old way. They expected AI to be plug and play. It is not. Out of the box it gives you average output, and most give up before they teach it their standards.
I wrote about why AI is not plug and play here: https://lnkd.in/gUXb2QGU
When I talk to working professionals, I hear a different two:
- Alignment
“My boss told us to use AI but never gave us a paid subscription.”
- Shadow AI
“So we use our own personal accounts. The company has no idea what data we are feeding into it.”
All four are addressable. But only if you surface them first. Most readiness tests never look here. So I built one that does.
It is free, takes about 5 minutes, and has 12 questions. By the end you will have a clearer picture of where your team stands.
Fun fact on the loud neo-brutalism look. Claude Code gave me 5 design options and most felt boring to me. In the past, redesigns and coding were expensive, so I always took the safe choice. Now that both are cheap, I asked myself, why not try something risky? I am not sure I made the right call. Tell me if you would have gone safer.
Check it out: https://lnkd.in/ga986aZi
If you are leading an AI push and it is not landing, the bottleneck is probably not your data. It is one of these four. Worth knowing which one.
Need help pushing AI adoption in your team? DM me.
#AI #AIAdoption #AIReadiness #ChangeManagement #FutureOfWork
Enjoyed this? Subscribe for more.
Practical insights on AI, growth, and independent learning. No spam.
More in Vibe Coding
Create a Free LinkedIn Carousel with Vibe Coding
(See the carousel below that I created for one of my posts)
After running 5 workshops for non-techies and "forcing" them to use Terminal / PowerShell, I have a...
1. Trying to use the mouse.
Want to monitor your context window, session, and weekly limit in real time?
One of the lesser-known Claude Code features: you can customize your status line.
Can AI really write production-quality code?
Here's a chance to peek how it is used in an actual project.
"Wait, you used to do THAT manually?"
I've been building software for 19 years. Something that would take me 2 months now takes 1 week.
Claude.ai, Claude Desktop, Cowork, or Claude Code: which one should you use, and when? And why is Claude Code not only for coding?
I get this question a lot, in workshops, in my DMs, and in offline conversations.
Create a Free LinkedIn Carousel with Vibe Coding
(See the carousel below that I created for one of my posts)
Want to monitor your context window, session, and weekly limit in real time?
One of the lesser-known Claude Code features: you can customize your status line.
Claude.ai, Claude Desktop, Cowork, or Claude Code: which one should you use, and when? And why is Claude Code not only for coding?
I get this question a lot, in workshops, in my DMs, and in offline conversations.
After running 5 workshops for non-techies and "forcing" them to use Terminal / PowerShell, I have a...
1. Trying to use the mouse.
Can AI really write production-quality code?
Here's a chance to peek how it is used in an actual project.
"Wait, you used to do THAT manually?"
I've been building software for 19 years. Something that would take me 2 months now takes 1 week.