Design Process Improvement — Copy & Topics Upfront
Overview
During the [1], the team identified a recurring friction point in the design workflow: designers were receiving insufficient context upfront, requiring back-and-forth clarification and slowing delivery. A process change was adopted requiring Account Managers to provide detailed copy and topic briefs before handing off to the design team.
The Problem
The design team's workload was described as "heavy" but manageable. However, a key inefficiency was identified: AMs were passing design requests without fully prepared copy or clearly defined topics. This created downstream delays as designers either had to wait for content or make assumptions that required revision.
The team noted that this had been easier when designers had deep client familiarity (e.g., a dedicated writer who "knew these clients so well that we could just be like, here's some topics, run, write"). As team composition changes, that institutional knowledge can no longer be assumed.
The Process Change
Account Managers must provide the following before assigning design tasks:
- Finalized or near-final copy — not placeholder text or rough notes
- Specific topics — clearly defined subject matter for each piece (e.g., social post, blog graphic, email header)
- Enough context for the designer to work independently — reducing the need for follow-up questions
This applies to recurring content (social graphics, email assets) as well as one-off design requests.
Rationale
- Designers cannot produce accurate work without knowing what the content says or is about
- Waiting on copy mid-task breaks flow and inflates turnaround time
- AMs are best positioned to know client voice, campaign goals, and approved messaging — that knowledge should be transferred explicitly, not assumed
Trade-offs & Acknowledgment
The team acknowledged this adds front-loaded work for AMs:
"I know that it adds a little bit more to our, as an account manager, up front, but in the end, it's just what we have to do right now."
This is accepted as a necessary cost to keep the design pipeline moving efficiently.
Related Notes
- This issue surfaced in the context of February content tasks being queued but not yet fully briefed — see [2]
- Similar upstream-dependency issues have appeared in developer workflows (e.g., the [3] email build stalling for a month due to a missing content doc)
- The general principle — that downstream team members need complete inputs before starting work — applies across design, development, and email build workflows
See Also
- [4]
- [5]