← All services
AIStrategyReadiness

AI Readiness Check

You want to use AI. Is your organisation actually ready to use it well?

A practical readiness review before AI enthusiasm turns into scattered experiments, blocked pilots or expensive tools without a clear use case.

Start with what is actually happening.

  • Different teams are experimenting independently.
  • Security questions stop conversations before use cases are understood.
  • There are dozens of ideas but no prioritisation.
  • Management wants AI use cases quickly.
  • People talk about models and tools more than the work that should improve.

Good work starts with better questions.

01

Where could AI create real value?

02

What foundations are missing?

03

Which risks actually matter in your context?

04

Which use cases are worth testing first?

The scope follows the problem.

I do not force every engagement through the same checklist. These are the areas that may matter; the agreed scope determines how deep we go.

Processes and recurring knowledge work

Data availability and sensitivity

Current tooling

Security and governance constraints

User capability and confidence

Human oversight requirements

Adoption readiness

Ability to measure value

Something you can use after the conversation ends.

The output should help you make a decision, change a practice or move the work forward. It should not exist simply to prove that work happened.

01

Readiness Assessment

Where you are ready to experiment and where basic conditions still need attention.

02

Opportunity Areas

The parts of work where AI could plausibly create value.

03

Risk & Dependency Map

Security, data, process and ownership constraints that need to be handled deliberately.

04

Priority Recommendations

What to explore first and what not to prioritise yet.

05

90-Day Starting Plan

A practical way to move from discussion to controlled learning.

Enough structure to make the work clear. Not so much process that the process becomes the work.

01

Context

We start with a short conversation about what is happening, what matters and what has already been tried.

02

Review

I analyse the relevant parts of the solution or operating model at the depth agreed for the engagement.

03

Prioritise

I organise observations around impact, risk and usefulness — not around how many issues I can find.

04

Walkthrough

We go through the findings together, challenge assumptions and discuss trade-offs.

05

Next step

You decide what happens next: implement internally, continue together or stop because the focused engagement was enough.

I keep the client-side time demand deliberately light. A focused assessment usually needs a kickoff conversation, access or materials, and a final review session. We agree the exact involvement before we start.

This is likely to help if...

  • AI interest is high but direction is still unclear.
  • You want to avoid buying tools before understanding use cases.
  • You need business, data, risk and adoption considered together.
  • You already have a validated use case and only need software implementation.
  • You are looking for formal legal advice on AI regulation.

If the problem is real but the format is wrong, that is useful to know early. I would rather redirect the conversation than force the challenge into the wrong service.

This does not automatically lead to another engagement.

Sometimes the focused piece of work is enough. If it reveals a useful next step, these are some of the directions that may make sense.

You want to use AI. Is your organisation actually ready to use it well?

Bring me the problem, not a polished brief. A few sentences about what is happening and what you would like to change are enough to start.

Tell me what's happening

Send me a message.

You do not need a polished brief. Whether the topic is Power BI, Fabric, AI, team training, mentoring, coaching or simply a challenge that needs untangling, leave a few details and we can start from there.

SIGNALMESSAGECONVERSATION

AI & TRANSPARENCY

AI supports selected parts of my work — it does not replace my judgement, responsibility or relationship with the client.

I use AI tools for tasks such as research, organising information, structuring content and preparing materials. I treat AI as support for my work — not as an autonomous author or decision-maker. Anything I publish or use professionally remains my responsibility.

In coaching, I do not use AI to automatically assess, diagnose or make decisions about a client. AI does not replace attention, confidentiality or human responsibility for the coaching relationship.

AI may support the process. Human responsibility remains.