Scaling Engineers Doesn't Mean Scaling Work

Been thinking about this for a while, so lemme just put it out there. The Observation: Scaling People vs Scaling Work Started from an idea about developers. Instead of keeping devs locked into frontend or backend only, we expand their scope. They become more general, but still keep their main strength. With coding agents, this makes even more sense. Tasks that use to be blocked can now get done faster. More people can help. Work moves quicker. In short, we scale people . And this part? It works well. But then I started thinking deeper, and noticed another layer. Kinda interesting actually. When we scale people, the work itself don't scale in the same way. We got more people who can execute now, but the number of ideas and problems still depends on the product team. Their size stays the same. Coding agents help us build faster, yeah, but they don't create new product ideas or new directions. So you end up with all these people ready to work, but the amount of meaningful work? It stays l