Short version: Think of your brand as two parts: the customers' expectation at the core, and the surface elements that signal that expectation. Usually, it's less wasteful to get the expectation right first (through conversation and low-fi prototypes), then invest in the surface elements once the brand expectation, customer needs and business model are validated.Let's start with the big picture. Your brand will have value to your business if it gives you advantages in your customer and partner relationships, and sales/marketing channels. These advantages come from an expectation about you.
It's that expectation you need to figure out first, not the surface elements of the brand.Surface elements are signals. They can be the logo, other graphical signals like typeface and colour, or non-graphical elements like response-time, language, simplicity or wacky customer service personalities. They have value to the brand because they signal what to expect to the customer.
Crystallise those at the later stages, when you’ve got evidence that their needs are pressing and your business model will make you money. Usually this is when you’re getting ready to scale.
At this point, designing the surface elements should be straight-forward because they’re based on real customer experience, not guesses. Invest in surface elements too soon, and they’re wasted if you discover your brand’s core expectation needs to change.
For example, the Leancamp logo took 20 minutes so we could get our first landing pages in front of real customers fast. We didn’t nail our core expectation until our second event.
The Leancamp brand isn’t about pink logos, it’s about a fun, no-bullshit place to learn from other startup types. The logo and name and brand are only worth anything because we learned to set that expectation.
Once we learned this, we knew what to signal and strengthened the DIY, community feel in our graphics, copywriting and at the event itself.
If you think this is helpful, please upvote this answer on Quora.
I'm Salim Virani. I've been designing peer learning programs since 2009, and these days I'm also having fun building random stuff.
In the past, I designed peer learning programs for Oxford, UCL, Techstars, Microsoft Ventures and The Royal Academy Of Engineering. I also played a role in creating the Lean Startup methodology, and the European startup ecosystem. You can read about this here.
I’m working on a communication tool for community groups and unconferences. It focuses on autonomising focused teams rather than top-down coordination.
I’m on the Kernel Stewards team, where we help ~2,000 fellows understand the what the development of blockchains mean to humanity on anthropological scales, and how to use them altruistically and prudently.
What do you need right now? (2023)
Making sense of DAOs (2022)
An Agile starter pack for DAOs (2022)
Building ecosystems with grant programs (2021)
Safe spaces make for better learning (2021)
Choose happiness (2021)
Working 'Remote' after 10 years (2020)
Emotional Vocabulary (2020)
Project portfolios (2020)
Amperage - the inconvenient truth about energy for Africa's off-grid. (2018)
The history Of Lean Startup (2016)
Three Skinheads are running at me, and all I can think to say is, “Here Dan, hold my kebab for a sec.” (2016)
Get your loved ones off Facebook (2015)
Entrepreneurship is craft (2014)
Peter Thiel vs the science fiction masters (2013)