One number, two histories
When two systems disagree about a shared metric, the consolidation starts with its definition.
- Architecture
- Governance
- Stakeholder alignment

Anil Thapa
Data & AI Platform Leader
Ask what the data platform cost last quarter and someone has the number. Ask what it changed and you get a list of dashboards. I have built platforms that gave that answer and led teams that had to do better, and the distance between the two answers is the subject of everything here. Every case study starts from a decision that was going to be made with or without the data, says what the platform had to get right for the evidence to arrive in time, and names what that cost. The essays carry the same question into the team: who owns a definition, what a recommendation has to carry before anyone acts on it, and how judgment is handed to the next person. Two short exercises give you the choice first and the cost after.
A platform is a cost until it changes a decisionanda career in data grows the same way.
For anyone paying for a data platform, or building a career on one.
The platform
Reliable numbers can still leave every decision unchanged.
The people and decisions around it
A persuasive recommendation can still rest on the wrong number.
What someone needs to decide determines which definitions, reliability, and cost the platform must support. What the platform can establish determines which recommendations are defensible.
The interface may be a dashboard, a briefing, or an AI assistant. The definition, the evidence, and the accountability still have to hold.
The organization needs evidence that informs the choice before it is settled. The data professional earns trust by making the recommendation and its tradeoffs clear.
Two exercises
Every case study here names the decision the work changed and what the choice cost. These two hand you the choice first.
Compare the twoEach subject crosses both halves. None of them is only about the platform, and none is only about the career.
When two systems disagree about a shared metric, the consolidation starts with its definition.
When analysis arrives after the decision, the work starts with being in the room while the options are still open.
When judgment stays with one person, hand someone a bounded decision and review their reasoning.
When an assistant answers from the platform, launch it narrower than feels reasonable and let the unanswered questions set the roadmap.
How to decide whether an AI data assistant should be widened, narrowed or retired: four numbers against the queue it replaced, and what retirement keeps.
When AI drafts the pipelines and models, review becomes the constraint: what changes in the queue, what a reviewer checks, and what it costs a data team.
Hiring for judgment in data: an interview built around one bounded decision, what to listen for, how to score it, and what the format costs.
The evidence of judgment in a data career is a record of decisions, not deliverables: four columns to keep, how to read them, and what the log costs.
For a talk, a podcast, or a different view on something written here, the writing is where to start. The contact page says what an invitation should include.