Key Takeaways — brief reading, less than 30 seconds
- Use 90 days as a sequencing model, not a fixed calendar: diagnose, then the brief, then approvals, then tools — each phase opens when the last one has landed.
- Three team-size patterns (rough starting points, not hiring rules): solo (10–20 creatives), ops + producer split (20–35), ops team with ICs (35+).
- Don’t hire into Creative Ops before the function is designed; you’ll get a senior PM doing intake triage.
- By week three the recurring time-sink patterns are obvious. Fix the upstream one first; a team can absorb a handful of changes in 90 days, not thirty.
- The brief is upstream of every other workflow. If briefs improve, reviews improve. If briefs stay broken, no downstream fix sticks.
- Pick tools last. Readiness is observable: the team can name the missing source of truth and the PM can show the time lost chasing approvals.
Glossary8 terms
- Creative Operations: The function that owns intake, routing, capacity, tooling, and metrics for a creative team. Distinct from creative production, which owns specific projects and stakeholders.
- Intake: The structured front door for new work — every request enters through one form or template instead of arriving via DMs, hallway conversations, or forwarded emails.
- Routing: The rules that send each incoming request to the right owner, channel, or approval path. Done by the tool when the team is mature; done by a human PM until then.
- Capacity: How much creative work the team can absorb in a given window, measured in person-days or projects-in-flight. Capacity is the budget side of intake.
- Throughput: How much creative work actually ships per week or per sprint. Throughput is the result you measure against capacity — the gap tells you where the workflow is leaking.
- Cycle Time: Elapsed time from brief approval to delivery. Don’t anchor on anyone else’s person-day figures — variance from your own baseline is the primary diagnostic.
- Rework Cycle: One full round of revisions on a deliverable. As an operator rule of thumb, healthy work runs 1–2 rework cycles; three or more signals a process problem, usually a broken brief.
- RACI: Responsible / Accountable / Consulted / Informed. The named-approver-per-round discipline is a lightweight RACI applied to each approval stage.
Editor's note: This is a playbook for the person who’s either been hired into a first creative-ops role or absorbed the function as part of a head-of-creative promotion. The same sequence works for both.
Most dysfunctional creative teams stay dysfunctional and still ship. Picture a 25-person team — a composite of teams this size, not one real client: the senior designer has been the unofficial PM for two years; the head of marketing escalates approvals through three different DMs. None of it works well; all of it works enough that the campaigns keep going out the door. That is what makes fixing creative ops harder than it looks — and why the wrong move on day one is to redesign the workflow. The right move is to spend the first month watching.
The creative-ops manager role is who this article is for from day 30 onward. The first 30 days are diagnosis, the next 30 the brief, the next 30 approvals — a sequence, not a fixed calendar. Each phase opens when the previous one has actually landed, not when the month turns over, and tools come last, once the team is reaching for them.
Don’t Rebuild Everything Day One#
The credit you spend in week one is hard to earn back. The team has its scars, its workarounds, its private agreements about who actually owns what. Walking in and announcing “we’re going to redesign the workflow” signals that you don’t respect what they’ve built — even when what they’ve built is broken. Earn it slowly: the credit you build by not touching anything in month one is what funds the brief change in month two and the approval change in month three.
Diagnose for a month before changing anything. Sit in on briefings. Sit in on review meetings. Watch a campaign go from intake to delivery. Note where time disappears, who’s the bottleneck, what gets escalated to whom. Don’t take notes on the team; take notes on the system. The system is the thing that’s broken; the people are the thing that’s coping.
The signals to listen for in week one: “we always have to ask twice,” “we never know which version is approved,” “the freelancer didn’t get the brief in time,” “legal came back on day six and we had to redo it.” Each complaint is a diagnostic data point. By week three the recurring patterns surface. If an issue shows up in two of three tracked projects, treat it as a top time-sink; if it doesn’t, extend diagnosis another week before you commit. The patterns that dominate are what you’ll fix in the next 60 days.
Team Structure: Who’s in the Function#
Three team-size patterns — rough starting points, not hiring rules — based on the size of the creative function the ops role supports.
- Solo Creative Ops Manager. 10–20 creatives. One person owns the function; intake, project setup, resource allocation, tooling, and metrics all sit with one role. Most common starting point. Reports to head of creative or CMO.
- Creative Ops + Creative Producer. 20–35 creatives. Ops and execution split. The ops manager owns process and tooling; the producer owns specific projects and stakeholder relationships. Reports usually go up through the same head of creative.
- Creative Ops team with multiple ICs. 35+ creatives. Head of ops with 2–4 individual contributors organized by area — one for intake/triage, one for vendor and freelance management, one for tooling and metrics, sometimes one for resource planning. Reports to a senior creative leader (VP Creative, head of marketing, COO).
The “I am the head of creative absorbing ops” pattern is common for first-time creative leads. Ops becomes a dotted-line responsibility you carry until the team grows enough for a dedicated ops hire. The playbook in this article works the same; the reader is the single accountable person for both the creative and the ops side until the team crosses the hiring threshold.
The wrong-first-hire risk: hiring into Creative Ops before the function is designed often produces a senior PM doing intake triage. The role hasn’t been scoped, the metrics haven’t been defined, the tooling decisions haven’t been made — the new hire fills the gap by doing whatever’s loudest, which usually means triage. Design the function first; hire to fill specific gaps.
Diagnose: Find the Three Biggest Time Sinks#
A few patterns will be obvious by week three: unclear briefs, contradictory feedback, missing approvals. Sometimes they’re different ones — resource allocation is broken, the brand kit is in five places, the freelancer onboarding is improvised every time. However many surface, two or three usually dominate the time sinks. The order matters. Fix the upstream one first.
Concrete diagnostic tools that work:
- Time-track a representative project end-to-end. Pick a routine campaign; have the PM log every status change with a timestamp. After three projects you’ll have cycle-time data of your own. Don’t anchor on anyone else’s person-day figures — what you’re after is direction, not benchmark parity. The variance from your own baseline is the diagnostic.
- Count rework cycles per project. Every revision round, every “can you redo it” moment. As an operator rule of thumb, healthy creative work runs 1–2 rework cycles per deliverable; three or more is usually a process problem, not a craft problem. (Agencies generally scope a fixed number of revision rounds(opens in new tab) per deliverable for the same reason.)
- Measure approval-round count vs target. What does the brief say the approval rounds should be (often two)? What’s the actual count? The gap between target and actual is the approval workflow’s broken-ness in one number.
A creative-asset audit applies here too: inventory the in-flight work, then pick the few biggest time sinks. Don’t try to fix everything — a team can absorb a handful of changes over 90 days, not thirty in a quarter.
Install the Brief Template First#
The brief is upstream of every other workflow. If briefs improve, reviews improve. If briefs stay broken, no downstream fix sticks — the approval-round count drops for one quarter and then rebounds because the underlying ambiguity that produced the rework was in the brief, not in the review.
Install a three-size brief template — full, repeat, edit — downloadable as PDF and DOCX, mirroring the recap template at the other end of the project. Don’t reinvent it; customize the field names if your team has strong opinions, but keep the structure.
Sequencing: brief template lands week 4–6. Kickoff meeting cadence (every project gets one, runs from the brief, takes 30 minutes max) lands week 6–8. Don’t combine — let the team adopt one change at a time. The pattern that works: announce the brief template at an all-hands, send the templates the same day, run the first project on the new brief by the end of the next week. Two or three projects later, the pushback usually gets more specific — fields they want renamed, sections they want cut, edge cases the template misses — which is the resistance you actually want, because it means they’re using it.
Approval Workflow Second#
Once briefs are clearer, approval becomes the visible bottleneck. The same project that took five rework cycles is now taking three; two of those three are happening in approval rather than in execution. That’s the signal that approval is the next layer to fix.
Sequence the approval intervention as three separate changes, each with its own announcement and its own absorption window:
- Named approver per round (week 8–10). Every project has a designated approver per stage. Not “the brand team” — the brand lead, by name. A lightweight RACI applied to each stage. Eliminates the “who has to say yes for this to ship?” ambiguity.
- Routing rules (week 10–12). The DAM (or the project tool) routes approvals automatically based on asset type, channel, and stakeholder list. The PM stops manually pinging approvers; the system pings them.
- Conditional rules (month 4+). Typo fixes don’t trigger full approval. Brand-color updates trigger only the brand lead. Off-channel-from-original triggers a fresh full review. Each conditional rule is a working agreement, written down, that codifies what the team has been doing informally.
The approval workflow template and the design-approval-process piece both cover the structure of this. The feedback craft inside the approval workflow is the related discipline; without good feedback, even a good approval workflow produces churn.
Tools Last#
By the time briefs and approvals are working, the tool gap names itself. The brand lead can’t find the current brand kit; the PM is still chasing approval through DMs; the senior designer is hunting through Dropbox for the partner-logo lockup. Specific, repeated, unprompted — those complaints are the signal that the tool you’d have proposed on day one is finally wanted.
The advantage of waiting: the buying decision becomes a team decision rather than an imposed one. Adoption tends to be easier when the team can name the pain itself — a useful signal is whether designers can explain what the tool replaces. Same implementation, very different adoption.
Concrete sequencing for the 90-day plan:
- Month 1. Diagnose. Sit in on meetings. Find the biggest time sinks. Don’t announce changes; build credit by listening.
- Month 2. Brief template lands. Kickoff cadence lands two weeks later. Two routine projects ship using the new brief.
- Month 3. Named approver per round lands. Routing rules a few weeks after that. Cycle time on routine projects should start dropping — look for the direction, not a target number.
- Month 4–5, if the signals show. Readiness is observable, not scheduled: the team can name the missing source of truth, designers stop asking where the approved file lives, and the PM can quantify the time lost chasing approvals. When two or three of those land, run a buyer’s evaluation cycle.
- Month 6. Tool selection and procurement. The implementation rolls out in month 7–8 with the team’s buy-in already won.
Budget conversations — when to ask, what to ask for, how to defend the line item — are the next deeper question, covered in a separate article. The 90-day plan above is what you do before the budget conversation matters; once the team is asking for the DAM, the budget conversation is much easier than it would have been on day one.
The Shape of the First 90 Days#
The thread running through all of this is sequence: diagnose before you change, fix the brief before the review, fix the review before you buy the tool. Run the steps out of order and you spend credit you can’t easily earn back. The team that follows you on day 90 is the team that watched you not redesign the workflow on day one.
By the end of month three, the artifacts on the wall are unglamorous: a brief template the team actually uses, a named approver per stage, a routing rule or two, three time-sink patterns measurably smaller than they were in week one. That’s the function. The DAM in month six is a consequence of the function, not a substitute for it.
Pick the project you’ll time-track first — the routine campaign, not the heroic one — and start logging status changes on Monday. The audit framework pairs naturally with the diagnostic month; run them together. What you’re building is the team’s appetite for the next change.
Frequently Asked Questions #
What’s the first hire into a creative ops function?
How small a team needs Creative Ops?
What tool stack should you start with?
What do you measure in month 1?
How do you know creative ops is working?
