The terms describe different jobs
Here, brand strategy means the decisions about who the business serves, what problem it is suited to solve, which alternatives buyers compare and what detail supports the offer. Visual identity means the system of marks, colour, type, imagery and layout used to make the business recognisable and give those decisions a visible expression.
They influence one another, but they are not substitutes. A polished identity cannot settle an unclear offer. A positioning document cannot give a team usable logo files, page layouts or image direction. A useful project makes the relationship between the decisions explicit.
Start with the business decision that triggered the work
Before choosing colours or references, name the reason for commissioning the work. Is the business entering a different market, combining several services, changing its audience, outgrowing a founder-led presentation, or correcting an identity that no longer represents the offer? Different triggers lead to different briefs.
Write down what must remain stable as well as what needs to change. If existing clients recognise the business by name, service or reputation, that recognition is an asset to handle deliberately. Do not assume a complete replacement is necessary just because the current identity feels dated to the team.
Agree the strategic inputs before the design review
A designer needs more than a preference for minimal, high-end or bold. Record the audience, the task they are trying to complete, the alternatives they consider, the offer the business can support, and the supporting detail available today. Mark assumptions separately from verified facts. This prevents visual references from quietly becoming unsupported positioning claims.
The brief should also state where the identity has to work: a website, proposal, product interface, packaging, signage or social profile. A system designed only for a presentation slide may fail when reduced to a small mobile header or used by someone outside the design team.
- Audience and buying situation
- Offer and meaningful boundaries
- Alternatives buyers compare
- detail the business can show
- Applications, constraints and decision owner
Then explore an identity that can carry the decisions
Once the strategic inputs are specific enough, visual exploration can test different ways of expressing them. The question is not whether a concept looks attractive in isolation. Ask whether it is recognisable at practical sizes, appropriate to the audience, distinct from nearby competitors, adaptable across the named applications and consistent with the message the business can substantiate.
A direction can expose a strategy problem. If every concept feels generic, the issue may be that the offer or audience is still broad. Return to that decision rather than asking the designer to decorate around the uncertainty. Strategy and design therefore work in sequence, with feedback moving both ways.
A simple sequence for commissioning the work
Use short review points. First confirm the audience, offer and reason for change. Next agree the words and detail the identity must support. Then review a small number of visual directions against those requirements. Once one direction is confirmed, develop the system, test it in practical applications and prepare guidance and files for the people who will use it.
Do not approve a visual direction and only afterwards discover that it cannot support a key product, service or buyer group. Include those applications in the review. If the business has several audiences, decide which elements stay consistent and where the content or journey should differ.
Business.gov.uk offers a useful reference order: define the business, understand customers and competitors, then use that research to shape the identity. It does not prescribe a universal project method. Use the checkpoints below to control major commitments; early discovery and rough visual exploration can overlap while choices remain reversible.
| Stage | Useful decision or deliverable | review before the next commitment |
|---|---|---|
| 1. Set the direction | Reason for the work; audience and need; offer; meaningful difference; detail and assumptions; priority applications. | Confirm the problem, audience and claims the design needs to support. |
| 2. Explore visual routes | A small set of concepts or moodboards tested against the agreed direction and named applications. | Choose a route to develop, or return to an unresolved business decision. Treat concepts as hypotheses, not final artwork. |
| 3. Develop the identity | Logo, colour, typography, imagery and layout rules, developed within the confirmed scope. | Review the system against the direction and the applications that matter before preparing final assets. |
| 4. Test and approve | Examples at practical sizes and in priority contexts, with a record of gaps and revisions. | Approve production only when the identity is usable in its intended contexts and the decision owner accepts the remaining trade-offs. |
When is it reasonable to work on both at once?
Some discovery and visual exploration can overlap when the team has a plain decision owner and understands that early concepts are hypotheses. For example, a designer may create several rough directions to help stakeholders discuss whether the business should feel more technical, more approachable or more established.
Keep those exercises exploratory. Do not order final production files, rewrite every page or announce a new market position until the underlying choices are confirmed and supported. The sequence is about controlling commitment, not forcing separate departments to wait for one another.
Check the brief before approving the next stage
Before moving into final identity production, ask whether a new contributor could explain the audience, the offer, the reason for change and the detail behind the claims. Then check whether the confirmed direction works in the applications that matter and whether a team member can use it without the original designer present.
If either answer is no, identify the missing decision or application and resolve it in scope. That keeps the identity useful after launch and avoids treating strategy and design as competing deliverables.