Why data modelling matters more than it looks

The gap between knowing this and actually doing it is where most teams lose ground. Data modelling is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

Numbers get quoted in meetings long after anyone remembers how they were calculated. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

What is actually at stake

The model outlives the application built on top of it. Getting it slightly wrong is survivable. Ignoring it entirely is not. If two people in the business would answer this differently, that gap is the actual problem.

Name things the way the business names them. This is the sort of thing that compounds, quietly, in both directions. Assume whoever inherits this will have half your context and none of your patience.

What to watch for

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.

The short version

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
• Name things the way the business names them — 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.