How I approach the work

My opinions on how design can be more strategic, and what I have done about them.

01

Product focus + user focus

Reality

HIPPOs or the largest customer crashes the roadmap, side step process. Teams are pushed into outputs over outcomes, shipping features without a clear problem, and the product debt builds.

Stance

To be a genuine partner rather than a service function, design has to understand the domain, the real value to the customer and the commercial drivers of the business.  Connecting their work with key levers like reduce cost, or grow revenue.

Where I've done it

Snyk: restructured technical docs around onboarding workflows for high-volume, low-touch customers, cutting cost to serve, reducing churn. IG: solved the actual drivers behind customer support calls, eliminating thousands of them.

Why it matters

Design earns a seat at the table by speaking the language of the business, its levers. This is how design moves from defending the user to shaping where the business goes next.

02

Silos into one experience

Reality

The fastest path is to build and buy standalone entities with no dependencies, but that leads to silo products. No stickiness, no moat. Both Snyk and PVcase scaled quickly with isolated point solutions.

Stance

Map the customer's world and where our product fits: the triggers that drive user behaviour, and the jobs to be done. Help product teams understand where their slice fits into the system. Then find broken workflows to turn into opportunities and build the sticky platform.

Where I've done it

Snyk: the experience map aligned everyone on domain and ICPs, that led to reorg of product & tech. PVcase: four siloed products consolidating into one platform, so users stop dropping out of our system and we gain access to rich data.

Why it matters

Setting a vision for the future can take design from an execution function into a change agent, setting  direction for the product and the org.

03

Scaling teams and capability

Reality

Whether scaling impact or headcount, the challenge is to raise the bar on accountability and craft. Unloved teams become individuals designing for their personal portfolios.

Stance

Keep standards, rituals and systems intact through growth, and use the growth to raise the craft bar, not just hold it. Paved paths with design systems, shared ownership of a single user experience. I’ve done both build-from-nothing and inherit-and-reshape.

Where I've done it

Snyk: design 1→12. IG: five disciplines into one 30+ person department. PVcase: inherited a team that worked in silos, rebuilding it as one platform group.

Why it matters

More people means more opinions to align, reduce impact and velocity. Growing headcount needs to compound.

04

AI: new ways of working

Reality

AI has turned the product development process on its head. The upfront work to de risk the build is no longer needed, building is now fast and cheap. Teams ship far more than before, including poor work: features that don't fit together or solve a real problem.

Stance

We can go faster, but the aim hasn't changed: solve real customer problems, and build a coherent system that people can use. User research, problem definition stay as key steps in the process. Be intentional about rapid prototypes being POCs not product.

Where I've done it

PVcase: leading the revision of the product development playbook. Prototyping in disposable code instead of Figma, AI to synthesise research faster, and small UI fixes shipping straight to production.

Why it matters

We are all still learning where the return is and where the traps are, so I run each change to the process as an experiment. Supporting our teams in transitioning to the new tools.