|
I think the frame of "Business/Idea Guy" vs "Technical Guy" is a mistake. Where does design fit into all of this? I can imagine an "Idea Guy" who just says "let's make AirBnB for pets" or something, and then the "Technical Guy" designs and codes everything according to loose goals stated by the "Idea Guy." In that setup, clearly unless the "Idea Guy" has a truly magical idea that he somehow has the means to protect, he's not worth much. But I can also imagine an "Idea Guy" who is also a product designer, who has a concrete vision for not just what to make, but how it should be implemented, how it should look and feel, what the process should be like, and so forth. He's synthesized a lot of complicated things and just needs a "Technical Guy" to translate his blueprints into a building. In this case, the "Idea Guy" is really valuable indeed, especially if his decision about implementation differentiate the business or otherwise drive it's success. In other words, execution is more than coding, it's making a ton of decisions. Value can be added by making lots of really good decisions, and you don't have to be a programmer to do that. Of course, if you have no familiarity with technology and can't see all of the possibilities, you won't make good decisions. |