Start with “Thank You”: Smoothing the Friction in Cross-Team Syncs
When working with partner teams, it’s easy to get bogged down by slow debugging, a lack of support, or endless back-and-forth messaging. When this happens, a quick sync is usually the best way forward—but how you start that meeting matters.
I’ve observed that my Tech Lead consistently starts these calls by thanking the partner team for their effort. Leading with gratitude does three things immediately:
- Smoothes the friction: It disarms defensiveness before the technical deep-dive begins.
- Creates a blameless culture: It frames the relationship as “us vs. the problem” rather than “our team vs. your team.”
- Builds collaboration: It acknowledges the work already done, making the partner team more willing to help.
It is a small change in communication that yields massive results in engineering efficiency. It’s a strategy I plan to use in my next cross-team sync.
The Weekly Habit That Makes Peer Feedback Effortless
We all know the struggle of review season: staring at a blank screen, trying to remember exactly what a colleague did three months ago to help your project. We usually end up writing something generic like, “Thanks for being a great collaborator.”
While nice, generic praise doesn’t actually help anyone’s career.
Recently, I picked up a great habit from my Tech Lead. To write highly effective feedback and meaningful thank-you notes, you need to rely on a system, not your memory. The trick is to keep a periodic—ideally weekly—record of your collaborators’ contributions.
It doesn’t require a complex setup. Just keep a simple, running markdown document or note. At the end of every week, take five minutes to jot down:
- The Collaborator: Who helped out this week?
- The Task: What specific technical challenge did they solve or assist with?
- The Impact: How did their work unblock the team or push the project forward?
By the time you need to write formal feedback or send a shoutout, you have a detailed log of con