Conversation

Replying to
4/ Finance reason does not truly explain why "self-disruption" fails (a strong leader *could* get the time constants and $ right)
1
1
Replying to
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
4
Replying to
8/ This is impossible in a sufficiently old company because years of cost-discipline ==> shared services. You can't pwn an entire function.
1
2
Replying to
10/ If marketing, say, hasn't been consolidated and centralized, one marketing node could be pwned exclusively by disruptor tribe
1
2
Replying to
11/ This means a CEO who wants internal disruption will have to sacrifice *margins* by forgoing organizational efficiencies.
3
3
Replying to
12/ i.e., keep the company structure a set of vertical, redundant flows, 1 per product. Build pay-for-redundancy into business model.
1
2
Replying to
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
5
Replying to
15/ VMs as a management metaphor means your *2nd* product is the one that determines whether your company has disruption resistant DNA
1
4
Show replies