Visualize Values and Name your Team

blog, management30

I was asked to assist Snappet during their Development Gathering a while ago. Snappet is a software development company in Utrecht, Netherlands. It is also an adaptive educational platform that challenges every pupil to develop himself or herself optimally. Snappet has around 23 people working in its software development department: product owners, UX people, graphical designers, testers, and developers.

In a few blogs, I want to share some of the activities we organized and what we all learned from them. In this first blog post, I will discuss team values and team names.

I believe it is important that team members know their team values. What do you find important as a team? Do you believe innovation is important? Do you want to have fun every day, or is being a professional something you value as a team? Having the team values clear helps you understand what you can expect from each other. When recruiting new team members, you can discuss the team values upfront to determine if there is a match between the candidate and the team. If being skilled, for example, is an important value, then you can expect team members to spend time growing their skills, e.g., by taking up work out of their comfort zone.

burgerflag

However, most of the team members never talk about their values. Yes, there are often company values, and they were likely decided on by a higher management team. You may find those values on the walls, at the reception when entering an office, even printed on the little cocktail flags that a chef puts in the burgers in the canteen, etc. But are those values always the same as the team values? I find that hard to believe. Perhaps some of the corporate values are also quite important for the team, but it is also likely that the team has more applicable values of their own that they find much more important in their work.

One of the things that I find very important and that I try to do in every job I take on is to make things explicit. When a team explicitly decides to have a daily scrum of 28 minutes, and they are all OK with it, then I am also OK. The same goes for team values. I believe it is important for a team to bring things into the open and, as a group, decide their values: what is important to a team, what is good, and what they want to be.

As I described before, it can help them focus when they need to decide where to go, they can use it to discuss work agreements, or people can make decisions because they know what to expect from the group.

To make things explicit, I organized a value workshop for every team. The goal was to let them find out about their team values. I used the sections Value Stories & Culture Books: Define the Culture by Sharing Stories and Work Expo from the book Managing for Happiness as an inspiration for the workshop. The setup was as follows:

  1. Share stories with your team about things that happened in the last months.
  2. Think about personal values: what is important for every team member.
  3. As a team, decide on your team values.
  4. Think about wish values.
  5. Visualize your team values.
  6. Close off by naming your team.

Let’s take a look at the different steps.

As a person, I believe you become who you are because of all the things you experience in your life. When I was young, I read a lot about World War II and all the terrible things that happened. Perhaps that is one of the reasons why I never try to judge people on the things they do or say (I am not saying that is easy). Maybe also because of what I read, I really don’t like autocratic behavior. But enough about me. The same holds true for a team: a team becomes who they are because of the things they experience in their existence as a team.

storycards

I asked the teams to share stories about things that happened to them in the last months. It is hard to just tell a story, so I put story cards on the table to trigger ideas about stories. It worked quite well, and new team members started talking about how welcome they felt in the team. When you share stories, you can find out about your personal or team values. Some of the teams discussed some of the conflicts they had.

The next step was for everyone to think about his or her personal values. The book Managing for Happiness contains a helpful list of some 250 values… Well, helpful; I don’t even like going to Subway because of all the decisions you must make before getting a sandwich… So, let alone a list of 250 values. No need to say that some people find it a bit too much. I used a smaller list from the Management 3.0 book, which still contained 50 values. I printed them on paper and gave all team members a page with the values. Next time, though, I will add an empty row at the bottom… Why an empty row? Well, to clarify people can also add their own values. Otherwise, people will feel constrained in deciding on their values.

personalvalues

After everyone had decided on their values, the next step was to share these values and put them on a flip chart. I asked them to put their personal values in the outer circle. I also asked them to briefly explain the personal questions and reflect on how these values come back in their work. The feedback I got from some of the team members afterward was, “Now I understand my teammates better,” and “It’s nice to hear from people what drives them.”

The next thing was to decide on the team’s values. The only thing I told them was: “OK, next step is to decide on your team values, just go and organize yourself.” Some of the teams grouped the values and decided to move the values with the most sticky notes to the center. Another team did a dot voting after grouping them. Other teams just looked in silence at the flip chart till some team member made the remark they should really work on the value Initiative :).

Of course, the question came: “How many values are we allowed to select?” Well, I don’t know. 3, 5, 7, or 10? Although that would maybe be a bit too much, you decide yourself. These are your personal and/or team values.” In the end, most of the people and teams came up with 3 to 5 values.

After deciding on the team values, I asked them to consider Wish values. “Which values do you wish you had in the team?” I made three stars on the top of the flip chart. Maybe I should not have done this because this already set an expectation of a maximum of three wish values. One team came with one wish value, the second had two wish values, and the third had three. I don’t know how much three stars guided this discussion. However, next time I will just write the words “Wish values”. They decided on the desired values just by discussing the values and what they, as a team, wanted to become. I noticed that a wish value was hard to talk about for most teams. So, I would advise teams to talk about Wish values a few times a year to really get the concept and also to reflect on them.

The final step of the team values was to ask the teams to visualize the values. Words are powerful, but I believe when you can turn words into physical symbols, they can sometimes be even more powerful. Turning values into symbols should be done by the team themselves, not by another department. I also asked the teams to make two copies of the visualization. One copy is for the Dutch office, and one is for the other office. Oh, and before I forget, please take into account that the visualization has to pass the security check at Schiphol Airport… so liquids, sharp metals, etc., are not a smart idea ;). They had a budget of 50 euros and had to share their visualization by the end of the week.

yoda

One team has Mastery as their most important value; for them, a small Yoda was the perfect visualization. They ended up buying two Yoda’s, one for both offices.

Another team created a poster that showed their team values. When a team creates a visualization, it is by default a good visualization. You cannot say it is not good enough or that it does not show all team values. As the values are owned by the team, the visualization is also owned by the team.

During my preparation, I talked with the Scrum Masters and Product Owners of Snappet. During these talks, they discussed team Teun, team AlexanderM, and team AlexanderK … OK … Did you name the teams after individuals? Yes, they are the leads, and we never thought about it. OK. I met Teun, AlexanderM, and AlexanderK during the gathering, and they are great guys, but naming a team after them… so the last step in the workshop was asking the teams to come up with new team names.

teamposter_values

We did the value and name session on Monday, and they had until Friday afternoon to visualize the values and come up with a new team name. I asked the teams to fill in a survey after the Gathering. One of the questions was: “How happy were you with the team value session?” The answer was 1, 2, 3 or 4. Where one was Not so happy, and four was Extremely Happy. 65% gave a 3 or 4 as an answer. So overall, they liked the session. The new team names are StravTempo, PoscoSkillus, and HyperMonkeys Go!

Does it now end with this single session about team values? No, the teams should regularly talk about their values. Maybe in a retrospective, we can discuss them: Are we still living up to our values, or did we change? I also don’t believe your team values are set in stone and will never change.

So next time you are involved in a new team, think about team values and a team name. I believe having clear team values and a real team name strengthens the team!

Do you want to learn more about Culture and Values? Attend a Management 3.0 Workshop!

Share:

Leave a Reply

Your email address will not be published. Required fields are marked *

Subscribe to my newsletter and you will receive my book “Doing it! – Management 3.0 Experiences” for free!

The book details and reflects on my personal experiences adopting and implementing Management 3.0 practices. The mistakes I made and the successes I achieved. I wrote them down primarily because I like to help people and organizations get started with Management 3.0 as well. Subscribe to my newsletter and you will get it for free! In case you prefer the paperback version, click here.

Get the book

    Please enter your data below. You will receive the book within five minutes in your inbox, be patient. Have fun reading it!



    Be aware! I will send you the pdf file by email. The total size is around 4 mb, if you have a limit on your incoming email, please contact me by email (info (@) agilestrides.com). If you select the not the English version, you will only get a pdf file.