Skip to main content

Safety - the perquisite for Leadership

Many coaches suggest that teamwork starts with trust.  Simon Sinek would have us believe that there is a perquisite for trust: followers feel safe.


That feeling of safety builds trust, and that trust sets the environment for teamwork.

Do your team members feel safe?  If the project succeeds or fails do they still have a job on your team?  Answer no to that one simple question and you have your answer to why collaboration and teamwork is a challenge in your organization.

Work toward changing that and you are demonstrating leadership.

Did your software development organization follow the lead of many Agile companies and create a large open space floor plan with rows of cheep tables and expensive chairs?  Did this environment create the collaboration that it was intended to?  I've been in several companies recently that believe they have an Agile environment - this is far from the truth.  Let's look at what they really have and what they desired (or assume would arrive magically).

The desired behavior was the high collaboration that a team room space fosters.  Those team rooms are a success because the team is protected from outside influences, have autonomy of action (such as displaying team artifacts on walls/boards), have alignment of purpose from the environment to the culture to the project's goals.

When organizations try to scale this localized behavior to a large group - what is the first thing to be destroyed?  Safety!  Humans will not feel safe in a group of 100 - 150 strangers.  I've experienced this in a recent company.  We had small team rooms that were too crowded for the 6-9 people, yet they were functioning well and gelling as teams, collaboration was increasing, alignment and focus was driving good team work behaviors.  Then it all changed.  We moved to a new building/campus across the street.  The new space for engineering was one large floor open space with managers and directors in glass offices surrounding the table and chairs of the developers.  All safety was lost, trust dropped, teamwork came to a screeching halt.

CEO Rich Sheridan removed the fear and ambiguity that typically make a workplace miserable. With joy as the explicit goal, he and his team changed everything about how the company was run. The results blew away all expectations. Menlo has won numerous growth awards and was named an Inc. magazine “audacious small company.”


Do you enjoy NPR All Things Considered style deep dives into a topic? If you also love more avant garde story telling -- try the Agile Path - In Search of Safety podcast.

"A journey to define safety; we intersect story telling, interviews and in-depth research, talking us on a journey through abusive environments to improvisational theatre.  Learning about safety, engagement and what happens when they don't exist."


See Also:
book by Stephen Covey (the younger) The Speed of Trust
book by Richard Sheridan  Joy, Inc.

TED Talk:  How to build (and rebuild) Trust - Frances Frei
Trust is the foundation for everything we do. But what do we do when it's broken? In an eye-opening talk, Harvard Business School professor Frances Frei gives a crash course in trust: how to build it, maintain it and rebuild it -- something she worked on during a recent stint at Uber. "If we can learn to trust one another more, we can have unprecedented human progress," Frei says.


Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.  

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.


Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?

We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
What if …