Tag Archives: Leadership

Business Agility for Beginners

Rufous Hummingbird_Alan Schmierer_640x516

Flickr Commons, Rufous Hummingbird – Alan Schmierer

There’s a new crop of thinkers who are noticing that while Agile and Lean Startup approaches are being enthusiastically embraced by organisations, they are mostly being implemented at a team level. The promised improvements, such as quicker delivery of product and happier teams may well be there, but the organisational improvements that will lead to innovation and customer value are not fully realised.

Barry O’Reilly summarises this perfectly when he explains how difficult it is for organisations to implement Agile and Lean Startup across the enterprise. He explains, “In most cases it [is] impossible to realize anything more than incremental improvements because only part of the organization [has] changed – and that part need[s] to work with the rest of the organization, which expect[s] them to behave in the traditional way.”

Jez Humble, Joanne Molesky and Barry O’Reilly’s fabulous book, Lean Enterprise: How High Performance Organisations Innovate at Scale, describes how successful organisations rethink everything, from financial management and governance, to risk and compliance, to systems architecture, to program, portfolio and requirements management, in the pursuit of radically improved performance.

Business Agility is about developing the patterns across an entire organisation to fulfil on the promise of Agile and Lean Startup:

  • Minimum viable everything – product, experience and process
  • Measure outcomes (value), not outputs (stuff done)
  • Experiment to learn – create a generative safe to try culture to continuously improve

Through meeting with thinkers at the forefront of Business Agility; Barry O’Reilly and Pat Reed, I’ve collated these questions to help organisations grow Business Agility.

Minimum Viable Everything

Do our processes generate value, rather than hold us back?

Can we map how much time we spend on value generation versus being busy?

Do we create “won’t do” lists to focus on the most valuable activities we should be doing?

Measure Outcomes no Outputs

Do we measure value in terms of making an impactful difference to a customer or to the business, with the least amount of output – more value at less cost?

Do we make value visible throughout our product development cycle?

Do we have a value model that provides a clear line of sight for everyone in the organisation on the work they do and the outcome desired?

Do our leaders articulate what success looks like in measurable terms and with real clarity, so the whole organisation can align on delivering value?

Do our metrics and reward systems measure outcomes (value) not output (more stuff done)?

Do our metrics measure the cost of value and time to value?

Do we balance business value and customer value for a sustainable organisation?

Experiment to learn

Are we an organisation that can thrive in extreme change?

Do we have feedback loops to ensure we understand:

  1. How we’re doing based on our commitments?
  2. How quickly we are learning and responding to customer feedback?
  3. If we are still doing the right thing, or if we need to change our goals based on shifting circumstances and priorities?

Do we accept that there are many unknowns, and recognise that everything is an experiment to discover where value actually lies?

Do we define tests as part of the experiment? Whether it’s a feature in a product, or a change to a process, do we identify the value which should be improved by the work, and then measure if it has been achieved?

Do we have a tolerance for failure, by testing first with a hypothesis, and being open to learning when the hypothesis proves not to be true?

Do we adapt quickly and celebrate learning?

Do we generate knowledge across the organisation by sharing the results of experiments, especially the failures?

Do we avoid big failures by breaking big challenges into thin slice experiments?

Do we accelerate feedback loops by shrinking the learning cycle to days or weeks and iterate?

Organisations on their way to Business Agility will recognise the above questions as aspirational. They will also recognise that opportunities to improve are everywhere, or as Barry O’Reilly expresses, “not just in the products or services we build, but in the way we behave and interact and most importantly, in the way we think”.

Agile leadership – questions for innovation & continuous improvement

Brick 101 - LEGO Ideas Research Institute - Flickr Commons

Brick 101, LEGO Ideas Research Institute, Flickr Commons

What are the questions great Agile leaders ask themselves to drive continuous improvement and innovation?

My previous blog explained how great Agile leaders, as coaches, business drivers, purveyors of purpose and enablers, acknowledge the success of their teams and reward right behaviour. How do these four roles shape leaders’ approach to continuous improvement and innovation?

Applying the coaching lens to continuous improvement, great leaders ask: Do I teach my teams how to embed continuous improvement through Lean and Agile techniques such as retros, kaizen and improvement katas?

Applying the business lens to continuous improvement, great leaders ask: Do I reward individuals and teams who regularly implement improvement activities to maximise lifecycle profits?

Applying the purpose lens to continuous improvement, great leaders ask: Do I energise and engage my people to drive continuous improvement?

Applying the enablement lens to continuous improvement, great leaders ask: Do I make time for my team to implement improvement? Do my people have the autonomy to implement improvement?

Jez Humble and Barry O’Reilly’s 2014 Lean Enterprise: How High Performance Organizations Innovate at Scale is truly a wonderful blueprint for developing the sort of generative company culture that leads to innovation.

These are some questions that Agile leaders ask to create such a generative culture.

Applying the coaching lens to innovation, great leaders ask: Do I model and teach collaboration, risk sharing and acceptance of failure in order to learn?

Applying the business lens to innovation, great leaders ask: Do I promote ways of working that foster innovation through continuous experimentation?

Do I run hack days?

Do I reward great ideas?

Applying the purpose lens to innovation, great leaders ask: Do I recognise that without autonomy, there will be no opportunity for my people to innovate?

Applying the enablement lens to innovation, great leaders ask: Do I create a generative culture that enables my people to think innovatively to resolve impediments?

Appelo makes it sound easy when he says, “We aim for a more powerful system, not better controlled people”.

What other questions, can we, as leaders ask, to propel continuous improvement and innovation?

Agile leadership – rewarding right behaviour & acknowledging success

Doughnuts - Amy - Flickr Commons

Doughnuts, Amy, Flickr Commons

What are the questions great Agile leaders ask themselves about acknowledging success and rewarding right behaviour?

My previous blog explained how great Agile leaders support learning, as coaches, business drivers, purveyors of purpose and enablers. How do these four roles shape leaders’ approach to acknowledging success and rewarding right behaviour?

Applying the coaching lens to entrenching success and rewarding right behaviour, great leaders ask: Do I teach individuals and teams that it is important to acknowledge and celebrate success?

Applying the business lens to entrenching success and rewarding right behaviour, great leaders ask: Do I measure the success of individuals and teams simply by their output, or by their focus on activities that relate to the core value stream?

Do I bring doughnuts when we get through a tough story or sprint? Do I know when my teams have got through a tough story or sprint?

Laugh you may, but what I’m emphasising is a leadership style that recognises the connection between acknowledging people’s effort and business success.

Do I wait until release of a product to acknowledge the effort of those involved, or do I thank my team regularly?

Applying the purpose lens to entrenching success and rewarding right behaviour, great leaders ask: Do my people feel valued? How do I know this?

Applying the enablement lens to entrenching success and rewarding right behaviour, great leaders ask: Do I reward people who resolve problems across the entire value stream?

I guess the antithesis of this is managers who reward people who do whatever it takes to get something across the line, regardless of whether it creates other issues, such as technical debt, poor staff morale or unsustainable processes.

I perceived the joy on a fellow’s face this week, when a leader acknowledged how the work he had done directly contributed to relieving a bunch of problem tickets in a service delivery queue. It’s not hard to acknowledge success and reward right behaviour. Are your leaders doing this?

Read on to learn the questions great Agile leaders ask to drive innovation and continuous improvement.

Agile leadership & learning – a new paradigm

Scrumtrooper Image - Axis Agile - Used with permission

Scrumtrooper image, Axis Agile, Used with permission

What are the questions great Agile leaders ask themselves about learning?

My previous blog explained how great Agile leaders support delivery, as coaches, business drivers, purveyors of purpose and enablers. How do these four roles shape leaders’ approach to learning?

Applying the coaching lens to learning, great leaders ask: Do I share knowledge, skills and perspectives with my people, to foster their professional growth?

Do I understand the role that mastery plays in helping individuals feel more engaged in the work they do?

Do I emphasise and model the value of life-long learning?

Am I the person recommending books, meetups and stuff I’ve read on the Internet?

Do I blog, respond to blogs or start conversations on Slack or Twitter?

Applying the business lens to learning, great leaders ask: Do I foster practices that drive experimentation and learning, to maximise product lifecycle profits?

Applying the purpose lens to learning, great leaders ask: Do I help my people understand the value of what they’re delivering, so that they develop a sense of purpose?

This of course references Dan Pink’s 2009 publication Drive: The Surprising Truth About What Motivates Us. W. Edwards Deming in fact predates Pink when he writes in Out of the Crisis in 1982, “The aim of leadership should be to …bring pride of workmanship to people”. In 1988 Deming revised this phrase to “joy of workmanship” and it refers to purpose.

Since Pink’s 2009 publication there have been a flurry of books on the topic of purpose, including Appelo in 2011 and unsurprisingly a couple of great little TED books from last year, Beyond Measure: The Big Impact of Small Changes, by Margaret Heffernan and Why We Work by Barry Schwartz.

I really like the work of Steve Denning on the topic of purpose and delivery, so I’ll quote him here:
“Delighting other people is inherently motivating…
The meaning of work isn’t in the bread that we’re baking; it’s in the enjoyment the customers get from eating the bread.
The meaning of work isn’t in the words the actor is reciting; it’s in the response of the audience to those words.”

So I’ll add to the list of questions that great leaders ask themselves: Do I expose my people to customers, suppliers and other world views to connect them with customers?

Applying the enablement lens to learning, great leaders ask: Do I create a culture where it is safe to fail? This question of course comes from an understanding that we learn from both failure and success.

Do I reward teams that experiment to learn?

Do I take a systems approach to learning, understanding that to resolve impediments I must see the whole, rather than just the component parts?

Do I use lean techniques to focus on the entire value stream, to measure and learn?

Am I am a driver for development of strong chapters and communities of practice, to support both new and expert practitioners?

In an interview online, Carsales.com CIO Ajay Bhatia talks about his leaders’ engagement in communities of practice:
“We run a book club for the leadership team across product and technology, where we discuss the most important things we picked out from the book and go away and try and implement those things among our teams… Our book club has been so successful that now it is no longer only limited to the leadership team and the number of members is ever increasing. This is creating a culture where we are constantly picking up new ideas and ensuring what we build in Australia is no less than world class.”

Jeff Smith, CIO of IBM, said in the keynote address at Agile Australia 2016, “it’s important for people to try stuff, but not get the OK from me to do it”.

Great Agile leaders know that learning isn’t just about sitting with individuals once a year to set a learning plan. It’s about always asking, “What did you try? What did you learn?”

Do you model these behaviours? Do you know leaders who have changed the paradigm?

Read on to learn the questions great Agile leaders ask about rewarding right behaviour and celebrating success.

Agile leadership & delivery – it’s not about pizza boxes

190310 - Losers of Friday Night Rejoice - Lis Ferla - Flickr Commons

Losers of Friday Night Rejoice, Lis Ferla, Flickr Commons

What are the questions great Agile leaders ask about themselves about delivery?

My previous blog explained how great Agile leaders communicate as coaches, business drivers, purveyors of purpose and enablers. How do these four roles shape leaders’ approach to delivery?

Applying the coaching lens to delivery, great leaders ask themselves: Do I give my people the Agile expertise and tools to deliver?

Applying the business lens to delivery, great leaders ask: Do I ensure that my teams work at a sustainable rate to maximise delivery?

You guys know that the best measure of this is the smell of pizza – right? Where you see a stack of empty pizza boxes in the office on Monday morning, then a team has worked over the weekend. When the smell of pizza on a Monday morning is the norm, then the team isn’t working at a sustainable pace.

Tom DeMarco in his classic 2001 book, Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency, says that “an increasingly common bit of organizational folklore holds that pressure improves performance and that maximum performance can occur only in the presence of maximum pressure. This idea, though deeply embedded in our culture, doesn’t stand up to examination in the light of day”

Managers who encourage their people to commit to the right amount of work and who reward those who meet the goals of the sprint time and time again, understand that sustainable delivery leads to predictable business outcomes.

Applying the purpose lens to delivery, great leaders ask: Do I provide the goal and strategic direction, allowing my people to define how they meet requirements? Do I trust my people to figure out how to meet requirements?

Nigel Dalton, CIO of REA Group, comments in an ITNews interview online, on the paradigm of leaders providing strategic direction and thus allowing people to deliver. He describes that Toyota has strict rules about what executives spend their time focused on:
“In Toyota’s hierarchy, the president and executive are only permitted to think about horizons two and three,
The people at the coalface must run and operate horizon one.
As a CIO, I am always drawn to the challenges of today – challenges around IT security, developer recruitment, or how we use cloud. But I have to trust the teams to manage horizon one.”

Applying the enablement lens to delivery, great leaders ask: Do I trust my people to resolve problems? Do I challenge them to balance delivery with managing accrual of technical debt?

Dipesh Pala, IBM’s Agile Capability Leader for Asia Pacific, exhorted leaders at Agile Australia 2016 to “shift from managing results, to designing environments that encourage results”.

At the same conference, Jeff Smith, CIO of IBM, remarked, in reference to a customer service help desk, that using Kanban was critical in delivery. He explained that “the ability to pull tasks, rather than being given them” was what created swift and effective delivery.

He went on to explain that “if we fundamentally change the way things work, it gets better”. I was struck by the simplicity and sense in this statement. Great Agile leaders are enablers for delivery. That is their job!

Are your leaders asking the right questions about delivery?

Read on to understand the new Agile leadership paradigm for learning.

Agile leadership & communication – so many opportunities

The Garage - Peter Kaminski - Flickr Commons

The HP Garage, Peter Kaminski, Flickr Commons

What are the questions great Agile leaders ask themselves about communication?

My previous blog explained how great Agile leaders apply their role as coaches, business drivers, purveyors of purpose and enablers to decision making. How do these four roles shape how leaders approach communication?

Applying the coaching lens to communication, great leaders ask: Is communication with my people face to face, authentic and regular? Do my people feel comfortable to initiate contact with me as much as I do with them?

Bill Hewlett and David Packard of Hewlett Packard fame, incepted the practice of “management by walking around”. Until they stepped down from HP in the 1970s, they interacted with their employees in an unplanned way to check equipment, understand the status of work and engage people in authentic conversations.

Appelo describes “management by sitting around” which of course means taking the opportunity to sit with your various teams, hear what they are working on and interact with them. If this isn’t possible, then he suggests “management by Skyping around” which is unfortunately less spontaneous.

I remain astonished by my observations in workplaces, of how frequently managers miss opportunities to interact with their people in an authentic and regular way. Standup is the time to hear how teams are progressing, showcases, even more so.

Do I know those I manage on a personal level?

Appelo suggests imagining a personal map of your people. Do I know what my people like to do outside of work, how many kids they have, who they are friendly with in the workplace? When you start this exercise you might be astounded at how little you know about your people.

Am I open to being influenced by those I manage?

Have I created an environment where individuals and teams are able to disagree where appropriate, negotiate, compromise, agree and commit?

Applying the business lens to communication, great leaders ask: Do I have a Kanban board to communicate progress on my goals?

Do I use Agile practices like standups, information radiators, blogs and conversation platforms like Slack, to establish the sort of two way communication required to maximise product lifecycle profits?

Do I insist on right fit ways to communicate the status of work, such as through conversations, standups, information radiators and A3 canvases, instead of reports and gannt charts?

Applying the purpose lens to communication, great leaders ask: Am I out and about interacting with my people to create opportunities for two-way conversations and interactions about our organisation’s purpose and strategy? Do I favour two-way communication to convey purpose and strategy, over group emails and formal forum events?

I’m not suggesting that whole organisation events shouldn’t happen, but where these are a one way conversation, with leaders pushing information to folks, and folks feeling uncomfortable in asking a question, it isn’t an effective two-way conversation about strategy.

Applying the enablement lens to communication, great leaders ask: Am I effective communicating across organisational boundaries and hierarchies? Is my communication underpinned by an understanding of the complexity of the organisation? Do I communicate to effect change within a complex system?

Connected communication is at the heart of effective leadership. Do the Agile leaders you know ask themselves these questions?

Read on to learn how great Agile leaders succeed at delivery.

 

Agile leadership & decision making – new patterns, new questions

Brain - Chris White - Flickr Commons.jpg

Brain, Chris White, Flikr Commons

What are the questions great Agile leaders ask about themselves decision making?

My previous blog explained how Agile leaders of today understand themselves to be coaches, business drivers, purveyors of purpose and enablers. How do these four roles shape how leaders approach decision making?

Applying a coaching lens to decision making and problem solving, great leaders ask: Do I teach my teams a model of delegated decision making?

Jurgen Appelo explains that “we can only escape [the] typical management trap and increase the quality of work when we distribute control in our organisation.” Comparing an organisation to a brain, Appelo continues that “all around us (and inside us) complex systems self-organise successfully because control is rarely centralised.”

The level of delegation will of course depend on the maturity of the team, the status of its work and the impact of decisions on the organisation.

Drawing on Reinertson’s work in Managing the Design Factory Appelo encourages teams to create delegation boards that clarify what level of authority teams have across different activities.

The seven levels of delegation that Appelo defines are:

  1. Tell – making the decision as the manager
  2. Sell – convincing people of the decision
  3. Consult – getting input from the team before decision
  4. Agree – making the decision together with team
  5. Advise – influencing the decision made by team
  6. Inquire – seeking feedback after decision by the team
  7. Delegate – no influencing, just letting the team work it out

Applying a business lens to decision making and problem solving, great leaders ask: Do I delegate enough control to allow my people to maximise product lifecycle profits?

A Product Owner, responsible for defining the features for a new app, needs the right level of authority to make decisions about which features should be built first second or not at all.

A Scrum Master shaping people and processes within a team needs authority to ensure folks in the team have the right equipment to build profitable products.

Applying a purpose lens to decision making and problem solving, great leaders ask: Have I conveyed the organisation’s strategy to my people, so that they have the right information for decision making?

I think about one organisation in which I worked where strategy visualisation happened on walls in a glass meeting room, but where those walls were covered in brown paper to prevent people outside the room seeing the information.

How different is this from the strategy boards on full view at companies like REA Group, Carsales and Envato. Where strategic conversations happen behind closed doors, teams simply won’t have the information they need to produce the right output.

Applying an enablement lens to decision making and problem solving, great leaders ask: Does my team have a delegation board that encourages them to make decisions and solve problems as appropriate?

David Marquet’s Turn the Ship Around talks about shifting the psychological ownership of problems and solutions using a simple change in language from a “Leader-Follower” pattern to a “Leader-Leader” pattern. Marquet, a former U.S. Navy Submarine Commander, achieved in the leadership and productivity guru Stephen Covey’s words, “the most empowered organisation he’d ever experienced.”

Marquet describes a conversation in the traditional Leader-Follower language sounding like this:
Captain: “Submerge the ship”
Subordinate: “Submerge the ship, aye”

In the Leader-Leader language it would sound like this:
Subordinate: “Captain, I intend to submerge the ship. All crew are below decks, the hatches are shut, the ship is rigged for dive, and we’ve checked the bottom depth.”
Captain: “Is it the right thing to do?”
Subordinate: “Yes sir, our mission requires that we submerge now in order to complete this exercise”
Captain: “Very Well”

An ability to appropriately delegate decision making and problem solving characterises Agile leadership. Do your Agile leaders ask themselves these questions?

Read on to learn the communication questions great Agile leaders ask.

Who is the new Agile leader?

Into the Unknown - Thomas Hawk - Flickr Commons

Into the Unknown, Thomas Hawk, Flikr Commons

My previous blog put a case for why we need a new style of Agile leadership. To enable self-managing teams to contribute and thrive within the complex ecosystem that is the organisation of today, Agile leaders need to understand their role as fourfold:

  1. As a coach; to share knowledge, skills and perspectives to development people
  2. As business driver; to maximise product lifecycle profits
  3. As purveyor of purpose; to connect people with the purpose of what they do
  4. As an enabler; to support  people to thrive within their environment

Even for traditional managers, there’s probably nothing controversial about these four roles, inspired loosely by the thinking of Michael Hamman and Michael Spayd. In fact to varying degrees, traditional managers might even feel that they fulfil these four roles now.

Traditional managers may perceive themselves as coach, in that they expect individuals to develop a learning plan, and if time and budget permit, they support an employee achieving it.

Nigel Dalton, CIO of REA Group, described in an ITNews interview online as, the Godfather of Agile in Australia, describes the role of Agile leader as coach:

“The company is divided into a set of teams focused on a kind of consumer ecosystem where each one is discreet from the others. Commercial property owners is mine; which is the smallest one. [The others are residential property owners and property developers]. We have understood that [there] is a kind of …‘unique customer experience’ in each one of these ecosystems.

[We asked] what if we put a full multidisciplinary team on those, and we chose a collective group to manage it?

Thus, I am not the general manager of commercial real estate – there isn’t one. I am the steward or coach of a group of seven people who are IT, sales, marketing, product, legal, finance, and human resources. Young managers in their thirties, who’ve got every competency to work as a team, and run that 40 million dollar business. I am there as their coach and all the Agile techniques come in under that. It is pretty self-contained and self-directed. It has its purpose and goal that flow down from the main company purpose. We have replicated that across the company – this is the primary structure.”

In traditional management the focus will largely be on the business role. The narrative on this would be “I reward individuals and teams who do whatever it takes to get over the line”.

The purpose role is a tricky one. Barely a middle to large sized enterprise today exists without some sort of mission statement. In traditional management, the existence of this mission statement and some resultant values might be perceived as bringing purpose to people working in an organisation. I can tell you from experience though, that the yearly exercise of requesting folks shoehorn their performance into the predetermined values of the company doesn’t yield much sense of purpose.

And finally to the enablement role. Traditional managers no doubt perceive themselves as enablers. They want their teams to succeed and would do pretty much everything to ensure this happens. I question though whether traditional managers would always take a holistic approach to enabling, seeing their team’s role in success of the whole organisation, rather than just success of the individual team.

Lisa Frazier, in her talk on Agile leadership at Agile Australia 2016, described how an Agile leader enables, by adopting a “follower-centred leadership style”. She cites three behaviours associated with this:

  1. Working for success of your team members above yourself
  2. Actively listening to your team
  3. Being a good follower

My favourite quote ever is from Nigel Dalton, at the same conference: “Leadership is not boss-ship, it’s servant leadership. Don’t ever mistake not being at the front with not being the leader”.

Jeff Smith, CIO of IBM, in the keynote address at Agile Australia 2016, said that “people come to work because they are ambitious and share the mission. The leaders’ job is to remove the obstacles”. Throughout this series of blogs, I’ll explore how great Agile leaders fulfil on their role as enabler.

Throughout this series of posts, I’ll contrast the role of Traditional Managers with Agile Leaders. What happens, when we ask great Agile leaders to reflect on these four roles in relation to the following leadership activities?

  • Decision making & problem solving
  • Communication
  • Delivery
  • Learning
  • Acknowledging success & rewarding right behaviour
  • Continuous improvement
  • Innovation

Read on to discover the questions great Agile leaders ask themselves in realtion to these activities.

 

Why Agile leaders need to ask themselves new questions

steampunk

We know that organisational culture can be shaped by the worst behaviours leaders are willing to tolerate, but can culture be shaped by the best behaviours that leaders are willing to amplify? This was a question I asked myself after hearing Dipesh Pala, IBM Agile Capability Leader for Asia Pacific, speak at Agile Australia 2016.

Last year’s VersionOne State of Agile Survey identified that four of the five top impediments for Agile adoption relate to management. Over a third of respondents cited:

  • Lack of management support
  • Company philosophy or culture at odds with core Agile values
  • External pressure to follow traditional Waterfall processes
  • Lack of support for cultural transition

The first impediment, lack of management support, needs no further comment, but when you think about it, managers also have accountability for company philosophy, pressure to follow Waterfall processes and lack of support for cultural transition.

Let’s start at the beginning, and the beginning is the most dominant style of management today, commonly described as command and control, or traditional.

Command and control was considered effective because our understanding of organisations was that they work something like the picture in this blog post.

Jurgen Appelo, author of Management 3.0 would describe this as complicated. There are many moving parts in this machine. There is also cause and effect. If one part isn’t working, it affects another part of the machine.  It almost certainly takes some time to learn all there is to learn about this machine, but, ultimately it is knowable.

Command and control was considered a way for managers to keep the machine in working order. So complicated means not simple, but ultimately knowable.

Appelo, on the other hand, describes what we know to be true of organisations today – that rather than them being complicated, they are in fact complex.

What is the difference between complicated and complex? Well, picture a rainforest and you can imagine complex.

A good friend of mine’s parents had a holiday house smack bang in the middle of a forest east of Melbourne. I found it a restful place – the river, the bird life and the amazing towering trees. This couple found it less so. So relentless was their weekend activity of cleaning bird poop off the veranda and sweeping the forest floor free of leaves, that they eventually sold the property.

A forest is a complex system. Complex systems exhibit:

  • Feedback loops – part of an output is used for new input
  • Spontaneous order
  • Hierarchical organisation
  • Emergent organisation
  • Numerosity – or an indefinite quantity of individuals

Other examples of complex systems are ecosystems, the universe, Earth’s global climate, the human brain, the stock market, a living cell and even organisations. Appelo describes complex as not simple and never fully knowable, given that too many variables interact.

The current thinking on organisations is that they are in fact complex adaptive systems. A complex adaptive system is a dynamic network of interactions. It is a system in which individual and collective behaviour mutates and self-organises, corresponding to a change-initiating event or collection of events.

Steve Denning also regards organisations as complex systems, but he remarks that it is the shift from semi-skilled to knowledge work, that means we need to re-examine the “unspoken assumptions…of the inevitability of … the practices of traditional management” such as command and control.

The management expert Peter Drucker notes that “Workers throughout history could be ‘supervised’. They could be told what to do, how to do it, how fast to do it and so on. Knowledge workers cannot, in effect, be supervised”

Perhaps the relentless bird poop cleaners and forest floor sweepers were a bit like command and control managers trying in vain to control an ever changing complex adaptive system.

How then can leaders of today enable self-organising teams to contribute and thrive within such an ecosystem? This introduction is the first of an eight part blog that tackles leadership for an Agile organisation.

Read on to understand the new four-fold role of Agile Leaders.

Easy Peasy Agile Leadership

Easy Peasy Agile Leadership

Photo: D Sharon Pruitt, Flikr

I work in Agile transformation, and the truth is, it’s not so easy peasy teaching leaders to change their style. The thing is, the effort to change leaders’ mindsets is worthwhile – it enables Agile teams to thrive.

Traditional managers think like this…

  • I am the manager of my people
  • My team looks to me to solve their problems
  • I shape how individuals and teams work
  • I reward individuals and teams who do whatever it takes to get over the line
  • I expect individuals to develop a learning plan, and if time and budget permit, I support them achieving it
  • I endeavour to reward team achievement at the end of a project, and individual achievement at performance reviews
  • I encourage individuals and teams to innovate, but there’s rarely time to do so

 Agile leaders think like this…

  • I lead through vision, but support as a servant
  • I set the mission, but decentralise problem solving
  • I trust individuals and teams to shape how they work
  • I reward individuals and teams who work at a constant sustainable development pace
  • I am a driver for development of learning opportunities, and make time for my people to achieve their goals
  • I acknowledge the achievements of individuals and teams spontaneously, and encourage celebration of success
  • I foster an innovation culture of cooperation, risk sharing and acceptance of failure in order to learn

What case do you put to leaders to make their mindset Agile?

Agile Leadership:

  • Supports teams working Agile, so we build better products and release more frequently
  • Emphasises continuous improvement, so teams become more productive
  • Increases sharing of best practice, so we keep upskilling our teams
  • Gets teams working at a sustainable pace, so there are fewer absences
  • Enables happier, more autonomous humans, so we retain our people
  • Builds an engaging workplace, so potential employees choose to work for us

If leaders in your organisation still aren’t convinced, then think about quantifying the benefit of better products more frequently, more productive skilled teams and retaining great people!