I am a UT graduate and love to play (flag and touch) football, but I've never been a huge UT football fan. Nonetheless, Wednesday I hosted a Rose Bowl viewing party. I had a little over ten people over, and all enjoyed the excitement of the game. Even aside from the game itself, it was an interesting "downtown" experience. There were almost no cars on the street during or immediately after the game. However, we watched from the balcony of my downtown loft as the streets clogged with cars and people within minutes, with horns honking incessantly and lots of cheering. It was a fun night.
The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos