What is the top requirement for high-impact teams? When I was recently asked this question, I started making a list.
- You need to know why you are doing what you are doing, and everyone on the team needs to know what that is.
- You need to trust the people on the team. Trusting them is connected to personally caring for each member of your team.
Assuming your team has a great purpose and people who trust and care for each other, will that guarantee a high impact? Maybe not.
From my perspective, the one thing that is essential on a high-impact team is for everyone to understand the workflow—from the beginning to the end. And not only to have a clear, shared understanding of all the steps but to have the workflow visible to all team members at all times.
How to make your work visible
If you build software or do other work in the virtual world, it’s not easy to make your workflow visible at each step. Here’s a process I came up with some time ago when working with a team that was in charge of delivering a website for a luxury products company. The expectations for the user experience were incredibly high. Some would say ridiculously high.
We started to investigate our team’s workflow by beginning at the end. On the upper far-right side of a large whiteboard, I wrote the word DONE in large letters and asked two questions:
- How do we know that our work is done? The website is behaving as expected by the customer on all the defined platforms.
- What changed between now and before? We implemented a new feature or a fix to an existing feature, and the result of this implementation is that the website is behaving as expected by the customer on all the defined platforms.
These questions gave us information about the steps that had to happen before considering a work item “done.” We need to test the website on all of the platforms. And we need to implement a feature or a fix.
On the whiteboard, I wrote TEST to the left of DONE, and IMPLEMENT to the left of TEST.
In the whiteboard’s upper-left corner, I added a new column called INBOX. I explained to the team that we would use cards on the whiteboard to represent all the work items we had to do. When a new card (i.e., work item) enters the workflow, we would place it in the INBOX column.
- What needs to happen between the INBOX and the IMPLEMENT column? Before we begin working on the issue, we need to assess its severity. We need to understand the new feature and how it will affect our personas.
I added an ASSESSED column between the INBOX and IMPLEMENT columns.
- How do we know what we need to implement? There are two types of work: planned work and unplanned work.
- Unplanned work is the fixes that are detected by the users, the customers, or our teams. We are committed to delivering the fixes in a defined timeframe according to the severity of the issue.
- Planned work is the new features that are defined with the representatives from the customer teams.
To distinguish between the types of work, I added a horizontal line across the columns to create an area in each column for Fixes (unplanned) and Features (planned) work.
Here’s what the whiteboard looks like:
We identified another issue we needed to address: The list of defined platforms had changed regularly, so we decided to make that list visible on a wall in the team room and use it as a checklist for the implementation and test activities.
How it works
A card enters our workflow in the INBOX column:
- If the card describes an issue to fix, the team assess its severity and places the card in the ASSESSED column of the FIX swimlane. The card is timestamped and assigned a due date, then all the cards are sorted by due date and severity.
- In the case of a feature to implement, the team evaluates what the ask means, discusses the implementation approach, and places the card in the ASSESSED column of the FEATURE swimlane. The customer and the team agree on the relative importance of the feature compared to the other features already in the column.
- On the list of defined platforms posted on our team room wall, the team also discussed and displayed the assessment criteria for bugs and features on each platform.
What’s the benefit?
This example walked you through how we identified our workflow and made the work visible. In the interest of brevity, I simplified what was a multi-day planning process.
The fundamental principles to make work visible are: Start with the desired end state, ask questions to understand what needs to happen to reach that state, and iterate to reach the beginning of the workflow. This must be a team activity because each team member will have his or her own view of the different steps.
The immediate benefit for the team is it is obvious what needs to be worked on next, so each team member can pick the next card knowing that he or she is doing the right thing for the project. The indirect benefit is that it shows where in the flow we are overinvesting–we can see it because the cards are pilling up in the column just to the right of our overinvestment. In this case, we must limit that space according to the capacity of the team and focus on keeping a continuous and even flow of cards.
What do you think?
By making the work visible, the team knows where to invest its energy to have the most impact. This is why I think making work visible is the top requirement for high-impact teams. What do you think is the #1 factor in a high-impact team? Please post your answer in the comments or tweet @alexismonville or @opensourceway with the hashtag #ChangingYourTeam.
The post was first published on opensource.com on July 31, 2018.