It’s Tuesday morning. A packaging file for a new SKU launch sits in version 7. Brand signed off on version 5 in Slack. Legal marked up version 6 in a PDF that came back over email. Regulatory hasn’t seen version 6 yet because they were reviewing version 4 when the copy changed, and now they’re asking whether the substantiation language on the front-of-pack claim was updated. Nobody can answer with certainty. The printer needs final artwork by Friday to hit the retailer reset window.
This is what cross-functional collaboration actually looks like in consumer goods creative operations. It isn’t a philosophical problem about “breaking down silos.” It’s a specific, repeating, expensive workflow failure that plays out on every SKU, every launch, every quarter.
If you run brand, creative, or marketing operations at a consumer packaged goods company, you already know the pattern. The more interesting question is why the standard fixes (better meetings, shared drives, more Slack channels, generic project management tools) never solve it, and what a real framework for fixing it looks like.
The Real Reason Brand, Legal, and Regulatory Don’t Collaborate Well
Most articles about cross-departmental collaboration treat friction between teams as a communication problem. Add a Slack channel. Schedule a weekly sync. Publish a RACI. The assumption is that everyone wants the same thing and just needs better tools to talk about it.
In CPG creative production, this framing is wrong in a specific way. Brand, legal, and regulatory don’t have a communication problem. They have a structural one. Each group is optimizing for a different outcome, operating on a different timeline, and evaluating the work against a different standard.
Different priorities, not different personalities
Brand cares about market impact, launch date, and whether the creative reflects positioning. Their success metric is a shipped product that performs at shelf.
Legal cares about claim substantiation, IP exposure, competitor litigation risk, and defensibility. Their success metric is the absence of a lawsuit two years from now.
Regulatory cares about compliance with FDA labeling requirements, nutrition panel accuracy, allergen disclosure, and category-specific rules that vary by product type and jurisdiction. Their success metric is a product that never triggers a warning letter or a recall.
These are competing operating standards. When a brand manager pushes for launch date and legal pushes back on a claim, they are both doing their jobs correctly. The friction is a feature of the org design, not a bug in the relationship.
Different vocabularies for the same asset
The packaging file that brand calls “the hero SKU carton” is what legal calls “the primary display panel with substantiation-bearing claims” and what regulatory calls “the label subject to 21 CFR 101.” When feedback comes back marked up in three different vocabularies against three different concerns, the designer implementing changes has to translate before they can act. Translation takes time. Translation introduces errors.
Sequential dependencies pretending to be parallel work
Brand should review before legal. Legal should review before regulatory. Regulatory sign-off gates production. Under launch pressure, teams try to run these reviews in parallel to save time, and it almost always backfires. Brand changes copy after legal already reviewed it. Regulatory flags an ingredient disclosure issue that requires the designer to reflow the panel, which invalidates the brand review of the layout. The rework loop starts, and the launch date slips.
No shared source of truth for versions or comments
This is the underlying condition that makes everything else worse. When brand is reviewing in a proofing tool, legal is marking up PDFs over email, and regulatory is sending redlines in Word, there is no single artifact that represents “the current state of the asset with all outstanding feedback.” The project manager becomes a human integration layer, manually consolidating comments in a scattered shared drive and hoping nothing is missed. When something is missed, and eventually it will be, the audit trail exists only in scattered email threads.
What This Actually Costs a CPG Business
The cost of broken cross-functional collaboration between brand, legal, and regulatory isn’t abstract. It shows up on a P&L in five specific ways.
Missed retail reset windows. Category resets at major retailers happen on fixed calendars. Miss the window and the SKU either ships late (losing weeks of shelf time) or ships with rushed approvals (introducing risk). Neither outcome is recoverable in-quarter.
Rework driven by miscommunicated feedback. When feedback from three reviewers is consolidated by hand, the designer implements what the project manager understood, not necessarily what the reviewer meant. A single misinterpreted comment on a regulated claim can trigger a full round of re-review, adding days to the cycle.
Revision round inflation. Well-run CPG creative teams typically move through three to four review rounds per SKU. Teams with broken collaboration workflows often need six to eight. Each additional round costs designer hours, reviewer hours, and calendar time. Across a launch calendar of 40 SKUs, the difference is material.
Launch delays that cascade into promotional windows. A packaging delay does not stay contained. It pushes back trade marketing timing, disrupts sell-in decks, misaligns advertising flights, and forces last-minute concessions with retail partners. The direct cost of the delay is small compared to the downstream cost of everything that had to move with it.
Compliance risk from unprovable approvals. This is the quiet one. When a regulatory question surfaces post-launch (a competitor complaint, an agency inquiry, a retailer challenge on a claim), the company needs to produce documented proof that the appropriate reviewers approved the specific version that shipped. If the approval evidence lives in email threads, Slack messages, and PDFs on someone’s laptop, producing a defensible audit trail after the fact is somewhere between painful and impossible.
What Is Creative Operations Actually Supposed to Do About This?
The question of what creative operations is, applied to CPG, has a specific answer. Creative operations owns the system that turns a brand brief into a shipped, compliant asset. That means owning the intake, routing, review, approval, and reporting infrastructure that brand, legal, and regulatory all touch but none of them individually owns.
It’s distinct from marketing operations, which manages budgets, campaign performance, and MarTech infrastructure. Creative operations sits upstream of all of that. It’s the function that determines whether the work gets made correctly, on time, and with a record that proves it.
When creative operations is working, brand managers spend their time on strategy and positioning rather than chasing legal for a sign-off. Creative directors spend their time on craft rather than reconciling contradictory feedback. Regulatory reviewers see clean, complete files with clear context rather than half-finished proofs with missing substantiation notes.
When it’s broken, or when the available tools can’t support the workflow, everyone downstream absorbs the failure. Brand managers become traffic managers. Creative directors become mediators. Regulatory reviewers become quality control for problems that should have been caught upstream.
The fix isn’t more meetings. The fix is a workflow system that enforces the collaboration structure instead of asking humans to enforce it under launch pressure.
A Practical Framework for Fixing Cross-Functional Collaboration in CPG Creative Production
The following framework addresses the structural failure modes described above. It’s not a checklist. It’s a set of workflow architecture principles that need to be built into the system your team actually uses every day, rather than layered on top of it as policy.
1. Enforce the review sequence in the workflow, not in the team’s memory
The order of review matters. Brand reviews first because their feedback often changes the copy or layout that legal and regulatory are evaluating. Legal reviews second because their edits often affect substantiation language that regulatory needs to verify. Regulatory reviews last because their sign-off gates production, and rework at this stage is the most expensive.
When the sequence is enforced by policy alone (“please don’t send it to regulatory before legal finishes”), it breaks under deadline pressure. When the sequence is enforced by the workflow itself, so that files literally cannot advance to the next stage until the current stage has signed off, it holds.
Here’s what a real multi-stage review looks like in practice. Stage 1: brand approvers. Stage 2: legal approvers. Stage 3: regulatory approvers. Each stage has defined reviewers, a defined SLA, and a defined scope. Nothing advances to the next stage until the current stage completes. The project manager isn’t the enforcement mechanism. The system is.
2. Scope feedback by role so reviewers stay in their lane
One of the fastest ways to blow up a review cycle is to let every reviewer comment on everything. Brand marks up regulatory language they don’t have authority over. Legal comments on visual hierarchy. Regulatory rewrites brand copy. Now the designer has thirty comments to interpret and no clear guidance on which ones are binding.
The fix is role-scoped feedback. When a legal reviewer opens the file, they see the fields, claims, and elements within their scope of authority. When regulatory opens the same file, they see the elements within theirs. Brand sees theirs. Feedback stays contained to the domain where the reviewer has decision rights. Comments outside a reviewer’s scope get flagged for the appropriate owner rather than added to the designer’s queue as if they were binding.
This is a workflow architecture decision, not a personality management problem. Reviewers stay in their lane when the tool defines the lane clearly.
3. Lock versions so approval means something
A signed-off version isn’t a signed-off version if the file can be edited after approval without breaking the sign-off. This is the single most common failure mode in email-based and shared-drive-based review processes. Legal approves version 5. A copy change happens. The file is now version 6, but the approval record still points at “the file.” When regulatory later asks whether legal approved the current copy, no one can answer definitively.
Version locking closes this gap. When a version is submitted for review, it’s frozen. Feedback and revisions produce a new version. Approvals are tied to the specific version reviewed, not to the file in general. The audit trail records exactly which version each reviewer approved, when, and with what comments. If the copy changes after legal signs off, the workflow surfaces that the current version is no longer approved and routes it back for re-review automatically.
In regulated CPG categories, provable version control is the difference between defensibility and exposure.
4. Capture sign-off automatically at the moment it happens
The audit trail shouldn’t be assembled after the fact from email archives. It should be captured as a byproduct of the approval itself. When a regulatory reviewer clicks approve, the system records who approved, what version, at what timestamp, with what comments. That record is immutable. It isn’t a screenshot of an email. It isn’t a summary in a project status report. It’s the actual approval event, captured in the system where the work is being done.
When a regulatory question surfaces eighteen months post-launch, the answer is a query, not an archaeology project. That’s what compliance-defensible looks like in practice.
5. Plan capacity across teams, not just tasks
Most project management thinking about creative operations focuses on task management: who does what by when. That framing misses the actual bottleneck in CPG launch workflows, which is reviewer capacity, not designer capacity.
A launch calendar with forty SKUs going through three stages of review will overwhelm legal and regulatory long before it overwhelms the design team, because legal and regulatory are usually staffed as shared services across multiple business units. If marketing operations plans the launch calendar based only on design capacity, the plan will fail at the review stage. Real capacity planning for CPG creative operations looks at reviewer availability alongside designer availability. It flags when three brand teams are all trying to route SKUs through legal in the same week. It surfaces reviewer utilization the same way it surfaces designer utilization. It lets marketing operations have a real conversation with legal and regulatory about capacity, staffing, and SLA commitments, based on data rather than anecdote.
6. Give occasional reviewers a way in that doesn’t require a paid seat
The regulatory affairs specialist who reviews one SKU per quarter. The outside counsel who weighs in on new claims. The packaging engineer at the co-manufacturer. The retailer contact who has to approve a private label variant. These are all people whose sign-off matters, and whose access to the workflow determines whether the audit trail is complete.
If getting them into the system requires a paid seat, teams work around it. They email PDFs. They screenshot comments. They keep the reviewer outside the system to avoid the cost, which produces exactly the audit trail gap that the system was supposed to prevent.
Your workflow architecture needs to let occasional reviewers participate in the review, provide sign-off, and have their approval captured, without triggering a per-seat licensing conversation. This is a pricing philosophy that shapes workflow behavior, and it matters more than most CPG teams realize until they experience the alternative.
7. Standardize intake so reviews don’t fail before they start
Half the friction in downstream review comes from insufficient information at intake. When a brand manager submits a request without specifying which retailer variants are needed, which claims are new versus previously approved, which SKUs are affected, or which regulatory territory the packaging will ship to, the designer starts work with gaps. The reviewers downstream then flag those gaps, which triggers rework, which restarts the cycle.
Structured intake that captures SKU-level detail, retailer specifications, claim substantiation references, and regulatory scope at the point of request eliminates a large portion of review-stage rework. Conditional logic on the request form adapts the fields to the request type, so a new product launch intake captures different information than a promotional redesign, and both capture more than a generic project brief.
Why This Matters Most for New Product Launch Workflows
Cross-functional friction is expensive on every project. It’s catastrophic on new product launch workflows specifically.
Product launch strategy in CPG typically involves a compressed timeline (retailer reset windows are non-negotiable), a high volume of interconnected assets (primary carton, secondary packaging, POS, digital assets, sell-in materials), multiple regulatory checkpoints (nutrition panel accuracy, claim substantiation, allergen disclosure, category-specific rules), and elevated legal scrutiny (new claims mean new substantiation, new IP exposure, new competitor risk).
Every friction point that costs a day on a routine SKU refresh costs a week on a new product launch. Every review cycle that adds a round on a promotional redesign adds three rounds on a launch. The workflow architecture that determines whether launch timelines hold is the same workflow architecture that governs routine work, but launches are where the cost of getting it wrong becomes visible to the executive team.
Marketing operations leaders who want to make the case for workflow investment should measure and report on launch cycle time, not just average project time. The gap between what launches should take and what they actually take is where the business case lives. If you’re building that case internally, our guide on 5 tactics to bring your products to market faster offers additional ammunition for the conversation.
Where Generic Project Management Tools Get This Wrong
Every generic project management platform treats approval as a checkbox at the end of a task. A reviewer receives a notification, clicks approve, and the task moves to done. That model works fine for internal work that doesn’t need to survive a regulatory audit.
It doesn’t work for CPG creative production. In this environment, approval isn’t the end of the workflow. Approval is the workflow. The review sequence, the role-scoped feedback, the version locking, the automatic capture of sign-off, the enforceable stage gates: these are the architecture the work is built around, not features bolted onto a task tracker.
When a team tries to run CPG creative operations on a horizontal project management tool, marketing operations spends its energy building manual workarounds for approval workflow: parallel spreadsheets tracking who approved what version, separate proofing tools for markup, email threads capturing sign-off, shared drives holding “final” files that turn out to be not-final. Each workaround is a place where the audit trail breaks and where cross-functional collaboration silently fails. Robust reporting on cycle time and revision counts is also the first casualty; if the workflow lives in five disconnected tools, no dashboard can see the whole picture.
The alternative is a workflow platform designed around the review and approval architecture that CPG creative production actually requires, connected via integrations to the tools your team already uses for design and delivery. Not a task tracker with approval added. A system where the review sequence, the version control, the role-scoped feedback, and the audit trail are the product, and the project plan exists to serve that architecture.
That’s what purpose-built creative operations infrastructure looks like. It’s what teams at Maui Jim, Lifetime Brands, and IVC rely on to keep launch calendars on track and audit trails defensible.
Where to Start
If your team is dealing with slow, friction-heavy approval cycles across brand, legal, and regulatory, the fix isn’t a communication initiative. It’s a workflow architecture change. Three practical starting points:
- Audit your last three launches for cycle time by stage. Where is the time actually going? If most of it is sitting in review queues or rework loops, the problem is workflow, not creative capacity.
- Map your current audit trail on one recently launched SKU. Can you produce, in under an hour, the complete record of who approved which version of the packaging at what timestamp with what comments? If not, your compliance defensibility has a gap that a regulatory event will expose.
- Talk to your legal and regulatory reviewers about what they experience. They will tell you exactly where the current process is failing them, and their answers will map directly onto the framework above.
The teams that get this right treat cross-functional collaboration as an infrastructure investment, not a soft skill. They build the workflow architecture that makes brand, legal, and regulatory able to do their jobs correctly under launch pressure. And they measure the result in launch cycle time, revision round count, and the ability to answer a regulatory question with a query instead of an archaeology project.
Ready to see what a purpose-built creative operations platform looks like for CPG teams? Explore RoboHead’s Consumer Goods solution or talk to our team about how in-house creative teams at CPG companies use RoboHead to shorten launch cycle times and build defensible approval audit trails.
Frequently Asked Questions
What is cross-functional collaboration in marketing?
Cross-functional collaboration in marketing is the coordinated work between departments (brand, creative, legal, regulatory, product, and operations) that produces shipped marketing assets. In CPG specifically, it refers to the review, approval, and production workflow that a packaging file or campaign asset moves through as it passes between teams with different priorities, standards, and decision rights.
Why does packaging approval take so long in CPG?
Packaging approval takes time in CPG because each reviewing group (brand, legal, regulatory, and often production) is evaluating the asset against a different standard. Brand evaluates positioning and market impact. Legal evaluates claim substantiation and IP exposure. Regulatory evaluates compliance with labeling requirements. Without a workflow that enforces the review sequence, scopes feedback by role, and locks versions between rounds, the process expands into rework loops that add weeks to the cycle.
What is marketing operations in a CPG context?
Marketing operations in a CPG context is the function that owns the system for turning strategic marketing intent into shipped assets on time, on budget, and on compliance. It includes intake, workflow management, resource planning, review and approval routing, reporting, and the technology infrastructure that supports all of it. In CPG, marketing operations also owns the audit trail infrastructure that makes creative approvals defensible under regulatory scrutiny.
Can Asana or Monday.com handle CPG creative approvals?
Horizontal project management tools like Asana and Monday.com can handle task tracking and basic approval checkboxes. They weren’t designed for the review architecture that CPG creative operations requires: enforced multi-stage review sequences, role-scoped feedback, version locking with automatic re-review triggers, and audit trails captured at the moment of approval. Teams using horizontal tools typically end up building manual workarounds in spreadsheets and email, which is where the audit trail breaks.
What metrics should CPG marketing operations track for approval workflows?
The most useful metrics are cycle time from brief to approved asset (broken down by asset type and by review stage), average revision rounds per SKU, SLA adherence against defined review turnaround commitments, and reviewer capacity utilization by team. Together, these metrics show where the production system is breaking down and where the highest-ROI workflow investments would land.
