Diana Fitter

My role

UX design lead — sole designer, embedded in an Agile team

Scope

Two user types, AI-assisted workflows, full component library

Shipped

Prototypes, rebrand, and a Figma system now in development

The problem

The platform had grown feature by feature, and every screen assumed you already knew the system. Two audiences — the internal team who run the product and the customers who use it — were sharing one undifferentiated interface, so both were doing work the software should have done for them. There was no component library, no type scale, and no agreed visual language, which meant every new feature reopened settled questions.

Key decisions

1. Split the experience by user type before touching a single screen. I mapped both journeys side by side and found the overlap was smaller than everyone assumed. That let me give each audience a home that answers its own first question instead of a shared dashboard that answered neither.
2. Made the AI a suggestion, not a decision. Early concepts had the model act and then report. Research sessions showed users didn't trust that, so the pattern I shipped proposes, explains its input, and waits — with a visible path to override.
3. Built the design library as I designed, not after. Components and the rebrand landed in Figma in the same sprint as the flows they came from, so handoff was a walkthrough rather than a translation.

My role

Lead designer — IA, flows, visual system

Users

Librarians, district administrators, and internal support staff

Shipped

Redesigned portal, new user roles, refreshed brand

The problem

The portal was built for one kind of user and then handed to everybody. Administrators, librarians, and internal staff all saw the same wall of controls, so routine tasks meant hunting through settings that didn't belong to them — and the dangerous ones sat next to the daily ones. Nothing about the interface signalled which organisation you were acting on behalf of, which is exactly the mistake you don't want an admin to make.

Key decisions

1. Defined real user types, then cut each view down to them. Instead of adding another filter, I gave each role a portal that shows only what that role owns — the fastest way to remove work is to remove options.
2. Reduced the multi-step tasks people do every day. I traced the most repeated flows, collapsed the ones that were only long because of legacy screen boundaries, and moved confirmation to the moment of consequence rather than the start.
3. Used the rebrand as a wayfinding tool. New type scale, colour, and a clear hierarchy of destructive versus routine actions — so the visual refresh did structural work instead of just looking newer.

My role

Lead designer — wireframes to visual design and audit

Users

Teachers and internal staff, on a school-day schedule

Shipped

Merged site, new nav model, WCAG 2.1 pass

The problem

Two training libraries were merging into one site, and each arrived with its own navigation, naming, and audience assumptions. Teachers were the people least able to absorb that: they come in with a prep period, a specific requirement to satisfy, and no patience for browsing. The question wasn't how to fit both catalogues on a page — it was how someone lands, sees what they already started, and gets back to it.

Key decisions

1. Put in-progress training above browsing. The logged-in home leads with announcements and what you're partway through; discovery sits underneath it. Returning beats exploring for this audience.
2. One category layer, not two taxonomies. I flattened the merged catalogues into a single browse grid with counts, so nobody has to know which of the two legacy sites a course came from.
3. Separated internal and teacher views. Staff need enrolment and reporting; teachers need their next course. Splitting the user types kept the teacher home short enough to scan in one screen.
4. Audited as part of design, not after launch. Contrast, keyboard order, and screen-reader labels were checked in the file — the fixes that usually arrive as post-launch tickets were already in the spec.