BioViridians.
Explore a service journey before building the back office.
An interactive website and client-portal concept for a laboratory testing workflow.
Interactive prototype01 /The context
What needed
to work better.
A testing service involves more than a contact form: sample intake, identifiers, status, reports, and corrections must make sense as a connected experience.
02 /What was built
- A front-end sample-submission flow and generated demonstration sample identifiers.
- Client status views, an operations queue, and report-verification concepts.
- Responsive pages explaining the proposed testing and documentation experience.
03 /The thinking
The prototype makes the proposed journey tangible so it can be reviewed before investing in the full data and operational system.
04 /The decisions
Prototype first, back office second
Walking through the service journey as a working interface surfaces the process questions that a specification hides. Building the operational system first would have meant building it twice.
Everything in it is marked as simulated
Sample identifiers and views are labelled as such throughout. A prototype that looks like production is a prototype that gets mistaken for one, usually by the person approving it.
It ends deliberately
The scope was a front end for review, not a system. Prototypes that quietly grow into products inherit every shortcut taken while nobody intended to keep them.
05 /Where it fits
A useful method for businesses planning a customer portal, multistep intake flow, or a service with several handoffs.
Explore the service06 /Questions
Is this a live system?
No. It is an interactive front-end prototype using simulated records, built to review a proposed workflow before developing the real thing.
What happens to a prototype like this?
Ideally it is thrown away and the decisions it produced are kept. That is what it is for.
Keep exploring