Bet

Independent product concept

Bet

A reasoning layer for product decisions.

Product teams remember what they shipped. Bet preserves what they believed, how confident they were, and what happened next.

Product strategy · AI interaction · Prototyping

Explore the case →
Bet product interface showing the assumptions behind a committed product decision

Selected work

Where the questions came from

The projects below left me with questions that continued beyond the work itself: how systems shape decisions, how organisations coordinate complexity, and where structure helps or gets in the way.

District corporate banking dashboard
Bringing multiple banking services into one experience

Work · Danske Bank · Platform

District

Building the customer platform behind Danske Bank’s corporate banking products.

One platform, many products, and every corporate customer’s daily banking sitting on top of it. The work was architecture as much as product: deciding what belonged in the shared foundation and what each team should own above it.

Platform architecture · Corporate banking · Build-vs-buy · Systems design

Explore the case →
Channels UI Platform conceptual interface
One platform underneath every digital channel

Work · Danske Bank · Platform

Channels UI Platform

Turning separate channel foundations into a shared product for teams across the bank.

Each channel had built its own foundation, and every one of them was maintaining the same things twice. The task was to make the platform a product in its own right—with a roadmap, releases, and internal teams as its customers.

Design systems · Platform strategy · Release management · Multi-team enablement

Explore the case →

The common thread

Across these cases, the work sits at the boundary between product, systems and people.

Worked across
Customer products · internal platforms · emerging technology
Questions explored
How systems shape decisions · how teams coordinate · how complexity becomes usable
Focus
Turning ambiguity into structures teams can build with

Derived reflections

Writing from the same questions

Reflection · Delivery

What Gets Embedded

The number that travelled upward was how many customers had moved onto the new platform. It had no opinion about what they’d actually moved into.

Read the note →

Reflection · Delivery

What Counts as Done

A minimum viable product promised before anyone agreed what “viable” meant. The deadline was clear. The learning was not.

Read the note →

Still unfolding

I am still interested in the gap between what people intend, what systems encourage, and what actually happens when the two meet.