My work is grounded in a simple idea:
Good systems come from understanding how work actually happens — not from tools, templates, or hype.
Technology changes quickly.
The gap between how work is imagined and how it is really done does not.
That gap is where frustration, inefficiency, and wasted effort accumulate.
It’s also where I focus.
My approach
I don’t start with software, automation, or AI.
I start by:
- observing how work really flows
- listening to the language people use to describe what they do
- noticing workarounds, friction, and repetition
- identifying where errors, delays, or stress are introduced
Only once that picture is clear does it make sense to decide what to change — and just as importantly, what not to build.
AI-assisted tools can be extremely helpful once clarity exists. They reduce effort and speed up implementation.
They remove drudgery
They don’t define direction.
Ways I Work With Businesses
Some work needs to be done on-site. Other work can be done effectively anywhere. I’m explicit about the difference so businesses can choose what fits.
On-site: Process Observation & Improvement
(Location-specific)
This involves spending time in the business — walking processes end-to-end, asking questions, and seeing how work actually functions day to day.
It’s typically structured as:
- Two days on site observing and discussing work
- a written report outlining:
- Where processes and systems create friction
- Where errors and rework are introduced
- Where small, practical changes would have the biggest impact
This is a fixed, stand-alone engagement.
There is no obligation to proceed beyond the report.
If further work makes sense, it is scoped separately.
Remote: Clarity Before Building
(Location-independent)
Not all work requires being physically present.
Often, what’s most valuable is clarity before committing time or money.
This may include:
- Reality checks before building apps or automations
- Structured reviews of existing workflows or systems
- Guidance on what to simplify, delay, or avoid altogether
This work is time-bounded and designed to reduce the risk of building the wrong thing — or building too much.
Remote: Scoped Implementation
Where it makes sense, I help implement specific, well-defined improvements.
Using AI-assisted tools allows this work to be done quickly and cost-effectively — but only after scope and intent are clear.
Implementation follows understanding, not the other way around.
What I don’t do
To keep the work effective, I’m deliberate about what I don’t offer:
- Open-ended consulting engagements
- Tool-led “transformations” without context
- Automation for its own sake
- Selling software as a solution
My goal is not to build impressive systems.
It’s to leave people with fewer decisions, fewer errors, and more confidence in how work gets done.
Simpler, not grander.
A note on geography
Some work depends on being present and is therefore location-specific. Other work translates well across borders.
Rather than pretending one size fits all, I’m explicit about which is which.
Understanding travels less easily than execution — and that’s a reality worth respecting.
Start a Conversation
If you’d like to explore whether this approach would be useful in your business, send a brief outline of what you’re dealing with, and we can decide whether a conversation makes sense.
You can reach me at:
[email protected]