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…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

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, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!



Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

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.