is often at odds with both the point above and below it. When a company is in rapid growth, there may be a point where the talent they relied on is not quite ready for the promotion they are hiring in for. Without expanding that search outside, you may become stale in the organization, and not provide the right mentorship to ensure that those interested in getting promoted will be able to do their job properly once there. I think the point should be, that you would want to ensure that those you import will be able to help promote from within as things progress.
I've actually been approached by recruiters in a few companies who want me to come in and "upgrade" the whole tech stack. I ask them what's wrong with it? It turns out management was not happy with it being built in a homegrown framework by a junior, even though it was functioning fine.
Situation for the last point: I was asked to come in for a years old team. The team didn't know source control or agile. But because a large number of them were used to operating without these tools, it was extremely difficult to get them to adopt proper techniques, and we only got the juniors and testers to use Git.
This, so much. No matter how many first-years physics students you have, you're not going to invent general relativity.
Related: Focusing on a single product when your customers rely on you for a suite. As I like to put it 'Being able to talk to the whole story'. Particularly relevant for MSPs - I once worked for one that went HARD on 'cloud first' to the point they stopped talking to clients about anything else.
Great, except all those clients lost interest real quick and switched to other providers who would talk to them 'about their whole story'.
The short sightedness of this is astounding - For many of those ex clients today, cloud is no longer 5 or 10% of their story, and we would have been able to continue selling to them all the way to their current adoption rates (50%+), IF we had taken them on the journey instead of refusing to talk to them about anything else.
* Spending too much on marketing/sales before people want the product. They usually just end up burning their brand if the product is too low quality.
* Too much focus on building multiple small features rather than focusing on the value proposition.
* Trying to negotiate deadlines for product development. "We don't have two months to finish this. Let's do this in one." In software estimation, there's the estimate, the target, and the commitment. If the commitment and estimate are far off, it should be questioned why, not negotiated.
* Hiring two mediocre developers at half the salary of one good developer. They usually can't solve problems past a certain treshhold.
* Importing tech talent, rather than promoting. Usually the people who have built the product have a better understanding of the tech stack than someone else they import.
* Startups that rely on low quality people to skimp on the budget. These people later form the DNA of the company and make it difficult to improve, if they're not the type who improve themselves.