Work

(Case studies & system)

My approach.

  1. Doubt costs less than code.

    One wrong bet costs a startup months of runway. Research once killed a feature on paper and saved two.

  2. Ship early, learn fast.

    A first version in real hands teaches more than a second draft in review. Some loops end in a better feature, some end in none.

  3. Quality is hiding in details.

    Nobody mentions the details, everybody feels them. They separate cheap from crafted, so emotion is built where a journey is decided.

What I bring to a team.

Six years of design in a B2B startup, through every stage of a product: a rough alpha, a first real version, then a base large enough that a wrong turn gets expensive. Each stage asked for a different one of these six.

  • Choosing what to build

    • Tying every screen to a business goal
    • Naming the value before the features
    • Shaping the roadmap, not taking it
  • Going after the signal

    • Running research that collects itself
    • Reading numbers and interviews together
    • Stating the assumption, then checking it
  • Crafting how it feels

    • Holding the same bar from flow to pixel
    • Placing emotion where the journey turns
    • Defending the detail when time runs out
  • Rationalising a design system

    • Writing rules a team will actually follow
    • Designing for scale and for speed
    • Making accessibility a token, not a review
  • Deciding with data

    • Setting the target before the build
    • Naming who decides, and on what
    • Answering why before touching how
  • Bringing a team along

    • Making room for juniors to own things
    • Pulling sales and support in early
    • Showing what design pays back