Team, operating model, and 180-day leadership practicum
Scale only when staffing and recovery evidence support the plan.
In this lesson · L7 of 7
All lessons in this track →Progress for this track is saved in this browser only. No completion badge is issued. View your learning.
Start with the idea
Scale only when staffing and recovery evidence support the plan.
Name critical jobs and who covers them. Compare required capacity with available people and time. A new title or meeting does not create tested backup coverage.
Operating coverage: People and procedures able to perform the required work when it is needed.
See the example and check your understanding
A made-up teaching example
NORTHSTAR has one engineer and a part-time reviewer. The proposed rollout needs continuous support and eight daily review hours. The plan lacks capacity, so it remains a narrower training exercise.
Ask yourself
Can the team assume missing support will appear after launch?
Show the explanation
No. Train a backup and measure review and recovery work before expanding.
Start with these checks
- Assign owners and backups.
- Measure review burden.
- Tie expansion to demonstrated capacity and recovery.
Use the different practice case below and check every requirement in its full instructions.
The video explains the main idea. Use the sources, instructions and checks below to complete the practice.
Captions appear here during playback.
Team, operating model, and 180-day leadership practicum
Scale only when staffing and recovery evidence support the plan.
Video playback is unavailable. Read the descriptive transcript below, go directly to practice, or open the video file.
Source-based teaching example · Fictional data · Reviewed 2026-10-03. Microsoft Mark · locally synthesized. On a small screen, use fullscreen for diagram details or read the transcript.
Read the descriptive transcript
0:00 · What you will learn
Scale only when staffing and recovery evidence support the plan.
What appears on screen
Scale only when staffing and recovery evidence support the plan.
0:06 · The idea
Name critical jobs and who covers them. Compare required capacity with available people and time. A new title or meeting does not create tested backup coverage.
What appears on screen
Name critical jobs and who covers them. Compare required capacity with available people and time. A new title or meeting does not create tested backup coverage.
0:20 · One useful term
Operating coverage. People and procedures able to perform the required work when it is needed.
What appears on screen
People and procedures able to perform the required work when it is needed.
0:29 · A worked example
NORTHSTAR has one engineer and a part-time reviewer. The proposed rollout needs continuous support and eight daily review hours. The plan lacks capacity, so it remains a narrower training exercise.
What appears on screen
NORTHSTAR has one engineer and a part-time reviewer. The proposed rollout needs continuous support and eight daily review hours. The plan lacks capacity, so it remains a narrower training exercise.
0:45 · Your turn to think
Can the team assume missing support will appear after launch? Pause and decide before continuing.
What appears on screen
Can the team assume missing support will appear after launch? Pause the video if you need more time.
1:02 · Why this answer works
No. Train a backup and measure review and recovery work before expanding.
What appears on screen
No. Train a backup and measure review and recovery work before expanding.
1:10 · Check 1
Assign owners and backups.
What appears on screen
Assign owners and backups.
1:15 · Check 2
Measure review burden.
What appears on screen
Measure review burden.
1:19 · Check 3
Tie expansion to demonstrated capacity and recovery.
What appears on screen
Tie expansion to demonstrated capacity and recovery.
1:26 · Now try a different case
Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete.
What appears on screen
Open the lesson Try the new case Check and revise The full task and its requirements are in the linked lesson.
Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →
Prerequisites: distinguish output from evidence; review the AI workflow reference. Public self-study is not official agency training, accreditation or a credential.
What you will be able to do
This lesson develops the ability to establish an operating model and defend a 180-day plan. The setting is NORTHSTAR Mission Portfolio, a fictional public-service portfolio containing ten proposed AI and non-AI interventions, three synthetic vendors, constrained staff capacity, and a staged incident. Every person, organization, system record, metric, and outcome in the case is fictional. Do not replace the case with operational, classified, CUI, export-controlled, proprietary, employer-confidential, or third-party personal information.
By the end of the lesson, you will be able to:
- Demonstrate how to establish an operating model and defend a 180-day plan.
- Apply that model to the synthetic NORTHSTAR Mission Portfolio environment.
- Produce a reviewable artifact that separates evidence, assumption, uncertainty, and authority.
- Recognize the critical failure and select a safe remediation path.
The performance standard is not confident language. It is a traceable decision, an artifact another qualified reviewer can inspect, a clear boundary around the learner’s authority, and a safe response to uncertainty. Knowledge checks are formative and do not award a certification or endorsement.
Module capstone. This lesson pulls together every skill in the module. Budget real time for it.
This curriculum runs self-study on VetsLearn. Where the text calls for an instructor, peer or formal review, use the stated acceptance criteria for self-review. Reflection questions support reflection; they do not replace independent assessment. A peer review is optional unless your actual organization requires it.
Part 1 Operating coverage and evidence gates
Cover mission/product, engineering, data, evaluation, operations and security/privacy/accessibility/acquisition/legal interfaces. Roles can combine; gaps, conflicts and backups remain visible. Independent challenge needs evidence and stop authority. Sequence baseline and ownership, bounded tests, acceptance/recovery review and conditional scale. Include non-AI and exit options. Dates are checkpoints, not promised deployment. Decision forums need inputs, owners, records, escalation and reconsideration triggers.
Write a gated 180-day plan
| Checkpoint | Evidence produced | Gate and fallback |
|---|---|---|
| Day 30 | Task baseline, boundary, owners | Unknown data owner → synthetic-only work |
| Day 60 | Two bounded pilots, failure outputs | Critical failure → pause affected function |
| Day 90 | Reviewer capacity and restore results | Missing coverage → retain manual process |
| Day 180 | Conditional scale/exit brief | Unresolved authority → no operational expansion |
Fictional capacity case: 120 notices weekly need five minutes review each: ten review hours. The assigned reviewer has six available hours, leaving four hours uncovered. Before scale, narrow the pilot to at most 72 notices at that assumption, add qualified capacity or redesign and retest review burden. Do not solve the arithmetic by declaring the reviewer faster without observation.
Decision forum: weekly test review consumes versioned results and failure examples; the mission owner decides scope within authority; security/privacy issues follow their designated routes; a named scribe records conditions and reconsideration triggers. If the provider changes models, reopen behavior tests. If the backup engineer leaves, reopen recovery coverage.
Feedback: the plan should show a decision it is willing to stop. A calendar that always advances regardless of evidence is not a gate.
Part 2 Synthetic worked example
NORTHSTAR has one engineer and a part-time reviewer. Day-60 rollout needs continuous on-call and eight review hours daily. The plan lacks capacity. Narrow to an offline exercise, train a backup, measure review burden and hold scale until coverage and recovery are demonstrated. A new executive title does not fix that gap.
Guided practice: identify the unsupported conclusion, name missing evidence and rewrite its scope. Change one assumption and identify which decision reopens.
Part 3 Feedback and repair
Pass when checkpoints produce evidence, both injects reopen relevant gates and staff gaps are not assumed away. Meetings help only when evidence and legitimate owners exist.
Retain the failed version, explain the criterion, correct the artifact and test a different invented case.
Next step: carry the artifact and failed cases into the next module lesson or capstone. Retain limitations when explaining your work.