When you need a brand — and when you don’t
Not everything needs to be a brand. Most initiatives are better served with a name.
This guidance helps protect the Lenovo brand and gives teams a clear path forward.
Quick rule:
If it doesn’t require long-term investment, shape customer preference, and have a defined identity, it’s a name.
Why this matters
Creating brands without clear intent:
- Fragments the Lenovo portfolio
- Weakens existing brands
- Confuses customers
- Creates rework (renaming, redesign, legal)
Make the right decision early to avoid rework and keep teams moving.
Brand vs. Name
A brand is more than a label. It’s a promise. A name is an identifier, not a brand on its own.
A brand:
- Drives customer choice
- Has a clear role in the portfolio
- Requires long-term investment
- Has a defined identity (logo, design, experience)
- Requires governance and approval
A name:
- Identifies a feature, program, capability, tier, or team
- Helps customers and employees navigate
- Supports an existing brand
- Uses Lenovo typography and hierarchy (no custom identity)
- Does not build standalone equity
Bottom line: Names help customers navigate. Brands drive preference.
A name should support the brand—not compete with it.
Brand decision framework
Use this to decide if something should be a brand or a name.
If you answer “no” at any step, use a name, not a brand.
Step 1:
Is it more than a description?
Does it need its own message in the market?
Is it more than just describing what it does?
Does it offer something meaningfully different from existing brands?
No: Use a name
Yes: Continue
Step 2:
Does it have a meaningful role?
Does it have a clear and necessary role in the portfolio?
Would removing it weaken Lenovo’s market presence?
Is it a long-term offering (not a campaign or launch)?
No: Use a name
Yes: Continue
Step 3:
Will we invest in it?
Are we prepared to build and manage it over time?
Does it require long-term investment and support?
Does this category typically use brands to signal differentiation?
No: Use a name
If you answer “no” to any of these, use a name.
Yes: Proceed with Brand creation
If all of the answers above are “yes”, proceed with brand creation.
What to do next
If it’s a brand:
- Engage Brand Strategy, Legal, and business teams early
- Define its role and long-term intent
- Secure approval before developing identity
- Align with corporate and subbrand standards
If it’s a name:
- Use existing naming conventions
- Keep it clear and descriptive
- Align with portfolio structure
- Submit for legal review
- Avoid creating logos, lockups, or standalone identities
If you need a name
Most initiatives don’t need a brand. They need a clear, useful name that supports the brand and helps people navigate.
What makes a good name
Good names should be:
- Clear: easy to understand
- Descriptive: explain what it is or does
- Supportive: ladder back to Lenovo or an approved subbrand
- Scalable: work across regions, channels, and future use
- Legally viable: ready for legal screening
Avoid names that are:
- Too clever or hard to understand
- Too close to an existing or protected brand
- Built around temporary trends
- Dependent on special styling or design
- Abbreviations that require explanation
Lenovo naming principles
Lenovo names are part of the corporate brand — not standalone brands — and should be presented as text only, not as logos or wordmarks.
Names can include business units, communities, employee groups, programs, podcasts, product features, services, software, solutions, technologies, and other offerings outside the subbrand portfolio.
Use a name to label and organize content, not to create branded elements.
Use our typography, spacing, and layout principles to create hierarchy and emphasis instead of custom styling.
Common mistakes to avoid
These examples highlight common misapplications. Avoid these approaches to maintain clarity, consistency, and brand recognition.
- Avoid treating a name as a branded element
- Avoid combining words or mixing multiple type styles within a single name
- Avoid adding icons, shapes, or graphic elements
- Avoid creating custom lockups or stylized treatments
- Avoid using multiple colors within names
Hierarchy and layout
Use a name to support hierarchy, not to compete with it.
Keep it visually simple so it doesn’t overpower key brand elements like the Lenovo logo or subbrand wordmarks.
Common misconceptions
These are common assumptions that lead to unnecessary brand creation and rework.
Visual ≠ Brand
- A logo does not make something a brand
- Not everything customer-facing requires its own brand
Ask: Are we solving a real brand need?
Competitive pressure
- Don’t create brands just because others do
- Differentiation matters more than naming
Ask: Does this make us meaningfully different?
Process shortcuts
- Branding too early often leads to renaming later
- Legal approval does not equal brand approval
Ask: Are we ready to invest long term?
Still unsure?
If you’re on the fence, it usually means the initiative needs a name, not a brand.
