You join a large enterprise as Enterprise Architect. What do you do in the first 90 days?
Short answer
Listen and diagnose (strategy, pain points, portfolio, delivery metrics), build lightweight artifacts that inform decisions (capability heat map, application inventory, key risks), set up a fast governance mechanism with clear principles, and deliver two or three visible wins tied to executive priorities.
Detailed answer
| Days | Focus | Outputs |
|---|---|---|
| 1–30 | Listen: CEO/CIO/CTO priorities, business unit heads, delivery teams, operations, security, finance | Stakeholder map, top problems, existing artifacts reviewed |
| 31–60 | Diagnose: capability heat map, top-200 application inventory with cost and risk, integration landscape, technology lifecycle risks | Draft current-state view, opportunity list |
| 61–90 | Act: architecture principles (8–12), lightweight review process, 2–3 initiatives with measurable value (e.g. retire duplicate CRMs, API platform), first roadmap | Principles, governance charter, roadmap v1, early wins |
Real-world example
An EA who started by publishing a 200-page current-state document lost momentum; one who delivered a one-page capability heat map linked to the budget cycle in week 6 gained executive sponsorship.
Follow-up questions
- How do you get buy-in from delivery teams? (Solve their problems: templates, faster approvals, platform improvements.)
- What would you deliberately not do? (Exhaustive modeling, heavy gatekeeping.)
What the interviewer expects
Business orientation, prioritization, lightweight artifacts and an understanding that EA earns influence through value.
Common mistakes to avoid
Starting with tool selection or a complete repository; imposing governance before trust exists.