Speaking at Agile2018!

…And hello again, guys,

I will be speaking at Agile2018 conference in San Diego. Please come see me at the conference, I will happy to talk with you. The talk will be: Organizational Learning: Getting Off the Ground.

Description

Have you ever wondered why is it so hard to instill a culture of learning in your organization? Have you experienced how vital empirical evidence is neglected and critical decisions are instead made based on speculation? Have you ever wondered what’s behind such organizational myopia and how you can help your enterprise overcome it?

Together we’ll immerse deep into organizational mechanisms that prevent enterprises from learning. We will see how existing organizational structure, its regular routines and leadership behavior encourage the certainty bias – an unreasonable confidence in speculative outcomes – and how this inhibits organizational learning.

But our journey won’t stop there. In the most critical part of the talk, we’ll discuss the tools you can use as an organizational leader, facilitator or coach, to address the certainty bias and instill a mindset of learning. We will seek answers in the following areas:
• Creating an environment of psychological safety that enables fearless exploration and ideation
• Establishing cross-cutting feedback loops that make validated learning possible
• Embracing uncertainty and variability in core organizational structures and routines
• Instilling the culture of outcome-oriented decisions

The neglect of organizational learning leads to the worst possible form of waste there is – the focus and energy of the entire organization is thrown at the wrong objectives. Let’s improve this together!

Speaking at Mile High Agile This Year!

Hello folks,

I’m glad to announce that I will have a talk at Mile High Agile this year (May 21, 22, Denver, CO). The topic is “Addressing the Reductionist Mindset”. More detail on the talk below and I will be happy to see you at the conference.

Talk Description

The most critical transformation is not the one that happens with processes and tools. The most important shift is the one that happens in the organization’s mindset and culture. As an industry, we have developed a large number of Lean and Agile practices, and yet the mindset of most of the organizations remains largely the same, relying on Reductionist Thinking – a thought process that is contrary to Agility, Innovation and Product Development Flow.  Addressing the reductionist mindset requires purposeful, focused action on the part of enterprise coaches and transformation agents. In this presentation, Alex Yakyma will discuss the following topics:

  • Certainty Bias and its influence on enterprise practices and policies
  • Establishing a new culture that embraces uncertainty and variability
  • Operating with assumptions and assumption chains in business strategy, user requirements, architecture, implementation strategy, etc.
  • Aligning individual motivation with value delivery
  • Creating flexibility to foster emergent behavior
  • Establishing cross-level learning in the organization

The talk outlines practical advice with respect to the steps in growing a new mindset. The presentation includes a number of organizational anti-patterns as well as suggestions of how to avoid them.

The Problem with Systems Thinking is in… Not Applying It

 

We often hear (and also say) things like: “avoid local optimization”, “optimize the system as a whole”, and so on… Those are very reasonable suggestions. And yet, as many of us know, organizations don’t seem to be very good at it. Actually, most of the time they are not good at this at all! It seems like whenever there’s a slightest opportunity to do some nice little local optimization, they are totally on it. At the same time, while there are important steps to be done in terms of optimizing the whole – nobody seems to notice the opportunity. It’s like some sort of selective vision impairment or some sort of a dark spell on people that mostly have university degrees and are overall considered smart.

My strong belief is that people aren’t inherently stupid, but as lots and lots of scientific evidence demonstrates, the brain function that is responsible for analytic thinking, gets often “hijacked” by the much more primitive (and yet powerful) system that utilizes various shortcuts and heuristics to arrive at conclusions that are not so beneficial in a complex environment, such as modern organizations (see references to various research results in D. Kahneman’s book, “Thinking Fast and Slow”).

Knowing how many organizational change agents have to deal with this problem in the context of the transformation, we decided to do a little research. We simply surveyed people with a simple question (let’s call it the “Main form“):

You’re starting a new job as a team leader in a new company. After spending a week in your new role, you discovered that there’s a systemic issue that prevents the team from performing at their best ability. It looks very likely that the root cause of the issue lies in the behavior of your bosses and, therefore, is beyond your control boundary as a team leader. There’s a slim chance, however, that the problem might be due to internal dynamic of your team. This issue does not render the team entirely blocked, but significantly affects their performance. What would you choose to do?

…and the answers were:

a) Focus primarily on working with your bosses to address the issue
b) Focus primarily on addressing the issue by changing the team behavior
c) Avoid disrupting the flow, let things be the way they are and let the team continue with their tasks

Please note that we deliberately did not include answers like “Work with the team first and if that doesn’t help – work with your bosses”. The reason for that was simple: we wanted to have them make a principal choice rather than select something particularly comforting, but not necessarily achievable-as-stated in their case.

We’ve also created two other forms of the same question, purposefully “biasing” the respondents a little, to add a sense of urgency. Here they are:

Alternative form 1:

You’re starting a new job as a team leader in a new company. At the very beginning, you were told by the person that hired you that the management is not happy with the team performance. After spending a week in your new role, you discovered that there’s a systemic issue that prevents the team from performing at their best ability. But it looks very likely that the root cause of the issue lies in the behavior of your bosses and, therefore, is beyond your control boundary as a team leader. There’s a slim chance, however, that the problem might be due to internal dynamic of your team. This issue does not render the team entirely blocked, but significantly affects their performance. What would you choose to do?

Alternative form 2:

You’re starting a new job as a team leader in a new company. It turns out that your predecessor was terminated. After spending a week in your new role, you discovered that there’s a systemic issue that prevents the team from performing at their best ability. It looks very likely that the root cause of the issue lies in the behavior of your bosses and, therefore, is beyond your control boundary as a team leader. There’s a slim chance, however, that the problem might be due to internal dynamic of your team. This issue does not render the team entirely blocked, but significantly affects their performance. What would you choose to do?

The difference with the Main Form is in red font. The answers remained the same as in case of Main Form.

Here are the results:

Main Form. 53 total respondents (unconstrained demographic):

Alternative Form 1. 53 total responses (unconstrained demographic):

Alternative Form 2. 51 total responses (unconstrained demographic):

Interesting, isn’t it?

For starters, notice how the answers spread between “a” and “b” in Main Form. That is an interesting, asymmetrical response, given that the question states that the first potential root cause (the problem being caused by the bosses) is stated to be significantly more probable than the second one (it being caused by the team). The two alternative formulations clearly biased the audience more towards answer “a”. Please note that all three forms were answered by different people, without overlaps; no one had to answer the question in more than one form.

I personally had a hypothesis that Alternative Form 1 would bias the respondents toward answer 1 (as it did), but Alternative Form 2 would rather bias them toward answers 2 and 3, which it obviously didn’t. Basically, both alternative forms had approximately the same affect. But still, notice, how many respondents selected answer “b” in both alternative forms.

At that point it’s been decided that “unconstrained demographic” is an interesting first approximation, but we need to know how would a more targeted audience react to this. For that, the Main Form was selected as the only form to continue with and the survey was answered by 51 people in various middle management positions. I can’t say that I exactly expected to see this:

This time around, however, we included a text field where we asked people to explain the rationale behind their choice. 37 out of 51 respondents did so. Some answers suggested that people were primarily focused on what was in their direct area of influence (here’s one interesting example: “My job is to direct my team not change management”). Quite a few others were basically suggesting that they selected “a” to start with the team and then move to the bosses if the former doesn’t produce the desirable results, which is funny because as I noted above, we tried to constrain the answers to not include that specific “comfortable” option. Finally, those who selected answer “a” mostly explained that they want “Only real solution” and “Try to fix the root of the problem”.

To be entirely clear, I am not suggesting that either one of those three answers (“a” or “b” or “c”) was a right one. The question purposefully contained some ambiguity and our goal was to rather see what answers people are mostly inclined towards. The main takeaway for me is that there’s definitely a strong asymmetry in play:

People are more inclined to local optimization despite the fact that it is unlikely to produce the desirable results and they are aware of that.

What does that tell us? I guess, a few things:

  1. You may educate the middle management in systems thinking all you want and it may not change too much, because their decision whether to use it is significantly impacted by other factors; it is very likely that physiological safety is one of them
  2. Maybe there’s much more value in the higher management creating a transparent environment where raising systemic impediments is not something frowned upon, but rather encouraged and thoroughly supported
  3. The effect may be a cumulative result of unintended consequences of existing policies, metrics and KPIs and established cultural scenarios (“bring me only good news!”, etc.). The impact of such “blowbacks” is what the higher management needs to be educated in.

Have a good day and focus on real problems, otherwise we will pay you a visit 🙂

By Alex Yakyma, Org Mindset.

Podcast: Organizational Factors that Influence Lean-Agile Transformation – with Andrew Long

Had a pleasure to talk to Andrew Long this time. Andrew is a managing agile consultant with LitheSpeed (www.lithespeed.com). I was waiting long for this conversation to happen (yes, pun intended!). We talked about key factors that influence organizational agility and flow, the disconnects between the actual state of those factors (that include important structural and behavioral aspects of enterprise life) and declared intentions as part of the transformation. We talked about how to best facilitate emergence of new organizational capabilities, such as responsiveness to change, ability to innovate and so forth. Dealing with constraints and systemic impediments the organization has, which of them to address and when, change by declaration vs. real change and much, much more… I hope you enjoy it. To find more podcasts, articles and blogposts, go to http://orgmindset.com.

New Podcast: Managing Assumptions and Risks in Complex Organizations – Michael Kuesters and Alex Yakyma

Michael Kuesters was on my podcast recently, folks. This was Michael’s second appearance (you can find the first podcast recording here). It was great to virtually host him (he feels a lot like a family now…) and discuss an interesting topic that every enterprise that depends on software or systems development for their success, has to deal with one way or the other. We talked about many things: the danger of reaching a comfort zone in managing assumptions and risks, cognitive biases that can stand in the way, raising hidden assumptions to the explicit level, how assumptions come into existence, “strong” and “weak” assumptions, applying Occam’s razor to assumptions and risks, obsessing with predictability, the trick with building confidence based on prior project successes, using pre-mortems and much more.

And yes, we talked about winning jackpot three times in a row… Because it’s surprisingly connected to some enterprise practices.

Here’s the podcast recording:



To find Michael’s books, use the following links:

Extreme Agility: https://leanpub.com/extremeagility

Spirit of Scrum: https://leanpub.com/spiritofscrum

Bundle: https://leanpub.com/b/non-conformistagile

Enjoy!

 

Fixed or Variable? It’s Actually Both!

Should my team structure be fixed or variable? Should my funding be fixed or variable? Should the plan reflect fixed expectations or variable possibilities?

The reality is, it’s neither one of those isolated notions, but rather both of them enabling organization’s performance in concert with each other.

On the one hand, enterprise reality contains inherent uncertainty and variability. External conditions change, internal factors evolve and, even more importantly, we are able to refine our understanding of those only over time. It is fundamentally irrational to attempt building organizational plans and structures that contain “all the answers” inside.

On the other hand, everything cannot be a moving part. In a sense, an organization cannot just sit and wait for the facts to unfold, it has to actively work to facilitate the desirable future outcomes. It cannot “design” the future in a conventional sense of the word – that’s not how complex adaptive systems operate – but it indeed can and should create the environment and enablement for moving in a desirable direction.

The importance of both of these factors has a direct impact on underlying processes and structures within the enterprise. So, for example, it is often impossible to meet the variable business demand with a fixed team structure, due to skillset/knowledge constraints, as well as other reasons. Instead, it is entirely logical to keep the boundaries of some teams soft, allowing for people to regroup as necessary to best respond to a significant shift in demand. Interestingly enough, the fixed part is important too, because whenever possible, we want to benefit from long-term interactions, as they are known to improve the overall team performance. Similarly, our funding cannot be all carved in stone for a long time horizon, as it would make it impossible to respond to the changing environment. At the same time, without any specific upfront allocation of funds, it would be hard to commit the necessary capabilities required for successful execution. As for planning, it gets even more interesting. Even though many organizations are nowadays trying (at least formally) to be iterative and incremental, it doesn’t imply that they are actually able to respond to change. The real question is instead: are they properly handling uncertainty in their plans. If your plan, even for a shorter time horizon (1-3 months), contains only predefined outcomes, then most likely, your organization is just blind to the unknowns. And it doesn’t actually matter that you iterate every month or two: myopia to uncertainty renders iterative and incremental paradigm useless in such environment. Every plan, no matter how long or short, has to explicitly contain assumptions, preventing the Certainty Bias from settling in and pushing the organization to a whole new level of self-deception. But then again, if the plan does not contain any specific outcomes, nobody really knows where the organization is headed.

So here are the questions for you, as a matter of quick self-assessment:

  1. How exactly are uncertainty and variability incorporated into your process? (consider organizational design, planning, funding, for example). For each one of your examples, try to go over the actual logic, explicit rules, proven scenarios in your environment, rather than potentialities.
  2. How are variable and fixed factors aligned in those examples?
  3. Is it really working?
  4. How do you know that it does or doesn’t?

Lastly, while both fixed and variable nature of organizational activities and structures is essential, there’s a little catch, and we briefly touched on it already: we are all biased towards certainty and predictability and, on the opposite, try to avoid uncertainty and ambiguity. So, when your organizational leaders are telling you something like “but we need some degree of certainty and predictability,” you need to know how to translate this Klingon speech into English. It usually means: “we are looking to define a big-upfront detailed plan, lock down the exact scope and funding, and define specific team structure that will best execute it all.” For most organizations, moderating their obsession with predictability is an insurmountable problem, so the conversation better revolves around embracing uncertainty and variability rather than the “balance”. Otherwise, you are probably just wasting an opportunity to change something to better.

 

By Alex Yakyma, Org Mindset.

High Reliability Organizations (HROs) – Podcast with Brian “Ponch” Rivera

In this podcast we are discussing how High Reliability Organizations (HROs) manage information flows, risks, team dynamics and more. Here’s the podcast recording:

To reach out to Brian:

https://www.aglx.consulting
@PonchAGLX
LI: https://www.linkedin.com/in/briandrivera/

References to books mentioned in the podcast:

Managing the Unexpected: Resilient Performance in an Age of Uncertainty
By Karl Weick and Kathleen Sutcliffe
Link: http://a.co/c7XEmp2

Black Box Thinking: Why Most People Never Learn from Their Mistakes–But Some Do
by Matthew Syed
Link: http://a.co/hpvGTi4

Beyond the Checklist: What Else Health Care Can Learn from Aviation Teamwork and Safety (The Culture and Politics of Health Care Work)
by Suzanne Gordon et al.
Link: http://a.co/0K75uNE

Antifragile: Things That Gain from Disorder (Incerto)
by Nassim Nicholas Taleb
Link: http://a.co/78d9wmA

Blink: The Power of Thinking Without Thinking
by Malcolm Gladwell
Link: http://a.co/9irTGE6

Highest Duty: My Search for What Really Matters
by Chesley B. Sullenberger et al.
Link: http://a.co/cnuLjA7

Safety at the Sharp End: A Guide to Non-Technical Skills
by Rhona Flin et al.
Link: http://a.co/40chYlZ

 

By Alex Yakyma, Org Mindset.

Org Mindset is a Platinum Sponsor of Mile High Agile 2018!

Hello folks! Some exciting news… We are sponsoring Mile High Agile this year that will take place in Denver, Colorado, May 21 & 22.

We will be happy to see you there. We’re gonna have a premium booth with plenty of interesting things, useful give-aways and, most importantly, we will be glad to chat with you, address your questions, participate in discussions on various topics.

We are really excited about this!

 

By Alex Yakyma, Org Mindset.

Feedback Loop Markers. A Panel Discussion During Our Class.

Last week we had a wonderful OMEC (Org Mindset Enterprise Coach) class. During the lunch break on day two of this three-day training we made a brief panel discussion with our attendees on one important topic: Feedback Loop Markers. It’s one of the many topics in the course. Hope you enjoy the video:

Our next class will be also in Boulder in April. You can find more information on the class schedule and the course description.