Keeping Procedures Short and Scannable
Keeping Procedures Short and Scannable records a distinct source-supported writing task while keeping adjacent procedure choices and implementation mechanics outside the page.
Keep procedures concise, omit unnecessary detail, and avoid overwhelming readers with too many steps; when practical, keep the sequence visible within a compact reading area.
Key details
Important caveats
Scope Boundary
Conciseness must not remove necessary context, safety information, prerequisites, or actions required to complete the task correctly.
Further guidance
Content
Keep procedures concise, omit unnecessary detail, and avoid overwhelming readers with too many steps; when practical, keep the sequence visible within a compact reading area.
Practical Application
Remove background detail that is not needed to complete the task, keep steps action-focused, and split long or branching workflows when that improves scanning. Preserve necessary warnings, prerequisites, decision points, and completion checks even when shortening the procedure.
Purpose
Shorter, focused procedures are easier to scan and execute while the reader is working through the task.
Reader Check
Can a reader scan the sequence and identify each required action without losing a prerequisite, warning, branch, or completion condition?
Worked Example
Instead of embedding setup history inside step 3, move the prerequisite before the numbered procedure and keep step 3 as the direct action the user must perform.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Writing step-by-step instructions — Microsoft Style Guide (opens in a new tab)Microsoft · Current Microsoft Style Guide evidence for structuring single- and multi-step procedures, procedure headings, step grouping, completion actions, and concise step writing.