Leading Distributed Teams

A map of where and when your team works, a shared overlap window and working agreement, written rhythms that replace hallway talk, and the habits that build trust across locations and time zones.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Leading Distributed Teams, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

♟️ Strategy & Leadership

Leading Distributed Teams

Leading teams spread across locations and time zones, with clear rhythms, written communication and trust built at a distance.

  1. Time zone and working hours map of the team
  2. Core overlap window for live collaboration
  3. Distributed team working agreement
  4. Channel charter for what goes where
  5. Response time expectations by channel
  6. Team handbook as the single source of truth
  7. Baseline survey of trust, clarity and isolation
  8. Remote workspace and equipment standard
  9. Public decision log for the team
  10. Monday written team update
  11. Written check-ins instead of a daily standup call
  12. Rotating meeting times to share the time zone burden
  13. Video one-to-ones across time zones
  14. Monthly distributed team retrospective
  15. Handoff notes between overlapping regions
  16. Quarterly meeting audit and calendar reset
  17. Documentation upkeep rota
  18. Recognition and thanks at a distance
  19. Quarterly distributed team health pulse
  20. Unstructured connection time for a remote team
  21. Leave and public holiday coverage calendar
  22. Writing for readers who are asleep when you send it
  23. Running hybrid meetings fair to remote attendees
  24. Facilitating remote workshops on a shared whiteboard
  25. Spotting disengagement and overload at a distance
  26. Cross-cultural communication in a multinational team
  27. Difficult conversations over video
  28. Written proposals for asynchronous decisions
  29. Choosing the team's remote, hybrid or office model
  30. Collaboration tool stack review
  31. Cutting recurring meeting hours by a third
  32. Proximity bias check in reviews and promotions
  33. Hiring process redesigned for remote candidates
  34. Remote onboarding for new joiners
  35. Deciding where to hire next by location
  36. Travel and gathering budget case
  37. In-person team week
  38. Distributed kickoff for a new cross-site project
  39. Quarterly planning session across time zones
  40. Opening a new satellite location for the team
  41. Remote team member departure and knowledge handover
  42. Taking over a remote team you have never met
  43. Leading an office team while you work remotely
  44. Leading contractors and agency staff across countries
  45. Being a strong teammate on a distributed team
  46. Supporting the one person in a far-off time zone
  47. Protecting your own hours as a distributed leader
  48. Follow-the-sun operating model for round-the-clock work
  49. Measuring distributed team effectiveness
  50. Information security habits for a team working from anywhere

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Time zone and working hours map of the team

Most distributed managers carry a rough picture of who is where, and it is usually wrong by an hour or two for half the year once daylight saving shifts. A single map showing each person's city, time zone, usual working hours and fixed commitments such as school runs shows at a glance when the team can meet live and who always pays the price.

First tasks

  • Ask each team member for their city and the hours they actually work
  • Build a table with time zone, start and finish times and blocked hours
  • Add the daylight saving change dates for each location
  • Pin the map in the team space and ask everyone to correct their row

Core overlap window for live collaboration

Across a spread of eight or more hours, live meetings drift to whatever suits the manager and the far-flung people quietly join at midnight. Agreeing two or three core hours a day when everyone is reachable, and protecting the rest for focused and asynchronous work, gives live discussion a home without taking over everyone's evenings.

First tasks

  • Shade the hours each person works on the time zone map to find the overlap
  • Propose two candidate windows and the cost of each to the team
  • Move or cancel recurring meetings that fall outside the chosen window
  • Add the overlap window as a shared calendar block for everyone

Distributed team working agreement

Teams that share an office pick up norms by watching each other, while distributed teams only have the norms they write down. A working agreement written by the whole team, covering hours, availability, how to ask for help, camera use and what happens when someone is offline, turns a dozen silent assumptions into a page everyone can point to.

First tasks

  • Share a blank agreement with headings for hours, meetings, help and time off
  • Give the team a week to write and comment on the draft
  • Agree the final wording in a team meeting and date it
  • Revisit the working agreement with the team @recurring(yearly)

Make it yours.

Install Leading Distributed Teams, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.