Building a product or business is a multi-skilled task. Broadly speaking you need to cover product development, marketing, finance.
Good leadership covers all 3 bases, but leadership in the latter 2 is more important than leadership in product.
Which sounds backwards, but you're the tech guy providing the tech. Leadership is figuring out what / how / to who of marketing coupled with the balancing of finances to make the business work.
VC funding of course up-ends this model. It removes financing and marketing (and even product fit) from the equation. Here's a pile of money, "go build something and we'll figure out the rest later..."
Sure 90% fail to figure it out, and the business part fails, but that's OK because the VC (although not always the techie) comes out a winner. It's a great model to handle the edge-case of good ideas that are hard to pull off.
If you end up in a non-vc business though, don't be surprised if most of the layers above you don't care about the tech.
Nvidia’s CEO is technical. Google’s was technical for a very long time. AMD’s is technical. Amazon’s was for a very long time. Microsoft’s was for a very long time and is again.
I think it’s a bold claim to make that technical people are only capable of designing for technical people. There’s plenty of people who understand how to build products that connect to the consumer and non-technical people don’t have a unique ability to do so.
I agree that many technical people don't give a shit about users or usability. However it is also true that non-technical people often don't give a shit.
Making sweeping assumptions about a group will only harm yourself.
Good techos must also be good at talking with users and understanding user needs: it is a critical skill for designing user interfaces (software or hardware). Anyone lacking user facing skills severely limits their salary and career choices.
There's a reason so many development methods and startup advice focuses on the user.