The Hidden Cost of Over-Modeled Analytics
Clean schemas are useful. But when modeling matters more than the user's job, analytics becomes expensive theater.
There is a point in many data teams where modeling stops serving the business and starts serving the model.
You can feel it. Every new question requires a new dimension. Every answer waits on a refactor. The semantic layer is beautiful, and the business is starving.
When aggregation breaks trust
Over-modeling usually hides behind good intentions: consistency, reusability, a single source of truth. But each layer of abstraction is also a layer between the user and the raw fact. When users cannot reconcile a number to something they recognize, they stop trusting it — no matter how elegant the lineage.
Star schemas are not a religion. They are a tradeoff you should be able to defend out loud.
Modeling for meaning vs. modeling for performance
These are different goals and they pull in different directions. Conflating them produces models that are fast and meaningless, or meaningful and unusable. Name which one you are optimizing for, per use case, and accept that the answer changes.
A cheaper path
Model the things that are stable and shared. Leave room for the messy, specific, fast-moving questions to be answered closer to the source. Not everything needs to graduate into the warehouse's permanent vocabulary.
Related essays
If Security Depends on Who Built the Dashboard, You Do Not Have a Security Model
Analytics security often starts with a reasonable shortcut. Restrict a folder, add a filter, configure a workbook, and ship. The problem appears later, when the same rules have to survive new dashboards, new users, new teams, and people who were not there when the original decisions were made.
A Metric Is Not Defined Until the Exceptions Are
Teams can agree on a metric in five minutes and spend months discovering what they actually agreed to. The formula is usually the easy part. Timing, incomplete work, corrections, customer configuration, missing data, and competing definitions are where a metric becomes real.
The Fastest Way to Ship Technical Debt Is to Call It a Shortcut
Most technical debt is not created by poor engineering. It is created by reasonable decisions made under delivery pressure that are never revisited. The shortcut is rarely the problem. Treating it as the new architecture is.