Design
Software people don’t dread
Software people avoid is software people work around, and the workarounds end up in the chart.
The gap between the demo and the front desk
Clinical software is usually chosen by people who will not use it forty times a day. It is evaluated in a conference room, on a good laptop, by someone with an hour to spare and no patient waiting.
Then it lands. The person at the front desk has ninety seconds and a phone ringing. The clinician has a note to finish before the next room. Whatever was charming in the demo is now just friction, repeated.
Friction has a predictable shape. Notes get deferred to the evening, then to the weekend. Fields get filled with whatever passes validation. Someone starts a spreadsheet. None of that is laziness. It is what people do when a tool fights them.
Why this is clinical, not cosmetic
A note written six hours late is a different note. Details soften. The thing you meant to flag becomes the thing you meant to remember to flag.
Data entered under duress is data someone else will later trust. A workaround that lives outside the system is information the next clinician cannot see. The interface is not decoration sitting on top of the care pathway. For long stretches of the day, it is the care pathway.
What we built instead
LogBlues follows one rule above all the others: if a control is visible, it works. No dead buttons. No cheerful confirmation of something that never happened. When the software cannot do a thing, it says so plainly rather than dressing the failure up as success.
That rule holds in the demo too. The patients are invented; the behavior is real. What you click in the demo is what you get.
Beyond that, we took the position that a workspace can feel alive rather than clinical-industrial. Screens grow vines between related items. Graphs are drawn as growing things. The visual language borrows from plants instead of dashboards, which sounds like a small decision and does not feel like one after a few hours.
Blues, the assistant, has moods and a personality you can dial from Professional to Expressive. It tells you what it is doing while it thinks, so you are not staring at a spinner wondering whether anything is happening.
Your day, your layout
Practices do not run on one rhythm, so the workspace bends:
- Drag dashboard cards into the order your day actually runs in.
- Edit the sidebar so the hourly things sit at the top and the monthly things do not.
- Choose from a collection of themes.
- Put your own logo on patient-facing forms.
Accessibility is settings, not a promise: text size, contrast, reduced motion, keyboard support. The small mechanics are handled too. Everything clickable shows a pointer cursor. Dialogs behave the same way every time. The layout is built for a 360-pixel phone as seriously as for a desktop, because someone on your team is checking a schedule from a car.
The thesis, stated plainly
We are not claiming software fixes anything about how the work feels at scale. That would be a large claim and we do not have it to make.
The smaller claim is one you can test in an afternoon. People use the tools they do not dread. A clinician who does not dread the software is a clinician whose notes actually get written, on the day they happened, by the person who was in the room.
That is the whole argument. Everything else is implementation.