if the fire started due to something you helped create and you have even a smidgen of impostor syndrome, fighting fires is about about saving yourself and cleaning up the messes you've made. the only way to prevent this is to build a team with a strong sense of collective ownership/responsibility and a healthy attitude towards mistakes.
If quality mattered, the best engineers would be making the fewest mistakes because mistakes are way more expensive than getting it right
She created these cluster fcks and then would throw out her shoulder patting herself on the back for putting it out.
She was in a constant state of panic. It was exhausting to watch her work.
Until you've been through another 30 years.
You haven't even reached mid-burn yet...
Like when I was an engineer, boom move get things done produce actual results, something would be deployed and value would be delivered, now, if I want to get something done, engage with two or three other teams to do something, talk with their team leads, then the actual engineers, then have a meeting to actually discuss requirements, and what should be a simple program that takes 3 api calls, turns into a 3 month long project.
Do all of the meetings/emails have to happen serially and in that order? If so, why?
Maybe look up what Amazon does with its 2-pagers and 6-pagers. See if you can do something similar where you are.
If it's really such a simple solution and that's obvious early, can you propose the obvious solution when you see it and get reactions?
If you're the only architect, you may have to define some of this stuff and make your changes part of the corporate culture.
If you have any PM buddies (whichever type of P), ask them for advice. A lot of this is their bread and butter, and if they already know your org, they'll have special insights.
I think part of it is that people get too wrapped up in their local world and don't see the big picture. For instance "If we don't get this widget added to the thingamabob in the next 3 days the company will go under!" when the thingamabob is just a minor piece of the puzzle for the larger company. Part of it though is driven from the top.
The one downside to having had this realization is it goes both ways. It also means that very few things you do have impact in a positive way as well. For some people this can be motivation killing.