I design the interfaces enterprises actually work in.

The brief

Broad A/S builds logistics software for retailers, operators and distributors who run their own delivery fleets. Three audiences, three very different jobs: dispatchers planning and monitoring zones, drivers executing routes on a phone, and recipients tracking a parcel they did not choose to be waiting for.

Built separately, those become three products that look and behave like three companies.

The approach

I ran the full lifecycle: user research, information architecture, prototyping and developer handoff, then pulled every surface back into a single Figma component library.

One system, one set of tokens, one behaviour for a status, a progress bar, a route marker. Fifty-plus screens across three products, and a dispatcher can recognise the driver app instantly.

Driver app

A driver reads this at arm's length, in a van, in poor light. So the home screen answers one question first, in the largest type on the page: how many stops are left. Everything else, scan, search, navigate, sits one tap away.

Route, scan and trace

The route view leads with the shape of the whole day, then expands only the next stop. Scanning puts mode selection in a colour-coded carousel under the thumb, so a driver switches state one-handed. Every scan writes to a shipment timeline the recipient can read.

The brief

Small and mid-sized companies know they are exposed and have no way to reason about it. Security tooling is built for security teams, so it reports in a vocabulary the person holding the budget does not speak.

We were building for a managing director, not an analyst. Every design decision had to survive that.

The approach

Three translations carried the product. Posture became a school grade from F to A. Exposure became a number in kroner. A pile of findings became a sequenced plan.

I ran 15 customer interviews to validate the concept, designed the full product, and defended the business plan as my MSc thesis at DTU, graded A−.

The brief

Booking digital advertising traditionally means an agency, a media plan and a wait. Ringier wanted advertisers to do it themselves, in minutes, without understanding ad tech.

The catch: underneath the simple flow sits real ad-server complexity. Line items, sync states, commission models, targeting taxonomies, and a campaign manager team who still need every one of those controls.

The approach

Two audiences, two surfaces, one system. Advertisers get a linear creation flow that asks one thing at a time. Campaign managers get a dense admin cockpit that exposes everything.

I delivered end-to-end UX, wireframes through developer handoff, covering the web, LinkedIn and Google ad creation flows in a fast-paced Agile team.