How to Collaborate With Designers and Developers

2. Why Do Marketing Requests Stall With Designers and Developers?

Quick Answer: Because the request carries a description of the output but not the decision behind it. The designer then guesses your intent, and you review the guess instead of the work. The fix belongs upstream — in the campaign brief, not in the third round of comments.

Figma’s 2025 designer and developer research found that differences in assumptions were the most commonly cited challenge developers face when working with designers, named by 52%. If assumptions break the handoff between two people who share a file and a vocabulary, they will certainly break the handoff from marketing, which shares neither.

Watch what a typical request actually contains. “Can you make a banner for the Raya promo, something festive, by Thursday?” That sentence names an output and a date. It does not name the offer, the audience, the placement, the size, the primary message, or who approves it. Every one of those gets guessed — and each guess is a future revision round.

Three assumption gaps cause most of the damage:

• The unstated constraint. You knew the banner must fit an existing template, or the page must not need a developer. The designer did not, so the first draft breaks a rule nobody wrote down.
• The invisible approver. You approve version one. Then your manager sees it and does not. The designer has now built the wrong thing twice, for two different people.
• The missing “why”. Told only what to make, a designer optimises for looking good. Told the campaign must drive form fills from cold traffic, they optimise for the form. Same brief, completely different work.

A creative team is not slow. It is being asked to read your mind, and it is very slightly wrong every time.

3. What Must Be in the Brief Before You Send It?

Quick Answer: Six lines: the job the asset must do, the audience, the one message, the hard constraints, the named approver, and the deadline with the reason behind it. If you cannot write all six, the brief is not ready — and sending it early does not save time, it spends someone else’s. Our guide to writing a creative brief covers the long version.

Most marketing executives write briefs describing what they want to see. Strong briefs describe what the asset must achieve, then leave the “how” to the person trained in it. That single shift removes most rework, because it stops you and the designer competing over the same job.

• The job. “Get cold Facebook traffic to book a viewing.” Not “a nice hero banner.”
• The audience. Who sees this, on what device, in what mood. A KL office worker scrolling at lunch is not a homeowner comparing quotes.
• The one message. If everything is important, nothing gets emphasised. Pick the sentence that must survive a two-second glance.
• The constraints. Sizes, brand rules, what must not change, what already exists. Send the source files, not screenshots — this is where organised brand assets pay for themselves.
• The approver. One name. The person whose “yes” ends the discussion.
• The deadline and why. “Friday, because the ads go live Monday” gets treated differently from “Friday” alone.

Writing this takes fifteen minutes. Not writing it costs a week, and the week is never billed to you — it lands on the designer, which is why they eventually stop replying quickly.

4. How Many Revision Rounds Should a Marketing Asset Take?

Quick Answer: One or two, if the brief was complete. Across ZenWeb-managed creative and web requests, briefs containing all six elements averaged 1.3 revision rounds and landed in about three days. Briefs sent as a one-line chat message averaged 3.6 rounds and took nearly nine. The table below shows the full spread.

The gap between the top row and the bottom row is roughly five and a half days per asset. Run twelve assets a quarter and the incomplete brief has quietly cost you two months of calendar time — time your report to management will show as “campaign delayed” without ever naming the cause.

5. What Actually Triggers the Rework?

Quick Answer: Late approvers and changed messaging — not taste. Across tracked requests, “a new stakeholder saw it” and “the offer changed after briefing” caused far more revisions than any disagreement about the design itself. That is why a written approval workflow beats any amount of creative direction.

Read the bottom row first. Actual creative disagreement — the thing everyone argues about — causes barely one revision in ten. The top two rows are process failures wearing a creative costume, and both are inside your control before a single pixel is drawn.

6. Should You Send Requests by Chat, Email or a Ticket?

Quick Answer: One channel, and it should be the one that keeps a record. WhatsApp feels fastest and finishes slowest, because the brief is scattered across eleven messages and nobody can find the approved version. A simple board or shared tracker — the backbone of marketing project management — beats chat on every measure except the first five minutes.

Chat is not the enemy — untracked chat is. Use WhatsApp to nudge, celebrate and unblock. Put the brief, the version and the approval somewhere both of you can still find them next month, and the same habit will save you when a last-minute request lands on top of the queue.

7. How Do You Give Feedback Designers Can Act On?

Quick Answer: Describe the problem, not the solution. “The offer is not readable on a phone” gives the designer something to solve. “Make the text bigger and move it left” hands them an instruction that may or may not fix the actual issue. Our guide to giving creative feedback goes deeper on the wording.

Feedback is where a good working relationship gets spent or saved. Collect every comment, remove the duplicates, resolve the contradictions internally, then send one consolidated list. Two people sending opposite comments on the same file is the fastest way to burn a designer’s goodwill.

Three habits do most of the work:

• Name the goal that is not being met. “Cold traffic will not know what we sell” is actionable. “I don’t love it” is a mood.
• Separate must-fix from preference. Label each comment. A designer who knows which three of your eleven notes are binding will happily argue about the other eight, and usually be right.
• Give it once. One consolidated round, sent by one person, on one deadline. Feedback that trickles in over three days is three rounds pretending to be one.

8. What Do Developers Need That Designers Don’t?

Quick Answer: Edge cases and access. A designer needs to know what the page should feel like; a developer needs to know what happens when the form fails, the promo expires, or the text runs to three lines. Answer those before they ask, and you remove the two days a developer usually spends waiting for you.

Designers and developers are lumped together in most marketing conversations, but they get blocked by completely different things. Design work stalls on intent. Development work stalls on detail and permissions.

Access deserves its own sentence. Half the “developer is slow” complaints in Malaysian SMEs are really “the developer has been waiting nine days for someone to grant analytics access”. Sort the logins before the sprint, not during it — and give them your pre-launch checklist early, so the go-live date is not the first time they see it.

9. Is Marketing–Creative Collaboration Getting Better?

Quick Answer: Only for teams with a written request standard. Since 2022, teams that brief through a fixed template have steadily cut revision rounds. Teams briefing ad hoc have gone backwards, because there are simply more channels, more sizes and more approvers to disagree about. The gap keeps widening.

The tools improved for everyone. Figma reports that 84% of designers now collaborate with developers at least weekly, yet only around two-thirds of either group calls that collaboration effective. Better software does not fix an unclear request; it just delivers the wrong thing faster.

10. What Changes When the Team Is External?

Quick Answer: The cost of a vague brief becomes visible. In-house rework is absorbed silently; agency and freelance rework is billed, or it eats the hours you paid for. Working with an external web design and development team makes the same discipline mandatory rather than optional.

Everything above still applies, with three additions when the designers and developers sit outside your company:

1. Agree the revision count in writing. Two rounds included is normal. Knowing the number changes how carefully you consolidate feedback.
2. Name one contact on each side. Five people briefing one agency produces five campaigns. This is the same discipline that makes a campaign kickoff meeting work — one owner, one voice.
3. Book a standing 30 minutes. A short weekly call kills the email chain and surfaces blockers while they are still cheap, which is exactly how you get more value from your agency and from any freelancers you coordinate.

And tell them what happens after launch. A designer who knows the page must convert cold Meta traffic will make different choices from one who thinks it is a brochure — the same context that keeps marketing and sales aligned works on your creative partners too.

11. Conclusion

Quick Answer: Work with designers and developers by removing the guesswork, not by chasing harder. One complete brief, one named approver, one consolidated feedback round, on a channel that keeps a record. Do that and the same team that felt slow last quarter will start delivering in days.

You cannot make a designer draw faster or a developer type quicker. You can stop sending them work that has to be built twice. That is the entire lever, and it costs fifteen minutes per request.

If the queue is the real bottleneck — no designer, one overloaded developer, campaigns waiting on a page that never ships — that is a capacity problem, not a briefing one. ZenWeb is a Google Partner working with 500+ Malaysian businesses, handling design, build and campaigns in one team so marketing stops waiting in line.

12. Frequently Asked Questions

1. How do I work with designers and developers when I am not their manager?

Trade authority for clarity. You cannot set their priorities, but you can make your request the easiest one on their list to finish: a complete brief, one approver, one deadline with a reason, and feedback delivered once. Work that is easy to close tends to get closed first.

2. How many revision rounds are reasonable for a marketing asset?

One or two. Tracked requests with a complete brief average around 1.3 rounds, while one-line chat requests average 3.6. If you are routinely past round three, the problem is almost never the designer — it is that an approver or a copy change arrived after briefing.

3. What should I do when my boss changes the design at the last minute?

Convert the change into a trade, out loud. “We can do that — it moves the launch by three days, or it replaces the email banner. Which?” Late changes are unavoidable; unpriced late changes are what destroy timelines and goodwill.

4. Should marketing requests go through WhatsApp?

Use chat to nudge, not to brief. Requests sent through a group chat took nearly twice as long to reach approval as those logged on a shared board, mostly because the brief, the file and the approval end up scattered across dozens of messages nobody can search later.

5. What is the difference between briefing a designer and briefing a developer?

A designer needs intent: the job the asset must do, the audience, the one message. A developer needs detail and access: final copy, where the form sends leads, what happens on error, and the logins. Send the wrong one to the wrong person and both will wait on you.