Skip to main content

Inward versus Outward Branding

With exposure to some of the traditional branding companies, I've noticed a problem with inward branding.

When you decide on a strategy to shape your company's image, you want the image to be one that resonates in the marketplace and ultimately yields profits. But what should your image be? How do you go about deciding what the image should be?

Some market strategy companies work with the management of the company to align the company's image with the management's personality. I recently interacted with a market strategy company on branding and found that they did a good job facilitating a dialog with the founders of the company. The founders enjoyed talking about themselves and envisioning the company's image reflecting their personalities.

Yet the bottom line is what will resonate with customers. If your strategists focus mostly on the company, rather than on the customers, you are dealing with The Uninformed Strategist. The branding such strategists recommend are unlikely to resonate in the marketplace or generate profits.

You're better off if the strategists do outward branding. Determine the image of the company by doing some solid market research and gaining a solid understanding of the problems prospective and existing customers face. Formulate your key messages using the approaches described in my article, "How to Formulate Marketing Messages".

Better yet, though, make your inward and outward branding converge. To be successful, the management and the rest of the company have to buy into the image and the branding. They have to live and breathe the customer experience. To be credible, your products must embody the key messages you communicate to the market.

Allow your strategist to build internal consensus for a market-driven brand. Then your inward and outward branding will be the same.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardw