You don't need to have your project figured out before talking to an architect. In fact, helping determine what the project should be can be one of the most valuable parts of an architect's work.
What matters is that definition happens before design — not accidentally through design.
Before plans begin taking shape, several fundamental conditions should be understood well enough to guide what comes next: what the project needs to accomplish, the investment available to realize it, the property and its constraints, timing, and how the project will ultimately be delivered.
Those aren't answers an owner needs to arrive with. They're questions the project needs to answer before design commits to a solution.
Begin with definition, then design
There's a meaningful difference between engaging an architect to help define a project and engaging one to begin designing it. Some architects start designing almost immediately — which feels like progress, and often produces appealing early sketches. But if the project hasn't been defined, those sketches are answering a question no one has fully asked yet.
Five things to define before design
What the project needs to accomplish — and why now
Not the particular solution you've been picturing, but the underlying needs, objectives and circumstances prompting the project — including who the place is for and how it needs to perform.
The total project investment
What you're prepared to invest overall — not merely what can be spent on construction. Professional services, investigations, approvals, contingency and other project costs need to be understood before an appropriate construction budget can be established.
Timing
When the place needs to be ready, what is driving that date, and how flexible it actually is. Timing can affect approvals, procurement, phasing and delivery strategy.
The property
Whether you own it, are considering purchasing it or haven't identified it yet — and what is known about its opportunities and constraints, including zoning and other regulatory conditions. Sometimes defining the property comes before defining the building.
How the project will be delivered
Who needs to participate, when construction knowledge should enter the process, and whether architecture and construction will remain separate or be integrated.
The goal isn't to begin with all the answers. It's to understand which questions the project depends on.
What to ask an architect before design begins
A good architect will welcome these questions, because they're really questions about how the project will be structured:
- How do you begin a project — with design, or with understanding what the project needs to accomplish?
- When does cost enter the conversation, and how is it tested as the design develops?
- How are zoning, existing conditions and approvals considered before design is committed to a direction?
- Who is responsible for the project from design through construction, and how does that continuity work?
- What will I have in hand at the end of the first phase?
Definition can be the first reason to engage an architect
Definition isn't work that needs to be completed before engaging an architect. It can be the first reason to engage one. The distinction is whether the engagement begins by defining the project or by immediately designing a solution.
When definition comes first, design begins with a clearer understanding of the people, place, investment, constraints, timing and delivery conditions it needs to respond to. That's when drawing becomes useful — because the project has finally established the questions the architecture needs to answer.