Laboratory Information Management System
Migrating from Excel-based workflows to a single
multi-user platform for laboratory management.
END USERS
SIX
- Engineers
- Test Engineers
- Managers
- Lab Managers
- Technicians
- Admins
THE TEAM
AGILE
- Product Owner
- Developers
- Stakeholders
- Project Manager
- QA Engineer
- Scrum Master
SKILLS
User research
Information Architecture
Design Systems
UI components
Wireframeing
Agile
Prototyping
Multi users interfaces
AI- Workflows
UX strategy and Audits
TECK STACK
Figma
FigJam
Figma AI
Miro
Notion
Notebook LM
Claude
Azure
Copilot
Lyssna
Microsoft Azure
THE PROBLEM
MIGRATE THE WORKFLOW
From heavy Excel sheets system, into an ALL IN ONE platform.
UNDEFINED PROCESS AND GOVERNANCE
Multiple users working slowed down the workflow.
COGNITIVE OVERLOAD
Users were adopting bad practices in their process, caused data and performance errors.
MISCOMMUNICATION
Unclear communication channels caused exhaustion and flow bottleneck.
THE MAIN CONSTRAINTS
DATABASE TECHNOLOGY
Data storage was limited to local directories and hard drives for security reasons.
DOCUMENTATION GAP
Task completion friction, onboarding comprehension, follow up implementations and governance.
MY APROACH TO THE SOLUTION
Interview, architect, design, test, repeat… then build for development
USER RESEARCH
35 USERS
I interviewed:
- Managers
- Engineers
- Lab technicians
UX AUDITS
- Performance
- Accessibility
- Efficiency
- User Satisfaction
BEFORE USER TESTING
NEXT STEPS
Weekly feedback meetings with users to keep improving.
BUILDING FOR IMPROVEMENT
User Personas
Capability Map
User Journeys
Laboratory Life Cycle
A/B Testing
Empathy Map
Mental Models
Governance definition
PROCESS AND RESULT
Dashboard Personalization
Problem: A generic home dashboard for all users. Low interaction and engagement.
UX Solution: Personalized User dashboard with latest notifications, processes timeline and approval tracking.
Reduced Cognitive load on heavy data tables
Problem: Excel sheets where overwhelming to fill and search data.
UX Solution: Multi parameters dropdown and select to reduce cognitive load.
Downloadable Test Request Documentation
Problem: Offline visualization and downloadable Test Request results.
UX Solution: User has the option to
CONCLUSION
What I learned
Communication: Improve communication with the development team and stakeholders.
UX Audits: Running multiple audits every quarter helped to gain the skills to run audits and sharpen my eye for accessibility and criteria.
UX Direction: Create a timeline of deliverables as we discovered new features that users needed. Act as doorkeeper and prioritize features for the project that would impact directly on how users use the tool.
What I would do different
Different Approach: When I joined the team the project was fairly new. We didnt have enought information to build such robust system. So I would dedicate more time to research deeply from early stages.
More documentation: I would advocate for deeper and detailed documentation from the begining, even when the team started iteration. Later in the project we found out, that our earlier findings and users reasoning where missing, because. The more documentation, better understanding.
