Haute Lumière
Commerce · I.09 · MMXXVI · daylight
WORKBOOK — THE LUMINOUS GAINSHARE EMPLOYEE
Chapter I.09 · The Institutional Handshake
For the person inside a gainshare, whose upside depends on results that have to pass through somebody else's approval machinery before they count.
WHY THIS CHAPTER IS YOURS
A gainshare pays you a share of a measured improvement. Every clause in it — baseline, measure, share, verification, period — is a rule you did not write and cannot change unilaterally. You are already living inside the situation this chapter describes. Your employer's scheme rules are an institution that cannot change its own rules, and so is every customer whose signature your gain depends on.
That has two consequences, and the second is the one worth the workbook.
The first is defensive: an improvement that cannot be classified under the scheme's measure does not pay you, however real it is. You have probably already made one of those.
The second is the opportunity. A scheme's rules are a published document with paragraph numbers, and the fastest route to a larger share is almost never a negotiation about fairness. It is finding the paragraph that already covers what you are doing, and citing it. That is the same move the chapter teaches a practitioner facing a procurement department, and it works here for the same reason: you are not asking for an exception, you are asking for a classification.
PART ONE — DISCOVERY
Days 1–30: read your own scheme as a scheme of delegation
Exercise 1.1 — Obtain the documents (2 hours)
Three things, and you are entitled to all of them:
- The scheme rules in full — not the summary sheet, the governing document.
- The measure definition — the formula, written out, with its inclusions and exclusions.
- The verification and dispute provisions — who checks, on what cycle, and what happens when the parties disagree.
Ask in writing, calmly, as a request for clarity. Note how long the reply takes. That is your first measurement of this institution and it is a useful one.
Exercise 1.2 — The classification table (90 minutes)
List everything your team did last quarter that created value. For each, mark whether the scheme's measure captures it, and if not, why not.
| What we did | Value created | Captured by the measure | If not, why not |
|---|---|---|---|
The last column is the whole exercise. Four reasons account for nearly all of it: it fell outside the measurement boundary; it landed in a different period; it benefited another team's number; or nobody has ever recorded it, so there is no data series it could appear in. The fourth is the most common and the easiest to fix.
Exercise 1.3 — Find the paragraph (60 minutes)
Read the scheme rules all the way through and find the sentence that comes closest to authorising the thing you want counted. Most schemes contain a clause on adjustments, on extraordinary items, on measure review, or on the addition of sub-measures by agreement.
Write it out by hand with its paragraph number. You now hold a category, and a category turns a grievance into an application.
Exercise 1.4 — The appreciative conversation (45 minutes)
Find whoever administers the scheme and ask exactly this:
"I'm trying to understand how the measure handles things it wasn't originally written for. Can you tell me about a time something got included that you didn't expect — what it ended up being treated as, and who worked that out?"
Take notes on the treatment, not the amount. Scheme administrators are almost never asked anything except whether the payment is right, and most of them would rather talk about the design.
PART TWO — THE ARITHMETIC
Days 31–45: compute what is actually at stake
Exercise 2.1 — Your own delegation ladder (2 hours)
Map who has to agree before an improvement becomes money in your hand.
| Step | Who decides | Their authority | Meets how often | Papers deadline |
|---|---|---|---|---|
| Counted in the measure | ||||
| Verified | ||||
| Approved for payment |
Then apply the chapter's arithmetic. Each layer that sits on a quarterly cycle costs a mean 59.7 days — 45.7 days of waiting plus about 14 for the papers deadline. Add them up. That total is the real lag between the work and the payment, and most people in a gainshare have never computed it.
Exercise 2.2 — The period trap (45 minutes)
Take one improvement you expect to deliver. Work out which measurement period it will land in, given the verification lag. Then work out what happens if it slips by four weeks.
In many schemes the answer is that it moves a whole period — sometimes across a baseline reset, which can mean it is absorbed into the new baseline and counts for nothing while permanently raising the bar you are measured against. That is the single most expensive thing that can happen to a gainshare employee and it is entirely avoidable by counting backwards from the period end.
Write the date by which the work must be verified. Put it in the team's calendar as the deadline, not the aspiration.
Exercise 2.3 — Value the classification, in money (1 hour)
Take one uncounted improvement from Exercise 1.2 and compute what it would pay if it were counted:
annual value of the improvement
x the scheme's share percentage
x your allocation basis
= what the classification is worth to you personally, per yearDo the same for the team. This is the number that makes the conversation concrete, and concrete is the register in which schemes get amended. A request to be treated fairly is a mood. A request to add a sub-measure worth a stated figure, under a named paragraph, is an application.
PART THREE — DESIGN
Days 46–70: make the uncounted countable
Exercise 3.1 — Start the data series now (2 hours, then weekly)
The most common reason something is not counted is that no one has ever recorded it. A measure cannot be added to a scheme without a series to measure, and a series takes time to exist. Start it before you ask for anything.
Record weekly, in the simplest possible form: date, the quantity, the method by which it was obtained, and who recorded it. Four weeks of honest data is enough to propose from. A year of it is unanswerable.
Exercise 3.2 — Write the one-page application (3 hours)
Not a complaint. An application, in the chapter's shape.
- Recital. "Under paragraph [n] of the Scheme Rules, adopted [date]…"
- What this is an instance of. One sentence.
- The baseline. Your four weeks of data, with the method and the dates, and a request that it be agreed and signed before anything changes.
- The proposed measure. The formula, written out, with inclusions and exclusions stated. Write the exclusions yourself; proposing your own limits is what makes the rest credible.
- Verification. Who checks and on what cycle. Offer the scheme's existing verifier — you are trying to fit inside the machinery, not beside it.
- The review gate. Named body, named date, and a threshold at which it is treated as working.
- The exit. A sunset: if it does not hold up over two periods, it lapses automatically. Nothing buys agreement like a cheap exit.
Exercise 3.3 — The counter-reading (1 hour)
Write out, in 300 words, the strongest case against your own proposal from the scheme administrator's side: that it adds administrative burden, that it opens a precedent other teams will invoke, that the data is self-reported. Then answer each in one sentence in your own document, before anyone raises them.
A proposal that has already answered the objections is a proposal that can be approved in one meeting rather than three, and the chapter's arithmetic says each extra meeting costs about sixty days.
PART FOUR — DESTINY AND DELIGHT
Days 71–90: make it hold
Exercise 4.1 — Get it written into the rules, not the email (1 hour)
An agreement that lives in a manager's inbox lasts until that manager moves. Ask for the amendment to be recorded in the scheme document, with a version number and a date. One sentence in the governing document outlives any number of reassurances.
Exercise 4.2 — Name roles, diary the reviews (45 minutes)
Check that the amendment names roles rather than people. Then diary the scheme's own review date and the baseline reset date. Be in the room for both. A baseline reset decided without you is the quiet way a good scheme becomes a treadmill: every improvement you make raises the bar you are next measured against, and nobody ever decided that should happen.
Exercise 4.3 — Pass it on (2 hours)
Teach the delegation ladder and the period trap to one colleague in another team, with their numbers. Two things follow. Their scheme gets better, which costs you nothing. And you acquire a second person who understands the machinery, which is how a practice survives you leaving — one person is a hobby, two is a practice.
The delight. There is a specific satisfaction in a gainshare that has become legible: being able to point at the line where what you did shows up, in both directions, in a good period and a bad one. That legibility is worth more than a percentage point of share, because it is what makes the thing feel like a share rather than a bonus. Ask your team directly, once a quarter: can you point to the line? If they cannot, the scheme is not yet delivering its main benefit, whatever it is paying.
KNOW YOUR MACHINERY — A CHECKLIST
Work through it once. Keep the answers.
| Answer | Paragraph / source | |
|---|---|---|
| Scheme rules — current version and date | ||
| The measure, as a formula | ||
| Inclusions and exclusions | ||
| Baseline value, date, and reset schedule | ||
| Measurement period and cut-off date | ||
| Verification lag, in days | ||
| Who may amend the measure, and alone? | ||
| The paragraph covering adjustments or new sub-measures | ||
| Approval layers between result and payment | ||
| Mean days per layer | ||
| Dispute process | ||
| Scheme review date |
Any blank row is a question worth asking, and asking it in writing, calmly, as a request for clarity rather than a challenge, is how a scheme improves without anyone losing face.
THE CONVERSATION, SCRIPTED
The order matters, and it is the same order the chapter gives the practitioner facing a procurement department: category, then number, then proposal.
"I've been reading the scheme rules, and paragraph 9 allows sub-measures to be added by agreement. There's something we do that isn't currently captured — I've been recording it for four weeks, and here's the series and the method. On these figures it's worth about £X a year. I've drafted a one-page proposal: the measure, the exclusions, your existing verifier, a review gate in April and an automatic sunset if it doesn't hold over two periods. Can I leave it with you?"
Note what it does not contain. No grievance. No comparison to another employer. No argument about fairness in the abstract. You arrive with a paragraph, a baseline and a proposal — which is precisely what the executive in the parallel workbook is being taught to arrive with at a procurement department.
That is not a coincidence. It is the point of the whole volume: the practitioner and the institution are not operating different economics, only different vocabularies. The person who can speak both is the one things move for.
WHEN THE ANSWER IS NO
It will sometimes be no, and three of those noes are real.
The scheme has no amendment power at all. Some do not. Then the route is the next scheme review, and your four weeks of data becomes four quarters, and you arrive at the review as the only person in the room with evidence.
The improvement genuinely belongs to another team's measure. Then the proposal is a joint one, and a shared sub-measure agreed between two teams is harder to refuse than either alone.
The value is real but lands in year six. The chapter's arithmetic applies to you too: discounted and multiplied by the chance the scheme still exists, a long-horizon gain is worth a fraction of its face value to whoever decides. Shorten the horizon of the claim — find the part of it that shows up this year, claim that, and let the rest arrive as evidence.
APPRECIATIVE QUESTIONS FOR YOUR TEAM
- When has something we did been counted that we did not expect to be? Who worked out how to classify it?
- What do we do here that visibly creates value and appears in no measure?
- Which paragraph of our scheme rules has nobody in this team ever read?
- What would we try if we knew the baseline were fixed for three years?
- Who administers our scheme, and has anyone ever asked them what they would improve about it?
- If every person here could point to the line where their work shows up, what would change about how we work?
- What is the smallest thing we could start recording this month that we would be glad to have a year of data on?
- Where have we improved a number by drawing down something we will need later, and how would we know?
- What is the real lag between our work and our payment, and what would it be worth to halve it?
- Which improvement have we not attempted because it would land in the wrong period?
- What is already working about how gains are shared here, and what makes it work?
- What would we want a person joining this team in three years to inherit from what we learn this quarter?