I work on how work gets done.

Where I’m coming from

I’m based in Sydney, and I run a waterproofing consultancy. I run it on systems I built: a back office that keeps jobs, invoices and follow-ups in one routine, and small tools for the reports. Two of them are on the Real work page. I call the system Ops, which is where the name RunByOps comes from.

I’ve also consulted within my family’s business, and I’ve helped friends bring AI into their own work. My background also includes logistics.

Whatever the business, I’d rather simplify a process than automate a messy one, and I’d rather explain why something works than hand over a system nobody understands.

How I approach the work

Start with a real example.

One recent piece of work that got stuck tells you more than a process map.

Simplify before adding technology.

A reference number, a few required fields and a named owner are often enough.

Design for the next person.

Every record is for someone who wasn’t there. If they can’t act on it without asking, it isn’t finished.

Make ownership visible.

Every open item gets a person and a date. ‘The office’ is not a person.

Plan for the awkward cases.

The odd one out is the real test. A system that only works when I’m in the room isn’t done.

Keep judgement with people.

Software and AI can organise, check and draft. Decisions, approvals and sign-off stay with the people responsible for them.

A note on the examples

The worked examples in the guides are illustrative: invented to show how a method works, and labelled that way. The Real work page is different: systems from my own business, described without client details, with a sample run where one helps. There’s no client case study on the site yet.

Getting in touch

The easiest way is a free 30-minute call about one thing that keeps getting stuck. You can also find me on LinkedIn.