Many organisations use the terms process, procedure, work instruction, plan, and strategy interchangeably. They are not the same. This article explains the key points to help clarify these differences.

Confusion between these terms leads to poor documentation, unclear responsibilities, and inconsistent delivery.

If you work in technical authoring, information management, or governance, understanding the difference is essential.

A good documentation framework clearly separates these elements and ensures people know what they must do and why.

What is a process?

A process is a set of interrelated activities that turn inputs into outputs.

A process describes a complete business activity from beginning to end.

You must:

• • • Learn the process
    • Understand why it exists
    • Perform it end-to-end

A process is:

• • • A high-level description of work
    • Cross-functional
    • Ongoing and repeatable
    • Updated periodically
    • Supported by policies and standards

A process answers the question:

“How does the business operate?”

What is a procedure?

A procedure provides more detail than a process but less detail than a work instruction.

It explains how to perform sequential tasks to achieve a defined outcome.

A procedure usually:

• • • Follows a logical sequence
    • Has an obvious start and finish
    • Can be completed in one working session
    • Describes responsibilities

A procedure answers:

“How do we complete this activity?”

What are work instructions?

Work Instructions (WI) describe exactly how to perform a specific task.

They provide step-by-step guidance with no ambiguity.

A work instruction:

• • • Describes one task
    • Contains detailed steps
    • May include screenshots or diagrams
    • Removes interpretation

Work instructions answer:

“How do I do this task?”

What is a plan?

A plan is not a process.

Many organisations confuse the two.

A management plan describes what will be done, not how work is performed.

A plan typically includes:

• • Objectives
  • Resource allocation
  • Timescales
  • Responsibilities
  • Risk considerations
  • Contingencies

A plan shows how an organisation will move from Point A to Point B.

It supports the strategy by describing how resources will achieve the aim.

A plan answers:

“What are we going to do?”

What is a strategy?

A strategy explains how an organisation will move from Point A to Point B.

It defines direction rather than detailed actions.

A strategy typically includes:

• • • Current position (Point A)
    • Desired position (Point B)
    • Problems and constraints
    • Opportunities
    • Tools and approaches
    • Decision principles

A strategy considers obstacles and risks that may slow progress.

Strategy answers:

“Where are we going and why?”

Your strategy defines what you want to achieve.

Understanding the difference between a strategy and a plan allows organisations to make better decisions.

What is a standard?

Standards define mandatory rules and behaviours.

They support policies and ensure consistency across the organisation.

Standards are:

• • • Mandatory
    • Enforceable
    • Organisation-wide
    • Consistent
    • Long-term

Define expected behaviour, for example:

• • • Email signatures
    • Naming conventions
    • Approved hardware and software
    • Document templates
    • Security controls

Must be enforced to be effective.

This applies equally to policies and standards.

Why does this matter?

When organisations confuse these terms, documentation becomes chaotic:

• • • Plans get mistaken for processes
    • Procedures become incomplete
    • Work instructions disappear
    • Strategies become wishlists
    • Standards are ignored
    • Clear documentation separates these layers and ensures:
    • Consistent delivery
    • Clear responsibilities
    • Better governance
    • Easier audits
    • Stronger information management

This structure is the foundation of a well-run documentation system.