The Productologist

I was in a meeting a few days ago where we were discussing the schedule for the upcoming release of my product. To my knowledge, everyone in the room already knew what the schedule was, but we have an internal wiki that we use to track release dates and that page had TBD in several slots, hence the meeting. What was really driving the meeting was that members of the exec team had different dates in their heads and when this came to light, there was an immediate scramble to get everything reconciled.

Two weeks ago, a friend and I went to a bar to watch the Packers-Cowboys game (thanks, NFL network). Normally, our sporadic football-watching happens as his house, as I don’t have TV (yes, I have a TV, just not an antenna, satellite dish or cable). We watch the game, make armchair quarterback calls, comment on the stupidity of most of the ads and discuss random technology issues (we both work at technology companies). But instead of our normal conversational environs, we were immersed in the revelry of the crowd.

[Business 2.0 Homage #2]

In previous posts, I have discussed the usage of Personas as a tool for insuring that your product meets the needs of the prototypical user(s) in the context of other challenges. Look for a posting on that specific topic soon, but for now, I’ve got another example of how important it is to truly understand who the primary and secondary users of the product is.