Decisions people
can build on.

Make the commitment smaller than the ambition.

An important initiative needs a clear first decision. I establish the customer, the business objective and the constraint before turning the opportunity into a roadmap.

At Neos, that meant a staged release for the product’s starting experience. At O-HIVE, it meant a complete review loop before a wider feature set. In market development, it meant a focused pilot before a broad launch.

Give responsibility a practical shape.

Hiring, contracts, priorities and reviews are part of product leadership when the team needs them. I make ownership explicit, surface dependencies and create a regular place for unresolved decisions.

I stay close enough to the work to recognise when the plan no longer fits. The team should understand why a priority changes, what has been deferred and who is responsible for the next step.

Make the requirement useful to engineering.

A requirement needs more than a proposed screen. I work through the information, permissions, states and exceptions that determine whether an experience can function.

I work directly with technical teams on what can be delivered and in which order. The intended outcome stays visible as we resolve the detail.

Know what has to happen around the product.

A platform needs participants, a partnership needs workable terms and a market launch needs an operation that can support it. I bring those dependencies into the product conversation early.

At Izisurf, creator recruitment and commercial trust shaped the product itself. In international market development, customer insight, partner capability and operational readiness shape the route to market.

The person behind the approach.

Hear me talk about my experience and how I work across product, design and business.