The work changed.Your metrics didn't.
HX — the Human Experience framework — is the successor to DORA, SPACE, and DX Core 4, built for organizations where humans and AI agents ship together. Four questions, one covenant, and a new primary source: the work's own record.
Past frameworks used what they could
DORA read pipelines. SPACE added surveys. DX Core 4 unified them. All three came before the biggest change in how software gets built — and none of them can see it.
“Is our software delivery healthy?”
The four keys, read from pipeline telemetry — and proof that speed and stability travel together.
“What is developer productivity, really?”
Five dimensions, and permission to treat how work feels as data.
“Can this be one deployable standard?”
DORA, SPACE, and DevEx unified into a benchmarkable four.
“How is work with AI actually going?”
Reads the work's own record — the sessions — with the author in control of sharing.
Your engineers produce two codebases. You keep one.
Alongside the code, every engineer now produces a second body of work: their sessions with AI agents — the requirements clarified, the alternatives weighed, the reasoning that became the code. It is work product, created in your repositories, for your product. And today it mostly lives in local folders on personal laptops.
Source code has been treated as intellectual property since the day it was worth paying for. The reasoning that produces it deserves the same custody — and it is the richest record your organization has ever had of how it actually works.
Measure where work happens
For a decade, “how we work” was analyzed in one system while the work happened in another. Insight traveled by export and quarterly deck — and mostly didn't survive the trip.
Findings crossed systems by integration and slideware. Action was always a meeting away, and the context was gone by the time anyone acted.
When the platform that runs the work also reads it, findings return to the next working session while the context is still warm.
That loop compounds. Two organizations adopt AI in the same quarter; one reads its own record, one leaves it on laptops. A year on, the difference between them isn't talent or headcount. It's that one of them got a little better every week — and the other planned to.
Kept by the organization. Shared only by you.
The organization stores and protects the record, the way it stores code. Reading it is a separate matter: a raw session opens to its author, and reaches a team only when the author shares it — under safeguards everyone can see.
The record
Kept by the organization — preserved, backed up, never lost to a laptop or network failure.
Reading
A raw session opens to its author. Sharing it further is the author's decision.
Team views
Numbers above the individual describe teams. The only person who sees a number about you is you.
Answers
Raise a problem and something visible comes back — a change, a decision, or a clear no with the reason.
Four numbers your dashboards don't have
Keep your DORA keys and your productivity benchmarks — they read delivery well. These four read the work itself, and every one of them is computable from the session record.
Landing
did the work land?The share of AI-assisted work that ships — sessions traced to merged, published outcomes.
Gthe Gap
structural minus feltWhat the record implies about how work is going, minus what people report. Divergence is the alarm.
TTime-to-receipt
does listening come back?Median time from a raised problem to a visible outcome: a change, a decision, or a clear no.
MMomentum
are we getting better?The trend of the other three across windows — whether the team is measurably improving with AI.
See where you stand.
Five minutes, sixteen statements, and a reading you can send straight to your leadership. Then read the covenant your people would want you to sign.