Watch the explanation. Practice the skill.
Build evidence of your capability
Describe your contribution, AI assistance and limitations truthfully.
Captions appear here during playback.
Build evidence of your capability
Describe your contribution, AI assistance and limitations truthfully.
Video playback is unavailable. Read the descriptive transcript below, go directly to practice, or open the video file.
Illustrated 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 · Show what you can demonstrate.
Career evidence is stronger when a reviewer can inspect your work and understand your contribution. A certificate or polished claim alone does not show capability. We will repair an inflated description of a fictional project without hiding the useful work that actually happened.
What appears on screen
Contribution · Artifact · Checks · Limits
0:19 · Start with the actual project record.
Riley wrote two tests using ten synthetic cases. A teammate built the interface. AI assisted with the README, which Riley reviewed. Two unsupported outputs were found. The project was not deployed to users, and savings were not measured. These facts define the scope of a truthful description.
What appears on screen
Riley: 2 tests · 10 synthetic cases Teammate: Built the interface AI assistance: README draft, reviewed by Riley Limitations: 2 unsupported outputs; no deployment
0:43 · Remove invented scope and outcomes.
The inflated description says Riley independently built and deployed a reliable system that saved forty percent. The evidence does not support sole authorship, deployment, reliability across real users, or measured savings. Correct those claims while preserving the testing and review contribution.
What appears on screen
Independently built and deployed a reliable system; saved 40%. Sole authorship: Teammate built UI Deployment: No user deployment Savings: Not measured
1:05 · Write a defensible project description.
A stronger description says Riley authored two tests over ten synthetic cases, documented two unsupported outputs, and reviewed an AI assisted README. It credits the teammate’s interface work and states that user deployment and savings are unmeasured. Specific contribution is more credible than inflated certainty.
What appears on screen
Authored two tests covering ten synthetic cases; documented two unsupported outputs and reviewed an AI-assisted README. Interface built by a teammate. No user deployment or measured savings.
1:28 · Package evidence for a reviewer.
Include a sanitized artifact, test cases and results, your contribution, AI assistance, and known limitations. Explain how the reviewer can inspect or reproduce the work. Do not publish sensitive information, unsupported business claims, or another person’s work as your own.
What appears on screen
Artifact: Sanitized, inspectable example Checks: Cases, results and failures Contribution: What you and others did Limits: Unverified outcomes and next work
1:50 · Prepare your own evidence packet.
Use the lesson’s fictional project record or an authorized sanitized project. Write a concise contribution statement, attach the relevant artifact and checks, and name one limitation. Passing means a reviewer can distinguish demonstrated skill from unmeasured outcomes and understand where AI helped.
What appears on screen
Could a reviewer verify your contribution? Inspectable artifact. Your role and AI assistance. Checks, failures and limitations. Your evidence: a truthful, reviewable project packet.
Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →