UX Designer · In-House Contract · 80 Hours

Key Result
16 → 5 min in testing
Speed
80 Hours
Type
Intranet + Design System
Client
Al Bayader

20 interviews. One diagnosis.
I interviewed 20 employees and walked through their actual daily workflows observing where they went when they needed information and where they got stuck.
This wasn't a survey. Watching real people do real work revealed friction that no one would have thought to report in writing.
"Critical information for daily tasks was scattered across several apps, creating daily frustration that led to miscommunications and delays."
Synthesis from 20 employee interviews, and five of them timed on their start-of-day routine

Eighty hours, no wasted motion
Phase
What I Did
Why It Mattered
Discovery
Contextual interviews with 20 employees, observed real daily workflows
Identified root cause: fragmentation, not missing features
Info Arch.
Designed unified navigation consolidating all key info types
Employees can find anything from one starting point
Comms Hub
Integrated API connections to centralise updates and discussions
Eliminated need to check multiple apps for status updates
Layout
Modular, team-editable layout system
Teams update their sections without needing design or dev support
Blog / Culture
Bilingual (English/Arabic) company blog
Gave Al Bayader a digital culture layer and company voice for the first time
Design System
Complete bilingual design system for developer handoff
Ensured build matched design and could be maintained long-term
A New, Simple Intranet

Easily accessible communication hub
Easy to update layout so teams can make it work for them.

An English/Arabic Blog
Complete with a Design System

From 16 minutes to 5
"Martín's ability to balance user needs with business goals ensured that our intranet wasn't just visually appealing but also highly
functional. His work laid a strong foundation for Al Bayader's digital transformation."
Anas Yehyawi, VP of SC Procurement for Transformation, Al Bayader
→
69% Faster, In Testing
From 16 minutes to 5, timed with five employees on their start-of-day routine against the designed flows. Five people on one routine is a small sample, so I am stating it as one.
→
One Starting Point, Not Five
Updates, documents and discussions designed into a single hub, with API integrations pulling them in from the tools teams already used, so nobody has to check four apps for a status.
→
Designed, Tested, Handed Over
Al Bayader did not proceed to build. The design and its bilingual system were delivered in eighty hours, ready for their developers. Nothing here is a running product.
What I would do differently
Stay involved through the build. I designed for a handoff, the handoff happened, and I never found out why it stopped. Budget, priority, or something in the design that made it hard to build. I still do not know, and not knowing is the part that bothers me.
Five people on one routine is a small sample and I knew it at the time. Eighty hours does not buy a proper study, so I measured the one sequence every employee repeats daily and timed five of them. That was the right call under the constraint. It is still five people, and the page should say so rather than let 69% imply a study that did not happen.
