Clarity before speed
People move faster when the outcome is written down before the task is assigned. I start with what success looks like, who decides, and by when.
In practice: Write the outcome first.
Read the thinking →Leadership
Leadership that makes the next step clear.
Clarity first, ownership shared, evidence over opinion, and a team that grows. This is how I lead, and how I try to inspire the people I work with.
Principles
01
02
03
04
05
06
Six commitments.
Ownership, made visible
Every decision and every piece of data has a named owner. Ownership is shared out on purpose and never left implied.
In practice: A named owner on every decision.
Read the thinking →Evidence over opinion
I would rather run the smallest test than win the argument. Proofs of concept, characterization tests and read-only checks settle debates calmly.
In practice: The smallest test that could prove me wrong.
Read the thinking →Show the reasoning
Decisions are dated and recorded with the alternatives and the tradeoff, so a new teammate can learn from them and a skeptic can disagree well.
In practice: Dated decision logs and risk registers.
Read the thinking →Grow the team
I align, lead and grow teams. Work is handed over with notes, written up so others can pick it up, and taught through writing rather than held in one head.
In practice: Handoff notes and write-ups, not heroics.
Read the thinking →Lead by doing
I stay close to the work: plans, status documents, commits and reviews. I take full ownership of what I build and say plainly what went wrong.
In practice: Status documents on day one.
Read the thinking →
How I inspire
Three ways I try to bring people with me.
Through story
I translate technical detail into clear actions and motivate teams with a story about why it matters, not just a list of tasks.
Through example
I do the work in the open: status pages, handoff notes and write-ups anyone can read and reuse.
Through safe experiments
Smaller tests make it cheap to try an idea, so people can propose bold things without betting the project on them.
The path
From hands-on to leading.
- Software engineer
Learned the discipline of business-critical code: testing, documentation, quality. - Development team lead
Led a team of five on a client platform for eight years. - Senior engineer, then development manager
Moved from building to growing the people who build. - Senior solutions architect
Set technical direction across systems and integrations. - Director of Technology & Innovation Current
Leads research, prototyping and delivery.
What you can expect
Working with me.
- Plain-language updates, not jargon.
- Decisions written down, with the tradeoff.
- A named owner for every piece of work.
- Small steps that can be reversed.
- An honest status, including what went wrong.