E-banking for millions of Danes

E-banking is the least forgiving design context I have worked in. Everyone uses it, most people use it reluctantly, and the cost of confusion is not a lost conversion but someone's money and their trust in an institution.

It is also unusually constrained. Security requirements, regulation and legacy systems all set boundaries before a designer opens a file, and none of them are negotiable.

The bulk of my time went into designing an entirely new e-banking platform and seeing it through to rollout. Not a reskin of what existed, a replacement, which meant every flow had to be re-argued from first principles rather than inherited.

In this domain the interesting question is rarely how a screen looks. It is what happens when someone is halfway through, uncertain, and about to abandon something that matters.

At BankData I was primary UX designer for the private e-banking platform, one of Denmark's most widely used digital banking products, owning design quality across the product for multiple member banks.

That meant partnering with product owners from several leading Danish banks and aligning their solutions without letting the underlying platform fragment into a set of special cases. Most of the work was finding the shared answer that each bank could still recognise as theirs.

I was also part of a team working through the technology options for a mobile app, weighing what each approach would mean for the experience we could actually build rather than treating the choice as purely an engineering one.

Alongside this I contributed to the original NemID validation app, a smaller piece of work but one with the same non-negotiable constraints.

At Jyske Bank the scope narrowed to one institution and widened in subject: digital products for private banking and investment customers across web and mobile, inside a cross-functional product team.

Much of the value was in coordination. Private banking, investment and compliance each arrive with legitimate and competing priorities, and the design job is turning that into one coherent decision rather than a compromise that serves nobody.

I challenged decisions where analytics alone weren't enough, pushing for research to surface the who and why behind the what. A number tells you that behaviour changed. It does not tell you who was affected, or what it cost them.

That instinct came from this domain, and it is the single habit I have carried into every role since.