<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distance-Bias on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/distance-bias/</link><description>Recent content in Distance-Bias on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 Jul 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/distance-bias/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Hybrid Isn't the Same as Integrated</title><link>https://drlongnecker.com/blog/2026/07/distance-bias-hybrid-team-integration-leadership/</link><pubDate>Wed, 01 Jul 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/07/distance-bias-hybrid-team-integration-leadership/</guid><description>&lt;p&gt;Most hybrid teams think they&amp;rsquo;re integrated, and the logistics of modern remote work make that easy to believe. Shared tooling and common meeting cadences give everyone the sense of working as one unit. But &lt;strong&gt;integrated&lt;/strong&gt; means something different than co-located-accessible. What distributed teammates often experience is something messier — technically included but not equally positioned.&lt;/p&gt;
&lt;p&gt;The gap between hybrid and integrated isn&amp;rsquo;t about technology or policy. It&amp;rsquo;s a distance bias problem, and most organizations are actively maintaining it without realizing it.&lt;/p&gt;</description></item></channel></rss>