As companies expand, complexity compounds. Alignment doesn't happen by accident – it needs to be intentionally designed.

Recently, in partnership with Humankind, we gathered founders and operators from high-growth New Zealand companies for Leading Through International Growth – a workshop-style session exploring how to scale leadership, align teams, and maintain clarity as businesses expand globally.

In Part 1, we covered the first international hire decision. This blog focuses on the second session: how to build the operating rhythms that keep distributed teams moving in the same direction.

The first thing to break

When asked what breaks first during international expansion, the answer wasn't communication tools or reporting structures. It was alignment of expectations: what success looks like, who owns which decisions, and how teams work together across markets.

Sales teams in new markets push hard to acquire customers. Product teams back home want to build something they're proud of. These tensions exist in any business, but distance and cultural differences amplify them quickly. One tech leader described how their Australian sales team, embedded with a major telco partner, had adopted a way of working that created real friction with their New Zealand-based team. The local context made sense; the downstream impact didn't.

The people and culture work, several founders agreed, is where most companies underinvest – and it's also the hardest to course-correct later. "What I think we would have done earlier is a lot of the people and culture stuff," shared one founder now operating across five countries. "The other things are black and white – you've got the healthcare plan, or you don't. But the people and culture stuff exists on a scale of how much time you can spend on it and how deep you can go."

Building systems for two-way learning

As teams spread across regions, the challenge shifts from individual hires to systemic knowledge sharing. How do you ensure insights from local markets flow back to decision-makers, rather than getting lost in a one-way broadcast from HQ?

One operator shared a framework their company adopted, built around structured experimentation. Each market worked toward a set of quarterly goals. Local teams ran experiments tied to those goals, documented in a standardised way. Failed experiments were expected and valued because the learning was the point. Insights were shared monthly across markets, with successful approaches becoming standard operating practices adopted across the business.

Several founders noted that these systems only worked when leaders reinforced them consistently, setting clear expectations about how decisions should be made and how teams collaborate across markets. As one founder described it: "You're basically a business owner in your own right in this jurisdiction. You've got a toolkit and standard operating procedures, but other than that, go for it."

The identity question

An unexpected tension surfaced in the session: should you lean into your Kiwi identity or present as a global company that happens to be headquartered in New Zealand?

Views differed. One leader has moved to global language across the business – no "out there" when referring to other markets, no casual Kiwi-isms in client communications. Others pushed back. "Being founded in New Zealand gives us curiosity," said one founder as they expanded into New York. "It's a little bit different." In some markets, the New Zealand origin story is an asset. In others, it needs to be held more lightly.

The honest answer is that it depends on your market and strategy. But the ambiguity itself is the risk. Companies that hadn't decided – that were somewhere between proudly Kiwi and quietly global – found it created confusion internally as much as externally. Deciding early and being consistent matter more than which direction you choose.

Centralised or embedded?

As companies mature globally, a structural question often arises: do you keep functions centralised – one global sales leader, one HR team – or do you embed people in each market, creating semi-autonomous regional teams?

There's no universal answer, but one pattern emerged clearly. The shift from centralised to embedded often happens gradually, driven by customer expectations or regulatory requirements rather than a deliberate strategic call. One company moved their technical support team from New Zealand to Australia in response to customer feedback. The impact was measurable – engagement scores lifted, and the team performed better because they understood their customers more deeply. "There's a feeling of 'these are my people,'" the founder explained.

The risk of waiting too long to make that shift is that a centralised structure designed for a single-market business quietly becomes a bottleneck as the company scales. The people doing the work know it before the org chart reflects it.

What this means in practice

The consistent thread across this session wasn't a single framework or model. It was intentional design. The companies that had navigated global expansion well hadn't stumbled into good operating rhythms. They had designed intentionally: writing down how work gets done, creating feedback loops between markets, and giving teams the clarity needed to perform.

The companies that struggled had often delayed the people and culture work, assuming it would sort itself out once the commercial foundations were in place. It rarely did.

Missed Part 1? Read Lessons From Leading Through Global Expansion: Part 1 for key takeaways on making your first international hires.

Leading Through International Growth was hosted in partnership with Humankind. Together, we've also launched Foundations for Going Global: A Talent Playbook – a practical resource giving exceptional Kiwi founders and teams the tools and frameworks to scale internationally with confidence. Download it here.

Connect with Steph here.