A client review loop, from both sides

The designer sends the review

Salma, the designer, opens the penthouse board. A design review is not a file emailed into the void — it is a question asked in the place the work lives.

The design package is ready: two living-area schemes, drawn and costed, waiting for the client to choose between them.

Salma opens the task to frame what she is asking. Drawings alone do not say what decision is needed.

She writes the question plainly — warm oak and brass, or pale ash — so the client knows exactly what to answer.

The client receives it

Rania opens her own board and finds the same task, with Salma’s question already on it. Nothing had to be sent to her.

Notice what she cannot do. A client’s account here is deliberately read-only: she can see the question, but she answers the studio directly rather than typing into the job.

So Salma writes the decision down on the same task, in the client’s own words. The question and its answer end up in one place.

That thread now holds the question, the answer, and the date it was given. Six months on, nobody has to remember who chose what.

The habit

The habit this loop teaches: frame the review so the client can answer in one line. A clear question gets a clear answer; a vague one gets a meeting.

What just happened

1. The designer sends the review

   Salma, the designer, opens the penthouse board. A design review is not a file emailed into the void — it is a question asked in the place the work lives.

2. The client receives it

   Rania opens her own board and finds the same task, with Salma’s question already on it. Nothing had to be sent to her.

3. The habit

   The habit this loop teaches: frame the review so the client can answer in one line. A clear question gets a clear answer; a vague one gets a meeting.

Open drawings → Opens Taskity in your own project.