Getting started
Where I would start with planning a realistic design programme
Allow time for the decisions that shape the work.
Why I would build a design programme around information, feedback and decisions rather than choosing a finish date in isolation.
A design programme is easier to understand when you know what each stage depends on. A date on a calendar cannot tell you whether the site information is ready, whether the brief is settled or whether an important decision still needs discussion.
Key points
- Explain the reason behind important dates.
- Ask what each stage depends on.
- Allow realistic time to understand and review decisions.
Begin with the dates that are genuinely fixed
Separate a preferred date from an immovable commitment. A school term, the end of a lease or a planned move may affect the project differently. Tell the team what is behind the timing so it can be considered honestly.
- Which dates are fixed, and why?
- Which dates are preferences?
- What flexibility do you have if information changes?
Look for dependencies
A useful programme shows what must happen before another task can move forward. Some work can progress together, while other decisions need reliable information first.
Ask your designer to explain the main dependencies in plain language. It helps you understand why an unanswered question can affect more than one drawing.
- Site information the team needs.
- Consultant input that affects the design.
- Client decisions that unlock the next stage.
- External processes the design team does not control.
Use these stages as a basis for asking which decisions and information the team needs next.
Explore the stages of a Modal Architecture projectMake space for your own review time
If you need a weekend to look at plans together, include that in the discussion. Quick feedback is only useful when you have had time to understand the information.
It can help to agree a small number of focused reviews with clear questions, rather than letting feedback arrive in fragments.
Treat the programme as a shared working tool
I would revisit the programme when the scope changes or new information appears. The purpose is to make the next steps visible and realistic, not to defend an outdated version of the plan.
Ask what is needed from you next and what that decision allows the team to do. That is often more useful than asking only when everything will be finished.
Read the published feedback as another perspective on the working relationship, rather than a promise about your programme.
Read client and consultant feedbackBring the question to your own project.
If this has helped you identify something you would like to explore, let’s talk about it.
Start a consultation