Trailhead for Teams

Six weeks to an AI-ready team, on your own workflow.

Your team lead runs it and sees the metrics. Any team you designate as sponsor, the same one or a different one, posts the project and scores the playbook. Weekly check-ins, or fully self-paced with a first-week touch and an outreach SLA. Nothing runs longer than it needs to.

How work gets reviewed
Who
A team of 6 to 15 people inside one organization, one facilitator (the team lead or L&D), one sponsor
Shape
Six modules, self-paced, finished in six weeks; weekly 60-minute check-ins, or fully self-paced with a first-week touch and an outreach SLA
Project
Your own recurring workflow, posted as a challenge brief by the sponsoring team
Who sees the metrics
Your organization: the team lead who signed up sees everything; the sponsoring team sees scores for its own briefs
Review
Scout checks every artifact against criteria your sponsor approved; only work that passes reaches the sponsor, who can send it back with feedback
Outcome
A team AI playbook scored by your sponsor on the six-dimension rubric, plus a before/after on the one operational number you chose in week 1
The six modules

One module a week, each one a page of the playbook.

Same loop as the schools track, adult voice: compare, invent the rule, defend it, unlock the lesson, apply it on the challenge brief, teach it to Scout, try it new without the coach. The Learn beat is assembled from your own team's rules, surface to deep.

Twelve short standardized tasks sit beside the modules, the same prompt for every learner, so the sponsor scores comparable work.

T1

Decompose the Work

Turn the team’s most common fuzzy request into an ordered ladder of decisions anyone can execute with AI.

Week 1 · Decomposition

T2

The Number That Ships

A 60-second check that keeps a plausible-but-wrong AI figure out of a client deliverable.

Week 2 · AI discernment

T3

Sources You Can Stand Behind

Never forward a claim or citation you have not resolved.

Week 3 · AI discernment, the routine taught directly

T4

Draft, Then Own It

Turn an AI first draft into something you would sign with your name.

Week 4 · craft, taught first

T5

Steal the Fix

Unstick a process by borrowing a proven mechanism from another industry, validated narrowly before anyone builds.

Week 5 · Research wide, validate narrow

T6

The Override & the Playbook

Overrule AI when it matters with a reason a sponsor accepts, and encode the team’s judgment as rules that run.

Week 6 · capstone, then the sponsor review

The six check-ins

Sixty minutes a week. The guest escalates.

Show the rule, work the project, who's in the room. The facilitator runs it with a copilot that sequences three learner rules for the room and offers constructive prompts, never explanations.

WEEK 1

Kickoff. The sponsor posts the challenge brief and names the one operational number. T1 opens; a first-week touch is scheduled for everyone.

Facilitator alone

WEEK 2

The 60-second number check on the team’s own one-pager. A practitioner from the sponsoring team shows one real figure that went wrong and what it cost.

A sponsor practitioner joins

WEEK 3

Resolvable versus plausible sources; the three-step check taught directly; how to phrase what you could not verify.

Facilitator

WEEK 4

The professional edit on AI drafts: two models of excellence, then the team’s own drafts made theirs.

Facilitator

WEEK 5

Borrowed mechanisms for the stuck part of the workflow, each with the assumption it carries and a one-hour test with a kill line.

Facilitator

WEEK 6

The override memo and the playbook. The sponsor reviews the playbook blind on the rubric, with the process trace and an oral defense.

The sponsor reviewer

How work gets reviewed

Scout checks it first. Your sponsor sees what is ready.

On the Teams track review is AI-first: Scout holds every artifact to the bar your sponsor set, so the sponsor spends their time on work worth their judgment. The facilitator only sees what needs a person: requests to look, work Scout was unsure about, and anything held for safety.

01

The sponsor approves the bar

Scout drafts the criteria from your challenge brief, each one linked to the sentence it came from. The sponsor edits and approves them before anyone is checked against them.

02

Scout checks every artifact

When a team member submits, Scout checks the work against those criteria and quotes their own words back. Not ready yet means one specific question per criterion, never the answer.

03

Only passed work reaches the sponsor

The sponsor sees the artifact blind with "Passed Trailhead’s check", and can accept it or send it back with a note the team member reads.

04

Revise and resubmit

Returned work reopens with the feedback pinned, and Scout coaches on exactly those points. Anyone who thinks Scout missed something can ask the facilitator to look.

For the people who sign the agreement

What leaves the building, and what never does.

Your text is never trained on

Every model call runs through a no-train gateway. Workspaces are isolated and every access is audit-logged.

Client data stays out

Every outside-AI step carries a do-not-share boundary and PII redaction. Sponsors score artifacts; they never read transcripts.

A before/after the sponsor scores

One operational number, chosen in week 1, measured before the course and 30 days after the playbook ships. Self-reported transfer inflates; the sponsor’s number does not.

Terms, not consent forms

Adults on a workspace agreement and a data-processing addendum. No parental consent flow, no K-12 moderation profile, the same audit trail.

Run a six-week cohort on the workflow that costs you the most.

Tell us the team, the workflow and who sponsors. We set up the workspace, the brief, the sponsor's criteria and the first check-in with you.