Especially the ones where the customer problem, technical constraints and business priorities don't line up neatly.
I've spent more than a decade building and delivering digital products across enterprise SaaS, healthcare technology, mobile, data and integrations. I moved formally into Product Management in 2021 after several years in digital delivery, working closely with engineering, design and customers.
What I enjoy most is the part where the answer isn't obvious yet. Getting close to the people doing the work, understanding what's actually causing the problem, making the trade-offs visible and helping a team decide what deserves to happen next.
01
Digital delivery taught me how things actually get built.
I started in digital delivery, working alongside engineering, design and customers on websites, mobile applications and enterprise platforms. It taught me early that a good strategy doesn't mean much if the team can't turn it into something people can actually use.
02
Healthcare made the consequences more real.
At Reliq Health, software became part of real clinical workflows. I worked across remote patient monitoring, reporting, integrations and connected medical devices. Reliability, data quality and edge cases stopped being abstract because the software sat inside work that people depended on.
03
At Cardata, the scope got much wider.
At Cardata, the scope got much wider. I progressed from Product Manager to Lead Product Manager and operated as the sole Product Manager for much of my tenure, with product ownership spanning platform modernization, mobile, analytics, integrations and financial workflows. I worked through a small Product, Design and Analytics team and partnered closely with Engineering, customer-facing teams and executive leadership, connecting what customers were experiencing with what Engineering was seeing, what Sales was hearing in the market and where the company needed to go next.
Give me a product with some ambiguity, legacy complexity, conflicting priorities and a real customer problem underneath it, and I'll probably want to dig into it.
HOW I TEND TO WORK
A few things I keep coming back to.
01
Get close to the workflow.
I'd rather watch someone struggle through the real process than start by asking them which feature they want.
02
Make the trade-off visible.
Most difficult product decisions aren't between a good option and a bad one. They're between two reasonable things competing for the same people, time or attention. Product's job is to make that trade-off explicit.
03
Leave it simpler than I found it.
New functionality is sometimes the answer. Sometimes the better answer is removing a step, automating a decision or deciding something no longer deserves to exist.
04
Ask what changed.
When a metric moves or a customer problem suddenly gets louder, I want to understand what changed before jumping to a solution. The difference between yesterday and today is often the fastest place to start.
THE PROBLEM SPACES I'VE WORKED IN
Different domains. Familiar problems.
A real workflow. A system that's outgrown its foundation. A decision about what deserves to stay complicated.
I'm drawn to products where complexity is becoming a constraint: a platform that needs to modernize, a company moving further into enterprise, something being built from zero, or a system where years of decisions have made the next one harder than it should be.
The domain matters less to me than the problem. I'm especially interested in enterprise SaaS, data and AI products, healthcare technology and connected products where Product stays close to both Engineering and customers.
Platform modernization0→1Enterprise expansionData & AI
BEHIND THE BUILD
I built this site as a product, not a brochure.
I designed and built this portfolio with AI-assisted development, from the information architecture and case-study system through visual direction, implementation review and responsive QA.
The useful part wasn't simply generating code faster. It was shortening the distance between a product decision and an artifact I could inspect, critique and improve.
Most of my time outside work belongs to my family.
I'm a husband and dad, and a lot of life outside work revolves around my family. I enjoy coaching my sons in soccer, being involved in what my kids are doing and watching that moment when something they've been working at finally clicks.
I like being active too. Hiking and working out are a big part of how I reset, and I try to take care of my health. Some of my favourite time is simply getting outside and spending time with my wife and kids.
I read because I get curious about things and usually want to understand them properly. And yes, I game. Strategy, RPG and management games are the ones that usually get me. I like building something, making decisions and getting far too invested in how the whole system works. Mostly, I just enjoy it.