Most companies start out with people that are flexible and capable to do a lot of different things. As you grow, it becomes more and more important to have spec

Most companies start out with people that are flexible and capable to do a lot of different things. As you grow, it becomes more and more important to have specialists that focus on only a small fraction of the overall work you have to do as a company. Here is what I would do: * let people work in small teams/duos * share knowledge by using a Wiki [1], especially the leaders (the flexible people) should write down as much as possible, but collaborate on the knowledge base (answer questions, add stuff that's missing) * take meetings as needed (don't overdo this, nobody likes to sit in unnecessary meetings) * automate as much as possible, the common developer does not need to know exactly how the build pipeline works (but a few people should) * let people try out new things, this keeps them motivated and improves themselves as well as spreading their own knowledge to co-workers [1] I found this to be very efficient if you have a team that has the right mindset. If you start out with people that are not used to document stuff, it'll be hard to get your knowledge base going. You can take a look at the product we build Emvi (https://emvi.com/ https://emvi.com/), which aims to solve some of these issues.