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.
Trap #195 – Not following the conversation Architecture concerns are the criteria to assess acceptability. Enterprise architects’ highest value is assisting stakeholders identify the best path to improving their organization. Then provide the governance tool […]Read More
Trap #7 – Asking the Easy Question Enterprise architects are in the room to address hard questions. Questions whose answers serve divergent outcomes. Crash and burn stories Too many EA teams are low functioning. Literally […]Read More
Trap #53 Starting From Scratch 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. If […]Read More
Trap #2 Not Making Progress 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. Low-functioning […]Read More
Trap #1 Trying to Own Decision Rights 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. […]Read More
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