Haute Lumière

Commerce · III.06 · MMXXVI · daylight

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

WORKBOOK — THE LUMINOUS GAINSHARE EMPLOYEE

Chapter III.06 · Mycelial Finance

How the mechanism reads from inside. What to measure, what to claim, how the ledger works, what to ask for.

---

WHAT A GAINSHARE ACTUALLY IS

A gainshare is a written rule that converts a measured improvement into money that reaches you. Not a bonus, which is discretionary and assessed centrally. Not equity, which pays on an event you do not control. A rule: when this number moves, this much of the movement comes to the people who moved it, on this date.

This chapter matters to you more than most, because it is about the difference between being assessed and being read.

A performance review is a central assessment. It costs the organisation real money — a manager's preparation, a calibration meeting, a moderation panel — and, exactly like the $3,000 credit assessment in the chapter, its cost does not fall with the size of the thing being assessed. That is why small contributions go unrecognised: not malice, arithmetic. A central assessment cannot afford to look at small things.

A gainshare reads a local signal instead. The line ran faster, the scrap fell, the renewal rate rose, the call did not have to happen twice. Nobody had to form a view about you. The number moved and the ledger paid.

Your work this term is to find the signal, get it counted, and make sure the rule that reads it is written down before there is anything to argue about.

---

PART ONE — DISCOVERY

Days 1–30: find the signal you already emit

1.1 — The four-week log. For four weeks, write one line a day: what did I do today that made something measurable move? Not achievements. Movements — units, minutes, defects, calls, renewals, tonnes, tickets, hours saved for somebody else.

At the end of four weeks you will have roughly twenty lines. Circle the ones where the movement is already recorded in a system somebody else can see. Those are your local signals. The rest are real work that is currently invisible, and Part Three is about making them visible.

1.2 — Apply the strict test. For each circled item ask the chapter's question: can this be read without anybody being asked? If your contribution is only visible when your manager remembers to mention it, it is not a signal — it is an assessment, and assessments are expensive and therefore rationed.

1.3 — Find the trades you are already in. List the five people whose work you make easier and the five who make yours easier. For each pair write what moves in each direction. This is Kiers' reciprocal reward at desk level: delivery in proportion to delivery, and it is running whether or not anybody has written it down.

Notice how much of the value in your team sits in those exchanges rather than in any individual's output. That is the whole argument for a pooled gainshare and you now have the evidence for it in your own handwriting.

1.4 — Find the existing rule. Get the actual scheme document. Not the intranet summary — the document. If there is no document, that is the most useful finding of the month and Part Four tells you what to do with it.

---

PART TWO — THE ARITHMETIC

Days 31–45: compute what the rule actually pays

2.1 — The flat pool. Take a pool of $480,000 shared by 60 people:

  480,000 / 60  =  $8,000 a head, flat

Every gainshare begins as this number, and every argument about gainshare is an argument about how far it should move away from it.

2.2 — The local-signal weight. Now weight it by a measured local signal with a weight of 0.30 — meaning a top-quartile contributor receives 1.30 times the flat share and a bottom-quartile contributor 0.70 times:

  top quartile      8,000 x 1.30  =  $10,400
  bottom quartile   8,000 x 0.70  =   $5,600
  spread                            =   $4,800

Sit with that $4,800. It is the entire behavioural content of the scheme. If the spread is too narrow, the signal is decorative and people ignore it. If it is too wide, people optimise the measure and stop doing the work — and you should ask for it to be narrowed, out loud, because a scheme that destroys the thing it measures pays nothing in year three.

2.3 — Compute your own number. Do this before any conversation about it:

  pool size (or the rule that determines it)        ______
  headcount in the pool                             ______
  flat share = pool / headcount                     ______
  weight applied to the local signal                ______
  your expected share at your current standing      ______
  your share if your signal moved one quartile      ______

The last line is the only one that tells you whether the scheme is worth responding to. If moving a quartile is worth a few hundred dollars, the scheme is a communication exercise and you should treat the work on its own merits.

2.4 — Your personal correlation. The chapter's honest negative applies directly to you. Redundancy protects against idiosyncratic loss and not against correlated loss, and most employees are far more correlated than they realise:

  salary            depends on   one employer
  gainshare         depends on   the same employer
  pension           often on     the same employer's sector
  professional network  on       the same industry
  housing cost      often on     the same city as the employer

That is not a diversified position. It is one position, held five ways. At ρ near 1 the number of exposures is irrelevant — exactly the finding that ten times the borrowers buys 0.03 percentage points of standard deviation at ρ = 0.05. Name one move this year that lowers your own ρ: a second income line, a transferable credential, a network outside the industry, savings held in something your employer's fortunes do not drive.

2.5 — What the scheme pays in a bad year. Find the clause. If the pool is a share of profit or of surplus, model it at minus twenty percent and at minus fifty percent. A scheme you have only ever modelled in a good year is a scheme you do not understand.

---

PART THREE — DESIGN

Days 46–70: make the uncounted countable

3.1 — Instrument one invisible thing. Take the most valuable item from your four-week log that is currently not recorded anywhere. Design the smallest possible measurement of it: one number, collected automatically if at all possible, with a baseline taken before you change anything.

The baseline is the whole exercise. A number without a before is an opinion, and an opinion is what a central assessment is for.

3.2 — Propose it as a rule, not as a case. There is a large difference between "my work should count" and "here is a number, here is how it is collected, here is what it was before, and here is the rule I propose for how it enters the pool." The first asks for an assessment, which is expensive, and expensive requests get deferred. The second is a piece of finished design, and finished design gets adopted because adopting it is cheaper than arguing with it.

3.3 — Watch for the form. The chapter's sharpest operational warning applies inside a company exactly as it does inside a lending network: a cheap signal quietly becomes an expensive assessment the moment somebody adds a form. If your new measure starts to require a monthly self-report, its cost has moved from forty dollars toward three thousand, and within two quarters somebody will kill it as bureaucracy — and they will be right.

Design it so nobody has to fill anything in, or do not design it.

3.4 — Ask who is on risk. This is the Balenciaga question turned on your own employer, and it is entirely fair to ask out loud. The intermediary in a network should hold a slice of what it originates, pari passu — otherwise it earns on volume and bears nothing. The equivalent question here: when the gainshare pool is smaller than forecast, what else gets smaller? If the honest answer is "only the employee pool", the scheme is a fee arrangement dressed as a share. Ask for one line connecting the pool to something the people who set it also feel.

3.5 — The price of refusal, inside a team. A pooled gainshare gives every member a financial interest in every other member's contribution, which means somebody eventually has to say that a colleague's contribution is low. That is the price of refusal from Brief 7 and it is paid in relationships, not cash.

Two ways to make it survivable, both worth asking for: make the weighting a rule applied to a measure rather than a judgement made by peers, and keep the spread narrow enough that no single member's standing is worth destroying a working relationship over. $4,800 is enough to notice and not enough to poison a team; a spread of forty thousand is not.

---

PART FOUR — DESTINY AND DELIGHT

Days 71–90: make it hold

4.1 — Get it into the standing pack. Whatever number you instrumented, get it onto a report that is produced monthly whether or not anybody asks. Reviewed monthly, it persists. Reviewed by exception, it disappears the first quarter somebody is busy.

4.2 — Ask for the four things in writing. These are what turn a scheme into a ledger, and every one of them is reasonable:

1. The formula — how the pool is determined, in arithmetic, not adjectives.
2. The denominator — who is in the pool and who is excluded, by name or by rule.
3. The dates — when the measure closes and when the money arrives.
4. The change clause — who can alter the formula, with what notice, and what happens to a period already underway.

A scheme with all four is a mechanism. A scheme missing any one of them is a discretion with a spreadsheet in front of it, and you should plan accordingly rather than resentfully.

4.3 — Recruit the second owner. A measurement with one champion is a hobby. Find one colleague in a different function who benefits from the same number and hand them the credit for the first result. This costs you nothing you actually needed and doubles the lifespan of the thing.

4.4 — Delight. The good moment in this work is not the payment. It is the first month the number is produced by the system without anybody touching it, and somebody in another team uses it in an argument that has nothing to do with you. That is the moment your measure stopped being yours and became infrastructure, which is exactly what you wanted and is why it will outlast your tenure.

---

KNOW YOUR SCHEME — A CHECKLIST

Answer every line. Any blank is a question to ask this month.

---

THE CONVERSATION, SCRIPTED

For the meeting where you ask for a signal to be counted. Fifteen minutes.

Open with what is working. "The renewal process has been running well since March, and I think the reason is measurable. I want to show you a number and propose a rule."

Hand over the number and the baseline. "Here is the figure for the four months before, and here is the figure since. It comes out of the same system we already use, so nobody has to report it."

Propose the rule, not the recognition. "I would like this to enter the pool calculation at a weight of X, starting next period. Here is what that would have paid in each of the last two periods, so we can both see the size of it before we agree to it."

Name the risk yourself, first. "The way this could go wrong is if people start optimising the measure instead of the work. The protection is that the spread stays around five thousand and the measure is read automatically, so there is no way to report your way into a better number."

Ask one clean question and stop talking. "Can we run it for two periods and review it against the pack?"

That is the entire meeting. You have brought a finished design, priced it, named its failure mode and asked for a bounded trial. It is very difficult to refuse and, more importantly, it is easy to say yes to — which is the property you are actually engineering for.

---

---

IF THERE IS NO SCHEME AT ALL

Sometimes Exercise 1.4 comes back empty: there is no document, because there is no scheme. That is a better position than an unwritten one, and here is why.

An unwritten scheme has already set expectations you cannot see and cannot audit. A blank page has not. So propose the smallest possible mechanism rather than asking for a scheme: one number, one pool, one period, one formula, one review date. Name a pool that is a share of a measured improvement rather than a share of profit, because a measured improvement is attributable and profit is not, and attribution is the thing an unconvinced finance function will refuse you on.

Ask for it as a trial with an end date. A two-period trial costs the organisation an amount it can compute in advance, which makes it a decision rather than a commitment — and decisions get made, while commitments get deferred to a planning cycle that never quite arrives. When the second period closes, you will not be asking for a scheme any more. You will be asking whether to continue one, and that is a different meeting with a much better ending.

APPRECIATIVE QUESTIONS FOR YOUR TEAM

Six, to be asked out loud, in the 4D order.

1. Discovery. What does each of us do that makes somebody else's work easier, and where is that currently recorded?
2. Discovery. When has this team been paid or credited for something it genuinely did? What made that possible?
3. Dream. If everything we actually contribute were readable without anybody filling in a form, what would change about how this team works on a Tuesday?
4. Design. What is one number we could start collecting this month that would be believed by somebody outside this room?
5. Design. What spread between the highest and lowest share would be enough to notice and small enough to keep us working together?
6. Destiny. What would tell us early that our measure had started to be gamed — and who among us would see it first?