Chapter 23: Brand, Design, and Craft

You are a product leader at a technology firm that has reached a plateau. Your product is functional. Your metrics are stable. Your customer support tickets are manageable. Yet your brand feels invisible. You have a name that describes what you do but fails to inspire. Your designs are clean but lack the magic that turns users into fanatics. You notice that your competitors are winning with inferior technology because they have captured the imagination of the market. You feel the tension between the logic of your engineering and the emotion of your brand. You face a choice between remaining a utilitarian tool or becoming a cultural icon. You realize that your brand is the aggregated sum total of every human experience with your company. You must decide whether to continue building features or to master the craft of brand and design. If you do not learn to design for emotion and intent you will remain a commodity. You face a world where the best product does not always win. The product that wins is the one that solves a sharp problem and makes the user feel something profound. You must either achieve excellence in craft or watch your company fade into the noise of the marketplace.

CORE SKILL OR PRINCIPLE

The core principle of advanced product building is that brand and design are strategic moats rather than aesthetic layers. You must stop viewing your brand as a logo or a color palette. Your brand is an experience and a promise to your customer. Success in this era requires you to transition from a focus on incremental better to a focus on exponential different. You must move from being a manager of output to being a steward of quality and craft. This requires you to internalize that you cannot delegate understanding. You must be in the details of every pixel and every word to ensure they align with your mission. To build a legendary business you must get product, company, and category right at the same time. This requires a disciplined process for naming, a commitment to small high-agency teams, and a moral obligation to solve human problems with intentionality. You must embrace polarization because if your team is comfortable with a decision you likely have not found the right answer yet. Your goal is to create a love mark that users are committed to and invested in for the long term.

EVIDENCE FROM THE CONVERSATION

Evidence from Lexicon Branding shows that naming is a science of linguistics and cognitive science. David Placek observes that humans only pay attention to what is new or different. He notes that a great name provides a symmetric advantage from the start. His team found that the sound of the letter V is the most alive and vibrant in the English alphabet. Conversely the letter B sends a signal of reliability and stability. Placek argues that you will not know a great name when you see it because humans naturally seek comfort in the familiar. Successful names like Pentium and Blackberry initially made clients uncomfortable because they were distinctive rather than descriptive.

Brian Chesky at Airbnb argues that leaders must be subject matter experts who stay in the details of the product. He believes that growing slowly and keeping teams as small as possible is the only way to maintain quality. Chesky advocates for a functional structure where engineering and design report directly to the founder or a product led leader. He suggests that five teams should do one thing rather than one team doing five things. This focus ensures that the vision is executed with high fidelity across every user journey.

Rory Sutherland observes that having a great brand allows you to play the game of capitalism on easy mode. He notes that fame fundamentally changes the rules of business in non-linear ways. Famous companies attract talent for less money and receive the benefit of the doubt from customers. Sutherland identifies that small teams of around ten people are more effective because they create debts of obligation and reciprocation between teammates. This designs for human psychology rather than just for an org chart.

Christian Idiodi at the Silicon Valley Product Group defines the product manager's job as solving problems on behalf of others. He argues that this is a team sport where the PM manages value and viability risks. Idiodi notes that the PM is the one people blame when things go wrong because they are held accountable for results. He believes there is no greater discipline than solving a problem so well that the customer gives you a certificate of appreciation in the form of revenue or loyalty.

PRACTICAL BREAKDOWN

THE THREE STEP PROCESS FOR BILLION DOLLAR BRAND NAMES

You must follow a three-step process to find a winning brand name: identify, invent, and implement.

The identification phase focuses on behavior and experience. You must ask how your company behaves now and how it wants to behave in the future. This behavior is bidirectional. You must consider how the marketplace behaves toward you and how you behave toward the marketplace. You must also develop a landscape of the competition to identify the language and names currently used in your space. Distinction is the goal. Imitation is failure.

The invention phase requires you to open the coffers of creativity by using multiple teams. You should assign three distinct teams with three different briefings. The first team receives the full and real project brief. The second team is given a disguised brief. For example if you are working for Microsoft tell the team they are working for Apple. The third team is taken out of the technology context entirely. Ask them to name a bicycle or a car instead of an IDE or a SaaS platform. This removes the constraints of the category and allows the teams to make creative mistakes that lead to breakthroughs. Use linguistics and cognitive science to evaluate the signals sent by every letter in a proposed name.

The implementation phase involves helping stakeholders visualize the lift a name can provide. You must create prototypes of the brand. Put the name on a baseball cap or a T-shirt. Create mock-up ads in respected publications that show the company's stock gaining value because of the new product. This helps executives see the name as a future experience rather than just a word in a spreadsheet.

WHY POLARIZING OPINIONS SIGNAL THE RIGHT NAME

You must seek polarization during the naming process. If your team is comfortable with a name it is likely because the name is descriptive or fits existing successful patterns. Comfortable names do not stand out in a crowded market. Polarization is a sign of strength in a word. It indicates that the name is pushing boundaries and creating a new distinction in value. You should look for names that cause tension and debate. A name that everyone merely likes is a name that the market will eventually ignore.

THE DIAMOND FRAMEWORK FOR NAMING

You must use the diamond framework to define your naming objectives. Draw a diamond shape on a piece of paper.

At the top of the diamond write the word Win. Define exactly how you define winning for your company. Be specific. Do not just say you want to be successful.

On the right-hand corner write what you have to win. List the things you are currently doing that make you a winner.

At the bottom of the diamond write what you need to win. This includes the resources, talent, and technical capabilities required to achieve your definition of winning.

On the left-hand angle write what you have to say to win. This identifies the message and the experience you must communicate to the market. This framework ensures that your name is aligned with your strategy and your must-have capabilities.

HOW EVERY LETTER CREATES PSYCHOLOGICAL VIBRATION

You must recognize that letters and sounds send subconscious signals to the brain. This is sound symbolism. The letter V is the most vibrant and alive sound in the English alphabet. It evokes roar and speed as seen in names like Corvette or Viagra. The letter B is one of the most reliable sounds. It signals stability and was a core rationale for the name Blackberry. You must choose letters that match the vibration of the experience you are building.

THE BEATLES PRINCIPLE FOR TEAM SIZE AND QUALITY

You must keep your teams small to maintain a high quality bar and a sense of obligation. The ideal team size is around ten people, similar to a sports team. In these small groups individuals feel a debt of obligation to their teammates. If one person fails the others must work harder. This natural human instinct for reciprocation drives performance and prevents the anonymity of large organizations. You should aim to have five teams doing one thing rather than one team doing five things. This ensures that everyone is focused on a shared vision and a high standard of craft.

DESIGN TENETS VS PRINCIPLES

You must distinguish between design tenets and operating principles.

Design tenets are context-specific and philosophical. They represent the heavy lifting of design by defining what the company is trying to achieve at a fundamental level. Tenets should be opinionated. They define what is in and what is out for a specific product or feature. You can identify potential tenets by paying attention to the debates that your team has over and over again. If a team is bifurcated into two camps you need a tenet to resolve the alignment.

Operating principles are broader organizational standards that apply to every function. An example is meticulous craft. This principle expects meticulous care from everyone, whether they are designing an API, building a user interface, or answering a support call. Principles provide the alignment underneath role-specific expectations.

THE MORAL OBLIGATION TO BUILD GREAT PRODUCTS

You must view product building as a moral obligation to the user. The real essence of the job is waking up on behalf of someone else to solve their problem. This requires a maniacal focus on making customers love you fanatically. You must bias every decision in favor of the customer's experience. Quality is not a choice between business goals and design goals. Quality is growth. By making a product easier to use and more understandable you drive activations and revenue. You have a responsibility to not build things that produce no value. You must bring intentionality to every decision by asking who is impacted and how they are using the thing you are building.

SKILL APPLICATION

Apply the three-step naming process to your next product or feature launch. Do not rely on a single brainstorming session with your core team. Assign multiple teams and use disguised briefs to find the most creative and distinctive options.

Use the diamond framework during your next strategy off-site. Force your leadership team to define winning and identify the specific experience you must communicate to the market. Ensure your resulting name and positioning reflect these choices.

Implement a walk the store ritual for your leadership triad. Select fifteen of your most critical user journeys. Every week experience these journeys exactly as a new user would, starting from an internet search. Write a friction log of every moment that feels slow, confusing, or janky. Use this visceral data to set and maintain your quality bar.

Establish design tenets for your team by auditing your most recent contentious meetings. Identify the recurring arguments and write a tenet that provides a clear opinion on the direction the company will take. Share these tenets with new hires to ensure organizational alignment from day one.

Operationalize meticulous craft by adding it to your ladder system and performance rubrics. Judge impact not just by business metrics but by the degree to which an individual improved the usability and desirability of the product.

Practice the conductor game before important presentations to raise your energy and tap into conviction. Recognize that your energy leads your emotions and your words will follow. This reduces the cognitive load of self-evaluation and allows you to communicate your vision with more power.

ACTION CHECKLIST

• Draw a naming diamond for your current project and define winning in one sentence.
• List the three things your product is not for to create a guardrail for your team.
• Schedule a walk the store session for your primary user journey this week.
• Identify one letter in your brand name and research its sound symbolism and vibration.
• Write down the one debate your team has every month and draft a tenet to resolve it.
• Audit your team structure and identify any pod with more than twelve people.
• Create a friction log for your own onboarding experience on a mobile device today.
• Replace the word great in your next product spec with a specific number or outcome.
• Ask one customer who loves your product fanatically why they would tell a friend about it.
• Review your recent design files and identify any three-pixel misalignments.
• Draft a personal README that describes your standards for craft and quality.
• Conduct a silent read of your next strategy document followed by a sentiment vote.
• Identify a high conviction low consensus bet and write down the evidence for your belief.
• Set a deadline trap for your next feature and commit to cutting scope to meet it.
• Ask your lead engineer which part of the code base is the most technically elegant but provides the least user value.
• Practice a six-second silence after asking a hard question in your next one-on-one.
• List three things you can ask for in a negotiation in exchange for a price discount.
• Write a one-page strategic plan that fits on a single mobile screen without scrolling.
• Identify one "side quest" in your current roadmap and remove it to focus on your North Star.
• Commit to dogfooding your own product for two hours this week.
• Schedule a demo Friday where your team must show working code instead of slide decks.