Firing
Four firings in a working month — how work heats, is shaped, checked, and handed over.
Heat in the room is metaphorical: the lamp, the marked proofs, the hour when everyone reads the same page. A working month here is not a calendar of tasks but four firings, each with a temperature and a finish.
Reading the brief
First week: the brief is spread, questions written in the margin, and a short return note sent within three days. Nothing is designed until the problem is named. Marketing lead reads the note and confirms or corrects the reading. This firing ends when architecture scope is agreed in writing.
Shaping direction
Second week: references pinned, direction note drafted, first proofs sketched at reduced size. Copy and layout begin together. Review is in person or on video with printed proofs shared beforehand. This firing ends at direction sign-off.
Orchestration and production
Third week: channel pack written, files sent to production, proof ladder opens. Supervision marks colour, crop, and copy line by line. Channel owners receive format specs. This firing ends when release candidates are held at the bench.
Launch and tempering
Fourth week: internal comms sent, external sequence runs, hold points watched. After release, a short tempering note captures what shifted and what to carry forward. This firing ends with archived documents and a one-page season summary.
Weekly bench rhythm
Within each firing, the week has a fixed rhythm. Monday is reading day: no new marks, only absorption. Tuesday and Wednesday are shaping days: layouts, copy, orchestration drafts. Thursday is proof day: everything marked in pencil, nothing approved by email without a held proof. Friday is writing day: review notes sent, next week named.
That rhythm is not decorative. It prevents the drift that comes when every day is an approval day and nothing reaches a finished temperature.
Not every month contains all four firings at full depth. A shaping month may stop after Firing I. A launch-only month may begin at Firing III. The naming still helps: teams know which temperature the work should have reached before moving on.
Firing I fails when architecture is skipped because "everyone already knows the audience". We still write the note. Firing II fails when direction is approved by email without a proof on the table. We hold release. Firing III fails when channel owners invent formats mid-production. The orchestration pack exists to prevent that. Firing IV fails when internal teams learn about launch from public channels. The comms sheet exists to prevent that.
The weekly bench rhythm is non-negotiable on full commissions. Clients who need daily check-ins are directed to asynchronous mark-ups on proof days. Daily verbal approvals recreate the drift the rhythm is designed to stop.
At month end, the tempering note asks three questions: What held? What bent? What should the next month carry forward? The note is archived with the season folder. It is not marketing; it is maintenance.
Bench rhythm applies to internal studio work as well. Fridays are protected for writing; external meetings cluster Tuesday through Thursday. That internal discipline is why clients receive notes on time even when proofs ran late on Thursday night.
Glossary alignment: when client teams use different words for the same document, we pick one term in the commission letter and use it consistently in every subsequent note. Synonyms create search problems in shared drives later.
Clients sometimes ask to compress two firings into one week. We document the risk in writing when they insist: proof quality and internal comms suffer first.