BACK
BACK
The team at Smart.Helios showed me what they had learned from a professional researcher: that virtually all patients entering a hospital or clinic, brought a smartphone with them (which was not really a surprise).
And that virtually all patients start by asking the staff virtually the same questions.
My task was to explore ways of helping the patients with answers, and the staff by alleviating the load on them.
After many sketches, and thousands of post-it notes on walls, I knew where each question and answer within the "descision tree" would lead to, and what exactly would appear on which page.
That knowledge needed to be made available to all.
And that is best communicated by visualizing the user flow.
This is a small section of the digitalized flow that I made.
A user flow like this shows how patients are welcomed by the application, how they "move" through it, what they see, how they respond, and sets up a blueprint for the application.
At this relatively early stage, where I had pressed on with a clickable prototype for testing purposes, we had our proof of concept.
The next stage would normally be fine concept... exploring those lovely little UI details that help make an application special, and nitty-gritty discussions with developers (front-end, back-end, DevOps etc.).
Unfortunately, the setup at Smart.Helios at the time was incomplete, and there were no engineers... we decided to wait with any further work until the team was on board.
I prepared everything for a hand-over to the product manager, and moved on.
Lean UX & iterative design
Data-driven
Evidence-based
Build - measure - learn
Husband to a lovely wife
Dad of two brilliant girls
Fan of two-wheeled transport