| I would call Jobs a "taste leader" (contrasting "thought leader." That is, he's someone you have to fit your work to the (very particular) aesthetic sensibilities of, if you have any hope of pursuing it. And I think this isn't an uncommon job-role, actually. Jobs wasn't uniquely flawed. There are "taste leaders" in other fields—this is what a movie director is, or a chef, or a newspaper's editor-in-chief, or any master of a trade. It's a job-role that's all over the arts. It's just not seen much in science-driven, engineering-driven, or business-driven industries, because taste doesn't usually drive customer-demand in these fields. Apple's consumer-electronics niche is even an exception within their larger field. (I.e. taste certainly doesn't drive computing products in general—just look at the "gaming" PC peripherals on the top of the Amazon rankings to see what I mean.) Usually, to get a project off the ground when a "taste leader" is in play, you have to ensure that your project is already to their tastes before they see it. That is, the taste-leader will can any project that doesn't currently fit their aesthetic, even if it might later fit their aesthetic. This is what forces the underlings of these people (in all of these fields) to work long hours, and to hide their work, and to lie about their work: they can't show it to the "taste leader" until it will suit their taste. Why is this done? Why do taste leaders do this? It's a pretty universal trait of taste-leaders in successful businesses, so it's probably a good strategy somehow (if it's not just an effect of success.) My guess is that taste-leaders do this for two reasons: • They think that if they don't, a project will gain momentum while still not matching their tastes, and then they won't be able to stop it from "taking off" once it has enough smiling, happy faces invested in it. They just won't have the heart to can it at that point, even if they think it sucks. Much easier to can it early. • They know that, by forcing everyone to adhere to this stringent set of aesthetic criteria at all times, they're imparting these same aesthetics to everyone around them. In order to please a taste leader, you can't just learn their tastes; you have to grok their tastes. Their tastes have to become your tastes. If you can't just iterate a project toward being something they like, but have to get it right from the start (or from the earliest point they're allowed to see it), then you have to be able to evaluate your own concept work against the aesthetic—and in fact use the aesthetic to figure out how to move across the fitness-landscape of possible features for the thing. And, if those two things are true, then "taste leaders" are probably not as flawed as you think—rather, they're playing a role. Some might play it naturally, but I think that for a lot of them, they know that this is how to best drive their business toward optimizing for their taste (which they believe is a taste customers have demand for.) That is: there are plenty of stories about people lying to Jobs. But did anyone ever get a chance to ask Jobs whether he knew they were lying, and just pretended to be oblivious to these skunkworks projects because he had faith in these people to eventually produce something he'd like (but just didn't want them showing their not-yet-aesthetic iterations off where others in the company could get excited about them)? I've known both chefs and directors who do this sort of thing. Why would Jobs be different? |