About me

Life is a puzzle, and I love putting the pieces together.

I’m a data and UX consultant. I work in the overlap between data, design and the people who use both.

My story

I started in physics, learning how the world fits together, then moved into data. I was hooked on how data could be shaped and joined until it told a story, for me or for the company I worked for.

After a few years, I saw a pattern. Engineers, me included, struggled to explain meaningful work to the people who would use it. No one teaches you how to communicate outside your own domain.

Then I joined Method, a design firm, as a data engineer. The data practice was new, so for three years I worked side by side with the UI/UX teams on data-heavy products. I ran around 100 interviews, synthesized research, presented findings to stakeholders, and made sure every solution was technically viable.

I fell in love with that work. It gave me the communication skills I had been missing, the ones many data engineers never get to build. Data is complicated. It doesn’t have to feel that way, and I’m here to translate it.

Outside of work

I’m a big nerd. In 2011 I started “scrobbling” everything I listened to on Last.fm, so I’ve always been like this. When streaming took over I missed the smart playlists that music players used to have, so I built my own tool.

Rain in My Head is also how I practise. I wanted to learn more about UI/UX, web development and hosting, and how to build with AI. It gave me real data, a real brief, and a Friday 5 to 7 pm playlist with its own feeling.

See the project

How I work

Clarity is the deliverable

If a stakeholder can’t explain it back, the work isn’t done.

Translate, don’t gatekeep

I help engineers and designers become fluent in each other’s constraints.

Feasible before beautiful

A design the data can’t support isn’t a solution yet. I check what’s real first.

Start with the people

Every dataset, pipeline and screen exists to help someone do their job.

TODO: add your name and a photo. The last two values were marked “suggested” in the Brand Foundation doc.

Building or inheriting a data-heavy product?

Tell me what you are stuck on. I will tell you honestly whether I can help.

hello@storyandstructure.studio