Archive for Organizational Culture

Whole Agile – Unleash People & Organizations

Agile missing partsAgile is incomplete. We need to augment it to create the “whole product”. But what is it?

There are many ideas: transformation approach, culture, leadership, but something is still missing.

 

 

Whole Agile

Whole = Agile + People + OrganizationWhole Agile is a holistic way to see the functioning of the entire organization.

In order to fully unleash the potential of workers we need to augment Agile with Valuing People and rewire Organizational Governance.

Valuing People is about building a place where the whole person is welcome so they are fully engaged in work. A place where there is safety, trust and authentic connection.

Organizational Governance refers to the approaches we use to run organizations: organizational structure, planning & control, roles & titles, compensation, performance management, information access, leadership and power. These need to shift for us to reinvent our organizations to unleash people’s capabilities.

This is essentially what I have been doing the last few years. Now I have a good name for it. I will be writing more about Whole Agile in the coming weeks but in the meantime, here is a video summary and slides.

Video Summary

Slides

Why “Whole Agile”?

An obvious question is: Why do we need something more than Agile? Why make up a new name?

One answer is that Agile is great at a team level but provides no guidance at an organizational level. We need to replace burdensome organizational processes and with lightweight ones that foster self-organization and engagement.

The most important reason for selecting a name is that we want to create a movement within the Agile community. Not everyone will be interested in building whole organizations and that’s OK.

Here are some alternative names:

  • Holistic Agile
  • Conscious Agile
  • Evolve Agile
  • Beyond Agile
  • AgileAsItWasMeantToBe

Online survey results with comments on names. You can add to the survey as well.

Acknowledgements

First, I would like to thank my dear friend and colleague Olaf Lewitz who has been deeply involved in developing this. Other key contributors include: Melanie Meinen and Laura Powers. Thanks also to those who responded to my online survey: Clint, Jeff K, Fanny, Olivier Gourment, Shyam Kumar, Geir, Peter Trudelle, Frank Olsen, Alistair McKinnell, Justin Reyna.

 

Leave a Comment

People over Process – Win with People

Success comes from Valuing People

Woody Hayes, PeopleWhen we simplify the Agile Manifesto’s “Individuals and Interactions over Processes and Tools” we get “People over Process”. Agile is about people. It’s about a people-first culture.

Sadly, many organizations are mired in organizational debt: mistrust, politics and fear. Changing the process won’t fix this. We need to go to the root of it – to find a way to talk about and shift to a healthier culture: one that values people.

The VAST (Vulnerability, Authentic Connection, Safety and Trust) shows us how we can make our workplaces more human.

We outline a fundamentally different approach for organizational change: one where valuing people is integral to building lasting success.

Slides from my Keynote at Lean Into Agile Conference

Video Summary (7 minute PechaKucha)

Comments (2)

Letting Go of Agile (Culture)

Letting go of Agile Culture“If you want something very, very badly, let it go free.  If it comes back to you, it’s yours forever.  If it doesn’t, it was never yours to begin with.” - Harry Kronman

I have discovered the truth of this with Agile. The one time in my whole life I truly surrendered my attachment to Agile, it resulted in a beautiful transformation starting. But most of the time I was too attached to Agile to let it go.

This post is about how we may accidentally harm organizations with Agile and how we can let go so that we may succeed.

Accidentally Harming Organizations

Here is the basic thinking:

  1. Agile is a good thing.
  2. We can help companies if they use Agile.
  3. Let’s do it!

Trap #1: Accidentally introduce cultural conflict

Agile for me is basic common sense – this is how to get stuff done. BUT Agile does not work in most organizations due to culture. Sure there are some small pockets where Agile just works but this seems to be relatively rare – especially now that Agile has crossed the chasm.

Agile is a different culture from most companies, so the first trap is to accidentally introduce organizational conflict. That’s why I wrote “An Agile Adoption and Transformation Survival Guide: Working with Organizational Culture” – to help people notice this trap and avoid it.

My suggestion was to look at two options:

  1. Adopt elements of Agile that fit with the culture.
  2. Transform the organizational culture.

For many, option 1 is like giving up on Agile since they key part of it is missing so many Agile folks don’t like that option.

Increasingly Agile experts go for option #2 instead: Transform the Organizational Culture. I sure did. I set out to learn how to change organizational culture. And I figured it out. But there was a problem. A big one.

Trap #2 Attempt to Transform to Agile Culture

The core of the problem is that Agile is not an end in itself. It is means to an end. Some common goals (ends) are: a quality product, time to market or engaged staff. The problem is not that Agile doesn’t help with these goals (it certainly does), the problem is that people confuse Agile as the goal and often act in ways that undermine the real goal. We see Agile being used as a Whip or a Shield. That is why it’s a good idea to Stop Agile Initiatives. A better alternative to an Agile initiative is to have an initiative around the real goals. One way to get at the real goals is to run a workshop to clarify why people want Agile.

It is a good thing to change culture in service to what organizations really want for themselves. A specific culture is not a goal in itself, but a means to accomplishing something. We may seek a culture of engagement and innovation not for itself, but because we want our organization to thrive in a competitive landscape.

There are many many beautiful, productive organization cultures all over the world that have nothing to do with Agile. The implication is that there are many ways to get to a place where people love what they do. If we really want to help people, then the best move is to work with them to evolve a wonderful culture that is right for them. And for sure it will not be exactly “Agile Culture” (especially since this is not completely precise). If it is a progressive culture, it will likely be Agile-compatible and using Agile to get benefits will be very natural. It’s a win – win.

Agile Culture should never be a goal. If it is, we will likely just cause harm.

Let Go of the Outcome to Find Success

Here is my secret to success: Let go of the outcome.

I wrote a couple of years about about how leaders have a choice between the red pill (deeper reality) and the blue pill (surface reality). I stated it like I gave people a choice. But I didn’t. The only choice I wanted was the red pill. I wanted so much to help the people in organizations I pushed for the red pill. The truth is I cared so much for the outcome which I assumed was best that I didn’t really give a open choice. In subtle and more obvious ways I was attempting to coerce leaders into taking the red pill. Ooops! Coercion is not any part of Agile, but here I was wanting my outcome for others. And it is not just me. I have talked to dozens of professional coaches and this is pandemic in the Agile community.

The solution is obvious. If we really want to stay true to Agile values, we can’t coerce. We have to let the people (especially management teams) make their own decisions and their own mistakes. We have to help them find and walk the path that they choose. This means letting go of the outcome. This means letting go of Agile.

This business of learning to let go is not new. In fact, letting go of attachment is a central message of Buddhism.

To close, the one time I fully let go of Agile it came back in such a beautiful sustainable and lasting way. Time to rinse and repeat.

“If you want Agile very, very badly, let it go free.  If it comes back to you, it’s there forever.  If it doesn’t, it was never meant to be.”

(Stay tuned for a follow-up post on Agile as a means of creating freedom by Olaf Lewitz.)

My Apology

I helped a lot of people see Agile as a culture system and learn how to stop causing accidental conflict.

Unfortunately, I also energized a lot of people to seek culture change with the goal of growing Agile. As clarified in this blog post, this was a mistake. I am sorry.

What’s the alternative? For those who want real change, let’s help them meet their organizational goals with culture transformation and let Agile come willingly.

Leave a Comment

Transformation Case Study – Video Interview

At Agile 2014, many people were inspired by this case study so Olaf Lewitz interviewed me. Here is what happened.

Slides and Highlights are here.

Leave a Comment

Self-Appreciation Game

At Play4Agile, Olaf Lewitz and I hosted an exploratory session on personal growth hacks. Everyone shared ideas and turned into the self-appreciation game.

Purpose of the Game

The purpose of the game is to give people practice at accepting praise and recognition so that we feel good about our accomplishments and successes. This cultivates our sense of self-worth so that we are more resourceful at work and in our personal lives.

Why Play the Game

In our society there’s rarely room to learn how to accept praise and recognition. We squirm and say “it was nothing” because it feels uncomfortable. We have a hard time seeing our own self-worth and feel this disconnect when we receive praise.

This is a great game to help people and teams become more resourceful so they are able to co-create a more positive environment.

It is very helpful if you are working to create a people-oriented organization.

Game Rules

Setup

Form a circle. If you have more than 10 people, consider the option of forming two smaller groups.
Explain the purpose of the game and it’s mechanics.

Mechanics

Self-Appreciation Game
Go around the circle with each person taking turns:

  1. Brag Protocol: Pick something that you are proud of and share it with the group.
  2. Applause: Everyone cheers and claps to celebrate your success.
  3. Soak it in: Let the appreciation soak in like maple syrup in a pancake. Connect deeply and fully with the feeling for 10 to 15 seconds. See Hardwiring Happiness for further explanation of letting in the good.

Go around the circle 2 to 4 times depending on how much time and energy you have.

Game Results

As we went around the circle the connection and trust increased. Everyone left this game feeling awesome.

Why This Game is Important to Me

I am on an epic quest for self-worth so that I can engage with the world from a centered and whole place. So that I carry my own weather around inside me. The game was invented to help me level up on my quest. And it worked. I hope you are interested in similar benefits.

Acknowledgements

We are deeply grateful to the participants of the workshop who helped co-create and test drive this game.

Leave a Comment

WholeHearted Manifesto: We Value People

The WholeHearted Manifesto consists on one value statement:

We Value People. (Period)

People are the driving force behind getting results. This is the secret recipe for success.

We value all people. Our customers. Our peers. But most of all ourselves.

It would be a mistake to think this is fluffy bunny stuff. It’s not. It is the hard stuff that makes all the difference.

Wholehearted Principles

The principles of the Wholehearted Manifesto are:

  1. People happen. Not right, not wrong. They will amaze you.
  2. Awesome outcomes emerge from people who truly connect.
  3. Collaboration is our oxygen: we co-create environments for people to flourish and grow.
  4. We all are on a unique journey and help each other along the way.
  5. We love and celebrate people for who they are.
  6. We are open and honest.
  7. We ask for help before we need it.

If you have any comments, suggestions, or enhancements – please add them on the manifesto page.

Help make a difference

If this message resonates with you – please go sign the manifesto. And please share the message. Let’s move towards a better world.

Acknowledgements

The manifesto spontaneously emerged during an intense, emergent collaboration session I had with Olaf Lewitz & Christine Neidhardt. We were not seeking this, it just arrived. So I imagine that many other people must be thinking the same thing. So this is a shared idea – not ours. Not anyones.

A wonderful group of people came together to help build the Wholehearted Principles at Play4Agile in Ruchersbach, Germany. Many thanks to:

We would also like to thank Brene Brown who has greatly influenced with her wonderful books and TED talks. She introduced the term “wholehearted” to describe people who are able to fully love themselves and bring joy to those around them.

Leave a Comment

The Business Case for an Authentic Workplace

People are messy: they have personalities and emotions. In this post we explore how we can embrace people’s messiness for advantage rather than have it act as a drag.

Default Business Model is Mixed Engagement

Workers are DisengagedA recent study from Carnegie Mellon Training shows that there are very mixed levels of engagement from workers. See diagram to right.

Current estimates are that staff disengagement cost $11 billion from turnover alone. If we include the costs from low productivity, then $11 billion looks like pocket change.

One challenge with the traditional business model is that it denies people’s individuality and feelings. People put on an “office persona” for how they think they need to be to fit in.

In our workplaces, we do not dare to show our true and whole self. We do not feel welcome, and co-create work environments where sub-optimal results and shared ineffectiveness are normal.

The Authentic Workplace

An alternate model for our work environments is to invite people to show up as themselves – as the wonderful human beings that they are – and fully welcome them.

We might imagine an environment that allow us to:

  • Relate and connect authentically.
  • Share and acknowledge feelings.
  • Trust each other
  • Feel safe
  • Be vulnerable

Typical vs. Authentic Workplace

Consider the following diagram illustrating difference between these models:

Authentic Workplace

In the traditional workplace we create a work identity that is often a shallow project of our true self. Our minds our filled with distractions from our life outside of work. We put in effort to create a distortion field around ourselves to that no one sees our true selves or our distractions.

In an authentic workplace we welcome each others dreams and ambitions, personal history and most importantly our feelings.

Authentic Workplace Benefits

Here are a few benefits:

  • People are motivated when they feel valued and connected at work
  • “Distractions” can be dealt with so people can focus
  • Emotional support for challenges so people get unstuck
  • Better decisions since people are safe to share information

Authenticity is a Spectrum

It is valuable in this discussion to keep in mind that this is not a black or white situation: traditional or authentic. We might imagine measuring or sensing the level of authenticity in a given environment. I am not thinking of metrics but guideposts such as: Do people talk about their emotions? Do people feel a sense of community and support? The 12 Questions from “First Break all the rules” can be a helpful here.

How can we develop the skills?

Below are three ways that I have been developing these skills in my own life and practice.

#1 Authentic Connection Circle – Toronto

This week I am starting an Authentic Connection Circle in Toronto as a way for people to build capacity for authentically relating to one another. We will do this by talking about the stuff that scares us to build trust and create a safe environment.

Some might dismiss this as fluffy Bunny New Age. It’s not.

It’s about character.

Mastering out own patterns and history so that we can engage effectively with others is hard work. It takes character to be authentic and welcome what shows up in people.

#2 Temenos Workshops for Trust and Connection

Temenos is an experiential workshop that invites us to experience connection, openness and trust on a level that’s not accessible to us in daily life. With Temenos, we can safely test more effective methods of relating with others.

Temenos provides a safe setting to explore this space to develop our existing skills. We discover that we can open up to people and learn that this satisfies a deeply rooted human need.

With this experience, we may dare to treat each other more openly, truthfully, and effectively than before. We’re more aware of who we are, and what we want.

Upcoming workshops:

#3 Core Protocols

The Core Protocols are a set of rules designed to support high-performance teams. Some of the protocols are very supportive of building an authentic workplace. I will briefly highlight a few of them here:

  1. Check-in. At the start of a meeting or day everyone shares their emotional state so that there is awareness around how people are entering this context. A simple format of: I am … <glad> <sad> <afraid> is used.
  2. Check-out. People check out when they feel they cannot focus and be productive.
  3. Alignment. People share what their personal development goal is and lets others know how they can help.

Leaders Go First

In “7 Habits of Highly Successful People”, Stehphen Covey talks about this as “Victory begins at home”. If you want to see these changes and benefits in your organization, you need to go first. Leadership in organizations comes from all levels. Be the change you want to see.

Acknowledgements

The primary source of this thinking for me comes from Brene Brown. Olaf Lewitz and I have been collaborating on the developing these ideas and applying them in workplaces. Parts of the text around Temenos were co-written with Olaf. Pascal Pink contributed key ideas in helping explain what Temenos really is about.

Leave a Comment

Lean Culture is about Cultivation and Control

I have thought for a long time that Agile and Lean are pursuing similar goals and quite similar in many respects. Although compatible, I now see they have significant differences in focus.

(Reader’s Note: this analysis was done in early  2012 but became a forgotten appendix for my book on Agile Culture. Thanks to Liza Provenzano who sparked a conversation on this topic at Impact99.)

The Schneider model is a very good tool for creating a quick and understandable analysis of a stated or implied culture system. If you are not familiar with it, I suggest taking a quick read and then coming back here.

Consider the result (below) where the principles of Lean are placed into the Schneider culture model. I used Jeffrey Liker’s 14 point model from his book The Toyota Way. As we can see the two dominant cultures are Cultivation and Control, with Competence a distant 3rd when we place each principle on the model.

Toyota Way - Lean Culture

The focus of Lean and Toyota Production System is on effective management of manufacturing facilities. As a result, it is not surprising to see such as strong operational focus with elements of control.

With this model of Lean, Collaboration culture is not strongly valued. Here there is a striking difference between Agile and Lean – Agile is much more about people since Collaboration and Cultivation are dominant. I would expect a different result if we looked at the culture of the Toyota Product Development which I imagine would be more similar to Agile.

Schneider identifies Cultivation and Control as opposites so having these be co-dominant would imply that either 1) the Schneider model is not sufficiently complex to deal with Lean philosophy, 2) The principles in Liker are a confused westernized attempt to model Lean based on the Toyota Production System or 3) I have misinterpreted the principles. Sadly, I don’t know the answer but this perhaps is indicative of the challenges that are encountered in real life with most failed attempts to instill a Lean culture.

I am aware that respect for people is considered a fundamental aspect of Lean. I have two observations to make. First, respect for people does not imply Collaboration culture. Second, Lean can be a dehumanizing system.

The Bottom Line

The bottom line for me is that we cannot safely ignore the culture we are working in or the culture that our ideology and tools bring with us. It is only by seeing the bigger picture and letting go of labels and tools that we can make effective, lasting change.

Comments (2)

10 Things Executives Need to Know about Agile

Slide deck with the top 10 things executives need to know about Agile:

Here’s the list with some handy links:

  1. Agile Is Mainstream
  2. Many Benefits from Agile
  3. Agile is not a Silver Bullet
  4. Agile Fails Due to Culture
  5. Agile Differs from Most Company Cultures
  6. Most Value Comes from Mindset/Culture, not Practices
  7. Adopt Agile Practices that fit Culture (Option 1)
  8. Change Culture through Organizational Transformation (Option 2)
  9. Culture Mismatch will Slow and Ultimately Fail Your Agile Initiative
  10. Culture Eats Strategy for Breakfast

Of course, it is fine to proceed with either option – adoption or transformation – it’s about what is the best fit for the client environment and their wishes.

There are two conversations around transformation that this deck is designed to trigger/encourage:

  • What does break-through organizational culture look like?
  • What does organizational transformation look like?

My Favourite Slide in the Deck

Benefit of Practices vs Culture

Acknowledgements

I would like to thank the hundreds of people who have attended my workshops and talks over the last two years to help clarify and refine this message.

Comments (1)

How to Build a Culture Bubble

The post is about how one can create a bubble of a new culture inside of an existing organization. For example, this may be used by a group interested in developing an innovation and learning culture inside a typical bureaucratic organization. This post is a continuation of my earlier post on how to Build Culture Adapters to Avoid Agile Failure.

I realized that I have drawn the diagram below dozens of times with clients, prospects and colleagues over the last year and realized other people may be interested in it.

The drawing below shows the hierarchy of a typical organization with a dominant culture (in blue) and a new culture bubble formed (in green).

Leader growing different culture in org hierarcy

Given the nature of a power hierarchy in traditional organizations, a leader/manager can induce a culture shift in the organization that reports into her. See Transformation? Leaders Go First! for an explanation of how leaders can support a transformation process.

It is of course, critically important to build adapters around your bubble so that it can safely interface with the rest of the organization and avoid trigger the attack of organizational anti-bodies.

A final comment is regarding the cooperation of partner groups (in light blue) that are tightly bound to the same customer value stream. The close cooperation required for success necessitates a higher level of alignment. This means that the partner group must either help lead the culture change (and go green) or at a minimum be neutral (as show in light blue).

In a software context, a very tight relationship exists between the product and development groups since they need to work together to create customer value. A common pattern is for the green bubble to be the development and the blue bubble to be product.

When and How to Use This Diagram

I typically draw this picture and provide this explanation when socializing alternative approaches to Agile. In virtually all cases, the change agent leading the Agile initiative is not the CEO and does not have a span of control or influence over the whole organization. It is usually the case that typical “modern” management practices are in place that are regressive and hostile to fostering an Agile culture. So most leaders have the option of sticking to the adoption of practices that are consistent with the existing organizational culture or undertake a transformation of their group to realize a new culture that is supportive of Agile.

It is of particular importance, that as an external change artist, we are fully respectful of our client’s wishes and intents. It’s their organization after all. For some coaches this means letting go of the dream of helping the organization move forward on the road towards an Agile mindset – or “real” Agile.

Related Work?

Some time ago I shared George Schlitz and Giora Morein’s Agile Enablement Battlefield model to help understand how a transition is progressing. I am no longer a big fan of the metaphor of war, however, the notions of “fog of war” can be helpful. As well, I have seen increasing danger and harm caused by wolves in sheep’s clothing. These are the folks who say they are on board and go along with changes, but resist in passive ways. Of course, this is a natural and understandable response to coercion. If we really want to change our organizations then coercion is a tool that we need to leave behind.

Acknowledgments

The basic ideas of managing gaps in culture comes from William Schneider’s book How to Make you Culture Work. Many thanks also to all the various workshop participants who validated that these patterns apply.

 

Leave a Comment