01
Shared intuition.
Use the same mental model to recognize where AI can help, where it can fail, and when verification is required.
Participants reach similar conclusions when they review the same unfamiliar scenario independently.
All courses / Engineering practice
AI-DLC
in practice.
A shared way to think.
A better way to build.
A hands-on course for engineers working with AI. Build shared intuition, a common vocabulary, and habits that carry into daily work.
- Designed for
- Engineers
- Learning format
- 7 practical lab stages
- Shared workflow
- 5 Workbench phases
Learn the process.
Make it your practice.
Make it your practice.
01 / The learning outcomes
Change how the team
thinks, speaks, and works.
Success is more than finishing the lab. It is what the cohort understands, says, and does afterward.
02
A common language.
Use agreed terms for context, specifications, boundaries, gates, validation, and findings.
Participants use the agreed terms to classify the same situations and support their decisions with evidence.
03
Everyday habits.
Keep using the Workbench process after the course, on real work and unfamiliar tasks.
Work artifacts show that participants continue to use the workflow on unfamiliar tasks without scripted prompts.
The goal is independence.
Participants can assess new situations, use the agreed terms, and follow the process without a prescribed prompt. People remain accountable for decisions.
02 / The lab journey
One increment.
Seven stages of practice.
Follow the work from context and specification to review and closure. Each stage produces evidence a facilitator can review.
Stage / PracticeWorkbench phase
01
Ground the work
DefineReviewable evidence
Explain why implementation must wait for a validated specification.
What this develops
Shared intuition and language
02
Audit compressed context
DefineReviewable evidence
Separate verified facts, supplied claims and unknowns.
What this develops
Shared intuition and behavior change
03
Author and validate the specification
DefineReviewable evidence
Write testable acceptance criteria and produce a ready specification.
What this develops
Shared language and behavior change
04
Plan across repositories
PlanReviewable evidence
Create an ordered plan that respects ownership and dependencies.
What this develops
Shared language and behavior change
05
Correct the draft with test-driven development
ExecuteReviewable evidence
Record a relevant failing test before changing production code.
What this develops
Behavior change
06
Validate with fresh context
JudgeReviewable evidence
Check the implementation against the specification and address each finding.
What this develops
Shared intuition and behavior change
07
Review, ship and close
Judge and LearnReviewable evidence
Record gate results, decisions, dispositions and lessons.
What this develops
Shared language and behavior change
The design principle
Every exercise
earns its place.
An exercise must support both a course goal and a Workbench stage. Remove it if it does not support both.
A course goal
Intuition, language,
or behavior.
A Workbench stage
Define. Plan. Execute.
Judge. Learn.
03 / Go a little deeper
The thinking
behind the practice.
Use these three views to develop and review the course, connect it to the goals, and decide what evidence to look for.
01 / Design
Learning design
What participants do and why each activity is included.
Explore the design 02 / LanguageShared vocabulary
The terms participants use during the course and at work.
Build a common language 03 / EvidenceMeasure results
The evidence that shows understanding and changes in behavior.
See what success means