3 ms·
I was afraid that this was going to be a post on solving hard technical things early. Which is a terrible idea, because it's basically making large bets on your
by wpietri 13y ago
I was afraid that this was going to be a post on solving hard technical things early. Which is a terrible idea, because it's basically making large bets on your future direction before you have any data about where you're going.
But this is actually pretty sensible. People learn culture mostly by osmosis, and the bigger you are, the harder culture is to change. If your organization is kinda screwed up at 5 people, it's reasonable to bet that growth will magnify the problems, making it pretty screwed up at 25, and a big ol' mess once you cross Dunbar's number at around 125.
- AnimalMuppet 13y agoYou're right, but people are going to take it wrong. If you're a startup, tackling a huge problem that you don't know how to solve is very likely to lead to failure. You are correct in that. But let's say you're starting a project. The technical part of the project is mostly straitforward, but there's this one part that you're not really sure anybody knows how to do. You'd better do that part earlier rather than later, or figure out a way where you don't have to do it. Find out how big the problem is when you still have time to do something about it. Find out if it will kill your project before you do a bunch of work that will be wasted because you can't solve the hard part.
- wpietri 13y agoI think these are both aspects of risk reduction. When you say "a project", I think you're saying, "Assume the business problems are solved." In which case, yes, technical risk is next. Startups too are faced with technical risk. But there's no point in solving technical problems until you have reasonable proof that doing so is worth your time.