Systems Engineering teaches the concept of POSTED: People, Organisation, Support, Training, Equipment and Doctrine. When a system is developed, it must give consideration to all of these aspects. Failing to do so means you design an incomplete system.
In this case, Uber has developed a piece of Equipment, their God Mode view. Franken's asking about the other pieces of the system, such as the training, support and doctrine and people. These are equally as important to design, document and implement. Failing to give due consideration to these aspects of the system is no different to having an incomplete equipment solution developed. I'm interested to see whether Uber gave due consideration to these aspects of the system.
There's something to be said about startups moving fast to develop technology but not necessarily the other aspects of a complete system. Mature systems engineering / software development firms do this day in and day out. Yes, it can lead to slower iteration on the core technology and capabilities, but it is critically important to consider. I suspect it's often a pinch point when start-ups try to scale, for example when a piece of technology then needs to consider user access rights, etc.