Library

Notes from the decision system.

Essays, artifacts, and field notes — on decision-system architecture, measurement, and the operating teams that ship them.

Decision-system architecture is the umbrella frame for this library — composed of four disciplines: Measurement, Integration governance, AI systems, and Organizational design. Each piece sits in one of the four; the arc pill on each card names which.

Also live: Public data as a decision system — a working demo of the framework applied to federal releases, with the honest question attached to every panel: did the number actually move?

Field Note

The absorbed data role.

Data work in mission-driven organizations decomposes into three buckets — entry, interpretation, and curation/governance — and the third one, the specialized semantic-layer role, almost never has a funded home. It gets absorbed by whoever is capable with numbers: a math teacher, a clinician, a director of instructional technology. This piece names the absorption pattern across four sectors and argues for the three-layer architecture that would replace it.

Organizational design
Essay

When the stakes are the mission.

When enterprise AI gets a signal wrong, someone loses money; when mission-driven AI gets it wrong, someone loses the intervention meant to reach them. This piece names the evaluation gap opening as mission-driven organizations adopt frontier AI, proposes a five-part essential minimum, and points toward shared infrastructure that could make it sustainable at sector scale.

Measurement
Field Note

We used to settle for thumbnails.

For most of human history, every institution carried you as a thumbnail: a name, a category, a score. That compression wasn’t malice, it was budget, and the price of the full picture has now collapsed. The choice institutions face isn’t whether to keep sorting faster or to hold people at higher resolution; it is whether they can answer the validity question underneath it.

Measurement
Essay

Who writes the contract.

The contracts that govern integrated data have to be written by someone, named, inside the institution. But the hiring rubric fuses two roles — engineering and governance — into one job description and screens only for the first. The person who can actually do the work almost never scores well on the rubric written to find them.

Organizational design
Essay

Two bets, one institution.

Every institution standing up AI in 2026 is making a model-layer bet, vendor-anchored or federated, whether or not it has named it as one. For institutions running both administrative and research-flavored work, the honest answer is a deliberate hybrid calibrated by domain. What makes the hybrid coherent is a third set of contracts nobody writes by default: the seam contracts between the two bets.

Integration governance
Essay

Why the rules look weird

Most rules in a system describe normal behavior. The handful that look weird — that interrupt, that constrain, that pre-resolve a specific exploit — are the rules doing the structural work. Five sports rules, five structural lessons for institutional design.

Organizational design
Field Note

The Reach Trap

A program officer, a portfolio manager, and a CSR lead can all report reach, but none can say whether it worked or where the next dollar should go. The usual diagnosis is a reporting problem. It isn’t. It’s a category error: a system of record for activity asked to behave like a system of record for outcomes.

Measurement
Essay

The Decision System

Most “data problems” are decision-system problems. Three things fail at the faucet — meaning, authority, and validity — and detach any one from the other two and the system produces confident nonsense at speed. This is the umbrella framework that unifies the Analytic Bytes library.

Integration governance
Field Note

Functions don’t run plays.

The mismatch between horizontal work and vertical org charts is structural. Multiple honest forms can carry it: councils that deliberate and hand playbooks back to functions, flash teams that merge for the deliverable, standing squads drawn permanently from across functions. All rely on the same seam contract underneath. Without that contract, none of them holds.

Organizational design
Field Note

It’s not a communication issue. It’s a blown assignment.

Most cross-functional breakdowns get diagnosed as a communication issue and answered with another meeting. They’re a football play instead: alignment, assignment, execution. Each phase fails differently, and a communication-issue diagnosis collapses all three.

Integration governance
Field Note

Plumbing got upgraded. The water didn’t.

The data integration layer is mostly solved — the pipes have been industrialized. The work that remains is closer to running a water authority: sourcing, testing, pressure, authority, who’s allowed to drink. The unglamorous part isn’t the pipes anymore. It’s the water.

Integration governance
Essay

The contracts between systems

Integration is two questions stacked on top of each other: do the bytes move, and when they arrive, can anyone act on them. Institutions have answered the first across three eras and skipped the second, and the agentic era is about to make that gap load-bearing.

Integration governance
Essay

The numbers don’t agree because the words don’t.

Two people read different student-persistence numbers from the same data. The governance council is functioning. The framework looks complete. What's broken is definitional, and the work to fix it is the work most councils skip.

Integration governance
Field Note

The Take-Home Test

More than a dozen interview take-home tasks, done cold across a decade, read as one experiment. The same few failures showed up in almost every one — and none of them was a skills gap.

Organizational design
Essay

What is this system actually measuring?

Universities have built the scaffolding to govern AI and left out a load-bearing pillar: evaluation. The measurement-science question every adopted system should face — what is this actually measuring, and is that what we meant?

Measurement
Essay

Actions, Not Answers

Agentic AI produces actions, not answers — and the human checkpoint that came free with every answer is gone unless you design it back in. Why agentic adoption is a decision-system question, not a technology one.

AI systems
Field Note

Burden, Disparity, and the Next Dollar

Burden and disparity are two different signals in the same CDC mortality data. The priority list you build from one is not the list you build from the other — and a framework that shows both changes where the next prevention dollar goes.

Measurement
Essay

Where Should Data Sit?

Who owns data infrastructure is one of the org chart’s most muddled questions. The fix is not a better title; it is a principle — report to the integration seat, never to a single function.

Organizational design
Field Note

LO 2.0 — Stitching the Layers

Why national education data, classroom assessments, and local instruments are most useful stitched together — and what the integration architecture looks like.

Integration governance
Essay

Grounding the AI Layer

Where AI belongs in the modern data stack, and the single contract that keeps every AI feature honest.

AI systems
Field Note

When GenAI Redesigned My Dashboard

A GenAI redesign of my own dashboard came back uglier — and clearer. What that taught me about data teams and AI tools.

AI systems
Essay

Three Surfaces, One Keystone

Why BI tool selection is the last decision, not the first — and the three reporting surfaces most analytics products owe their audiences.

Organizational design