Created by the First Role Skills Editorial Desk. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
Start with the work
A realistic scenario
You need to explain a recurring task. The screen contains names, email addresses, browser tabs, and account details that must not appear in a training document.
Avoid rework
Three beginner mistakes
Capturing the full desktop when only one control matters
Blurring data lightly enough that it can still be read
Using a screenshot instead of writing the instruction
The method
Complete it in six controlled steps
- 01
Prepare a safe environment
Use fictional records and close unrelated tabs, notifications, chats, and password tools before capturing. Prevention is safer than relying on redaction later.
- 02
Write the instruction first
State the action, expected result, and decision rule in text. The screenshot should confirm location or appearance, not carry the entire explanation.
- 03
Capture the smallest useful area
Include enough interface context to orient the reader, then crop tightly. Keep cursor placement and zoom consistent across a sequence.
- 04
Annotate sparingly
Use one numbered callout or outline for the relevant control. Do not cover labels or rely on red and green alone to convey meaning.
- 05
Redact and inspect
Remove email addresses, phone numbers, tokens, filenames, and personal browser details. Zoom in after export and ask another person to inspect the image.
- 06
Name and describe the asset
Use a useful filename, concise alt text, and a caption that explains why the image matters. Record the application and review date in the SOP.
See the difference
Before and after
Full desktop screenshot showing inbox names, open tabs, profile photo, and a tiny highlighted button.
Cropped fictional interface with one numbered callout, alt text, caption, and no personal or account data.
Original practice
Complete the exercise
Create a three-step SOP using a fictional browser form or spreadsheet. Run the privacy checklist, export images, and ask a reviewer to identify any remaining sensitive details.
Use only fictional or fully anonymized data. Never upload an employer's confidential information to a portfolio.
Explain your decisions
Turn the exercise into credible evidence
Keep the original safe practice screen, the cropped annotated image, and the completed privacy checklist. In your explanation, identify what you excluded from the frame, why one callout was enough, and how the alt text supports a reader who cannot see the image. Record the second-person review result. Never use a real inbox, customer record, token, or employer interface simply to make a portfolio sample look more authentic.
Quality gate
Check your own work
- Fictional environment
- Instruction written first
- Tight crop
- Sensitive data removed
- Alt text provided