Modernization Matrix RACI

Content owner: orlando.pereira@roche.com

Purpose

The Modernization Matrix RACI defines who owns, contributes to, validates, and maintains the Modernization Matrix.

It keeps assessments evidence-based, consistently facilitated, and focused on actionable modernization priorities. Architecture owns the method and scoring consistency. Product Family Leads own the product family scope, business context, and follow-through.

RACI Legend

Code Meaning

A

Accountable: owns the outcome and final decision.

R

Responsible: performs or drives the work.

C

Consulted: provides input, review, challenge, or expertise.

I

Informed: kept aware of progress, outcomes, or decisions.

Roles

Role Contribution

Architecture Team

Owns the framework, facilitates assessments, defines scoring logic, and ensures consistency across product families and domains.

Product Family Lead

Owns the product family scope, business context, stakeholder engagement, remediation planning, and progress tracking.

SMEs

Provide technical and operational evidence across infrastructure, security, delivery, data, operations, reliability, and dependencies.

Domain Leads / LT

Confirm business criticality, usage context, and prioritization relevance so decisions reflect business impact.

Architecture Catalysts

Review results, challenge inconsistencies, resolve escalations, and endorse remediation actions.

Modernization Matrix RACI

Theme Activity Architecture PFL SMEs Arch Catalysts Domain Leads / LT

Modernization Matrix

Define dimensions, scoring logic, and evidence rules

A/R

I

I

C

I

Modernization Matrix

Update the matrix over time

A

I

I

R

I

In-scope

Propose in-scope applications

A/R

C

I

C

I

In-scope

Confirm in-scope applications

R

A

I

C

I

In-scope

Set benchmark priority or business criticality

C

A

I

C

I

Benchmark workshop

Facilitate benchmark

A

C

C

R

I

Benchmark workshop

Provide system facts and evidence

C

A

R

I

I

Benchmark workshop

Gather technical and operational evidence

C

A

R

C

I

Benchmark workshop

Challenge inconsistencies and ensure scoring consistency

A/R

C

C

R

I

Validate scores

Consolidate draft scores

A/R

C

C

R

I

Validate scores

Validate final score per system

A

R

C

C

I

Actions and roadmap

Propose remediation actions

R

A

I

I

I

Decisions

Approve modernization priorities

C

C

I

C

A/R

Track progress

Reassess periodically

R

A

C

C

I

How to Apply the RACI

1. Confirm Scope

The Product Family Lead confirms the product family and applications in scope. Architecture supports scope definition and ensures the selected systems can be assessed consistently through the Modernization Matrix.

2. Prepare Evidence

The Product Family Lead brings the right SMEs into the assessment. SMEs provide current, specific, and traceable evidence such as architecture diagrams, operational metrics, lifecycle status, security findings, incident history, delivery data, dependencies, or platform constraints.

3. Run the Benchmark Workshop

Architecture and Architecture Catalysts facilitate the benchmark using the agreed dimensions and scoring rules. The workshop should focus on evidence-based scoring rather than opinion-based ranking.

During the workshop, participants should capture evidence, record assumptions, identify gaps, and challenge inconsistent scoring across similar systems.

4. Validate Scores

Architecture consolidates draft scores. The Product Family Lead drives final validation per system with input from SMEs and Architecture Catalysts.

Validation confirms that scores are evidence-backed, consistent, business-aware, and ready to inform prioritization.

5. Define Actions

The Product Family Lead owns the translation of validated results into remediation actions and roadmap input. Architecture contributes recommendations and ensures alignment with target architecture direction.

Actions may include refactoring, re-platforming, security or resilience improvements, dependency reduction, operational maturity improvements, consolidation, retirement, or further discovery.

6. Approve and Track Priorities

Domain Leads / LT approve modernization priorities based on validated assessment outcomes. The Product Family Lead tracks progress and drives periodic reassessment with support from Architecture, SMEs, and Architecture Catalysts.

The Modernization Matrix should remain a living input to modernization planning, not a one-time scoring exercise.

Expected Outputs

A completed assessment should produce:

  • Evidence-backed scores per system

  • Documented assumptions, gaps, and disputes

  • Validated modernization priorities

  • Proposed remediation actions

  • Clear ownership for follow-up

  • Reassessment cadence or trigger

Review Triggers

Review the RACI and Modernization Matrix when:

  • Scoring dimensions or evidence rules change

  • Product family scope changes

  • Major platform, technology, or operating model changes occur

  • Major remediation actions are completed

  • Modernization portfolio priorities are reviewed