Skip to main content

My Brain's Companion

For almost seven years, I owned a Motorola Startac mobile phone. Friends snickered about it being an "antique". It being my first mobile phone, I was thrilled with it until it stopped working after I dropped it on the ground too many times. During the years I owned the phone, many new models of mobile phones were coming out, but I didn't see any compelling reason to buy them. When my Startac finally died, I was left with little choice but to buy a new phone. I bought a Motorola mpx200.

It was only after I bought and used the Motorola mpx200 that I realized the seriousness of the problems I faced all those years without it. The mpx200, like many other phones (but not the Startac), has a calendar and will keep it synchronized with the calendar in Microsoft Outlook. It also has e-mail and will synchronize messages with Outlook. Using these features changed my life. The mpx200 is like an adjunct to my brain.

The problem I had for all those years was a memory and scheduling problem. I could not keep track of appointments and social events, because there was simply too much information that I either (a) needed while I was not at my computer or (b) discovered while not at my computer. But I didn't realize just how serious a problem the memory and scheduling was until I used the mpx200 and was able to see how different my life could be with my brain's "companion".

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

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

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the