"Be More Strategic" Has a Mobility Problem, Too

Somewhere in a global mobility program right now, a VP is telling their team to "be more strategic about the program." The team nods, goes back to their desks, and has no real idea what that means in practice. So they keep doing what they were doing, just with more of the word "strategic" in their next deck.

A recent leadership piece made a point that lands just as hard in mobility as it does anywhere else in the org chart: "strategic" isn't a trait, it's a set of specific, teachable, observable behaviors, and when leaders skip straight to the label without naming the behavior, they don't get more strategic thinking. They get people quietly guessing, performing the vocabulary instead of doing the work. Nobody asks what it means, because asking feels like admitting they should already know.

That's not just a management-training problem. It's the missing piece in the governance conversation we've been having in this space. We've argued that mobility is shifting from move execution to mobility governance. But "govern the program better" is exactly as vague as "be more strategic." It's a direction without a destination. If governance is going to mean anything operationally, it needs the same translation Herd prescribes for managers: which specific behavior are you actually asking for?

Here's what that translation looks like when you take her five behaviors and run them through a mobility lens.

Prioritization becomes policy discipline

In the original framing, this is about picking the two or three things that matter this quarter instead of saying yes to everything. In mobility, it shows up as policy scope creep. A benefit gets added because one executive asked, a lump sum tier gets created for one loud business unit, and three years later nobody remembers why the policy has fourteen exceptions built into its "standard" version.

Being strategic here means being willing to say no to a benefit request that doesn't serve the program's actual priorities, and being able to explain why in one sentence.

Root cause thinking becomes exception pattern analysis

Herd's version: stop solving the same problem over and over without asking why it keeps happening. In mobility, this is the exception log nobody has actually read end-to-end in a year. If the same three types of exception keep getting approved for the same three business units, that stopped being an exception a long time ago. It's an undocumented policy, and pretending otherwise just means the next audit finds it before you do.

This is also where a platform like Point C earns its keep: catching the pattern before it becomes a governance gap disguised as a one-off. It's part of why implementing companies have seen exception spend drop by roughly 10x. Exceptions didn't stop happening. The pattern got surfaced and addressed at the policy level instead of re-approved case by case.

Second-order thinking becomes downstream cost awareness

Solving today's problem in a way that creates three more next month. In mobility, the classic version is capping a benefit to hit this year's budget number without modeling what that cap does to time-to-productivity, to acceptance rates on international assignments, or to the next renewal conversation with the business unit that just lost the benefit. The savings shows up in one line item and the cost shows up in three others, six months later, attributed to something else entirely.

Framing for decision-makers becomes the one-page recommendation

Herd's example translates almost word for word: don't bring leadership five vendor options with no recommendation, bring them your pick and your reasoning. Mobility teams are especially prone to the opposite instinct, because the underlying subject matter (immigration timelines, tax equalization, cost-of-living data) is genuinely complex, and complexity feels like it deserves a full briefing instead of a one-page ask.

It doesn't. The complexity is yours to absorb so leadership doesn't have to sit through it. If a policy recommendation needs six pages of caveats before it gets to the ask, those caveats belong in an appendix. The pitch stays clean.

Connecting to the business becomes connecting to retention and readiness

The last of Herd's five is the one mobility teams most often skip entirely: explaining not just what you did, but why it matters to the things the organization actually cares about. A mobility function that reports moves completed and average cost per relocation is reporting execution. A mobility function that can tie its numbers to offer-acceptance rates, time-to-productivity for critical roles, or retention of relocated talent at the 18-month mark is speaking the same language as the CFO and the CHRO, and that's usually the difference between mobility having a seat at the strategy conversation and mobility finding out about the strategy after the fact.

How does a good policy drift?

There's a related trap worth naming, because it's the one that catches teams even after they've done the work above. A policy document, however well-designed, is a snapshot, a fixed representation of the program drawn under one set of assumptions, at one moment. Snapshots are useful. They're also, by nature, already slightly out of date the moment conditions shift: a new business unit relocates differently than the one the policy was designed around, a tax rule changes, a talent market tightens. That's not a failure of the original policy. It's what happens to any fixed document sitting in a moving environment.

The instinct when a policy stops fitting is to blame execution. The team isn't enforcing it consistently, the exceptions are getting sloppy. Usually the real issue is upstream: nobody built a way to check the policy against current reality on any cadence shorter than "whenever we get around to the next full refresh." Planning happens once and produces a document. Governing well means treating the policy less like a finished map and more like an instrument, something checked against actual conditions regularly enough to catch drift before it becomes the exception sprawl a leadership team eventually has to explain.

That's the throughline connecting all five behaviors above: none of them are one-time fixes. Policy discipline, exception pattern analysis, downstream cost awareness. Each one only holds up if it's revisited on a real cadence. File it away and the next audit forces the issue.

The actual ask

None of this requires a bigger team or a new platform. It requires the same thing Herd is asking managers to do for their direct reports: stop handing down the label and start naming the behavior. If your leadership is asking mobility to "be more strategic," the useful response isn't a new deck with the word "strategic" in the title. It's asking, plainly, which of these five they actually mean, and then building the specific, observable practice that answers it.