https://www.google.com/search?q=%22People%2C+Organisation%2C...
EDIT: Removed quotes.
(warning: 8.1MB PDF) http://foiaelibrary.gsfc.nasa.gov/_assets/doclibBidder/tech_...
They may not refer to the acronym "POSTED" exactly, but said acronym is what I learned and I thought highlighted the scope of what a system covers, specifically that it is not just the equipment i.e.: software. In the NASA SE Handbook, page 3 says the following, which essentially maps across to what I described:
"A “system” is a construct or collection of different elements that together produce results not obtainable by the elements alone. The elements, or parts, can include people, hardware, software, facilities, policies, and documents; that is, all things required to produce system-level results."
Same idea either way - the system is far more than just the equipment/technology.
"People Organization Support Training Equipment Doctrine POSTED"
We DID IT! We made it a THING!
EDIT: To be precise, I see [1], plus two mirrors of it, plus two links back here, but only from my phone. On my desktop I get zero results.
[1] http://parlinfo.aph.gov.au/parlInfo/search/display/display.w...
I favour (!) British spelling too but 'organization' is more correct in the etymological sense as it derives from the latin 'organizo'. The British form is in a way a corruption itself because it favours 'ise' as it is easier than learning the etymology. 'Oxford Spelling' is an etymologically correct variant of British spelling.
You are making it clear that you have an emotional interest in the story, and the people responding to you are just readers of this website.
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.