Principles
Translate the strategy into creative criteria.
→IMPRNT Identity™
Turn strategy into a distinctive operating system.
A visual and verbal identity process designed to create recognition while remaining practical across channels, teams and suppliers.
Strategic purpose
Identity converts strategic difference into a small set of recognisable, repeatable behaviours.
The goal is not universal approval. It is a system that is distinctive to the right audience, credible to the organisation and practical under real production conditions.
Governing question: Which creative rules must remain consistent for recognition to compound?
Business value
Value appears as better decisions, not more artefacts.
- Builds recognition
- Improves production consistency
- Gives teams reusable tools
Decision sequence
Each stage reduces a different uncertainty.
The diagram summarises the framework stages and their relationship. The detailed sequence and outputs are described below.Open full-size diagram
Explore
Develop and evaluate distinctive identity directions.
→Systemise
Build typography, colour, imagery, voice and layout rules.
→Prove
Test the system across priority applications.
Working sessions
Activities follow evidence and decision rights.
- 01Principles: Translate the strategy into creative criteria.
- 02Explore: Develop and evaluate distinctive identity directions.
- 03Systemise: Build typography, colour, imagery, voice and layout rules.
- 04Prove: Test the system across priority applications.
Useful outputs
Every output should support a named decision or owner.
Planning the timeline
Timing follows access, evidence and consequence.
Concept evaluation should happen before the system is expanded. Proving one direction across difficult applications is more valuable than polishing many routes.
Questions
Using IMPRNT Identity™ with discipline.
Which creative rules must remain consistent for recognition to compound?
The answer should be agreed in evidence before the framework moves into its next stage. IMPRNT Identity™ makes that decision and its assumptions visible.
How should timing be set?
Concept evaluation should happen before the system is expanded. Proving one direction across difficult applications is more valuable than polishing many routes.
Can this connect with the other IMPRNT frameworks?
Yes. The frameworks are modular, but each connection should follow a real dependency rather than an automatic sequence.
Evaluate the decision
Assess the system, not the presentation.
Use explicit creative criteria and test the direction across the hardest priority applications.