PERSPECTIVES / Brand Building & Renewal
A brand project brief needs clear priorities
Shared priorities keep strategy and design aligned throughout the project.
Research Notes
Shared priorities help strategy and design stay connected. This article explores the relationship between content, design and use, offering a sequence of judgments to guide project discussions.
Make goals concrete enough to discuss
Describing the direction as a brand upgrade, rejuvenation or internationalization is not enough. A brief should also specify the audience, use cases, existing problems and the change you hope to see.
Separate must-haves from explorations
Names, facts, production conditions and milestones must be clear; visual direction can leave room for exploration. Separating the two keeps reviews focused on the changes that matter.
Record decisions, not just changes
Explaining the rationale and scope behind each round of feedback reduces back-and-forth later. A shared record of decisions also gives the next design phase a clear starting point.
Bringing it into project discussions
- Direction: Can one sentence explain why customers choose you?
- System: Are relationships between group, business units, and products clear?
- Application: Can sales, digital channels, and on-site teams use the same expression?
Bring these questions to real materials and use cases, recording the current version, the rationale for changes and feedback from use. When every adjustment has a clear basis, the team can keep applying these judgments in future work.
Reader's Note
This article presents design methods and project observations written by Qingmei Future for its website. The project links below are provided for reference to existing work and application materials. The methods suggested here do not imply that all listed projects followed the same process, nor do they constitute project outcome data.
CONTINUE READING Further Reading
Find your next step, starting with the question at hand.
When you get in touch about a project, it helps to share your business context, existing materials, primary use scenarios and the problems you want to solve. We'll use this to discuss scope and how we might work together.
Communicate project requirements ↗

















