[yanilkr]

For some reason reading this reminded me of this old conversation about frameworks. http://discuss.joelonsoftware.com/default.asp?joel.3.219431....

In a lot of ways, this Leader, LeaderLeader thing is lot like Factory and FactoryFactory patterns in java. That FactoryFactory conversation came out when enterprise java was at its peak and everyone else were preaching that was the standard way of doing things. Then nodejs, rails and functional programming entered mainstream and it made java look very very complex and naturally everyone embraced simplicity and java itself could learn to be simple. It is possible the same is true for technology management.

There are a lot of underlying assumptions here. Like for e.g. This many layers are necessary. There is a right way to be a technology Leader or LeaderLeader and Technology Leader has some awesome supernatural powers to make things happen.

I am not sure if there is a great recipe for managing successful products/teams, if there were one, a lot of people with a lot of money would have done it by themselves with out need for "startups" to innovate. After some point, companies like Google and Microsoft tend to grow mostly by acquiring someone else, usually startups and there is very less LeaderLeader pattern in startups.

I am not too sure how much impactful the LeaderLeader pattern is in tech world. But as a creator of things for other people to use, it might be a better approach to see things from your user's perspective. It appears appealing to that many layers of organization leader hierarchy is a drain on human creative energy.