Remote and in-office associates can work as one team when communication, access and expectations are explicit. These 20 practices support a blended team spread across locations and time zones.

  1. Set clear communication channels between remote and in-office workers using email, instant messaging, video conferencing or a combination.
  2. Write a communication plan that says how often and through which channels remote workers and in-office workers will communicate.
  3. Set response-time expectations for both remote and in-office workers.
  4. Use collaboration tools such as Google Docs, Slack, Asana or Trello for shared work.
  5. Schedule regular check-ins so people can surface concerns and confirm that work remains aligned.
  6. Use video conferencing for meetings and project updates so remote workers stay connected.
  7. Create social contact through team-building activities, virtual happy hours or other events.
  8. Give remote workers the training and support they need to do their jobs.
  9. Use project management tools to track progress, assign tasks and keep work moving.
  10. Invite remote workers to the office for periodic meetings that build relationships and collaboration.
  11. Offer flexible schedules that respect different work styles and needs.
  12. Give remote workers access to the same software, hardware and support available to in-office workers.
  13. Explain how remote workers should access resources and request support.
  14. Offer professional development to remote and in-office workers.
  15. Celebrate team successes together, regardless of where each person works.
  16. Assign a point of contact for remote workers with questions or concerns.
  17. Use time tracking tools so remote workers record time accurately and receive fair pay.
  18. Give remote workers regular feedback so they can improve and stay connected.
  19. Encourage open communication between remote and in-office workers to build transparency and trust.
  20. Review the blended-work strategy and adjust it when the team's needs change.

Original publication on GoDaddy