Earlier quoted context omitted.
Very typical. I've run into cases where an "idea guy" basically says "you do all the product and tech half, I'll do marketing and strategy." Which is dumb, because sometimes I'm legitimately better at the strategy half too. Generally these people want ridiculous equity splits of that nature. It's worth anyone technical's time to build skills in strategy, marketing, finance, etc. The technical co-founder always gets s…
> Which is dumb, because sometimes I'm legitimately better at the strategy half too A semi-related thought I've had recently: I've run into a number of non-technical product people that say that they're primary skill is that they have a great "product sensibility" that engineers lack so they need to step in and provide guidance. It's true that many engineer-designed products are terrible, but I'd argue that most engi…
Every feature, design decision, and iota of technical debt are money and time. Either that's raised and spent up front, eating at equity, or it is deferred until a point where revenue pays for it, it is redundant due to a pivot, or becomes so essential that new funding is raised (possibly from a pool that doesn't dilute so much value).
Presenting an accurate and fair cost / benefit analysis of these tradeoffs (at least on the technical side) is the main purpose of a technical lead. Non-technical business people can't get that information on their own. They should have a say in the decision if it materially affects the product's launch, but that's the normal give and take.