Clients in the room

Every studio has the same email thread. The client asks where the homepage copy is up to. Somebody looks it up, writes a paragraph, and sends it. Two days later the client asks again, because something changed. The paragraph is rewritten. Nobody has done anything wrong, and yet a good part of the week is now spent translating work into prose for someone who would rather just have seen it.

The status email is not a communication problem. It is a visibility problem wearing a communication problem's clothes.

Why the client is kept outside

Ask a studio why the client cannot see the project and the answers come quickly. The tool charges per seat and the client would be a seat. The client would see the other clients. The client would see the messy middle: the task that slipped, the note that says "no idea why this is broken". The client would start moving things.

Every one of those is a real worry, and every one of them is a worry about the tool, not about the client. A client who could see only their own project, and could speak but not steer, would be a relief to have in the room. It is the tools that made that hard, and so the habit became: keep them out, and write.

What changes when they can see the plan

The first thing that changes is the question. "How is it going?" is a question you ask when you can see nothing. When the plan is in front of you, you ask something smaller and better: "is anything late on my project?" That question has a yes or a no. Most days it has a no, and a no that the client can see for themselves is a status update nobody had to write.

The second thing is the direction of the conversation. When the work is visible, the client's questions land on the work. A note on the task about the pricing section, rather than an email about the homepage in general — the same reason a question beats a report. The designer who is on that task sees the note where she is already looking, answers it there, and the answer stays with the thing it was about. The thread that used to live in four inboxes now lives in one place, and it is the right place.

The third thing is quieter. Clients who can see the plan stop asking whether there is one.

The line that makes it work

None of this survives if the client can move the plan. A client who can change a due date is a client who will, with the best intentions, on a Friday afternoon. A client who can finish a task will finish it before it is finished. The moment that is possible, the studio starts hiding things again, and the email thread comes back.

So the line is: see everything on your project, say anything about it, change nothing. Read the tasks, read the notes, open the files, follow what you care about, write your own notes. Not create work, not assign it, not move dates, not touch the project itself. And not a glimpse of anyone else's project, ever, because a studio's client list is not the client's business.

That line is not a limitation to apologise for. It is what makes letting the client in safe enough to do.

What it looks like from the client's side

Tuesday morning, the client opens their project. Seven of twelve things are done. The homepage copy is in progress, it is Sandy's, and it is due Friday. They open it and read Sandy's last note, with the draft attached and two questions about the pricing section. They answer the two questions where they sit. Sandy hears about it within the minute and the note is quoted in full.

Nobody wrote a status paragraph. Nobody forwarded a file. When the client wonders on Thursday where the copy is up to, the honest answer is that they were the last person to write on it. If they want to be told, the Monday email does it in one line, and only when there is something to say.

The price of a seat

Behind all of this is a decision about money. If a client costs the same as an employee, no studio with thirty clients will ever let them in, and the email thread is the tool's fault. The people you pay for should be the people who do the work. A client who reads and speaks is not doing the work. They are the reason it exists.

We built sjTasks on that footing: guests are free on every plan, in any number, and they see only the projects they are named on. The specifics live in the guide. This piece is about the habit worth breaking, whatever you use.

If you want one thing to try this week: pick one client, one project, and let them in. Then watch what happens to the email.

The question this answers is the client's, and it is a good one: Show me what is late on my project. When the client can see the plan, they can ask it themselves, and most days the answer is nothing.