4 ms·

Rightsizing [for what] is the question. GP assumes the goal is to do just enough to keep the product alive. This usually means a degraded customer experience.

• andsoitis 3y ago
  > GP assumes the goal is to do just enough to keep the product alive. They wrote "mature and don’t need a lot of work". Why would anyone put lots of people on a product that is mature and doesn't need a lot of work? > This usually means a degraded customer experience. Why? If the product is mature, works well, then surely you need fewer people to keep it in good shape and support customers?
  • Keegs 3y ago
    Of course you can maintain mature products with a smaller workforce. I’m pointing out that intent makes a difference. If Bending Spoons plans to put the apps on life support and squeeze out revenue - a fair assumption - then user experience will suffer.
  • blamarvt 3y ago
    > Why would anyone put lots of people on a product that is mature and doesn't need a lot of work? Nobody is suggesting anyone put 'lots of people' on a mature product. However, there are always things that need to be done. Apps need to be updated for new devices, OS/library/security updates, and general bug reports to name a few. That's just on the app side, the same is true for any build pipelines/hosting infrastructure. These apps don't run themselves regardless of how mature they are. You're right in that fewer people are needed and I'm all for optimizing but what I feel like you're missing is that it's quite easy to over-optimize for cost at the expense of users.