Data modelling, explained without the jargon

There is no clever trick in this one, just a handful of decisions worth making deliberately. Here is data modelling without the vocabulary that usually surrounds it.

Numbers get quoted in meetings long after anyone remembers how they were calculated. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

The short version

The model outlives the application built on top of it. The teams that handle this well are rarely the ones with the biggest budgets. Doing this properly once is usually cheaper than doing it approximately three times.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. Small and consistent beats large and occasional here.

Name things the way the business names them. None of that requires a large budget, only a decision and someone to own it. If it only works because one person remembers to do something, it does not work yet.

Where to go from here

Model what is true, not what is convenient this quarter. This is the sort of thing that compounds, quietly, in both directions. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

In practice

Most data problems are ownership problems that turned into technical ones. Three things worth confirming about data modelling before you move on:

• Someone can say what the current setup is without going to look
• The model outlives the application built on top of it — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.