The Decide, Design, Deliver framework in three panels: a flooded road, a coastal house and timber roof framing.

How I work: Decide, Design, Deliver

I’ve been an architect for over 30 years and Ruth Newman Architect has been a practice for 20. In that time, I’ve watched a lot of projects succeed and a lot fail. The pattern that separated them was always the same. The projects that worked got the front-end decisions right before anything was drawn. The projects that struggled started drawing too early.

That pattern is now the way I work and I’ve called it Decide, Design, Deliver. This is a short explanation of what the three phases are, why I’ve named them, and what changes for clients who engage me from here on.

Why I’ve named the way I work

Most architects don’t separate decision-making from design. The two get blurred together at the start of a project, often by the time the client is paying for a concept. Decisions that should have been tested in their own right get baked into a drawing before anyone notices they hadn’t been tested at all.

This is how budgets blow out before construction begins. It’s how approvals stall after the design is locked in. It’s how clients end up with a beautiful concept that doesn’t survive contact with reality. The fix isn’t better design. It’s separating the decisions from the design and doing them in the right order.

That’s what Decide, Design, Deliver does. I’ve named the way I work so clients know exactly which phase they’re in and what they’re paying for. My design fees were always staged: sketch design, developed design, and the design work to finalise approval documents. What’s new isn’t the staging. It’s pulling the front-end judgement out of design and naming it as its own phase, before any design begins.

Each phase now has its own purpose, its own deliverable, and its own price.

Decide

The front-end judgement phase. Before any design is committed to. In Decide, I answer the questions that determine whether a project should proceed and how. Is the brief viable against the budget? Does the site support what’s being proposed? What does council actually require? Where are the risks? What needs to change before this becomes a design?

What Decide looks like depends on the project. For some clients, it’s a Research Project. For clients ready to move at pace, it’s a VIP Design Day, a full focus day that can be used for master planning a school, scoping a retail rollout, pressure-testing a commercial fit-out brief, or working through a residential design problem in depth.

For commercial fit-outs, Decide is what I’d do before a lease is signed, not after. For schools, it’s master planning and capital works scoping that runs across months, not weeks. For retail rollouts, it’s program scoping done once at the front, not per site. Decide is where I add the most value.

Design

The architectural design phase. Once Decide has confirmed the project is viable and how it will proceed. Design now happens against a tested brief, a real budget, and a known approval pathway.

The drawings produced are the resolution of decisions that were tested upstream. When Decide has been done, Design is faster, cleaner, and more accurate. The design holds against scrutiny because the assumptions underneath it have already been tested. There are fewer revisions because the brief isn’t shifting.

The client knows what they’re seeing because they were involved in the decisions that shaped it. When Decide hasn’t been done, Design becomes a discovery process. Every drawing surfaces a question that should have been answered weeks earlier. This is where most of the lost time and money in architecture lives.

Deliver

The documentation, approvals, and construction phase. The clarity established in Decide is carried through to handover.

Deliver involves the production of technical documentation, management of approvals (DA, CC, CDC), coordination of consultants, and the tender process. Ideally it includes administration of the contract through construction, and overseeing site delivery to practical completion. Deliver is where the project becomes real, and it’s where contract administration earns its place.

When an architect administers the contract, they read the builder’s claims against the drawings, hold quality to the standard the rest of the project was held to, and keep the client clear on where things stand. Decide, Design, Deliver only works if the clarity from Decide is held all the way through. That continuity is the deliverable.

For homeowners, Deliver means attendance at site inspections, coordinating the contract, and holding the work to the standard the rest of the project was held to.

For commercial fit-outs, Deliver means the program lands on opening date because everything upstream was tested. For schools, Deliver means staged construction that respects term breaks and a board that knows where the project is at every step. For retail rollouts, Deliver means documentation that scales across sites and jurisdictions.

What this means for you

If you’re already working with me, nothing about your project changes. Decide, Design, Deliver names what I’ve always done.

If you’re considering working with me, the difference is that the judgement phase is now named and priced on its own, before design starts. You’ll know exactly what you’re engaging me for and when. Each phase has its own purpose, its own deliverable, and its own price.

This is deliberate. The structure is how I filter for clients who want to be led properly, not managed.

If you’re at the start of a project and not sure whether it’s ready for Design, you’re probably in Decide. A clarity call or a site visit is the simplest way to find out. A Research Project is the proper engagement if you’re ready to test the project properly. That’s how I work. That’s what changes from here.

by Ruth Newman

Why do architect-designed projects blow their budget?

Usually because the decisions that drive cost get made inside the design rather than before it. When a brief, a budget, and a site haven’t been tested against each other first, the design starts carrying assumptions nobody checked. By the time those assumptions surface, they’re already drawn, and changing them is expensive. The fix isn’t better design. It’s testing the big decisions before any design begins.

Should I pay an architect before any design starts?

If you’re at the start of a project, yes, and here’s why. The most expensive mistakes in a build are made before anything is drawn: a brief that doesn’t stack up against the budget, a site that won’t support the plan, an approval pathway nobody checked. Paying for judgement at this point is far cheaper than discovering the problem once it’s designed, or worse, once it’s built