Visualize Problems with a Board

Your team might want to note problems (impediments, risks, other obstacles) on its board. I prefer to separate the problems from the work. That’s because a servant leader (not the team) may take the lead on addressing these problems. One team uses a board like the one shown in the following figure.

The team wants to track the date it added a problem to this board. If the team doesn’t address risks early enough, the risks turn into problems. But visibility doesn’t mean the team has to start working on it yet. When it’s time for someone to work on the item in the Concern column, the team promotes that item into the Ready column. This team has a WIP limit of seven items in progress to make sure it continues to review and address its problems. Whoever works on the item can move it into a Waiting state too—waiting for an external or team decision. Once the person or team resolves the item, the item is moved to Done.

I’ve been vague about who would work these problems. Often a servant leader manages these problems. Sometimes team members do. There is no One Right Way to address risks, impediments, or other problems. Make the work visible and work it. Your team might want to track items from a retrospective parking lot on this board, especially if it has trouble starting the work on that parking lot. (See ​Use a Parking Lot for the Improvement List​.)