Design and marketing: divide the work when AI enters production
If every visual generated by marketing comes back to design for a rebuild, the team has moved production work into corrections. Saving time requires a clear distinction between requests marketing can complete alone, those that need review and those that call for a new creative direction.
In this article
Make marketing responsible for a complete brief
A product announcement arrives with a provisional headline, an old screenshot and a benefit that still needs confirmation. A designer could begin the layout, but it would need revising. With AI, the same incomplete brief can generate several versions before anyone notices the problem.
Marketing should provide the audience, message, evidence, channel and intended action. A product representative confirms what is actually available. This preparation avoids asking the designer or model to resolve a commercial question through an image.
For an initial pilot, make these fields mandatory in a shared brief. Missing information should be visible before creation starts. You can then measure production time from a consistent starting point.
Designers also shape how production happens
Designing a system means creating components, defining their uses and documenting decisions. A designer can deliver a family of compositions and a way to adapt them alongside an individual poster or page. Exceptions deserve particular attention because they show where the shared model stops being helpful.
The Defacto case study illustrates the translation of an identity into production rules. Gladia shows how a library can serve several teams. In both cases, the library makes design decisions reusable. The team can draw on them for adaptations, while a new creative direction requires dedicated design work.
Assign decisions before assigning tools
Useful autonomy requires everyone to understand what they can decide. I recommend defining responsibilities by decision type rather than giving one person an undefined responsibility for “AI”. A small team may combine roles, but the decisions should remain identifiable.
| Decision | Suggested owner | Evidence of approval |
|---|---|---|
| Message and audience | Marketing | Approved brief |
| Product accuracy | Product representative | Source or validated wording |
| Visual rules and direction | Design | Approved library and examples |
| System updates | Named maintainer | Documented version and checks |
| Distribution | Campaign owner | Approval of the final deliverable |
Adapt this starting point to the organisation. It avoids making designers implicitly responsible for commercial claims or asking marketers to guess composition rules. It also creates a place to resolve disagreements before they become repeated corrections at the end of production.
Distinguish three types of request
Routine adaptations of an approved template can follow a lightweight path: complete fields, preview, checks and review appropriate to the risk. A new campaign needs more exploration. A new brand expression needs a design decision before it enters the shared system.
Changing an event date in a stable template is different from explaining a complex new feature. If both follow the same process, the team either slows simple tasks or underestimates unfamiliar ones. AI should help direct a request to the right workflow while leaving a clear route to human support. Classification itself should be correctable when a request has been misunderstood.
Feed corrections back into the library
An isolated correction fixes one deliverable. An understood correction can improve the system. After review, distinguish brief, content, rule, template and execution problems. The same visual symptom can have several causes: a title overflows because it is too long, the template is inappropriate or the wrapping rule is missing.
Regularly review recurring corrections. Some deserve to become shared rules; others should remain exceptions. Marketing should be able to report difficulty without independently changing the foundations. Design should be able to evolve the library without silently breaking work already in progress. Keeping the production’s rule version makes those conversations more concrete.
Measure the time returned to each team
Track the time from a complete brief to approval, then the time design spends correcting the output. Compare similar requests: changing a date and creating an original campaign require different work. Counting generated assets alone would hide that difference.
Also review recurring corrections. If marketing produces independently but a designer fixes the same hierarchy every week, the template needs updating. If the corrections concern product claims, the brief and its approval process need attention.
Start with one family of assets, assign the decisions and observe a full production cycle. Expand autonomy when marketing can finish the intended adaptations and design can spend its time on new decisions. Validate that division of work before rolling out the tool more widely.
