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.


Post a Comment

Popular posts from this blog

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*2And 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 their fellows can resol…

DAD Inception Phase Workshop Agenda

Disciplined Agile Delivery (DAD) realised the reality of the projects and introduced back phases to Agile community. Whoever works in a project based company, especially a project based company where projects are usually less than one year in length and each are for different clients, understands the reality of Agile in such environment. When you start working on a new project for a new client, it is essential to go through a phase that you get to know each other better, to understand the business purpose of the project, to understand the scope of the project, to know what are the high level architecture and what technologies are going to be used and who is the initial team, and if funding is available and also when things must be delivered and to whom.
In answering these questions you may need to meet with different people, run couple of workshops and brainstorming sessions. And this is called Inception Phase. As DAD is more like a goal oriented decision framework and not a prescrip…

Collocation is not the silver bullet for success and agility

To collocate or not to collocate? Most companies that are new to agile have been "consulted" by a "Scrum" Agile Coach, who suggested that they must break their organisation and have cross-functional teams to sit together in one location. Is that the recipe for success?.. Is it really?

Even though collocation has its benefits, it is not the necessary condition for a successful delivery team. Collocation as a dogmatic view may hurt you more than you think, and will not necessarily help you to deliver more successful products.

I am neither for nor against collocation, but I have experienced and worked with both approaches. And each sometimes worked very well and sometimes failed. All the variations of teams geolocation (collocated, fully-dispersed, partially-dispersed, or distributed) can work. It all depends on how the collaboration model is setup, what is the context and conditions, and how much the team and organisation are aware of each other, and are aligned.

Ha…