I started playing badminton years ago. Nothing serious. Just a couple of times a week with friends, a bit of competition, and an excuse to get off a screen for an hour. But somewhere along the way I noticed something that I couldn't stop thinking about, and it had nothing to do with backhands or serves.
It was about what you couldn't see.
In doubles, the really good pairs don't look like they're trying very hard. They move well, they cover the court, they rarely get in each other's way. From the outside it looks effortless. What you don't see is the hours of unspoken agreement that went into building that. Who takes the left side. Who covers the net. Who goes back when a smash comes. Who calls it when there's doubt.
The game you watch isn't the game that matters. The game that matters is the one that was agreed before anyone picked up a racket.
That's systems. Right there. Not the visible stuff, not the talent on the court. The invisible framework that means two people can operate at pace, under pressure, without stopping to ask each other what to do next.
When it goes wrong
I've seen pairs where both players are strong individually but hopeless together. They both go for the same shot. They both hold back expecting the other one to move. There's a collision, or a gap, or the shuttle just drops between them while they both look at each other.
Sound familiar?
I see this in businesses every week. Two capable people, no clear system, and a gap that nobody owns. Not because they aren't talented. Because nobody sat down and agreed who does what, when, and how. The system was never built, so the game can never flow.
The stuff operating in the background
What struck me most about the best doubles pairs is this: they aren't thinking about the systems while they play. The systems are just running. Underneath everything. Invisible but constant. You can't see them. You barely notice them. Until they stop working.
That's the goal in business too. The best systems are the ones your team doesn't have to think about. They just know. Where to find the information. Who to go to. What the process is. How to handle it when something goes sideways. It runs in the background so the people in your business can focus on the actual game.
You don't build a system so people have more to think about. You build one so they have less.
Understanding your partner
The other thing badminton taught me: you have to understand how the person next to you thinks, not just what they do. Two people can have the same role and play it completely differently. One attacks. One defends. One calls everything. One prefers to read and react.
Neither is wrong. But if you don't understand which one you're working with, you'll keep stepping on each other's toes.
In a business context, that's the difference between a team that gels and one that grinds. It's not always about skill gaps. It's often about not knowing how the people around you operate. What they need from you. What you can expect from them. That understanding doesn't happen by accident. It's built. Deliberately. Through the right conversations, the right structures, the right systems.
What this means for your business
If your team feels chaotic, if people are stepping on each other, if things keep falling through the gaps, don't start by looking at the people. Start by looking at the system behind them.
Nine times out of ten, the issue isn't who you've got. It's that the framework they're operating in hasn't been built yet. The game is being played without anyone agreeing the rules first.
Build the system. Agree who covers what. Make the invisible stuff visible, just long enough to get it working. Then let it run in the background, where it belongs.
That's when the team starts to flow.