Iterative & Incremental.

I follow an approach that involves framing opportunities, discovering and developing MVPs, measuring success, and then repeating the process. By working iteratively and incrementally, I deliver thin vertical slices of a complete vision, allowing for continuous measurement and improvement.

Thin vertical whats?

'Thin Vertical Slices' is a phrase you'll hear from me often! It refers to the leanest, usable feature set. Instead of creating an empty homepage facade with unusable features, I identify all the necessary steps for an MVP and deploy early. This ensures the product starts generating a Return on (your) investment (ROI) as soon as possible. If the project halts tomorrow, the product will still be complete and the best it can be at that moment. I build all features at their leanest fidelity and layer on complexity until the project ends, much like an onion or a parfait.

Key principles.

My approach centres around five key principles:

Design Thinking

A non-linear, iterative process that seeks to understand users, challenge assumptions, redefine problems, and create innovative solutions to implement and test.

Lean UX Design

A mindset, culture, and process that embraces Lean-Agile methods. It implements functionality in minimum viable increments and measures success against a benefit hypothesis.

Agile Delivery

An iterative approach to delivering outcomes where teams adjust their ways of working incrementally rather than delivering all outcomes at once.

ROI Focus

A commitment to ensuring that each iteration delivers measurable value and generates return on investment as early as possible. By prioritising features that provide immediate value, the project remains aligned with business goals and justifies continued investment.

Learn, Build, Measure, Repeat

A continuous cycle that involves learning from users/stakeholders, building MVPs, measuring their success, and repeating the process to refine and improve the product.

If Learn, Build, Measure, Repeat were a diagram….

Deliver Lean, Working Features

This image illustrates what can happen when a project is over-engineered at the start. Jeff’s face and hair are highly detailed, but his legs are sparse and probably don't work properly. This situation arises from focusing too much on certain parts initially and then running out of time towards the end.

It's better to deliver all features lean and functional, adding complexity if time allows. The product should still be something you’re proud of—perhaps even more so because it is a working product without bugs.


Dual Track Delivery

When designers and developers work in sync and collaboratively it really is a beautiful thing.