Writing Effective Procedures

Last updated: 01/28/2026

Clear, concise procedures reduce errors and help users complete tasks without confusion.

Start with an action verb

Begin each step with a direct action verb. Users immediately know what action to take, which reduces hesitation and confusion.

Correct

  1. Install the latest version of Docker.
  2. Deploy the latest build:
    kubectl apply -f deployment.yaml

Incorrect

  1. The latest version of Docker needs to be installed. Select here to install.
  2. You should deploy the latest build using kubectl apply -f deployment.yaml.

Be clear and direct

Specificity removes ambiguity. Each instruction should clearly define what action to take, where to perform it, and why.

Correct

  1. Navigate to the /var/logs directory to review the server logs.

Incorrect

  1. Check the server logs.

Limit each step to one action

Each step should focus on a single task. Users are less likely to make mistakes when steps don't combine multiple actions.

Correct

  1. Select File > New Project to create a new workspace.
  2. Select File > Open.
  3. Select Options > Preferences.

Incorrect

  1. A new workspace is created by going to the File menu and selecting New Project.
  2. Select File, open it, and adjust your settings.
  3. Go to Options, select Preferences, and adjust your settings.

Include expected results within the same step

Include the expected result immediately after the action. Users confirm they're on the right track without leaving the step.

Correct

  1. Select Refresh to update the page. The latest data appears.
  2. Select Start to begin the process. A green status light indicates it's working.

Incorrect

  1. Select Refresh. You will see the latest data on the page.
  2. Select Start. The machine will start working (indicated by a green light).
Why the incorrect examples fail

Both incorrect steps use future tense ("will see," "will start") to describe system behavior. Use present tense instead.

Use simple, accessible language

Avoid jargon or overly technical terms unless necessary. When you must use a technical term, define it on first use.

Correct

  1. Use the slider to adjust the volume.
  2. Select Connect to start the connection.

Incorrect

  1. Manipulate the audio output level with the slider control interface.
  2. Initiate the process of establishing a connection by selecting the Connect button.

Avoid using "please"

Starting with "Please" makes the instruction sound passive and less direct, and often unnecessary. In technical environments, clarity and precision are valued more than politeness.

Correct

Enter the component name.

Why this is better: This version is straightforward and removes unnecessary formality. It gets to the point and respects the user's time.

Incorrect

Please enter the name of the component.

Be specific, not generic

Generic descriptions like "the name of XYZ" do not provide meaningful guidance. Descriptions should indicate what the user needs to input or select.

Correct

Enter a unique name for the microservice, for example, 'payment-service'.

Why this is better: This version provides context ("unique name") and an example, making it easier for the user to understand what is expected.

Incorrect

The name of XYZ.

Provide context where necessary

Offering context helps users understand the purpose of a step, especially when the step requires a decision. Keep added context under 150 words. For longer explanations, use a separate section.

Context empowers users with knowledge, leading to more informed actions and a deeper understanding of the process.

Correct

  1. Restart your system to apply the changes after updating the software.

    Restarting ensures all components of the software update are fully integrated and any in-memory data is refreshed.

Incorrect

  1. Update the software and then restart your system.

Incorporate helpful visuals

Use screenshots or diagrams to support complex steps or software navigation. Avoid adding images that don't directly support the instruction.

Visual aids reduce cognitive load. Too many visuals clutter the documentation and dilute their impact.

Correct

  1. In the Settings window, select the Advanced tab.

    [Image of the Settings window with the Advanced tab highlighted]

Incorrect

  1. Go to the settings and then find the right tab for more options.

No visual is provided, leaving users to guess which tab to select.