The real cost of ignoring data modelling
The advice here is unglamorous, which is probably why it gets skipped. Nobody bills you for neglecting data modelling. The cost shows up somewhere else.
Data outlives the applications built on top of it, which is why the model deserves more thought than the screens. It rarely shows up as a line item, which is exactly why it slips.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- The model outlives the application built on top of it
- Rework, once the problem is finally visible
Name things the way the business names them. Getting it slightly wrong is survivable. Ignoring it entirely is not. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.
Making it stick
Model what is true, not what is convenient this quarter. Small and consistent beats large and occasional here. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
What this looks like day to day
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
- Model what is true, not what is convenient this quarter — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Most of the value here comes from doing the first two things, not all of them.