Why Everyone's Talking About Data (And Why You Should Care)

Here's a sentence you've probably heard a dozen times in the last year: data is the new oil. It's become one of those phrases people drop in meetings to sound smart, right up there with synergy and circle back. But strip away the buzzword and there's something real underneath it — something that quietly decides which businesses grow and which ones stall out.

This series is about the skill that sits behind that sentence: SQL. Not because SQL is trendy (it's actually older than the internet), but because it's the single most useful, most underrated skill a non-technical person can learn right now. And here's the twist that surprises most people: in the age of AI, SQL matters more than ever, not less.

Let me explain why.

From gut feel to spreadsheets to databases

For most of business history, decisions were made on gut feel. A shopkeeper in Mombasa knew which products sold because he watched the shelves every day. A matatu operator knew which routes made money because he counted the coins at the end of each trip. When your business was small enough to hold in your head, intuition was plenty.

Then businesses got bigger. Spreadsheets arrived, and for a while they felt like magic. Suddenly you could track sales in rows and columns, and run a total at the bottom with a formula. Excel and Google Sheets became the default "data tool" for an entire generation of founders, accountants, and operations managers.

But spreadsheets have a ceiling. The moment your data grows past a few thousand rows, or lives in more than one place — orders in one sheet, customers in another, payments in a third — spreadsheets get slow, error-prone, and painful. You've probably felt it: the file that takes 30 seconds to open, the formula that breaks when someone adds a column, the "which version is the real one?" email thread.

Databases solve exactly this. They're built to hold millions of rows, stay fast, and keep data consistent. And SQL is the language you use to talk to them.

What SQL actually is (in one sentence)

Here's the whole thing, in one sentence:

SQL is a language for asking questions of a database — short, written instructions that pull out exactly the information you need.

That's it. SQL stands for Structured Query Language, and a "query" is just a question. When you write SQL, you're not programming in the scary sense — you're writing a very precise sentence that says "give me this data, filtered like this, sorted like that."

The best part is that SQL is close to plain English. The two most important words in the entire language are SELECT and FROM, which is exactly what it sounds like: select these things from that table. We'll write your first real query in the very next post, and you'll see how little ceremony is involved.

One more reason SQL is worth your time: it's not a passing fad. It's been the standard way to talk to databases for over fifty years — since 1974 — and it still quietly runs the world, from bank ledgers to airline bookings to the apps on your phone. Unlike the framework of the month, SQL is a skill you'll still be using in twenty years. It's the Latin of the data world: old, stable, and still holding everything together.

Why AI makes SQL more relevant, not less

Here's the part that surprises people. You might think: if AI can write SQL for me, why learn it at all?

That's the right question to ask, and the answer is genuinely interesting. AI can write SQL — tools like ChatGPT are remarkably good at turning "show me our top customers this month" into a working query. But here's what nobody tells you about that magic trick: AI confidently writes wrong SQL.

It will occasionally get the join backwards, pull the wrong date range, or double-count rows — and it will do it with total, unshakeable confidence. If you can't read the query it produced, you can't catch the mistake. You'll present numbers in a board meeting that look plausible and are quietly, subtly wrong. That's worse than having no data at all, because nobody questions a confident-looking chart.

Knowing SQL turns AI from a risky autopilot into a co-pilot. You write the plain-English question, AI drafts the query, and you read it to verify it's actually answering what you asked. You become the verification layer. That's a skill that compounds, because it means you can move ten times faster while staying accurate — and accuracy is the entire point of doing this at all.

The restaurant analogy

If all of this still feels abstract, here's the mental model that makes SQL click for almost everyone: querying a database is like ordering food at a restaurant.

• You sit at the table. You're the analyst — you have a question and you want an answer.
• You tell the waiter what you want. The waiter is SQL — the messenger that translates your request into something the kitchen understands.
• The kitchen is the database — it holds all the ingredients (your data) and knows how to combine them.
• The plate that comes back to your table is the result — the exact answer to your question.

You never walk into the kitchen and start rummaging through the fridge. You tell the waiter, and the kitchen does the work. SQL is that waiter. You describe what you want in a precise, structured way, and the database returns exactly that — nothing more, nothing less.

This is also why the skill transfers everywhere. Every serious system you'll ever touch — your shop's sales, your website's traffic, your M-Pesa transactions, your customer list — almost certainly sits in a database you can query with SQL. Learn it once, and you can ask questions of all of them.

What this series will cover

Over the next seven posts, we'll take you from zero to genuinely useful. Here's the map:

1. Your first query — the two words (SELECT and FROM) that unlock any database.
2. Filtering the noise — the WHERE clause, so you pull out only what matters.
3. Sorting and ranking — ORDER BY and LIMIT, so your answers come back in order.
4. Counting, summing, averaging — COUNT, SUM, AVG, and friends, so you can see the big picture.
5. Combining tables — JOINs, so you can connect customers to orders to payments.
6. SQL + AI — how to use ChatGPT as a co-pilot without flying blind.
7. From reader to practitioner — the roadmap from here to confident data work.

A word before we start

Two promises before you read on.

First: no prerequisites. You don't need a computer science degree, and you don't need to be "technical." If you can write a tidy WhatsApp message or fill in a spreadsheet, you can learn this. We'll use a small, imaginary Nairobi business — think of a shop selling products, with employees, customers, and orders — and every example will be concrete and human.

Second: you'll actually do it. Reading about SQL is fine, but SQL is a doing skill. Each post ends with examples you can type into a free tool, and the final post points you to free practice sites where you can sharpen it for real. By the end, you'll be able to walk up to almost any business's data and ask it a precise question — and trust the answer.

That's a superpower in 2026. Let's go get it.