Software architects who excel in their role take responsibility for their work. As a leader of the team, it is important to take responsibility for your work and not make excuses. It is easy to take responsibility when things go well, but being a leader means accepting responsibility when things do not go well. When things go wrong, rather than making excuses or blaming others, it is more productive to use that time and energy to come up with options for how to alleviate the issue. I think that most people, including myself, really respect colleagues who take ownership and responsibility.
If everyone on the team takes responsibility, that type of collective attitude prevents software rot or disorder within a software system. Degradation of software can occur for a variety of reasons. One typical cause is the overall culture of the work environment...
