If you’re a hammer, you just want to smash nails; if you’re a programmer, you just want to build features. But features do not a successful product make. This is the central myopia that eventually blinds even the most brilliant engineer-entrepreneurs, unless they’re smart enough to surround themselves with people who can check their bias.
If you want an interesting example of this phenomenon, look no further than Adam Bosworth, the co-founder and chief technology officer at San Francisco-based health gamification startup Keas. There’s no question about this guy’s brilliance. At Citicorp in the late 1970s, he invented an analytical processing system that helped the bank predict changes in inflation and exchange rates. At Borland, he built the Quattro spreadsheet, and at Microsoft, he built the Access database. He was one of the first to propose standards for XML—the foundation of most Web services today. At Google, he helped to develop Google Docs before moving on to start Google Health.
But as everyone knows, Google Health was a failure—and so was Bosworth’s next effort, Keas, at least until the venture-backed startup went through a dramatic pivot in 2010. How Bosworth figured out that his old approach wasn’t working, and how Keas reinvented itself as a provider of health-focused games for large employers, is the tale I want to tell you today.
