If your design pipeline constantly backs up, it isn’t usually a sign that your team’s broken.
It’s a sign your system needs a rethink.
At Perpetual, we’ve seen every bottleneck imaginable – vague briefs, messy handoffs, endless reviews, work redone from scratch.
And we’ve spent the last two years building processes that fix those at the root.
Here are the practical tips that made the biggest difference.
1. Set the Rules at Intake – Not During the Job
Vague requests break everything downstream.
We solved this by creating one intake form to rule them all. Every job starts there. No exceptions.
What’s in the form:
- Format, channel, and audience
- Fixed vs. flexible deadlines
- CTA, tone, and reference material
- Final approver – and who’s advisory-only
Why it works:
Designers get full context up front, so work starts fast – not with a game of Slack tag.
Creative Ops
Application
As your Creative Ops become more robust, programmatic intake forms can rule out 80-90% of creative decision making – saving time, revisions, and guaranteeing brand accuracy.
2. Route the Work Based on Complexity
We used to have one general design queue. Everything sat in it. Urgent. Not urgent. Complex. Simple. All waiting.
Now? We triage requests into three flows:
- Fast Track: Tempts/templates only, minimal lift
- Creative Uplift: One Enhancer + light strategy
- Net-New Build: Full briefing, stakeholder call, scoped delivery
Why it works:
No more over-processing simple jobs or under-scoping big ones. Each job gets the flow it deserves.
Creative Ops
Application
On top of the intake form, this step is powerful for reducing time to deliver, and time spent per asset.
3. Limit Review Rounds and Own the Outcome
Creative stalls when no one owns the final say.
We set hard rules:
- One approver, identified at the start
- One review round. Two, max.
- Advisory feedback welcomed – but not directional
Why it works:
Clear decision-makers = faster approvals, less backtracking, and no design-by-committee.
Creative Ops
Application
This helps to create idealised good feedback loops for evolution over time.
4. Build for Reuse, Not Reinvention
No one should be starting from zero unless it’s intentional.
What we do:
- Every asset becomes a “base layer” (our word for templated components)
- Copy blocks and tokens live in an asset library
- All assets are tagged by use case, searchable
Why it works:
More speed. Less QA. Greater brand consistency.
Creative Ops
Application
Brand guidelines only get you so far as reference material – design systems are where true gains are made.
5. Track Time Lost, Not Just Time Spent
Most teams track effort. We track momentum. We log every pause between stages – not just the time someone’s “working.”
We track:
- Time from intake to kickoff
- Time spent in review
- % of jobs sent back for rework
- Hours where no one touched the ticket
Why it works:
This shows where we’re stalling – not just how long work takes.
Creative Ops
Application
Brand guidelines only get you so far as reference material – design systems are where true gains are made.
Wrap-Up: Flow Isn’t About Perfection. It’s About Visibility.
You don’t need perfect processes.
You need ones that reveal what’s working – and what’s not.
Once you start seeing the system clearly, fixing it becomes a whole lot easier.