Thanks for taking the time to comment, Craig. In the middle of the article you can see a graphic that depicts a simple table with columns that represent the steps/stages of the actual opportunity backlog.

If you have a team with a dedicated space/team room, I’d suggest taping up the table’s 5 columns on the wall—leaving room to add post-its or notecards in each columns. As you identify & define problems, add them to the 1st column (it helps to color code the problems with dot stickers or colored post-its or notecards). Decide with your team which problems are the most important, and you’ll take that problem through each step of the framework. For instance, Problem #1 gets a red dot sticker. The opportunity description in the second column gets a corresponding red dot. As hypotheses are developed for Problem #1 they get added to the third column and indicated with the red dot. Design concepts are developed; they can be printed out and attached to the wall in the fourth column. Again, apply the red dot to associate the designs with Problem #1. Finally, include relevant information you gathered during concept testing by adding important findings/user quotes to color-coded notecards/post-its in the last column.

This process could take a few days or a few weeks depending on how long it takes the team to define the problem/hypothesis, create design concepts, and gather feedback. I suggest reviewing this backlog at least 3 days/week with the team to chart progress and adjust content in the columns. Hopefully, I wrote that out clearly enough!



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Scott Kiekbusch

Digital product design & strategy expert. Team builder. Stoic. Keynote speaker. Co-Author of The Designer’s Guide to Product Vision