Comment by citrablue

This is only valid if every new employee can contribute to core payments. Scaling laws indicate only a small number of employees can work on one products; additional employee resources might be a net negative.

It may be useful to think of a product/project as a bucket that gets filled via a Zeno's paradox, with possibly negative contributions. At a reasonably small scale (few hundred employees), it may be better to explore new buckets than to add another fractional (and potentially negative, independent of employee quality) unit to core skills.

>End of the day - every employee who is distracted by looking after the assets & numbers for these side projects is an employee who is not focused on their core payments system.