Design brief template: how to brief designers with examples for landing pages and web projects

If your designer keeps bringing back work that looks polished but misses the point, the brief is probably the problem.

Most teams still hand over a deadline, a few stakeholder opinions, and a messy request, then wonder why round three looks like round one with better spacing. A usable design brief template fixes that. Whether the work is in-house or outsourced, design execution is only as good as the brief.

That matters most on landing page design, web design, CRO, and UX projects, where small decisions affect lead quality and conversion rate.

The quick answer

• A good design brief tells the designer what outcome matters, for whom, and under what constraints.
• The most useful design brief template includes seven things: goal, audience, message, scope, constraints, success criteria, and approvals.
• For landing page design and CRO work, the brief should define the conversion action, traffic source, audience intent, and what can or cannot change.
• The best briefs are short enough to scan, but specific enough that two designers would make similar strategic choices from the same input.

Definition: A design brief is a working document that translates a business problem into a creative assignment. It tells the designer what outcome matters, for whom, under which constraints, and how the work will be judged.

How to brief designers: template + examples?

Briefing designers well is mostly about removing strategic ambiguity. If the team has not aligned on audience, offer, and decision criteria, the designer gets stuck doing marketing strategy and execution in Figma.

A request says, “We need a new landing page by next Friday.” A brief says, “We need a landing page that increases qualified demo requests from high-intent paid traffic without hurting lead quality.”

A design brief template that is actually useful

1. Project summary

State what is being created, why it exists, and why it exists now.

• Project:
• Asset or page type:
• Requested by:
• Deadline:
• Why this project exists now:
• What changed or triggered it:

Example: New landing page for paid search traffic promoting enterprise demo requests. First draft in two weeks. Current page converts some traffic, but lead quality is poor and sales says expectations are mismatched.

2. Business goal

Define the business outcome, not the visual aspiration.

• Primary goal:
• Secondary goal:
• What happens if this succeeds:
• What happens if it fails:

“Refresh the page” is not a goal. “Increase qualified demo requests from non-branded paid search” is a goal.

3. Audience and intent

Tell the designer who the work is for and what that audience needs to decide.

• Primary audience:
• ICP or segment details:
• Awareness level:
• Traffic source:
• What they care about:
• What they are skeptical about:
• What they need to understand before converting:

“B2B buyers” is not an audience. Say whether this is for a practitioner, a marketing leader, procurement, or a mixed buying group.

4. Core message and offer

Spell out what the design has to help communicate.

• Main promise:
• Supporting points:
• Offer or CTA:
• Key objections to handle:
• Mandatory claims or language:
• Message hierarchy:

If the team has not settled the message, pull in the right content writing and design support before debating layouts.

Example: Main promise: faster landing page optimization than a traditional agency. Supporting points: better experimentation, cleaner UX, stronger conversion paths. Offer: book a strategy call. Hierarchy: outcome first, credibility second, process third.

5. Scope

Define what is included, what is excluded, and how much variation is expected.

• Included deliverables:
• Excluded deliverables:
• Number of concepts or routes:
• Responsive requirements:
• CMS or dev considerations:
• Reuse versus net-new:

If the designer thinks the team wants one page and stakeholders think they are getting a messaging overhaul, the problem is scope.

6. Constraints and non-negotiables

List the rules before the first review, not during the third.

• Brand constraints:
• Technical constraints:
• Legal or compliance constraints:
• Accessibility requirements:
• Content constraints:
• Stakeholder must-haves:
• Elements that cannot change:

Example: Use the current type system and button styles. No custom module that requires a front-end sprint. Avoid guaranteed-results language. Existing nav stays.

7. Success criteria

Define how the work will be judged before anyone says, “I just don’t love it.”

• Primary KPI:
• Secondary KPIs:
• Qualitative success criteria:
• Baseline or benchmark:
• Review criteria before launch:
• Post-launch learning plan:

For conversion work, success criteria should include both performance and pre-launch standards. If not, reviews drift into taste wars.

If you want a deeper look at CTA microcopy, form friction, and trust elements, the psychology of conversion on landing pages is a useful companion read.

8. Review and approvals

Name who reviews, who decides, and how feedback gets consolidated.

• Reviewers:
• Final approver:
• Feedback deadline:
• Feedback format:
• Approval criteria:
• What is out of bounds in review:

Example: Growth lead, content lead, and paid media manager review. Head of marketing approves. Feedback is consolidated in one doc. New strategy asks are out of scope once the brief is approved.

What should a design brief include for landing page design?

Landing page design briefs need more operational detail than brand or editorial briefs. If the page exists to support paid search, paid social, or retargeting, treat the brief as part of the broader digital advertising workflow, not a detached design request.

Include these details every time:

• Traffic source: paid search, paid social, email, partner, direct, retargeting
• Audience intent: cold research, problem-aware, vendor comparison, existing demand
• Conversion action: demo request, trial start, consultation, sign-up, download
• Offer structure: single CTA or multiple paths
• Funnel context: introducing the value prop or converting existing interest
• Current friction: weak headline, low proof, cluttered hierarchy, poor mobile form UX, message mismatch
• Testing constraints: iterating on an existing page or designing net-new
• Analytics requirements: what gets tracked, by whom, and when results will be reviewed

For page-level follow-up after the brief is done, this guide on PPC landing page optimization is a practical next layer.

What most teams get wrong

Most teams miss because they treat design like decoration instead of decision-making.

They brief the deliverable, not the problem

“We need a new page” is not a problem statement. The real issue might be weak message match, poor hierarchy, confusing CTA structure, or form friction.

They dump stakeholder opinions into the brief

A founder wanting the page to feel premium, sales asking for more proof, and paid media wanting tighter message match are not equal inputs. Some are requirements. Some are preferences.

They hide the real constraints

If legal will slow approvals, say that. If the CMS cannot support the hero idea, say that. If the brand team hates illustrations, say that too.

They use design to paper over positioning problems

Sometimes the page is not underperforming because the designer missed. Sometimes the offer, proof, or audience fit is off. This message-market fit diagnostic is useful when the real issue is upstream of layout.

They leave success vague

When nobody defines what “good” means, reviews default to taste. That is how teams spend twenty minutes debating a button color while the CTA is still doing the job of a headline.

How long should a design brief be?

Long enough to remove ambiguity. Short enough that busy people will read it.

For most web design and landing page design projects, one to two pages in working-doc form is enough. Bigger initiatives can run longer, but the rule stays the same: compress the thinking, not the context.

If your brief is six pages of background and still does not define the audience, offer, and KPI, it is not thorough.

A simple scorecard for checking your brief before design starts

The brief quality checklist

• Can someone explain the business goal in one sentence?
• Is the audience specific enough to shape hierarchy and UX choices?
• Does the brief state what action the user should take?
• Does it explain why the user might hesitate?
• Does it define what must stay fixed?
• Does it define success beyond “looks better”?
• Does it name who approves the work?
• Does it separate required inputs from stakeholder preferences?
• Does it note technical, legal, or content constraints?
• Could a new designer join the project and get oriented in ten minutes?

If you answer “no” to more than two of these, the brief is probably not ready.

Design brief examples

Example (hypothetical): B2B SaaS landing page redesign

Project summary: Redesign a paid landing page for demo requests. The current page converts, but sales reports poor fit and drop-off after the first call.
Business goal: Increase qualified demo requests without increasing junk leads.
Audience and intent: Heads of marketing and demand gen leaders at mid-market SaaS companies arriving from high-intent search.
Core message and offer: Speed to value, strategic depth, and ease of execution. CTA: Book a strategy call.
Scope: One page, desktop and mobile states, one thank-you page, light component variations, reuse of the current design system.
Constraints: Existing CMS, existing nav, conservative claims language, CRM-compatible form fields.
Success criteria: Better message match, clearer hierarchy, smoother form completion, stronger lead quality over time.
Approvals: Growth lead consolidates comments. Head of marketing approves.

Example (hypothetical): Pricing page refresh with too many stakeholders

Project summary: Refresh a pricing page to clarify packaging and reduce friction.
Business goal: Help buyers understand plan logic faster across self-serve and sales-led paths.
Audience and intent: Practitioners, team leads, finance reviewers, and procurement-involved buyers.
Non-negotiables: Pricing structure stays, legal language stays, product marketing owns naming, RevOps validates packaging logic.
Review process: Product marketing owns messaging comments, design lead owns hierarchy and UX, VP marketing is final approver.

Notice what these examples do not include: a paragraph about wanting the page to “feel modern.” That should not be driving the brief.

When should you use a template versus a live kickoff?

The template is the record. The kickoff is where ambiguity gets exposed. A simple rhythm works well:

• Brief owner drafts the template
• Core stakeholders review asynchronously
• Designer reads the brief before kickoff
• Kickoff is used to clarify tradeoffs, not dump context
• Brief gets one post-meeting revision
• Work starts after approvals, not while approvals are still wobbling

Starting design while the brief is still politically unstable is just preloaded rework.

Who should write the brief?

The first draft should usually come from the person closest to the business goal: a growth lead, demand gen lead, marketing manager, product marketer, web lead, or design lead.

The designer should improve the brief, not reconstruct it from Slack archaeology. A useful test: the brief owner should be able to answer these three questions without guessing.

• What business outcome matters?
• Who is this for?
• How will we judge whether it worked?

If nobody owns those answers, the problem is upstream of design.

What staffing and execution actually look like

Many teams do not just need a better template. They need a better operating model. This guide to the marketing operating model for in-house, agency, and fractional support is useful if the process feels messy no matter who is doing the work.

In-house team

Best when:

• You have steady design volume
• Brand and product context are complex
• Stakeholders need frequent collaboration

Typical pitfalls:

• Designers become traffic controllers instead of problem solvers
• Strategic context lives in people’s heads instead of in the brief

Agency execution

Best when:

• You need speed across design, copy, strategy, and production
• The work spans CRO, UX, paid media, and messaging
• You need outside perspective plus delivery capacity

Typical pitfalls:

• The internal team under-briefs because it assumes the agency will figure it out
• Too many reviewers create churn

Fractional or freelance support

Best when:

• You need senior thinking without full-time overhead
• The problem is strategic but not constant
• You need a specialist in landing pages, growth design, or web UX
• You want flexibility without a full agency scope

Typical pitfalls:

• Fractional talent gets used like overflow production
• There is no internal owner to consolidate feedback
• Scope expands quietly because nobody set decision rules

If you are leaning fractional, start with clean ownership and intake. This playbook on how to build a fractional marketing team around one strong internal owner applies to design and web work just as much as broader marketing execution.

If the bigger issue is access to the right skill set, not just more hours, staffing for marketing roles makes sense when the workload is real but the full-time case is still weak.

What to do next

Do not start by hunting for a prettier template. Start by reviewing your last three design projects and asking:

• Where did rework actually come from?
• Which decisions were unclear at the start?
• Which stakeholder opinions showed up late and changed direction?
• What constraints surfaced after design had already started?

Then fix the system, not just the document.

A strong design brief template works because it forces the right questions earlier: one owner, clear review rules, explicit constraints, and real success criteria. Give a good designer that operating context and the work usually gets faster, sharper, and a lot less dependent on interpretive dance during review.

FAQs‍

What is a design brief template?
A design brief template is a repeatable format for capturing the strategy, scope, constraints, and success criteria behind a design project. It keeps teams from briefing designers through scattered docs, Slack messages, and vibes.

How to brief designers: Template + examples?
Start with the business goal, audience, message, scope, constraints, success criteria, and approvals. Then pressure-test the brief with a real example, like a landing page redesign or pricing page refresh, to make sure the level of detail is actually useful.

What should a design brief include for landing page design?
A landing page design brief should include traffic source, audience intent, conversion action, current friction, offer structure, technical limits, and success criteria. Without that context, the designer has to guess what should drive hierarchy and UX decisions.

How long should a design brief be?
For most web and landing page projects, one to two pages is enough if the thinking is clear. The goal is not to write more. The goal is to remove ambiguity.

Who should write the design brief?
Usually the person closest to the business goal should draft it first, such as a growth lead, marketing manager, product marketer, or design lead. The designer should refine the brief, but should not have to invent the strategy.

What is the difference between a design request and a design brief?
A design request asks for an asset. A design brief explains the business problem, audience, constraints, and success criteria behind that asset. One creates activity. The other creates direction.

Can agencies, freelancers, and in-house designers use the same brief template?
Yes. In fact, a shared template matters more when external partners are involved because context is easier to lose. The fields may stay the same even if the workflow around approvals and ownership changes.