As the more people in your organization start using Wrike, the messier it can be figuring out which things belong to what teams. Even if those features are created at a space level (like a custom field), you'll have a hard time selecting the correct "Region" field when building a recipe in Workato. Yes, you could have fields at the account level that everyone uses, but that takes a lot of planning and coordination, and you need a solution with a faster turnaround.
Solution: Space abbreviaion as a suffix for all CFs, CITs, and custom statuses. This way each space can have options custom to itself, but the space context of that item follows it everywhere. I like to use a pipe delimiter, and then the suffix (example: "… | XYZ".
Do watch out for ripple effects when changing legacy names. They could break existing automations and recipes.
Also some features I build for multiple spaces, but it makes sense to always keep them at the space level. For example, I have a custom field to callout exclusions so the task/project doesn't qualifying to certain rules. For some spaces, that list of exclusions can be long. I like keeping this field localized to a space, so the list of exclusions doesn't become massive.\
Let me know some ways you keep your account organized with naming conventions.