Working with design partners: a practical campaign collaboration process
Set up a clear working relationship between campaign owners and design partners, from the first brief through reviews, changes and final delivery.
Agree how the relationship will work
A productive design partnership depends on more than a good brief. Both sides need to understand how information will arrive, who makes decisions and what happens when the campaign changes. Discuss the working process at the start, while there is time to resolve differences. A short agreement about communication and review can prevent repeated confusion during production.
Identify the main contact on each side. The campaign owner coordinates the organisation's requirements and decisions; the design lead coordinates the creative response and production questions. Other specialists can contribute, but the two contacts should know how to route those contributions. This avoids giving the designer contradictory instructions from several people who each assume they are the sole decision maker.
Explain the organisation's context without assuming the partner already knows it. Share the intended audience, campaign objective, relevant history and any constraints that affect the work. A partner joining for the first time should not have to infer internal terminology or approval politics from scattered comments. Give them enough context to ask useful questions and make informed design choices.
Define scope in terms of outputs and decisions
Describe the agreed deliverables, variants and review stages. Include the expected formats, languages, placements and any source-file handover requirements. Distinguish concept development from adaptation and production. This helps both sides understand what the project includes and where a new request might change the amount or sequence of work.
Clarify which inputs the organisation will supply and when. These might include approved copy, logos, photographs, factual details or a production specification. The designer should know whether an asset is final, provisional or still missing. A schedule built on assumed inputs can fail even when the design work itself is progressing well.
Use the agreed scope as a working reference, not a weapon in every conversation. If a new need arises, identify it and discuss its effect openly. The aim is to make the consequences visible so the campaign owner can choose between changing time, effort or deliverables. Quietly absorbing repeated changes often produces rushed work and resentment that could have been avoided.
Establish one place for campaign context
Keep the brief, current requirements, review files and final decisions in an agreed campaign location. Messages can alert people to changes, but they should point back to the authoritative record. If the source of truth is distributed across private conversations, the partner may miss a decision even while checking the shared workspace carefully.
Organise the record so a new participant can understand the campaign. Identify the current brief, the latest review version and the unresolved questions. Avoid giving equal prominence to superseded drafts. A simple current view with accessible history is more useful than a large collection of files whose status must be reconstructed from timestamps.
Campaign Bay brings organisations, design partners, briefs, reviews and deliveries together. Use that shared context to support the working process, while still agreeing the team's practical conventions. The presence of a workspace does not automatically decide who approves artwork, how quickly people respond or which file is ready for use.
Set a communication rhythm that matches the work
Agree when updates are needed and what they should contain. A useful update explains what has changed, which decision is needed and whether a dependency threatens the next milestone. It does not need to be a long narrative of every task. The communication rhythm should help the campaign move forward without interrupting production unnecessarily.
Distinguish urgent issues from routine questions. A factual error in a file scheduled for publication may need immediate attention, while a preference about a future concept can wait for the next review. Define an appropriate route for urgent issues so neither side relies on repeatedly marking ordinary messages as high priority.
Respect review windows. The organisation should gather feedback within the agreed period, and the partner should explain when a revision will be ready. If availability changes, update the plan visibly. A missed review deadline can affect delivery just as much as a production delay, so the schedule should represent responsibilities on both sides.
- Name the main contact and decision owner.
- Agree where the current brief and files live.
- Set review windows and response expectations.
- Define how urgent issues are raised.
- Keep unresolved questions visible.
- Record changes to scope and timing.
Give the partner room to solve the problem
A brief should explain the objective and constraints without prescribing every visual choice. Designers can contribute more when they understand why the campaign exists and what success requires. Invite them to challenge unclear assumptions, identify missing information and suggest a stronger approach. A partner who only receives instructions after all decisions are fixed has less opportunity to improve the result.
When reviewing a concept, discuss how it serves the audience and message. Ask the designer to explain the reasoning behind major choices. That explanation can reveal useful tradeoffs, such as choosing a simpler composition so a call to action remains readable on a phone. Evaluate the reasoning against the brief rather than treating the review as a contest of personal taste.
Creative freedom still needs clear boundaries. Mandatory wording, approved claims and production requirements should be identified explicitly. If a constraint is negotiable, say so. If it is fixed, explain who owns it and why it matters. This keeps the designer from spending time exploring a direction that the organisation cannot use.
Consolidate feedback before sending revisions
The organisation should resolve internal disagreements before presenting a required revision list. A designer can help explore alternatives, but should not be expected to decide which stakeholder's objective takes priority. Choose one person to collect comments, identify conflicts and communicate the agreed changes with their reasons.
Make feedback specific and connected to the work. Identify the asset and version, describe the issue and state the desired outcome. Separate factual corrections from questions and optional preferences. This gives the partner a usable plan for the next revision and makes it possible to check whether the changes were addressed.
Preserve the decision history without forcing the partner to reread every message. A concise consolidated list can link to the original context. If a suggestion is rejected, record the decision so it does not reappear as an unexplained requirement in the next round. Clear feedback is one of the most practical ways an organisation can reduce unnecessary design work.
Manage changes openly
When the campaign objective, audience, message or deliverables change, update the brief and discuss the effect on the plan. Do not disguise a new direction as a minor correction. A designer may need to revisit the concept, regenerate variants or repeat reviews. Naming the change accurately helps both sides agree a realistic response.
Ask for options when the deadline cannot move. The partner may suggest reducing the number of variants, using a simpler adaptation or separating essential launch assets from later material. The campaign owner can then choose with a clear understanding of the tradeoff. A blanket instruction to keep everything while shortening the timeline does not resolve the underlying constraint.
Record the agreed adjustment in the shared campaign context. Include what changed, who decided and which milestones or outputs are affected. This creates a practical reference for everyone joining later and prevents the original scope from continuing to circulate as if nothing had changed.
Keep approvals and delivery responsibilities clear
Identify who can approve each stage and what that approval covers. Concept approval, factual review and final file approval are distinct decisions. The partner should not have to interpret a friendly comment as permission to deliver or publish. Use explicit outcomes tied to identifiable versions.
Agree who performs final technical checks and who verifies the files after handover. The designer may prepare the outputs, while the recipient checks them against a platform or printer's requirements. Clarify the boundary so a necessary check is not omitted because each side assumes the other completed it.
At handover, provide a manifest or clear deliverable list. Confirm that the package contains the agreed files, instructions and source material. If an exception remains, identify its owner and expected resolution. Closing a campaign should mean the receiving team can use the work, not simply that the partner has stopped editing it.
Review the partnership after the campaign
Hold a short retrospective focused on the process. Ask which inputs arrived late, which reviews were useful and where decisions became unclear. Look for specific changes that would improve the next campaign. A retrospective should not become an opportunity to reopen approved creative preferences or assign blame without considering the circumstances.
Use examples from the actual workflow. If three rounds were spent correcting copy that was labelled final, improve the copy approval process. If reviewers repeatedly commented on the wrong file, improve version identification. If the partner lacked important audience context, change the briefing template. Concrete observations lead to better adjustments than broad statements that communication should improve.
Keep what worked as well as what failed. A clear review owner, a useful placement matrix or a well-organised handover can become part of the next project. A strong partnership develops a shared working method without assuming that every future campaign has identical needs.
Example: a new partner joins a recurring campaign
An organisation brings a new designer into a campaign it has run several times before. Instead of sending only last year's artwork, the owner explains the current objective, what changed in the audience and which previous elements should be retained. The partner receives current brand assets, an updated deliverable list and a named review contact.
During concept review, the designer notices that the old layout gives too much space to background information. The team agrees a clearer hierarchy and records the decision before adaptations begin. Feedback is consolidated, final variants are checked and the handover includes a manifest. The partner contributes useful judgement because the process provides context and clear decisions.
Frequently asked questions
Should stakeholders contact the designer directly?
Direct discussion can be useful when the purpose and authority are clear. Required changes should still reach the consolidated campaign record so the partner does not receive conflicting instructions. Agree which questions can be resolved directly and which need the campaign owner's decision before production changes.
What if the design partner challenges the brief?
Ask them to explain the concern and how it affects the audience, message or feasibility. A challenge may reveal an important missing requirement or a stronger approach. Evaluate it openly, then record the decision. The organisation remains responsible for its objective and factual requirements, while the partner contributes design expertise.
How do we prevent endless revisions?
Provide a clear brief, settle major decisions early, consolidate feedback and identify scope changes honestly. Use explicit review stages and version-specific approvals. Revisions are not automatically a problem, but repeated rounds caused by missing context or contradictory instructions are a signal to improve the process rather than simply asking the designer to work faster.