Skip to content
Foundations · Written for management, not engineers

Why AI? A director's foundation

Every guide tells you how to use AI. Almost none tell you why it exists, why it works, or why it arrived now and not thirty years ago. That gap is what leaves a director nodding along in meetings while somebody junior quietly runs the room. This is the other guide.

🎯 No prompts, no tools 📊 2 figures, 1 framework 💬 Vocabulary you can use ⏱ 14 min
Ingredients
4
Terms you’ll know
28
Boardroom questions
6
Idea → your desk
1943→2026
🧠
The core idea

AI is pattern recognition, industrialised

Strip away the marketing and artificial intelligence is one thing: a machine that finds patterns in examples, then applies those patterns to something it has never seen before. That is the whole idea. Everything else is engineering around it.

A de-lidded GPU die under macro photography, showing the physical circuitry beneath “billions of parameters”
An actual chip die under a macro lens. This is what “billions of parameters” physically sits on. Photo: Fritzchens Fritz, CC0.
A pattern engine turning examples into a prediction EXAMPLES Thousands of pastcases, labelled THE MACHINE Adjusts billions ofinternal numbers untilits guesses stop being wrong PREDICTION Applied to a caseit has never seen
Figure 1: the whole idea, in one picture. Everything else in this guide is detail underneath these three boxes.

This tells you what AI is for. Not a thinking machine, not a database: a pattern engine. The right question on any AI project never changes: is there a real pattern in this data, and do we have enough examples of it?

The old way

You write the rules

A person decides the logic in advance. If the invoice is over 50,000 dirhams, route it to finance for a second signature.

This works beautifully when the rules are few and knowable. It collapses when they are not. Nobody can write the rule for “this photograph contains a cat” or “this customer is about to leave us.”

The new way

The machine finds the rules

You supply examples instead of logic. Here are 200,000 invoices and what happened to each one. Here are eleven years of customers and which ones left.

The system works out the patterns itself, including ones nobody thought to look for. You never write the rule, and often you cannot read it afterwards.

A director’s rule of thumb for the budget meeting
📋

Rule known, data thin

Ordinary software. Code the logic directly. Cheaper, faster, easy to audit.

🗃️

Rule known, data rich

Keep the rule running, but mine the history sitting behind it. That data will sharpen the next decision.

⏳

Rule unknown, data thin

Not ready. Collect real examples first. A model has nothing to learn from silence.

🎯

Rule unknown, data rich

The genuine AI candidate. This is the quadrant the technology was built for.

Half the failed AI projects in any company sit in the top-left box: an ordinary software problem, wearing an expensive costume.

Humans have always done this. A buyer with thirty years in a market can look at a supplier and tell you something is wrong without being able to say what. That is a pattern learned from thousands of examples, held below the level of language. AI does the same thing, on more examples than one lifetime allows, and with no ability to explain itself either.

⏳
Why this decade

The idea is old. The conditions are new.

The core idea is not new. In 1943 the neuroscientist Warren McCulloch and the logician Walter Pitts published a mathematical model of a single artificial neuron. By the 1980s, researchers including Geoffrey Hinton had working methods for training networks of them. Most of the mathematics behind what you are reading about was settled before the web existed. So the honest question is not what did they invent but what changed.

Four things have to be true at once for this to work. Until recently, no era had all four.

Ingredient one
Computing power
Enough arithmetic to push millions of examples through a model repeatedly, at a price a business can absorb.
Ingredient two
Data
Enough real examples that the patterns found are genuine signal rather than coincidence.
Ingredient three
Algorithms
Methods that actually improve as you add more data instead of stalling, which older approaches did.

The fourth is the unglamorous one: infrastructure. Storing, cleaning, labelling and moving that volume of data is most of the real work, and it is where most corporate AI programmes actually fail. Not at the model. At the plumbing.

  • 2006
    Cloud storage becomes a utility
    Keeping enormous datasets stops being a capital project and becomes a line item. Data that used to be discarded starts being kept.
  • 2012
    AlexNet wins ImageNet, by a landslide
    Three Toronto researchers, Alex Krizhevsky, Ilya Sutskever and Geoffrey Hinton, enter the annual ImageNet contest with a large neural network. It beats the next-best method by roughly 10 percentage points. The field reorganises around the approach within two years.
  • 2016
    Graphics chips become the engine
    Hardware built for rendering games turns out to be near-perfect for the arithmetic neural networks need. Training times collapse from months to days.
  • 2017
    “Attention Is All You Need”
    Eight researchers at Google publish the transformer architecture under that title. It handles language and context far better than anything before it, and keeps improving as it is made bigger. Every system you have heard of since, GPT, Gemini, Claude, descends from this one paper.
  • 2022–2026
    General-purpose systems reach the desk
    Models stop being one-task tools built by specialists and become general instruments any employee can use without permission, budget or training. This is the part that reached your organisation.
The technology did not sneak up on your industry. The cost did. What was a research budget in 2015 is now a subscription.The actual shift

This is why treating AI as a passing enthusiasm is a category error. Enthusiasms fade because the thing underneath them was never real. Here the underlying conditions, cheap computation and abundant data, are not reverting. They compound.

📚 Read the sources in full

McCulloch, W. S., and Pitts, W. (1943). “A Logical Calculus of the Ideas Immanent in Nervous Activity.” Bulletin of Mathematical Biophysics, 5, 115–133. The first mathematical model of an artificial neuron.

Krizhevsky, A., Sutskever, I., and Hinton, G. E. (2012). “ImageNet Classification with Deep Convolutional Neural Networks.” The AlexNet paper, presented at NeurIPS, that won the ImageNet contest by a wide margin and reset the field around deep learning.

Vaswani, A. et al. (2017). “Attention Is All You Need.” Eight authors at Google, published at NeurIPS. Introduces the transformer architecture underneath every large language model in this guide.

⚙️
The mechanism

Inside the machine, without the mathematics

You do not need to build one. You need to know roughly what is happening inside, because that is what lets you tell a sound plan from an expensive one.

A neural network is a long chain of simple arithmetic. Data enters at one end. It passes through layer after layer, each one multiplying and combining the numbers slightly differently. A result comes out the other end: a category, a score, a next word.

Rows of server racks inside a real data center, the physical hardware training happens on
Training happens on rooms full of these. Photo: PDC, CC BY-SA.
Data entering a neural network and a prediction leaving it INPUT HIDDEN LAYERS OUTPUT billions of these connections adjust during training, none of them labelled by a human
Figure 2: the raw numbers go in on the left. Nobody assigned meaning to the middle. One prediction leaves on the right.
What actually happens to one example
Inputthe raw example
Hidden layerswhere the pattern lives
Outputthe prediction
InputA loan application: income, tenure, sector, existing debt, 40 other fields.
The layersEach layer combines those numbers into slightly more abstract ones. Nobody assigned meaning to them; the meanings emerged during training.
OutputProbability of default: 0.07. The number is a confidence, not a fact.
The layers hold parameters — the numbers that get adjusted during training. A modern system has billions of them.

Those parameters start as noise. Training is the process of correcting them, and it is far less clever than it sounds:

  1. Show the system one example where you already know the right answer.
  2. Let it guess. Early on the guess is close to random.
  3. Measure how wrong it was. That measurement is called the loss.
  4. Nudge every parameter a fraction in whichever direction would have made the guess less wrong.
  5. Repeat several million times. There is no fifth step. That is the entire method.

Two consequences follow directly, and both are commercial rather than technical.

First, the system can only be as good as the examples you showed it. If your historical decisions were biased, the model learns the bias precisely and applies it consistently at scale. It does not average out human error. It industrialises it.

Second, nobody can point to where the knowledge sits. It is spread across billions of parameters with no labels. This is the real reason AI systems are hard to audit, and why any vendor promising full explainability deserves a second look.

Why humans cannot simply write these rules

Three reasons. The number of inputs is too large — a photograph is millions of numbers. The inputs interact — two factors together mean something neither means alone. And the volume required is beyond a person — the patterns only become visible across hundreds of thousands of examples. Machines are not smarter here. They are just tireless.

💬
Terms in the room

What your team means when they say it

Most of the authority gap in an AI review is vocabulary, not intelligence. These are the terms that come up, what they actually mean, and what each one should make you ask.

Training data
The examples the system learned from. The single most important input to any AI project, and the one least often examined in a steering meeting. Ask where it came from and who labelled it.
Accuracy is 94%
Right 94 times in 100 — on some specific test. Meaningless without context. If 96% of transactions are legitimate, a fraud model that flags nothing at all scores 96%. Ask what the baseline is.
Overfitting
The system memorised the training examples rather than learning the pattern. It performs brilliantly in the demonstration and poorly in production. One of the most common causes of an AI pilot that never scales.
Test set / holdout
Examples deliberately kept back so the system is judged on data it has never seen. If a result was not measured on a holdout, it is a rehearsal, not a result.
Loss
How wrong the system currently is. It falls during training. When it stops falling, training has finished — for better or worse.
Parameters / weights
The billions of adjustable numbers inside the model. More is not automatically better; it costs more to run and needs more data to train properly.
Fine-tuning
Taking a system somebody else trained at enormous expense and adapting it to your specific task with a comparatively tiny amount of your own data. Usually the sensible commercial choice.
Inference
Running the trained model to get an answer. Training is the capital cost, paid once. Inference is the operating cost, paid on every single request, forever. Ask about it early.
Hallucination
The system produces something fluent, confident and false. Not a bug being fixed — a direct consequence of how these systems generate output. Design the process assuming it will happen.
Drift
The world changes, the training data does not, and the model quietly degrades. A model is not an asset you install. It is one you maintain.
Six questions that establish you know the subject
  • Where did the training data come from, and who labelled it?
  • What is the accuracy on data the model has never seen, and what does a do-nothing baseline score?
  • What does it cost per thousand predictions once we are live?
  • What happens when it is confidently wrong, and who sees it before the customer does?
  • How will we know when it starts to drift?
  • If we removed the AI from this process tomorrow, what would actually break?

The last question is the most useful one you own. A good team will answer it precisely. If the answer is vague, the project is decoration.

The ten terms above are the foundations. These eighteen are what floated into the room since generative AI arrived — darker tiles are the ones where getting it wrong costs more than looking uninformed. Each links to one free (or clearly marked paid) course if you want the fuller version.

The umbrella term for any system doing something that used to need a person: recognising, deciding, generating. It is not one product. When someone says “we’re adding AI,” ask which specific technique inside it they actually mean. Free: DeepLearning.AI, “AI For Everyone.”
The technique underneath most of what gets called AI today. The system learns the rule from data instead of being told the rule. The rule is only as good as the data, so ask what the data was before asking about the model. Free to audit: Stanford/DeepLearning.AI’s Machine Learning Specialization.
A method inside machine learning using many-layered models, the engine behind image recognition and language models. It needs a lot of data and compute. If a small dataset is getting the “deep learning” label, that is usually the wrong tool for the job. Free to audit: DeepLearning.AI’s Deep Learning Specialization.
A deep learning model trained on huge amounts of text to predict and generate language: GPT, Claude, Gemini and similar. Most “AI chatbot” projects today are an LLM wearing a company logo. Ask which model, and whether it runs through a paid API or in house. Free: DeepLearning.AI, “How Transformer LLMs Work.”
The wider category above LLMs, any system that creates new text, images, audio or code rather than only classifying or predicting. Ask what happens the moment it generates something wrong, since nothing here comes with a guarantee. Free: Google Cloud, “Introduction to Generative AI.”
The field of getting a computer to work with human language. LLMs are the newest branch of it, but NLP also covers older, cheaper tools like spam filters and sentiment scoring. Not every “reads the text” pitch needs the expensive branch. Free to audit: DeepLearning.AI’s NLP Specialization.
AI applied to images or video: quality-control cameras, document scanning, facial recognition. Ask about accuracy on your own images specifically. A model trained on generic photos often struggles on a niche factory floor or warehouse shelf. Free: Microsoft Learn.
Tokens are the small chunks of text a model reads and bills by. The context window is how much it can hold in view at once. If a project reads long documents, ask about the context window — that decides whether it sees the whole file or only part of it. Free: DeepLearning.AI.
Writing instructions carefully to get useful output from an LLM. Real, but limited. If a project’s entire pitch is “we wrote a good prompt,” that is a thin foundation, not a moat. Free: DeepLearning.AI, “ChatGPT Prompt Engineering for Developers.”
Connecting an LLM to your own documents so it answers from your real data instead of only what it memorised in training. This is how most “AI that knows our company” tools actually work. Ask how the source documents stay current — stale data is the most common failure. Free: DeepLearning.AI.
The plumbing behind RAG. Embeddings turn text into numbers that capture meaning; a vector database stores and searches those numbers fast. You do not need the mechanics, just know it is what runs underneath any “search our files with AI” feature. Free: DeepLearning.AI, “Understanding and Applying Text Embeddings.”
Models learn from historical data, so they can repeat historical unfairness in hiring, lending or similar decisions. If a project decides something about people, ask what it was tested for and against which group. A legal exposure question now, not only an ethical one. Free: Google Cloud, “Introduction to Responsible AI.”
The step beyond chatbots: a system that takes multi-step actions on its own — browsing a site, sending an email, editing a spreadsheet. Higher risk because it acts, not just advises. Ask what stops it from taking the wrong action. Free: DeepLearning.AI, “Functions, Tools and Agents with LangChain.”
Most AI projects do not build a model, they call one over the internet from OpenAI, Google or Anthropic and pay per use. Ask which provider, and what happens to your company’s data once it leaves the building. That is the real privacy question. Free: AWS Skill Builder.
The specialised, expensive hardware AI runs on. Almost everyone rents it rather than owns it. If someone proposes buying hardware or training a model from scratch, that is a materially bigger and riskier budget than calling an existing API. Know which one you are actually signing off. Needs Coursera Plus or paid enrollment: Google Cloud’s “AI Infrastructure: Cloud TPUs.”
Closed models like GPT and Claude run through a paid API and you never see inside them. Open-source models like Llama or Mistral can be run and changed privately, often better for data privacy, but need real in-house skill to operate well. Ask which is proposed, and why. Free: DeepLearning.AI, “Open Source Models with Hugging Face.”
The policies, review steps and named owner that should exist before an AI project touches real customers or decisions. If none of this exists yet at your company, that gap is bigger than any single project on the table. Raise it on its own. Free: Google Cloud, “Responsible AI: Applying AI Principles.”
Narrow AI does one thing well, which is everything that exists today. AGI is the hypothetical future system with general, human-level intelligence — it does not exist yet, no matter what a pitch deck implies. Multimodal means one model handling text, image and audio together. Treat any “close to AGI” claim as marketing, not fact. Free: Microsoft Learn, “Fundamental AI Concepts.”
🚧
The boundary

What it does well, and what it cannot do at all

Knowing the limits is worth more than knowing the capabilities. The capabilities are advertised to you daily. The limits are where the money is lost.

Genuinely strong at

  • Recognising patterns across data too large for a person to hold
  • Forecasting when the future resembles the past
  • Sorting things into categories at volume
  • Flagging the anomaly in ten million ordinary records
  • Producing a competent first draft of almost anything
  • Doing all of the above without fatigue or mood

Cannot do, and will not soon

  • Distinguish correlation from causation
  • Handle situations genuinely unlike its training data
  • Make an ethical judgement — it optimises what you specified
  • Explain its reasoning in terms you can audit
  • Know when it is wrong, which is why it is confidently wrong
  • Take responsibility, which remains yours

The causation point is the expensive one, so it is worth an example.

A pattern that is real and still a trap

A model reviewing years of lending finds that applicants from one district default less often, and starts favouring them. The pattern is real. But the cause was that a single experienced officer covered that district and screened well. Promote him, and the pattern dissolves — while the model keeps applying it, now as a straightforward geographic bias, at scale, in writing. The model was never wrong about the correlation. It simply has no concept of why.

Which is the honest summary of the whole technology. It finds what travels together. It has no idea what causes what. Supplying the why is the part that stayed human, and it is the part directors are paid for.

♟️
The commercial case

Why this sits on your desk and not in the IT department

A technology becomes a management problem, rather than a technical one, at the moment it changes what a company can be asked to do. AI crossed that line when it became cheap enough for any employee to use without approval.

Three consequences reach you directly.

One

Capital allocation, with no reliable instinct to fall back on

Your decision, not your CTO’s

You will be asked to fund AI projects. Some are genuine and some are ordinary automation with a fashionable label. Without a working model of why AI succeeds or fails, you are choosing between them on the quality of the presentation.

Four questions and most weak proposals do not survive them:

  • Is there a real pattern here, and not just a hunch?
  • Do we have enough examples to teach it?
  • Was it measured on data the model has never seen?
  • What does it cost per prediction once we are live?
Two

It is already inside the organisation

Whether it was procured or not

Your staff are pasting material into AI systems today. Some of it is confidential. This is current practice in nearly every company of any size, procured or not.

A director who understands the mechanism sets three things in one page:

  • What data may leave the building, and what may not
  • Which decisions need a human to check the answer first
  • Where a confident, wrong answer would actually cost money

A director who does not tends to reach for a blanket ban, which staff ignore, or a blanket permission, which is worse.

Three

Authority is downstream of comprehension

The part nobody says aloud

People calibrate quickly to whether a leader understands the thing being discussed. Once a team concludes you do not, they stop bringing you the difficult version of the decision and start bringing you the version that gets approved. You lose the information before you lose the authority.

The remedy is not fluency in the tools. It is the mechanism, the vocabulary and a handful of questions that cannot be answered with enthusiasm. That is recoverable in an afternoon, which is roughly what this page is.

You are not competing with your staff on how well you use these systems. You are responsible for whether the organisation uses them correctly — and that is a different subject entirely.The actual division of labour
Case for your next meeting

A regional manager shows you a model that predicts which branches will miss their quarter, 91% accurate on last year’s data. Funding is on the agenda in ten minutes.

Before you approve it: what did 91% beat? A branch missing its quarter is rare, so a model that predicts “no branch will miss” every time might already score close to that. Ask for the baseline before you ask for the budget.

✅
Monday morning

What to do with this

Four moves, in order

  • Inventory what is already running. Ask each function what AI they use, sanctioned or otherwise. The list is always longer than the register.
  • Take one live project through the six questions. You will learn more about your organisation’s AI maturity in that hour than from any external assessment.
  • Write down where a confident wrong answer costs real money — pricing, credit, clinical, legal, anything customer-facing. Those get human review. Everything else can move faster.
  • Decide what data may leave the building, and say it in one page that a person can actually follow.

None of that requires a tool, a vendor or a budget. It requires understanding why the technology behaves as it does, which you now have.

For the director who wants the actual course
🎓

AI Essentials for Business

Harvard Business School Online, taught by Jeffrey Bussgang, Senior Lecturer in Entrepreneurial Management. Four modules: The Age of AI, The Rise of Generative AI, Strategy (network and learning effects), and the Transformation Journey.

See the course →

🏛️

Future Proof with AI

From Harvard Business School's AI Institute, led by Karim Lakhani with seven other HBS faculty. Splits AI into predictive, generative and agentic, with tracks for strategy, finance, HR, marketing and R&D.

See the course →

This guide gets you through the door in ten minutes. Those two are the multi-week version, taught by the people who did the underlying research.

Five videos, if you would rather watch than read
Andrew Ng, Stanford GSB. The most quoted explanation of why AI matters at all, in under ten minutes.
Eric Schmidt, former Google CEO, TED. The view from inside one of the five companies building this.
Greg Brockman, OpenAI President, TED. Why the company that built the tool is also its biggest source of hype.
Google Cloud Tech. The architecture behind GPT, BERT and T5, the paper cited in this guide’s sources, on video.
3Blue1Brown. The clearest visual walkthrough of the mechanism in Section Three, if the diagrams were not enough.
Five affordable courses, Udemy and Coursera
Andrew Ng, DeepLearning.AI on Coursera. No coding. The non-technical primer this guide draws its spirit from.
Andrew Ng, DeepLearning.AI on Coursera. The same approach, aimed specifically at the generative wave.
Google on Coursera, around $49. Built by one of the companies running the largest models in production.
Kartik Hosanagar, Wharton on Coursera. Strategy, governance and applications, written for a leadership audience.
Udemy, one-time purchase, often discounted. The cheapest entry point of the five.
Where the automation itself lives
Send-time optimisation and AI-written copy, built into a tool most small marketing teams already own.
Workflow automation across email, SMS and WhatsApp. Common in e-commerce and retail.
AI layered across the CRM: lead scoring, content drafts, and pipeline reporting in one place.
Autonomous agents for sales and service, built by one of the five companies this guide keeps returning to.
On-brand marketing copy at volume, the tool most often behind a company’s daily outreach emails.
The one-sentence version

AI is pattern recognition at industrial scale; it arrived now because computation and data finally became cheap at the same moment; it is exceptional at finding what travels together and incapable of knowing what causes what — and that last gap is precisely where your job still lives.

Want this applied to your own operation?

I build AI agents, automation and reporting for Gulf businesses — owner-operated, no agency layer, and no project that cannot answer the six questions above.