Why decisions go unmeasured, what a semantic layer actually does, why hiding a column is not access control, and when you should not buy from us. Filter by the problem you came in with.
Twenty-five pieces. Pick the one that sounds like your business.
Every reporting tool takes you to a number and stops. The gap after that is where the value went.
Governance and AI readinessA policy in a document is a hope. A policy in the query path is a guarantee.
BI cost and trustOne definition of revenue, enforced everywhere, and why the alternative costs more than it looks.
Building something data-heavyOpen formats, an open catalog, and what you can still read on the day the contract ends.
Starting outFour situations where we are the wrong answer, written down so you find out now rather than later.
Governance and AI readinessThe model was never the hard part. Nobody can say what it is allowed to see, or prove it afterwards.
Governance and AI readinessNot an architecture diagram. A specific answer about a specific field, with evidence nobody drew by hand.
Governance and AI readinessA shared key tells you a query happened, not who asked or whether they were allowed to.
Governance and AI readinessMonitoring tells you after the meeting. A gate stops the load and keeps yesterday's good data in place.
Governance and AI readinessRules built around tables need rewriting every reorganisation. Rules built around the business survive one.
BI cost and trustNobody built a wrong one. Two people built reasonable ones from different definitions.
BI cost and trustOnce every reader is a line item, who gets data becomes a budget conversation.
BI cost and trustSprawl is a symptom: making a new dashboard is easier than finding the right one.
BI cost and trustMost self-serve hands people raw tables and calls it freedom. That is why it fails.
BI cost and trustCertified models work as long as everyone follows them, which is until somebody is in a hurry.
Building something data-heavyHire, then build, then ship costs quarters. And the first hire arrives with nothing to run.
Building something data-heavyIt looks like ceremony until you need to rebuild against history you did not throw away.
Building something data-heavyDifferent constraints to internal reporting: isolation, latency, and definitions you cannot quietly change.
Building something data-heavySeparate deployments isolate obviously, and cost linearly. There is a middle option.
Building something data-heavyEstimates cover the parts you can imagine. The overrun is in drift, backfills and on-call.
Starting outThe first version optimises for a quick dashboard. Those shortcuts are why it gets replaced.
Starting outEvery project has one somebody maintains by hand. Excluding it does not remove it.
Starting outNot a tool selection. Pick one argument the business keeps having, and follow the numbers behind it.
Starting outUsually framed as cost against cost. The useful frame is which risks you can carry.
Starting outBelow a certain point, a spreadsheet really is the right answer. Here is roughly where the line is.