Every AI vendor pitch I've sat through in the last eighteen months has opened with the same slide. Some variation of "the technology is ready." And honestly, they're not wrong - the tooling has matured faster than most of us expected, and the use cases are real.
But none of those slides ever show you the expression on a senior associate's face when you tell them the firm is rolling out an AI-powered document review tool. Or the passive resistance of a practice lead who nods along in the steering committee and then quietly never logs in. Or the IT director who's been burned by three transformation projects in five years and has learned that the safest career move is to slow-walk everything until the hype passes.
The technology is ready. Your people might not be. And if you don't know where they stand, you're about to spend a lot of money finding out the hard way.
Culture is too soft to measure. We just need to get on with it and people will adapt.
I hear this constantly, and I understand the instinct. You're running a firm that bills by the hour. You don't have time for what sounds like an HR exercise. Just buy the tool, train everyone, and crack on. But the evidence keeps pointing the same direction: cultural resistance kills more AI initiatives than technical failure. Gartner found that 80% of AI projects fail to scale beyond pilot stage, and the primary reasons are consistently organisational, not technical. McKinsey's State of AI research shows that the firms seeing real value aren't necessarily the ones with the best models or the biggest budgets - they're the ones that invested in change management alongside the technology.
So when I talk about measuring cultural attitudes, I'm not suggesting you run a feelings survey and stick the results on a noticeboard. I'm talking about a structured, repeatable assessment that tells you exactly where resistance lives, where your champions are, and where to focus your change management budget before you commit to a single licence.
I was working with a 300-person professional services firm last year - the kind of firm that does everything thoughtfully. They'd done their research. Selected a genuinely good AI tool for proposal generation. Built a solid business case. Got board sign-off. Ran training sessions. The whole playbook.
Six months in, adoption was at 14%. Fourteen percent. The tool worked brilliantly for the handful of people using it. Everyone else had found workarounds, or simply carried on doing things the old way. The CTO was tearing his hair out. "We gave them everything they needed," he said. And technically, he was right.
What he hadn't done - what almost nobody does - is understand the landscape of attitudes before pressing go. He'd assumed that if the technology was good enough and the training was thorough enough, people would adopt it. That's a rational assumption. It's also wrong.
Here's what was actually happening beneath the surface. About 20% of the firm were genuinely enthusiastic - they'd have adopted the tool without any training at all. Another 15% were actively hostile: senior people, mostly, who saw AI as a threat to the expertise-based model that had built their careers. And the remaining 65%? They were what I'd call the persuadable middle. Not opposed, not enthusiastic. Waiting to see which way the wind blew. When the senior resistors made it clear - through body language, through offhand comments, through simply never mentioning the tool - that this wasn't something serious people did, the middle followed their lead.
That firm effectively spent six figures on a tool that 86% of its people ignored. If they'd measured cultural attitudes first, they'd have known exactly where to focus: neutralise the vocal resistors, equip the champions with visible wins, and give the middle a reason to follow.
I had a shorter, messier version of this conversation with a legal firm about a year earlier. They'd skipped the cultural assessment entirely - "we just need to get on with it" - and six weeks into their pilot, a senior partner sent a firm-wide email questioning whether the AI tool was "appropriate for client-facing work." No evidence, no specific concern, just a vague unease dressed up as professional caution. That email set the programme back by four months. One email. If anyone had thought to ask that partner what he actually thought before the launch, they could have addressed it in a conversation rather than a crisis.
Right. So how do you measure something as apparently woolly as "cultural attitude toward AI"? You break it down into dimensions that are specific enough to assess and act on.
We use five when we work with firms on AI readiness. None of them require a psychology degree to evaluate. All of them produce data you can do something with.
The first is general attitudes toward change - and I mean general, nothing to do with AI specifically. How does your firm handle change? Have recent shifts - a new CRM, a restructured team, a change in billing model - been absorbed smoothly, or does every change get met with months of foot-dragging? A firm that struggles with change broadly is going to struggle with AI specifically, and no amount of "but this is different" will overcome that. You're measuring the soil before you plant the seed. Look at the last three significant changes in the firm: how long did adoption actually take, where did resistance cluster, and what was the gap between announced go-live and real-world use? System logs, project post-mortems, and honest conversations with team leads will give you this. Score it 1 to 5.
Trust in technology is subtler, and it matters more than people expect. This isn't about whether people use technology - everyone uses email and Excel. It's about whether they trust technology to make or support decisions. Do your partners trust the CRM pipeline data enough to make resourcing decisions from it? Or do people keep shadow copies, maintain their own spreadsheets, and treat central systems as something they feed but never consume? Low trust in existing technology is a leading indicator of AI resistance. If someone doesn't trust the CRM, they're definitely not going to trust an AI system drawing on the same data. Survey a cross-section with specific scenarios: "If the system flagged a client as at risk of churn, would you act on that without checking manually?" The answers will tell you a lot.
Then there's data literacy - and I don't mean data science literacy. Basic data literacy. Can your people read a dashboard? Do they understand what a conversion rate means? Can they distinguish between correlation and causation when presented with a chart? AI tools produce outputs that require interpretation. If your team can't evaluate data from existing tools, they won't be able to evaluate AI outputs either - which means they'll either blindly trust everything or dismiss everything. This one's easier to measure than people think: give a sample group a real dashboard from your existing systems and ask them three questions about what it shows. The answers will tell you more than any self-assessment.
Willingness to experiment is the fourth. Some firms have a culture where people try new approaches, share what worked, and aren't punished for things that didn't. Others - and this is common in professional services, where mistakes can have regulatory consequences - have a culture of caution. Neither is inherently wrong, but a firm with low experimentation tolerance needs a very different AI rollout strategy. Ask people when they last tried a new tool without being told to. Ask team leads whether their people suggest process improvements. Look at whether pilot programmes in the past attracted volunteers or had to be staffed by assignment.
And then leadership signals, which is the one that matters most and the one firms are most reluctant to assess honestly. What are your senior leaders actually signalling about AI? Not what they say in the all-hands meeting - what they do in practice. Does the managing partner use the tools they've endorsed? Do practice leads reference AI outputs in client discussions? Or is there a visible gap between the official narrative and the observable behaviour?
I'm not being facetious when I say I've sat in firms where the partner championing AI adoption still dictates everything to his PA and has someone else print his emails. More than once. Anonymous upward feedback - specific to AI and technology signals - is the only way to surface this honestly. "Does your line manager visibly use the tools the firm has adopted?" "Has your team leader mentioned AI in a team meeting in the last quarter?" The answers will either confirm that leadership is walking the talk, or reveal that the biggest barrier to adoption is sitting in the corner office.
Once you've scored across all five dimensions, you'll have a cultural readiness map. And that map will reveal three distinct groups.
The champions score highly across most dimensions. They're already bought in. Your job isn't to convince them - it's to make them visible. Put them on the pilot. Let them present results to the wider firm. Give them permission to be enthusiastic in a culture that might otherwise discourage it.
The resistors score low across multiple dimensions. Some have legitimate concerns - about data quality, about client confidentiality, about the reliability of AI outputs. Those concerns deserve engagement, not dismissal. Others are simply change-averse, and no amount of evidence will move them. The measurement helps you distinguish between the two. Engage the first group seriously. Manage around the second.
And then there's the persuadable middle, which is the group that determines your outcome. They're watching the champions and the resistors to decide which way to go. Your entire adoption strategy should be designed to make it easier, more rewarding, and more socially acceptable for this group to follow the champions. Give them low-risk entry points - small, contained uses of AI that let them experience a win without betting their reputation on an unproven tool.
As for the change-averse resistors: sometimes you just need to make sure they're not in a position to block progress for everyone else. That sounds harsh. But I've watched too many firms let one or two vocal sceptics set the pace for the entire organisation, and it's a genuinely dispiriting thing to see.
Culture shifts. Slowly, usually, but it shifts. The firm that scored 2 out of 5 on trust in technology six months ago might score 3 after a successful pilot. The leadership signals dimension might jump after a partner sees a competitor win work using AI-generated insights and suddenly gets religion.
Measurement needs to be repeated. Quarterly for the first year of any AI programme, then every six months once you've established a baseline. Each round tells you where to focus your change management effort next. Maybe the persuadable middle has largely moved to the champion camp and you can tackle more ambitious use cases. Maybe a new pocket of resistance has emerged in a team that felt overlooked in the first wave. You won't know unless you measure.
There's a secondary benefit to repeated measurement that's easy to miss: the act of asking signals that you take this seriously. When people are surveyed about their attitudes toward AI - when their concerns are acknowledged and their feedback visibly shapes the rollout - they're more likely to engage constructively. The difference between "the firm is doing AI to us" and "the firm is doing AI with us" is smaller than you'd think, and it starts with whether anyone bothered to ask.
Measuring cultural attitudes toward AI will, in some firms, surface things leadership would rather not know. You might discover that your senior team is the primary source of resistance. You might find that trust in technology is so low that you need to fix your existing systems before anyone will take AI seriously. You might learn that a significant portion of your firm views the whole initiative as a management fad that will pass if they wait long enough.
None of that is a reason not to measure. All of it is a reason you need to.
The firms I see getting real value from AI - not pilot-stage value, but genuine operational improvement - are the ones that treated cultural readiness as seriously as technical readiness. They measured attitudes before buying tools. They designed rollout strategies around what the data told them, not what they hoped was true. And they kept measuring, adjusting, and investing in the human side of adoption long after the technology was live.
Your AI tools don't fail because the technology doesn't work. They fail because the people who are supposed to use them don't trust them, don't understand them, or don't see anyone they respect using them. That's a cultural problem. And you can't fix a cultural problem you haven't diagnosed.
If you want a broader view of where your firm sits on AI readiness - covering data, infrastructure, and governance alongside culture - we've put together an AI readiness guide that covers all four dimensions. And if you'd like a downloadable version of the cultural readiness assessment framework described here, something you can adapt and run internally, get in touch and we'll share the template.