When an organisation comes to us saying they want to implement AI, the first thing we do is work with their leadership team. Not their technical team. Not the team that's going to use the AI system. Their leadership: the people who control budgets, set strategy, have influence over how the organisation operates, and ultimately decide what gets priority and what doesn't. This seems backwards to some people. Shouldn't we be talking to the people who actually do the work? Shouldn't we be assessing the technical environment first? Shouldn't we be identifying which systems have APIs we can connect to?

No. Those things matter, but they come second. Leadership alignment comes first, and this is the difference between AI implementations that succeed and those that fail. The most sophisticated tool in the world will fail if the leadership team doesn't understand it, doesn't genuinely support it, and doesn't make space for it to succeed. The simplest tool will succeed if the leadership team is aligned, understands what the tool does, and has committed resources to implement it properly.

Why Leadership First, Not Technology First

Technology is easy. Finding a tool that does what you want is solvable. Connecting it to your systems is solvable. Configuring it to work with your data is solvable. Training your team is solvable. All of these are technical problems with technical solutions. What's hard is the human side: getting an organisation to actually change how it works, getting teams to use a new system when they're comfortable with the old way, getting managers to hold people accountable for using the system correctly, getting leadership to make space for the disruption that comes with implementation.

We've seen organisations with the best technology implementations fail because leadership didn't support them. A shiny new system gets implemented, costs a lot of money, and then a year later half the team isn't using it regularly because their manager doesn't make it a priority. We've also seen organisations with mediocre technology implementations succeed because leadership made them a priority. The system was slower than they wanted, didn't integrate perfectly with their existing systems, required workarounds, but it was used because leadership made it clear it mattered.

The reason this is so consequential is that AI implementation always requires change. Processes need to be mapped, understood, and sometimes redesigned. Data needs to be cleaned and structured. Teams need to learn new ways of working. Time needs to be invested in configuration and testing. Someone needs to be accountable for making sure the system stays accurate and relevant as the business changes. None of this happens without leadership support and allocation of resources.

What We Assess With Leadership

When we work with your leadership team, we're assessing several things. First, do you genuinely want to do this, or are you exploring because it feels like you should? Sometimes organisations feel like they need to adopt AI because they've heard it's transformative, or they're worried about falling behind competitors. That's a different situation than an organisation that has a specific problem they want to solve and believes AI might help. We need to understand which one you are.

Second, are you willing to make this a priority? Implementing AI successfully requires time from senior people. Someone from leadership needs to sponsor the project, remove obstacles, and keep it moving. If the answer is "we're too busy right now but we'll make time eventually," implementation is going to struggle. We need to understand whether this has real priority or whether it's on the back burner.

Third, do you understand what change this will create? AI implementation disrupts work. People have to learn new processes. Some people will embrace it and some will resist it. Data that worked fine in the old system might not work in the new system. Decisions that used to take two hours to make manually might now be questioned because an AI system is providing alternative recommendations. Are your leaders ready for that, or are they expecting implementation to happen smoothly with no organisational disruption?

Fourth, what does success look like? Different leaders often have different visions of what AI should accomplish. One person thinks it's about cutting costs through automation. Another thinks it's about improving decision quality. Another thinks it's about freeing people to do more strategic work. A fourth thinks it's about improving customer experience. These aren't contradictory, but if you don't align on what matters most, you'll prioritise implementation tradeoffs differently. You need to get aligned on what you're trying to accomplish before you start.

Fifth, what's your tolerance for disruption and risk? Some organisations can tolerate a slow, careful, minimal-risk implementation. Others need to move quickly and can tolerate more disruption. Some have zero tolerance for mistakes because they work in high-stakes environments. Others have more flexibility. We need to understand this because it determines how we recommend approaching implementation.

The Assessment Conversation

With leadership, we typically have structured conversations that explore these questions. We ask about the business problem you're trying to solve. Not "we want to implement AI" but "what specifically is painful about how we work now?" Is it that you're spending too much time on data entry? Is it that your reporting takes too long? Is it that you're making decisions based on incomplete information? Is it that you're losing good people because the work is tedious? Once you understand the underlying problem, you can figure out whether AI is actually the solution.

We ask about your organisation's readiness. Have you successfully implemented other significant changes recently? How did people respond? Were there pockets of resistance? How did you handle them? What did you learn? This tells us what kind of implementation approach is likely to work with your team. An organisation that's gone through successful digital transformation is likely to be more open to AI than an organisation where past implementations have been rocky.

We ask about your constraints. What's your budget? What's your timeline? Do you have internal technical expertise that can support a complex implementation, or do you need a tool that's simple enough that external consultants can largely hand it off? Are there regulatory or compliance constraints? Are there data privacy concerns? These constraints shape what's actually feasible for you.

We ask about accountability. Who's going to be responsible for this project succeeding? Who's going to keep pushing when implementation gets difficult? Who's going to hold people accountable for using the system correctly? Without clear accountability, implementations drift and eventually stall.

What This Prevents

Working with leadership first prevents several common failure modes. It prevents you from buying a tool and then not having resources to implement it properly. It prevents you from implementing a tool that solves your technical problem but creates cultural friction because nobody was ready for the change. It prevents you from investing in AI that solves yesterday's problem instead of today's problem. It prevents you from implementing a tool that requires your team to work in ways that contradict your values or your culture.

It also prevents death marches. Some implementations struggle because the technical team is sprinting to get something working while leadership is unclear on whether they actually support the project. A technically skilled team working on a project that leadership isn't truly committed to is demoralising. It creates burnout. It generates cynicism. Whereas a project that leadership is genuinely committed to, even if it's technically slower or harder, maintains morale because people understand that what they're doing matters.

What Happens After Leadership Alignment

Once leadership is aligned, we work with the operational teams to understand the actual processes, the data, the constraints, and the opportunities. We map where your time is actually spent. We identify which parts of your work would genuinely benefit from automation and which parts shouldn't be automated. We recommend specific tools based on that assessment. We create a realistic implementation plan with clear milestones and resource requirements. We identify risks and how to mitigate them.

By the time we get there, we're not starting from scratch with leadership buy-in. We're implementing something they've already committed to and understand. Implementation still has challenges, but at least the leadership team isn't a source of friction. At least when something is difficult and the team is tempted to give up, leadership is there saying "this is important, we're going to work through the difficulty."

The organisations that succeed with AI are those where leadership and operations are pulling in the same direction. Where leadership has committed resources, created space for disruption, and stayed committed when things get difficult. Where operations understands why the change matters and gets the support they need to make it work. That alignment doesn't happen by accident. It happens because someone intentionally built it at the beginning of the project.