By Dropalo Editorial
Every service is performed somewhere.
Draw any public or personal service on a whiteboard and it looks the same wherever it runs: a request comes in, a check happens, a decision is made, something is handed over. Boxes and arrows. That diagram is useful, and it is also the part of a service that is easiest to copy from one organisation to the next.
What the diagram leaves out is the building. The steps do not float. Each one is carried out at a particular clinic, at a particular counter, in a particular queue, by people who know the room and in a room that either helps them or does not.
A process is a plan, a place is where it happens
Think about the three settings in the title. A clinic is a set of rooms with a sequence of thresholds. A counter is a point where one person’s need meets another person’s attention, usually with others close by. A queue is a line with a front, a back and a direction, and it only works if everyone can read it.
Each of these is described on paper as a stage in a flow. Each is, in practice, a physical arrangement: which corridor leads to which door, where the line forms when it is busy, what can be seen from the chair you were asked to take, which end of the counter is quieter. Change the arrangement and the same process produces a different experience, even when every box on the diagram is untouched.
This is why two places that follow the same procedure can feel so unlike each other. The procedure was never the whole service. The service is the procedure performed in a place.
Why the place gets overlooked
Processes are easy to write down, count and compare. They fit in a document, they can be audited, and they can be moved to a new location with a training session. Place knowledge is harder to hold. It sits in the heads of the people who work there, in the habits of the regulars, in small adjustments nobody ever wrote up: use the side entrance after four, the lift is slow, the person on the left will know.
So when services are redesigned, the process tends to be what gets redesigned. The room is assumed. Then something goes wrong at a counter or in a corridor and the cause is described as a failure of the process, when it was really a failure to account for where the process was happening.
What gets copied and what does not
Booking tools, status messages, forms and routing rules will keep improving, and they will be adopted widely because they work the same in many places. That is the nature of a process layer. It travels well, and so it commoditises.
The layer that does not travel is the specific one: what this room is like, where this queue actually forms, how this counter receives people on a weekday morning. It has to be known place by place, and keeping it current is slow, local work.
The direction, stated plainly
Dropalo is a digital company, working towards digitising physical places. For services, that points to a digital layer able to carry what a clinic, a counter or a queue is really like, so the service and its place are understood together. That is an ambition, not a launch, and how it would work is deliberately left out of this piece.
Nothing here is advice about using or reaching any health, care, legal or public service. It is a view on places.
The process will look the same in a thousand locations. The service will not, because it is performed somewhere, and the somewhere is part of what is delivered.