The basis for a useful brief
A useful website brief does not begin with favourite animations. It describes the business question behind the website: who the main visitor is, what they need to understand or do, which content exists and who makes decisions.
The brief does not need to become a book. Two clear pages with concrete answers are more valuable than twenty pages of general statements.
The briefing canvas
| Area | Question | Useful example |
|---|---|---|
| Trigger | Why does the site need to change? | Our offer expanded, but the site only shows the old service |
| Audience | Who needs help first? | Operations managers at Belgian SMEs |
| Action | What is the main next step? | Request an introductory conversation |
| Evidence | Why should someone trust us? | Two cases, client quotes and eleven years of experience |
| Content | What already exists? | Service overview, photography and product documentation |
| Decision | Who gives final feedback? | One project owner after internal consultation |
Start with the change, not the sitemap
“We want a new website” is the means. The trigger may be an evolved offer, poor customer understanding, weak mobile performance or a site the team cannot maintain. Define what should be noticeably different after launch.
Only then decide which pages are required. The sitemap grows from real questions rather than a competitor’s navigation.
Choose a primary visitor
A website can serve several audiences, but every message cannot appear first. For the primary audience, describe:
- the situation bringing them to the site;
- the language they use themselves;
- what they need to know before making contact;
- the objection or risk they feel;
- a realistic next step.
This gives design and copy a direction. “Everyone” is not a usable primary audience.
Make responsibilities visible
Many website projects slow down because of missing content or unclear feedback rather than technology. Agree upfront:
- who supplies copy and imagery;
- who checks facts and legal claims;
- who consolidates feedback;
- which languages are required;
- who maintains content after launch.
Pre-start briefing check
- The trigger and desired change are concrete.
- One primary audience and action are chosen.
- Services and priorities are stated.
- Available evidence and missing content are listed.
- Features connect to a real need.
- One decision-maker or feedback process is agreed.
- Languages, responsibilities and launch requirements are clear.
What JF-ICT handles during a website project
JF-ICT uses the first conversation to test and sharpen the brief. Goals, audience and offer become a content structure, design priorities and explicit scope. Missing answers are not hidden behind visual design.
Market research, branding or full copywriting may be useful, but they are not automatic parts of every web design engagement. The proposal states who supplies which content.
Explore the SME web design process or discuss your project.