Technology judgement for non-technical directors

Who this is for

This is for the director, trustee, or senior sponsor who is asked to approve software, AI seats, or a robotics cell and does not have an engineering background. The paper is fluent. The demo is clean. The risk sits with you if the thing does not earn its keep, or if it creates a mess in a customer file.

You do not need to learn to code. You need a short list of questions the vendor and your own team cannot slide past.

The business problem

Tool spend has become easy to wave through because everyone else is buying. McKinsey reported in 2025 that 88% of organisations use AI in at least one function while only about a third have scaled past pilots, and that only 39% see any EBIT impact. The Conference Board reported in 2026 that only 33% of workers received employer AI training in the last six months. TalentLMS reported in 2025 that 49% of workers say AI is moving faster than their company's training. World Economic Forum reporting in 2025 found that 63% of employers name skill gaps as the top barrier to transformation.

That is a board-level pattern: capital and licences ahead of judgement and training. The licences are paid for. The team was not trained. is what that looks like after the invoice. This note is what to do before you sign.

A recorded LMS module will not give you that judgement. See In-person AI training versus an LMS module if someone has offered you a digital academy as the entire capability plan.

What judgement is, for a non-technical director

Judgement here is not a architecture review. It is the ability to test a proposal against the work, the people, and the record.

The work. Which process gets better, in a sentence a supervisor would recognise? If the answer is "innovation" or "transformation," send it back.

The people. Who will use it every week, who will check the output, who owns it when it fails? If the answer is "IT will roll it out," you are buying a deployment, not a capability.

The alternative. What happens if you do nothing, or if you train on the tools you already own? New spend is not the only option.

The evidence. What will you look at in 90 days that is not a vendor dashboard? If there is no answer, you are buying a story.

McKinsey has also reported that leaders with highly AI-fluent teams are 3.9 times more likely to capture enterprise value. Fluency is a people fact. A platform purchase without a training line is a bet against that fact.

Questions that expose a weak paper

Ask these in the room. Write the answers down.

1. Which roles, by name of function, will use this weekly?
2. What is the checking standard for an output that leaves the organisation?
3. What data must never go in, and who enforces that?
4. What do we already pay for that this duplicates?
5. Who is trained before go-live, live, with a register?
6. What does "stop using it" look like, and who can call that?
7. What will I be shown in a quarter that I can understand without a specialist?

If the presenter cannot answer 4, 5, and 7, you are not ready to sign. Choosing Technology Well is the course Experrt runs so sponsors practise those questions on real proposals, not on a case study from another industry.

Technology for Non-Technical Leaders is the foundations session: enough vocabulary to stay in the conversation without pretending to be the architect. AI Strategy and Oversight for Executives is the board-level version when the spend is an AI programme rather than a single tool.

What good looks like

A director who can judge technology will delay a purchase until the role map and the training line are on the same page as the price. They will prefer a smaller, trained rollout to a wide licence dump. They will treat "everyone is buying this" as a reason for caution, not a reason to hurry.

They will also refuse a certificate as proof of value. Certificates prove attendance at best. Value is checked work and a process that still runs when the vendor is not in the building. If the only artefact in the paper is a logo wall and a go-live date, you are being asked to fund a launch, not a capability.

What to insist on before you approve

• A one-page role and process map attached to the business case.
• A training line with dates, not "enablement to follow."
• An owner who is not the salesperson.
• A 90-day evidence list you can read.
• A written alternative: train on what you already have, or do not buy.

Experrt is a training academy. We will not tell you which vendor to pick, and we will not take a cut of the licence. We will train the people who have to live with the decision, including the directors who have to sign it.

What to do before the next paper

Take the last three tool approvals and ask which of the seven questions were answered in writing. The gaps are your curriculum. Book a short director session if the next paper is already in the diary.

Contact Experrt with the kind of spend on the table (AI seats, a platform, a cell) and who signs. We will tell you which cohort should sit first.