Twenty years making complex work legible — to the people who need to act on it, approve it, and deliver it. The methodology is in the work. Some of it is available to take away and use.
Standalone browser-based tools, practitioner guides, and content products built iteratively with Claude — domain expertise directing AI capability toward real practitioner problems. Process flow builder, Gantt builder, BA guide, prompt library, and MQU navigation tools.
Complex organisational problems made legible — cross-domain process maps with LINQ cost analysis, ERP migration across five systems with zero customisations, and a modular AI-assisted safety architecture built for incremental delivery in field operations.
Pre-AI-era product and UX design work — an award-winning iOS panorama app shipped before the iPhone had one, hardware UX for Gallagher's farm weigh scale range, a regulatory browser tool for EECA, and an online will builder where trust turned out to be harder than simplicity.
Every engagement follows the same underlying logic — understand the problem before designing the solution, map the people before writing the requirements, build the evidence before making the case.
The BAD methodology isn't a framework I've borrowed — it's the working logic extracted from twenty years of practitioner engagements, made explicit enough to teach. Five phases. Twelve artefacts. One consistent thread from problem statement to delivery.
The phase maps below show how that logic actually unfolds. Each phase has its own diagram. The full journey map shows all five in sequence. The artefact relationship map shows how they connect and depend on each other.
This is the methodology the BAD guide is built around — and the same logic I bring to every engagement.
My work sits at the intersection of how organisations operate, how information flows, and how people make sense of complexity. I work across process engineering, service design, systems thinking, and visual communication — often on the same project.
The challenge is always to come out with observations and insights — and then to articulate those in meaningful ways that inform decisions.
If you have a complex problem that needs to be made legible — to a team, a leadership group, or the people doing the work — I'd like to hear about it. Currently available for process engineering, service design, and systems thinking contracts in NZ and remotely.