SiSu RevOps

M3  /  L3.2  /  about 13 minutes

Blast radius sets the process

You have a shortlist. Someone now has to say yes to it.

That conversation goes badly when your answer to "what happens if it gets it wrong" is a feeling, and well when the answer is a table you filled in before you were asked.

That is blast radius. Not a warning label: it decides who reads the output, who approves the run, and what you do at 16:40 on a Friday when something has already gone out.

What you will be able to do

  • Assign a blast-radius class and derive its review gate, approver and reversal plan.
  • Say when a workflow is promoted to writes-to-system, and why it never starts there.
  • Derive your own never-delegate list from five rules, not from somebody else's list.

The three classes and what each one obliges

This table is ours, teaching design. What it responds to is the product's directory and permission boundary.

Class Review gate Approval Reversal plan
Read-only Spot check on a sample None needed Delete the output
Draft-only Full human read before it leaves the folder The sender Do not send
Writes-to-system Sample verify, then staged apply Named approver, per run Written, tested, and in the run record before the first write

Three things people get wrong here, in order of cost.

The class is set by where the output goes, not how the work felt. A list of at-risk accounts is read-only until someone pastes it into a customer's business review deck; then it was draft-only all along and nobody reviewed it. Follow the output to its final destination, not the folder it lands in.

"Reversal plan" means tested, not imagined. "We would just re-import the old values" is a sentence. A plan names the file with the previous values, names who runs the re-import, and has been run once on a small batch. It goes in the run record before the first write, because after is when you need it and cannot think straight.

Approval for writes-to-system is per run, not per workflow. A workflow approved in March is not approved for a September batch full of objects March never saw.

The promotion rule, the most useful line in this lesson:

A workflow starts draft-only and is promoted to writes-to-system only after it has run clean several times, with verification, and has a tested reversal path.

Nothing arrives as writes-to-system: not because the model is untrustworthy, but because you do not yet know what your own brief does at the edges, and the edges are where systems of record get damaged.

Check yourself: take one shortlist entry and derive its review gate, approver and reversal plan, without asking anyone.

Five rules that generate your never list

Do not memorise a list of forbidden tasks: lists go stale and do not transfer. Derive your own from five rules, so a new request classifies itself in ten seconds.

Rule 1. Anything that reaches a customer without a human reading it. Not "anything customer-facing", which would exclude useful drafting work. The condition is the missing human. Drafting the renewal email is fine, sending it is not.

Rule 2. Anything that changes a system of record where the change cannot be reversed. Reversibility, not writing, makes the difference. A field update you can re-import is a different risk from a merge you cannot unmerge. answer-keys/PLANTED-ISSUES.md in your pack, which you open only after attempting the lab, documents eight duplicate-accounts rows that genuinely should merge, for example ACC-02890 and ACC-02988, the same company under a punctuation variant. Proposing those merges is delegable. Executing them without a reversal path is not.

Rule 3. Anything where the source of truth is a person's judgment rather than a record. A forecast call. A performance conversation. A pricing exception. This is the Checkability veto from Lesson 1, stated as a rule you can quote.

Rule 4. Anything you must be able to evidence to a regulator or an auditor, because the Compliance API and Audit Logs do not cover Cowork yet. People mis-state this one: the exclusion is not "Cowork does this badly", it is that you cannot prove what it did at the level an auditor requires. It is also the rule most likely to change, since it rests on a vendor gap, not a property of the work.

Rule 5. Anything you could not defend line by line if a VP asked where a number came from. If you cannot walk the number back to a file and a rule, do not put your name on it.

Try this now Three minutes: derive three never-list entries, each with the rule that generates it. The rule matters more than the task: in six weeks it decides a request you have not seen yet.

Check yourself: for each of your exclusions, can you state the rule, not just the task?

Watch a task get classified

The task. "Check every opportunity's currency label against its account's billing currency, and tell me which ones disagree."

Why it looks refusable. 528 opportunity rows against 308 account rows. Tedious. Never done. It sounds like an audit.

What it actually is. DATA-DICTIONARY.md in your pack's data folder says opportunities.currency should always match the account, and on a few rows it does not. PLANTED-ISSUES.md documents exactly four, class SUBTLE currency-mismatch: OPP-006697 (account ACC-03045), OPP-006729 (ACC-02958), OPP-007089 (ACC-03089) and OPP-007326 (ACC-03021). Each says USD while the parent account bills in EUR and the amount magnitude matches the EUR list price.

Decision 1: the class. Read-only. It produces a list, writes nothing, sends nothing. Spot check on a sample, no approver, reversal plan is deleting the output.

Decision 2: the checkability. Every finding is a two-column comparison verified in fifteen seconds: open the account row, read the currency, compare. Wrongness is visible on inspection, which a plausible-looking summary cannot give you.

Decision 3: what I refused to add. "And fix them" is writes-to-system on a money field, and it is not obvious in every case which value is wrong. So: a proposed-changes file plus an exceptions file, a human decides, and the workflow is promoted later or never.

Worth knowing: this work is unpleasant and completely verifiable. Those two properties are independent, and confusing them is the most common triage error there is.

Tell these apart

A task that is hard, and a task that is unverifiable. Both trigger "I would not want to be responsible for that." The decision is opposite: hard work is the best thing you can hand over, and unverifiable work is the thing you must not.

Hard, and a good candidate: the currency reconciliation above. High volume, tedious, easy for a tired human to get wrong, done by nobody. And fully verifiable: two columns, one rule, each finding checkable in seconds against a named file. Difficulty argues for handing it over: the agent does not get bored on row 400, and you can check its work faster than you could have done it.

Unverifiable, and not a candidate:

"Read the call notes and tell me which of these deals is actually going to close this quarter."

Not hard at all: sixteen notes, half an hour for a competent reader. Unverifiable: the source of truth does not exist yet. It arrives when the quarter closes, after the moment you need to act. And the output would be excellent, confident, specific, well argued, with no way to tell the good version from the bad one until too late to matter.

The test in one question: if this came back wrong, what would I compare it against, and would I have it before I need to act? The currency task: accounts.csv in your pack's data folder, available now. The notes task: nothing, available in eleven weeks.

A wrong answer, answered. A learner puts the currency reconciliation on the never list: "too hard to verify at that volume, keep it human". The response:

You applied a real rule (do not hand over what you cannot check) to the wrong property of the task. You measured effort; the rule is about evidence. You do not verify a 528-row pass by redoing 528 rows, which is the assumption under your answer: you verify with a reconciliation and a sample, and Module 4 teaches both. Each of the four documented mismatches (OPP-006697, OPP-006729, OPP-007089, OPP-007326) checks in fifteen seconds against the parent account's currency field.

Applied consistently, your reasoning would exclude every high-volume task, since every high-volume task is expensive to redo by hand. Backwards: high Volume plus high Checkability is the strongest hand-over profile there is, and this task is one. The genuinely unverifiable task feels easier: sixteen call notes, which deals will close, nothing to check against until the quarter ends. That one goes on your never list, under rule 3.

Swap the two entries, and write the deciding factor on each, because that is what stops this pair being confused again: Checkability, high on the currency task, Checkability, absent on the notes task.

What you keep

revenue-workspace/40-reference/delegation-policy.md, the file you started in Lesson 1, section 3 filled: three or more never-list entries, each carrying its generating rule, not only the task. Plus review gate, approver and reversal plan completed on the shortlist entry from Lesson 1.

Quick check

  1. A workflow has run draft-only for six weeks, clean verification every time. Someone proposes promoting it to writes-to-system. Name the one thing that must exist before the first write, and what "tested" means for it.
  2. A task labelled read-only has its output pasted into a customer's quarterly business review deck. Reclassify it and state the added obligation, in the words you would use with the person who pastes it.
  3. Which of your never-list entries would change if the Compliance API covered Cowork tomorrow? If the answer is none, check rule 4 again.
  4. Give a task from your week that is hard and verifiable, and one that is easy and unverifiable. Which have you been avoiding handing over, and why was that backwards?
Answers

1. A tested reversal plan, in the run record before the first write. "Tested" means executed once on a small batch: the file with the previous values exists, a named person can run the re-import, and somebody has watched it restore rows. Six clean weeks earn the conversation. They do not replace the plan.

2. It is draft-only, and always was. Added obligation: a full human read before it leaves the folder, with a named reviewer. To the person pasting: "this is a draft until someone has read it against source, and once it is in a customer's deck the reviewer is you."

3. Only entries under rule 4, because that rule rests on a vendor gap, not a property of the work. If your answer was none, your rule-4 column is empty and you have probably filed an auditability exclusion under rule 5 by mistake.

4. Open. The common pattern is avoiding the hard, verifiable one because volume feels risky, which is backwards: volume plus a source of truth is the best candidate profile there is.

Where this goes next

Next lesson: the rewrite drill that turns an open-ended request into something checkable, what usage costs you, and revising your Module 1 fit log.

Track labs: the exercise sheet in labs/LAB-03 of your practice pack (start with its README). Part A has you defend three scoring decisions in writing, and scores a matching answer with a wrong reason as a miss.