Tag: rétrospective

Learning from the neuroscience of trust

Learning from the neuroscience of trust

Trust is the foundation of the human relationship and the foundation of an effective team. I recently shared how our behavior will create or destroy trust in the article The Evolution of Trust, and more about trust as the foundation of a team in the article The Five Dysfunction of a Team.

Paul J. Zak, the author of Trust Factor, shares in The Neuroscience of Trust the 8 management behaviors that will foster trust.

We could use the 8 behaviors as discussion points with teams to improve our way of working. The question could be, How are we doing on:

  1. Recognize excellence: personal public recognition from peers that occurs immediately after the fact, tangible and unexpected has the largest effect on trust.
  2. Induce “challenge stress”: stretch goal, but a still achievable goal, assigned to a team will intensify focus and strengthen the social connection.
  3. Give people discretion in how they do their work: autonomy and self-organization, is another important contributor, being trusted creates trust.
  4. Enable job crafting: trusting people to choose what they will work will ensure focus and motivation. The author gives the example of Valve, the gaming software company, I recommend their employee handbook to have an idea of how they work, and inspire the conversation with your teams.
  5. Share information broadly: uncertainty and stress undermine teamwork, openness, transparency and daily synchronization are the proposed antidotes.
  6. Intentionally build relationships: encourage people to care for each other will make them happier and more productive.
  7. Facilitate whole-person growth: meet frequently and give constant feedback on personal and professional growth.
  8. Show vulnerability: asking for help, and acknowledging what we don’t know, help to build credibility.

Could this discussion be the Retrospective on Trust for your team?

Fight Club Retrospective

Fight Club Retrospective

You probably remember the first 2 rules of Fight Club, right?

Let’s review the rules:

“Welcome to Fight Club. The first rule of Fight Club is: you do not talk about Fight Club. The second rule of Fight Club is: you DO NOT talk about Fight Club! Third rule of Fight Club: if someone yells “stop!”, goes limp, or taps out, the fight is over. Fourth rule: only two guys to a fight. Fifth rule: one fight at a time, fellas. Sixth rule: the fights are bare knuckle. No shirt, no shoes, no weapons. Seventh rule: fights will go on as long as they have to. And the eighth and final rule: if this is your first time at Fight Club, you have to fight.”

― Chuck Palahniuk, Fight Club

Let’s now define what a retrospective is. A retrospective, is a specific session, in which a team reflects on what happened during the previous iteration. This reflection will lead the team to decisions, either to reinforce positive behaviors, or to invest time to improve what is preventing the members to achieve their goals.

There’s a lot of ways to facilitate retrospective, you could go here and there to find out more.

Isabel, my amazing wife, had the idea to create an “all-in-one” retrospective plan based on the Fight Club rules. You will learn more about this plan in her book to come.

In the meantime, I would like to present how I used the idea to foster productive conversations in a team that is scared of conflict. This is the second of the 5 dysfunctions of a team.

Maybe you think that using fight is too violent in the workplace. And at the same time, what happens in us, during a discussion could be felt as fight.


The meeting will start with the explanation of the goal, and how the Fight Club rules are transposed in our work environment.

The first 2 rules are useful, because, as stated by a manager in the team, the children don’t want to hear that “mum and dad are fighting”. I could argue that this statement in itself says a lot about the current state of trust in the organization, and that in an effective organization, the manager will probably not consider himself or herself as the parent of the team members. If we put that aside, the first 2 rules are useful to create a secured space in which conflicts are allowed, and nobody knows that we could have conflict in this team.

So we are saying there, that during this specific meeting, we will not seek artificial harmony, we will accept to start the conversation on topics that we are not in agreement (yet).

Third rule, we need to be able to stop the conversation. Fourth rule, only two people involved, everybody fighting at the same time against one is not a smart idea, right?

Fifth rule: one fight at a time. Let’s not mix all the topics in the conversation.

Sixth rule: no protection and no weapon. Is referring to your boss a weapon? Let’s discuss what it means for the team.

Seventh rule: … as long as they have too… We need the conversation to end with a decision.

Eighth rule: first timer have to speak up. In fact, every team member will have to bring a topic on the table.


What is missing there, is a way to bring topics that is non judgmental. So we could have a productive conversation. Isabel proposed to use Non Violent Communication, to encourage people to observe, express their feelings (and not their thoughts), to express their unsatisfied needs, and their requests.


This explanation of the 4 part of the NVC process could help 🙂


Happiness level during your last quarter

Happiness level during your last quarter

Two weeks ago, I facilitate a quarterly meeting of a distributed team. They met in person only once a quarter during this meeting.

I chose to start the meeting with an exercise to share their feeling about the last quarter. I asked:

Can you draw a line representing your happiness level during this period?

The levels are represented by weather symbols that make them more understandable for the people of this team who are coming from several countries in the world. They almost all chose to comment the drawing when they were drawing the line, and when they were not, I asked them to comment, and after that I thank each of them for sharing.

I was amazed by the amount of information shared during this simple exercise about their general feeling about their work, what make them tick from holidays to specific achievements, learnings, relation established with other people and so on…

I feel also that the state of mind of the whole group was best prepared to review the results achieved during the last quarter.

On the second day, in front of the drawing, I start by thanking them again to have shared their feelings about the last quarter and I asked them to use one or two post-it notes to answer this second question:

What are you proud of?

Once again, a good question to understand what’s important for the individuals in the team, and a good way to set the stage for the day.

If you try this, I would appreciate your feedbacks.

Spotify engineering culture

Spotify engineering culture

Henrik Kniberg shared two 15 minutes videos explaining Spotify Culture.

First part covers mainly teams organization.

Second part covers failure and learning culture, that fosters innovation.

30 minutes to study the way of working of a company that live with agile values and principles since the beginning (for the pleasure of their 30+ millions of users, yes, I am one of them…).

PS: I had the chance to met another Crisp coach working with Spotify a few month ago, see this article: Agile est agile à grande échelle (in french).

Contrat Creative Commons
Les articles publiés ici sont mis à disposition selon les termes de la Licence Creative Commons Paternité 3.0 non transcrit.