How to run a two-week brand sprint
A working schedule for choosing a brand direction and testing it on real materials.

A two-week brand sprint helps a team make one clear decision about how to present an offer. You might clarify who the website is for, what people should understand at a glance and how to express that visually. Start with one audience, one priority use and a person authorized to make the decision.
Choose the decision you need to make
If the brief is “redo the brand”, ask where the current brand causes a problem. Does the website try to speak to several audiences at once? Does the sales proposal use terms customers do not recognize? Do the presentation and website look as though they came from different companies? An observable problem gives you a goal you can verify.
- Choose the offer and audience the sprint will cover.
- Collect the current website, presentations, common customer questions and available assets.
- Name where the new direction will first be used, such as a service page or a proposal.
- Decide who collects feedback and who approves the direction. Book reviews before you start.
Agree what comes later. Naming, trademark checks, a full website rebuild and production of every asset may each need their own piece of work. If the team has yet to agree on the offer, settle that before investing in the visual applications.
A two-week schedule from discovery to handover
This is a proposed schedule for a team that can give feedback at agreed points. The Design Council’s Double Diamond offers a useful process reference for understanding the problem, exploring alternatives and testing solutions. Here we apply that approach to choosing a brand direction.
| When | Work | Result to verify |
|---|---|---|
| Days 1 and 2 | Gather materials, listen to the people who sell or use the offer and review how it is described today. | A short brief with the audience, problem, goal and constraints. |
| Days 3 and 4 | Draft a positioning statement and check the messaging against real customer questions. | A main message, evidence that supports it and open questions. |
| Day 5 | Show two visual directions in the same context, such as the opening of one web page. | One selected direction and an agreed reason for choosing it. |
| Days 6 to 8 | Apply the selected direction to the web page and a second format the team needs. | Prototypes people can read and try in context. |
| Days 9 and 10 | Check understanding and readability, address agreed feedback and hand over the files and instructions. | Reusable assets, an owner and the next decisions. |
Compare directions using the work they need to do
Show each direction on the same application. Use the same copy and information when you want to compare visuals alone. If the messaging changes too, write down what each test should tell you. Ask readers what they think the offer is, who it is for and what they expect to do next.
Check that the text is readable on a phone and that the design works with long copy or without a photo. Record the observations that affect the decision. An informal test can help you catch unclear messaging before producing all the assets.
Example for a company that sells maintenance
Hypothetical example. A business offers planned maintenance and one-off repairs. Customers read the service page and still ask what the agreement includes. The sprint brief focuses on the planned service and aims to help visitors understand what gets checked, how to make a request and when they will receive a quote.
The team compares two versions of the same page opening. It also tests the chosen direction on one page of a sales proposal. If readers still confuse included work with extras, clarify the messaging before extending the visual design to other formats.
What to hand over at the end
- A one-page summary of the audience, message, supporting evidence and open decisions.
- Guidance for typography, colors, imagery and approved assets.
- Editable source files and exports for the agreed formats, with relevant licensing information.
- Ready-to-use examples and a single place for the team to find the assets.
If your first application is a website, use the technical checklist for a business website as you move from prototype to publication. It covers checks such as page access, metadata and mobile presentation.
Sources
Written by

Matteo Lucrezio
Startupper | Lead Software Engineer
Book 30 minutes with Matteo
Leave your contact details, then choose a day and time for a free 30-minute initial conversation. Any technical assessment and subsequent work are agreed separately.
No suitable time or prefer to write? Email me at matteo.lucrezio@lucz.dev.