Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Make the next step clear for each healthcare website audience.
We map the public-site journeys for the agreed audiences, then prototype their screens and interactions. A commercial enquiry, resource request and application sign-in are treated as different tasks with different information needs.
A few clients we’ve worked with
What we do
UX/UI design for healthcare teams: journey definition, interaction design, review and handoff.
Decisions that shape the scope.
What is the visitor trying to decide before taking action?
Which actions belong on the public site versus an authenticated application?
What interface decisions cost when nobody makes them.
Interfaces are not decorated; they are decided. When the tasks, roles and states are never agreed, they get invented during development — one screen at a time.
Development stops guessing
An agreed screen inventory and behaviour means engineers implement decisions instead of making product decisions in code review.
The product survives its next feature
Patterns designed once hold when the roadmap adds a role, a plan tier or a new workflow.
UX/UI design: scope.
These work areas are scoped against the organisation’s existing site, approved information and available technical access.
Journey definition
Document entry points, audience questions and the intended destination. Keep public enquiry journeys separate from authenticated clinical workflows.
Interaction design
Specify navigation, filters, forms and their error or empty states. Include long product labels and mobile use in the prototype.
Review and handoff
Walk through the scenarios with the organisation’s content and operational owners. Record approved behaviour and unresolved integration requirements.
Selected healthcare and life-science website projects
All case studies
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“I was impressed by Norml Studio's good communication and efficiency.”
“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
What you receive.
The brief identifies which outputs are required and who reviews them.
- 01
An audience journey map.
- 02
Wireframes and a clickable prototype.
- 03
UI states and implementation acceptance notes.
Our process
How the work runs.
Map tasks
Describe the entry point and next step for each audience.
[ 01 ]
Prototype interactions
Build navigation, forms and error states with test inputs.
[ 02 ]
Review the journeys
Walk through success and failure scenarios with the operational owners.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedUX/UI design for healthcare: questions.
Does this include designing a clinical application?
A clinical application needs its own users, risks and requirements. This page’s default scope is the public website and agreed non-clinical journeys.
Does the work include testing with external participants?
Participant testing can be scoped with suitable recruitment and consent. An internal walkthrough is reported as a different activity.
Website 2.0 combines strategy, design, development and launch in one engagement.