Haute Lumière

Commerce · III.10 · MMXXVI · daylight

La Bourse  /  Volume III  /  Nº III.10  /  Workbook — the Gainshare employee

WORKBOOK — THE LUMINOUS GAINSHARE EMPLOYEE

Chapter III.10 · Reserves and Resilience

For the person working inside a gainshare arrangement — where a defined share of verified improvement returns to the people who created it. Reserves are where gainshare schemes are won and lost, because a buffer is the one improvement that looks like a cost on every measure a scheme usually tracks.

---

WHY THIS CHAPTER IS DIFFERENT FROM INSIDE

Most of what a gainshare rewards is visible: less waste, less downtime, more output, lower unit cost. Reserves are the opposite. A buffer built this year shows up as inventory, idle capacity or unbilled hours — a cost today against a loss that may not arrive for years.

So a scheme measured on cost reduction will pay you to remove buffers and pay you nothing to build them. That is not somebody's bad faith. It is the mechanism working exactly as written, and it is the single most valuable thing you can put your hand up about.

There is a second half, and it is the one that puts money in your pocket. The reserve that is easiest to build from the floor is the living kind — skill, maintenance practice, supplier relationship, the ability to run a line without the one person who knows how. Those cost almost nothing to hold, they produce in ordinary weeks, and they are invisible in the accounts. An uncounted gain is not a shared gain. Making them countable is the highest-leverage move available to you.

---

PART ONE — DISCOVERY

Days 1–30: find the buffers you are already carrying

Exercise 1.1 — The buffer you personally hold (90 minutes)

Write down every buffer you or your team maintain that nobody has asked for and nobody has costed:

Prompts that reliably find them:

• The spare part somebody keeps in a drawer.
• The second person trained on the machine "just in case."
• The half-hour at the end of the shift that absorbs the overrun.
• The supplier contact somebody keeps warm with a Christmas call.
• The workaround only one person knows, which is a buffer and a single point of failure at the same time.
• The standard you hold above specification because you know what happens when you do not.

Exercise 1.2 — Which of them has actually been drawn? (30 minutes)

Mark the last time each was used. A buffer that saved a shift last March is a documented buffer, and a documented buffer can be claimed. Get the date, the shift, the job number. That evidence is the asset. You cannot claim what you cannot date.

Exercise 1.3 — Whose variance are you absorbing? (45 minutes)

The chapter's arithmetic: in its worked case, 96.34 percent of the required buffer came from supplier lead-time variance, not demand. On the floor this is extremely recognisable — most of what you absorb is somebody else being late, short or wrong, upstream of you.

List the five largest sources. If they are mostly external, you are personally carrying a cost the firm has not priced and cannot see. That is not a complaint. It is an unpriced contribution, which is exactly the thing a gainshare exists to convert into money.

Exercise 1.4 — The appreciative team conversation (45 minutes)

"Think of a time here when something could have gone badly wrong and didn't. Not the big save — the quiet one. What was in place that made it a normal day?"

Take notes on what was in place, not on who acted. What you are assembling is a list of reserves, and reserves are conditions rather than heroics. A scheme can pay for a condition. It cannot pay for luck.

---

PART TWO — THE ARITHMETIC

Days 31–45: compute what the buffer is worth

Exercise 2.1 — Price one buffer, properly (90 minutes)

   annual cost of holding it   =  value tied up × carrying rate (use 25%)
                               or hours held × loaded hourly cost
   value when drawn            =  what the event would have cost
                                  × the share this buffer actually prevented

That second multiplier is the recovery fraction and it is the number everyone gets wrong. Toyota's post-2011 chip buffer bought roughly two quarters of a shortage that ran over a year. Claim the share, not the whole event — a claim at 1.0 gets challenged and loses the entire argument; a claim at 0.4 that you can defend gets paid.

Exercise 2.2 — Break-even return period, for your buffer (45 minutes)

        loss the event causes  ×  share this buffer prevents
   T* = ─────────────────────────────────────────────────────
                   annual cost of holding it

Worked, from the floor: a spare drive assembly worth £8,000 carries at 25 percent = £2,000 a year. A line stoppage costs £40,000 and the spare prevents about half of it, so T* = (40,000 × 0.5) / 2,000 = 10 years. Now look at the maintenance log: if that failure has happened twice in nine years, the interval is 4.5 years, and the spare clears break-even by 2.2×.

That sentence — "this clears break-even by 2.2 times on our own maintenance log" — is worth more in a scheme meeting than any argument about safety, because it is in the scheme's own units.

Exercise 2.3 — The three questions to ask of your scheme (one week)

1. Does the measure count a buffer as a cost? Almost all do. Inventory, unbilled hours and idle capacity all score against you.
2. Does the period reach the payoff? A buffer pays on a return period of years. A twelve-month measurement window with a resetting baseline will never see it, so the rational response of everyone in the scheme is to build only improvements that show inside twelve months. Yours is a design problem, not a motivation problem.
3. Is there an avoided-loss clause? Some schemes credit verified avoided cost. Most do not, because nobody wrote one. This is the ask, and it is the central ask of this workbook.

Exercise 2.4 — The honest negative, and why you should raise it yourself (45 minutes)

Over-reserving loses. A firm holding 20 percent of capital in dead reserve drags growth from 12 to 10 percent; over twenty years the lean competitor ends 43.39 percent larger, and the buffer is only justified if ruin without it would arrive more often than once in 56 years.

Raise this before anyone else does. A person who arrives arguing for buffers is heard as someone protecting their own comfort. A person who arrives with both directions — here is what we are under-reserved on, here is what we are over-reserved on, and here are the two return periods — is heard as someone running the number. The second person gets the clause written.

---

PART THREE — DESIGN

Days 46–70: make the uncounted countable

Exercise 3.1 — Draft the avoided-loss clause (one week)

Four parts, and it is the same four parts as any gainshare:

1. The register. A named list of buffers, each with an event, a duration and an annual cost. Agreed and signed, like a baseline.
2. The trigger. An incident of the named type, logged, with a date.
3. The computation. avoided loss = event cost × recovery fraction, with the fraction agreed in advance, not argued after the event when everyone's interests have moved.
4. The share. The scheme's existing percentage, applied to avoided loss exactly as it is applied to realised saving.

Pre-agreeing the recovery fraction is the whole craft. After an incident nobody can distinguish the buffer's contribution from everyone's improvisation, and the argument becomes unwinnable in both directions.

Exercise 3.2 — Build one living reserve and document it (three weeks)

Living reserves cost almost nothing to hold because they produce in ordinary periods. Pick one:

• Cross-training. A second person fully competent on the constraint machine. Costs training hours; returns flexibility every week, not only in a crisis.
• Maintenance practice. A rebuild programme instead of a replacement cycle.
• The supplier relationship. The contact who takes the call at six in the evening. Log the calls; it is a real asset and it is entirely undocumented.
• Design for repair. A fixture or fixture change that makes a failure a thirty-minute job instead of a three-day one — this reduces both the event cost and the buffer needed, which is the best move on the board.

Document from day one: hours in, ordinary-period benefit, and the log of every time it was drawn.

Exercise 3.3 — The correlation check (30 minutes)

Living reserves are cheap because they sit inside the system they insure — and weak for the same reason. Cross-training fails when the whole shift is off sick. The supplier relationship fails when the supplier's whole sector is short.

Say this out loud when you propose it. Naming the limit of your own proposal is what makes the rest of it credible, and it is the difference between being the person with an idea and being the person the scheme committee asks.

---

PART FOUR — DESTINY AND DELIGHT

Days 71–90: make it hold

Exercise 4.1 — Get the register into the standing pack (day 71)

One line per buffer: the event, the annual cost, T*, the observed interval. Anything reviewed monthly persists; anything reviewed by exception erodes. Once a number is in the pack, removing it requires somebody to explain why — a conversation nobody wants to have.

Exercise 4.2 — Run one drawdown drill (days 75–85)

Use a buffer on purpose, at small scale, and write down what stopped you. It is almost never the stock. It is the authority: somebody has to be allowed to open it, and the eight hours in which opening it matters are not the hours to discover who that is.

Exercise 4.3 — Ask for the clause (day 90)

One page, four lines, in the scheme's own units. Given to whoever chairs the scheme. Not the whole workforce, not a newsletter. One person, one page, one number.

Delight. There is a particular satisfaction in the shift where nothing happens because of something you built eleven months earlier — the part arrives, the second operator steps in, the supplier picks up. Nobody outside notices. That is the product: an ordinary week where an extraordinary one was available, and once the register exists, the ordinary week has a number beside it and the number has your name on it.

---

KNOW YOUR SCHEME — A CHECKLIST

Answer in writing. Any blank is a question for the scheme chair this month.

1. Does the measure treat inventory, spares or idle capacity as a cost?
2. Is there any avoided-loss or risk-reduction term at all?
3. What is the measurement period, and does the baseline reset?
4. Who logs incidents, and is that log the same one the scheme would use?
5. Is the recovery fraction agreed anywhere in advance?
6. Are training hours a cost against the pool, or an investment outside it?
7. Is there a floor or carry-forward for a period that misses?
8. What is the allocation basis — headcount, hours, salary-weighted, team?
9. Who verifies, and when?
10. If the firm avoided a £2m loss next quarter because of something this team built, is there a single line in the scheme document under which you would be paid for it?

Question ten is the whole workbook. If the answer is no, that is not a grievance. It is a gap in a document, and documents can be amended.

---

THE CONVERSATION, SCRIPTED

"I've put the team's buffers on one page — what we hold, what it's against, what it costs us to hold, and how often the event has actually happened on our own log. Three of them clear break-even comfortably. Two don't, and I'd take those out. The scheme currently counts all five as cost, so we're being paid to remove the three that are working. I'd like to talk about an avoided-loss line — and I'd want the recovery fraction agreed up front so nobody's arguing about it after an incident."

Four things make that work, and they are the only four. You brought both directions. You brought the firm's own log. You used the scheme's units. And you proposed a document change, not a feeling.

---

APPRECIATIVE QUESTIONS FOR YOUR TEAM

1. Think of a shift where something could have gone badly and didn't. What was in place? Who put it there, and does anyone outside this room know?
2. Which of our buffers has actually been used in the last two years, and what did we learn about who is allowed to open it?
3. What do we hold above the standard because we know what happens otherwise — and what would it take for that to be counted rather than tolerated?
4. Which upstream variance do we absorb most often, and what would it be worth to the firm if it stopped arriving?
5. If we could add one line to the scheme document, what would it say — and in whose words would it have to be written to get signed?
6. What is the one living reserve — a skill, a relationship, a practice — that we would most want still standing here in ten years?

---

THE LEDGER — how an avoided loss is actually recorded

A gainshare pays out of a ledger, and a ledger will not accept a sentence. Here is the form that clears verification, in the order a verifier reads it.

Two disciplines make this survive contact with a finance function.

Net of the cost of holding. Credit avoided loss − annual carry, not the gross. A scheme that pays the gross while the firm absorbs the carry will be closed by the first controller who reads it, and a closed scheme has paid you nothing.

Carry the register forward unchanged. If the register is rewritten after each period, every buffer becomes arguable and the ratchet arrives through the back door. Fix it for a stated term — three to five years is the common shape — and publish any change schedule in advance, so everyone can see it coming.

When those two are in place, a buffer stops being the one improvement the scheme cannot see and becomes the one improvement it can price.