Consider this
- A website can contain the information.
- A process can follow the policy.
- A service can meet every requirement.
- A tool can operate exactly as intended.
- Yet people may still be unable to accomplish what they came to do.
The missing measure
Systems are designed. Experiences are lived.
Picture a parent who qualifies for a service, spending forty-five minutes hunting for it on the website that offers it. The information is there the whole time. They give up before they find it.
Most metrics would still call that website healthy. No complaint was filed, no error was logged. The visit looks like any other, and the one person who knows it failed has already left.
That silence is what we measure. The people who can’t get through rarely show up in the data at all.
What we do
The Human Systems Audit
We take one journey through your system, one thing people come to accomplish, for one population: the people it is meant to serve.
Then we measure whether that population can actually reach the outcome, compared against how the broader public would fare with the same task.
Not whether the system works in general. Whether it works for them.
How the measurement works
The same method, every audit.
- Start from the outcome.The thing people actually came to do, before anything the system offers.
- Define the real population.The specific people the system is meant to serve, rather than an average user who may not exist.
- Walk the path as they would.Watching for what quietly stops people: more to hold in mind than anyone can, words the system never explains, steps that assume knowledge it never teaches, time costs no one disclosed.
- Measure against a national reference.So a gap stops being a feeling and becomes a number you can act on.
- One principle governs all of it: a single severe barrier can floor the entire score. In a real journey, one wall ends the trip, no matter how good everything around it is.
What you receive
Something you can act on.
- A Human Success Score. One clear measure of whether your intended population can accomplish the intended purpose.
- A barrier analysis. Every barrier we find, named and labeled. The ones the system imposes, which you can remove, and the ones the task itself requires, which you can teach.
- Recommendations organized by that distinction. Imposed barriers go to redesign; inherent ones go to support. Your team knows not just what’s wrong, but what kind of fix each one needs.
- A re-score after the changes. The same measurement run again, so you can see the fixes actually worked.
Who this is for
Systems where the stakes belong to the person.
What sets this measurement apart is whose outcome it counts. Most analytics answer to the organization and its conversion or engagement. This answers to the person: their eligibility, their access, their deadline that doesn’t move.
- Public-facing government systems, where a person’s eligibility or access depends on getting through.
- Education, including community colleges and workforce programs, where a confusing path is the difference between a family getting through and giving up.
- Internal systems your own people are required to use, where an employee’s pay, evaluation, or standing rides on a tool they didn’t choose.
The research foundation
Built on published research.
The method rests on a documented research foundation, drawn from cognitive science, plain-language research, public administration, and usability measurement. Every claim is labeled by how strong the evidence behind it is.
We tell you what is directly supported and what is a reasonable extension. That honesty is the point.
Start the conversation
Where every audit begins.
Tell us one system, one group of people, and one thing they’re trying to do. That’s where every audit starts, and where this conversation does too.