Still Being Defined Is Not Modesty

A colleague a year or so into the business asked us: when will the Glacier Model be final? Our answer was four words: it is still growing.

Let me state the view up front. The name can be finalised later; the method has to grow every day. Why? Because a methodology is never something written on paper first and then taken away to be executed. It is run on the front line first, then distilled, then named. The part written on paper is always a little less than the part that was run.

Look first at how the ones before us answered. Toyota's lean production (TPS), Motorola's Six Sigma, Intel's OKRs, Haier's Rendanheyi, Amazon's flywheel. Five names across half a century, with only one thing in common: none of them was a concept invented out of thin air; each was an answer forced out by new tools. Better tools of production always change the relations of production. Now it is the AI generation's turn, and the name in that slot is still empty. We are filling it with one: the Glacier Model (Orchestrator Model), meaning people working with AI and the organisation doing the orchestrating. Three words hang off the end of the name: still being defined.

A Name Is a Coordinate, Not a Label

Naming something is setting yourself a coordinate in history. Once the coordinate stands there, every later choice has to answer one question: is this worthy of the name. A slogan stuck on the wall does not do that. A label is only stuck on; a coordinate is a ruler. In other words, the weight of a name is not in the day it is announced but in the days it is quoted again and again. So is "still being defined" a form of stalling? No. It hands the right of acceptance away. But handing it away carries interest: until the thing has grown, we have no slogan to use. So we are in no hurry to declare it finished.

So What Makes It Grow? Projects Feed It

While a methodology sits in a few people's heads, it is only personal ability. There is one way to make it the organisation's: put it through real transactions over and over. Glacier Capital does twenty to thirty mandates a year, half of them new and half of them existing clients coming back for the next round — and that volume is both capacity and training ground. Too few projects and the method decays into legend. Too many and attention is thinned out, and accompaniment decays into brokerage. But between those two ends there is no formula to copy. You can only calibrate it year by year.

Colleagues one or two years in can follow three to five projects through a full cycle. At sixty days and eight checkpoints a mandate, that is twenty-odd gates passed by his own hand in two years. The denominator is his own two years, not somebody else's experience. Not hearsay — handled. Which is why we often say the organisation is an amplifier of method.

Boundaries Only Grow

We reviewed the last few projects and found that what we had used was in fact the same set of moves. Luck on a single case becomes capability for the organisation only after a review. The plainest component of the Glacier Model is the subtract-only list (Stop Doing List): whatever may no longer be done, written down as a prohibition and reread by everyone at every review. In the meeting, evidence first, conclusion second. Methods can iterate; boundaries only grow.

So why set the subtraction first? Because addition can be trial and error, while subtraction is bought with a price. Behind every prohibition is a bill already paid. But the list has a price of its own: it slows people down, and it blocks some approaches that might have worked. That price is worth paying. A little slower loses nothing.

When does "still being defined" come off? When it has grown, it will come off by itself. Until then we do not intend to package it as a slogan — its most honest state right now is exactly that: still being defined.

(For the eighth-anniversary two forms and the organisational method, see the Archive entry "Eighth Anniversary: The Two Core Forms".)