EA Plan -1st Q

🎯 How I Would Approach My First 90 Days as Enterprise Architect

🗓 First 30 Days – Onboarding, Assimilation & Leadership Alignment

Objective: Understand, align, and avoid disruption.

In the first month, I focus on three parallel tracks:

1. Formal onboarding

2. Business & cultural assimilation

3. Clear alignment with my reporting leader

1️⃣ Leadership Alignment (Critical – Week 1 Onwards)

Since my boss hired me, I would prioritize 1:1 alignment early.

I would explicitly ask:

• What strategic outcomes do you expect from me in 6–12 months?

• Where do you see architectural gaps today?

• Is my role transformation-driven, stabilization-driven, or governance-driven?

• What political sensitivities should I be aware of?

• Which initiatives do you want me to influence first?

This ensures:

• I support his/her strategic theme

• I don’t unintentionally disrupt existing power structures

• My priorities reflect executive expectations

Before influencing the organization, I must be aligned with the mandate.

That’s realistic EA behavior.

2️⃣ Formal Onboarding (Weeks 1–2)

Complete:

• Organization structure understanding

• IT operating model

• Security & compliance onboarding

• Tooling landscape (JIRA, DevOps, cloud, repos)

• Review standards, principles, reference architectures

• Governance forums (ARB, CAB, steering committees)

• Current technology baseline and roadmap

At this stage, I absorb — not judge.

3️⃣ Business & Strategy Understanding

I would understand:

• Top 3 business priorities

• Revenue growth vs cost pressure

• Regulatory exposure

• Digital transformation commitments

Architecture must reflect business temperature.

4️⃣ Cultural & Decision Mapping

• Who really makes decisions?

• Engineering-led or business-led?

• Centralized vs distributed governance?

• Is architecture influential or bypassed?

If culture is delivery-heavy, I will not introduce heavy governance early.

5️⃣ Stakeholder Listening Tour (Weeks 2–4)

Meet:

• CIO / CTO (ongoing alignment)

• Business heads

• Engineering leads

• Cloud / Infra

• Security

• Data leadership

• Senior delivery managers

Ask consistent questions:

• What are your top priorities?

• Where does IT struggle?

• Where does architecture help or slow you down?

• What worries you in the next 6–12 months?

Goal: Context + trust + perception mapping.

6️⃣ Review Current Initiatives & Pain Points

Understand:

• Major in-flight programs

• Programs under stress

• Cloud migration status

• Audit findings

• Integration complexity

• Tech debt hotspots

As a new EA, I support existing momentum — not introduce new transformation.

🗓 30–60 Days – Support & Stabilize

Objective: Move from observer to contributor.

1️⃣ Embed in 1–2 Critical Programs (As Directed by My Boss)

I would ensure these align with leadership priorities.

Support by:

• Clarifying architecture direction

• Reducing rework

• Aligning cross-team dependencies

• Introducing lightweight guardrails

Goal: Delivery feels supported.

2️⃣ Validate Governance & Standards

Instead of rewriting:

• Are standards practical?

• Are they followed?

• Is ARB effective?

Refine selectively. No structural overhaul yet.

3️⃣ Provide Leadership Feedback Loop

By around Day 60, I would sync back with my boss:

• Observations

• Early risks

• Organizational dynamics

• 2–3 improvement opportunities

This keeps executive confidence high.

🗓 60–90 Days – Establish Direction & Credibility

Objective: Gradually move toward structured influence.

1️⃣ Propose 2–3 Practical Improvements

Examples:

• API-first integration model

• Cloud guardrails & FinOps visibility

• Data ownership clarity

• Observability baseline

• Lightweight intake process

Small but structural.

2️⃣ Align with 12–18 Month Business Strategy

Present:

• Architectural capability gaps

• Risk exposure areas

• Prioritized roadmap aligned to:

  • Revenue

  • Cost

  • Risk

  • Compliance

3️⃣ Relationship Capital

Influence > AuthorityTrust > FrameworksSupport > Control

Architecture becomes embedded only when delivery trusts it.

“In my first 90 days, I would focus on onboarding, assimilation, and leadership alignment. Since my reporting leader hired me with specific expectations, I would first clarify the strategic outcomes expected from my role and align my priorities accordingly. I would then understand business goals, cultural dynamics, governance maturity, and ongoing initiatives. Rather than introducing large-scale transformation early, I would embed myself in critical programs to support delivery and build trust. By the end of 90 days, I would present incremental architectural improvements aligned to business and executive priorities. My goal is clarity, credibility, and alignment — not disruption.”