About
Leaning into the challenge
I enjoy turning complexity into shared understanding: a problem definition people agree on, a scope that's buildable, and decisions that hold under pressure.
Philosophy
My path into product wasn't linear. I started in law, where I learned to think in systems and tradeoffs — and to take words seriously. Precision matters, because clarity changes outcomes.
Even then, I gravitated towards the practical side: building processes that help people work better together. When I moved into tech, I saw the same pattern everywhere — teams don't slow down because they lack talent; they slow down because context is fragmented and decisions stay implicit.
What motivates me isn't technology as novelty. It's the moment an idea becomes real — when it becomes part of someone's workflow and affects how they think, choose, and act. That comes with responsibility.
In an economy designed to capture attention, I'm interested in products that do the opposite: tools that respect people's time, increase human agency, and help them act with intention.
That's the kind of work I want to do — and I'm building Hesya as a live case study in this philosophy: a native iOS product designed to be needed less over time.
My Approach
My process is built around three pillars: focus, flexibility, and visibility. I use a structured system to turn ambiguity into clear decisions and steady delivery.
Frame the problem in writing
Start with a short PRD: business context, aims, and a precise problem statement — plus scope, out-of-scope, and references to learn the domain.
Shape a buildable MVP
Define the MVP as a complete, usable workflow. Prioritise using Must / Should / Could / Won't, grounded in constraints and the timeframe we've committed to.
Build the known core; clarify the unknown
Write down what's clear, validate directly with business stakeholders and domain experts, and deepen domain understanding in parallel.
Keep decisions easy to find
Small day-to-day decisions live in tasks and comments. Bigger tradeoffs are aligned with the business and reflected in the PRD.
Deliver steadily and protect quality
Ship every two weeks. Track progress through what we committed to deliver and user acceptance testing outcomes — supported by retros, Quality Tuesdays, and DX interviews.
What I Do
I take full ownership from problem framing to delivery — helping teams make decisions with clarity and ship products with confidence.
Shape the idea early
Turn goals into a clear problem statement, PRD, and MVP scope.
Make requirements buildable
Map workflows, define acceptance criteria, and unblock decisions fast.
Build what's certain; clarify what isn't
Keep the team shipping the defined core while resolving complex or uncertain parts.
Adapt without losing focus
Manage tradeoffs, re-scope responsibly, and keep priorities stable as conditions change.
Protect quality
Reduce friction in handoffs, keep delivery predictable, and support clean, maintainable builds.