How I work

Growth creates complexity. Clarity doesn't have to disappear.

When companies scale past 20-30 people, the informal ways of working that got you here stop holding.

You start noticing:

  • Decisions slow down or pile up on the founder's desk

  • Ownership blurs, "I thought you were handling that"

  • Pressure concentrates in the wrong places (usually on your best people)

  • New hires take months to figure out "how we do things here"

Founders feel it first. Teams feel it everywhere.

The reality is: this isn't a people problem.

Your people aren't the issue. Your systems are.

Not your tech systems. Not your product architecture.

Your human operating systems, the practical, lived ways work actually gets done.

When those systems are under-designed, everything else strains.

What I do (and what I don’t)

  • I help scale-ups design human operating systems that support growth instead of fighting it.

    This is not traditional HR. I'm not building policies or handbooks.

    This is systems thinking, applied to humans so growth doesn't break the people doing the work.

    • Decision-making frameworks (so you're not the bottleneck)

    • Clear workflows and handoffs (so things don't fall through cracks)

    • Role clarity maps (so ownership is obvious, not assumed)

    • Operational rhythms (so mistakes get caught and fixed)

    • Inclusive process design (so diverse thinkers can succeed)

    Not rigid. Not bureaucratic.

    Clear, flexible, and scalable.

Find out More

Why sustainable scale requires three systems to stay aligned

Most founders focus heavily on two of these:

  1. Technology (how work flows through tools and infrastructure)

  2. Governance (how decisions get made and who has authority)

But they under-design the third:

  1. People systems (how teams experience responsibility, autonomy, and belonging)

When the people system is invisible or assumed, the other two start breaking.

Signs this is happening

  1. Your best engineer leaves because "it's not clear what I'm supposed to own"

  2. Cross-functional projects stall because no one knows who decides

  3. The same problems keep happening because there's no learning loop

  4. Teams work in silos because collaboration isn't designed in

My work focuses on making the people system visible, intentional, and fit for what's next.

I don't believe in one-size-fits-all frameworks. Every scale-up's operational challenges are unique.

But the process of diagnosing and fixing them follows a proven pattern.

This is what I call the Human Systems Architecture Method and it's how every engagement works:

My Approach

  • We start by understanding what's happening, not what's written in decks or process docs.

    What this looks like:

    • Interviews with key people across teams

    • Pattern spotting through observation (where does work slow down?)

    • Targeted questions to surface friction, duplication, and invisible labour.

    Outcome: Clarity on where energy is leaking and why.

  • Together, we define the real problem to solve and just as importantly, what not to tackle yet.

    This prevents over-engineering and keeps focus on what will unlock the most momentum.

    • We identify:

      • Bottlenecks (where work gets stuck)

      • Decision failures (who should decide what, but doesn't)

      • Ownership gaps (who's responsible, but it's unclear)

      • Invisible labour (who's holding things together through heroics)

      Outcome: A clearly scoped challenge aligned to current business priorities + a visible map of friction, risk, and opportunity.

  • We map how work actually flows (vs. how you think it flows).

    This includes:

    • Cross-team handoffs

    • Decision points

    • Communication patterns

    • Where tribal knowledge lives

    Outcome: A clear picture of your current operating system (the good and the broken).

  • We explore options, not assumptions.

    We design and test practical solutions, then prioritise what will deliver the most impact with the least drag.

    Outcome: A realistic, prioritised Human Operating Backlog, not a wish list, but a roadmap of what to fix first, second, third.

  • Meaningful change requires repeatable habits, not just documents.

    I support leaders to embed new ways of working into behaviours, rhythms, and expectations, adapting as the organisation continues to grow.

    Here's what makes this different:

    During the engagement, we take one priority focus area through full design, implementation, and behaviour embedding.

    Other challenges uncovered during discovery are captured in your Human Operating Backlog, a clear, prioritised roadmap for what to address next.

    Outcome: Change that holds under pressure, not just on paper.

This method comes to life in the Human Operating Blueprint my flagship engagement. A 90 day focused sprint designed to create clarity, momentum, and shared ownership across teams.

What it does:

  • Reduces people risk

  • Eliminates founder bottlenecks

  • Speeds up onboarding

  • Stops repeated mistakes

  • Makes growth sustainable

What it gives you:

  • Systems that work for diverse thinking styles (not just neurotypical extroverts)

  • Operational clarity without bureaucracy

  • Confidence that growth is supported by design, not held together by individuals

Get Started

Why this Matters Now

The operational friction you're experiencing today, the bottlenecks, the communication breakdowns, the founder dependency, it only gets worse as you scale.

You can ignore it and hope it fixes itself.
(It won't. It'll just get more expensive to fix later.)

Or you can design the systems now that let you scale sustainably.

That's what I help you do.

Book a 30-min clarity call