Most founders who haven't worked closely with designers before approach a brief one of two ways: they either over-specify — coming in with mockups, exact colors, and pixel-level opinions — or they under-specify, handing over a vague mandate and hoping the agency figures it out. Neither works well. Here's what a great brief actually looks like.

Start with the problem, not the solution

The most common briefing mistake is describing what you want built instead of what problem you're trying to solve. "We need a redesigned dashboard" is a solution. "Our power users can't find the data they need quickly enough, and it's causing churn" is a problem. The second brief gives a design team something real to work with. The first just gives them a scope of work.

Be specific about your users

You don't need a formal persona document. You need to be able to describe your most important user in concrete terms. What's their job title? What do they care about? What are they doing before and after they use your product? What frustrates them? The more specific you can be, the better the design output will be.

Share what's not working — with evidence

If you have data — drop-off rates, support tickets, session recordings, NPS comments — share it. If you don't have formal data, share anecdotes. "Three enterprise clients told us they couldn't find the reporting tab in their first week" is useful signal. Design agencies are good at pattern-matching from messy inputs. Give them the raw material.

Define what success looks like

A good brief includes a definition of done. Not "it looks better" — something measurable. Activation rate improves. Sales demo feedback changes. Support tickets about X decrease. This gives the design team a north star and gives you a way to evaluate the work objectively.

Be honest about constraints

Timeline, budget, technical limitations, internal stakeholders who need to approve things — put it all in the brief. Agencies work better when they know the real constraints upfront. Surprises mid-engagement slow everything down.

What you don't need to include

You don't need to know what it should look like. You don't need to have design opinions. You don't need to have all the answers. A good design agency will ask the right questions to fill in the gaps — but only if you give them something solid to start from.

The bottom line

The best design briefs are honest, specific, and focused on outcomes rather than outputs. If you can describe your users, your problem, and what success looks like, ReadySet Design can take it from there.