2/ Finance reason is well known: sustaining innovation looks for measurable, quick top-line impact that disruptive does not show early on
-
-
Replying to @vgr
3/ Sociological reason: due to cooperative nature of work (individual contributions buried), the default internal tribe is the slacker tribe
1 reply 3 retweets 2 likes -
Replying to @vgr
4/ Finance reason does not truly explain why "self-disruption" fails (a strong leader *could* get the time constants and $ right)
1 reply 1 retweet 1 like -
Replying to @vgr
5/ Sociological reason does explain: slacker tribe does not *want* to accelerate.
1 reply 3 retweets 3 likes -
Replying to @vgr
6/ Attempts to create an inner, faster tribe will lead to ostracization from essential support function.
2 replies 3 retweets 5 likes -
Replying to @vgr
7/ Only way to resist that is to create a "full stack" internal tribe with independent soup-to-nuts capability, not just P/L.
1 reply 2 retweets 4 likes -
Replying to @vgr
8/ This is impossible in a sufficiently old company because years of cost-discipline ==> shared services. You can't pwn an entire function.
1 reply 1 retweet 2 likes -
Replying to @vgr
9/ You could try "internal vertical integration" -- resist the allure of efficiency, keep redundancy.
1 reply 1 retweet 1 like -
Replying to @vgr
10/ If marketing, say, hasn't been consolidated and centralized, one marketing node could be pwned exclusively by disruptor tribe
1 reply 1 retweet 2 likes -
Replying to @vgr
11/ This means a CEO who wants internal disruption will have to sacrifice *margins* by forgoing organizational efficiencies.
3 replies 2 retweets 3 likes
12/ i.e., keep the company structure a set of vertical, redundant flows, 1 per product. Build pay-for-redundancy into business model.
-
-
Replying to @vgr
13/ There is a CS metaphor here: run every product inside its own VM. Only bare-metal functions are corp. governance ones (legal, cap table)
2 replies 3 retweets 5 likes -
Replying to @vgr
14/ People don't realize how powerful VM ideas have gotten since VMWare. Check out Bromium for MicroVMs for instance.
3 replies 3 retweets 3 likes - 12 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.