Technology Standards and Architecture Roadmaps

Managing a technology radar and standards lifecycle, and building enterprise architecture roadmaps with transition states, dependencies and value milestones.

Technology standards

Maintain a catalog of technologies with lifecycle status, popularized as a technology radar (ThoughtWorks): Adopt, Trial, Assess, Hold. Enterprises often use: Preferred, Approved, Contained (no new use), Retiring, Prohibited.

Category Preferred Contained Retiring
Language/runtime Java 21/25, TypeScript, Python 3.12+ Java 11 Java 8
Relational DB PostgreSQL (managed) Oracle (existing systems) DB2 on AIX
Messaging Kafka platform, SQS RabbitMQ (existing) IBM MQ for new integrations
Integration API gateway + events ESB Point-to-point file transfers

Each entry: owner, support model, versions supported, end-of-support dates, guidance and reference architectures.

Architecture roadmaps

A roadmap shows how the enterprise moves from baseline to target through transition architectures, sequenced by dependencies, value and risk.

gantt
  title Customer platform roadmap (illustrative)
  dateFormat YYYY-MM
  section Foundations
  Cloud landing zone             :done, 2026-01, 2026-04
  API platform & identity        :active, 2026-03, 2026-08
  section Customer domain
  Customer MDM (golden record)   :2026-06, 2026-12
  Digital onboarding             :2026-09, 2027-03
  section Retirement
  Legacy CRM decommission        :2027-02, 2027-06

Good roadmaps include: business outcomes per milestone, dependencies, transition states (what runs where at each point), retirement dates, funding and risks. Update them quarterly.

Interview questions and answers

How do you retire a technology that 40 applications use?

Mark it Contained (no new usage), publish the replacement standard and migration patterns, prioritize applications by risk/end-of-support, fund migrations through the portfolio process, track progress publicly, and set a firm end date with exceptions requiring executive approval.