@1ftt+180e5Oyx
What you said makes sense and I agree. That's not what I was saying. If you're making drastic changes to the organizations you have to sort out what things change and what don't. There will surely be more org changes and things need to get sorted out over time. Without hearing what was said, it's a bit tough to understand context. Heck, just this week I've run into situations where we were working with a team and the manager was laid off. That pretty much threw that person's direct reports into confusion on what they're going to do now.
Bottom line is the orgs can only handle so much change and you don't want to break anything that works. Saul's DR's and 2 downs already have a c-ap done going on with more stuff being thrown on the pile of work to do beyond actually developing and supporting systems. App health, CI/CD, api, resiliency, app decom, cloud, auto testing, etc. etc. And that's while throwing a monkey wrench into the org by cutting head count.
I honestly am concerned there will be too much change they're trying to implement.