Unthought.

Data & Analytics

Pipelines, reporting surfaces, and the question of which number is the real one.

Almost every business that asks for a dashboard already has several. The problem is rarely that the numbers are missing; it is that three systems each report a version of the same figure and nobody can say which is authoritative or how it was derived. The first deliverable is usually not a chart but a written definition.

The work covers data pipelines, synchronization between systems of record, warehousing where it is warranted, reporting surfaces, and measurement and attribution for anything that spends money to acquire customers.

Every metric carries its derivation. A figure on a dashboard is accompanied by what it counts, what it excludes, which system it came from, and when it was last refreshed. This is not documentation added afterwards — it is a required field, so a metric whose derivation nobody can state cannot be added to the surface at all. The failure this prevents is specific and common: two people reading the same dashboard, meaning different things by the same word, and discovering it in a meeting six months later.

Data is pulled from systems of record rather than re-keyed. Where a figure exists in a billing platform, a scheduling system, or a CRM, the pipeline reads it there. Anything stated twice will eventually disagree, and the version a human retyped is always the one that is wrong.

Freshness is displayed, not assumed. Every reporting surface shows when its data last synchronized, and a stale surface says so on its face instead of presenting old numbers as current. A dashboard that silently stops updating is worse than a dashboard that is down, because the first one is still being trusted.

Attribution work is approached with more caution than the field usually applies. Multi-touch attribution models produce confident numbers from ambiguous evidence, and the confidence is the dangerous part. We prefer to instrument what can be observed directly — a form submission, a booked call, a completed checkout — and to be explicit about where inference begins and observation ends.

Reporting is built to answer decisions instead of to display everything available. A surface with forty charts is a surface nobody reads. The design question is which handful of numbers would change what someone does this week, and everything else is available on request instead of on the page.

Access is scoped at the start rather than retrofitted. A reporting surface that shows everyone everything is easy to build and difficult to withdraw, and the figures a business is least comfortable circulating internally are frequently the ones with the most operational value. Deciding which roles see which numbers is a design question with an answer, and answering it late means answering it after somebody has already seen a column they should not have.

Historical data is preserved rather than overwritten. When a definition changes — when a metric starts counting something slightly different — the change is recorded and the prior series is kept, because a chart that silently rewrites its own history is worse than no chart. Anyone comparing this quarter to last quarter is entitled to know whether the two numbers were produced the same way.

Exclusions

What Data & Analytics does not take on.

  • Predictive modeling presented as certainty. Forecasts are labeled as forecasts, with their assumptions stated.
  • Attribution models that assign credit the underlying data cannot support.
  • Buying, enriching, or reselling third-party personal data.