Kindness is the foundation of a healthy collaboration.
Candor is the foundation to effective communication and growth. 💙 Kindness and 🌶️ Candor can coexist.
Remote communication comes with the challenge of missing non-verbal cues, making it harder to understand emotional nuances. Maintaining a happy tone and assume the best intentions in others helps foster positive collaboration vibes. Avoid ambiguous communication like sarcasm.
When sharing important decisions, always include the thought process behind how you reached those decisions. Great decisions are the outcomes of great thought processes. Sharing the rationale allows others and oneself to evaluate the quality of the decision itself.
Encourage a sense of team collaboration by framing discussions and decisions in terms of “we” rather than “I” or “you”. Collaborative language emphasizes teamwork and shared ownership, creating a stronger team spirit and mutual accountability within the team.
Prioritize asynchronous communication and collaboration, whenever possible. Minimize forced context switching, respect deep focus and flow states and respect the team’s valuable time. Use the appropriate communication tools for the appropriate purpose. Prioritize single-instance, contextual, archivable and searchable communication.
Every active project runs on two rituals: one weekly internal meeting and one weekly sync with the client. Everything else is async by default. Minimum sync to stay aligned, maximum freedom over our time. In hard times, sync more.
Every meeting has a leader who prepares an agenda and a pre-read. The agenda brings clarity and efficiency, but leave some room for wandering. Calendar invites confirm who is coming. If you accept a meeting, show up. Schedule by prioritizing other people's focus time. Use the optional invite feature.
In internal huddles, camera is optional but a nice-to-have. In client meetings, camera presentation matters. If you are listening-in while multitasking, turn camera off to avoid distracting others. Don’t talk about progress, show the actual progress: videos, builds, screen-share, images or screen-recordings.
Knowledge transfer at Treeview is never person ↔ person. It is Person ↔ Documentation ↔ Person. Every role should maintains real-time documentation of their domain. Our stack per role may be: Linear, Notion, changelogs, context.md, Looms, Figma, Git, design reviews, meeting notes.