Before You Implement Technology or AI, Three Questions for Your Teams

When we engage with an organisation looking to build a new technology solution or start an AI initiative, the first question is usually about technology.

"Which tool should we use?"
"Should we build a web app or a mobile app?"
"Can AI do this for us?"

These are fair questions. They are also the last ones we should answer.

After twenty years of working with teams on design and innovation, there are three other questions I would like a team to answer first. Each comes at the problem from a different angle: the leader, the team, and the people being served. Most stuck projects have an unclear answer to at least one of them.

1. Who owns the outcome?

This is the leader's side of the picture.

As an outside partner, I usually already have a working relationship with one part of the organisation — IT, Strategy, Operations, HR, Marketing, L&D, or an innovation team, depending on who engaged us.

Each of them holds a real piece. The business knows why it matters. Technology knows what is possible and safe. Operations knows how the work actually gets done. Design knows whether it works for people. L&D knows what skills are missing.

The trouble starts when one of them ends up owning the whole thing by default.

• Strategy alone gives you roadmaps and slide decks, and little change on the ground.
• Technology alone gives you tools looking for a problem.
• Change management alone gives you campaigns for something nobody needed.
• Training alone gives you certificates, while the work stays the same.

So the question is not "who owns AI?" or "who owns the technology?" It is: who owns the result this is meant to improve?

That person does not have to do everything. They need the authority to bring the right people together, and to decide when priorities clash.

As an external partner, we can help drive the change. We cannot own the result. That has to sit inside the organisation.

2. Is the team prepared to work differently?

An owner with a clear goal still needs people who can do the work of change. That takes more than AI skills.

A mix of skills. The team needs to be able to manage stakeholders, generate ideas, make those ideas visible, present them, and work well across functions.

A shift in mindset. This is the harder part, and it can feel uncomfortable.

• From "we already have all the information" to being curious.
• From starting with the company or the product to starting with people.
• From needing clear instructions to being able to work with what is still unclear.
• From "we cannot fail" to learning from what fails.
• From one right answer to several points of view.

An AI initiative demands this even more. When a tool hands you a polished answer in seconds, it is tempting to skip the slow work of understanding the problem.

A well-prepared team knows when to trust an AI output, when to challenge it, and when not to build anything at all.

3. What is worth building?

This is about understanding the needs of the people being served.

AI has made building very cheap. One person can now make a working prototype in an afternoon. That is a gift when you are building for yourself.

It becomes a risk when everyone in the organisation can do it. You end up with many small tools that each made sense on their own, and are hard to manage together.

The AI Builder Paradox: the easier it is to build, the more it matters to decide what is worth building.

Three steps help teams align.

1. Agree on the service, not the software. What is each group really trying to get done? Where does it break down today, and who quietly pays for that?
2. Map the service. The screen is the smallest part. Most of the cost and risk sit behind it — the records, approvals and data, and the people who keep it all running.
3. Work from the outcome down. Start with the result that matters most. List what stands in the way. Then weigh the options, and remember that some gaps are closed by changing a process or a role, not by adding software.

After that, questions like "web app or mobile app?" usually answer themselves. The platform follows the needs of the user — where they are, and what they are doing at the time.

Why all three, together

Each question fails without the other two.

• An owner without a prepared team gets a mandate nobody can deliver.
• A prepared team without an owner gets good ideas with no authority behind them.
• An owner and a team without a clear view of what to build get speed in the wrong direction.

Transformation is one journey seen from three sides: who is accountable, who does the work, and who it is for.

AI makes building cheaper. It does not make deciding easier.

So before your next project, try the three questions with your team.

Who owns the outcome?
Are we prepared to work differently?
What is worth building?

Which of the three is hardest to answer in your organisation right now?