Complex systems break in the gaps between policy, operations, and technology.
Organizations know something’s wrong. Nobody can find where.
Three layers. Three owners. The gaps between them are where your problems live.
Every broken system has the same structure: what the rules say, what people actually do, and what the software allows. These three layers drift apart over time. The drift is invisible until someone maps it.
Working software in days, not strategy decks in months.
01 — Map the three layers.Contract/policy requirements. Operational practice. System behavior. Document each, find the gaps. This is where most of your failures live.
02 — Build with the people who do the work.Sequential 1:1 sessions with your operations staff. Each person refines what the last one validated. Working prototypes, not wireframes. By Friday, your team has shaped the tool they’ve been requesting for years.
03 — Validate with the people who use it.Real users, real tasks, real evidence. Exact quotes, attributed, with confidence levels. Not “we think this works” — proof that it does.
04 — Document everything that matters.Every design decision traces to a person, a quote, and a result. When someone later asks “why do we do that?” — there’s an answer. When someone requests “simplification” — you see what breaks.
Regulated, high-stakes domains where eligibility meets human needs.
Problems where the forms look simple but the rules underneath are not.
- Government benefits and fee assistance
- Federal program administration
- Healthcare eligibility and access
- Permit and licensing systems
- Any system where ops built shadow tools to survive
Federal program modernization.
Replaced a legacy application system serving military families. Complete first-attempt submissions were so rare that coordinators had a name for one: a unicorn.
Results
- First-attempt completion: from a rounding error to the norm
- Processing turnaround: from weeks to days
- A chronic resubmission problem everyone had learned to live with: root cause found and named, with evidence
Not a consultancy. Not a software vendor.
I build in days, not quarters.Working software in hours, not months. Validated with real users before anyone writes a requirements document.
The evidence holds up.Every finding traces to a person, a quote, and a decision. Not a strategy deck — an evidence trail that survives scrutiny.
The work survives after I leave.Decision rationale, design logic, evidence trails. When I leave, the institutional knowledge doesn’t leave with me.
Your system is broken in a specific, findable way.
I’ll find it. And when I’m gone, you’ll still know why.