How to Build Trust as a New Manager in a Fully Remote Team

Summary

The post explains why building trust as a new manager in a fully remote organization differs from joining a team with established relationships: passive cues and casual interactions are harder to observe, so remote work requires intentionality. The proposed 90-day plan focuses on the environment during the first 30 days, the team during the next 60, and the manager thereafter. Early actions include pairing sessions, one-on-ones, peer-group sessions, understanding the wider organization, setting up remote tools, and building cross-company relationships. Team leadership emphasizes spending time with members, using asynchronous communication for productivity and synchronous meetings for connection, and creating psychological safety through open communication and transparent discussion of failures. The final phase addresses FOMO, workday design, and experimentation through feedback and reflection.

Context

Starting remotely in a company where trust has not yet been established differs from moving from an office to home after relationships and collaboration patterns already exist. In a remote setting, passive trust-building signals and casual, non-transactional relationships are harder to observe and require more intentional design.

Approach / What changed

The post presents a 90-day onboarding plan: focus on the organizational environment in the first 30 days, the team by the first 60 days, and personal working practices from day 90 onward. It recommends pairing sessions, one-on-ones, peer groups, deliberate tool setup, relationship building, asynchronous work for productivity, synchronous meetings for connection, and transparent practices that support psychological safety.

Takeaways

• The 90-day plan divides onboarding into environment, team, and self-focused phases rather than treating remote integration as an informal process.
• Asynchronous communication is recommended for automated dailies, code reviews, feedback, and technical design collaboration, while synchronous meetings support retrospectives, coffee sessions, demos, and planning.
• Remote psychological safety can be encouraged through open communication, inviting discussion of issues in retrospectives and all-hands meetings, and being transparent about personal failures or ineffective approaches.

Related reading