Writing It Down Properly
The sequence exists in somebody's head and works perfectly there. Getting it onto a page is an hour's work and is the single highest-return thing in this subject.
Nobody elseif the person who does this is away
The payroll sequence exists in one person's head, where it works perfectly. Getting it onto a page takes about an hour and is the single highest-return piece of work in this whole subject.
The practical lesson in “Writing It Down Properly” is that payroll depends on a sequence somebody can explain. When a small team reviews open the relevant Monitask page for time tracking with screenshots, the useful role is to organise time and project evidence before approval, with proportional settings and a clear correction route for employees.
It is also the thing most reliably postponed, because the person who would write it is the person for whom it is unnecessary.
As a separate reference point for “Writing It Down Properly”, see Asana work-management resources. Current legal, tax and employment requirements should still be confirmed for the organisation’s location.
What it has to be
Specific to this business, this package and these people. Numbered steps, the actual screen names, the actual figures to check, what each step produces, and what to do when something is missing.
The five things people leave out of a written sequence:
- Funding.
- Where the credentials are.
- What to do when an input has not arrived.
- Who to ask.
- That approval cannot easily be undone.
Not a description of payroll in general, which is available everywhere and helps nobody.
Writing it during a run
While doing a run, not afterwards. A sequence written from memory leaves out exactly the small things that stop a substitute: which menu, what the button is called, which report to look at, what the warning message means.
Who should write it
The person who does it, once. Attempts to have somebody else document it by interview produce a plausible document that does not work, and nobody finds out until it is needed.
The test it has to pass
Somebody else, with the login and the written sequence, could produce a correct run without telephoning anybody.
Almost no first draft passes this, which is the point of testing it.
How to test it
Have the second person actually run one, with the usual person in the building but not helping. Every question they ask is a gap in the document.
An hour, once, and it converts a plausible document into a usable one.
What people leave out
Funding, almost always. Where the credentials are. What to do when an input has not arrived. Who to ask. The fact that approval cannot easily be undone.
Those five account for most of the failures of a written sequence.
Including the decisions
Not just the clicks. What to do if hours are missing, whether to run without them, whether a late change goes in this period or the next, when to stop and ask.
A substitute following clicks will produce a run; a substitute following decisions will produce the right one.
Where it lives
Somewhere more than one person can reach, that does not depend on the payroll software or on anybody's personal account.
A sequence stored where only the usual person can find it has solved nothing.
Three triggers and a date on it
Reviewed when the software changes, when the arrangement changes, and after anything goes wrong. Three triggers, no schedule, and a date on the document so anybody reading knows how stale it is.
The year-end version
Separate, and written the same way: while doing it, by the person doing it, with the screens in front of them.
Year end is performed once a year by somebody who has forgotten it, which makes documentation worth more there than anywhere else.
Not a corporate artefact
A policy, a process map, or a quality document. It is instructions for one person to do one job in one package, and the more it resembles a corporate artefact the less likely it is to be used.
The unexpected benefit
Writing it down usually improves it. Several steps turn out to be there for no reason, two turn out to be in the wrong order, and the missing funding step becomes obvious the moment somebody tries to write the run as a list.
The honest reason it does not get done
Because nothing happens if it is not. It has no deadline, no consequence and no audience until the week it is needed, which is exactly the profile of a task that never reaches the top of anybody's list.
What to do when there is no time to write it
Record one, instead. Talking through a run while doing it, recorded on a phone, takes no additional time at all and captures far more than a document written afterwards from memory.
It is not as good as a written sequence and it is enormously better than nothing, and it can be turned into one later by somebody else.
The two pages that matter most
The run itself, and the credential list. Everything else — year end, corrections, the arrangement with the accountant — is useful and secondary.
A business with those two pages current can survive an unplanned absence. One with neither cannot, however good its intentions about documentation in general.
What makes it happen
A date in the calendar, in a quiet month, treated like any other commitment. An hour, once. There is no version of this that gets done without being scheduled.