Early-stage diagnostic practice
Most projects fail before they begin.
Not in delivery. Not in execution. At the point before anyone opens a brief — when the wrong problem gets named, assumptions go untested, and the shape of the work gets fixed before anyone has earned the right to fix it.
It happens the same way every time. The business has a theory. The people brought in to help have one too. By the time the project is underway, the original assumption hasn't been tested — it's been built on. The project hits its marks, the KPIs get met, and it gets called a success. Measured entirely against criteria that inherited the same assumption they were never asked to examine.
This practice exists for that earlier moment.
Structured diagnostic work, applied before decisions get locked in. Four disciplines — Discovery, Analysis, UX, and Brand Sense — used individually or in combination, at the point where they have the most leverage. Not consulting. Not strategy in the conventional sense. The kind of rigorous early-stage work that most project teams aren't structured to do, and most engagements skip entirely.
If you're about to start something, or you've started and something feels off — this is where that gets examined.
Capabilities
Four disciplines. Applied at the point where they have the most leverage.
Each one is a practice in its own right. Each one can be engaged individually. Used in combination, they cover the full diagnostic range of early-stage work — from hypothesis to structure, from user to brand.
Discovery
Understand the problem before you commit to solving it.
Most engagements begin with a solution already in mind. Discovery works the other way. It starts with a hypothesis — what do we think is true, and what would we need to see to confirm or challenge it — and works forward from there.
This is structured, hypothesis-driven work. It surfaces assumptions, tests them against reality, and produces a clear picture of what the problem actually is before any significant resource gets committed.
What comes out of Discovery isn't a report. It's a defensible foundation for everything that follows.
Analysis
Analysis isn't about capturing what people want. It's about understanding whether what they want is what they need.
Most project environments treat analysis as a documentation function — capturing what stakeholders want and formalising it into a list. That's transcription. What this practice does is different. It interrogates the request, tests it against what the organisation actually needs, and maps what any proposed change will genuinely touch. The document is the output. The thinking is the work.
Sometimes what Analysis unearths needs to go back to Discovery. A finding that doesn't fit the original hypothesis. A structural gap that reframes the problem. That loop isn't a setback — it's the process working as it should. It's how the right question gets found before the wrong answer gets built.
Done properly, Analysis is the foundation everything else is built on. It prevents the kind of mid-project surprises that aren't really surprises — the ones that were always there, just never examined.
UX
Users are not edge cases. They're the point.
UX practice here is user-led and principled — not aesthetic, not assumed. It starts with how people actually behave, not how they're assumed to behave. That means research before recommendations, observation before opinion, and a consistent return to the question of whether the thing being built is genuinely usable — or just usable in theory.
The work is digital and web-specific. It covers the full range of early-stage UX activity — user research, task analysis, journey mapping, prototype testing — applied at the point where they have the most leverage, before interface decisions get locked in and behaviour gets designed around assumption rather than evidence. Most usability problems aren't discovered during design. They're inherited from decisions made before design began.
The tools used are chosen for the situation. Some engagements need structured research. Some need a fast usability audit. Some need both, run in sequence. What doesn't change is the operating principle: if they have to think, something needs to change.
Brand Sense
Most brand problems aren't brand problems.
They're structural. Cultural. Sometimes they're a product problem wearing a brand coat. Brand Sense is a diagnostic practice that starts at ground level — inside the organisation, not at the campaign layer — and works back up to strategy.
The work uses a set of diagnostic instruments developed for this practice. The primary one is Embedded Diagnostics — a structured process that goes in close, stays long enough to see what's actually operating rather than what's being presented, and produces a clear account of where the brand stands and why. Not a survey. Not a stakeholder audit. A ground-level examination of identity, coherence, and operational reality, before anyone starts talking about what the brand should look like. Other tools work alongside it depending on what the engagement needs — gap analysis, competitive positioning, customer language mapping. The instrument is always chosen for the situation, not applied by default.
Engagement model
A defined contribution. A specific remit. Agreed upfront.
This isn't a retainer relationship and it isn't open-ended consulting. Each engagement is scoped around a clear outcome — what needs to be understood, what needs to be produced, and what a sound result looks like — before the work begins.
I sit alongside existing structures, not across from them.
Most engagements already have a team. A project manager. An account lead. A designer or developer. A UX resource. I'm not a replacement for any of them and I'm not here to reorganise how they work.
What I bring is a specific kind of early-stage diagnostic capability that most project teams aren't structured to provide — and don't need to be, because it's only needed at particular points. I come in at those points, do the work, and hand off something the rest of the team can build on.
Engagements are priced on outcomes, not hours.
The question at the start of any engagement isn't how long this will take. It's what a sound result is worth — to the project, to the business, to the decision that depends on it. That's what gets agreed. That's what gets delivered.
No hourly billing. No ambiguity about what you're paying for. A clear scope, a clear outcome, a clear price — before anything begins.
What that looks like in practice.
Every engagement starts with a conversation. Not a pitch — a diagnostic one. What's the situation, what's already known, what's been tried, where does it feel wrong. From that, a scope gets proposed. The scope names the outcome, the method, and the cost.
If it fits, we proceed. If it doesn't, you're no worse off for the conversation.
Portfolio
The work, as it actually happened.
Four practice pillars — Discovery, Analysis, UX, and Business Sense. Each case study is built as a standalone piece with its own visual treatment. Real work is anonymised. Fictional work is set in Adelaide.
Discovery
Who actually drinks here?
A third-generation Hindmarsh brewery believed they knew their customer. Six weeks of discovery work suggested otherwise — and reframed a brand modernisation project into something more interesting.
Analysis
The document that needed to be thrown out
A clinical trials digitisation project that began with an inherited requirements document, hit a structural wall mid-engagement, and had to be rebuilt from scratch — under budget pressure, with client trust on the line.
UX
Designing for people who didn't ask to be designed for
Translating clinical trial workflows into a usable digital system — for users who were expert, time-poor, and had a paper process they already trusted.
Business Sense
Holding the relationship through a difficult moment
Scoping, negotiation, and the work of keeping a client's trust when a project needs to reset. Coming soon.
Start a conversation
If something feels wrong, that's worth examining.
You don't need a fully formed brief to make contact. You don't need to have diagnosed the problem yourself — that's part of what this work is for.
If you're about to start something and want to make sure you're starting in the right place, or if you're already underway and something isn't sitting right, a conversation costs nothing and commits you to nothing.
Let's talk about what you're working on.