Reddit Reddit reviews The Innovator's Dilemma: The Revolutionary Book that Will Change the Way You Do Business (Collins Business Essentials)

We found 9 Reddit comments about The Innovator's Dilemma: The Revolutionary Book that Will Change the Way You Do Business (Collins Business Essentials). Here are the top ones, ranked by their Reddit score.

Business Management
Business Management & Leadership
Business & Money
The Innovator's Dilemma: The Revolutionary Book that Will Change the Way You Do Business (Collins Business Essentials)
Check price on Amazon

9 Reddit comments about The Innovator's Dilemma: The Revolutionary Book that Will Change the Way You Do Business (Collins Business Essentials):

u/jazzyzaz · 14 pointsr/business

>ignore it altogether

this is up for debate. there's a theory/business thinking called "disruptive business/disruptive technology," and one of its main tenets is that a company should go the lengths to "ignore" what its customer base is saying... but the tenet is followed up with a statement that says that a company should do all in its power to seek out new innovations the customer is not expecting or doesn't know of.

customers don't know everything, and sometimes it's not a bad idea to ignore them while you cook up some fancy new features (iPhone's visual voicemail for example).

what RIM did was the opposite of this. It's apparent that while they were caught up in their own success, their hubris led to them thinking they did not have to worry about the iPhone and its encroachment of the business sector.

They failed to notice that the walls between one's 'corporate career' and 'personal life' have been coming down over the years. Devices that make one's personal life easy to manage have now found themselves in the 'corporate career' zone, all thanks to a well developed UI and lots of research into HCI.

you can read more about this stuff in this book, it's pretty good stuff:

u/mantra · 13 pointsr/apple

Strictly speaking I'm not surprised. Not because I'm an Apple Fanboy (I am - but for "right" reasons ;-) ).

But really just because if you look at the financials of each company over the last 10 years and look at how the product lines and marketing are handled, it's pretty obvious (since ~2000 to me anyway) Microsoft was going to and probably has now, hit a brick wall on revenue growth and innovation to drive more.

Where was Microsoft going to grow when Windows adoption has been stagnant and the compounding rate of adoption drying up compared to 1990s norms. Think about all those corporate users still using Win2K and WinXP; this is a very, very bad juju because corporate IT are one of the big 3 customer bases for Microsoft. And then there's Office. Between these two, there really are no other reliable cash cows in their stable of products. None.

XBox is a promising product line expansion but is it big enough to float Microsoft? I don't think so. Maybe highly profitable as an independent spin-out but where does that leave Microsoft itself? And the market size for games vs. the market size for tablets. Things that make you say "hmmm".

The laughable (when idiots spout it) and simple fact is that high market share doesn't assure revenue growth - in fact above, say 60-80% share, it seriously works against you if your products are in late adoption.

The classic Wintel PC is in late adoption as is the broader class of "computing devices" which includes all computers and tablets. Windows and Office are in late adoption as software products. And these are cash cows? What's really going to replace them? And they will have to be replaced. More Windows? More Office? LOL ROFL! Just like more Burroughs mainframes? That's all that's needed!

Tablets themselves are early adoption as a subclass. The point is, that you don't want high market share in late adoption in a rapidly changing technology. The Innovator's Dilemma describes why this is bad - it create inertia against innovation and it limits your revenue growth opportunities. It's the "why" of where Burroughs or Connor are today. Microsoft has all the classic symptoms.

Simply stated: Microsoft should have not been so aggressive in growth in the past - they wouldn't have this problem now. A simply lack of self-discipline and self-control in as much in opposition as Apple reeks with self-discipline and self-control.

Thus Microsoft's problem is akin to how Apple doesn't have the same problem now even though both companies are about the same age (give or take a year). Although you can think of this as karma for being assholes during the 1990s - it's really just that there's a real physical organization/economic mechanism behind it. Or... karma is real and physical!

Corporate IT is one of Microsoft's three major customers. Another is ISVs (most of whom were the VB6 weenies alienated in ~2000). Sure many people adopted .NET/VB7/C# etc. but Microsoft also lost a large and enthusiastic (blindly so in most cases) part of their mojo. Kind like Apple kicking out the trendy hipsters and expecting all to go well.

The third leg are Wintel HW vendors who have their own disconnects with the end-user markets. All insist on keeping customers at "arm's length".

And, no, end users are not in the top-three of Microsoft's customer base. Microsoft will say otherwise but it's BS lies or self-delusional lies they tell themselves: the supply chains tell the real story. And that is and always has been a serious problem for them despite their successes.

Further the market architecture of the Wintel system is fatally flawed for late adoption innovation - Microsoft's primary customers are 1-2 supply chain links up from actual end-users of their products.

Similarly Intel itself and most of the Wintel HW vendors are 2-3 supply chain links up from the actual end-users as well. This disconnect is part of why the A4 and A5 exist!

Then compare this with Apple which has 0 supply chain links from the customer, end users, for both HW and SW and it's pretty damn obvious who is going to "own late adoption" for computing appliances.

Late adoption requires "appliance-ification" of your product which can not be done at a distance like these supply chain gaps create. No, it's not a matter of "good top-down management" - it's that "bottom-up emergent activity" can't survive or thrive with supply chain gaps. Not when you have to design things by committee across corporate legal entity barriers.

This is why you need to do both HW and SW together - a goodly part of why Apple has its success. And this is why it's a fatal market flaw for Wintel. Which Android has chosen to replicate also. Brilliant! Duh!

As an entrepreneur I've always seen this kind of "it's not my job; I do SW (HW) not HW (SW)" behavior as a wonderful, heaven-sent opportunity to skewer larger competitors. It's an Aikido thing: use their weaknesses as your strengths so they their attempt to muscle you ends up damaging themselves more. It works surprisingly well. It seems to be working for Apple too.

The funny/sad part is all the Geeks who try to defend Wintel/Linux or Android who manage to irrelevantly talk right pass the iPad-buying public with specs and tech-weenie justification that mean absolutely nothing most paying customers. It's like trying to impress the prom queen with your slide rule skillz. It doesn't even register as rational or relevant. Nobody who matters (has money and want to spend it) cares.

You see a lot of these Geeks never lived through the actual leading edge period of PCs nor have most seen an entire technology cycle to even know what early or late adoption look like or how they are different in terms of selling or buying processes. In an early adoption environment, geeks have some power to (de)leverage sales.

I think that's what most of these folks are trying to tap into with spec-talk and nerd-talk about the L33t Pwr2 of Android or OSS or Wintel. The problem is the higher order technology adoption of computer devices is not in early adoption - only the subtechnology of tablets is so in terms of majority buyers, it's a late adoption buying process, not early adoption.

In that world, geeks are nearly powerless to influence most buying decisions because you are so tiny in number and the buyer market made up of non-Geeks so enormous in number. It's a Bayesian statistic prior population thing.

It's the early adoption phase when Geek outnumber or have parity with early adopter buyer markets that Geeks can play the role of "diffusion process gatekeeper". Not in late adoption though. It's a different game at that point. And Apple knows that game far better than all of the Wintel, OSS and Android crowd combined. Funny-Sad.

u/hubert · 7 pointsr/

Your comments on the insiders not wanting to cut an existing source of revenue is the entire subject of a book by Clayton Christensen called the Innovator's Dilemma. Christensen chronicles the hard drive industry and shows how firms continuously refined their products in incremental ways and did everything right according to management and shareholders, only to be crushed by new disruptive technologies.

That's one item that I got from my worthless (50k) MBA.

u/mitc0185 · 5 pointsr/business

I'm reading a book called the Innovator's Dilemma that explains how a company (and Sears is a perfect example) can do all the right things, and still lose its position as the dominant player in the market.

It's a very insightful read -- I recommend it. Very interesting if you're ever thinking of starting your own business.

u/grotgrot · 5 pointsr/technology

> don't have the financial need to innovate

The Innovator's Dilemma book covered this. They do need to innovate and they know that. The problem is that any innovation will look like a rounding error compared to current financials and so on those terms it is hard to make any progress.

u/rob_dimarco · 2 pointsr/

This topic is well covered in the book "The Innovator's Dilemma" by Clayton Christensen

Chapter One...

u/yoda17 · 1 pointr/programming

That is the goal of pretty much all business startups. See The Innovator's Dilemma.

u/PirateINDUSTRY · 1 pointr/explainlikeimfive

Correct for some companies. Especially, now that the internet has really helped us define affinity groups or tribes. Check out Seth Godin if you like discussing that.

The economy has scared a lot of companies into consolidating their products to target the acceptance of the mass bell-curve. This is the safe route; they don't want to wait for the adoption curve to pick up.

Here's the other kick: Some companies are too big to take small wins. A company has to show good returns on their stock every quarter. A small company can turn a profit from niche; however, a larger company has too much infrastructure to support for anything other than large wins and huge margins (to turn the same percent growth).

Suggest reading the Innovator's Dilemma if this is interesting to you.

u/CSMastermind · 1 pointr/learnprogramming

Entrepreneur Reading List

  1. Disrupted: My Misadventure in the Start-Up Bubble
  2. The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win
  3. The E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It
  4. The Art of the Start: The Time-Tested, Battle-Hardened Guide for Anyone Starting Anything
  5. The Four Steps to the Epiphany: Successful Strategies for Products that Win
  6. Permission Marketing: Turning Strangers into Friends and Friends into Customers
  7. Ikigai
  8. Reality Check: The Irreverent Guide to Outsmarting, Outmanaging, and Outmarketing Your Competition
  9. Bootstrap: Lessons Learned Building a Successful Company from Scratch
  10. The Marketing Gurus: Lessons from the Best Marketing Books of All Time
  11. Content Rich: Writing Your Way to Wealth on the Web
  12. The Web Startup Success Guide
  13. The Best of Guerrilla Marketing: Guerrilla Marketing Remix
  14. From Program to Product: Turning Your Code into a Saleable Product
  15. This Little Program Went to Market: Create, Deploy, Distribute, Market, and Sell Software and More on the Internet at Little or No Cost to You
  16. The Secrets of Consulting: A Guide to Giving and Getting Advice Successfully
  17. The Innovator's Solution: Creating and Sustaining Successful Growth
  18. Startups Open Sourced: Stories to Inspire and Educate
  19. In Search of Stupidity: Over Twenty Years of High Tech Marketing Disasters
  20. Do More Faster: TechStars Lessons to Accelerate Your Startup
  21. Content Rules: How to Create Killer Blogs, Podcasts, Videos, Ebooks, Webinars (and More) That Engage Customers and Ignite Your Business
  22. Maximum Achievement: Strategies and Skills That Will Unlock Your Hidden Powers to Succeed
  23. Founders at Work: Stories of Startups' Early Days
  24. Blue Ocean Strategy: How to Create Uncontested Market Space and Make Competition Irrelevant
  25. Eric Sink on the Business of Software
  26. Words that Sell: More than 6000 Entries to Help You Promote Your Products, Services, and Ideas
  27. Anything You Want
  28. Crossing the Chasm: Marketing and Selling High-Tech Products to Mainstream Customers
  29. The Innovator's Dilemma: The Revolutionary Book that Will Change the Way You Do Business
  30. Tao Te Ching
  31. Philip & Alex's Guide to Web Publishing
  32. The Tao of Programming
  33. Zen and the Art of Motorcycle Maintenance: An Inquiry into Values
  34. The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity

    Computer Science Grad School Reading List

  35. All the Mathematics You Missed: But Need to Know for Graduate School
  36. Introductory Linear Algebra: An Applied First Course
  37. Introduction to Probability
  38. The Structure of Scientific Revolutions
  39. Science in Action: How to Follow Scientists and Engineers Through Society
  40. Proofs and Refutations: The Logic of Mathematical Discovery
  41. What Is This Thing Called Science?
  42. The Art of Computer Programming
  43. The Little Schemer
  44. The Seasoned Schemer
  45. Data Structures Using C and C++
  46. Algorithms + Data Structures = Programs
  47. Structure and Interpretation of Computer Programs
  48. Concepts, Techniques, and Models of Computer Programming
  49. How to Design Programs: An Introduction to Programming and Computing
  50. A Science of Operations: Machines, Logic and the Invention of Programming
  51. Algorithms on Strings, Trees, and Sequences: Computer Science and Computational Biology
  52. The Computational Beauty of Nature: Computer Explorations of Fractals, Chaos, Complex Systems, and Adaptation
  53. The Annotated Turing: A Guided Tour Through Alan Turing's Historic Paper on Computability and the Turing Machine
  54. Computability: An Introduction to Recursive Function Theory
  55. How To Solve It: A New Aspect of Mathematical Method
  56. Types and Programming Languages
  57. Computer Algebra and Symbolic Computation: Elementary Algorithms
  58. Computer Algebra and Symbolic Computation: Mathematical Methods
  59. Commonsense Reasoning
  60. Using Language
  61. Computer Vision
  62. Alice's Adventures in Wonderland
  63. Gödel, Escher, Bach: An Eternal Golden Braid

    Video Game Development Reading List

  64. Game Programming Gems - 1 2 3 4 5 6 7
  65. AI Game Programming Wisdom - 1 2 3 4
  66. Making Games with Python and Pygame
  67. Invent Your Own Computer Games With Python
  68. Bit by Bit