Security & Access Control

Security products carry high stakes, where people have to trust the interface and act on it fast.

Trust on sight

A visual language that earns confidence before a user reads a word.

Roles and permissions

Admins, operators and viewers each get exactly the control their role allows.

Hardware pairing

Interfaces that account for device state and connectivity, not just clean data.

Real-time monitoring

Dashboards where the one event that matters is the one you notice first.

Audit trails

Compliance and history made visible without burying the live picture.

High stakes, on screen. People have to trust the interface and act on it fast.

Roles and permissions, real-time alerts, audit trails. I design the hierarchy so the one event that matters is the one you notice first.

UX Design

Research-led design for security-critical products.

UI Design

Interfaces for monitoring, access control, and management.

Branding

Brand identity that communicates trust and authority.

Apps

Mobile apps for access control and field hardware.

iCetana

Branding and website for an AI-powered surveillance analytics platform. Trust-first visual identity.

View project

Truphone

Rebrand and website design for a global telecoms provider operating in 200 countries.

View project

Rapport

Employee engagement platform. UX and product design for internal communications and recognition tools.

View project

14 Apr 2026

What Makes a Good Portfolio Website?

Why does a security product need a specialist designer?

Because the stakes are visible in the interface. Users need to trust what they see and act fast. Get the hierarchy wrong on a monitoring dashboard and an operator misses an alert that mattered.

Have you designed access control or monitoring products before?

Yes. iCetana's AI surveillance analytics platform, plus access control and body-worn camera systems. I know the patterns: roles and permissions, real-time alerting, audit trails.

Can you design for complex user hierarchies and permissions?

Yes. Role-based interfaces are a core part of this work. Admins, operators and viewers each need exactly the right amount of control and no more, without the product feeling like five different products.

Do you handle hardware-software interfaces?

I've designed software that pairs with hardware: cameras, sensors, access readers. The interface has to account for device state and connectivity, not just clean data.