Somebody once told me the following and it's particularly relevant for software architects.
Share the successes with your team, take on the failures yourself.
From a software architect's perspective, you can't necessarily blame the development team for failure. If your architecture didn't meet the non-functional requirements, that's your fault. If the system didn't meet the functional requirements, that's also your fault (probably jointly with the other senior members of the team). If the quality of the system wasn't of a high enough standard, that's your fault too.
If you have junior people on the team and your project fails, the senior people should take that failure on themselves. You can't simply push it onto the development team because it's the senior members of the team that have most the influence to make things happen, not them. Software architects are senior members of the team and the responsibility for the success or failure of a project is in there hands.
Simon is an independent consultant specializing in software architecture, and the author of Software Architecture for Developers (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.