Approach

Stronger teams.
Better outcomes.

I combine deep technical experience with genuine people leadership — creating the conditions where engineers grow, teams align and organisations deliver what actually matters.

01

People
first

Strong engineering starts with psychological safety. People need to feel safe challenging decisions, admitting uncertainty and raising problems early — before they become expensive. Everything else follows from that.

→
02

Clear
direction

As a Scrum Master and engineering lead, I've learned that clarity of direction isn't about more process — it's about the conditions for informed, autonomous decisions. I give teams the context to act without waiting for instruction.

→
03

Technical
credibility

20+ years of hands-on engineering. I stay close to the code because good architectural decisions require understanding the trade-offs, not just the patterns. Technical leadership means being able to challenge assumptions, not just endorse them.

→
04

Sustainable
pace

I care about flow and cognitive load, not just output. Teams carrying too many responsibilities, dependencies and interruptions slow down regardless of individual talent. The DORA research confirms it: elite teams achieve both speed and stability.

→

How I Think

Create conditions.
Trust the team.

I don't manage output directly — I manage the conditions that make great output possible. Amy Edmondson's research shows psychological safety is the single strongest predictor of team performance — not talent alone. Four things I work to put in place for every team I lead.

Psychological safetyPeople speak up, take risks, admit mistakes
Clear directionGoals, priorities and ownership are unambiguous
Removed blockersFriction is cleared before it slows teams down
Room to growStretch work, feedback and autonomy to own outcomes

Principles

  1. 01
    Context over rules

    I give people the why, so they can decide without me.

  2. 02
    Feedback is a gift

    Caring personally while challenging directly — not one or the other. Honest feedback is how engineers grow.

  3. 03
    Protect deep work

    Fewer interruptions, more meaningful output.

  4. 04
    Hire for growth

    I look for curiosity and character, not just credentials.

  5. 05
    Lead by example

    I write code, give reviews and stay close to the work.

In a nutshell
“ The best thing I can build is a team that doesn't need me to make every decision. ”
AS

Reading & Influences

  • AccelerateForsgren, Humble & Kim
  • Team TopologiesSkelton & Pais
  • The Manager's PathCamille Fournier
  • Staff EngineerWill Larson
  • Radical CandorKim Scott
  • Psychological Safety at WorkAmy Edmondson

Let's build something that lasts.

Get in touch →