Remove USD averages from expenses policy because they don't reflect a global company

Why is this change being made?

As a globally-distributed company, presenting USD averages for expensible items is non-inclusive, and is causing friction and confusion with new employees. I've already raised this, with evidence, for desks but received no replies.

I'm proposing that we remove these "averages" entirely for the following reasons:

1. They don't appear to be evidence-backed
2. They are not representative of global markets
3. It's counter to our policy of "expense what you need to do your job"
4. The friction caused by this is likely more expensive in lost productivity than what we save, if anything
5. Nobody seems to take ownership of these numbers, or who is responsible for them is not clear

As a case study, let's take desks. The "USD Average" is $500, which can get you two sit/stand desks in the UK:

1. An IKEA Bekant. Well known to be unstable. Out of stock everywhere and stores are closed. Not available in 180cm top.
2. An Autonomous. 2-3 month shipping delay at the moment, possible import duty, numerous poor reviews & not available with a 180cm top.

I've compiled a (non-exhaustive) spreadsheet of other prices here: https://docs.google.com/spreadsheets/d/1lxWOK-5Tq9PN6_8K8J5ULG-9vlp2nzrRHHbo8RnfFbw/edit?usp=sharing

So as the UK average for desks works out more like $900, do UK team-members only get to expense "half a sit/stand desk"? Surely we should be aiming to equip our team equally, within reason, no matter their location, and therefore anybody should be able to expense "a sit/stand desk" to do their work.

As the system currently sits, we're sort-of-providing-a-guideline-but-not-really and it's open to interpretation. If listing average prices is deemed important then these should be evidence-backed, based either on the average of items expensed in Expensify, or by providing evidence of the average prices per region and providing a more inclusive global average.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the change relates to any part of the project other than updates to content and/or data files (e.g. team.yml) please make sure to ping @gl-static-site-editor in a comment for a review and merge.
  • If the DRI for the page/s being updated isn't immediate clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies

For help with failing pipelines reach out in #mr-buddies in Slack