Sunday, 12 April 2015

How Do You Take Your Coffee?

Analogies are fantastic. They allow you to portray difficult concepts against a set of real world comparators thus enabling someone to better understand and interrogate ideas. In theories of management, analogies occupy a key station in this lexicon. Let’s take coffee…
In most organisations, ‘Management’ and coffee go hand-in-hand; most meetings start with coffee, are punctuated by coffee, and end with coffee. Often, the most important conversations are those held at the coffee machine. But thinking about coffee in the round provides us with a means of interrogating management styles.
There are a number of different styles of coffee, and - although fanciful - we can parallel them with approaches to management.
Ristretto - a very short, dark, and intense hit, possibly with a bitter after-taste. In management terms, perhaps we can see ristretto as a rapid, no-holds barred, hard-driving, decision-making style, often adopted in extreme circumstances. From a management perspective, advantages of the ristretto approach is that it is ultra-dynamic and things get done in the shortest time possible - but running the risk of doing so in the least elegant or ideal way. Disadvantages? A lack of compromise, perhaps; no prisoners are taken; and perhaps, like the ristretto itself, you can only take so many before you are ‘eyeballs out’, completely hyper, out of control, and unable to relax.
Espresso - also short, dark and intense, but not to the extreme of a ristretto. Espresso management would promote dynamic decision-making also, moving with pace, but in a slightly more refined manner than the extreme and condensed ristretto. The approach still gets things done quickly, with execution the priority above all else; but perhaps there is a little more flexibility and longevity in the approach, although again, after too many espressos, sleep can prove elusive.
Americano - essentially a ‘watered down’ espresso, and with the option of a little milk. On the scale of hard driving, the americano manager will allow the troops a little extra time compared to its condensed parent, and the addition of milk suggests a management style that offers the option of flexibility; more the carrot-and-stick approach than being constantly driven by hard imperative. If quantity is the killer with the ristretto and espresso (in terms of how many hits you can take before it harms you), with the americano it is likely to be volume that is a problem - from a resolution viewpoint, there is only so much you can actually take-on within a given timeframe.
Macchiato - an espresso in a dress. The short, intense hit is still there; results can be dynamic and reasonably rapid; but there is a considerable amount of froth disguising the style. So the macchiato management style can take some time in building up that froth before the ‘wham!’ of delivery. Perhaps slightly less genuine than an americano, the macchiato manager might be in danger of being seen to be just a little duplicitous or inconsistent by the troops.
Latte - here the espresso is bathed in warm and creamy milk. Essentially things still get done, but inevitably they will take a little longer to get over the line. The experience will be softer, less intense; no bitter after-taste; no shock from the coffee hit. In management terms, this would be the most collaborative and engaging style of them all perhaps. But it’s still coffee; there’s still an espresso there at the heart of it, and the manager must ensure that he or she doesn’t lose sight of it if they are to ensure that things still get done.
Cappuccino - the most complex and indulgent of all; espresso, milk, froth, and a sprinkling of chocolate! One of those management styles you probably either love or hate; a mix of hard, soft, bitter and sweet. When it comes off, a cappuccino can be wonderful - but a bad cappuccino is just unpleasant. You need to be an innovative, self-confident and somewhat machiavellian manager to be able to pull off this style effectively. Things will still get delivered, but you might polarise or alienate people along the way.
And finally, cafe au lait - all milk, no substance. A management style like the coffee: at its worst, weak, wishy-washy, bland. Some people would say that this wasn’t coffee at all…
All very fanciful, of course. But the analogy does offer a lens through which to view management styles, to depict or grade how these styles compare to each other, and - crucially - to understand how we prefer to work ourselves.
And the parallel gives us more than that. If you think about coffee, we probably each of us have our favourite from the short list above. In the same way, we each of us have our preferred way of managing - and being managed. If your natural style is perhaps espresso, but your line manager is much more a latte kind of manager, then it is quite likely that you will get frustrated with them because they won’t move fast enough for you. And they are likely to find you reactionary, threatening and perhaps not a little unpleasant or difficult to handle.
Whole organisations can have a ‘coffee culture’ too. Why is this important? Well, it is highly likely that someone who loves their cafe au lait approach will struggle in anything stronger and more intense than a latte organisation. A mismatch of styles, a clash of approach, will be bad for company, manager and employee in various measures.
There are many management definition tools - such as Belbin or Myers-Briggs - that can help to illustrate styles and predict how divergent ones will interact with each other. In all cases, recognition is the first step; tactics to handle disparities follow after that. The simple parallel offered here allows us to start on that analysis journey with a really easy question: “How do you take your coffee?”.


-*-

About the author / copyright

Ian Gouge is widely experienced in business-driven Information Technology, culminating in significant achievements majoring on organisational and process change, and with a proven track record in turning around / re-engineering IT functions. He possesses in-depth experience of change, transformation, IT delivery, customer and supplier engagement, and broad International exposure. Also the author of management books on the topics of IT Strategy and Project Management, the impact on IT of e-Business, and the IT Organisation.

This material is copyright of Ian Gouge © 2015. All rights reserved. Any similarity to actual IT or business organisations is entirely coincidental and unintentional. 

Any redistribution or reproduction of part or all of the contents in any form is prohibited other than the following: 

·         you may print or download to a local hard disk extracts for your personal and non-commercial use only; 

·         you may copy the content to individual third parties for their personal and non-commercial use, but only if you acknowledge the author and blog as the source of the material. 

You may not, except with express written permission from the author, distribute or commercially exploit the content. Nor may you transmit it or store it in any other website or other form of electronic retrieval system.

Wednesday, 31 December 2014

Flat Structures - Really?!


As Managers, what is our job? Once, many years ago, when I was promoted into a senior management role, my then boss informed me that “I didn’t have to ‘do’ anything”. It took me some time to realise what he meant. He didn’t, of course, mean that I sat around, drank coffee and read the papers all day! There were things to ‘do’ – but more in the sense of taking the lead, of helping others to 'do the ‘do’'.

At the end of the day, a Manager’s job is to create an environment which maximises what can be delivered from those components (people, money, capital items etc.) for which he is accountable, however it is appropriate to measure that delivery: profit, service, quality... Which is fair enough, isn’t it?

But often there are other criteria that, whilst we may not realise it at the time, cut completely across that ‘enabler’ ambition and can critically compromise what we can contribute – and therefore, most likely, what others can contribute too. Take the notion of the “flat hierarchy”.

Logically very sound: not too much management; clear line-of-sight between ‘top’ and ‘bottom’; people feeling ‘more connected’ somehow; less bureaucracy, and so on. But in practice?

If you accept the Manager’s role as an enabler, then this means that he or she has to have the time and capacity to help their team: to mentor; to suggest; to coach. Essentially, through the distribution of their experience and expertise, they must enhance what their direct reports can achieve. It fits with the maximisation of the delivery of the 'components' they have at their disposal. If we compromise that, then surely what a manager can contribute is diminished somehow – and if he or she gives less to their team, then those next down the line already start at a disadvantage…

So let's assume we have a flat structure with 111 people and just three layers, top-to-bottom. To achieve this, every one of the eleven managers (the top man and his immediate team) needs ten direct reports to create that organisation.

Perhaps you are one of those managers, and that you are lucky enough to work just a 40 hour week. Depending on your role, you may spend 50% of your week on projects, initiatives, administration. Then there will be the meetings you have to attend outside of your function or team, perhaps with customers, or Finance, or HR. Say another 15%. Then there’s that unplanable ‘stuff’ that crops up (usually from email!) that takes away another 10%.

Where does that leave us? 75% gone, 25% left. That’s just 10 hours in a week to share with your direct reports. If you have ten of them, that's just one hour per person, per week. Is that enough to help them, their teams; to mentor, suggest, and coach? Really? Not only are you stretched as an individual, your people don't start with the full boost you could be giving them.

There is a 'multiplier effect' at work here too. From the top manager to the middle management layer, and then - with those 'middle managers' being at less than 100% effective - down to the real 'doers' in the team.

But what happens if the 111 team has four layers? Then each manager might have just four or five direct reports. Suddenly those free 10 hours per week now gives you around 2 hours for each of your direct reports. If your input is of value (and you would hope it would be!) then all your people should benefit accordingly.

It would take a scientific study to prove the point, but I would be confident that the overall measurable loss of 'effective input' or productivity cascading downwards from management layers would be greater with the former case - two layers only, ten direct reports per manager - than with the second - three layers, more managers, but only four or five direct reports per manager.

You might object that in the 'fatter' organisation, there is a greater level of man management admin and/or non-productive time from a greater percentage of the 111 team (i.e. 21 'managers' vs. 11 'managers'). This ignores the greater effective loss from the flat organisation as suggested above. Also, the truth is that there is no reduction in man management admin delivered by the flat structure: for example, appraisals for all 110 people don’t just go away. They still have to be carried out, and with fewer people to execute them, those eleven managers can only be less effective in this area - and their output of poorer quality.

And it is worse than that of course. In the flat structure, bottom to top needs only 2 promotions – which effectively means that the top 11 positions are ‘blockers’, and the remaining 100 people are looking upwards, seeing no possibility of progression and advancement – unless of course you make the ratio of middle managers to the top guy maybe 1 to 12…

And don't forget, the extra time for managers offered in the deeper structure will more likely be ‘quality’ time. And the “dead man’s shoes” scenario in the second organisation isn’t quite so prevalent.

Are you working in an organisation that's 'too flat'? Of course, you can go too far the other way. A 111 team with six levels of management would clearly be inefficient. There is a reason that 'best practice' suggests the optimal number of direct reports for any manager is between four and seven.

In any event, don’t assume that a flat structure is a good structure; it may not always be the case…


-*-

About the author / copyright

Ian Gouge is widely experienced in business-driven Information Technology, culminating in significant achievements majoring on organisational and process change, and with a proven track record in turning around / re-engineering IT functions. He possesses in-depth experience of change, transformation, IT delivery, customer and supplier engagement, and broad International exposure. Also the author of management books on the topics of IT Strategy and Project Management, the impact on IT of e-Business, and the IT Organisation.

This material is copyright of Ian Gouge © 2014. All rights reserved. Any similarity to actual IT or business organisations is entirely coincidental and unintentional.

Any redistribution or reproduction of part or all of the contents in any form is prohibited other than the following:

·         you may print or download to a local hard disk extracts for your personal and non-commercial use only;

·         you may copy the content to individual third parties for their personal and non-commercial use, but only if you acknowledge the author and blog as the source of the material.

You may not, except with express written permission from the author, distribute or commercially exploit the content. Nor may you transmit it or store it in any other website or other form of electronic retrieval system.