zone access management is a telecom enterprise's internal b2b platform for physical access across a national estate: network staff request temporary or permanent zone access, admin managers approve the queue, super admins own the policies, and field engineers use it on site at building entrances and equipment rooms.
the tool had been built desktop-first, which suits the super admins and admin managers who will run it from a desk. field engineers, though, will be using it on the go on handheld devices, where the unadapted interface would make navigation a struggle, raise cognitive load and leave their tasks misaligned with the screens. the evaluation also found functional friction for every persona: blockers that surface late at checkout, order statuses hidden behind drill-downs, and deep navigation for simple tasks such as identifying building zones.
lead ux/ui designer, january 2026 to present. i led the ux evaluation, diagnosis and redesign direction before the application went live, and had to deliver every change inside the client's existing component library through html restructuring and css adaptation only: no backend change, no parallel app. i worked with engineering to validate feasibility and with business stakeholders on constraints.
eight friction gaps identified and addressed in the redesign across desktop and mobile, with wcag 2.1 aa targeted and the engineering handoff documented. projected from internal evaluation and validation sessions with representative users: 70% less order-status navigation overhead and an 85% mobile usability gain. the application was not yet live, so these are projections, not measured results.
designing for a system before it reaches its users means the usual feedback loops don't exist yet; what remains is structured evaluation, pattern recognition and the discipline to design for people who aren't in the room and who will meet every missed friction point at scale on day one. the constraint of the existing codebase wasn't the obstacle; it defined the problem precisely.
a global telecoms enterprise had built a robust internal tool to manage physical zone access across its estate - a b2b platform used by network staff, admin managers, and super admins to request, approve, and provision building access. the engineering foundation was solid. but when i engaged the project, the application hadn't yet gone live to primary users and the gap between what the system could do and how users would experience it was significant.
"the system worked. the experience didn't."
manages physical access requests across a national estate. users request temporary or permanent zone access, approvers process the workflow, and field staff use it on-site to verify and provision entry.
the interface had been built desktop-first with no meaningful mobile adaptation. interaction patterns, cognitive load, and status visibility were unaddressed. a pre-launch evaluation revealed systemic friction that would surface immediately at scale.
the rwd approach would be wrapped as a hybrid mobile app - b2b focused, shipped to field users who work across tablet and mobile, often in environments where desktop access is not possible.
i led the end-to-end ux evaluation, diagnosis, and redesign direction for this project. my engagement began before the application went live - which was both a challenge and an opportunity. there was no user feedback data. no support call logs. no usage analytics. what i had was the system itself, a set of target user groups, and over two decades of enterprise ux pattern recognition.
with no live usage data available, i treated the application as the primary research subject. expert evaluation, heuristic analysis, workflow walkthroughs, and an ergonomic field observation gave me the evidence base to diagnose both the visible friction and the systemic patterns beneath it.
"every mature application reaches a point where the interface needs to catch up with what the system can do."
cognitive
benchmarked against nielsen's 10 usability heuristics. identified violations across status visibility, error prevention, and flexibility of use - with particular severity on recognition vs recall and system feedback.
physical
discovered desk-based user groups (super admins, admin managers) routinely work across 37-inch wide-screen monitors and 14-inch laptops simultaneously. this informed layout density and information hierarchy for desktop views.
structural
mapped the five-stage approval workflow end-to-end. performed cognitive walkthroughs for each user group across zone selection, checkout, and order management scenarios.
research & findings
evaluation severity scored across primary interaction zones, weighted by user group impact and frequency of encounter.
research & findings
three distinct user groups with fundamentally different device contexts - each requiring a tailored but unified experience.
"owns the system. needs the full picture at all times."
37" wide-screen + 14" laptopmanages platform-wide access policies, user roles, and system configuration. works at a fixed desk with a dual-screen setup. responsible for large data sets and high-volume oversight.
"processes the queue. speed and clarity are everything."
37" wide-screen + 14" laptopreviews and approves access requests. manages multiple orders simultaneously. desktop-primary but may review on-the-go. needs one-click actions and clear status visibility to maintain throughput.
"in the field. one hand. needs it to just work."
handheld + tablet & mobilefield engineers requesting zone access at building entrances, equipment rooms, and restricted areas. primarily mobile users. needs fast, thumb-reachable interactions with minimal scrolling.
drag to compare the friction gaps & the applied solution
six recurring failure patterns - each with a direct design solution. two layout proposals below.
users must open each order row individually to check status. at scale - managing 10+ simultaneous requests - this creates significant unnecessary interaction overhead.
restricted zone justification only appears at final checkout. users complete the full flow before hitting this blocker - most common cause of abandoned submissions.
desktop layout carried to mobile viewports unchanged. small touch targets and horizontal scroll - particularly problematic for field staff at building entrances.
zone relationships between buildings and constituent zones are unclear. users can't determine whether a sub-zone is covered by a parent selection. ambiguity drives errors.
justification input focus triggers the soft keyboard, pushing critical warning messages out of view - hiding the information needed to write an effective justification.
state indicators use colour exclusively with no iconography or text labels. violates wcag 1.4.1. creates barriers for users with colour-vision deficiency.
colour-coded state, progress tracker and approval summary so users can scan all active orders at a glance without navigating into each row.
justification requirements surfaced within the zone selection accordion when a restricted zone is selected. zero late-gate blockers at checkout.
thumb-zone optimised layout, 44px minimum touch targets, bottom navigation pattern, keyboard-scroll-aware behaviour. tablet intermediate breakpoint defined.
indented zone tree with visual inclusion indicators. parent selection states show coverage. sub-zone coverage determinable without guessing.
css scroll behaviour anchors the justification input within a fixed viewport zone. critical warning content remains visible above the keyboard at all times.
status communicated via colour + icon + text label in combination. wcag 1.4.1 compliant. screen reader accessible. universally interpretable.
challenge & achievements
every screen improvement was achieved within the constraint of the existing codebase. html restructuring and css adaptation - no backend changes, no parallel application. the visual outcomes below represent the key workflow screens across desktop and mobile.
these outcomes are based on internal evaluation sessions and usability validation with representative users prior to engineering handoff. the application was not live to primary users during the engagement - outcomes reflect pre-evaluation findings and projected improvements.
overview & take away
working on a system before it reaches users is a rare position to be in. the feedback loops that normally shape iteration don't exist yet. what you have instead is pattern recognition, structured evaluation methodology, and the discipline to design for users who aren't in the room - and who will encounter every friction point you missed, at scale, on day one.
designing for a system before it meets its users is not a limitation - it is a responsibility. every friction point you catch in evaluation is one a field engineer won't face at a building entrance at 7am. the aha moment wasn't finding the problems. it was realising no one else had looked for them.
one codebase, zero backend changes, three user groups, and two screen extremes - from 37-inch wide monitors to field handhelds. the constraint wasn't the obstacle. it defined the problem precisely. that is where ux architecture earns its place.
