Haute Lumière
Commerce · VI.11 · MMXXVI · daylight
WORKBOOK — THE LUMINOUS GAINSHARE EMPLOYEE
Chapter VI.11 · The Limits of Self-Governance
For the person working inside a gainshare arrangement — where a defined share of verified improvement returns to the people who created it. This chapter is about where self-governance runs out. A gainshare pool is a commons, it has a boundary, and this workbook is about reading that boundary from the inside: what to measure, what to claim, and what to ask for.
YOUR SCHEME IS A COMMONS, AND IT HAS A BOUNDARY
A gainshare has four parts: a baseline, a measure, a share, and a period with a verifier. Chapter I.01 showed those are the same four parts as a regeneration facility. This chapter adds the fifth part nobody writes down.
A gainshare pool has a boundary, and the boundary decides who the scheme can see. Everyone inside it is a member of a commons: you share a resource — the pool — that your collective behaviour creates and can deplete. Everyone outside it is affected by your decisions and has no vote in them.
Write your boundary out now, honestly, in two columns.
| In the pool | Affected by the pool, not in it |
|---|---|
The right column is almost always longer than people expect. Agency staff and contractors doing the same work. The night shift, if the measure is a day-shift measure. The site that joined after the baseline was set. The next cohort, who will inherit a ratcheted baseline. The team downstream whose numbers get worse when yours get better. Maintenance, if you optimise throughput. Safety, if you optimise anything.
None of this is a reason to be uneasy about the scheme. It is the reason the scheme needs a floor, and the floor is the thing worth asking for.
PART ONE — DISCOVERY
Days 1–30: read the mechanism from inside
Exercise 1.1 — The five questions, in writing (2 hours)
Take your scheme document and answer these, on paper:
- What exactly is the baseline, and when was it set?
- What is the measure, as a formula?
- What is the share, and is it of gross improvement or net of costs?
- Who verifies, and when?
- What happens to the baseline when a gain is realised?
Question five is the one that decides whether the scheme is worth being in. If the baseline resets to the improved level each period, you are on a treadmill. Every gain raises the bar you are next measured against, so the same effort yields less each cycle and eventually nothing. A well-designed scheme holds the baseline for a stated term — three to five years is typical — or ratchets on a published, gradual schedule everyone can see coming.
And here is the connection to this chapter. In governance terms, a baseline ratchet is the floor being lowered by amendment. The chapter names it as the commonest failure of any chartered self-governing body, and says why it is hard to catch: it never feels like dishonesty from the inside; it feels like clarifying a definition. Your scheme's baseline is your floor. Find out how hard it is to move, and who has to be told when it moves.
Exercise 1.2 — Find the gain that is not counted (one week)
You can see things the scheme's designers could not. Walk the five places:
| The formal place | What you actually see |
|---|---|
| Waste | What leaves that somebody would pay for |
| Retention | Why people stay or go — the real reasons |
| Assets past schedule | The machine or system that works because somebody tends it |
| Suppliers | Who picks up the phone at six, and who does not |
| Quiet pride | What your team would defend if somebody tried to cut it |
You are looking for an uncounted gain, because an uncounted gain is an unshared gain, and making it countable is the highest-leverage thing available to you inside a scheme.
Exercise 1.3 — The appreciative conversation (45 minutes, with your team)
"Think of a time here when something went unusually well. Not the biggest win — the one that surprised you. What were the conditions? What did we do that we do not normally do?"
Notes on conditions, not outcomes. Repeatable causes are exactly what a gainshare pays for.
PART TWO — THE ARITHMETIC
Days 31–45: compute your scheme's three thresholds
Exercise 2.1 — Does peer accountability still work here?
A gainshare relies on peer pressure: the pool is shared, so a free rider costs everybody a little and is expected to feel it. That mechanism has a ceiling.
n* = D × (S_max / g) D = 150g is what a member gains by coasting for a period — their share of the pool is barely affected, so put a value on the effort saved. S_max is what full disapproval costs somebody fully embedded in this workplace.
At the chapter's parameters the ceiling is 450. Count your pool. If your pool is larger than your n*, peer accountability is not doing the work somebody assumed it was doing, and the scheme needs either a smaller pool unit or an explicit measure that attributes contribution — and it needs it before the first serious dispute, not after.
This is also the honest argument for team-level sub-pools, and it is a better one than the usual fairness argument, because it has a number in it.
Exercise 2.2 — Is the scheme's clock fast enough?
T_g ≤ T_d / 2If the thing you are being measured on changes faster than the period over which you are measured, the scheme is measuring noise and paying it out. An annual period on a quarterly variable pays somebody for the weather.
Write the fastest variable in your measure, its turnover time, and your payment period. Any row where the period exceeds half the turnover time is a row you can raise with evidence rather than with a complaint.
Exercise 2.3 — What does your decision rule cost you?
Many schemes have a committee that approves improvement claims, and many of them run on consensus. At thirty members each assenting with probability 0.9, unanimity passes 4.24 percent of proposals — 23.6 tabled to pass one — against the optimum of 29 of 30, which unanimity costs 2.65×.
The thirtieth signature costs more than the whole rest of the decision. If your improvement claims die in committee, that is very often the mechanism, and it is not personal.
Exercise 2.4 — The value you supply, priced
The chapter's charter case: a state warden costs £1.00 a hectare to reach the required detection rate; members monitoring themselves cost £0.55, a 44.7 percent saving with oversight included, and the levy is 5.3 percent of the right it secures.
Your version: what would it cost the firm to obtain by inspection the adherence, care and reporting that this team currently supplies voluntarily? Inspector days, their day rate, and how much ground one covers. The number will be larger than your share of the pool. That is not a grievance. It is your negotiating position, and it is arithmetic rather than sentiment.
PART THREE — DESIGN
Days 46–70: the four things to ask for
Ask for these in this order. Each is small, each is specific, and each maps onto one of the chapter's four reserved powers — held the right way round, so that they protect the scheme rather than constrain you.
3.1 A named floor. The list of things the scheme may not do, however the numbers move. Minimum: the baseline is held for a stated term; safety and maintenance measures are carved out of the improvement calculation; no gain may be booked that moves a cost onto a team outside the pool.
Ask: "Can we write down the three things this scheme will never do, and put them somewhere harder to change than the annual targets?"
3.2 Notice and a hearing before the baseline moves. This is the abrogation power pointed the useful way. A baseline change is announced a period in advance, with the reason, and the pool may be heard on it.
Ask: "If the baseline is going to be reset, can we have it a period ahead with the reason in writing?"
3.3 A voice for the people outside the pool. Somebody in the room whose job is to say and what does this do to nights, to maintenance, to the agency staff. It can be a standing agenda item. It costs nothing and it is the single clause that stops a scheme becoming the thing its critics say it is.
Ask: "Can we add a standing item: who outside this pool is affected by what we just decided?"
3.4 The enforcement count, published. Once a year: how many claims were made, how many verified, how many refused and why. A scheme that refuses nothing is not generous — it is not looking, and the first audit will say so.
Ask: "Can we see the claim and refusal counts for the year?"
PART FOUR — DESTINY AND DELIGHT
Days 71–90: make it hold, and notice what it feels like
4.1 Get it into the standing pack. Anything reviewed on a calendar persists; anything reviewed when somebody remembers does not. One number of yours on the standing agenda is worth more than any presentation you will give.
4.2 Find the second owner. One person is a hobby; two is a practice. Recruit them by giving them the credit for the first result. This is not tactics — it is the only thing in the record that reliably survives the original person moving on.
4.3 Write the honest negative yourself. When you present a gain, present the thing it cost and the confound beside it, in the same document. The chapter does this with Nepal: +11.36 percentage points of forest on one definition, +5.14 on the stricter one, and a remittance effect that moves the same series with no institution involved. It prints all three.
This is the fastest way to become somebody whose numbers are believed, and being believed is the whole currency of a gainshare. A claim with its own caveats attached is checked once. A claim without them is checked every time.
4.4 What it actually feels like. There is a specific relief in a bounded remit — in knowing exactly what is not yours to decide. The floor does not diminish the pool. It takes away the questions the pool was never going to answer well and leaves the part it is genuinely good at: the ground you know, the people you know, the improvement you can see from where you stand.
And there is a quieter pleasure in the standing item about the people outside. After the first year nobody experiences it as adversarial. They notice that the meetings are shorter, that the arguments are about thresholds rather than about who is a good person, and that the scheme is the one nobody outside can call a carve-up.
KNOW YOUR SCHEME — A CHECKLIST
Tick what you can evidence. An unticked box is a question, not a fault.
- I can state the baseline and its date
- I can write the measure as a formula
- I know the share, and whether it is gross or net
- I know who verifies and when
- I know what happens to the baseline when a gain is realised
- I know the size of the pool, and I have computed
n* - I know the fastest variable in the measure and its turnover time
- I can name three people affected by the pool who are not in it
- I know what the scheme may never do, and where that is written
- I know how many claims were refused last year, and why
- I have priced what my team supplies that the firm would otherwise inspect
- I have a second owner for the one number I care most about
The fifth box is the one that decides whether the scheme is worth being in, and the ninth is the one that decides whether it will still be here in five years.
THE CONVERSATION, SCRIPTED
For the meeting where you ask. Short, specific, and with the arithmetic already done.
"I have been reading how our scheme actually works, and I want to bring you three things rather than a complaint.
First, the one that is working: the pool has found ___ this year, and the part I want to protect is ___ , because it is the condition the rest depends on.
Second, a number. Our pool is ___ people. Peer accountability holds to about ___ — that is Dunbar's relationship limit times the ratio of what disapproval costs to what coasting gains. Above it, peer pressure stops doing the work, whatever anybody's intentions are. I think we are [above / below] , and if we are above it the fix is team sub-pools, not more encouragement.
Third, four small asks: a named floor of three things the scheme will never do; a period's notice before the baseline moves; a standing item on who outside the pool is affected; and the claim and refusal counts once a year.
None of those costs anything, and all four are the clauses that make a scheme survive a change of management."
APPRECIATIVE QUESTIONS FOR YOUR TEAM
- When has this team fixed something without being asked, and what made that possible?
- Where has the firm done something for us that we genuinely could not have done ourselves?
- When have we handled a disagreement with another team well, and what did we do that worked?
- If everyone affected by our improvements had a way to be heard, what would we change first?
- What would our scheme's first page say if other sites copied it?
- What is the floor under this scheme — what would we never do for a number?
- At what size does looking out for each other stop working here, and what should we put in its place before then?
- What would have to be true for this scheme to still be running when everyone currently on this shift has moved on?