4 ms·
I disagree. Startup employees care about making a good product, too. That's the rule when you join a startup: you won't have the highest salary, and maybe your
by palata 4y ago
I disagree. Startup employees care about making a good product, too. That's the rule when you join a startup: you won't have the highest salary, and maybe your startup bankrupts in 6 months, but you get to have more impact.
If you don't want the risk and don't want to care, go in an established company.
But that all means that you should be transparent with startup employees, because many decisions depend on that at all level. If you hire employees who believe that they have infinite time and money to get the product to work, then you probably did not hire well, IMO.
- webmobdev 4y agoSure, employees should care about making a good product, and should be provided all relevant info they need for that. They however do not need to know everything about how the business is run. Their focus should be on making the product.
- palata 4y agoI would argue that it is often relevant for the technical employees to have an idea about how business is going: who wants the product, how they (intend to) use it, and also who discussed a partnership and eventually did not go with the product. As you said, not everyone can be into business. Which also means that not everyone can be technical. Who says that the business people are good at translating requirements from potential clients to technical employees? Isn't it likely that the technical people know more about what is technically possible? If you share too much with your employees, what's the worse case? They leave with that data? So what? If the whole value of the startup is that the founder knows a bunch of business numbers, anyway it doesn't sound very promising. However, if you don't share enough, maybe you miss very good solutions that they would come up with if they had access to all the data. Worse: if your interpretation of what the customers want and what is technically possible is slightly wrong, maybe you will send your whole startup in the wrong direction. All that just because you thought you knew what your technical people needed to make a good product.