How centres earn their next charter

We mapped the leadership behaviours behind charter expansion across the centres we work with, and the clearest pattern was the simplest one. The parent hands more ownership to the centre it has quietly stopped auditing, because that centre stopped needing to be checked. Trust is the currency here, and it’s earned in the unglamorous act of being reliably right when nobody is looking over your shoulder.

Delivery metrics get a centre in the door. They rarely expand the mandate on their own. What expands it is a parent that has learned it can hand this centre a harder, fuzzier problem and not lie awake about it. A charter grant is a decision about where to place a bet, and the parent bets on the centre it no longer feels it has to supervise.

From the parent’s side of the table, the calculation is about downside. Handing a centre a bigger charter means putting a piece of the enterprise’s actual work, a product line, a risk function, an architecture decision that reaches customers, somewhere the head office can’t watch day to day. The question underneath every expansion is “can I stop worrying about whether they deliver?” Centres that keep earning charters have made the answer obvious long before the conversation happens.

When a parent weighs a harder charter, the quiet question underneath is who actually catches this if it goes sideways. A centre with one strong head and a thin layer beneath is a bet on a single person and that person’s calendar. A centre with a real senior bench is a bet on an organisation. The second is far easier to say yes to, and the centres that keep winning charters understood this early. They built layer two before the ask.

Those centres made trust the obvious call by having the depth in place that made a bigger mandate look survivable. When the parent looked for the failure mode, there wasn’t an obvious one, because the capability didn’t rest on any one desk. In roughly 4 out of 5 of the expansions we studied, that second layer was already staffed and ramped before the new charter was named.

The reason early matters is that senior hiring is slow, and it’s slowest exactly when you’re in a hurry. A leader with a clear enough read on where the charter is heading has time to find the right people, assess them properly, and let them ramp. A leader scrambling to staff a mandate they’ve just been handed is buying under pressure, in a thin market, against a clock. A genuinely senior GCC hire can take several months from open to fully ramped, and that time is either spent ahead of need or lost in the middle of it. The bench built early is steadier and better than the bench built in a panic. It just costs attention before the payoff is visible.

Across the handovers we studied, the leaders who kept earning charters shared a short list of habits. They surfaced bad news early instead of managing it quietly. They made calls the parent would have made the same way, without being asked to. They built the bench deep enough that the centre’s capability didn’t depend on any single person. And they spoke the parent’s strategic language, not only the centre’s operational one. All of them are the signals a parent reads when deciding whether a centre can hold more of the enterprise’s real problems, and none is throughput.

The habit that carries the most weight is the first one. A leader who brings a problem forward before the parent finds it teaches the parent that nothing is being hidden, which is the exact condition under which supervision starts to relax. The leader who quietly absorbs a slip and hopes it resolves is doing the opposite, whatever the delivery dashboard says. Trust is built by being the person who names problems first.

The frame that ties the habits together is that these leaders staff and act toward the centre they intend to become. Sometimes that means hiring a person the current scope doesn’t fully justify, a deliberate bet on where the charter is heading. It reads as over-hiring right up until the harder work lands, at which point it reads as foresight. The bench comes first, the mandate follows, and the centre grows into a depth it already has instead of promising a depth it’s still trying to hire.

Charter expansions aren’t bolts from the blue. They’re preceded by a fairly consistent set of signals, and the centres that watch for them can tell when a bigger mandate is coming into range. The parent starts routing ambiguous problems to the centre rather than fully specified ones. Review cadences lengthen because the parent no longer feels it needs weekly proof. The centre’s head gets pulled into conversations about strategy rather than status. And the parent begins referencing the centre’s judgment, not just its output, when it explains decisions upward.

Each of those is the parent testing the water. A fuzzy problem handed over is a small, low-stakes charter in disguise, a way to see whether the centre can own something without a spec. A lengthened review cadence is trust being extended a little further than before. Leaders who read these signals lean into them: they take the ambiguous problem and return a clean answer, they use the longer leash to show initiative rather than to coast, they show up to the strategy conversation with a point of view. The signals are an invitation to demonstrate readiness, and the readiness has to be real when the invitation arrives.

The through-line is that charter expansion is retrospective. By the time the parent grants the bigger mandate, the leader has already been behaving as though they held it, taking responsibility they weren’t formally given, thinking about problems above their pay grade, treating the centre as a business rather than a cost line. The grant is the parent catching up to a reality the leader created.

Which means the centres that plateau are usually waiting for permission that only arrives after you’ve stopped waiting for it. Ownership is demonstrated first and ratified later. The leader who builds the bench, surfaces the bad news, and answers the fuzzy problem well makes the bigger charter the natural next step, and the natural next step is the one parents take.

For a CHRO or a GCC sponsor, the practical read is to treat charter expansion as an outcome you build toward. Fund the second layer before the scope formally justifies it. Reward the leader who brings problems forward, alongside the one who hits the dashboard. Watch for the signals the parent is already sending, and make sure the readiness behind them is real. The centre that does this becomes the obvious place to put the next charter.