When people doubt or resist the T-shaped philosophy, it’s easy to assume that they just haven’t understood what being T-shaped means and why it’s valuable. More often than not though, I’ve found that a lack of information isn’t what’s holding people back. In my work with organisations and teams, I’ve come across 6 main reasons why people resist the trend towards being T-shaped. I’ve outlined these reasons for you below and have included some remedies that may help you and your teammates get past any hesitation. 1. Their identity is tied to their role Many people identify with their role. They may have worked with something for many years or…
Spread Tribal Knowledge with History Lines
To help teams share and document tribal knowledge I run/facilitate an exercise I call History lines[1]. In this exercise teams are asked to visualize how different things have changed over time and at the end of the exercise you’ve helped spread knowledge to everyone in the team, the team has drawn new conclusions about their past, and they’ve documented some parts of their tribal knowledge. I’ve found History lines useful when: Team composition changes e.g. when merging or splitting teams or when onboarding several new members in a short period of time Team members have come to rely on specific people for context Bootstrapping new teams Visualize what makes sense…
How to use the Value Cards exercise to help your teams collaborate better
What do you think would happen if someone who values empathy, love, kindness, respect, and humility were to join the same team as someone who values boldness, success, fame, influence, and reputation? Do you think they would collaborate well from the get-go, making use of each other’s unique perspectives to complement and improve upon their ideas? Or do you think they’d be more likely to struggle, misunderstand each other, and face their share of conflict? You’ve probably seen the latter in action. And, to be fair, it’s a much easier pattern to default to. But it doesn’t have to be that way. If team members can make their own values…
3 Powerful Observation Techniques
Some agile coaches and managers are uncomfortable with setting expectations, offering feedback, and making decisions on behalf of other people, and they go around asking powerful questions. “Who am I tell people what to do in our autonomous organization?” they sometimes say. However, utilizing powerful questions when there is a specific answer that the team needs to arrive at only allows the situation to continue, can damage your relationships, and can subdivide your team. One alternative to asking powerful questions is making powerful observations and in this blog post I share three different examples of how to make and visualize powerful observations. Making powerful observations helps teams see themselves which makes…
Questions I ask in interviews – How do you enter new teams?
Coaches at Spotify are expected to help squads who need help. Sometimes we stay with a squad for a year and sometimes we only stay for a few months. Some reasons to this include organisational changes, that squads split, and new priorities, etc. But how you as a coach enter a teams greatly impacts your effectiveness, the speed of which you’ll gain context, the amount of relationships and strengths of those. In short if affects the impact you can have on a team. Because it has such an impact, if you’re interviewing with me for an agile coach, product owner, or manager role I might explore how you enter systems…
No, Agile Coaching Is Not Cat Herding
Agile coaches and leaders in agile organisations sometimes refer to parts of their job as herding cats. While said with a smile it has a negative connotation. I’ve done this in the past myself and I think it’s important that we stop talking about our jobs, and people and teams this way for several reasons: Talking about cat herding hides the real problems at hand. What exactly is the team doing that makes them appear as cats? And what should the team improve in order to not be a bunch of cats? It’s disrespectful and as a coach or leader you are likely loose influence. Sure, cats are smart, independant, and resourceful, but what coaches/leaders…
Case Study – Optimizing Cycle Time for Data Center Maintenance
Overview Most teams do not measure lead time and cycle time [1], missing opportunities to improve their system’s value flow. Here’s an example of how a data center team I worked with managed to reduce their cycle time from 32 days to 5 days by starting to measure it. Initial Setup and Discovery We visualized our work on a physical board and tracked our metrics manually because the available tools (Jira, Trello, LeanKit Kanban) did not meet our specific needs. We did not know what we would discover, but once we measured our metrics, we learned that our cycle time was significantly higher whenever work involved scaling a part…
Here’s how you can help teams improve their planning meetings
About a year ago I worked with a team that wanted to improve their planning meetings. As I observed this team, I noticed that they used their planning meeting for 5 other things. Technical discussions and designing solutions – about features or requirements not a part of the coming Sprint’s backlog. Grooming the backlog – preparing the backlog for the future. Walking the board – progress review and status updates on stories and milestones. Discussing ways to improve e.g. teamwork, process, etc – reviews of how the team works, their process, and collaboration. Off-topic requests for help – team members asking each other for help with work and features unrelated to the…
Experiential book clubs help people grow, and they’re fun too! :)
In this blog post I go through the differences between conceptual and experiential book clubs. I also share some tips if you’d like to organise an experiential book club for yourself. A few years ago I coached a team that was making a huge effort to reduce their technical debt. I offered to organise a book club around the book Clean code but I was faced with some skepticism. Several team members had participated in book clubs in the past but those had not been valuable. I explained that this book club probably would be different from previous ones they’d attended because this one was going to be experiential. I…
Surface Silent Disagreements
If you’ve ever worked in a team that makes lots of decisions but that struggles with making progress on those decisions, here’s a technique you can use to understand if your team is aligned on decisions or if people are disagreeing in silence. To avoid confusion and potential conflict it’s good to get your teams consent before trying this technique out. Build surfacing silent disagreements into your decision making process[1] Whenever your team has made a decision ask someone to repeat the decision then make the following three statements, one at a time, and ask the team to answer yes or no depending on if they agree or disagree with each statement. Three statements to surface disagreement I agree with this decision. I feel that…
What does an agile coach at Spotify do?
A common question that I receive from the agile community is “What does an agile coach at Spotify actually do?” and about 2 years ago Joakim Sundén answered this question in his blogpost The agile coach role at Spotify. This blogpost is about my current focus and how it has evolved over the past months. While I won’t go into specifics about the challenges we have had and still have, I will illustrate what reality can look like for an agile coach at Spotify. Four months ago I left the IO-tribe (Infrastructure Operations) to join the six month old BITS-tribe (Business Information Technology Systems). I was the first agile coach to join (btw we’re hiring) :) and the…
What happens when you send a dev team to a 3 day group development course?
Are group development courses such as IMGD silver bullets when it comes to helping teams mature? That’s what Martin Wasielewski (also an agile coach at Spotify) and I wanted to find out. In order to find the answer we defined an experiment, and identified a 3 day group development course called S360 encounter that we would send a (willing) development team to. Our hypothesis was that: By increasing people’s self awareness, improving their self esteem, teaching them how to communicate effectively, and raising their understanding of other people’s needs, teams will become high performing. How we would evaluate this experiment Three and six months after our dev team had taken the course we would evaluate the experiment on the following:…
Solve problems with experiments
Lately I’ve been exploring tools that can help teams more successfully solve problems. This article is about how you can use experiments to help you solve problems more effectively. Your convictions are more likely assumptions In product development we are finally starting to acknowledge that the convictions we have about our product actually are assumptions (that often also turn out to be wrong). The realisation of this is one of the reasons to why we adopt lean startup or create impact maps. We want to find out if our convictions are wrong early because we want to discover what our users or customers actually want faster i.e. profit faster. That’s…
9 Questions That Help Determine Your Decision Making Style
I am fascinated by how teams make decisions. Some teams I’ve worked with have wanted all decisions to be made by consensus. Others preferred to have a team lead or unofficial leader have the final say in making their decisions. I’ve also worked with teams that resist any and all decisions coming top-down. This often translates to an inverted top-down decision-making process. In a team like this, managers aren’t allowed to make any decisions or tell anyone what to do. One of the responsibilities that you as a leader have is to create an environment in which all individuals can contribute to solving problems and making decisions. To do so,…
Why are only some improvements successful?
That’s what a team that I have been coaching for 1 year and I wanted to answer. We were curious about the answer because I was leaving to coach another team. We thought that the answer to this question would allow the team to improve more effectively. Call it waste reduction in improving if you will. While we weren’t able to identify “one magic ingredient” that made improvements successful we did gain some insights that we think are valuable to others. The format of our retrospective We drew a timeline ranging from July 2013 to October 2014 and we filled it with two different types of data: “Non product related” events, and “Product related” events. Examples of…