Architecture Path · The Leap · Step 8

IC to Head of Data Architecture

1,163 words5 min read

The bridge program for the deeply experienced individual contributor, twenty years and more in data, who is ready to lead but stuck in an IC role. It builds the missing capabilities that separate a senior practitioner from a Head of Data Architecture: enterprise influence, executive communication, stakeholder alignment, strategy, and leading through others rather than doing the work yourself.

8
Modules
40
Chapters
IC to Head
The leap
Capstone
Leadership portfolio + plan
The journey

Eight modules, one arc

The eight modules build cumulatively toward a real capstone. Watch the work move, and the value compound, at every stage.

M01-02MindsetFrom doing to directingM03InfluenceWithout authorityM04-05CommunicateExec & the big pictureM06StrategyVision & roadmapM07-08LeadTeams & the planSenior ICHead of Data Architecture

Each module builds the capability the next one depends on, ending in a portfolio-ready capstone.

Outcomes

What you'll be able to do

Shift from doer to leader

Move from delivering the work to setting direction and leading through others.

Influence without authority

Drive alignment across a federated organization you do not control.

Communicate to executives

Articulate the big picture clearly to a board, a CIO, and business leaders.

Manage senior stakeholders

Build trusted relationships and influence priorities across teams.

Own strategy and roadmap

Turn technical depth into an enterprise vision and a multi-year roadmap.

Lead a team and land the role

Build and lead an architecture team, and execute a plan to reach the role.

Curriculum

8 modules, 40 chapters, ending in a capstone

Eight modules of five chapters each, sequenced so the material builds cumulatively to a real, portfolio-ready capstone. Expand any module for its focus and lessons.

01 Why Experience Alone Does Not Promote You

Understand the real gap between a senior IC and a data-architecture leader.

  1. What actually separates a Head of Data Architecture from a senior IC
  2. Why deep expertise can trap you in the IC lane
  3. The shift from being the answer to enabling the answer
  4. Honest self-assessment against the leadership bar
  5. Naming the specific gaps you will close in this program
02 From Doing to Directing

Let go of the work and lead through others without losing credibility.

  1. Delegation when you could do it faster yourself
  2. Setting direction instead of solving every problem
  3. Trusting and growing a team's judgment
  4. Protecting your time for leadership work
  5. Redefining your value around outcomes, not output
03 Influence Without Authority

Drive alignment across an organization you do not control.

  1. How federated organizations really make decisions
  2. Building coalitions and reading the stakeholder map
  3. Persuasion, framing, and earning trust
  4. Handling resistance and competing agendas
  5. Driving a decision without formal authority
04 Executive Communication

Say less, land more, and speak the language of leaders.

  1. Communicating the big picture simply and clearly
  2. Tailoring the message to a CIO, a board, and the business
  3. Structuring a recommendation an executive can act on
  4. Data storytelling for decisions, not detail
  5. Presenting and defending a position under pressure
05 Stakeholder Management and Relationships

Build the trusted senior relationships the role depends on.

  1. Mapping and prioritizing senior stakeholders
  2. Building trusted relationships across business and technology
  3. Managing up, across, and into the executive layer
  4. Negotiating priorities and expectations
  5. Sustaining influence over time
06 Strategy, Vision and Roadmap

Convert technical depth into enterprise strategy and direction.

  1. From technical opinions to an enterprise vision
  2. Setting a target-state architecture direction
  3. Building a multi-year roadmap leaders can back
  4. Tying architecture to business outcomes and value
  5. Articulating a strategy that wins sponsorship
07 Leading Teams and Building the Function

Build and lead the team, and the capability, around you.

  1. Leading and growing a team of architects
  2. Hiring, developing, and raising the bar
  3. Building the architecture practice and its standards
  4. Managing performance and difficult conversations
  5. Creating a culture of business engagement and delivery
08 Capstone: Your Path to Head of Data ArchitectureCapstone

Assemble a concrete leadership portfolio and a plan to land the role.

  1. Define your target role and the gap to close
  2. Build your leadership narrative and evidence
  3. Draft an enterprise architecture vision you can present
  4. Create a stakeholder and influence plan
  5. Capstone: present a personal leadership portfolio and 12-month plan to reach Head of Data Architecture
Who it's for

Built for 20+ year individual contributors scaling to Head of Data Architecture

20+ year data ICs

Deeply experienced practitioners ready to lead but stuck in an IC role.

Principal and staff engineers

Senior technical individual contributors moving toward architecture leadership.

Lead architects without the title

Those already doing the work who need the leadership capabilities and positioning.

Technical experts changing gear

Experts who must convert depth into influence, strategy, and leadership.

Program formats

How you learn

Self-paced

Work through it at your own pace, with lifetime access to every module and the capstone.

Mentor-led cohort

A guided cohort with live sessions, reviews, and a peer group working the same path.

Private corporate

A closed cohort for your team, tailored to your platforms, domains, and priorities.

Portfolio-building

Every module produces an artifact; the capstone assembles them into a portfolio deliverable.

For teams

Bring it to your team

Run IC to Head of Data Architecture as a private, closed cohort tailored to your platforms, domains, and priorities, as part of building the architecture capability your organization needs.

FAQ

IC to Head of Data Architecture - answered

Who is this bridge program for?

Deeply experienced individual contributors, typically twenty years or more in data, who are ready to lead but stuck in an IC role, and who want to reach Head or Director of Data Architecture or an adjacent data-leadership role.

How is it different from the technical programs?

The other programs in the path build architecture, product, and platform capability. This one builds the leadership capabilities that actually get you promoted: influence, executive communication, stakeholder management, strategy, and leading through others.

Do I need the other programs first?

Not necessarily. If you already have deep technical depth, this bridge focuses on the leadership gap. Many learners take it alongside or after the architecture and platform programs in the path.

Is it only for financial services?

No. The leadership capabilities apply across industries, though examples draw on enterprise data environments including financial services.

What is the capstone?

A personal leadership portfolio and a twelve-month plan to reach Head of Data Architecture: your target role, leadership narrative, an enterprise architecture vision, and a stakeholder and influence plan.

Self-paced or cohort?

Both. Many learners find the mentor-led cohort especially valuable here for feedback on communication and influence.

Take the next step on the path

Enrol, enquire, or explore the full IC-to-Head of Data Architecture path.