an experienced professional confidently directing AI-assisted work

AI for people who weren't “born digital”: you don't need to be technical to be good at this

“I am not technical enough for AI” is an expensive sentence at work. It makes people sit out before they have even tried the useful part.

The gap is real. The newest EU-wide digital-skills release, published in June 2026 and based on 2025 data, reports that 60% of EU citizens aged 16 to 74 had at least basic digital skills. It also reports strong variation by age and education. Eurostat, 2026

But a gap in experience is not a verdict on ability.

It tells us who has had more practice with digital tools. It does not tell us who can learn a new one, make a good decision, understand a customer, or spot nonsense in a report.

And those last skills matter a lot when you use AI.

AI literacy is not a coding test

You do not need to write software to use a chatbot well.

You do need to understand what it can do, where it can go wrong, what information you should not share, and how to check its work.

That is not just my opinion. The EU's AI-literacy guidance tells organisations to consider staff members' technical knowledge, experience, education, training, and the context in which an AI system is used. In other words, the right level of learning depends on the job and the tool. One-size-fits-all training is not the point. European Commission, AI literacy Q&A

For a normal office worker, that usually means learning how to do a few very ordinary things well:

  • Give a clear brief

  • Ask for the output in a useful format

  • Check facts, names, numbers, and sources

  • Keep confidential information out of unapproved tools

  • Improve a draft instead of accepting the first answer like it came down from a mountain

None of that requires coding.

It requires judgment.

Your work experience is not the problem. It is the advantage.

A younger colleague may be quicker to open a new app. Great. That is useful.

But speed is not the same thing as good work.

You know what a reasonable client email sounds like. You know which numbers in a report matter. You know that a proposal can be beautifully written and still completely miss the point. You know when somebody is confidently talking rubbish.

Those are exactly the things AI does not know on its own.

AI can give you a draft in seconds. It cannot know whether your customer has been frustrated for three months, whether a number is commercially sensitive, or whether your manager hates three-page updates.

You supply the context. You make the call. You are still the person responsible when the work leaves your desk.

Learn by doing one real task, not by watching twenty demos

There is a lot of AI content that makes learning feel like homework. Long videos. Endless lists of tools. Skip it for now.

Start with a task you already understand.

Try this 20-minute exercise instead:

  1. Pick one boring task from this week. A follow-up email. A meeting summary. A first draft of a proposal. Something real.

  2. Explain the situation in plain language. Who is this for? What happened? What needs to happen next?

  3. Tell AI exactly what you want back. A five-bullet summary. A short email. A table of actions and owners.

  4. Read the result like an editor, not a fan. What is missing? What is wrong? What sounds unlike you?

  5. Tell it what to change. “Keep the structure. Make it shorter. Remove the jargon. Add the deadline.”

That is already a proper AI skill.

You are directing work.

The four things worth learning first

If you are starting from zero, do not try to learn everything. Learn these four habits.

1. Give context.

“Write an email” is not a brief. Tell it who the reader is, what happened, what tone you need, and what the email must achieve.

2. Ask for the finished format.

Do not ask for “ideas” when you need a two-paragraph email. Ask for the two-paragraph email.

3. Check anything that matters.

AI can be helpful and wrong in the same sentence. Check facts, figures, quotes, sources, and anything you will send, publish, or use to make a decision.

4. Protect the information you were trusted with.

Do not paste confidential client data, employee information, passwords, contracts, or internal figures into a tool unless your organisation has explicitly approved that exact use.

That is the foundation. Not secret prompt tricks. Not a fifty-tool stack. Four habits.

You do not need permission to start small

Follow your company's rules for particular AI tools and work information. Then practise with a safe, low-risk task: a generic email, your own rough notes, or public information.

The European Commission's guidance makes the same practical point from the employer side: AI literacy should reflect the tool, the task, and the risks involved. The first useful lesson for someone writing marketing copy is not the same as the first lesson for someone using AI in recruitment or healthcare. European Commission, AI literacy Q&A

Start where the risk is low and the value is obvious.

The question to ask instead

Do not ask, “Am I technical enough for AI?”

Ask, “Can I describe the job clearly, recognise a bad answer, and take responsibility for the final one?”

If the answer is yes, you already have the part that matters most.

The rest is practice.

You are not too late. You do not need to become an engineer. You need to become a better director of the work already on your desk.

If you want a simple starting point, my free PDF guide walks through the core framework for giving AI clear instructions and checking the result. [free guide link]

Sources

Back to blog

Share