I very much agree. But I think it still leaves a problem. In my experience, sometimes the camps of 'business' and 'development' find themselves unable to have a conversation on common ground, and that makes the "passion+curiosity" test difficult to do. This often exhibits itself through language (one or both uses words the other cant understand), which maybe a symptom of domain protection.
My advice to someone who is trying to find someone who has a different skill set to theirs: find a way of talking about your domain in a way that can be understood by a bright lay-person. Then encourage them to do the same with their domain. If they can't / won't do that, then move on. If they can do it, then you can have meaningful conversations in which you can figure whether your goals are aligned, and how you can each help reach those goals. From there, it should be obvious whether you want to work with them (assuming they aren't lying through their teeth :)
The other night I spent half an hour in a bar waiting for friends, eavesdropping on the conversation at the next table. It was two young guys (mid-20s) talking about search engines, both obviously comfortable with business concepts, one with a decent technical understanding and the other not so much. I gathered that they lived in the neighborhood, and I knew they needed to be extremely well-off to do so, so I was naturally curious about what kind of people make so much money so fast in technology. Were they, I wondered, extremely bright?
I figured out quickly that the technical guy was pretty bright, but I never got a hand on the other guy. He exhibited behaviors that I associate with idiocy or flat-out frat boy douchebaggery: making things up, pretending to understand things he didn't, ridiculing ideas that he didn't even pretend to understand (I'm not making that up), bragging about himself, continuing stories after his listener had pointed out that their premise was factually untrue, and so on. Yet occasionally he said something that made me think no, a stupid person could never have said that. Plus the technical guy, who apparently knew him well, was taking all of this douchebaggery in stride and was talking to him as if he were an intellectual equal, not holding back or simplifying at all. The technical guy had apparently known this guy long enough to realize that he was much smarter than he seemed.
Even the fact that the technical guy consistently, quietly corrected the other guy's facts -- and then sat patiently while the guy finished his story despite the fact that the correction removed both the point and the credibility of the story -- seemed to indicate that they had a considerable level of mutual comfort and respect. I mean, if the guy had really been a complete idiot, the technical guy would not have bothered correcting him so often. Not to mention that an arrogant idiot would not have been so tolerant of correction as this guy was.
Anyway, that whole story was just to illustrate that there is a huge cultural gap between technical people and nontechnical people. The way that guy acted, I would not have trusted him to feed my goldfish. Apparently, though, he was a bright guy who had learned a different set of social mores.
> there is a huge cultural gap between technical people and nontechnical people
100% agree. It's sometimes staggering how big it is. My point is that a small amount of effort can go a long way to bridging the divide, and using common language is a powerful first step.
I very much agree. But I think it still leaves a problem. In my experience, sometimes the camps of 'business' and 'development' find themselves unable to have a conversation on common ground, and that makes the "passion+curiosity" test difficult to do. This often exhibits itself through language (one or both uses words the other cant understand), which maybe a symptom of domain protection.
My advice to someone who is trying to find someone who has a different skill set to theirs: find a way of talking about your domain in a way that can be understood by a bright lay-person. Then encourage them to do the same with their domain. If they can't / won't do that, then move on. If they can do it, then you can have meaningful conversations in which you can figure whether your goals are aligned, and how you can each help reach those goals. From there, it should be obvious whether you want to work with them (assuming they aren't lying through their teeth :)