Frequently during discussions with clients, I hear a desire for “a catchy, short one-liner to describe us.” Whether you call this a tag line or a USP or something else, the quest for brevity is a regular occurrence. And there is nothing wrong with that. Customers are overwhelmed with information and have many conflicting priorities. Getting attention is important.
However, while the quest is important, the approaches I see people take to get there is often the cause of failures. They start by brainstorming short phrases and put them out there without any context. They do this because others ask them for that catchy phrase. But this approach seldom works.
I believe there is an alternative.
First, develop your “full length” story, using our recommended format:
- Situation (without you)
- Impact (The case for change)
- Resolution (How you help them change) format
Once you have that full story, you’ll often discover key points that really stand out. Make a list of all of these. Then start your brainstorming for the catchy elements from there. The list probably will include elements throughout the story. You may discover that you win by focusing on the customer need, not your product or service. In other cases, the way you do something may be the most prominent.
You’ll likely come up with some better candidates to satisfy the brevity quest. But remember, that your real goal is to build interest in deeper exploration, something we call progressive engagement. It’s really about spurring enough interest in the customer, that they say “Tell Me More.” Then reveal more of the story.
Brevity is important, but it is really about setting the stage to tell the whole story.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.