We're getting an agency to design our site — apparently we need to write a brief, but I have no idea how. What should a brief include?

my first brief was way too short and revisions got delyed and on the second project I wrote a detailed brief and the agency hit the deadline. big difference.

edit: typed from phone, sorry for typos.

writing a brief is important. honestly overview+timeline+budget+deliverables are the minimum. add reference designs.

Brief Checklist: - Project overview (1-2 paragraphs) - Scope: what's included, what's excluded - Timeline: start, end dates - Budget: total price - Target audience: who will use it - Deliverables: design files, source code - Design reference: benchmark sites - Content: do you provide it or the agency? - Revision: how many revisions included - Technical: hosting, domain, domain - Acceptance: approval criteria

Brief template: 1-pager (one A4 page): [Project Overview] [Scope & Deliverables] [Timeline & Budget] [Target Audience] [Design References] [Content & Technical] [Revision Policy] Important: written, signed, copy for both sides.

The purpose of a brief: to reduce ambiguity. Good brief = fewer revisions = lower cost = faster delivery. Agencies like briefs too because the scope becomes clear.

I disagree with you on this point. When you try to change everything at once, nothing settles.

If you post the result here, it will help others too.

Yes, that's exactly how it is with how to write a brief. Taking notes for two weeks yields better results than a six-month estimate.

I went through the same thing.

Correct. The harder it is to reverse a decision, the slower you should make it.

If you have questions, write them; I'll answer as best I can.

Same here. honestly the harder it is to reverse a decision, the slower you should make it.

Hope this helps.

Same here. like when making decisions, write down the worst-case scenario too, not just the best.

In legacy systems, the most expensive thing is unknown dependencies. btw if you post the result here it will help others too.

I agree, and I'd like to emphasize that. If it's your first time, start small; scaling comes later.

Just leaving this note, it might be useful.

This approach has a cost, which isn't discussed. If scope grows, either time or budget must grow. There is no third option.

Of course, it varies if your situation is different.

This thread is archived.

Here's how it went for us. Payment schedules should be tied to project phases, not calendar dates.

Correct me if I'm wrong.

Saved. When making decisions, write down the worst-case scenario too, not just the best.

If I were you, I'd go this route.

I'll try it.

Let me speak from the other side; I'm on the supplier side. Most time waste accumulates in tasks waiting for approval.

Good luck with that.