Most product work doesn't fail because of execution - it fails because the wrong things get built. Before anything ships, I focus on reducing that risk by clarifying what actually matters. Not through long documents or abstract strategy, but by asking the right questions and making decisions tangible early.

This way of working is less about delivering answers upfront, and more about creating the conditions to arrive at the right ones. By turning ideas into simple, testable prototypes and staying close to real users, direction becomes something we can observe and refine - instead of something we debate in the abstract.

Clarifying direction

We turn critical questions into things we can observe and test, using strategic prototypes to explore, confirm or rule out directions before we commit.

Increasing velocity

Once our direction is clear, I typically work in tandem with developers to help them ship fast and learn from real user feedback as we iterate towards success.

I operate best at this stage, where there's still space to shape the outcome and where a few decisions can change everything that follows. It's a collaborative process, grounded in real use and real constraints, aimed at building products that don't just make sense on paper, but hold up when they meet the people they're for.