It targets people. It focuses on users. And Apple lets them decide how and where they’ll use its products.
This sounds simple, but in my experience very few companies think this way. Most startups write business plans that dredge up IDC data on market size, then define their target market (e.g., “Global 2000 enterprises”). Few seem to realize that there are people employed within these target markets, and these people will be the ones who actually embrace or reject one’s product.
Indeed, I’d go so far as to suggest that this is one of the primary failings of most enterprise software today: It’s built for enterprises, not for people employed by the enterprises, a theme echoed by noted developer Michael Nygard.
Not all companies screw this up. The open-source world offers a few good examples of companies that understood their target market was the individual, not the tribe/company.
Marc Fleury’s JBoss, for example, understood its target market was the developer buried within corporate IT. All JBoss’ early marketing was focused on developers, not CIOs, and its product development was focused on making developers happy. Only later did those developers return the favor by pushing JBoss into serious production, requiring the CIOs to get involved.
Along the way, JBoss took its share of criticism for this indifference to decorum and CIO concerns, including accusations that the company “astroturfed” to drum up developer support. True or not, the accusations don’t diminish JBoss’ clear success winning over developers by catering to developers.
The same is true of SpringSource, which fought off the accusation that it wasn’t “enterprise ready” by being “developer ready” from the start, and focusing relentlessly on pleasing its target market: the developer.
This is how great companies are built: they focus on individuals and build exceptional products for them, and let these individuals determine how best to make use of the technology.
Nice summary of the value of people-centered design.