The Sinking Enterprise Architect
posted by John Spacey, March 31, 2011Some Enterprise Architects (EAs) can't resist getting involved in solution architecture or infrastructure planning — the sinking EAs.
There are several motivations for EAs to sink:
1. Pressure to contribute to solutions for important projects
2. Refusing solution work often seen as lazy
3. Solution work can lead to personal recognition
4. Solution work is easier than tackling EA problems
5. EAs with a background in solution architecture or infrastructure — old habits die hard
Whatever the reasons, sinking EAs are bad for any enterprise architecture program:
1. Sends the wrong message about EA
2. EA work gets neglected
3. Sinking EAs often have trouble thinking like a EA
|
Learn about the 10 most important patterns for SOA success. |
|
A large collection of enterprise architecture tools. |
|
Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats.
~ Howard Aiken |
|
Imagine your hardcore IT geek talking to a company executive. What would they talk about? |
Recently on Simplicable
| The 5 Levels of Enterprise Integrationposted by Anna MarEnterprise Integration has traditionally focused on moving data from one database to another. Recent technology trends have challenged this approach. |
| Do "Real" Architects Dislike Technology Architecture?posted by Anna MarGo to any job site and query architect — you'll be hard pressed to find the adverts for construction architects in the sea of job postings for technology architects. |
| 101 Game Design Principles for Social Mediaposted by Anna MarThe convergence of social media, software and gaming. |
| Business Capability Mapposted by Anna MarThe most important diagram in all of business architecture — without it your EA efforts are in vain. |
