Writing
Everything here is a method you can run yourself without hiring anyone. We publish the working version, not a teaser of it.
Ten pieces. Each one is a procedure, not an opinion.
A handover is finished when the team that will run the operation has run a real job without the people who built it. What the receiving team needs, a checklist with the evidence for every item, and the live-run test that decides sign-off.
One job number, one shallow folder template and one file-name pattern, carried into SharePoint, Teams, the project board and the invoice. Folders versus columns, Microsoft's path limits, and how to fix an existing mess without breaking links.
Running, reporting and working are three different things, and almost every silent failure lives in the gap between two of them. The three shapes the failure takes — including the one where green means "I could not look" — the four assertions that catch them, and a drill that proves your checks work by breaking them on purpose.
Most process documentation is written by asking someone to describe what they do, which is the defect no template fixes — a description is what someone remembers, a record is what happened. Six steps, written from the record, plus the handover test that is the only one that means anything.
A boundary you cannot verify after the fact is an intention, not a boundary. Six fields per action — including the one almost nobody writes, which is the only one that answers "was it allowed to do that?" — why the record must be append-only, and the four things to actually review each week.
The process that annoys people most is rarely the one that pays back first. Four properties decide it — how much time it really consumes, whether the rule can be written down, what breaks if it goes wrong, and whether you would know. A scoring pass you can run on your own operation in an afternoon.
Procedure folders rot for structural reasons, not because anyone is undisciplined: a fact recorded in two places with nothing forcing the two to agree will diverge. Four causes, a five-sample test for how bad yours is, and what actually closes the loop.
Every operation has four separate accounts of itself: what people say they do, what they are observed doing, what the written procedure claims, and what the systems recorded. They disagree, and the disagreements are where the money leaks. A four-source method for finding out which account is true — including the version you can run yourself.
The question that decides whether autonomous work is an asset or a liability. A concrete model for sorting every action into three buckets — do it, draft it for approval, never touch it — and for making the boundary auditable afterwards instead of implicit.
The five-step loop: document, build, govern, audit, improve. Why the order is not negotiable, and what goes wrong at each step when someone tries to skip straight to automation.
Bring us the operational problem you're carrying, and we'll tell you what we'd do first.
Work with us