by Gregor Petri | November 30, 2013 | Comments Off on How many CEO’s to screw in a lightbulb
The CEO title also – at least in Europe – was deemed only approiate if you were at the head of a fairly large and preferably multi-national organization. Sure, startups of just two people sometimes had democratically divided all available CxO titles among themselves (Hi, I am the CT/F/MO and this is Bart who is the COO and CISO). But since founder sounds so much cooler, we nowadays see less and less of that. Also founder has the distinct advantage that you get to keep that title if you grow (Have a look at the movie ”Jobs” to get an idea of the process I mean). Soon the CEO title may go the way of the VP title, which was rapidly enhanced by adding terms like Senior, Corporate, Executive and of course Senior-Corporate-Executive VP. Let me know if you get the first card that says Sr. or Corporate CEO.
Now I am not implying or even assuming that adding multiple CEO’s is just about cosmetics and ego’s. In many cases there is a need to have units that are more agile, more aggressive and more focussed than the typical large corporate multinational. And if you as headquarter actually manage the unit as if you are merely a shareholder – meaning you sit on the non-executive board of this CEO and decide on firing/hiring/paying him but do not get involved in running the unit yourself in any way shape or form – than fine. We used to have the term “general manager” to describe that role, but within the aforementioned modern matrix organization general managers often cannot even decide when to change the aforementioned lightbulb (as facility management does so on a global basis), or on how to organize sales (as corporate product units and lines of business leaders appoint product and sales leads into his unit).
Personally I am a big believer in organizing using cell structures. The late Eckard Wintzen – founder of Origin, later part of Atos Origin – wrote a great little book about this called “Eckarts Notes” (in Dutch and strangely enough never translated, but for a summary in English see http://reinout.vanrees.org/weblog/2011/01/23/eckarts-notes.html). The cell approach – where you split cells if they get tpo big to be managed by one person – was pioneered earlier and is still in use today by other IT service companies. The general idea was that within a unit of between 50-100 people you don’t need a HR department (as the general manager knows each of his people – and their strengths and weaknesses), you don’t need facility management (as you can tell people to clean up their own mess behind them) and you on’t need a purchasing department (as the GM does large purchases himself and leaves individual purchases to the (empowered) individuals . It’s a very entrepreneurial approach, some practitioners even incorporate each cell as a separate company, meaning that cells can go out of business if not managed well.
Tell you what. Why don’t you have as many CEO’s as you like (but do give them full P&L responsibility and operational/tactical and strategic authority for their cell, unit or division), but stick to one CCO (Yes, one Chief Cloud Officer) who coordinates the internal cloud services (that your employees consume) and the external cloud services (that you provide to your customers). Something to ponder on in 2014? Is cloud really more about enabling cells to thrive and prosper, than about centralizing everything into a large grey monotony?
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.