Claude Code Leadership Briefing

Most engineering leaders did not choose to adopt AI coding. Their developers chose it, and the leader now has to reason about a capability that is already in the room. The leadership question is no longer "should we adopt this" but "what do we measure, what do we fund, and what do we allow." This is not a hands-on course. It is a working session that ends with a written plan a leader can put in front of their own management and their own team.

Course objectives

  • A measurement model that separates AI-attributed output from raw throughput
  • A funding decision across Pro, Max, Team, or Enterprise
  • A governance baseline defining what is mandatory, recommended, and restricted
  • A 90-day rollout calendar with named owners, weekly checkpoints, and a defined kill switch
  • A one-page brief the leader can forward internally by Friday

Target audience

Engineering managers with 5 to 30 reports, heads of engineering, CTOs of mid-market companies, VPs of engineering inside larger organizations, and platform or developer-experience leads who own the tooling budget.

Prerequisites

No prior knowledge is required to attend this course.

Important information

Pre-Course Self-Assessment

Every participant takes a 10-minute online self-assessment before the course. It checks what they already use:

  • Slash commands
  • Memory
  • Skills
  • Hooks
  • MCP
  • Subagents
  • Agent teams

It also checks how they currently handle planning and verification, and what their review process looks like. The assessment routes them to the right track and flags obvious gaps.

Why this matters to our customers:

  • It reduces course-mismatch complaints
  • It doubles as a sales qualification tool
  • It gives the instructor room-specific data before the session starts

That lets day one open with "here is what this room already knows and where the shared gaps are" instead of generic material.

Take-Home Template Pack

Every participant leaves with a versioned template pack checked into a real repository they can open on Monday. The pack is not a slideware deliverable. It is a working set of 10 to 20 files such as:

  • Slash commands
  • CLAUDE.md
  • Hooks
  • Subagent definitions
  • Skill directories
  • MCP configuration samples
  • Permission settings

The pack is co-authored during the course. Participants do not receive it as a gift at the end. They build it, review each other's entries, and commit it. That is what makes it stick. If nobody has owned a particular file by the end of the day, it does not go in the pack.

30- Day Follow-Up

Two weeks after delivery, the instructor runs a one-hour follow-up with the cohort. The agenda is fixed:

  • What has actually been adopted
  • What broke
  • What got quietly abandoned

The follow-up is included in the course price. Without it, most of the value walks out the door inside a month.

Session 1 - What The Data Actually Says

A short, evidence-based walkthrough of the DORA findings, 2026 AI engineering telemetry, and Anthropic's own adoption data. Discussion: where does the leader's team sit on the throughput versus stability trade-off today?

Session 2 - Measurement: What To Track, What To Ignore

We walk through a minimal metric set that answers the questions that matter now:

  • How much of the team's output is AI-assisted
  • How much of it survives 30 days without rewrite
  • Whether review capacity is keeping up
  • Whether change failure rate is creeping

Exercise:

  •  The leader defines a baseline and the three numbers they will track weekly

Session 3 - Funding And Governance

Plan tier selection, realistic usage patterns by team size, SSO and audit requirements, and when centralized configuration becomes worth the overhead.

Exercise:

  • The leader drafts a three-column governance sheet: mandatory, recommended, restricted

Session 4 - The 90-Day Rollout Plan

A working session, not a lecture. Each leader drafts a 90-day plan with three phases:

  • Pilot
  • Expansion
  • Standard practice

The plan includes named owners, success criteria, and a kill switch. It is reviewed by the room before anyone leaves.

Practical information

Duration: 1 day
Price: 10 900 NOK
Language: English
Format: Instructor-led classroom training with hands-on exercises

FAQ

Hva er Claude Code Leadership Briefing?
Dette kurset gir ledere en overordnet forståelse av hvordan Claude Code og AI-assistert utvikling påvirker organisasjon, arbeidsprosesser og strategi.

Hvem passer kurset for?
Kurset passer for ledere, beslutningstakere, CTO-er og andre som ønsker innsikt i hvordan AI kan brukes i utviklingsarbeid uten å måtte gå i dybden teknisk.

Trenger jeg teknisk bakgrunn for å delta?
Nei, kurset er tilrettelagt for både tekniske og ikke-tekniske ledere og fokuserer mer på forståelse og anvendelse enn implementering.

Er kurset praktisk rettet?
Kurset er mer strategisk enn teknisk, men inkluderer eksempler og demonstrasjoner som viser hvordan verktøy som Claude Code brukes i praksis.

Hva får jeg ut av kurset?
Du får innsikt i hvordan AI-verktøy påvirker utviklingsteam, hvordan du kan ta bedre beslutninger rundt bruk av AI, og hvordan du kan legge til rette for effektiv og ansvarlig bruk i organisasjonen.

Andre relevante kurs

22. juni
5 dager
Classroom Virtual
23. september
3 dager
Classroom Virtual
10. juni
3 dager
Classroom Virtual
2. juni
4 dager
Classroom Virtual