Working With Designers & Developers
Part of the Digital Marketing Roadmap
In short
The fastest way to annoy a designer is to send a finished mock-up and say 'just make this'. Bring the problem and the goal instead, and you'll get better work back.
Bringing designers and developers a clear brief and context rather than a pre-baked solution, and understanding enough of each discipline's constraints to collaborate well without micromanaging.

Think of it like this
Talking to the mistri
When building a room, you tell the mistri 'four people will sleep here and we need a window for light'. You don't tell him where to place every brick. He knows walls, wiring and what will crack. Give designers and developers the need, and trust them with the build.
Watch it happen
Briefing a new landing page
brief: goal, audience
1/5The marketer shares the goal (webinar sign-ups), audience, key message and deadline.
The big ideas
What you need to know
Share the problem
Explain the goal and the audience. Let experts propose the solution.
Involve them early
Bring developers in at the start so tracking and tech limits shape the plan, not wreck it.
One round of consolidated feedback
Collect everyone's comments, resolve conflicts, then send one clear list.
Learn their limits
Know roughly what's quick and what's hard to build. It makes your asks realistic.
See it in code
Walk through the code
1Project: Webinar landing page, 'Excel for Freshers'2Goal: 500 sign-ups by 20 April3Audience: final-year students, mostly on mobile4Key message: Free 60-min session, certificate included5Must have: sign-up form, date and time, speaker photo6Tracking: form submit event, UTM source saved with lead7Deadline: design 5 April, live 10 April8Owner for questions: Aditi (marketing)1/3What it is, why it exists and who it's for.
A one-screen creative brief. It explains the goal and must-haves, but leaves the actual design choices to the designer.
Save yourself the pain
Common mistakes
Oops
Forwarding five people's conflicting comments straight to the designer.
Do this instead
Merge feedback, settle disagreements internally, then send one clear list.
Oops
Remembering tracking needs after the page is built.
Do this instead
Put tracking requirements in the brief so developers build it in from day one.
Your mission
Write a proper brief
Quick check
When should you tell developers about tracking requirements for a new page?
Go deeper
- 1Practice writing a creative brief that states the goal and audience, not the exact visual.
- 2Learn basic web/landing-page constraints (load time, responsive design) that affect marketing asks.
- 3Ask a designer or developer what makes a marketer easy versus difficult to work with.
More topics at this stop
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.