Operations
By Jason Kumpf · April 23, 2026
When a multinational stumbles, the post-mortem usually blames strategy. More often the strategy was fine. What broke was coordination. The unglamorous work of getting many teams, in many places, to move in the same direction at the same time.
Every border a company operates across adds a layer: a time zone, a language, a regulation, a local incentive that quietly competes with the global plan. None is fatal alone. Together they turn a clear strategy into a dozen local interpretations.
The companies that operate well globally are deliberate about what must be identical everywhere. Standards, data, the few non-negotiables. And what should flex to local reality. Confusing the two creates either rigidity that frustrates local teams or chaos that no one can manage.
When every region reports differently, leadership flies blind. Shared definitions and a single view of the numbers are not bureaucracy; they are what makes coordinated action possible at all.
The hardest part of running operations across countries is not distance. It is time. When your teams are awake at different hours, the easy habit of solving things in a quick hallway conversation disappears. The companies that run smoothly replace that with rhythm. They decide what has to happen synchronously, in real meetings where everyone is present, and what can happen asynchronously, where one team finishes a piece and hands it cleanly to the next. Most work, it turns out, does not need everyone in the room at once. It needs a clear baton pass.
Done well, time zones stop being a problem and start being an advantage. Work can move around the clock, with a team in one region picking up where another left off, so progress never fully stops. That only happens when the handoffs are deliberate and the expectations are written down. Set a small number of fixed moments when the whole operation syncs, protect them, and let everything else run on clear written handoffs. A global operation that masters its own rhythm gets the benefit of the sun never setting on the work.
Most operational friction lives in the gaps between teams, not inside them. A task is done well, then passed along with half the context missing, and the receiving team spends an hour reconstructing what the first team already knew. Multiply that across a global operation and the lost time is enormous. The fix is to treat the handoff itself as part of the work, not an afterthought. A good handoff says what was done, what is left, what to watch for, and who to ask. It takes a few minutes to write and saves hours downstream.
The best operators design their handoffs once and then make them routine. A simple shared template, used every time, removes the guesswork and the dropped details. People stop having to remember what to include because the format remembers for them. Over time this turns into one of the quiet superpowers of a smooth operation. Work moves between teams and across borders without losing its thread, and nobody has to chase down the missing piece.
Every operation has a layer of work that is necessary, repetitive, and a poor use of human attention. Pulling the same report each morning, reconciling two systems that should already agree, copying data from one place to another. This is exactly the work that modern automation and AI tools are good at. Handing it over does two things at once. It removes a steady source of small errors, and it gives your people back the hours they were spending on tasks that never required their judgment.
The goal is not to replace the people who run the operation. It is to aim their talent at the parts that actually need a human, the exceptions, the judgment calls, the relationships. Let the software handle the predictable middle, and let your team handle the edges where experience matters. Operations that adopt this balance tend to feel calmer even as they grow, because the volume that used to require more hands now requires better tools and the same sharp people.
It is natural to measure operations by how much gets done. A smoother operation also measures how the work flows. How long does a typical request take from start to finish. Where does it sit and wait. Which step is the bottleneck this month. Those questions reveal the things a simple output number hides. Two teams can produce the same volume while one is calm and the other is constantly firefighting, and the difference shows up in flow long before it shows up anywhere else.
Watching flow gives a leader somewhere useful to act. When you can see where work piles up, you can fix the actual constraint instead of pushing everyone to try harder everywhere. Often a single well-chosen improvement at the bottleneck speeds up the whole system. That is the quiet art of operations. Find the one place that is slowing everything down, clear it, and watch the entire flow improve without anyone working longer hours.
Behind every smooth operation is a group of people who quietly make the connections work. They know who to call, where the bodies are buried in the process, and how to keep a promise to a customer when something unexpected happens. These operators are easy to overlook because their best work is invisible. When they do their jobs well, nothing goes wrong, and it is tempting to assume nothing was at risk. The strongest companies know better and invest in them accordingly.
That investment is partly training and tools, and partly trust. Give operators the authority to fix problems without asking permission for every small thing, and they will solve issues before customers ever notice. Connect the people who run operations in different regions so they learn from each other instead of each reinventing the same solutions. A global operation is, in the end, a network of capable people who trust one another. Strengthen that network and the whole thing runs better.
An operation tuned only for speed can be fragile. The smoothest ones are also built to bend without breaking. That means having a second person who knows each critical task, a clear plan for the days when something goes wrong, and enough slack in the system to absorb a surprise without a scramble. Resilience is not waste. It is what lets an operation keep its promises on the day that does not go to plan, and those days always come.
Building it in is mostly a matter of foresight. Ask where a single point of failure sits, and remove it before it matters. Write down how to handle the common emergencies so nobody has to invent a response under pressure. The companies that do this look lucky from the outside. They rarely have dramatic breakdowns. In reality they simply prepared, and that preparation is one of the clearest signs of an operation that is built to grow.
A global operation generates an enormous amount of information, and most of it ends up somewhere. The question that separates smooth operations from chaotic ones is whether anyone can find it later. Knowledge that lives only in one person's head, or buried in a thread nobody can search, may as well not exist when a teammate in another country needs it at two in the morning. The smoothest operations treat findable information as a core asset. They write things down in places others can reach, and they keep those places tidy enough to trust.
This does not require a heavy system. It requires a habit. When a recurring question gets answered, capture the answer where the next person will look. When a process changes, update the one document everyone relies on rather than emailing a few people. A little discipline here compounds quietly. Six months on, new team members get up to speed faster, the small mistakes that come from missing context fade, and the operation stops depending on a handful of people being awake to answer the same questions again and again.
It is easy, inside a busy operation spread across regions, to lose sight of the person at the end of it all. Work becomes tickets and tasks and handoffs, and the customer quietly turns into an abstraction. The strongest operations resist that drift on purpose. They keep the customer's experience visible at every step, so that everyone, no matter how far from the front line, can see how their piece affects the person being served. That shared view is what keeps a global team pulling in the same direction.
Simple practices do the job. Share real customer stories across the whole operation, the good ones and the instructive ones. Let the people who never speak to customers see the difference their work makes. When a team in one country understands how a clean handoff lands for a customer on the other side of the world, they make better choices without being told. A customer kept visible is the simplest alignment tool a global operation has.
Smooth global operations are not the product of one clever system. They come from a handful of habits practiced everywhere. Standardize the core and adapt the edges. Keep one source of truth. Pass clean handoffs, automate the routine, watch the flow, and build in enough resilience to handle a hard day. Most of all, invest in the people and the shared understanding that hold it together. None of it is flashy. Together it is what lets a company operate across many countries and still feel like one team, and that smooth foundation is exactly what makes confident growth possible.
Process is essential, but it has a limit. No playbook can anticipate every situation a global operation will meet, and the gaps are exactly where trust earns its keep. When people across regions trust each other, they fill those gaps with good judgment instead of waiting for a rule. They give a colleague the benefit of the doubt, pick up a loose end without being asked, and assume the best when a message arrives terse at the end of someone's long day. That trust is the lubricant that lets a documented process actually flow.
Trust between distant teams is built on purpose. A little face time, even over video, goes a long way. So does giving people the chance to deliver for one another and see it returned. The leaders who invest in those connections find that their operation needs fewer rules, not more, because people who trust each other coordinate naturally. Process sets the floor. Trust is what raises the ceiling.
None of this has to happen all at once. The encouraging truth about operations is that small, steady improvements compound. Tidy one source of truth this month. Standardize one handoff next month. Automate one repetitive task after that. Each change is modest on its own, and together they turn a stretched operation into a smooth one over a single year. The companies that run beautifully across borders did not get there through one grand reorganization. They got there by improving one thing at a time and never stopping.
Strategy gets the headlines, but coordination wins or loses the quarter. Invest in the connective tissue, and a good plan finally has a chance to ship.
Jason Kumpf has learned that global operations succeed on coordination as much as strategy. He is Head of US Revenue at Razorpay, a board advisor, angel investor, and speaker. More about Jason.