Taking part in the design process

This article is a skeleton — the content has to come from you

On the site this article is a placeholder. The assumption was a Speckle-based live model, but that has to be confirmed: we do not write down what we do not know for certain.

What needs answering

1. Does the client see a live model

Is there an interface where they can look at the model as work proceeds? If so: which one, what do they see, and does it need software?

If this really works, it is one of the strongest arguments for general design — worth highlighting, not burying in a paragraph.

2. How often are there discussions

Per stage? Weekly? On request? Is there a fixed point where something has to be approved before we go on?

3. What has to be approved

Which decisions do we not proceed without — and which do we make ourselves and merely report?

4. How are decisions recorded

Email, minutes, in the model? Who signs off?

5. What happens if no answer comes

Waiting for decisions is the commonest cause of delay. Is there a deadline for the client’s answer, and what follows if it is missed?

What we already know, and belongs here

Flagging the decision points is the designer’s job: we signal in advance when a decision will be needed and what it is, so there is time for it. The design programme.

The point of a common data environment is that everyone works from the same current state and change is traceable. Model-based collaboration.

The point

The skeleton is here. If the live model really works, say so — it deserves its own article, not a paragraph.