<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>duxup</author><text>Even just changing simple behaviors across a large company can be impossible.  I worked at a company with several thousand employees all required to attend mandatory training on &amp;quot;effective meetings&amp;quot;, several hours long spread out across thousands of employees.  Rule 1 was to have an agenda for the meeting.  This was something nobody did at this company and you would regularly attend meetings unprepared.&lt;p&gt;After all that training, still nobody did it (ok I did and one other guy).   That company couldn&amp;#x27;t change anything.   It was amazing.&lt;p&gt;They had a project to change a department into more proactive than reactive.  The solution was to create a lot of bureaucracy surrounding being proactive.  As you can imagine bureaucracy about being proactive was really just institutionalizing ... not being proactive.&lt;p&gt;I eventually left and work at a smaller company now.  It&amp;#x27;s been refreshing for years now when we can decide &amp;quot;this process doesn&amp;#x27;t work, let&amp;#x27;s not do it anymore&amp;quot; and it just happens.  Even just new coworker: &amp;quot;I won&amp;#x27;t be in tomorrow, who do I tell?&amp;quot;, me: &amp;quot;you just did, have a great time off&amp;quot; seems revolutionary after being at a big company for so long.&lt;p&gt;I&amp;#x27;m convinced that as the sheer numbers of humans increases the friction to making real change in a company decreases and there&amp;#x27;s not much you can do.   Fundamental change to respond to real disruption, nigh impossible.</text><parent_chain><item><author>mrandish</author><text>You highlight one of the most interesting (and perhaps less understood things) about the key Innovator&amp;#x27;s Dilemma insight. Even if the senior management have read the Innovator&amp;#x27;s Dilemma books, know they are being catastrophically disrupted and desperately trying to respond - it&amp;#x27;s &lt;i&gt;still&lt;/i&gt; incredibly difficult to actually do.&lt;p&gt;Not only are virtually all organizational processes and incentives fundamentally aligned against effectively responding, the best practices, patterns and skill sets of most managers at virtually every level are also counter to what they must do to effectively respond. Having been a serial tech startup founder for a couple decades, I then sold one of my startups to a valley tech giant and ended up on the senior leadership team there for a decade. I&amp;#x27;d read Innovator&amp;#x27;s Dilemma in the 90s and now I&amp;#x27;ve now seen it play out from both sides, so I&amp;#x27;ve thought about it &lt;i&gt;a lot&lt;/i&gt;. My key takeaway is that an incumbent&amp;#x27;s lack of effective response to disruption isn&amp;#x27;t necessarily due to a lack of awareness, conviction or errors in execution. Sure, there are many examples where that&amp;#x27;s the case but the perverse thing about I.D. is that it can be nearly impossible for the incumbent to effectively respond - even if they recognize the challenge early, commit fully to responding and then do everything within their power perfectly.&lt;p&gt;I&amp;#x27;ve even spent time sort of &amp;quot;theory crafting&amp;quot; how a big incumbent could try to &amp;quot;harden&amp;quot; themselves in advance against potential disruption. The fundamental challenge is that you end up having to devote resources and create structures which actually make the big incumbent less good at being a big incumbent far in advance of the disruptive threat appearing. It&amp;#x27;s hard enough to start hardcore, destructive chemo treatment when you actually &lt;i&gt;have&lt;/i&gt; cancer. Starting chemo while you&amp;#x27;re still perfectly healthy and there&amp;#x27;s literally no evidence of the threat seems crazy. It looks like management incompetence and could arguably be illegal in a publicly traded company (&amp;quot;best efforts to maximize&amp;#x2F;preserve shareholder value&amp;quot; etc).</text></item><item><author>martinpw</author><text>Whenever this topic comes up there are always comments saying that SGI was taken by surprise by cheap hardware and if only they had seen it coming they could have prepared for it and managed it.&lt;p&gt;I was there around 97 (?) and remember everyone in the company being asked to read the book &amp;quot;The Innovator&amp;#x27;s Dilemma&amp;quot;, which described exactly this situation - a high end company being overtaken by worse but cheaper competitors that improved year by year until they take the entire market. The point being that the company was extremely aware of what was happening. It was not taken by surprise. But in spite of that, it was still unable to respond.</text></item></parent_chain></comment><story><title>The Rise and Fall of Silicon Graphics</title><url>https://www.abortretry.fail/p/the-rise-and-fall-of-silicon-graphics</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>rbanffy</author><text>I think SGI failed to understand that there was a point where desktop PCs would be  good enough to replace dedicated workstations. Continuing to make hardware that&amp;#x27;s much better than the best PCs wasn&amp;#x27;t going to save them after PCs crossed the good-enough line - whatever they had, would be relegated to increasingly rarefied niches - the same way IBM now only makes POWER and mainframes - there is no point of making PCs, or even POWER workstations anymore for them, as the margin would be too narrow.&lt;p&gt;SGI could double down on their servers and supercomputers, which they did for a while, but without entry-level options, their product lines becomes the domain of legacy clients who are too afraid (or too smart) to port to cheaper platforms. And being legacy in a highly dynamic segment like HPC is a recipe for disaster. IBM survived because their IBMi (the descendant of the AS&amp;#x2F;400) and mainframe lines are very well defended by systems that are too risky to move tied to hardware that&amp;#x27;s not that much more expensive than a similarly capable cluster of generic and less capable machines. As the market was being disrupted from under them, they retreated up and still defend their hill very effectively.&lt;p&gt;The other movement they could do was to shift downwards, towards the PC, and pull the rug from under their workstation line. By the time Microsoft acquired Softimage and had it ported to NT, it was already too late for SGI to even try that move, as NT was solidified as a viable competitor in the visual computing segment, running on good-enough machines much, much cheaper than anything SGI had.</text><parent_chain><item><author>mrandish</author><text>You highlight one of the most interesting (and perhaps less understood things) about the key Innovator&amp;#x27;s Dilemma insight. Even if the senior management have read the Innovator&amp;#x27;s Dilemma books, know they are being catastrophically disrupted and desperately trying to respond - it&amp;#x27;s &lt;i&gt;still&lt;/i&gt; incredibly difficult to actually do.&lt;p&gt;Not only are virtually all organizational processes and incentives fundamentally aligned against effectively responding, the best practices, patterns and skill sets of most managers at virtually every level are also counter to what they must do to effectively respond. Having been a serial tech startup founder for a couple decades, I then sold one of my startups to a valley tech giant and ended up on the senior leadership team there for a decade. I&amp;#x27;d read Innovator&amp;#x27;s Dilemma in the 90s and now I&amp;#x27;ve now seen it play out from both sides, so I&amp;#x27;ve thought about it &lt;i&gt;a lot&lt;/i&gt;. My key takeaway is that an incumbent&amp;#x27;s lack of effective response to disruption isn&amp;#x27;t necessarily due to a lack of awareness, conviction or errors in execution. Sure, there are many examples where that&amp;#x27;s the case but the perverse thing about I.D. is that it can be nearly impossible for the incumbent to effectively respond - even if they recognize the challenge early, commit fully to responding and then do everything within their power perfectly.&lt;p&gt;I&amp;#x27;ve even spent time sort of &amp;quot;theory crafting&amp;quot; how a big incumbent could try to &amp;quot;harden&amp;quot; themselves in advance against potential disruption. The fundamental challenge is that you end up having to devote resources and create structures which actually make the big incumbent less good at being a big incumbent far in advance of the disruptive threat appearing. It&amp;#x27;s hard enough to start hardcore, destructive chemo treatment when you actually &lt;i&gt;have&lt;/i&gt; cancer. Starting chemo while you&amp;#x27;re still perfectly healthy and there&amp;#x27;s literally no evidence of the threat seems crazy. It looks like management incompetence and could arguably be illegal in a publicly traded company (&amp;quot;best efforts to maximize&amp;#x2F;preserve shareholder value&amp;quot; etc).</text></item><item><author>martinpw</author><text>Whenever this topic comes up there are always comments saying that SGI was taken by surprise by cheap hardware and if only they had seen it coming they could have prepared for it and managed it.&lt;p&gt;I was there around 97 (?) and remember everyone in the company being asked to read the book &amp;quot;The Innovator&amp;#x27;s Dilemma&amp;quot;, which described exactly this situation - a high end company being overtaken by worse but cheaper competitors that improved year by year until they take the entire market. The point being that the company was extremely aware of what was happening. It was not taken by surprise. But in spite of that, it was still unable to respond.</text></item></parent_chain></comment><story><title>The Rise and Fall of Silicon Graphics</title><url>https://www.abortretry.fail/p/the-rise-and-fall-of-silicon-graphics</url></story>