In company-managed projects, workflows, permission schemes and field settings are shared objects. Several projects can point at the same workflow, so one edit changes how all of them behave. Team-managed projects keep their own configuration, which is safer to change and harder to keep consistent.
Before you change anything shared, list who uses it. Here LARK and HELP both use the Delivery workflow. A service team asking for an Escalated status should not give the dispatch team an Escalated status too. The safe move is to give HELP its own workflow, check that every status its current work items sit in exists there, and only then switch the project.
The reverse applies too. A change one team needs might be right for everyone, and copying configuration for each request leaves you maintaining ten near-identical workflows. Decide on purpose. This practice site lets you edit workflows and point a project at one; hosted status migration screens and scheme mapping are not simulated.
Change shared configuration only on purpose, and split it when only one team needs a change.