The Real Question Behind the Question

When someone asks how I keep teams aligned across borders, what they’re usually asking is something deeper. They want to know how you maintain standards, communicate priorities, and ensure follow-through when your operations span New York, Israel, Italy, and multiple cities in Africa. The short answer is that alignment isn’t about holding more meetings or writing longer memos. It’s about clarity, repetition, and creating systems that make misalignment obvious before it becomes expensive.

I learned early on that distance amplifies every small gap in understanding. A vague directive in a single-location project becomes a disaster when execution happens six time zones away. The fix isn’t micromanagement. It’s being relentlessly clear about what matters and why.

Start With What Doesn’t Change

Every project has variables: budget shifts, regulatory changes, unforeseen site conditions. But the principles guiding the work should remain constant. I make sure every team member, regardless of location, understands the non-negotiables. Quality benchmarks. Safety protocols. Deadline structures. Reporting cadence.

These aren’t just policies. They’re the shared language that lets a crew in one country and a planning team in another stay coordinated without constant intervention. When everyone knows what won’t bend, they can make smarter decisions about what can.

Over-Communicate the Why, Not Just the What

I’ve seen projects stall because teams executed instructions perfectly but missed the intent behind them. If I tell a team to adjust a timeline, they need to know whether it’s because of a financing milestone, a regulatory approval window, or a partner commitment. Context determines how they prioritize the dozen other things competing for attention that week.

I don’t assume that sending information once means it landed. I repeat key points in different formats: written briefs, calls, site visits. Repetition isn’t about distrust. It’s about fighting the noise that comes with complex, multi-location work.

Build Feedback Loops That Actually Close

Alignment breaks down when information flows one direction. I need to know what’s happening on the ground, not just what’s in the weekly report. I ask specific questions: What took longer than expected? What assumption turned out wrong? What would you do differently if you started this phase again?

The goal isn’t to catch mistakes. It’s to surface the real conditions teams are working under so I can adjust plans or provide support before small issues compound. Teams that know their input shapes decisions are far more forthcoming than teams that feel like they’re just checking boxes.

Use Local Leadership, But Stay Close Enough

I rely on strong local leaders who understand the regulatory environment, the labor market, and the cultural expectations in their region. They’re not just executors. They’re decision-makers within a defined scope. But I don’t delegate and disappear.

I stay involved enough to understand the pressures they’re under and the trade-offs they’re navigating. That proximity lets me support them without undermining their authority. It also keeps me from being blindsided when a situation escalates.

Create Visibility Without Creating Bureaucracy

Alignment requires transparency, but not every team needs to see every detail. I structure reporting so people get the information relevant to their role: financial teams see cost tracking, site teams see scheduling and logistics, permitting teams see regulatory timelines.

What everyone does see is progress toward shared milestones. When a delay in one location affects another, both teams know immediately. Visibility prevents silos, and it makes accountability easier because no one is operating in the dark.

Expect Friction, and Address It Early

Teams in different countries will sometimes have competing priorities. A financing timeline might conflict with a construction sequence. A permitting delay in one jurisdiction might create downstream pressure in another. I don’t treat friction as failure. It’s a signal that priorities need to be re-ranked or resources need to shift.

The mistake is letting friction simmer. I address conflicts directly, with the relevant people in the room (or on the call), and we solve it with the project’s overall goals in view. Quick resolution prevents resentment and keeps everyone focused on the work.

The Unglamorous Truth

Keeping teams aligned across borders isn’t about charisma or inspiration. It’s about clarity, consistency, and creating systems that make coordination easier than confusion. It’s repeating yourself more than feels necessary. It’s staying close enough to understand ground truth without stepping on the people you’ve trusted to lead.

The question I get asked is how to keep teams aligned. The answer is that you never finish aligning them. You just build the habits that make alignment the default, and you reinforce them until they’re automatic.