Feeds:
Posts
Comments

Archive for the ‘Management’ Category

shortcutRecently reading Dan Pink’s Drive, I was mesmerised by a statement of leadership type classifications. I wondered whilst reading it if there was a way to short cut the interview process to get the right type of leader by asking the following question:

We believe here at <Company X> that people fundamentally dislike work and would avoid it if they could. They don’t take responsibility for their actions and badly need direction. We want managers at <Company X> to co-erce, control and direct their staff to put adequate effort to the achievement of the organisations objectives – are you the sort of person that relates to this and can help us with this?

Now what you are actually seeking here is not a positive affirmation. What you are seeking is the look of shock and horror. The right person is the one that says “I’m sorry but this is definitely not the place for me; thank-you for your time,” and walks away. Most people wouldn’t do this, they would dance around the question, but a real leader is the type of person that will stick up for their beliefs and despite the negative impacts to them will stand firm. It takes juts to say no to this sort of question, especially this early in the process of understanding the organisations culture. It takes honesty to speak true to your beliefs. It takes a leader and not a manager to negatively respond to this question.

What do you think? Would this short-cut work if you were trying to hire an Agile leader?

Read Full Post »

purposeSometimes there are moment in life when like a bolt out of the sky you have a major self realisation. I had one of those moments recently when I realised that for a majority of my coaching life I have been pushed and prodded by my leaders/managers to behave as a Purpose Driven Agile Coach.

What is a Purpose Driven Agile Coach?

It is a coach that is asked/told that when they implement Agile that there needs to be a plan to improve capability. Targets are set and tracked weekly. An example could be, “Improve stand-ups within the month”, it is still very open ended but the practice it is linked to and the time frame is set.

I would imagine that this is quite common in organisations with low Agile maturity and very strong old school management mentality. In these cases, organisations want to predict and understand the value that Agile Coaching provides. Often this is linked to definable metrics, before and after of Agile capability in teams, but I often felt that this capability was shallow. I would be pulled and moved onto another team before I had a chance to really embed the change and ensure that behaviours didn’t regress. I was often only given the time to teach the ‘shu’ basics and never the time to allow for trancendence to ‘ha’ (and certainly not ‘ri’).

But lately I have been less pressure bound from a coaching perspective (I still have pressure, it is just different). This release of pressure to not plan has resulted in me using a different model – Opportunistic Agile Coaching.

What is an Opportunistic Agile Coach? 

It is a coach that only course corrects or teaches based upon the moment, taking into account both team and individuals mental model readiness, change value and change fatigue. Let’s break this statement down some more.

Mental model readiness is about whether the team or individual is in an intellectual state of readiness to receive the coaching advise/support/inception reflection idea. For example, I might personally believe that the benefits of estimation are limited, but the team may have given the concept little thought. Mental model readiness is about whether they have been asking the same questions themselves or whether I have introduced the inception reflection idea. I say ‘inception reflection idea’ because it really is like the movie Inception – you want to seed the idea or consideration in the team as to whether the practice is worthwhile or not and give them time to reflect on it.

Change fatigue should be fairly simple – how much change is the team or individual currently dealing with? If they are completely new to Agile or are mentally still coming to grips with some concepts of Agile then I am less inclined to make drastic changes. For example, if they are familiar with Scrum terms such as PBI and Sprints, where as I am more comfortable with saying Stories and Iterations, I will just go with their flow and not introduce name conflicts for the sake of it.

Change value is about whether the team or individual will get much (if any) improvements from the change. By improvements I mean faster client feedback, improved customer value, improved personal engagement, etc.

Regardless of which Agile Coaching method, I have always started by mentally creating my own backlog. It is easy for me to see what practices need to be improved and where. Sometimes if there are a lot of issues or the complexity is significant I will write it down as a real backlog and estimate it. To some extent, I have always done coaching with opportunistic elements – ie I gauge priority by change value and do take into account mental model readiness, but when there is no set plan, then it is really very liberating.

As a problem or situation crops up I can assess it against where the item fits in my mental backlog. If it was bubbling up closer to the top then I will use the opportunity there and then to address it. I might let certain opportunities pass as they are still very low on the list, but what might have been tackled four weeks later in a planned approach is addressed on the spot, with immediate context and relevance.

Relevance to revolution vs evolution in Agile models

My realisation of the existance of two Agile Coaching approaches, purpose vs opportunistic, made me then immediately think of the revolution versus evolutionary debate in the Agile community. A purpose based approach is more closely aligned with a revolutionary approach where mass transformation is expected/desired and cookie cutter conformance is achievable due to standardised but complicated teams. A opportunistic approach is more closely aligned with a evolutionary approach where incremental change is made based on team readiness and self-realisation – there is no cookie cutter conformance and there is a realisation that there is no such thing as standard teams, or that teams that are dealing with complex problems.

Conclusion

I know we would all like to think of ourselves as opportunistic coaches, but how many of you are really doing purpose based Agile Coaching and is there a right/wrong way?

Read Full Post »

It is highly regarded among many in the Agile community that:

  1. One of the most common causes of Agile transformational failure is due to either the lack of focus on or lack of effective change of the middle management layer.
  2. One of the more common successes of Agile transformations is when small, incremental or evolutionary change is encouraged (rather than what I have termed “legion” style transformation which includes massive roll-outs of training and sparse support).

But I wonder if there is a better way, a way that combines these two points together for more successful, albeit slower and less Agile Coaching consultative heavy model -

Rather than trying to teach Agile inside of an organisation day 1, instead work with the middle management layer to re-introduce learning as one of their key practices.

learning

If middle managers spent one to two days a week learning what do you think that would do to the organisation? I think it might kick start the organisation in all sorts of unbelievable ways. I think middle managers, rather than being forced to have these new approaches thrust upon them, would instead be the most passionate advocates for them. They might not choose to try Agile, they may want to try something else, but at least they are experimenting and thinking wider than just the day to day firefighting.

I know some managers already do this, but it is the exception and not the rule. But why is this? Do managers stop learning because they think it ends at university? Do they stop learning because they think it ends when they finally get into a leadership position? Or is it because they no longer have time anymore? Always in meetings or always fighting a fire?

Maybe the only way that managers will have the time to create a learning culture is if they limit their work in progress and begin to trust and empower their staff more? Now if managers start to trust and empower their staff more because they have to limit their work in order to learn, it is sounding like a win-win to me.

What do you think?

Read Full Post »

When I mentioned to some community friends that I was going to be reading Steve Denning’s Radical Management book a number of them looked at me as if I had contracted some form of virus. “Why would you read a dumbed down book on Scrum?” they said.

The answer for me was simple -

  1. Agile, I feel, isn’t an easy concept for Managers to get. I wanted to check the three prominent books on the market that are there to help Managers become Agile in order to see which one I would recommend if I ever had a manager (which admittedly to date I haven’t) one of them asked me for a recommendation.
  2. Because I do feel that it is hard for Managers to get Agile I wanted to see if there were any hints to what I could do differently or on what practices are relevant for Managers.
  3. I really like Steve Denning’s HBR articles. He has a beautiful writing style which I can appreciate for its simplicity and purpose.

Within this book review I won’t be comparing this book to the other two (although I might do then when I review those), instead I want to focus on my thoughts as I read the book.

Firstly, focusing on my third point above I was not disappointed. For the most part I did continue to enjoy Steve’s writing style in this book. Most pages I felt engaged in and whilst the pages didn’t all fly by, certainly up to the end of Chapter 9 they did (from there it does drag on a little).

Secondly, for a manager that has absolutely zero understanding of Agile and has focused for most of their management tenure on traditional command and control methods, either intentionally or not, I feel that this is an excellent book… to start them on the mental journey.

Which brings me into my third point. It tries to give a practical angle of applying it but I couldn’t in all honesty give this book to a Manager and expect them to be able to do the practices effectively. In fact, in a number of instances there is no detail on how to do a practice. So what this book does really well is get Managers to begin to question what they do and how they do it, less so actually enact change. This could be perceived as quite a concern for many but I don’t think it is that big of a deal – the difficulty is in the mindset change and this book does address well why you would want to shift from being a traditional manager to a radical manager. Additionally the book is riddled with references so if you did read this book and wanted to find more than there are a huge number of useful references at the back.

Now for the negative bits (which I don’t feel outweigh the positive):

  1. Some of the examples are poor – they don’t get the message across or they are weak links to the lesson. Steve is a good storyteller, just a few of the stories are duds. The first one in Chapter 10 is an example of a dud, as is the communicating example further in the same chapter. The roles in Chapter 1 also felt disconnected.
  2. The focus is strongly on Scrum. There is little content on Lean and only a sentence or two on Kanban. It would have been nice to have a broader view of being radical aside from Jeff Sutherland’s perspective. I was aware of this prior to reading the book so maybe I was a little more conscious of it than most readers would be. That said, I actually find that non Iterative Agile is an easier concept for Managers to understand.
  3. Iterations. I’m left with a feeling that Steve doesn’t understand what an Iteration is. It seemed to hint more towards an increment rather than an iteration. The examples that he gives on iterations are poor and for a fundamental principle I think it could have been articulated further.
  4. There are some occasional inaccuracies in advice (in my humble opinion) – like the concept that Value Stream Maps would find the phantom traffic jam problem and what defines “divergence” when using Planning Poker.

So it might be early days to know what book to give to a Manager to learn Agile (even if this was not the intent of this book and it’s intent was to be wider in focus), but overall I would give it a 7/10.

Read Full Post »

In April 2002 Rob Thomsett released his successful book Radical Project Management. Contained within was a little gem known as Project Success Sliders.

In normal Project Management there is a well known term called ‘the Iron Triangle’. This triangle represents the three key facets that a Project Manager needs to normally watch like a hawk – the scope, the cost and the time. In non-Agile Project Management these three elements are commonly fixed. In Agile Project Management these elements are defined at the start of the project, however as circumstances change we want a trade-off to occur. If we can’t meet our initial proposed scope, cost, time and quality then something has to give.

Generally I don’t allow team satisfaction to be traded off, it goes directly against sustainable pace and good leadership. Similarly I don’t normally have stakeholder satisfaction because ultimately that is a gauge of the four elements (scope, cost, time and quality) at play.

So what Project Success Sliders allows you to do is have an upfront frank discussion to acknowledge that it is hard to meet all four elements and that if something has to give what is it? Not all four can be possibly fixed. One will always be the most flexible, one will always be the most fixed. Two will be somewhere in the middle. This is about a conversation to understand critical needs.

So why do I raise the subject of Project Success Sliders?

In organisations I believe there is a similar model at play. I call them, for lack of anything incredibly imaginative, Organisational Success Sliders. Rather than the slider elements at play being time, cost, scope and quality we instead have Shareholder Value, Employee Engagement, Customer Delight, Supplier/Partner Symbiosis and lastly Environmental/Ethical Responsibility. The first three should be fairly obvious. The last two might require some explanations – supplier/partner symbiosis is about a mutually beneficial relationship. It isn’t healthy to screw your suppliers value down to nothing. It results in a loose/loose situation. Environment/Ethical Responsibility is about being corporately responsible with the world. How much is an organisation investing in being sustainable? In being carbon neutral? In ensuring that its suppliers aren’t using child labour in China?

Most organisations have Organisational Success Sliders set to Shareholder Value fixed at priority 1. Employee Engagement and Customer Delight are in the 2/3 slots, usually with customers winning over employee satisfaction. Supplier/Partner Symbiosis and Environmental/Ethical Responsibility are both vying for the last spot as the most flexible.

I want organisations to think of more than just Shareholder Value. I want them to consciously choose whether to put Shareholders above and beyond all other elements. Should these elements really be prioritized? Probably not, but they are, so call it for what it is and make is clear where the priorities lie. Only through firstly making this constraint transparent do we free ourselves to question it.

Read Full Post »

I have an hour to kill in the Vienna hotel I am staying at so I thought I would take the opportunity to do a brain dump of what I have seen and done Agile (or technologically related) as a bit of a midrospective:

  • Telstra are evil. I tried to get my phone working with an Austrian SIM card and the phone is hard coded to not allow any other SIM card to work in it. Several internet searches have found that this is due to the way Telstra and Apple setup the phones.
  • Apple is evil. For some reason unbeknown to me apple products don’t work on 95% of WiFi connections here (including my hotel, which was one of the reasons why I choose it). There is nothing worse than watching my hubby surf at ease on his android and me being devoid of any interwebs.
  • Austrian keyboards are weird. The z and y are around the other way. Count how many ‘Y’s there are in this blog. Each one of them I typed a ‘z’ in originally. Many of the special keys are in different spots or work using the right Shift or Alt.
  • I am finding some intriguing parallels between the history of Vienna and Agile. When I get back home I will write a more detailed blog but in essence there is definately a theme of people who were considered revolutionaries, who were incredibly passionate and entreprenurial but were ostricized for most of their lives. How they dealt with it and the ethics that they had I found very inspirational.
  • I have just finished reading Buyology whilst here. Again I will probably blog about it but again found huge parallels to Agile and Lean Startups. If you haven’t read this book then get a copy – it is eye opening and highly educational.

Non Agile related:

  • Surprisingly there is very little sunshine in Summer (it has rained every day)
  • Nothing opens until generally 10am. This would not be an issue if I didn’t wake up at 6am every morning. On the upside most things are open till late at night.
  • I’m sleeping really well. Walking about 7 hours every day will do that for you.
  • I need to buy another memory card. I have been taking about 400 photos per day (and processing them back to 100 at night). Vienna is truly an incredibly beautiful city. If you love jaw dropping architecture every time you walk around a corner then this is a must see destination for you.

Read Full Post »

For a while now I have been discombombulated. The cause of my confusion and desperation has been around the issue of management. 

I am not talking about Leadership. Leaders are people (whether in a position of hierarchy or not) that naturally foster an environment of collaboration, understanding and consensus. No, what I am talking about is the ability to influence creatively or constructively criticise the status quo to a person considered your “superior”. I want to use the term superior loosely knowing how much people will hate it, to represent an authority figure in a command and control environment. After all, Managers who aren’t getting the message about Leadership really do think they are superior (how many sweeping generalisations can I put in one post?).

I have come to the conclusion that a good number of employee frustrations are systemic from the culture; a culture which is powered by management. It is incredibly difficult to change culture from the bottom up. It can be influenced from the bottom up but there is a point where it cannot stretch anymore without management buy-in to the culture change. Failing senior management or C-suite buy-in to seriously throw money into changing a culture (yes culture change costs currency) I have been pondering how it may ever be possible for this problem to fixed in any way.

The C-suite don’t get it. Either they weren’t educated in it, don’t want to be educated in it or are too busy improving shareholder value. They are the Lords of this day and age, and how much did the Lords ever care about their serfs? Middle management are the Courtiers. Lower management are the cooks. Everyone else is working in the field.

Groups like STOOS believe that they can solve this problem through conferences targeted to the C-suite.  It is an interesting approach, but the sort of C-suite executives that will attend are the ones that I think for the most part are already on the journey or starting to question their belief system. It will make some in roads but I fear it won’t cross the chasm and I desperately ache for this chasm to be crossed. More needs to be done.

Others believe that they need to be right-shifted. I am admittedly still looking into this but have yet to get into significant enough depth to see if there is a mechanism to induce the chasm crossing.

I have been relaying this story a lot recently -

When a new person joins your team watch them closely. Watch how they learn and what they say. Watch how people react to what they say. Start to gather a pattern. What you will find is that when people join an organisation they are highly motivated. This is called the “Honeymoon phase”. The organisation is a veritible field of endless possibilities. They have been sold a dream by a HR department and manager.

The new person will listen for a while, enveloping themselves in the culture, trying to best see where they fit. They will start critically thinking early. They will ask questions like “Why do you do <insert task> that way?” They are trying to frame the task around their mind-map of how they have done it before and are judging it for efficiency and common sense. Failing a suitable answer they will delve further. Naturally they will gravitate towards the 5-whys, despite never hearing of Lean.

Eventually their critical thinking will be blocked by the “Monkey and the Banana syndrome” response. A root cause is not met and the first brick on the wall of critical thinking resistance is placed. As their first few weeks progress the same scenarios occur. Their brick wall begins to get higher.

When the wall reaches their knees self doubt sets in. Naturally they try to fight it, but in a different way. Rather than taking a critical thinking approach they will try a different tact. They will try the innovation path – providing suggestions of how they have seen it done elsewhere and the benefits that they had in doing it that way. They will get more Monkey and Banana syndrome responses or “We have tried that before, it didn’t work because <x> and <y>”, then the new person is back to the same lack of response to critical thinking. Innovation bricks now get added to the pile that is up to their knees.

After a few months their wall is up to their eyes and they can no longer see over the wall. There is no vision. No hope. The organisations culture is now embedded in them.

Sometimes I am asked what the Monkey and Banana syndrome is (usually younger people who haven’t heard it before). For those unfamiliar with it this is how it was told to me about fifteen years ago. I haven’t ever read the internet version so it may be a little different for those that have read it:

This is a story based upon a scientific experiment. A scientist puts into a large white room a metal ladder with a finger of bananas hanging from the ceiling. The middle step of the ladder is rigged to set an electric shock through the metal floor of the room. The scientist then lets in five monkeys. The monkeys excitedly see the bananas. One scrambles up the ladder and gets to the middle step. An electric shock is sent through the floor and ladder with all monkeys get shocked. The second time the monkey hits the middle step the other monkeys begin to get the picture. On the third attempt the monkeys pull the hopeful monkey on the ladder down and beat him up.

Subsequent attempts to climb the ladder result in beatings. The scientist then takes out one monkey and replaces them with a brand new monkey. This monkey sees the bananas and proceeds towards the ladder. He only gets two steps up before he is pulled down and beaten. He never knows why but after the second attempt he knows that if he tries to get up the ladder his peers will exert physical pressure.

The scientist continues to rotate the original set of monkeys out one by one and replace them with new monkeys. Eventually the room is filled of monkeys that have no understanding about why they are not allowed up the ladder but that if someone ever tries they should be beaten up.

“That’s just the way we have always done it around here.”

So you can see by my thought process that unlike some other thought leaders, I actually don’t think the ability to critically think is a lost art despite many years of behavioural conditioning supposedly beating this out of us. I believe critical thinking is a subconscious ability that we all have and continue to have despite command and control overriding it almost every single day. It is there. We have just given up trying to use it because no one is listening.

To get out of this endless rut I see a few possible solutions:

  1. Managers get better listening skills. Right now that you are done laughing, what are the other options.
  2. People get better persuasion and communication skills. On a scale of 1 to 10, 1 being highly unlikely to work and 10 being certain to work I probably rate this a 3.
  3. Have scientific metrics that prove empowerment, innovation and critical thinking are advantagous to the bottom line of an organisation. I am pretty sure the information is out there, but this depends on solution 1, and well, there goes that idea.
  4. Revolt. This is essentially option 2 but done on a less individualistic scale and more ganging up. This does happen naturally in teams but this method seeks pre-emptive goal setting. Despite being able to do this it will only work for one level above the team and from there will fizzle to get any traction, unless you get many teams to revolt at once and that is getting beyond the realm of possibility. Someone suggested to me that as an analogy it is like the monkeys ignoring the ladder and hopping on top of each other to form a monkey pyramid to get to the bananas.
  5. Teams get better facilitation skills and all team sessions have a pre-set, well skilled facilitator. In a team environment I give this a 5 to work, but outside of a team environment we are back to the original problem. That said you could encourage an environment where all suggestions of process change and innovation are raised through a facilitated team environment (sounds very Agile doesn’t it?)
  6. Enable a way to give a singular voice a pedastal. I am toying with an approach for this. I don’t think this will realistically happen inside of an organisation but I wonder if there is a means to force more social pressure for the C-suite to change their belief system.

What do you think? Are there other options to open up the eyes and ears of management?

Read Full Post »

Moneyball has been credited within the Lean Startup community as a classic example of some of their principles.

I thought for those who haven’t had an opportunity to watch it that I would note some of the more powerful statements made in the movie. Some are slightly modified to apply outside of baseball so that you can potentially better relate it to your own environment:

  • The first guy through the wall always gets bloody.
  • This is threatening not just their business, this is threatening their livelihood. It’s threatening their jobs, it’s threatening the way that they do things.
    And every time that happens, whether it is a government, or the way they do their business, or whatever it is, the people that are holding the reigns – their hands on the switch, they go bat shit crazy.
  • Anyone that’s not changing – they’re dinosaurs.
  • There is an epidemic failure in the system to understand what is really happening. This leads people who run their teams to mis-manage their teams.
  • They are asking all the wrong questions. If I say it to someone I am ostracized. I’m a leper.

Read Full Post »

I have been pondering since reading Steve Denning’s on Fighting the Kool-Aid of Stock Based Compensation  and Umair Haque’s Harvard Business Review’s The Economic Roots of your Life Crisis about perilous journey that we might be on. Take a step back for a moment and consider some cause and effect.

When my parents worked it was pretty much considered a job for life. Most of my friends around the same age had similar experiences for their parents.

When I entered the permanent workforce in 1997 this mentality was beginning to peter out. Big organisation after big organisations that I worked for all went through regular retrenchment periods. Some were as short as every six months, others in two yearly cycles.

They called them different names – offshoring, outsourcing, departmental restructure, voluntary reduced hours; but the intent was always the same – cut the bottom line.

Thankfully I have never been directly impacted by such acts but it has led me to a feeling of constant insecurity. I have never felt safe in a job.Our clock is ticking down

Does anyone else think that this is crazy? What is the point of ever being a permanent employee if you cannot feel safe (naturally excluding performance issues)? At least a contractor knows when their date is going to end. The rest of us that were after secure jobs to pay our mortgages and support our tribe of kids wanted something that we could depend upon. But we cannot depend upon it. We are like a character of “In Time“, our clock is ticking down, but we have no idea when the timer is going to reach zero.

Because of my parent’s experiences within companies I was raised with the belief “You look after your company because your company will look after you.” Extra hours was sometimes part of that deal. Towing the company line as well. But what I was experiencing was something considerably different. It didn’t appear like the organisations cared about its most long term employees (they were commonly the first ones to go). It shattered my illusions. It left a void in my belief system.

I am not the only Generation X person who has been left feeling like they are in the Matrix. Companies no longer care about their people, they care about the almighty shareholder seemingly above and beyond any other competing priorities.

So as anyone with a dysfunctional belief system does, they find a new belief to fulfill this empty hole. We believe that if the company doesn’t care about us then we need to care about ourselves. What behaviours and patterns emerge from this?

We appear selfish. It is all about what we can get right now. We want recognition right now. We don’t feel obliged to have to stay at an organisation for too long (especially if the organisation loves to retrench frequently). We see no problem with being headhunted. We see no problem with doing the work for the hours that we are meant to be paid and no more. This makes us look lazy.

Does this sound familiar? Take a look at the wikipedia definition of a Generation Y:

 Studies predict that Generation Y will switch jobs frequently, holding far more than Generation X due to their great expectations.[70] The UK’s Institute of Leadership & Management researched the gap in understanding between Generation Y recruits and their managers in collaboration with Ashridge Business School.[71] The findings included high expectations for advancement, salary and for a coaching relationship with their manager.

Is this singularly minded focus on shareholder value turning us all into Generation Y thinkers?

Read Full Post »

The Smithsonian is the world’s largest museum and research complex with hundreds of affiliated museums.

The Stoosonian is much the same but switch up museum with people and thought leaders. It could be the collective noun for people focussed on building such a network focussed on leadership in the same guise that the Agile Alliance crowd marketed the Agile Manifesto.

If you haven’t heard of Stoos then you might have been on holidays and not reading or following the twitter streams in the Agile community. In just one week I heard about it from three separate sources so the community is certainly abuzz. And I hope rightly so.

So what is Stoos? Take a look at their opening statement at http://www.stoosnetwork.org

Reflecting on leadership in organizations today, we find ourselves in a bit of a mess. We see reliance on linear, mechanistic thinking, companies focusing more on stock price than delighting customers, and knowledge workers whose voices are ignored by the bosses who direct them. All these factors are reflected in the current economic crisis, increased inequity, bankruptcies and widespread disillusionment.

There has to be a better way.

In January 2012, a diverse group of twenty one people including senior executives, business strategists, managers, academics, and lean/agile development practitioners from four continents, met in Stoos, Switzerland. We believe that we uncovered some of the common characteristics of that better way.

Stoos SwitzerlandFrom the stoos network page there is a myriad of information that can be found from the closed sessions that were held. A good portion of content has started being posted on LinkedIn and on a variety of blogs and other mediums including #stoos on twitter. In fact, the wide variety of mediums does mean you have the traverse around a bit to gleam everything that is being talked about but without a doubt the social stream is incredibly active.

I spent a few nights taking everything in and having a look around. The hype from colleagues lived up to my initial delve and then I began to test the waters on a few questions that I had. My first concern had been the target Stakeholder list. Now let me start that I am highly impressed that the group took the effort to do this list, debate it and then re-evaluate it. But two things jumped out on that list (and a third now that I have received some responses):

  • The C-section (eg CIOs, CEOs, etc) are rated so low (before and after),
  • First line management is non existent (but maybe that is due to deviations in definition of middle management)
  • Shareholders are rated at 0

The reason why I was concerned in particular about the C-section being so low is that every time I have done an Agile transformation within an organisation it absolutely had to have C-section level buy-in. This wasn’t an optional element. It was critical to success. Without C-section level buy-in teams were left to do Agile in stealth. Sure they worked better than before but there was a upper bound of roadblocks that endlessly re-0ccured and never got addressed because there was no organisational focus on being Agile. Culture of the team subtly changed but without C-section buy-in the culture of the organisation would never change.

This is critical to not miss. Agile, to get the benefit, requires cultural transformation. The Leadership problem is no different – in fact it is more often then not Leadership that drives culture. I’m not just talking about first line managers but also middle managers, CIOs and CEOs.

I then did a deep dive at the problem analysis done. The Stoos problem mind mapAgain I want to take a moment and congratulate the Stoos team on the job they did on generating this starting diagram. I would imagine they spent a few hours on this and as a starting map I think it covers most of the key points. To get it past 80/20 right it would have likely taken the whole two days.

If you take a look at the top two (not necessarily by priority) root causes you see shareholders and C-section management as the cause.

So my concern is that without doing something to address those two root causes that all this effort might be in vain.

Side note: would love to see the 5 whys applied to the root causes because they aren’t base root – eg Why are leadership skills missing in today’s managers?

Now I posed the question of C-section being non targeted in the twitter stream and was given a couple of nice links which is great information and a step in the right direction but again isn’t the root cause. The root cause as in the article is lack of education – and who do we need to educate? – the C-section, shareholders, and future to-be C-managers. Which is why I am happy that educators are high on the target audience. So there is hope, but maybe not in my lifetime.

What I love about the Stoos community thus far:

  • They are responsive, they are listening and they have some beautifully deep thinkers in there. A few of the questions that popped up in my mind today whilst I was a road-trip I was amazed to have found others ask and have had answers/responses to.
  • There is an appreciation that the command and control culture is thousands of years old – this is a very deeply embedded behavioural human trait. I am curious if it is neurologically driven somehow.
  • There is an appreciation that we actually have the answers on how to lead – it is just that for some reason it is not disseminating as expected. This is where I think some deep thinking root cause analysis needs to be directed towards.

As a test I asked a friend of mine who leads a team of ten about their leadership.

Do you think you are a leader or a manager?
A little of both. More detail then given.

How do you think your team perceives you – more as a leader or a manager?
Probably a manager.

Why did you go into management as a field?
For the money.

Not because you enjoy working with people?
No. I was smart, it was expected of me to progress that way.

How much time do you spend learning of new leadership and management techniques?
None. I have no time for that sort of stuff. I am too busy. 

So if you weren’t so busy you would spend some time learning how to be a better leader/manager?
Probably not. 

I could have continued going on to find the root cause but at that time my friend was starting to get the picture that I wasn’t playing nicely. Getting honest answers on this is going to be hard but we need to get some broad understanding (ie real metrics lean start-up style) to make sure we are going to make a dent in this massive global problem.

So lastly I want to say thank-you to the Stoos group for having the guts to tackle this and to make a great start on it. I am pleased that the group has such a diverse set of thinkers but would love to see a few other thoughtleaders included in the list – my pick would be someone who represents motivation (eg Dan Pink), someone for crowdscourcing (eg Dan Tapscott) and someone from the field of Neuroscience (to be honest Peter Burrows wouldn’t be so bad as he conceptually understands Agile and more importantly has some interesting team dynamic theories).

Keep it up and don’t take this blog as a big rant of criticism – the good certainly way outweighs the bad.

Read Full Post »

Older Posts »

Follow

Get every new post delivered to your Inbox.

Join 604 other followers