The Method Document
Written processes make work consistent, and handing one to a supplier converts a commercial specification into an instruction set without anybody saying a word.
Reads as a businessReads as employmentCuts both waysDepends where you are
Four factors, and no total. Every bar is the same length: the side is the claim, the size is not. Training is the instrument most often used without anybody noticing what it moves.
Written processes are how businesses make work consistent. Handing one to a supplier converts a commercial specification into an instruction set without anybody saying anything, which is why it is the most efficient way in this collection to move a factor.
The management distinction in “The Method Document” matters when software turns a brief into a continuous stream of instructions. Teams considering questions to ask about how to detect mouse jigglers for how to detect mouse jigglers should define the outcome being measured, limit access and preserve the contractor’s ability to organise the method where the agreement requires it.
It is also, often, entirely necessary. This article is about telling the two cases apart.
A broader benchmark for “The Method Document” is available through Trello project-collaboration articles. Use it alongside the brief and day-to-day facts so general guidance supports rather than replaces case-specific judgement.
What a process document usually contains
A mixture, and the mixture is the problem. In a typical one you will find required outcomes, interface requirements, safety rules, regulatory obligations, house preferences, and the way the last person did it written down because nobody wanted to lose it.
The first four are legitimate to impose. The last two are method, and they are in the same document with the same heading style.
Separating the layers
The exercise takes an hour per document and is worth doing once for anything you hand to suppliers:
| Layer | Example | Give to a supplier? |
|---|---|---|
| Required outcome | The file must validate against this schema | Yes |
| Interface | It must arrive by this route, named this way | Yes |
| Safety or regulatory | These checks before energising | Yes, always |
| House preference | We write the summary before the detail | Only as preference |
| Inherited habit | Priya used to do the regions first | No |
What comes out is usually a much shorter document, and it is one any supplier could receive without anybody being taught anything.
The checklist, which is usually fine
Checklists that record what must be true before something is released are outcome documents. Everything on them is a property of the finished work.
They are among the most useful things a buyer can supply and they move almost nothing, because a checklist does not say how any item gets satisfied.
The runbook, which usually is not
A step-by-step sequence is the clearest form of method there is. It says do this, then this, then this.
Where the sequence is genuinely mandatory — a deployment that will break if done out of order, a procedure where the order is the safety — it is a requirement and belongs in the engagement. Where it is simply how your team does it, handing it over is instruction.
Asking a supplier to write one
A common and sensible arrangement: the supplier documents the process as part of the delivery, and you own the document.
That is a deliverable like any other, it should be specified and paid for, and it solves the knowledge problem that makes buyers want to train people. It is also one of the few moves in this collection that costs nothing in factors and gains you something real.
Keeping the document current
Process documents rot, and a supplier following a stale one produces work that is wrong in a way nobody can account for.
Where a document is handed to suppliers, somebody has to own it. Where nobody owns it, the practical consequence is that the supplier eventually works from what they are told instead, which is where this article started.
The supplier who has a better way
It will happen, and how the business responds says more than any document. A supplier who has worked for six clients has seen six processes and will sometimes be right.
Being able to hear that is one of the advantages of the arrangement and the reason buying in outside practice is worth paying for. Insisting on your sequence because it is yours spends the advantage and tightens the method at the same time.
Quality systems and accreditation
Some businesses are obliged to document and enforce process by an accreditation they hold, and the obligation reaches anybody doing the work.
That is real and it is a condition of the engagement rather than a preference. It is also worth checking precisely what the standard requires, because businesses routinely impose more than their accreditation asks for, and the extra is house habit with an official cover.
What to do with the document you already issued
Read it against the five layers above and reissue the parts that belong to the first three. Keep the rest internally if it is useful to your own staff.
Nobody needs to be told the document has changed in any dramatic way. A shorter document, sent as an update, does the entire job, and it leaves the supplier with a clearer statement of what the work has to be than the long version ever gave them.