Building Bridges Between Teams with Rahul Garg

A different kind of guest this episode: Ren talks with Rahul Garg, a project management professional who's spent his career in telecom and fintech coordinating between developers, testers, quality teams, and senior stakeholders. Rahul isn't a technical writer, but his approach to communication, audience-tailoring, and building a team newsletter has striking overlap with what technical writers do every day.

Rahul breaks down why he sees himself as "the bridge" between isolated stakeholder groups, how ambiguous words like "done" or "highlight" can derail a project if teams aren't aligned on meaning, and how he turned a messy, jargon-heavy team newsletter into a concise, consistent communication tool that became a single source of truth for his project.

In this episode

• Rahul's background in telecom and fintech project management, and how his role evolved from "managing work" to helping people understand what they're doing and why
• Why he calls himself a bridge between stakeholders working in isolation, and how he tailors content differently for developers, testers, quality teams, and senior leadership
• The importance of defining shared vocabulary on a project (what does "done" actually mean?) before work even starts
• Building a communication plan for distributed, cross-timezone teams, and using handoff notes to bridge gaps when no meeting time overlaps
• How Rahul launched a team newsletter, why the first version flopped (too long, too jargon-heavy, almost nobody read it), and the structure he landed on: quick wins, risks, delivery updates, blockers, and recognition
• Why consistency and recognition matter so much in a recurring newsletter, and how it created two-sided value — visibility for the team and a documented record protecting against "I wasn't aware" moments later
• Streamlining how he collects input from contributors so the newsletter doesn't become an unmanageable dump of blockers and non-highlights
• Where project management and technical writing overlap and diverge: technical writers own the "how," project managers own the "what and why" — and where friction between the two roles can show up
• His hill to die on: organizations massively underestimate the cost of poor communication, and transparency has declined since the pre-COVID era