Service design · No code / low code
Sketch the workflow before anyone builds software
Make an idea visible with a paper sketch or simple mock-up, then see whether it fits the real work.
What you’ll have at the end
A tested workflow sketch and a clearer decision about what, if anything, needs building.
How to begin
- Describe the job to be done, who needs to do it and what happens today. Include the exceptions staff have to handle, not only the ideal route.
- Sketch the proposed steps on paper or a whiteboard. Mark who sees each piece of information, who acts next and what happens when the information is missing.
- Walk through the sketch with the people who do the work and with patients or representatives who use the service. Ask them to show where it would not fit.
- Revise the sketch and test it with fictional examples. Keep data, systems and clinical decisions out of an unapproved prototype.
- Write down what you learned, what remains uncertain and who would need to approve a real build. Stop if the simplest answer is a clearer process or instruction.
What to measure
- Outcome: did the sketch expose a workable next step or a problem with the original idea?
- Process: did the right patients and staff get a chance to review it?
- Balancing: would the proposed step add work, hide an exception or make another route harder to use?
Before using real data
A mock-up is for discussion, not clinical use. Do not enter real patient information into consumer prototyping tools or use an unapproved prototype to make care decisions.
Agree scope, data handling, supervision and escalation with your practice. Use approved systems. Do not upload patient information to this website or a public AI tool.