I turn complexity into actionable intelligence.

Founder & Principal Architect at Model Citizen. I work at the seam between raw, messy data and the decisions it's supposed to drive — building the systems that turn analysis into infrastructure teams can rely on. This page is the short version of how I think, how I work, what I think matters, and what that looks like in practice.

Adam Young, Principal Architect

Big data is like teenage sex: everyone talks about it, nobody really knows how to do it, everyone thinks everyone else is doing it, so everyone claims they are doing it.

Dan Ariely
Adam Young
Founder & Principal Architect
How I think

The data is usually fine. It's a translation problem.

The raw material is almost always there — a tangle of events, logs, transactions, a decade of accumulated systems, no different from raw ore before anyone's refined or shaped it. What's missing is the throughline from that tangle to a decision someone can defend on Monday morning. My work is to empower leaders to go into those calls with confidence and clarity.

Data Sourcesraw · inconsistent
The Data Modelthe semantic spine
Data Surfacesevery surface, one model

Define it once. Trust it everywhere.

How I work

Six principles I bring to every engagement

Six principles I work by

  1. Outcomes over outputs

    Start from the decision, not the dataset.

    A dashboard nobody acts on is decoration. I start from the decision that needs to get better and work backwards to the data — not the other way around.

  2. Trust is the real deliverable

    A number only counts if someone will defend it.

    A number people believe beats a clever model they quietly ignore. Most of the work is making metrics legible, reconciled, and owned — so they survive scrutiny in the room where it counts.

  3. Operationalize, don't just analyze

    An insight in a notebook is a hobby.

    Value shows up when the work runs reliably without me — scheduled, monitored, and resilient to the 3am page. I build analysis into infrastructure, not one-off artifacts.

  4. Make the complex legible

    Complexity is unavoidable; confusion is a choice.

    I translate fluently between the warehouse and the boardroom. The hard part is rarely the math; it's turning a tangle of systems into a story a team can act on with confidence.

  5. Build for the handoff

    If it only works while I'm in the room, I've failed.

    The best engagement leaves a team stronger than I found it — with patterns, documentation, and habits they own. I'm a conduit, not a dependency.

  6. Pragmatism ships

    The elegant system that never launches loses.

    The boring solution that ships this quarter beats the elegant one that never lands. I optimize for momentum and maintainability over novelty for its own sake.

Ideas

I write to think in public

All writing →
Outputs

Proof, not promises

Full gallery →
Decision IntelligenceGlobal Hospitality

The Data Concierge, Deployed

A governed semantic model, curated and AI-ready, standing behind every ITSM report a global hospitality enterprise runs — plus an agent that doesn't just answer a metric question, it explains why the number is what it is.

1 model, every report
Decision IntelligenceSaaS

From Ticket Queue to a Tool 200 People Open Daily

See how a semantic layer and a small set of certified metrics turned analytics from an endless request queue into self-serve — tripling weekly active dashboard use along the way.

Have data that should be doing more?

Tell me about the pipeline that breaks, the metric nobody trusts, or the analysis stuck in a notebook. Let's operationalize it.