Case Studies

Different systems. Different risks.

Each of these systems presented a different execution problem, and each required a different decision. What follows is what the work involved and what the evidence supports.

Built a clinical documentation workflow inside the consultation

Featured case

CLINICAL DOCUMENTATION

Featured caseCLINICAL DOCUMENTATION

Built a clinical documentation workflow inside the consultation

A clinical team's documentation was consuming time and interrupting the consultation itself.

Read the case
Re-engineered a system around therapist workflows
THERAPIST WORKFLOWS
SaaS / System Optimization

Re-engineered a system around therapist workflows

A mental health platform had become slow and difficult to use for the people who depended on it daily.

View Case Study
Built document intelligence for case review
DOCUMENT INTELLIGENCE
Data / Document Intelligence

Built document intelligence for case review

Review effort was spread evenly across documents regardless of which ones could change the outcome.

View Case Study

Three systems. Three different problems.

These cases are not three versions of one lesson. The constraint was different each time, and so was the decision that mattered.

1
ClaraThe clinical work was well understood. The workflow built around it was not.
2
TempusThe system was not broken. It was misaligned with how the team actually used it.
3
Upcode BusterThe data was already available. Review effort was aimed at the wrong cases.

What these share is not a pattern in the systems. It is a discipline: identifying the real constraint before committing to build.

If the next move isn’t clear yet, development isn’t where to start.

Validation is where that clarity comes from.

Start with Validation