Skip to main content

What do Old GM, Amazon and Apple have in common?

Alfred Sloan is the one who actually made General Motors a strong brand and a market dominant for decades. One of the strategies he implemented was a simple multi-brand strategy. He reduced the number of GM cars to five and categories them by price. As Jack Trout stated at Big Brands Big Troubles, "The policy was to mass-produce a full line of different cars that were graded upwards in quality and price. The concept was to get people into GM family and move them up. It was one of the earliest examples of market segmentation"

Chevrolet $450 - $600
Pontiac    $600 - $900
Buick      $900 - $1,700
Oldsmobile $1,700 - $ 2,700
Cadilac      $2,700 - $3,500

More than a half century past from those glorious days of GM, and companies who do not learn from history continue to have irrational product lines and they all ask why do we loose market share. They look into their marketing budget, sales force, technology and many areas but not the root cause of their failure. However, there are companies like Apple, with huge potential of falling into downward spiral of irrational product line manufacturing. But, what Apple type of companies do is simple: Clear product line, clear segmentation and do what they can do best.

Amazon is another example of a company with clear product line. They recently introduced several new Kindles at different price tag and totally different features, designed for specific market segments. You may join Amazon Kindle family at a price of $69 and move up to $500, every Kindle is different and meets certain market needs.

Kindle $69
Kindle Paperwhite $119
Kindle Keyword $139
Kindle Fire $159
Kindle Fire HD $199 - $499


Although there are two Kindle products that do not fit into this category and therefore have and will have minimum sales and eventually Amazon will stop producing them: Kindle PaperWhite 3G $179 and Kindle DX 3G $300-$400.

There are many lessons here, but one simple lesson is "Do Not Make Your Costumers Confuse!"

Your customers leave you when they are confuse about your products or brands. When you make it difficult for them to make purchase decision.


Comments

Popular posts from this blog

Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle

I was thinking what the title of this blog post could be, I had couple of options to select from and decided to use a title that uses Disciplined Agile (DA 2.0) Lifecycle. Other options for titles were: Moving From Scrum to Kanban From High Performing Scrum Teams to Hyper Performing Kanban  The bottom line is that at some point you may want to move away from Time boxes to a flow of work and service oriented teams and improve performance and throughput without massive and sudden organisational change.  As always, I only share my experience and this may not apply to all situations, context is important.  Another reason that I selected “Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle” as the title, was that for many it is a question mark how to navigate through DAD life cycles. and I think this blog post could be one of the ways to navigate.  Context: A Delivery Team started with Type A Scrum with 2 weeks Sprints. After a while,

Stay Fitter

1st edition of Fit for Purpose: How Modern Businesses Find, Satisfy, and Keep Customers from David J Anderson and Alexei Zheglov was published in Nov 2017. They wrote the first edition in 7 weeks during summer 2017. I had a chance to provide feedback to them as they were writing and editing their chapters. The book basically talks about what a product and service is made up of, how customers measure the product or service and what metrics company managers must apply at different levels to be always fit for customer purpose (the Why's of the customer). If I want to summarise the book in one statement, it would be like: Align your business to how your customers measure your product and service. When I was reading the chapters, four guys came to my mind: Peter Drucker, Jack Trout, Eliyahu M. Goldratt and Clayton Christenson. The book reminded me of Peter Drucker; because he once made a profound observation that has been forgotten by many, his observation goes like this: "B

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe. At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better . The reasons are simple: It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2 And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next! At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and thei