Haute Lumière
Commerce · III.11 · MMXXVI · daylight
For the person inside a scheme that pays a share of what the business gains. This chapter is the one that decides whether your scheme is worth being in, because it is about the gap between what gets counted and what actually happened — and you are standing in that gap every day.
A gainshare pays on measured gain. So the whole question, from where you sit, is what the measurement can see.
You already know the answer, because you can name the things you do that the ledger has never registered: the handover that stops a defect two weeks later, the customer you talk down, the colleague you train, the shortcut you refuse to take. None of that has a price. Some of it can be priced and nobody has bothered. Some of it genuinely cannot, and if it is forced into a number it will be a bad one that follows you around.
This chapter gives you two instruments for exactly that situation.
The convergence test tells you which of your uncounted contributions is priceable. Two methods, one ratio. If they converge, go and get it counted — that is money. If they do not, stop trying to price it and ask for the other kind of recognition instead, because a bad number in a scheme is worse than no number.
The incidence of a refusal tells you who benefits when something is left uncounted. The answer, reliably, is whoever is already inside. In a gainshare, that is whoever sits closest to the metric.
Exercise 1.1 — The uncounted inventory (2 hours)
List fifteen things you do in a month that create value the scheme does not measure. Be specific: not "I help people" but "I rewrite the handover note so nights do not have to call days."
For each, three columns:
| What I do | Who would notice if I stopped | How long until they noticed |
That third column is the one that matters. A contribution with a long detection lag is exactly the contribution a measured scheme will fail to see, and it is the one most at risk when a scheme starts paying on what it can count.
Exercise 1.2 — The concentration question (one week)
Look at where the gainshare's measured gain lands. Then ask, on the chapter's pattern: who is closest to the measured thing?
The chapter's water city is the general form. A subsidy of $74,646,000 is distributed by a rule nobody wrote down, and the richest quintile takes 40.3 percent while the poorest takes 5.6 percent — 7.24 times as much — because the rule is really do you already have a connection. In a gainshare the equivalent question is: do you already sit on a metric? If the scheme counts throughput and you are in quality, you are the household without a meter.
Write one paragraph identifying who in your business is unconnected to the metric. You will be asking for them later, and that is a stronger position than asking for yourself.
Exercise 1.3 — The appreciative team conversation (45 minutes)
Ask your team, out loud:
"When has something gone unusually well here that the numbers never showed? What made it possible? And what would somebody have had to offer you to make you less willing to do it?"
Take notes on the third answer especially. The chapter's evidence is that a small payment attached to a discretionary act can reduce it — donation among women fell from 52.0 percent to 30.0 percent under a small offer, a relative fall of 42.3 percent, and the effect vanished when the money could be given to charity. Your team will tell you where that risk sits in your own scheme, and they will tell you accurately, because they have already felt it.
Exercise 2.1 — Price one uncounted contribution (90 minutes)
Take the single item from Exercise 1.1 with the largest consequence. Price it twice, by two methods that share no assumptions:
Write both, and write the ratio.
Read the ratio the way the chapter reads it. Under about 3, you have a priceable contribution and a claim you can make. In the hundreds — the chapter's undefined case runs at 903.2 times, against a value of a statistical life where two independent public methods land within a deflator of 1.556 of each other, at $7,400,000 in 2006 dollars becoming $11,514,782 — you do not have a claim, you have a case for a different instrument. Ask for recognition, a standard, a protected allocation of time. Not a line in the bonus.
Exercise 2.2 — Your share, computed (60 minutes)
Take the scheme's own formula and run it on the contribution you just priced.
your share = measured gain x pool rate x your allocation
Write all three numbers down. Then write the number from Exercise 2.1 beside it. The gap between them is the honest size of what the scheme cannot see, and that gap is the entire subject of your next conversation with the person who owns the scheme.
Exercise 2.3 — The honest negative, about your own scheme (45 minutes)
Every measurement regime reshapes behaviour toward what is measurable. That is not a reason to refuse measurement; it is a reason to name the risk in advance and design against it.
Write down three ways your scheme could be gamed without anybody breaking a rule. Then write, beside each, the standard or the floor that would prevent it — a minimum quality threshold, a safety veto that cannot be traded, a non-convertible recognition for the long-lag work.
This is the single most valuable document you will produce in ninety days, and it is far better received before a scandal than after one. The chapter's form: the lead phase-out did not price a microgram; it set a standard — blood lead from 15.0 µg/dL to 2.8 µg/dL, a fall of 81.3 percent, a ratio of 5.36 — and put the market inside it as tradable credits. A gainshare with standards inside it is the same design.
Exercise 3.1 — Build the baseline nobody built (2 weeks)
For the contribution that passed the convergence test, build the measurement. A count, a log, a monthly tally — it does not have to be elegant. It has to exist before anyone argues about it.
The rule the chapter insists on and you should inherit: where you cannot measure, write unknown, never zero. A missing answer and a zero are not the same fact, and a scheme that cannot tell them apart cannot be trusted about either.
Exercise 3.2 — The proposal (one page)
What it is. [The contribution.] What it is worth. Method A: [X]. Method B: [Y]. Ratio: [X/Y]. Why it is not currently counted. [The reason, without blame.] What I propose. [The measure, and who verifies it.] What it costs to add. [Honestly.] Who else it would reach. [The unconnected group from Exercise 1.2.]
That last line is the one that gets it agreed. A claim that also lifts people who are not you is a different kind of claim.
Exercise 3.3 — Read the reversion (1 hour)
Find out what happens in your scheme when a measured gain is fully realised. Does the share continue, taper, or revert? Ask directly and get the answer in writing. The well-designed version reverts the benefit to the operating team once the funding is repaid, and that reversion is what buys genuine cooperation rather than compliance.
Exercise 3.4 — Ask for the non-convertible recognition (one conversation)
For the contributions that failed the convergence test, ask for something that is not cash and cannot be turned into cash: protected time, a named standard you own, a role in the review, your name on the method.
This is not a consolation prize and you should not present it as one. The evidence is that non-convertible recognition holds discretionary effort where a small payment destroys it. You are asking for the instrument that works, not the one that pays.
Exercise 4.1 — Into the standing review (one conversation)
Get your new measure into the monthly review. Anything reviewed monthly persists. Anything reviewed by exception is a hobby.
Exercise 4.2 — The second owner (this month)
Find one colleague who benefits from the measure and hand them the credit for the first result. One person is a hobby; two is a practice.
Exercise 4.3 — The written record (ongoing, 10 minutes a week)
Ten minutes, once a week: what you did that the ledger saw, and what you did that it did not. At the end of a year this is the most persuasive document in any conversation about your scheme, and it cannot be reconstructed afterwards.
Exercise 4.4 — Delight, honestly (ongoing)
The pleasure available here is not the payout. It is the moment a thing you have been doing invisibly for two years appears on a page with a number beside it, and somebody who had never noticed it says the number back to you in a meeting. That is the moment a contribution becomes infrastructure. It stops being yours, which is exactly what you wanted.
Get written answers to every one of these. A scheme that will not answer them in writing is a scheme whose answers you will not like.
You. I want to put something in front of you that I think the scheme is not currently seeing. I have priced it two ways, and the two answers are within [ratio] of each other, so I think it is measurable rather than a matter of opinion.
Them. What is it?
You. [The contribution, in one sentence, with the detection lag named.] Method A says [X], method B says [Y]. The scheme currently pays me [share] on the measured gain, which does not include any of this.
Them. What are you asking for?
You. Three things, and the third is the one that matters. A measure — here is what I would count and who could verify it. A floor — here is the standard that stops the measure being gamed, including by me. And it should reach [the unconnected group], not only me, because they are further from the metric than I am and doing the same work.
Them. And if we cannot measure it?
You. Then we should say unknown rather than zero, and I would ask for the non-cash version instead — protected time and ownership of the standard. A bad number in a scheme is worse than no number, and it is worse for you than it is for me.
It happens, and it is not the end of the ninety days. Three routes, and all three leave you better placed than before you asked.
Route one — measure it anyway, and keep the record. A refusal to add a measure is not a refusal to let you count. Keep the tally yourself, monthly, for two quarters. A claim supported by six months of your own consistent record is a different conversation from a claim supported by a conviction, and the second conversation costs the scheme owner far more to decline.
Route two — take the floor instead of the share. If the measure will not be added, ask for the standard: a written quality threshold, a safety veto, a minimum handover, something that cannot be traded away for measured throughput. This protects the work whether or not it ever pays you, and it protects the people further from the metric than you are. It is also, on the record, the higher-yield instrument — the lead phase-out is the case, and no microgram was ever priced.
Route three — ask who else has asked. A single request reads as a personal grievance; three requests from three parts of the business read as a design fault in the scheme. Find the other two. The colleague in quality, the one on nights, the one whose work has the longest detection lag. You are not competing with them for a fixed pool — you are all outside the same metric, and that is a stronger fact together than separately.
And keep the tone the chapter keeps. Nobody built the scheme to exclude you. Schemes measure what is easy to measure, and easy-to-measure is a property of instruments, not a judgement about worth. You are offering to extend the instrument, which is help, and it should sound like help.
Do not ask for a small payment attached to a discretionary behaviour — yours or anyone else's. It is the one request in this workbook that can make things worse, and the evidence is specific: a tiny piece rate produced 23.1 correct answers against 28.4 unpaid, 18.7 percent worse; a 1 percent commission returned 153.6 NIS against 238.6 unpaid, 35.6 percent worse; and even 10 percent, at 219.3, stayed 8.1 percent below the unpaid arm.
If a behaviour is currently held by professional pride, a small payment will convert it into a job and price it badly. Pay properly or do not pay. Ask for the measure and the proper share, or ask for the non-convertible recognition. Never ask for the token.