Healthcare SaaS product design case study
Knowlab in context
A role-aware laboratory workspace designed to make operational knowledge, patient work, quality control, and oversight easier to find and act on.
The problem
Hospital laboratories run on more than test results. Staff need current SOPs, reference ranges, job aids, patient context, QC records, escalation guidance, and a clear view of what requires attention. When those sources are split across paper folders, shared drives, spreadsheets, and separate systems, the cost is not just inconvenience—it is slower work and weaker traceability.
The challenge was to bring that information into one workspace without turning the product into an overwhelming document portal or a generic analytics dashboard.
How might laboratory knowledge appear at the exact moment—and level of authority—where it is needed?
The product
Knowlab is a laboratory knowledge management and operations platform for hospital teams. It connects patient workload, result entry, SOPs, tests, job aids, training, quality-control logs, staff oversight, reporting, alerts, and an in-context AI assistant.
The workspace changes with the user’s role and active laboratory bench. That means the same system can support hands-on bench work, supervisory review, and department-wide governance without showing every person the same interface.
My role
I worked across product structure, information architecture, role-based journeys, dashboard design, workflow states, interaction design, prototyping, and the visual system. A major part of the work was deciding what each role needs to see first and how an action moves from one level of responsibility to the next.
I also defined a reusable interface language for dense operational data: quiet surfaces, strong typography, clear status chips, restrained colour, and a consistent relationship between summary cards, queues, tables, and detail views.
Users and roles
Staff
Find bench-specific SOPs, tests, job aids, training, patient work, and QC tasks without leaving the active unit context.
Supervisor
Review QC signals, monitor staff and patient work, assign SOP writing, request changes, and forward approved material.
HOD
See department health, validate SOPs, monitor workload and alerts, manage users, and review operational reports.
The operational view
The HOD command centre begins with the state of the department rather than a wall of charts. Turnaround compliance, registry queue, critical alerts, validation rate, active cases, and bench workload create a hierarchy from urgent signals to deeper operational detail.
Bench drilldowns and patient workload sit in the same view so a department-level pattern can lead directly to the people and tests behind it.
SOP governance
Knowlab treats an SOP as a controlled workflow, not just a file. Staff can be assigned writing tasks, supervisors can review drafts and request revisions, and approved work moves to HOD validation before publication.
The queue separates pending work, requested changes, approvals, and rejections. This makes ownership and document status visible while preserving a traceable route through each review stage.
Quality and reporting
QC records need both fast scanning and enough detail for review. The QC log brings run level, shift, analyst, status, date, and pending sign-off into one table, with filters for passed, warning, failed, and pending-review states.
Department reports then turn those records into a broader view of QC performance, patient workload, competency, and alerts. The design keeps targets beside current values so a status such as “Watch” has an understandable reason.
Contextual AI
The AI assistant is designed as a layer over the workspace rather than a separate destination. It inherits the active bench context and offers prompts related to QC priorities, held patient results, supervisor handovers, tests, SOPs, and laboratory workflows.
The panel also exposes confidence and configuration state. That keeps the assistant useful without presenting generated guidance as an unquestionable source of truth.
Key design decisions
Context is persistent. The active department and bench remain visible across the product, reducing the risk of acting in the wrong operational scope.
Roles change priority, not the entire language. Staff, Supervisor, and HOD workspaces use the same visual grammar while changing navigation, summaries, queues, and decision rights.
Exceptions come before averages. Critical alerts, held orders, QC warnings, pending reviews, and validation work are surfaced early because they require action.
Dense information stays calm. Large type, white space, restrained colour, and consistent table structures help a complex system remain readable during routine work.
Reflection
Knowlab reinforced that workflow clarity is an information-design problem before it is a visual-design problem. The interface feels simple because each role receives a deliberate slice of the system, the active lab context stays visible, and every summary has a route into the underlying work.
What worked
The role model, persistent bench context, actionable dashboards, governance queues, QC states, and in-context AI create one connected operating system instead of separate tools.
Next
The next phase would validate the product in live shift conditions, test handovers across roles, refine alert thresholds, and measure whether staff reach trusted SOP guidance faster.
Have a complex product that needs clarity?