Insights

Insight for Innovation ®

Here, you will find thought-provoking (and perhaps smile-provoking) resources developed for product innovation professionals. Your feedback is not only welcome, it is actively encouraged. Feel free to comment on the Fresh Insights blog, download articles and peruse the original cartoons. Thanks for looking in.

April 9, 2010

Product Communications: Promise Before Positioning?

pos-impact_low-res1

Along with my work in design strategy and research, I’m occasionally asked to work on new product positioning and communications. Sometimes a new product is not performing to expectations, or there’s evidence that consumers are not receiving key messages or using a product as intended. Consumers just aren’t “getting it”.

I’ve found that there are often two possible reasons why a great product can fall on deaf ears:

1.  The strategic process by which communications are developed is faulty, and messages   become weak and muddled.

2.  Language used to translate positioning intent into communications is misleading, not relevant or just boring.

Here, I’d like to address the first issue, as there’s more to chew on and it’s closer to my own process-driven heart. Sad, I know.

As you might expect, each consumer products marketer has their own unique definitions for process deliverables such as “concept”, “positioning”, “reason-to-believe” and “claim”. And their own order in developing them. But the reason for doing so should always be the same: To find a role in the marketplace for the product and a way of talking to consumers about it that will drive communications across channels.

Often, I find that marketers want to jump right from a concept statement to formulating a positioning. But many times, because both are often phrased in consumer-friendly language, they can sound the same. I could argue that a positioning statement may be worth devising, but is not the most vital link in the communications strategy chain. Allow me to introduce the idea of a Consumer Promise. More on that later.

I’d like to propose a set of terms and definitions, as well as a process for using them that seems to work. In order of investigation:

CONCEPT: The concept defines the key consumer problem/insight/opportunity, and then proposes a product-driven solution. It’s supported by product features and attributes. It’s written for internal use, not in consumer lingo. Its role is to state the what of the product and achieve a common understanding among team members as to what the product delivers. Then, each function can do its job. From formulation development to package design, a clear concept is key.

TERRITORY: Defined as the “room to roam” for the product. It addresses the relationship between the product and other in-house brands, as well as competitive brands and substitutes. It specifies a usage occasion and a consumer target—demographically or psychographically. In essence, it finds a place in the category for the new product. So, its role is to define the where of the product.

CONSUMER PROMISE: This might be a new idea for some, but it’s the lynchpin of the process—perhaps the critical driver of a successful communications strategy. And the element most often neglected. The Consumer Promise translates the concept into a compelling, persuasive and relevant argument for consumers. It starts with a problem statement in language a consumer might use. It then proposes a solution in product terms that addresses purpose, occasion, frequency, and most important, outcome. Then, followed by a single, all-encompassing REASON-TO-BUY, the Consumer Promise offers the why of the product. Why should I believe that it works? Why should I buy it? The RTB supports the Consumer Promise solution by convincing the consumer that the product performs as it says it does.

One concept can and should spawn several potential Consumer Promise statements. Each might characterize a given consumer problem in different ways, or direct itself at distinct insights. As well, the proposed solutions might differ somewhat. But the RTB will remain the same. That’s why the product works. It’s the foundation for performance credibility and the Claims to come. The role of the Consumer Promise is to identify with the consumer. It’s the first time the consumer can react to your offering (or promise, really) and you can best get a fix on how to talk about it. There are ways to test alternative Consumer Promises, but we won’t go there now. Feel free to ask me.

CLAIMS: These are tricky, because they can sound a lot like RTBs or benefits if you’re not careful. But they’re not. Claims are the how of the product offering. How does the product deliver on the RTB? How does it deliver on the Promise?  There are typically multiple Claims statements, each providing a performance characteristic in credible fashion. Claims may demonstrate how the product is proven to work. Or the impact or outcome the consumer can expect. The key is credibility and tangible performance. The role of Claims are to support various communications channels with flexible language templates that can be tailored to the needs of packaging, advertising and other media.

POSITIONING: Why did I leave this to last? Because it’s a by-product of the above real work, and serves little communications purpose. That’s right…I said it. Its role is to galvanize the team by bringing together the Territory, Concept and Promise in one place for internal review and agency direction. It’s efficient, but it’s not a driver of communications strategy or language. Positioning is how we talk to each other in shorthand about the product. Not how we talk to consumers. So, write it whenever you want. Or don’t, if it doesn’t serve the team. Scandalous, I know.

Why bother using these tools to build a communications strategy? Because the discipline outlined here does several important things:

· It ensures the team concurs on product benefits and the consumer needs they are addressing.

· It allows for meaningful testing intervals with consumers to validate consumer problems, insights and solutions.

· It grounds the communications team in what they must convey to consumers and how to bring it to life in words and visuals.

· It makes sure the product is aligned with others in the company’s portfolio, and has a role in maximizing share and penetration for the brand.

So, the next time you think a product is in need of “repositioning”, consider first whether it is making a strong promise and keeping it. After all, consumers buy a product for its compelling promise, not its position on a brand map.

February 2, 2010

Concept Screening: Redefining the Task and Tools

actions_low-res1

All of a sudden, several companies have asked me about new ways to screen concepts with consumers.  When I ask them why this has become an immediate concern, they cite one or more of the following:

  • Project timelines have shortened and brand owners need to make better decisions in less time, and with fewer steps.
  • With more experience launching and evaluating new products in the marketplace, brand owners realize that their research tools aren’t helping them to pick winners as often as they should.
  • The cost of producing models or prototypes for review doesn’t align with today’s budgets.  Brand owners need valid, early-stage assessment of multiple concepts without development cost.
  • Consumers have become more astute, coached and practiced at providing feedback.  Their intent isn’t malicious, but it stems from a desire to please recruiters and the corporate deep pockets that are paying them and weighing their words.

Today’s marketers need to get an early bead on the perceptual, emotional and functional variables at work in a concept set.  It’s no longer a matter of flashing some concept sketches and getting visceral feedback.  Focus group discussions just can’t dissect concepts into what’s truly working, what isn’t and why.  Instead, they provide a murky, unfocused and less actionable reaction that is often limited to “I like it” or “I don’t like it”.

Volumetric and conjoint tools are useful, but too little, too late.  At that point, you’ve whittled 30 concepts down to 3.  But have you chosen the right ones?  And more to the point, what if the right solution was a hybrid of attributes not found in one cohesive concept?  By picking a few, you have by definition sub-optimized the screening process.  While the “winner” will be relatively more attractive than the others, who knows what you’ve left behind? Or what combination of attributes might have been a stronger absolute performer?

So what do you do?  First, abandon your notion of what “concept screening” means.  The evaluation of individual, fully integrated product concepts at an early stage is inherently flawed in execution.  Every comparison is a mixed bag of feature apples and oranges.  Some overlap in the concepts and some don’t.  Each offers a different way to interact on shelf and in use.  Or, it doesn’t.  Asking consumers which of 20 concepts they like in the midst of all these moving parts is an exercise designed to fail.

What’s the better way?  First, let’s come at the problem from another direction.  Redefine concept screening as “attribute” screening.  In the early stages of concept development, concepts are too immature for valid independent screening.  They are comprised of different, rather raw ways of delivering certain valued utilities.  You can’t even call these “features” yet.  So the right question is not “which concept does the consumer prefer”, but “which set of attributes across concepts delivers the most consumer value?”

Am I talking about an early conjoint test?  Not really, because this approach answers both the “whats” and the “whys” in vivid perceptual and functional terms.  And if presented properly, the answers are not constrained by invalid verbal response or feature interpretations that may miss the mark.  Once attributes are properly explored and valued, they can be recast in an optimized product configuration or, at the very least, a given concept can be chosen that does the best job of delivering on captured consumer expectations.

Are there any research tools that can provide a solid, early stage concept (er…attribute) assessment to help narrow the field and guide development?  As you might expect, I’ve invented a few, and have been using them successfully for some time.  They are grounded in qualitative methods, yet have “qual / quant” benefits.  You can find out more about them on this site in the Tools section.  Or, just get in touch with me.

November 16, 2009

Innovation Process: Are You Working Backwards?

inno-emphasis-chart2I’m not big on coining phrases to label the steps of an innovation process.  That’s because there’s no one best approach for all innovation challenges.  And, I might even argue that the very notion of implementing a standardized innovation process and expecting a higher new product success rate is like putting a strategic planning function in place and expecting a ground-breaking strategy.

It doesn’t work that way.  Quite often, the goal becomes one of navigating the process itself at the expense of carefully vetting tools, participants and creative input.  Often, success is measured in phases completed rather than unrecognized needs exposed or compelling solutions devised.

But, I rant.  So, back to the title of this post.  I’m using catchy descriptors here to make a point.  I believe the following about the drivers of successful innovation:

  • There is infinitely more success leverage in “Defining” than in “Delivering”.  Sure, execution is critical and projects fail because of it.  But, they never succeed because of it.  If you haven’t defined what you’re solving for in a way that can focus,  inspire and guide concept development, you have no chance.
  • Design firms tend to be technically competent, but lacking in “front-end” strategy and direction-setting activities.  So, ideation can be unfocused and proposed solutions may be less than right for the brand, the marketplace and the organization.
  • Research firms are great at executing research, but lack the strategic underpinnings to identify objectives, select proper research tools and analyze results from a brand perspective.

Now that I’ve trashed the most common “substitutes” for the work I do, it’s time to admit that this chart is self-serving.  Yep.  But that doesn’t mean it’s not true…

October 27, 2009

Ken’s Book: “Insight for Innovation” — FREE!

book_cover2

I recently updated my book, “Insight for Innovation” to include three published case studies and a number of  new, original cartoons.  As well, it includes 17 short articles I’ve written for publication over the years on topics such as:

Innovation tools and processes

Product development strategy

Design research/VOC methods

Concept ideation approaches

Consumer behavior and trends

For a free copy, please click on the “Contact” tab at the top of the page and fill out the short form.  Be sure to check the box indicating you would like to receive the book.  It’s a quick read with a table of contents so you can check out the articles that are of most interest to you.  But be sure to thumb through the entire book to catch the original cartoons.  They take an amusing look at the trial and tribulation of working in innovation these days.  Let me know if you agree…

July 28, 2009

KMG Innovation Methodology: PATENTED July 28, 2009

I’m very excited to announce that my Innovation Methodology was issued a US Patent today.

What’s it all about, you ask?  Well, take a look at what’s behind the “About” and  “Tools” tabs on this site.  That will give you a feel for the consumer insight and analytical tools that work together to help focus, inspire and guide concept development for product and package innovation projects.

But there’s more to the Methodology (and the patent) than can be presented here.  So get in touch to find out more.

July 14, 2009

Original Cartoon: How Marketers and Designers Co-Exist

drivingpost5

When I first wrote and published this cartoon, some were offended.  Thankfully, both sides took me to task.  But while the depiction might be stereotypical in equal opportunity fashion, I think the point is valid.  At least the less obvious point.  The most obvious point is that marketers and designers solve problems differently.  Newsbreaking, I know.

Less apparent may be the idea that in spite of different ways of viewing the world, marketers and designers desperately need each other.  And not because we expect creative and analytical minds to sit in separate corners performing the discrete tasks to which they are best suited.  But because when they work together on the very same task, the results are better.

Why?  Think about the engine and transmission of a car.  One generates unbridled horsepower.  The other makes that power more efficient and purposeful, delivering it to the road.  Some would argue that the transmission can choke off and constrain the engine.  Instead, I think it harnesses and distributes the power as needed and helps the engine react to road conditions.

In the same way, the analytical mind can focus and guide the creative mind in very deliberate fashion to put the horsepower against the project parameters that matter most.  Not to elaborate here, but that’s what my KMG Innovation Methodology is basically all about.

So, the next time you see marketers and designers on a collision course, try working through the gears together.

July 7, 2009

Pseudo-Ethnography: Constructive when Contrived?

enthnographer_low-res

Recently, I was preparing for some Immersion work for a client that involved witnessing some consumer shopping occasions.  I contacted a recruiter that I hadn’t used before, but had been recommended.  I was looking to recruit grocery store shoppers along specific category, attitudinal, demographic and behavioral criteria.  No big deal.

Until the recruiter asked me for a few details:  What should the scheduled interview times look like each day?  At what specific stores in the area would I like to meet the respondents?  Do I want to meet them before they shop or after?  Those of you who have been involved in ethnographic research can plainly see the danger signs in this line of questioning.  And those of you who haven’t might certainly smell something fishy.   When I asked the recruiter why she was asking me for this information, she said:  “It’s easier for all of us that way”.  Oh, well–if it’s easier…

I told the recruiter that I wasn’t too concerned about “easy”, and that I wanted to do the sessions when, where and how the consumer typically shops.  Silence on the other end, as she thought about how this little wrinkle would impact her day.  As if no one ever demanded this before.   Suffice it to say that we did it my way, which in my mind is the only worthwhile way to do it.

Contrived ethnography is a contradiction in terms, as well it should be.  Whether in homes, stores or anywhere else, Immersion is not simply an interview in context.  The user experience cannot be “scheduled”.  Insight into shopping behavior cannot be gleaned in an unfamiliar store or a forced in-store routine.  True Immersion doesn’t involve more time in a sit-down Q&A than in observation.  And, it does not involve scads of note-takers, videographers and observers.

So, the next time you are asked by your ethnographer when and where you would like to do the “in-home interviews”, run.  Or, better yet, say “whenever and wherever the consumer wants”.

June 29, 2009

Original Cartoon: Ideation Goes Over the Edge

letsjustgopost8

After catching the end of “Thelma and Louise” again on TV, I was inspired.  Here, the poignant last line in the film is borrowed to suggest the fate of concept ideation without some thoughtful pre-work.  My apologies to Geena Davis.

June 15, 2009

Brainstorming Etiquette: No “Bad Ideas”?

There are bad movies and bad meals.  Bad art and bad haircuts.  And yes, I’m afraid there are also bad ideas.  Where do you think all those bad movies come from?

I was recently invited to participate in a client brainstorming session dedicated to new package concepts.  The moderator (not me) began by outlining the “rules” of the session, one of which was that “there are no bad ideas.”  Each pearl would be duly recorded, discussed and evaluated.  Well, it was not my place to question this edict, and I know that it is a common guideline for brainstorming sessions.  But for this and other reasons, the team failed to achieve the goal of the session.  Stop me if you’ve heard this one…

My guess is that the “no bad ideas” rule came about to ensure the free flow of creative thinking and to encourage participation by all.  But I can’t help thinking that the genuine, proven reason for this practice is that we don’t want to undermine group dynamics and alienate team members in a hurtful critique of their ideas.  These are noble intentions, but they exact a high cost in productivity and even quality thinking.  Why?

Because the team ends up spending a lot of time in attempt to squeeze something meaningful from each kernel of wisdom.  Everyone in the room knows there’s often nothing to salvage, except for bad feelings.  Now, I’m not saying that team members are prone to dispensing worthless ideas.  Quite the contrary.  I think they are inclined toward brilliance…with the right focus.  But without that focus, it’s a crapshoot and there’s no reason to expect more good ideas than bad ones.  There’s not even a reason to believe we know what a good idea is.

So, how do these less than good ideas come about, and how are they best managed in the moment?  Certainly, team members are smart, capable and experienced.  But I believe that very often not enough pre-brainstorming preparation is done to frame up the problem, identify what the session is solving for, and define what a good idea really is.  Describing this process is not the subject of this little rant, but suffice it to say that everyone must be well versed in how the consumer defines expected performance (“utilities”), and the drivers of value.  These should be articulated in clean, clear, simple platforms that team members can be mindful of and refer to throughout the session.  I call this approach “Precision Ideation”, a topic for another day.

This approach has two positive impacts:  First, it allows team members to edit their ideas before exposing them to the group, saving time and distress.  Second, it encourages a powerful focus on solving for the key value drivers in very specific terms, ensuring all ideas are stronger.  When time, available resources and/or knowledge does not permit this approach, there is another rather simple method.  When I run such sessions, I like to break the team into subgroups for the most thought-intensive activities.  I think that the most cogent ideas often come from individuals, and that ideas that emanate from large teams tend to be watered down and meandering.  Therefore, small groups are the closest we can get to an environment that can best nurture a great idea in a brainstorming setting.  It’s also the most delicate arena for quashing a bad one.  That’s because a small group is informal, closely knit and non-confrontational.  So, there’s no risk of humiliation.  On the flip side, such a supportive, no-risk setting is just as likely to induce brilliance that may never have surfaced in a larger group.  Small groups can build and refine their idea set, present them to the larger group, and share all the recognition among them–both positive and negative.

It’s a win-win-win.  Ideas are better, forwarded in less time, with no personal recrimination.  In the end, acknowledging that there are, in fact, bad ideas out there helps to ensure that there are great ones, too.

June 8, 2009

Selling it In: Define, Develop and…Defend!

I’ve got a few issues with innovation processes.  Not because they are not effective in driving go-no-go decisions and speeding time to market.  But because I think they ignore  a critical cause of innovation project failure:  Unsuccessful sell-in to management.  There’s no real prescription for how to do this right.  I’ve seen more than a few solid business cases fall flat with management because the team couldn’t quite motivate and inspire the audience.  But, it’s not the team’s fault.  It’s all in the storytelling.

Many brand design firms like to talk about project “stages”.  They’re often some variation on “Define, Develop and Deliver”.  I would insert one more “D” word–”Defend”–between Define and Develop, as a way to standardize the sell-in process.  Defending a course of action is a key activity, but often the project review presentation is organized by sequential deliverables and their results.  But, a senior audience isn’t inspired by a chronological parade of facts and findings.  They want to visualize the opportunity.  They want to be told an engaging story.  They want to be sold.

A good story vividly demonstrates how key insights surfaced emotional and functional drivers of value for consumers.  And how those drivers were captured in a strategy and then translated into unique and exciting concepts.  Concepts that exceed consumer expectations and are mindful of internal constraints.

So, I’d love to hear about a business case that worried less about the chronology of a project and more about the progression of the thinking.  Just like really smart, intuitive kids,  I’d like to think management’s eyes brighten at the telling of a good story.

« Newer PostsOlder Posts »