Who I Am — Wesley

This isn’t a bio. A bio lists where you’ve worked and what you’ve done. That’s not very interesting.

This is an attempt to be honest about how I’m actually wired — because I find that more useful, both for myself and for anyone trying to understand why I think and work the way I do.

I’m a systems thinker first

I don’t just want to do things. I want to understand how they work, improve them, and — where possible — scale them.

That’s why I’m drawn to automation, process optimisation, machine learning, and strategic frameworks. Not because they’re fashionable, but because they represent the same underlying thing: leverage. The ability to produce more output per unit of effort by improving the system rather than just working harder inside it.

I don’t like randomness. I like leverage.

This shows up in how I approach problems at work, how I train for Ironman, and how I think about learning. I’m almost always asking: what’s the system here, and how could it be better?

I learn through application, not theory

I have very little patience for abstract concepts that don’t connect to something usable.

What I actually want: systems I can use, frameworks I can apply, models I can build and test. Concepts earn their place by doing work in the real world. If an idea doesn’t change how I act or what I build, I’m not sure it’s worth much.

The loop I try to run: Learn → Apply → Refine → Systematise.

That’s also how this writing works. Most posts here aren’t finished positions. They’re attempts to think something through by forcing it into language — which is the most honest test I know of whether you actually understand something.

I’m moving toward high-leverage impact

There’s a transition I’ve been making consciously:

From: how do I do the work?
To: how do I build systems that do the work?

That shift changes everything. It means thinking about ownership over execution, scale over effort, influence over activity.

I’m not there yet. But it’s the direction I’m orienting toward — in how I approach my role, how I think about career, and how I think about teams.

I know what I want from the people I work with

I’ve spent enough time in misaligned teams to know what I’m looking for:

Someone who executes well and follows through (the Operator)
Someone who holds the pieces together across people and processes (the Integrator)
Someone who challenges assumptions and doesn’t let weak thinking slide (the Challenger)
Someone who brings new ideas and sees around corners (the Explorer)

I’m naturally the Challenger, sometimes the Operator. I’m building toward being the person who can hold the whole system.

The honest version

I’m not trying to be “successful” in the conventional sense.

I’m trying to become highly effective at scale — in myself, in the teams I’m part of, and eventually in the organisations I help build or lead.

That’s why I care about systems. That’s why I care about structure. That’s why Ironman matters to me as much as anything I do at work. It’s all the same underlying project: building the ability to design and execute under pressure, consistently, over time.

This site is part of that project too. Writing is how I test whether I actually understand something — and how I stay honest with myself about where I’m at.

If something here resonates, or you think I’ve got something wrong, I’d genuinely like to hear it.