Publishing operations.
Running many event brands at once. The brief as an artefact, intake, review and approval, brand systems, launching an edition, and naming and rebrands.
14 articles · Publishing engine
- What an event brief template must decide before anyone designs anythingevent brief templateAn event brief template only works if five sections carry an actual decision. Here is how to score a live brief, section by section, and what to cut.
- Which creative brief sections are decisions and which are just descriptioncreative brief sectionsCreative brief sections split into two kinds: decisions that must be made fresh each edition, and descriptions that can safely be copied forward.
- A brief quality score you can apply before work startsbrief quality scoreA brief quality score built from five items, each scored zero to two, gives a portfolio a number it can compare across shows before work starts.
- Treating the brief as source of truth when decks keep contradicting itbrief as source of truthMaking the brief the source of truth means every decision has one home, and any deck that disagrees with it gets deleted the same day it is found.
- Designing a marketing request intake form that ends the side channelmarketing request intake formA marketing request intake form makes demand visible by requiring an outcome, a date and a budget owner, so capacity stops looking infinite to everyone asking.
- Creative request triage for a team running eight shows at oncecreative request triageCreative request triage on three axes: reversibility, edition date, and whether the request needs a new decision or reuses one that is already approved.
- Intake queue prioritization when every show director says theirs is firstintake queue prioritizationIntake queue prioritization by cost of delay divided by effort, with the edition date as a hard constraint, published so the argument happens once.
- Prefilled form fields make people agree to things they never readprefilled form fieldsPrefilled form fields get accepted because accepting takes no action. On an event brief that turns last year's decisions into this year's approved answers.
- Rolling over event briefs is how last year becomes this year silentlyrolling over event briefsRolling over event briefs copies last year's answers and marks nothing as copied, so an unreviewed section reads as confirmed. Ship roll overs as unconfirmed.
- Brief field provenance and why every answer needs an author and a datebrief field provenanceBrief field provenance stores who wrote each answer, when, and whether it was typed, inherited or generated, then shows it beside the value during review.
- Automation bias in approvals and why reviewers rubber stamp generated textautomation bias in approvalsAutomation bias in approvals is measurable. Compare the edit rate on generated brief sections against typed ones, then make reviewers attest field by field.
- Section status definitions that stop draft and in review meaning the same thingsection status definitionsSection status definitions work only as a state machine: six states, a named actor per transition, and evidence each transition must carry before it fires.
- A definition of done checklist for each section of an event briefdefinition of done checklistA definition of done checklist gives each brief section three to five objective items, so approved stops being a mood and becomes a claim you can check.
- Percent complete reporting lies about briefs and here is the arithmeticpercent complete reportingPercent complete reporting hides the one fact that matters about a brief: the arithmetic that turns ninety per cent into a zero, and what to report instead.