In partnership with
Read time: 4.3 min.
TOGETHER WITH OYSTER
Still setting up entities in every country you hire?
What’s changing in how companies expand globally?
Hiring internationally used to mean opening entities, navigating months of legal setup, and building local infrastructure before making a single hire.
That model is starting to shift.
More companies are using EOR not just as a temporary solution, but as a strategic way to access talent faster, test new markets with less risk, and scale globally without adding operational complexity too early.
But the biggest change may not be the hiring model itself. It’s how companies think about expansion.
Instead of building infrastructure first and hiring second, many teams are now hiring where the best talent already exists — and building strategy around that reality.
Oyster’s Strategic EOR Whitepaper explores how modern companies are using EOR to scale internationally, where the model works best, and why the global expansion playbook is evolving faster than most leaders realize.
{{First Name | My friend}},
She had seen this request before.
The request came from a longtime relationship borrower with a solid track record. A regional manufacturing company navigating a time-sensitive facility renewal, the outcome of which would determine their capital position heading into the next fiscal year. The exception fell just outside the standard approval threshold. It was the kind of request that, in her experience, was exactly what exceptions were designed for.
She knew the borrower. She knew the market. And she knew, with the quiet confidence that comes from two decades of reading credit risk in this community, that the answer was “yes.”
What she didn't know was whether she was still the one who got to say it.
She was the Chief Risk Officer of a community bank in the midst of a merger. The bank had deep roots, meaningful scale, and a risk function she had built relationship by relationship over twenty years. Six months into the integration, her title was the same. Her responsibilities were the same. But something about the authority underneath those responsibilities had shifted in ways nobody had quite named yet.
The integration that looked clean
From the outside, the merger was progressing exactly as planned.
The core systems were compatible. The cultures were cordial. Leadership from both institutions was communicating with genuine goodwill. The conversion timeline was on track, and the combined organization's early performance metrics were encouraging.
If you had looked at the integration dashboard on the day that exception request landed on her desk, everything would have appeared to be moving cleanly.
But dashboards don't show the decision layer.
What the systems couldn't capture was the informal authority structure that had governed risk decisions at her bank for decades. That structure wasn't written down anywhere. It lived in relationships, in track records, and in the institutional memory of leaders who knew exactly how far their authority reached because they had built it themselves, over time, through thousands of decisions made well.
The merger hadn't dismantled that structure. It had simply placed a second one on top of it.
And nobody had resolved which one governed.
The exception that nobody could approve
She routed the request the way she always had and immediately felt the difference.
The acquiring institution had its own approval thresholds, its own escalation requirements, its own risk rating methodology built for a different portfolio in a different market. The acquiring institution's framework was legitimate. It was built deliberately, tested over time, and designed to govern risk at scale.
But it had been built without the context of this community, this borrower, or this institution's way of reading risk.
The exception didn't fit cleanly inside that framework.
It wasn't clearly above her authority. It wasn't clearly within it either. So it moved upward through a process that wasn't designed for a borrower it had never met, in a market it was still learning to read.
Two days became two weeks.
The facility renewal was time-sensitive. The borrower's capital planning window was closing. And the relationship banker who had managed this account for twenty years absorbed every day of that delay personally. He had shepherded this borrower through three credit cycles. He knew things about their business that no risk rating model would ever surface.
The institution had learned, over time, to trust that knowledge because it had proven itself across decades of sound decisions.
In the new system, that weight had no place to land.
It had never been confirmed, never been translated into the kind of formal standing that the new governance framework could recognize and act on. A form of institutional knowledge that had taken twenty years to build was sitting quietly outside the decision process, while the exception waited for an answer from people who had never met the borrower and a relationship quietly absorbed a cost it was never meant to carry.
What was actually happening
When the exception finally moved, something became visible that the integration dashboard had been obscuring.
This wasn't a process problem. It wasn't a communication gap. It wasn't a technology issue either. The systems were running smoothly, and everyone knew it.
What the smooth surface had been masking was something structural.
There were two authority systems operating simultaneously inside this integration.
One was documented, formal, and built for scale. The other was informal, relationship-based, and carrying decades of institutional knowledge that the formal system didn't yet know how to hold.
Neither system was wrong.
Neither was sufficient on its own.
And every decision that fell into the gap between them would take longer than it should. The organization had simply not yet answered the question that would let its leaders move.
Who holds authority here?
Under which conditions?
And when the two systems produce different answers, which one governs?
That is not a question the acquiring institution's governance framework can answer unilaterally. Importing one institution's decision architecture into another doesn't resolve the gap. It relocates it. The informal authority structures that made the acquired bank effective don't disappear when a new framework arrives.
They go underground.
And decisions that once moved cleanly start moving differently, in ways that are harder to see and harder to name.
The CRO understood this. So did the relationship banker. What neither of them had yet was a system that understood it too.
The integration looked clean.
The decision layer told a different story.
What this means beyond the merger
A merger makes the authority question unavoidable. But the question itself is not unique to mergers.
Any time two teams share a decision, any time a reorg shifts accountability without redefining authority, any time a new leader inherits a portfolio of informal agreements they weren't part of building, the same dynamic is present. Two systems running simultaneously. One visible, one not. And the gap between them showing up as friction that feels operational but begins somewhere else entirely.
The connective tissue between the integration dashboard that showed everything running smoothly and the facility renewal that took two weeks longer than it should have runs through the decision layer. It’s where formal governance and informal authority either get reconciled explicitly or get left to collide quietly in every high-stakes decision that follows.
The question worth sitting with, in a merger, in a reorg, or in the ordinary complexity of a leadership team navigating interdependent decisions, is this.
Where in your organization are informal authority structures and formal ones running alongside each other without resolution? And who is absorbing the cost of that gap right now?
Until Next Sunday,
Shawnette Rochelle, MBA, PCC
Founder, Excellence Unbounded
Decision Architecture for Executive Teams
If you’re curious to learn more about my work with executive teams, you can find it here.
If you want to have a conversation to learn more, schedule it here.
