How we work
You shipped it.
They went back to the spreadsheet.
Most enterprise products fail in production, not in design.
The reasons are almost never what the team thinks.
Three phases. One measure: adoption in the real world.
200+
Enterprise products built
11% → 68%
Physician adoption · CDSS
78 → 8 min
Per case · Agentic EMR
4 months
vs. 18 typical
The premise
"There's a version of your product that works beautifully in demos. Then there's the version that has to survive a 14-hour shift, a skeptical supervisor, and an IT department that didn't buy in."
Most UX frameworks design for the first version. We build for the second. After 200+ enterprise products, the pattern is consistent: sticky notes on monitors, printed checklists taped next to screens, shadow spreadsheets quietly replacing million-dollar tools. Nobody announces this is happening. It just does, while the design team is congratulating itself on a successful launch.
The way we work came from a simple observation: the things that kill adoption in enterprise aren't primarily design problems. They're organizational reality problems. Politics. Accountability requirements. Stress conditions. Workarounds that became workflows. Teams defending decisions they made two years ago.
The core distinction: Intuitive isn't the standard in regulated, high-stakes enterprise environments. Defensible is. Users need interfaces they can explain to a supervisor, an audit, a medical review board, not just interfaces that feel easy in testing.
32°N · Proprietary Methodology
200+ products built on this method
WHAT TEAMS FEEL
"Users aren't adopting." The brief that reflects stakeholder consensus, not ground truth. The problem as imagined.
WHAT WE SURFACE
The real problem named. Org dysfunction mapped. Workarounds documented. "Success" redefined for production conditions.
WHAT BRIEFS ASK FOR
Intuitive interfaces. Ideal users. Demo-polished. Stakeholder-approved. Optimised for the room, not the ward.
WHAT WE BUILD FOR
Tired users. High stakes. Accountability chains. Interfaces people can explain to a supervisor, an audit, a review board.
WHAT TEAMS CALL SUCCESS
Satisfaction surveys. Controlled test rates. Launch-day numbers. Training sign-offs. Metrics from the room.
WHAT WE MEASURE
Production adoption. Workflow integration. Before/after in business terms. The gap between demo and reality, closed.
WHAT GETS SIGNED OFF
Pilot success. Rollout playbooks. Vendor sign-offs. The optimistic story that travels up to leadership.
WHAT WE HARDEN
Admissibility architecture. Boundary cases. Drift detection. The 3am edges that decide whether the system stays trusted.
01
Surface
Surface
Find the real problem
What looks unique to you is a pattern we've solved before. We've watched the same product fail at 8 different companies. Same interface, same user type, same stated problem, same outcome. Surface is fast because it isn't research. It's recognition.
- →Failure pattern identification
- →Organizational reality mapping
- →Stated vs. real problem gap
- →Dysfunction as design input
- →Production success definition
In practice
6 weeks
to surface the real compliance problem
340B Compliance Intelligence02
Architect
Architect
Design for production
Enterprise users don't just need interfaces they can use. They need interfaces they can explain, to a supervisor, an audit, a review board. We don't say "fix your dysfunction and then we'll design." We design through it. The dysfunction is the environment.
- →Trust architecture design
- →Defensible interaction patterns
- →Production condition simulation
- →AI reasoning transparency
- →Navigation through organizational dysfunction
In practice
11% → 68%
physician adoption in 4 months
Clinical Decision Support03
Prove
Prove
Adoption is delivery
If they need a training programme, the interface isn't done. When enterprise products require extensive onboarding, the product is compensating for something the interface should be handling. Prove closes the gap between demo performance and production reality.
- →Production adoption tracking
- →Before / after documentation
- →Training-as-UX-failure audit
- →Workflow integration mapping
- →Business outcome reporting
In practice
78 → 8 min
per clinical case
The Agentic EMR Experiment04
Govern
Govern
Design for the edges
Adoption gets you live. Governance keeps you live. Once a system is in production, the failures shift from usability to admissibility. What evidence does the interface produce? What boundaries does it enforce when a user, or a model, drifts? Govern is the layer most teams discover only after their first audit, lawsuit, or quiet rollback. We design it in.
- →Admissibility architecture
- →Boundary hardening
- →Drift detection
- →Pre-deployment audit
In practice
0 rollbacks
across regulated deployments
340B Compliance IntelligenceWhy this is different
What we do differently.
Most UX frameworks
How we work
Solves design problems.
Solves adoption problems.
Designs for ideal users in controlled environments.
Designs for real users under stress, pressure, and accountability.
Treats organizational dysfunction as something to fix before design starts.
Treats organizational dysfunction as a design input. We build through it, not after it's resolved.
Hands off governance and admissibility to a post-launch compliance review.
Builds governance and admissibility into the brief, before launch.
We didn't build this in a workshop. We built it across 200+ products, in environments that ranged from functional to deeply dysfunctional.
The ecosystem
Three practices, one brief.
Design lives with us. Development lives with a specialist partner. Governance lives with another. Three practices, one brief, no vendor tax.
We sustain depth across your full product surface without staffing a 30-person studio.
How we workThe method in practice
Clinical Decision Support System
11% → 68% physician adoption
A $2M AI diagnostic tool gathering dust. 89% of physicians ignoring it entirely.
The Agentic EMR Experiment
78 → 8 min per case
Clinical documentation consuming 40% of physician time. Voice-first AI prototype.
340B Compliance Intelligence
6-week discovery sprint
Manual compliance processes creating audit risk across 340B programs.
Go deeper
We write about the same patterns we solve: adoption failures, AI trust gaps, production realities. Two newsletter series, 9 editions, same throughline.
Every engagement runs this way.
If you're building complex enterprise software and adoption is the metric that matters, let's talk.