Adopter Learning Path - Paired Engineering

Purpose

This note gives adopters a practical path through the project materials based on who they are and what they need.

The goal is to reduce overwhelm and stop people from reading artifacts in a random order.

How to use this path

• start with your primary role
• read the minimum path first
• only move to the deeper path if you need more detail
• do not treat every artifact as mandatory

Path 1. Executive or sponsor

Minimum path

1. One-Pager - Paired Engineering at a Glance
2. Executive Deck - Paired Engineering for an Initial Pilot Cohort
3. Leadership Note - Capability Building Versus AI Cost-Cutting
4. Leadership Note - Why Usage Metrics Are Not Adoption Metrics

Deeper path

5. Leadership Deck Slide Copy - Paired Engineering for an Initial Pilot Cohort
6. Pilot Evidence Model - Practical Metrics and Lightweight Collection
7. V1 Rollout Playbook - Initial Pilot Cohort

Outcome

You should understand:

• what the program is
• why it exists
• what leadership must protect
• what not to measure simplistically

Path 2. Manager or people leader

Minimum path

1. Manager Deck Slide Copy - Leading Paired Engineering in Delivery Teams
2. Manager Coaching Guide - Paired Engineering in Delivery Teams
3. Manager and Technical-Lead Responsibilities for AI Enablement
4. Software-Specific Apprenticeship and Onboarding for AI-Enabled Teams

Deeper path

5. AI-Assisted Requirements Management
6. Apprenticeship-Aware AI Enablement
7. Pilot Evidence Model - Practical Metrics and Lightweight Collection
8. Leadership Note - Why Usage Metrics Are Not Adoption Metrics

Outcome

You should understand:

• what managers own
• how to protect learning and review quality
• what signals matter more than raw activity

Path 3. Staff Engineer or technical enablement lead

Minimum path

1. Staff Engineer Deck Slide Copy - Paired Engineering Through Influence
2. Verification Standards by Artifact and Work Type
3. AI Tool Selection Framework
4. AI Enablement Across the Software Delivery Lifecycle

Deeper path

5. Capability Model - Oversight Readiness x Task Familiarity x Risk
6. Apprenticeship-Aware AI Enablement
7. V1 Rollout Playbook - Initial Pilot Cohort

Outcome

You should understand:

• how to lead through influence
• how to shape standards and workflow quality
• how to select tools and protect apprenticeship capacity

Path 4. Practitioner

Minimum path

1. Practitioner Playbook - Paired Engineering with AI
2. Practitioner Workshop Deck Slide Copy - Paired Engineering with AI
3. Verification Standards by Artifact and Work Type

Deeper path

4. Workshop Pack - Paired Engineering with AI
5. Exercise Library - Paired Engineering with AI
6. Exercise Worksheet Pack - Paired Engineering with AI

Outcome

You should understand:

• how to use AI as paired engineering
• how to choose mode and verification path
• how to keep learning visible while still using AI productively

Path 5. Facilitator or enablement coach

Minimum path

1. Workshop Pack - Paired Engineering with AI
2. Exercise Library - Paired Engineering with AI
3. Exercise Worksheet Pack - Paired Engineering with AI
4. Learning Design Principles for Adult Technical AI Enablement

Deeper path

5. Learning Pattern Library
6. Capability Model - Oversight Readiness x Task Familiarity x Risk
7. Verification Standards by Artifact and Work Type

Outcome

You should understand:

• how to run the workshops
• how to choose exercises by audience
• how to keep learning patterns evidence-aware

Path 6. Public reader or outside adopter

Minimum path

1. One-Pager - Paired Engineering at a Glance
2. Public Overview Deck Slide Copy - Paired Engineering
3. Getting Started with Paired Engineering

Deeper path

4. Project Charter
5. Executive Deck - Paired Engineering for an Initial Pilot Cohort
6. Practitioner Playbook - Paired Engineering with AI

Outcome

You should understand:

• what the project is
• how it differs from generic AI productivity messaging
• where to go next without reading the whole vault

Suggested sequencing rule

If you are adopting this approach inside a real organization, the usual order is:

1. leadership alignment
2. manager and Staff understanding
3. practitioner workshop or playbook rollout
4. exercise-based reinforcement
5. measurement and refinement

Not every path is required

This project is modular.

An individual may only need the practitioner path.

A sponsor may only need the executive path.

A technical enablement lead may need several paths.