The journey board
Lead, intake, scheduling, visit, payment - one pipeline, advanced by the systems that already know what happened, so staff attend to what needs a person.
Ask a practice where a given patient is in the process and you will usually get an accurate answer assembled from three places: someone checks the EMR, someone else checks the inbox, and a third person remembers a phone call.
The answer is right. Producing it is the problem.
One pipeline, end to end
A journey board puts the whole relationship on a single pipeline: lead, intake, scheduling, visit, payment. Not five systems reporting five partial truths, but one board where a card moves from the first enquiry to the settled invoice.
The stages are the practice’s own. We do not ask a clinic to adopt our vocabulary for its intake process - the board is configuration, not custom code, and it is built to describe how this practice actually works.
The board advances itself
Here is the part that decides whether a board survives contact with a busy week.
Boards that require a human to drag cards are accurate exactly as long as someone has time to maintain them, which is to say: accurate until the day you most need them. So on a journey board, the EMR’s own events advance the cards. An appointment is booked, so the card moves. A payment settles, so the card moves. The board reflects what the systems already know rather than what someone remembered to record.
Where judgment matters, a person still moves the card by hand. The distinction is deliberate: automation advances what the systems can observe, and people advance what requires a decision.
What staff actually see
The point of this is not the board. It is what the board removes.
When the mechanical stages advance themselves, the items left visible are the ones that need attention: the intake that stalled, the follow-up nobody claimed, the payment that did not settle. Staff stop scanning for exceptions and start working them.
That is the same principle running through everything we build. The machine handles what a good back office repeats. People handle what a good back office judges. A journey board is just that principle applied to the shape of a patient relationship.
It is not a reporting layer
A board like this is sometimes mistaken for a dashboard - a place to look at work rather than a place to do it.
It is the opposite. The board is where the work is worked. Reporting falls out of it as a by-product: because every stage transition is a real event on a real record, the daily digest reads the operation without anyone assembling a status update. The measurement is free precisely because the board is not a summary of the work. It is the work.