이 에피소드에 관해
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
영어
미국
전사 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
이 팟캐스트의 다른 에피소드
In this episode of Behind the Docs, Patrick sits down with Manny Silva, Head of Documentation at Skyflow, to explore what happens when technical writing evolves into full-scale content systems.
From growing up building computers to working at Apple and Google, Manny shares how his path into technic…
In this episode of Behind the Docs, Ren sits down with Dachary Carey of MongoDB to explore a rapidly emerging challenge: AI agents can’t reliably read your documentation and most teams don’t realize it.
Dachary shares how a deep dive into agent workflows (sparked by tools like Claude Code) uncovere…
Jeff Cross didn't plan to become a technical writer. He started a computer science degree, dropped out, spent a year trying to make it as a fiction writer, went back for a philosophy degree, considered academia, and then — almost by accident — realized that technical writing was the thing that made…
In this episode of Behind the Docs, Ren sits down with Melanie Denise Davis — journalist-turned-technical-communication leader, AI Wrangler, and founder of Dragonfly Diva Docs.
Melanie’s career spans the evolution of modern technology itself: from punch cards and mainframes to structured content an…
In this episode of Behind the Docs, Ren welcomes back Sara Feldman, Director of Member Engagement at the Consortium for Service Innovation and longtime advocate for knowledge-driven customer experience.
Sara began her career as a technical writer, spending a decade embedded with support teams befor…
면책 조항: 이 페이지에 포함된 팟캐스트와 작품은 Heretto에서 가져온 것입니다. 이 팟캐스트는 소유자의 재산이며 Listen Notes, Inc.와 제휴하거나 보증하지 않습니다.
