A shared design language

Different teams. One familiar experience.

Ledger is a fictional design system for Halden Bank. The brief was to connect a growing family of banking products without making every screen feel identical. I worked across product design and front-end development, starting with the everyday patterns customers encountered most often.

Start with the things people repeat.

An interface audit revealed a familiar problem: each team had a slightly different answer for buttons, account balances, errors and form fields. We mapped those differences, kept the useful ones and agreed on a smaller shared set. Tokens for color, space, typography and state gave the system a foundation that could travel between design and code.

The library grew through live product work. Every new component came with a reason to exist, guidance on when to use it, and keyboard and screen-reader considerations. We paired visual examples with clear writing, so the system could explain itself to someone joining the team.

A foundation, with room to grow.

The resulting concept brings together component patterns, a reusable token model and practical documentation. The aim is a more recognizable banking experience and fewer repeated decisions for the teams making it. This is an illustrative portfolio case study; the company, interfaces and project details are fictional.