My Approach

I advocate for a methodical and precise approach to projects, one that considers the mission in context and achieves it in a clear, structured way.

Context

Context is key to understanding almost everything in life, and construction projects are no exception. Nothing happens in a vacuum. Every decision, parameter, and variable is linked, directly or indirectly, to the environment it exists in.

Is this your first project, or are you a seasoned developer? Is it a standalone effort, or just one step towards realising your larger ambitions? How much time, effort, and money do you have to commit? These kinds of questions help frame the project properly, revealing the the things that really matter to you. That’s how better decisions get made, and how you get better results.

Information

Successful projects are tied together by clear communication that is delivered appropriately and in a timely manner. Information should flow in a way that accurately conveys meaning and intent and ensures that objectives are achieved.

Drawings should speak for themselves. A planning drawing should communicate proposals with clarity and appeal. A planning statement should justify the application in plain terms. A setting-out plan should enable a builder to position a building without having to ask follow-up questions.

The method of delivering information should follow a logical flow that supports the project timeline. It should also be appropriate in both scope and scale. A simple job doesn’t need a 50-page specification, but it still needs a clear and safe plan to carry it out.

Some information might seem desirable in theory but isn't necessary in this specific context. Some things are flexible, others aren't. Knowing the difference is part of doing things well.

Mission Focussed

We start with your objectives. This defines the mission and provides a clear end state we are working toward. From there, the approach adapts: to the project, to your time, to your knowledge, and to how involved you want to be.

You might want to make every decision yourself. Or you might prefer clear, well-reasoned advice so you can make your own decisions with confidence. Or perhaps you want to delegate entirely. There is no single right way to do it, there is only the way that works for you and this project.

You don’t know what you don’t know, and figuring that out is part of the process. Identifying priorities is critical to achieving the best outcomes. In an ideal world, every project would be fast, affordable, and flawless. In reality, something always has to give. Quality and quantity take time and/or money. Saving time usually means spending more or narrowing the scope. Pushing costs down means something else has to give.

The key here is knowing what can and can’t be compromised and what these trade offs mean in real terms. This is why understanding the context is so important. It enables us to ensure expectations align with what’s actually realistic and achievable.

Roadmap

Every project has a lot of moving parts. Different trades, timelines, decisions, and dependencies. The roadmap is a tool we use to bring structure and clarity to that complexity. It breaks the project down into logical stages, modules and steps. This allows for structure whilst maintaining flexibility. It ensures the optimial sequencing of tasks, helping to avoid bottlenecks and delays, and managing risks, financial or otherwise.

The goal isn’t to overcomplicate, and the roadmap is inherently adaptable. This is where context and appropriateness come to the fore. Its scope grows with the scale and complexity of the project. For something simple, it stays light. For something ambitious, it expands to match.

The roadmap isn’t the project. It’s the bespoke tool we use to deliver the optimal outcome for the project.