Have you ever tried to plan a team meeting when half your crew is in pyjamas and the other half is heading out for lunch?
Welcome to my world.
As a Project Manager working in the WordPress and WooCommerce space, I lead remote teams spread across Africa, South Asia, the Middle East, Oceania, and North America. We collaborate on projects while navigating time zones, task priorities, and the occasional power outage or cricket match.
Itās challenging. Itās rewarding. And with the right tools and mindsetāit works beautifully.
Hereās how I keep everything running smoothly (most of the time), even when no two team members are in the same time zone.
š Embracing Asynchronous Communication
Imagine trying to run a three-legged race⦠except youāre all on different continents. Thatās remote coordination in a nutshell.
The solution? Asynchronous communicationāfancy speak for āwe donāt all need to be online at the same time to move things forward.ā
Hereās what we rely on:
š§µ Slack ā for project updates, nudges, quick check-ins, and the occasional meme to keep morale high
š§© Google Workspace ā shared Docs, Sheets, and Meet for collaboration
š ļø Jira ā our task manager and structured chaos central
I keep things organised with dedicated Slack channels, clear tags, and clear messages for walkthroughs. That way, if itās 3 a.m. in Sydney, our Aussie team member can still get context without needing a late-night Zoom.
š” Think of it like leaving sticky notes on a digital fridge. Everyone checks in when theyāre ready.
š Establishing Clear Processes & Documentation
Letās be honestāif your project plan is āweāll figure it out as we go,ā then youāre not planning. Youāre just hoping for the best.
Early on, I learned the hard way that lack of clarity = delays. Iād assign tasks, ask for updates⦠and hear nothing. Developers werenāt unmotivatedāthey just didnāt have the right information, or the ask wasnāt clear enough.
Now I document everything:
Google Docs ā for briefs, wikis, and project overviews
Google Sheets ā for release schedules, bug logs, and tracking deliverables
And I simplify, always.
If a five-year-old wouldnāt get it, I rewrite it.
ā
Short paragraphs
ā
Bullet points
ā
Clear next steps
ā
Realistic timelines
And yes, I follow up. Like a polite squirrel that never forgets where it hid the acorns.
š§ Scheduling with Empathy & Efficiency
Hereās a real look at my life:
This is what it takes to find a single 30-minute overlap for team members in Nigeria, Australia, India, and Bangladesh. I call it ācalendar Tetris.ā
How I make it work:
World Time Buddy ā to spot overlap across time zones
Rotate meeting times ā so one region isnāt always taking the hit
Ask, āCan this be async?ā ā often the best meeting is the one that didnāt happen
Remote work is a team sport. It works best when everyone feels their time is respected.
š Continuous Learning & Adaptation
Working with remote teams is like building LEGO with gloves on. Youāll fumble, drop pieces, and occasionally step on something sharpābut every project teaches you something new.
What Iāve learned (and keep learning):
How to write better briefs
How to spot blockers early
How to listen more and assume less
And I keep sharpening my skills:
Make WordPress ā for staying on top of ecosystem updates
Slackās Remote Work Guide ā practical and tactical
šÆ Each lesson is a building block. Step on it onceālearn. Step on it twiceāyou werenāt paying attention.
ā
Wrapping Up: Herding Global Cats (and Loving It)
Hereās the big picture:
Use Slack, Google Workspace, and Jira to streamline communication
Write briefs a 5-year-old could understand
Schedule with empathy and rotate fairly
Always learn, adapt, and laugh when things go sideways
Want to improve your own coordination game? Start with:
šØļø Over to You
How do you keep your remote developers accountable and projects on timeāwithout becoming "that manager"?
Have any rituals, tools, or war stories to share?
Drop them below š
Or find me on LinkedIn āletās trade notes!
Top comments (0)