There is a Friday afternoon ritual inside most growing creative teams. The senior designer — the one whose taste you hired for, whose judgment you pay a premium for, whose attention is the rarest resource you have — opens a deck template, drops in three screenshots, writes two paragraphs of context, and emails the result to the client.
It takes ninety minutes. It happens every week. It is invisible on the org chart. And it is, almost certainly, the most expensive ninety minutes inside the entire business.
What you are actually paying for
When a senior designer assembles a status deck, you are not paying for the deck. You are paying for the deck instead of the work the deck is supposed to be reporting on.
The math is unkind. A senior designer at $180,000 fully loaded costs about $90 an hour. Ninety minutes of deck assembly is $135 of clerical labor — every week, fifty weeks a year — almost $7,000 a year, per designer, on a task that does not require the judgment you hired for.
Multiply that by a team of six. The number is no longer rounding error.
The deeper cost is the context switch
But the dollar figure is the smaller half of the problem. The bigger half is what happens to the work itself.
Senior creative work requires long, uninterrupted blocks of attention. A study of software engineers found that recovering deep focus after an interruption takes, on average, twenty-three minutes. Designers are not different. The Friday deck does not just take ninety minutes. It takes the ninety minutes plus the unrecoverable end of the day on either side of it.
You are paying for the deck. You are also paying for the work that did not happen because of the deck.
The honest test
Ask the deck-assembler what part of the process actually requires their judgment. The answer is almost always the same: choosing which two or three things to highlight, and writing the framing sentence.
Everything else — the screenshots, the layout, the consistent template, the polite intro paragraph, the formatting of next steps — is mechanical. It is the kind of work a system can do, and a person should not be doing.
What this looks like fixed
We have built this exact system inside several agencies. The pattern is always the same. The senior designer writes one sentence — what mattered this week — into a small interface. An agent does the rest: pulls the latest renders, formats the deck, drafts the framing copy, queues it for review, and sends it on approval.
The senior designer spends three minutes instead of ninety. The deck looks better. The client gets it earlier. And the rest of Friday afternoon is real work, not the residue of clerical work.
Where the line is
This is the craft / ops line in its plainest form. The taste — the choice of what to highlight, the framing — is craft. It stays human. The assembly is operations. It goes to an agent.
The mistake most businesses make is treating the whole task as one thing. It is two things. Separating them is most of the win.
