Quality Management articles: tips, advice, ideas, strategies & solutions

Subscribe to our Quality Management Articles Feeds


Feeds

What's this?

Home > Quality Management

Product Promise

thumb it up Brian Lawley
Is your Product Promise really a promise?

I had an experience with a product this week that was so far off base I decided write about Product Promises.

A product promise is the implied commitment made to customers by a company. It embodies everything that the company, brand, marketing, features and benefits and product description convey. Put simply, a product promise is kept if the customer has an experience that is at least as good as what they expected based on what the company told them.

Products that keep their promises tend to build loyal fan bases and succeed. Products that don't, often fail (though if they solve a burning need for the customer and are the only available solution they sometimes succeed anyway).

What are some examples of product promises where companies met customer expectations and it paid off for them? The original Palm Pilot made a product promise that synchronization would work seamlessly. For me it worked so well I couldn't believe it (at the time). Macintosh (at least the early days) had the product promise that it was the easiest to use personal computer available. Amazon.com had the promise that they offered the world's largest selection of books and that purchasing and customer service be hassle-free. Google's product promise is that you will find what you are looking for on the Internet rapidly with a minimum of effort.

Product promises have gotten a bad rap, primarily because of what happened during the boom. Companies shipped crummy products, made claims that were nowhere near true, burned their customers, and then wondered why they had no repeat or referral business. In fact, one of the biggest challenges the tech industry faces today is that it has trained even the most tech-savvy people to be late adopters. Why beta test software or hardware for a company when you can wait until it is solid and many other people are using it reliably. Of course, this mentality leads to no one using anything because everyone is waiting for the other guy to endure the pain.

Oftentimes Product Management has to be the gatekeeper to watch over whether customers are truly being taken care of. Engineering will always have pressure to ship the product, no matter what. Sales will want the product now, and by the way, it had better work right. Upper management will feel the pressure to make quarterly numbers and will tend to want to ship the product even if it isn't completely ready. QA will tell you what the bug count looks like, and how many severe problems remain. But in many cases the only group that truly has a handle on whether the product will meet customer expectations and keep its promises is Product Management.

At one point during the boom I was offered a high-level job with a company going public in three months. They had an incredible story, lots of talent, a first-class board and executive team, and $120M in funding. But after consulting there for 2 months I declined their offers, despite the fact that they sweetened the pot multiple times and made me by far the best offer I had ever received in my career. Why? I was running Product Marketing and Product Management for them and despite my communication that the product was nowhere close to meeting its product promise, management was barreling ahead and determined to ship it. They did. They never made their numbers. Not even close.

Yes, the founders made some money. But think of the momentum and wealth they might have had if they had truly kept their product promise. They might even still be in business today.

Does your company really keep its product promises?
About the Author:
Brian Lawley is the President of the 280 Group, the Product Marketing & Product Management Experts™. The 280 Group provides consulting, contractors, training and templates to help companies define, launch and market breakthrough new products. For more information about the 280 Group's services and toolkits (Product Roadmap, Product Launch, Beta Program, Developer Program & others) visit www.280group.com.
 

 

No. of Times this article has been viewed : 544
Date Published : Jun 21 2007

Most Recently Published Quality Management Articles as of

Dec 22 2008    The 7 Simple (but ignored) ‘Rules' For Ensuring Your Meetings Are Productive

by Andrew Rondeau

A recent survey (by Dr. Steven G. Rogelberg, Professor and Director of Organizational Science at the University of North Carolina Charlotte) of 1,900 business leaders, 72% indicated they spend more time in meetings today than they did five years ago.

Nov 26 2008    Inspection Techniques for Print Quality on Molded Plastic

by Steven ZHAO

In the inspection of correctly inserted print templates, it has been shown for instance that two feature detection algorithms can be applied.

Jul 1 2008    Profitable Product Creation - Uncover 7 Brand New Methods to Explode Your Product Creation

by Roy Sutanto

Creating new product can be a daunting and overwhelming task as it requires ample time, creativity, and resources. Yet it is something that every entrepreneur must embrace in order to better serve their customers and address their ever-changing needs and demands.

Feb 21 2008    The Meaning of Six Sigma

by Carl Wright

Six sigma has different meanings to different people. Some believe it is all about reducing variation, while others believe it's strictly a quality improvement method. While reducing variation leads to quality improvement when the target is met, there are broader meanings to the term...

Feb 14 2008    Six Sigma Training - Maximize Your Quality Standards

by Anna Woodward

No matter what an organization's function is, quality management is critical: not just the management of quality, but the quality of management. While a variety of Quality Management processes are available, none give you a more accurate statistical process performance metric than...

Feb 12 2008    Using Expert-Based Research to Enable Innovation

by Brian Reuter

Research shows that it takes nearly 300 ideas to achieve a single successful product. The challenge to innovate is great, yet most companies struggle through a disjointed process, often stuck in their traditional way of looking at their business.

Jul 10 2007    Writing Effective Benefits Statements

by Brian Lawley

How to turn features into compelling benefits that matter to customers. When you create effective features benefits will arise and customers will notice.

Jun 21 2007    Product Promise

by Brian Lawley

Make promises that your company will uphold to satisfy the customers.

Jun 20 2007    Prioritizing Features

by Brian Lawley

Prioritizing the features for your product will add to the products overall success.

Apr 15 2007    Crash Testing New Products - Performance Testing Guide

by Article Marketer

Road testing, is actually a good way for the manufacturers of all sorts of products especially in the field of technology to be able to obtain the objective kind of feedback that they need from their prospective buyers in order to ensure the success or failure of their products or services.

Feb 6 2007    ROI of User Experience

by rajesh kumar

Building a product, whether it's a web based or standalone application, is not the goal in itself. The ultimate challenge and success lies in how the product guarantees return on investment (ROI).

Sep 21 2006    Beta Testing, Anyone? 10 Potent Strategies for Achieving Success

by Adele Sommers, Ph.D.

Beta testing should involve a methodical prove-in of a carefully designed system, such as a software product, Web site, or automated tool. It's not meant to be a hit-or-miss Band-Aid that you can apply at the last minute. Here are 10 strategies for s

Search for ebooks on Management & Business