SiSu RevOps

M3  /  L3.1  /  about 17 minutes

The dangerous output is the plausible one

Here is an account list. Well formatted, sorted, total at the bottom, done in forty seconds instead of forty minutes.

Retail accounts, EMEA and NA
account_id   account_name                    country          arr_usd
ACC-02988    Highmoor Retail Inc             United States    (blank, prospect)
ACC-03104    yewtree foods sl                Spain            (blank, prospect)
ACC-03174    Marlowe Stores NV               Netherlands      23220.0
...
Total accounts listed: 87

Nothing about it looks wrong. That is the problem. The correct count is 88. The list is wrong twice.

Everything this lesson uses came in the practice pack from the course page; if you have not downloaded it, do that first.

Once, on a leading space. ACC-02948 carries industry Retail, leading space included (answer-keys/PLANTED-ISSUES.md in your pack, which you open only after attempting the lab, class inconsistent-values). Filter on the exact string Retail: 87 accounts. Trim first: 88. One character, one missing account, no error message.

Twice, on a comma. Row ACC-02890 is named "Highmoor Retail, Inc.", a comma inside a quoted field (DATA-DICTIONARY.md in your pack's data folder, Conventions), and is documented under class duplicate-accounts as a punctuation variant of ACC-02988: the same company. Split on commas without honouring the quoting and you drop the row, shift every column, or invent a company called "Highmoor Retail.

The total at the bottom is still a number, still bold, still wrong. Nobody reading the list will find out.

What you will be able to do

  • Say why plausible is not evidence, in words you can use with a VP.
  • Score any candidate task on five factors and reach a decision.
  • Name the one factor that vetoes a task no matter how good the rest look.

Plausible is not the same as right

Two failure shapes. Only one is a problem.

Visibly wrong. The run errors or produces something obviously mangled. You notice in four seconds. Cost: four seconds.

Plausibly wrong. A clean artifact, wrong in a way you can only see by reading the source. You do not notice. Your manager does not notice. The customer notices in six weeks, or the number lands in a board pack and gets defended by someone who was not in the room.

Everything in this course exists for the second shape. The product fact to quote when someone says the fix is a better prompt: open-ended, recursive or poorly defined tasks raise both the likelihood and the impact of errors. Both. A vague task does not just fail more often, it fails larger, because vagueness lets it touch more.

Check yourself: name a task on your fit log whose failure would be plausible rather than visible.

The five-factor fit test

This is our instrument, built for this course, not product guidance. A scoring sheet, not a formula: its job is to make you say why, not to hand you a number to hide behind.

Score each factor 1 to 5.

Factor Question 5 looks like 1 looks like
Volume How many items, how often? Hundreds of rows, every week Three items, once
Checkability Is there a source of truth I can compare against? A file or system holds the right answer The right answer does not exist yet
Judgment density How much of this is a call only a human can make? Almost none: it is a rule applied to records Almost all of it
Cost of being wrong What happens if a wrong answer ships? Low and reversible: I delete a file A customer sees it, or a system of record changes
Specification cost Can I write down what done looks like in under 20 minutes? Yes, and I already have I would have to think about it for a week

Reading the score. High Volume plus high Checkability plus low Judgment density is the strongest candidate. Do not add the numbers and take the top five. There is a veto:

A low Checkability score is a veto, regardless of everything else.

Low Checkability means shipping work whose correctness you cannot establish, at volume, repeatedly. Volume then flips from an argument for handing over to an argument against: a wrong method on three items is a mistake, on four hundred it is a report.

Two tasks can score identically and want opposite decisions, because the deciding factor differs. So record the deciding factor, not just the total. A manager can argue with a factor. Nobody can argue with a 17.

Check yourself: score one task from your fit log on all five factors, one sentence each.

Watch one task get scored

The task. "Every Monday, produce the list of live customers whose renewal date has already passed with no renewal opportunity, with the ARR at risk on each."

A real pattern in the shipped data: PLANTED-ISSUES.md narrative N8, "Renewals are being missed, not lost", lists eight accounts: ACC-02956, ACC-02958, ACC-03043, ACC-03097, ACC-03099, ACC-03107, ACC-03123, ACC-03174. Not losses. Absences. Nobody built the process.

Factor Score The sentence behind it
Volume 3 308 accounts, weekly. Not huge, but every week forever, and it takes a person forty minutes because no view puts renewal date and renewal opportunities on one screen.
Checkability 5 Two named files, one rule. accounts.renewal_date compared against opportunities where type = Renewal. I can verify any row in twenty seconds.
Judgment density 2 The rule is mechanical. The judgment is what you do about the list, which stays with the CSM.
Cost of being wrong 2 Read-only. A false positive costs a CSM a five-minute check. A miss costs what it costs today, the same as not having the list.
Specification cost 5 I wrote the rule in one sentence, above.

The decision. Hand over now, read-only. Deciding factor: Checkability. Not volume, not time saved.

The deciding factor tells the next person what would change the decision. Add "and create the renewal opportunity" and Cost of being wrong jumps from 2 to 5 (it now writes to the system) while Checkability holds. The decision flips, and the record shows which factor moved it.

And "forty minutes a week" is an estimate stated as an estimate: the labs require baselines measured by doing the task by hand, verification cost counted separately, before any time-saved claim.

Try this now

Your VP wants "a plan for what we automate first". Three candidate tasks from the Talvera revenue team are on your desk. By end of day you need a shortlist row for what goes first and a never-list row for what does not go at all.

Budget six minutes.

Setup

  • Open DATA-DICTIONARY.md in your pack's data folder. You do not need to run anything.
  • You are advancing revenue-workspace/40-reference/delegation-policy.md, sections 2 and 3. This is a file you create yourself, starting this lesson, in the workspace you built in Module 2; the seed template is templates/M3/delegation-policy.md in your pack.
  • The exercise itself is read-only.

The three candidates

Task A. Every Monday, list live customers whose renewal_date has passed with no renewal opportunity, with the ARR at risk. (Scored for you above. Use it as your calibration anchor.)

Task B. For every open opportunity, read the rep's most recent notes and set forecast_category to match what the notes actually say.

Task C. Decide which of this quarter's Enterprise deals we will call as Commit.

Steps

  1. Score B and C on all five factors, one sentence per factor, not just a number.
  2. Name each task's deciding factor in one word.
  3. Write the shortlist row for the task that belongs in section 2 of delegation-policy.md: blast-radius class, review gate, approver, reversal plan.
  4. Write the never-list row for the task that belongs in section 3, naming the rule that excludes it.
  5. One of the three is not clearly in either place. Say in one sentence what would have to change for it to move.

Starter brief, with gaps marked

## Shortlist entry

Task:            <<GAP 1: the task, scoped tightly enough to be checkable>>
Fit score:       V _  Ch _  Jd _  Cw _  Sc _
Deciding factor: <<GAP 2: one word, and it is not "volume">>
Blast radius:    <<GAP 3: read-only / draft-only / writes-to-system>>
Review gate:     <<GAP 4: what a human reads, and how much of it>>
Approver:        <<GAP 5: a person's role, or "none needed" with a reason>>
Reversal plan:   <<GAP 6: what I do if a run ships something wrong>>
Minutes saved:   ____ per week, verification cost of ____ minutes already subtracted

## Never-list entry

Task:            <<GAP 7>>
Excluded by:     <<GAP 8: the rule, not the task. Rules are in Lesson 2.>>
What would change it: <<GAP 9, or "nothing", and say why>>

Stuck? Two hints, in order.

  1. Two tasks are blocked, and not by the same thing. Only one is blocked by risk; the other is blocked earlier, by something missing before you start.
  2. Finish this for each: "I would know this output was wrong if I compared it against ___." Two of the three take a filename in the blank. For the one that does not: does the right answer exist before or after you must act on the output?

Reference answer

Task B: set forecast_category from the rep's notes.

Factor Score Reasoning
Volume 4 Hundreds of open opportunities, refreshed continuously.
Checkability 3 Partly. You can verify the field matches the note, not that the note is right, and the note is the input.
Judgment density 4 High. What a note "actually says" about a deal's confidence is interpretation, and reps write notes the way reps write notes.
Cost of being wrong 5 It writes to the system of record, and forecast category feeds the forecast.
Specification cost 2 Try writing down what makes a note mean Commit: far longer than twenty minutes, and you will not get agreement.

Decision: not as described. Reclassify rather than delegate as stated. Deciding factor: Cost of being wrong, backed by Judgment density.

The version that survives is different: a draft-only list of opportunities where forecast_category contradicts stage, with the evidence line for each. Checkable against a rule, writes nothing, real work in it: PLANTED-ISSUES.md documents fourteen rows in class forecast-contradiction, including OPP-006692 (Closed Lost still in Best Case) and OPP-006934 (Omitted while the stage is Negotiation). The rewrite keeps the value and drops the write path.

Task C: decide which Enterprise deals we call as Commit.

Factor Score Reasoning
Volume 2 A handful of deals, once a quarter.
Checkability 1 Veto. No source of truth. The right answer comes into existence when the quarter closes, after you must act on it.
Judgment density 5 It is the judgment. That is what a forecast call is.
Cost of being wrong 5 The number goes to the board.
Specification cost 1 If you could write down what done looks like, you would not need a forecast call.

Decision: never list. Excluded by the rule "anything where the source of truth is a person's judgment rather than a record". Deciding factor: Checkability.

What would change it: nothing. But do not confuse the call with its support work: assemble the evidence pack each Enterprise deal needs for the commit conversation is high-volume, checkable and mechanical. Assembling the evidence is delegable. Making the call is not.

Your answer may differ, within limits. Scores can move a point either way, and reasonable operators disagree on Task B's Checkability. What may not differ: Task C is vetoed by Checkability, not by risk. "Too risky" is the wrong reason, and it will not survive a VP willing to accept the risk.

Worth knowing: the task you must refuse is not the one with the largest downside. It is the one where you could not tell afterwards whether it worked.

What you keep

revenue-workspace/40-reference/delegation-policy.md, started: one shortlist entry, one never-list entry, and your calibration anchor from the demo. Lesson 3 fills section 1 and the rest of 2 and 3, once you have the blast-radius obligations and the never-delegate rules.

Quick check

  1. Two tasks score 17 out of 25. One is handed over this week, the other never. Give a pair from your own fit log where that is true, and name the factor that differs.
  2. Someone argues a low-Checkability task is fine to hand over because the volume is enormous and doing it by hand is impossible. Answer them in two sentences.
  3. Take the lowest Specification cost item on your fit log and write its definition of done in one sentence, now. If you cannot, what does that say about the score you gave it?
Answers

1. Open on which pair. The factor that differs is the deciding factor, almost always Checkability or Cost of being wrong. Identical totals with different deciding factors is the normal case, which is why the total is not the output of this instrument.

2. Volume is not a defence, it is the amplifier. A wrong method on three items is a mistake, on four hundred it is a report, and low Checkability means you would not find out either way. If it truly cannot be done by hand or checked, then nobody knows whether it is right, including the person asking.

3. Open, and a self-test. If you cannot write it in one sentence now, your Specification cost score was optimistic. Re-score it: that factor is the one people flatter most.

Where this goes next

Next lesson: blast radius starts setting the process, plus the five rules that generate your never list.

Track labs: the exercise sheet in labs/LAB-03 of your practice pack (start with its README). Part A ships twelve real-shaped tasks across all four roles, with reference scoring, and names the two tasks where reasonable operators disagree.