Describe the change you need to make, the people it should matter to and the evidence that will tell you the work is ready.
01 / Describe the business change
“We need a modern website” describes an impression. “Our offer has changed, but prospects still think we sell the old service” describes a problem a team can work on. Explain what is happening in the business, what currently creates confusion and what the next stage requires. Include the existing website and brand materials, even the pieces you dislike.
Separate the launch objective from the longer-term ambition. A new market entry may first need a clear offer and a credible inquiry journey. A complex customer portal can follow later. Naming those priorities makes it easier to compare proposals and protects the work from becoming a list of unrelated requests.
02 / Explain the decisions your audience makes
Describe the people who need the offer, the situation that brings them to it and the alternatives they consider. Go beyond broad labels such as “business owners.” A first-time buyer researching a category needs different information from a returning buyer comparing technical specifications. Identify the primary audience for launch and the secondary audiences that still need a path.
Gather the questions prospects already ask, the objections they raise and the evidence they need before taking action. Useful source material might include approved product details, sales questions, customer research and service documentation. If those inputs do not exist, make research a visible part of the scope rather than expecting visual design to supply the answers.
03 / Connect the promise to the page content
Draft a plain-language statement of who you help, what you provide and why it matters. It does not have to be final copy. Use it to expose vague claims and competing priorities before the team starts polishing a headline. Identify statements that need evidence, especially performance claims, qualifications or comparisons with alternatives.
Map the pages to real questions. A service page can explain the situation it fits, what is delivered, how the work proceeds and what the buyer should prepare. A guide can explore a decision in greater depth. Google’s people-first content guidance supports creating material for an intended audience with a clear purpose; adding pages solely to repeat search terms is a poor editorial brief.
Reference: Google Search Central: Creating helpful, reliable, people-first content ↗
04 / Test the identity in real applications
List the environments where the brand must work: a phone screen, proposal, product interface, social campaign, printed pack or event display. Share representative content lengths and languages. A beautiful short headline does not tell you whether the system can handle a long service name, a detailed comparison or a second language.
Ask the design team to show the identity in those applications early. Review how type, color, image direction and layout work together. Decide which patterns need reusable templates and which can be composed for a specific campaign. This turns the handover into something the future operator can use, instead of a folder of disconnected artwork.
- Priority audiences and the questions each needs answered.
- Launch pages, essential user journeys and required integrations.
- Existing assets, content owners and third-party usage rights.
- Representative copy, languages and accessibility needs.
- Approver, review stages, launch dependencies and maintenance owner.
Explore the strategy, identity and handover deliverables in Brand & Design
05 / Define what ready means
Turn general expectations into reviewable conditions. The brand handover might require editable templates and exports that work on light and dark backgrounds. The website might require a tested mobile inquiry journey, reviewed content, working redirects and an explanation of how updates are made. Specify who supplies photography, approves claims and operates the site after release.
Finally, share a realistic budget range and any fixed date, together with the reason that date matters. Invite the team to explain tradeoffs and propose stages. A useful proposal should connect the brief to deliverables, responsibilities, review points and exclusions. You can then judge whether the proposed work solves the problem you began with, and make changes while they are still easy to discuss.
About this guide
EmberGrids publishes practical guidance on brand design, digital products, applied AI and immersive experiences.
Prepared with AI assistance using the linked primary documentation. The recommendations bring those concepts into practical questions for scoping and evaluating a project.
Sources and further reading
Put the thinking to work
Bring us the question
behind your project.
We can help turn an ambition into a clear brief, a useful prototype and an agreed plan for delivery.
Discuss a project ↗