About
I work at the intersection of strategy, storytelling, and user experience — helping turn ideas into meaningful, scalable products.
With a foundation in communications and a strong pull toward building, I bring both creative thinking and structured execution to the work. I’m most comfortable in the space where ideas are still forming, assumptions need testing, and teams are trying to figure out what actually matters.
An unconventional path into product
I didn’t start out in product management in a traditional way.
My early career was in fashion, PR, and communications, where I worked closely with customers and audiences; gathering feedback, spotting patterns, and translating insights into messaging and strategy. Over time, my curiosity shifted. I became less interested in how things were positioned, and more interested in how they were shaped:
the features we chose to build, the trade-offs behind them, and the impact those decisions had on real people.
That curiosity pulled me into product, and I haven’t looked back since.
What stayed with me from those early roles is a strong bias toward user perspective — listening carefully, asking better questions, and making sure what we build actually makes sense to the people using it.
What I'm building now
I’m currently the Co-Founder and Product Lead at Table Talks, a performance-driven marketplace connecting restaurants with food content creators.
I’ve been involved from the very beginning; shaping the concept, designing and building the platform in Webflow, setting up operational automations with Make.com, and working directly with users to iterate based on feedback. The focus has always been the same: build something that’s easy to use, scalable, and delivers real, measurable value for both creators and businesses.
Alongside this, I work with clients to help them organise what they’re trying to build whether that’s a website revamp, a new feature, or an entirely new product.
Often, people come with a clear sense that something isn’t working, but not yet a clear plan for what to do next. That’s where I tend to plug in.
How I usually work
Every team and project is different, but the work tends to follow a similar rhythm.
Start with what feels unclear
We begin by understanding what’s not working or what’s still fuzzy. You walk me through the product, feature, or site, and we talk about what you’re trying to achieve and why. The goal is to align on the real problem before jumping to solutions.
Bring structure to the ideas
Next, I turn that understanding into something tangible. This might be product flows, feature definitions, wireframes — always at the right level of detail to support decision-making. The focus here is clarity: making the ideas concrete enough.
Build, learn, and refine
Once there’s a clear direction, I stay involved through the early versions — supporting build decisions, thinking through edge cases, and putting feedback loops in place. From there, we refine based on how people actually use what’s been built.