Enterprise Architecture Graveyard
Crash and burn stories
We all know too many EA teams are low functioning. Literally hanging on by their fingernails. If you see these practices, stop! Stop now! Do your part to professionalize enterprise architecture.
Every enterprise architecture trap outlines what we see and then explores how to overcome the challenge and become a better architect.
High functioning EA Teams are efficient. They aggressively use other people’s reference architectures. They leverage an EA repository. Crash and burn stories Low-functioning EA Teams. One anti-pattern after another.
Enterprise architects at the top of their game develop architecture. An enterprise architecture is useful while it is being developed, and after the stakeholder approves it. We use diagrams.
There is a frankly alarming trend in the EA profession: short-lived EA Teams. High functioning EA teams align their deliverables to the business cycle and use a structured repository.
Stakeholders own the enterprise architecture and all decision rights. They approve the target architecture. They decide how to address compliance failures. Crash and burn stories Low-functioning EA Teams.
We develop EA Teams every day. We see what works. We see what crashes. We see what crashes and burns.
Learn the failure patterns to avoid
Be a better architect
Free 90-day Personal Enterprise Architect Kickstart to be a better architect.
Weekly recorded webinar, with downloads