SiSu RevOps

M4  /  L4.4  /  about 11 minutes

Steering, and what survives the session

A run is going wrong in front of you. It has read the wrong file, or taken "the pipeline" to mean something you did not mean, three minutes into a job that will take eight.

Most people do one thing: keep typing corrections until it looks right. That produces an output you cannot reproduce, because the corrections lived in a session that will not exist tomorrow. Then, six weeks later, someone senior asks about a number you no longer remember producing.

What you will be able to do

  • Steer a running task with three moves, and spot the signal that says stop steering.
  • Keep a run record that lets a colleague reproduce a run and lets you defend a number a month later.
  • Say plainly what survives a session and what does not.

Three steering moves, and one rule

Interrupt and narrow. "Stop. Only the EMEA accounts." For when the work is right and the scope is wrong. Cheap, and it usually works.

Interrupt and correct. "Stop. The amount field is in local currency, use the account currency and convert." For when a specific fact is wrong. Also cheap, with a catch: it fixes this run only. The fact belongs in the folder file or the brief, or you will say it again next Tuesday.

Abandon. Stop, do not correct, rewrite the brief and start again.

The rule that tells you which one you are in:

If you have corrected the same misunderstanding twice, stop and rewrite the brief.

Twice. Not "when it gets annoying". The second identical correction is evidence about your brief, not the run: something in it is genuinely ambiguous, and you have confirmed it by observation. A third in-place correction produces work you cannot reproduce, because corrections live in a session that will not exist tomorrow. Abandoning feels like losing three minutes. It is buying back every future run.

Before you abandon, write down the correction you were about to make. It is usually the missing line in your Constraints, easier to capture now than later. Which of the three moves did your last frustrating session need?

The run record

One line per run in 50-runs/RUN-LOG.md, a file you keep yourself: start it from templates/M4/RUN-LOG.md in your practice pack. Nine fields, and each one exists because a specific question gets asked later.

Field The question it answers
Date "When was this produced?"
Brief file used "What exactly was asked for?"
Input files and their dates "Was this before or after the July export?"
Output files "Which file are we even looking at?"
Verification performed, and the result "Did anyone check this?"
Exceptions count "What did it not handle?"
Blast-radius class "Did this need a reviewer?"
Approver, if draft-only or writes-to-system "Who said yes?"
One line of note "Anything odd?"

The input file dates are the field people skip and the field asked about most. "The pipeline export" is not an answer when there have been six of them, and an entry without dates cannot say whether two runs used the same data, the first question anyone asks when two reports disagree.

Worth knowing: the Compliance API and Audit Logs do not cover Cowork yet. At team level that is a rollout question for Module 8. At your level it means the audit trail is a file you maintain, about twenty seconds per run. Do not make the log clever: a markdown table you actually fill in beats a system you abandon in three weeks.

Your memory is a folder

Here is the sentence the whole module is built to earn: there is no memory between sessions. Continuity is a file convention, not a product feature. What survives is exactly what you wrote to disk, nothing else.

What survives Where it lives What it does next time
The brief 20-briefs/<workflow>.brief.md The next run costs a sentence instead of a rewrite
The folder rules revenue-workspace/CLAUDE.md Every task in this folder inherits your conventions
The verification procedure 40-reference/verification-checklist.md You check the same way twice, which is what makes two runs comparable
The run record 50-runs/RUN-LOG.md You can answer "where did this number come from"
The exceptions file next to each output You know what your brief does not handle yet

What does not survive: the correction at minute four, the clarification at minute six, the reason you chose that folder. If those mattered, they were supposed to become one of the five rows above.

The test that separates Assign from Keep: deleted, and the next run is still correct but slower to set up? Assign. Deleted, and you can no longer prove what happened or reproduce the judgment? Keep.

Which of the five files are you missing, and what question can you not answer without it?

A real correction, and the moment it became a rewrite

The task. This week's list of open opportunities whose close date has already passed, grouped by owner, from the shipped data. Fourteen such rows, documented as class overdue-open-pipeline in answer-keys/PLANTED-ISSUES.md in your pack, which you open only after attempting the lab.

Minute two, correction one. The output had more owner groups than there are account executives. I interrupted: "Trim whitespace on owner and treat Dagmar Wexford with two spaces as the same person as Dagmar Wexford." The issue log documents six inconsistent-values rows in opportunities.owner, including OPP-006696, OPP-006746 and OPP-006934 as Dagmar Wexford, and OPP-006795 as bettina costa.

Minute five, correction two. The same thing on a different spelling, Aisling Calderon with a trailing space (OPP-006805), which I had not named.

The decision. Second correction of the same misunderstanding: owner names are dirty and my brief never said what to do about it. I stopped. What I wrote instead, before restarting, went into the folder file rather than the brief, because it is true of every task that groups by owner in this data:

The owner field in opportunities.csv is not clean. Before grouping by owner,
normalise: trim leading and trailing whitespace, collapse repeated internal
spaces, and match case-insensitively. Report the raw variants you merged and
how many rows each covered.

The cost, honestly: the restart took four minutes, the two corrections had already cost three. A third correction would have left a correct output with no route back to it, and next Tuesday the seven minutes again. The rule paid for itself on the second run. The run log entry, written immediately after:

| 2026-08-02 | overdue-pipeline.brief.md | opportunities.csv (2026-08-02 copy),
accounts.csv (2026-08-02 copy) | 30-output/overdue-pipeline/2026-08-02.md |
Reconciliation: 14 rows out, 14 open rows with close_date < today in source.
Sample 10 checked against source, all correct | exceptions: 2 |
read-only | n/a | Rewrote brief after second owner-normalisation correction.
Rule moved to CLAUDE.md. |

Twenty seconds, and six weeks from now that entry answers which export, which brief, whether anyone checked, and why the brief changed.

What you keep

The complete brief pack, four files you created across this module, the module artifact:

  • 20-briefs/account-snapshot.brief.md
  • 40-reference/verification-checklist.md
  • 50-runs/RUN-LOG.md, with at least three real runs recorded
  • revenue-workspace/CLAUDE.md, updated with the output conventions and the standing exceptions rule

Try this now The reusability test is literal. Before you call this done, hand the brief file to another person, or open it yourself in a clean session with nothing else, and see whether it works without additions. A brief only its author can run is not reusable, however good the output.

Check yourself

  1. You have corrected the same misunderstanding twice in a running session. State the correct next move and give the reason in terms of reproducibility, not frustration.
  2. A run log entry records the brief, the outputs and the verification, but not the input file dates. Name the question it can no longer answer, and give a situation where that question is the only one that matters.
  3. Your workflow now runs from a saved brief. Which of these breaks it: deleting the brief file, the run log, CLAUDE.md, or last month's output? For each, say whether what you lost was Assign or Keep.
  4. You measured three numbers on this workflow: time to first output, time to verified output, time to second run using the saved brief. Which one justifies the method, and which one is usually quoted instead?
Answers

1. Abandon and rewrite the brief. Not because it is annoying, but because a correction lives in a session that will not exist tomorrow. A third correction gives you an output nobody can reproduce, including you. Write down the correction you were about to make: it is the missing line in your Constraints.

2. "Did these two runs use the same data?" That becomes the only question that matters the moment two reports disagree and somebody senior is deciding which to believe.

3, one line per item:

  • Brief file: breaks it. Assign. Not runnable as it stands, though rewritable from the output.
  • Run log: does not break the next run. Keep. Nothing stops working and you can no longer prove what happened.
  • CLAUDE.md: degrades it quietly. Assign. The run still produces something, conventions gone, nothing announcing their absence. The one people mis-sort, because the exceptions rule it carries is what produces a Keep artifact.
  • Last month's output: breaks nothing, and it is neither. A product of a run, reproducible from the brief.

4. Time to second run justifies the method, and it is usually the smallest of the three. Time to first output is the number people quote, and it says least.

Where this goes next

Next module: Module 5 runs T, R, A, C, K in order against CRM data hygiene. Every findings list from here on is measured on detection: how much you found, how much was real, whether you caught the defects that do not announce themselves.

Track labs: the exercise sheet in labs/LAB-04 of your practice pack (start with its README). Part B builds this same pack on your own top shortlist workflow from Module 3, behind the redaction gate, and measures time to first output, verified output and second run.