The Problem

Norton Rose Fulbright's compliance and privacy audit teams were running investigations the hard way. Analysts juggled emails, folders, spreadsheets, and a previous tool that had better visuals than functionality — the client's own words during our discovery session.

Reports were manually assembled, prone to error, and clients frequently didn't receive properly formatted final documents. The ask: build a structured platform to replace it entirely.

Discovery — Listening before designing

Rather than working from a written brief, we ran a structured stakeholder session directly with the client. I contributed to preparing the session agenda covering five areas: briefing, strategic objectives, user context, product requirements, and next steps.

The questions were deliberately outcome-oriented — not "what features do you want" but "what does success look like for your team?" This gave us the clarity to design for real needs, not assumed ones.

Key Design Decisions

Selected Screens

My Role — Honestly

I was the UI designer on this project. A UX designer handled information architecture and user flows. My ownership was translating those flows and discovery insights into visually structured, component-based screens — every state, every error, every success message, every modal.

I also contributed to the client requirements session, which gave me context most UI designers wouldn't have. I built a component-based Figma library and worked directly with the frontend team during implementation.

Outcome

NT Analyzer was successfully delivered to Norton Rose Fulbright, replacing a fragmented manual process with a structured end-to-end workflow. The platform covers case initialization, report generation, legal verification, client delivery, and full audit trails with version history throughout.

The Challenge

Norton Rose Fulbright needed to replace an aging intranet. The project involved EICE designing all UI templates, with Infodash handling development and all deeper page implementation. Our screens would be handed to a vendor to replicate across hundreds of pages.

That constraint shaped everything. Every design decision had to be self-evident. Patterns had to be consistent enough to scale without our involvement. We weren't designing pages — we were designing rules that pages would follow.

Key Design Decisions

Selected Screens

Outcome

Athena's template system was delivered to Infodash for full platform implementation. The screens established the visual language, component patterns, and information hierarchy for the entire intranet — covering the homepage, all primary sections, and specialist tools like the CV System.

For a firm of NRF's scale, an intranet is infrastructure. Designing that infrastructure at template level — knowing our decisions would be multiplied across hundreds of pages — required a different kind of design discipline than most product work.

The Challenge

EICE makes 7+ products across very different categories — security, ERP, logistics, AI, file sync. The challenge wasn't just design — it was making a fragmented product suite feel like one coherent company. With no brief given, I defined the problem, the direction, and the solution.

Outcome

A live corporate website unifying EICE's full product suite under a single coherent visual language — navy and cyan brand system, consistent typography, and a navigation architecture that makes 7+ products feel like one company. Used by the sales team for enterprise client pitches.

Add your full case study content here once written. This page is ready for your text and screenshots.

Coming Soon

This case study is being written. Add your HR Portal screens and case study content here. The page structure is ready — just replace this placeholder text with your narrative following the same format as the NT Analyzer case study.

Live product: eicepayrolldev.eicetechnology.com