Public Overview Deck Outline - Paired Engineering

Usage note

This outline and its slide-copy companion now form the accepted locked markdown baseline for the public overview deck.

Use this note as the deck map unless a substantive audience or content gap appears.

Deck goal

Introduce the core thesis of the project to an external audience in a way that is clear, credible, and safe for publication.

This deck should help an outside audience answer four questions:

• what problem AI enablement is trying to solve
• why paired engineering is a better alternative to the usual extremes
• why the work is about capability growth and verification, not just speed
• why apprenticeship and the junior path still matter in an AI-enabled world
• what this project offers to technical leaders and teams

Recommended deck shape

• Keep the deck to roughly 8-12 slides.
• Optimize for GitHub readers, meetups, talks, or general sharing.
• Use plain language and a strong narrative spine.
• Keep enterprise-specific details narrow and clearly labeled.
• Do not rely on private field observations or sensitive examples.

Presentation layers

• Outline deck: this note
• Slide-copy companion: Public Overview Deck Slide Copy - Paired Engineering

Use this note as the deck map.

Use the slide-copy companion when the public overview deck needs fuller on-slide language and presenter notes.

Narrative arc

1. AI rollout is being framed too often as either hype or fear.
2. The more useful question is how teams should work with AI well.
3. Good enablement treats AI as paired engineering with verification, learning, and apprenticeship built in.
4. The project offers a practical delivery model, not a vendor pitch.

Slide 1. Title

Headline:

Paired Engineering

Subtitle:

A practical delivery model for AI-enabled software teams

Slide goal:

Introduce the project in the clearest possible terms.

Slide 2. The problem

Headline:

Most organizations are rolling out tools faster than they are designing good working practices.

Slide goal:

State the core problem without overreaching.

Speaker points:

• access is outpacing enablement
• productivity language often dominates the conversation
• learning, verification, and workflow quality get underdesigned

Slide 3. The false choice

Headline:

This is not ban AI versus let the model do the work.

Slide goal:

Set up the better-alternative positioning.

Speaker points:

• rejecting AI entirely is too blunt
• blind delegation is too shallow
• paired engineering is the more durable path

Slide 4. What paired engineering means

Headline:

Use AI to think with, compare with, and learn with, not just to draft faster.

Slide goal:

Explain the core delivery stance in simple language.

Speaker points:

• ask questions
• generate or compare options
• verify
• revise
• learn

Slide 5. Why this matters beyond productivity

Headline:

Speed is not the only outcome that matters.

Slide goal:

Bring in the broader quality and capability argument.

Speaker points:

• verification matters
• review burden matters
• capability growth matters
• apprenticeship and onboarding still matter

Slide 6. The bottom rung still matters

Headline:

Shallow rollout harms both ends of the ladder.

Slide goal:

Make the junior-pipeline and apprenticeship concern explicit without overstating the evidence.

Speaker points:

• early-career and learning-rich work is vulnerable when AI is framed only as replacement
• the same rollout can also force more ambiguous, cleanup-heavy, and review-heavy work upward onto a smaller senior layer
• removing the bottom rung does not remove the need for future independent engineers
• forcing too much work upward does not remove the need for sustainable team design
• this is an enablement-design problem, not just a hiring-market complaint

Slide 7. What this project includes

Headline:

AI enablement needs more than a tool list.

Slide goal:

Summarize the project’s actual content.

Speaker points:

• rollout lifecycle
• oversight-readiness model
• verification standards
• learning design
• measurement model
• tool taxonomy and selection guidance

Slide 8. What this is not

Headline:

This project is deliberately not a few common things.

Slide goal:

Set expectations and avoid category confusion.

Speaker points:

• not a vendor catalog
• not a prompt-count adoption program
• not an anti-AI argument
• not a justification for cutting apprenticeship before replacing it

Slide 9. Who this is for

Headline:

The model is built for software delivery work, but it scales across contexts.

Slide goal:

Show audience fit without artificially narrowing the work.

Speaker points:

• individual practitioners
• Staff Engineers and technical enablement leaders
• delivery organizations
• teams exploring a pilot

Slide 10. A practical first step

Headline:

Start small enough to learn honestly.

Slide goal:

Give the audience a practical entry point.

Speaker points:

• choose one real workflow
• define how it will be verified
• decide how success will be judged honestly

Slide 11. Where to go next

Headline:

Use the package in the way that matches your need.

Slide goal:

Point people toward the broader project materials.

Supporting notes:

• One-Pager - Paired Engineering at a Glance
• Getting Started with Paired Engineering
• Executive Deck - Paired Engineering for an Initial Pilot Cohort
• Workshop Pack - Paired Engineering with AI
• Exercise Library - Paired Engineering with AI
• Pilot Evidence Kit - Initial Pilot Cohort
• Apprenticeship-Aware AI Enablement