You do not need SQL: data-driven management for non-technical people
For twenty years, querying data was a technical skill. It stopped being one. What replaced it, and why that changes the manager’s job more than the analyst’s.
For a long time there was a mandatory translator between the doubt and the data: someone who could write the query. That created a queue and, worse, a silent censorship — the small question never entered the queue because it was not worth bothering anyone.
The translator is gone. What replaced it is not technical knowledge: it is the ability to ask precisely and to distrust the answer.
What the skill became
| Before | Now |
|---|---|
| Knowing query syntax | Knowing how to define period, scope and criteria |
| Knowing table names | Being able to describe the fact in plain language |
| Trusting the analyst | Checking the working that came with it |
| Requesting and waiting | Asking and refining on the spot |
Not one line in the right column is technical. All of them are business knowledge — which is why managers usually extract more value from this than analysts, who already had the path open.
The three things you have to be able to say
- 01The period. "Last 7 days" is a different answer from "this month" and from "same period last year".
- 02What counts. Do approved sales include later refunds? Do renewals count? Which currency? Those choices are yours, not the tool.
- 03What to compare against. A number without a comparison informs nothing, and the comparison is always a business choice.
Anyone who can state those three can pull almost everything a standard report would give — and more, because they are not limited to what someone programmed in advance.
What still requires technical people
- Connecting and keeping sources alive. It is the invisible work everything else rests on.
- Deciding how different systems represent the same person. Identity resolution is engineering, not a question.
- Making sure incoming data is correct. No good question fixes bad ingestion.
- Defining permissions and access scope. Who sees what is a risk decision, not a convenience one.
Technical work did not end — it moved. It left the answer and went into the foundation. That is what freed the answer for whoever has the question.
The first exercise
Take a number you already know by heart and ask the connected assistant for it. Compare. If it matches, ask the second question — the one you never asked because it would create work for someone. That second question is where the value is, and it exists in every company.