I have said many times that what EA means to me is well orchestrated change… the ability to create a design for the future and work within the current environment through well orchestrated change to realize the vision.
The fact is this is not something that will happen overnight. One of my favorite sayings is changing an organization is like turning the titanic with a wooden spoon… and some days it feels like the wooden spoon is being eaten by fish.
I want to share three of my techniques for helping an EA Practice in it’s first year…
- Start passively – year one is all about “influencing change” … listening, observing, validating the design, and planting seeds.
- Educate through example – pick one project, and run it as an EA influenced project to show the benefits and value,
- Stay in your lane – think strategically by connecting the dots to ensure:
- information flow is not being impacted across the organization,
- reusable components are used across business areas and departments and
- priorities and dependencies across all 5 architectural disciplines are not overlooked.
The job of the EA Practice is to create a design and be armed with a million ideas for how to implement it and be able to pivot the thinking based on the environment, priorities and discussions at hand.