Reframing patient rounding around the real floor workflow
A proposed parallel module would have fragmented the platform. Remapping the floor workflow kept the product within the existing system.
About
I’ve designed products across ServiceNow, Compass Healthcare Digital, and Charles Schwab, spanning enterprise platforms, healthcare operations, and financial services.
The systems I work on increasingly make calls and take actions themselves, so deciding what the system owns, what stays with people, and how the workflow holds together is the product.
My best work happens before the roadmap: turning months of competing assumptions into a direction a team can actually build from.
Case studies
Enterprise workflow problems, proven in healthcare: one prevented platform fragmentation across sites; the other replaced shared-workbook operations with role-based records, explicit permissions, and explainable exceptions.
03 / Judgment
Deciding what an AI system may do on its own, and what it has to hand back to a person, is the call I make on every product I work on. It is rarely a model question. It is a question about consequence.
Where can the system act?
Low-cost, recoverable actions can move without a person.
Where must it ask?
Consequence and permissions can make review part of the product.
What happens when it’s wrong?
Recovery, reversibility, and accountability have to be designed in.
Move the three dials to describe a decision.
How much of the mistake can be taken back.
One click undoes itTakes work to undoPermanent
What it costs when the system is confidently wrong.
A minor annoyanceCostly to fixReal harm
How far the consequence travels past the person who triggered it.
Only the person actingTheir whole teamEveryone downstream
Recommended operating mode
Easy to take back and costly to get wrong, while the impact stays with the person acting. The system can prepare the action, but a person makes the commitment.
From the dials
My call: let it prepare the move, but the yes stays with a person. Ask me why, or move a dial and I may change my mind.
04 / Experiments
Where I test these decisions in code, interfaces, and policy. These are unfinished on purpose: each one exists to answer a question I could not answer by reading about it.
Compare notes
System acts
Where errors are bounded and recoverable.
Pauses for approval
Where a person sees the evidence before the system commits.
Hands control back
With a clear record of what changed, what triggered it, and why.
Send a note. I reply within two business days.