Latest / Safe As Podcast / E41: Writing better procedures with the dark arts of human factors (quickisode)

Transcript

E41: Writing better procedures with the dark arts of human factors (quickisode) · Safe As Podcast

• 0:07
  Effective procedures aren't static instructions, they're
• 0:10
  really supposed to be dynamic tools that support human
• 0:12
  performance in real world conditions.
• 0:16
  Hey everyone, welcome to the next quickest site of safe as.
• 0:19
  Let's dive into the human performance Oil and Gas or
• 0:22
  Hedgepog Best practise and procedure writing guide in 2021.
• 0:28
  This HPOG guide emphasises that procedures must reflect work is
• 0:31
  done rather than work is imagined.
• 0:35
  This means capturing how tasks are actually performed,
• 0:37
  including informal practises rather than idolised versions.
• 0:42
  This is a 47 page guide on crafting page procedures so I
• 0:46
  can only cover so much in a few minutes, but check out the full
• 0:49
  report first. They have some assumptions.
• 0:52
  We have to clear up 1 procedure following is a skilled cognitive
• 0:56
  activity, not a mechanical checklist.
• 0:59
  Workers must interpret, adapt, and respond to dynamic
• 1:02
  conditions. 2 Linear execution is rarely feasible.
• 1:08
  Tasks often require jumping between steps, pausing or
• 1:11
  revisiting prior actions due to real time things like life is
• 1:15
  dynamic 3. Predictability is a flawed
• 1:18
  assumption. Variation is inevitable, and
• 1:21
  procedures must accommodate unexpected delays, missing
• 1:24
  tools, or changing priorities. As far as reasonable 4 control
• 1:29
  is limited. Workers operate under
• 1:31
  constraints, pressures, and interdependencies that demand
• 1:34
  flexibility and procedural adaptability.
• 1:37
  Now into the meat of writing and formatting procedures,
• 1:41
  structure, and language. Begin each step with a clear
• 1:44
  action verb in the present tense.
• 1:46
  Avoid passive constructions and vague modifiers.
• 1:50
  For example, open valve V12 for 10 seconds is preferred over
• 1:55
  Valve should be opened for a short time.
• 1:58
  Use one action per step and break complex steps into
• 2:02
  substeps. Use positive commands and
• 2:04
  address the primary worker directly.
• 2:07
  The vague modifier I just referred to is things like vague
• 2:10
  adjectives into adverbs like drain the tank slowly.
• 2:14
  That's vague, whereas Drain the tank at 10 litres per minute
• 2:18
  isn't. Vocabulary.
• 2:20
  Use simple, familiar terms. Avoid jargon, contractions and
• 2:24
  ambiguous phrases like quickly or appropriate location.
• 2:29
  Consistency is key. Use the same term throughout,
• 2:32
  like always. Use blind rather than
• 2:34
  alternating with stop or plate formatting.
• 2:38
  Number steps systematically 11.11.2 and use indentation to
• 2:44
  distinguish levels. Use bullets for unordered lists
• 2:48
  and numbered lists for sequences.
• 2:50
  Avoid excessive punctuation and stylized fonts.
• 2:54
  Use bond or italic sparingly to highlight key information.
• 2:58
  Apply parallel structure and headings and lists to improve
• 3:01
  readability. Visuals, diagrams, and figures
• 3:06
  should be directly relevant, legible, and match the actual
• 3:10
  equipment. It seems so funny to read this
• 3:12
  out loud, but these are match reality.
• 3:15
  Use contrasting colours in clear annotations.
• 3:18
  Avoid clutter and ensure clarity in black and white printing.
• 3:22
  Arrows should be thin and directional and annotations
• 3:25
  should be consistently oriented. Safety and warnings Place hazard
• 3:30
  warnings before the relevant steps using standardised symbols
• 3:34
  like danger warning. Caution.
• 3:37
  Avoid embedding action steps within safety messages.
• 3:41
  Include environmental warnings and historical incident
• 3:44
  references to reinforced learning and use colour coded
• 3:47
  boxes and icons consistently. Tables and figures caption
• 3:52
  tables above the content. Use left aligned text and
• 3:56
  maintain font consistency. So they say 11 to 12.4 body and
• 4:01
  9.4 tables. Ensure figures are indexed,
• 4:04
  labelled, and updated if equipment changes so it needs to
• 4:08
  be captured within your MOC process.
• 4:11
  Avoid using figures that don't directly support the procedure.
• 4:15
  Next, numerical clarity. Use digits for numbers above 10
• 4:19
  and spell out numbers at begin sentences.
• 4:22
  Avoid symbols with multiple meanings.
• 4:25
  Provide ranges rather than tolerances, So 4.9 to 5.2
• 4:31
  instead of five, plus or minus whatever.
• 4:35
  Adaptability is another element to look at.
• 4:37
  Procedures should allow for deviations when necessary.
• 4:41
  Recognise that linear, predictable and controllable
• 4:43
  assumptions often fail in practise.
• 4:47
  Design procedures to guide users through unexpected conditions
• 4:50
  safely. Fail safely.
• 4:52
  If something is just too critical to allow any sort of
• 4:55
  deviation or departure, then make it really clear and review
• 5:00
  and validation. Use walkthrough, talkthrough and
• 5:03
  task analysis to develop procedures.
• 5:06
  Engage frontline workers and subject matter experts and
• 5:09
  leadership in the reviews. Validate rocedures in the field
• 5:13
  and revise based on feedback. Include lacekeeing tools like
• 5:17
  checkboxes or initials for tracking rogress.
• 5:20
  That's it on this quick a set as safe as.
• 5:22
  Thanks everyone.