<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Esedu on Medium]]></title>
        <description><![CDATA[Stories by Esedu on Medium]]></description>
        <link>https://medium.com/@eseduhq?source=rss-a00e1f1cde0e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*77FYh82vYC3n2n73kUYJOw@2x.png</url>
            <title>Stories by Esedu on Medium</title>
            <link>https://medium.com/@eseduhq?source=rss-a00e1f1cde0e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:30:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eseduhq/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Real Cost of Care Debt: What Distributed Teams Are Missing]]></title>
            <link>https://medium.com/@eseduhq/the-real-cost-of-care-debt-what-distributed-teams-are-missing-c42d102940d0?source=rss-a00e1f1cde0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c42d102940d0</guid>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[car-debt]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[engagement]]></category>
            <dc:creator><![CDATA[Esedu]]></dc:creator>
            <pubDate>Sat, 01 Mar 2025 11:44:00 GMT</pubDate>
            <atom:updated>2025-03-01T11:44:00.002Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vvI39xfG8kCCRDRK-Z6KuA.jpeg" /><figcaption>A desk with a laptop showing a Zoom call, an untouched birthday card, and several notification messages on a phone</figcaption></figure><p>It was my third week leading a distributed team when I received the resignation email.</p><p>“I appreciate the opportunity,” Ella wrote, “but I’ve accepted a position elsewhere.”</p><p>When I called to discuss her decision, her answer caught me off guard: “I just never felt like I really belonged here. Everyone’s nice, but… it’s like we’re all just passing through the same digital space without actually connecting.”</p><p>Her words stayed with me for months. We had good compensation. Flexible hours. Interesting projects. What had we missed?</p><p>The truth emerged slowly as I spoke with more team members. The problem wasn’t any single interaction — it was the accumulation of small disconnections over time. The birthday that went unacknowledged. The project milestone celebrated three days late. The personal struggle no one noticed because it wasn’t visible on video calls.</p><p>I began to think of these missed connections as “care debt” — a concept borrowed from the technical debt that plagues software projects. Just as engineers accumulate shortcuts that eventually slow development to a crawl, teams accumulate missed opportunities for connection that eventually erode the cultural foundation.</p><h3>What Care Debt Looks Like</h3><p>Care debt builds up gradually, making it easy to miss until it’s severe. Here’s how it typically manifests:</p><p>Maria completed a challenging client project over the weekend. On Monday, she mentioned it briefly in Slack. A few teammates sent emoji reactions. Her manager planned to recognize her effort in the next team meeting, but got busy and forgot. A small debt began.</p><p>Wei celebrated his five-year work anniversary. The company’s recognition system automatically sent him a digital badge, but his teammates didn’t know about it. Another small debt.</p><p>Alejandro struggled with a family health crisis for weeks. In an office, his demeanor would have signaled something was wrong. In a distributed team, no one noticed his increasing silence in meetings. The debt grew larger.</p><p>None of these instances would break a healthy team culture on its own. But together, over months? They create an environment where people feel fundamentally unseen.</p><h3>The Human Impact</h3><p>“I used to put my whole self into my work,” a developer at a remote-first company told me. “But after months of feeling invisible, I started holding back. Why pour your heart into something when no one seems to notice or care?”</p><p>This sentiment echoes across industries. A designer described turning her camera off more frequently during calls, retreating further from connection. A product manager admitted to choosing the path of least resistance on projects rather than advocating for better solutions.</p><p>These aren’t just emotional responses — they’re rational adaptations to environments where care seems scarce or inconsistent.</p><h3>From Personal to Organizational</h3><p>While care debt begins as a personal experience, it quickly becomes an organizational problem. Research from Gallup suggests that disengaged employees cost organizations 18% of their annual salary in lost productivity. When disconnection leads to turnover, the costs skyrocket — with replacement expenses reaching 100–300% of annual salary for skilled positions.</p><p>For a team of 50 people earning an average of $75,000, just a 10% increase in turnover can cost over $750,000 annually.</p><p>But the impact goes beyond finances. Teams with high care debt show measurable decreases in:</p><ul><li>Innovation and creative problem-solving</li><li>Willingness to raise concerns or identify problems early</li><li>Collaboration across departments</li><li>Customer service quality</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MbTVEG0q8OvYZChnnGUyzQ.jpeg" /></figure><h3>Breaking the Cycle</h3><p>After losing Ella and witnessing the ripple effects of disconnection, I became determined to break the cycle of care debt in my team. Here’s what actually worked:</p><p><strong>1. Make care visible</strong></p><p>We created a simple “connection calendar” that tracked important dates for team members — work anniversaries, birthdays (for those who opted in), project milestones, and personal achievements. This made previously invisible opportunities for connection visible to everyone.</p><p>The key wasn’t just having the information, but making it actionable. Each team member was assigned one day per week to check the calendar and take one meaningful action.</p><p><strong>2. Remove logistical barriers</strong></p><p>We established a modest budget for sending physical tokens of appreciation — books, local treats, handwritten notes — and pre-approved spending up to a certain amount without additional permissions.</p><p>This eliminated the friction that often prevents good intentions from becoming reality. When someone wanted to recognize a teammate’s effort, they could do it immediately rather than navigating approval processes.</p><p><strong>3. Create rituals of recognition</strong></p><p>We built recognition into our rhythms rather than treating it as an extra. Our weekly team calls now begin with “wins and appreciations,” where anyone can highlight something a teammate did well.</p><p>The structure makes appreciation a consistent practice rather than an occasional afterthought.</p><p><strong>4. Measure what matters</strong></p><p>We started tracking not just productivity metrics but connection metrics:</p><ul><li>How many team members receive specific recognition each month</li><li>How many report feeling “seen and valued” in pulse surveys</li><li>How often team members reach out to help each other</li></ul><p>These measurements created accountability for the cultural environment we were creating.</p><h3>The Return on Connection</h3><p>Six months after implementing these changes, we saw tangible results. Team turnover decreased by 22%. Pulse survey scores for “feeling valued” increased by 31%. And most surprisingly, innovation metrics — the number of new ideas submitted and implemented — rose by 27%.</p><p>One engineer summarized it perfectly: “When I know my team actually cares about me as a person, I’m willing to bring my whole self to work. That includes the creative, risk-taking parts that I used to keep to myself.”</p><h3>Starting Simple</h3><p>Building care infrastructure doesn’t require complex systems or massive budgets. Start with these questions:</p><ol><li><strong>What matters to your people?</strong> Ask team members what makes them feel valued and connected. Don’t assume — differences in background, generation, and personality create different needs.</li><li><strong>Where is care breaking down now?</strong> Identify the moments where connection consistently fails in your team. Is it during onboarding? Around performance reviews? During stressful project periods?</li><li><strong>What’s one ritual you could implement tomorrow?</strong> Choose something simple and sustainable that addresses a specific care gap.</li><li><strong>How will you know if it’s working?</strong> Determine what signals would indicate improvement in your team’s connection.</li></ol><h3>The Fundamental Shift</h3><p>The most profound change in our team wasn’t any specific practice — it was the shift from viewing care as an individual responsibility to seeing it as essential infrastructure.</p><p>Just as we wouldn’t expect a remote team to function without internet access or proper equipment, we no longer expect meaningful connection to happen without deliberate systems to support it.</p><p>When Ella left, I thought we had a single disconnected team member. What I eventually realized was that we had a disconnected system — one that relied on chance and individual heroics to create belonging.</p><p>Building care infrastructure isn’t just about retention metrics or productivity gains, though those benefits are real. It’s about creating environments where people can do their best work because they feel fundamentally valued and seen.</p><p>In a world where more teams are distributing across geographies and time zones, this isn’t a nice-to-have — it’s the foundation everything else is built upon.</p><p><em>Have you experienced care debt in your team? What systems have you found effective for creating genuine connection across distance? Share your experiences in the responses.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c42d102940d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Gift Cards Aren’t Enough (The Hidden Complexity of Cross-Border Care )]]></title>
            <link>https://medium.com/@eseduhq/when-gift-cards-arent-enough-the-hidden-complexity-of-cross-border-care-263e724d68bb?source=rss-a00e1f1cde0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/263e724d68bb</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[global]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[hr-talent-management]]></category>
            <dc:creator><![CDATA[Esedu]]></dc:creator>
            <pubDate>Wed, 12 Feb 2025 14:51:51 GMT</pubDate>
            <atom:updated>2025-02-12T14:51:51.927Z</atom:updated>
            <content:encoded><![CDATA[<h3>It seemed like such a simple gesture. Elena, a team lead in Milan, wanted to treat her engineer in Tallinn to dinner after he pulled an all-nighter fixing a critical bug. “I’ll just send him a gift card,” she thought. Two hours and three failed attempts later, she gave up.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5aYf9KXUZaOGXdvi" /><figcaption>Photo by <a href="https://unsplash.com/@katemacate?utm_source=medium&amp;utm_medium=referral">Kate Macate</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This scene plays out thousands of times daily across global teams. What starts as a simple impulse to show appreciation becomes a masterclass in international commerce complexity. The reality is: sending food across borders is anything but simple.</p><h3>When “Just Send a Gift Card” Goes Wrong 🤦‍♀️</h3><p>Let’s follow Elena’s journey:</p><p>First attempt: Send a Glovo gift card. Blocked — service doesn’t operate in Estonia. Second attempt: Find Wolt, a local food delivery service. Found it, but their gift cards only work with Estonian payment methods. Third attempt: Try to pay directly. Currency conversion fees and platform restrictions made this €25 dinner a bureaucratic nightmare.</p><p>Meanwhile, her colleague Marta in Riga faces similar challenges trying to celebrate her design team’s success in Lisbon. Each country’s unique payment systems and platforms create invisible walls between team members.</p><h3>The Hidden Complexity of Cross-Border Care 🔍</h3><p>What makes this seemingly simple act so complicated? The challenges stack up like layers of a particularly complex cake:</p><ol><li>Provider Fragmentation 🧩 Every country has its own dominant food delivery players. What works in Lagos (Chowdeck) doesn’t work in Malta (Wolt). Even within the EU, there’s no single service that works everywhere, making it impossible to have one simple solution.</li><li>Currency Conundrums 💶 Even in the Eurozone, gift cards often need to be purchased through local payment processors. Outside it, in places like Stockholm or Prague, you’re dealing with kronor and koruna conversions on top of platform restrictions.</li><li>Local Payment Systems 💳 Each region has its preferred payment methods. iDEAL dominates in the Netherlands, while Klarna is crucial in Sweden. Gift cards often work with only one system, creating invisible walls between markets.</li><li>Regulatory Mazes 📋 Cross-border transactions trigger a web of compliance requirements. Even within the EU, local tax implications and regional restrictions create a complex tapestry of rules that vary by country.</li></ol><h3>Why Simple Solutions Fail ❌</h3><p>The typical solutions offered for this problem tend to fall short:</p><p><strong>Global Gift Card Platforms</strong> They sound promising but usually have limited coverage beyond major cities — exactly where many distributed teams have members.</p><p><strong>Direct Money Transfers</strong> Clean in theory, messy in practice. High fees, slow processing times, and the loss of the gesture’s meaning as it becomes a simple cash transaction.</p><p><strong>Digital Vouchers</strong> Often restricted by device type, operating system, or local app availability. What works on an iPhone in Madrid might not work on an Android in Bucharest.</p><h3>The Infrastructure Gap 🌉</h3><p>At its core, this isn’t a gift card problem — it’s an infrastructure problem. The current system is built on a patchwork of local solutions trying to work globally. It’s like trying to power a modern city with a collection of generators instead of a power grid.</p><p>What’s needed isn’t another gift card solution, but rather an infrastructure that can:</p><ul><li>Handle currency conversion invisibly</li><li>Navigate local payment systems automatically</li><li>Work with local providers seamlessly</li><li>Maintain the meaning of the gesture throughout</li></ul><h3>Building Bridges, Not Walls 🚀</h3><p>The future of global teams depends on our ability to make caring across borders as simple as caring across the office. This requires rethinking not just how we send gifts, but how we build the infrastructure that enables care to flow freely across borders.</p><p>Because when a team lead wants to show appreciation to a team member, they shouldn’t have to become an expert in international finance. They should be able to act on that impulse to care as easily as they send an email.</p><p>After all, in a world where teams are increasingly distributed, our ability to show care can’t be limited by geography or complicated by technology. It needs to be as borderless as the teams we’re building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=263e724d68bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Distance Makes Care Harder: The Hidden Challenge of Global Teams]]></title>
            <link>https://medium.com/@eseduhq/when-distance-makes-care-harder-the-hidden-challenge-of-global-teams-d7feeb6ca10c?source=rss-a00e1f1cde0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7feeb6ca10c</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[benefits]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Esedu]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 09:48:15 GMT</pubDate>
            <atom:updated>2025-02-04T09:48:15.653Z</atom:updated>
            <content:encoded><![CDATA[<p>A manager in London wants to celebrate her team member’s big product launch in Singapore. In the past, she would have taken the team out for lunch to celebrate. A simple gesture that says “I see you, I value you, we’re in this together.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZJj2K3qq0I8dT5U7" /><figcaption>Photo by <a href="https://unsplash.com/@goian?utm_source=medium&amp;utm_medium=referral">Ian Schneider</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>But today, that team member is 6,800 miles and seven time zones away.</p><p>So instead, she sends a congratulatory Slack message. Types, deletes, and retypes trying to convey genuine appreciation through emojis and exclamation points. It feels hollow. Not because she cares any less, but because distance has made it harder to show that care in meaningful ways.</p><p>This is the hidden challenge of our new distributed world. It’s not just about productivity tools or video calls. It’s about maintaining human connection when traditional gestures of care break down across borders.</p><h3>The Geography of Care</h3><p>Think about the small ways we traditionally show care at work: Grabbing coffee when someone seems stressed. Bringing in birthday cupcakes. Ordering pizza for the team during a late night push.</p><p>These micro-moments of care weave the fabric of team culture. They turn colleagues into companions. They make work feel more human.</p><p>But in distributed teams, these organic opportunities vanish. The spontaneous becomes impossible. The simple becomes complex.</p><p>A manager in New York can’t just order DoorDash for their team member in Lagos. A colleague in Berlin can’t grab coffee for their partner in Tokyo. The physical infrastructure of care breaks down across borders.</p><h3>When Digital Doesn’t Fill the Gap</h3><p>“Just send a gift card!” is the common suggestion. But anyone who’s tried knows it’s rarely that simple.</p><p>First, there’s the complex web of which services work where. Then there’s currency conversion, local restrictions, delivery limitations. What starts as a simple gesture of care becomes a logistical puzzle.</p><p>More importantly, digital alternatives often feel impersonal — another notification in an already overwhelming stream. They lack the tangible quality that makes gestures of care feel real.</p><h3>The Cost of Care Friction</h3><p>When showing care becomes harder, we often do it less. Not because we care less, but because the friction wears us down. Each blocked attempt to show appreciation, each failed effort to celebrate success, each moment of connection lost to logistical complexity — they all take their toll.</p><p>Over time, this creates what we call a “care gap” in distributed teams. The desire to show care remains strong, but the ability to act on that desire diminishes with distance.</p><p>Team members feel less seen, less valued, less connected. Managers feel frustrated by their inability to support their people in meaningful ways. The human elements that make teams thrive start to fray.</p><h3>Building New Bridges</h3><p>The solution isn’t to accept this diminished ability to care, nor to try forcing old models of care into a new world. Instead, we need to reimagine how care can work across borders.</p><p>We need ways to show care that are as simple as sending an email, but as meaningful as sharing a meal. Tools that handle the complexity of cross-border care while preserving the human intention behind it.</p><p>Most importantly, we need to make it effortless for people to act on their natural desire to show care — regardless of distance, time zones, or borders.</p><p>Because in a world where teams are increasingly distributed, our ability to show care can’t be limited by geography. The future of work depends not just on our ability to collaborate across borders, but on our ability to care across them too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7feeb6ca10c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Geography of Workplace Culture]]></title>
            <link>https://medium.com/@eseduhq/the-geography-of-workplace-culture-78e8bcc39361?source=rss-a00e1f1cde0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/78e8bcc39361</guid>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Esedu]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 10:59:27 GMT</pubDate>
            <atom:updated>2025-01-27T10:59:27.296Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Invisible Divides Shaping the Future of Work</h3><p>📍 <strong>If your team is spread across multiple cities, your workplace culture isn’t just one thing — it’s a map of invisible divides.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zWaY0VxAZG4TnwTvUikGOg.jpeg" /></figure><p>Once upon a time, workplace culture was easy to define. It lived in the hallways, the lunchrooms, the Friday drinks, and the spontaneous brainstorming sessions by the whiteboard. It thrived in <strong>physical presence.</strong></p><p>Fast forward to 2025, and the office landscape looks very different.</p><p>🔹 <strong>HQ teams</strong> — those in the main office — experience work differently. They grab coffee together, brainstorm in real time, and naturally bond through everyday moments.<br>🔹 <strong>Remote employees</strong> — whether full-time staff or contractors — exist in a different reality. They join calls, submit work, and contribute just like everyone else, but they rarely experience the <strong>organic culture</strong> of the company.<br>🔹 <strong>Companies with multiple HQs</strong> often struggle with an internal identity crisis. One office operates with a different culture from another, leading to subtle divisions in priorities, communication, and collaboration.<br>🔹 <strong>Fully remote teams</strong> are left figuring out how to maintain connection without ever sharing physical space.</p><p>Every organization now exists in <strong>a fragmented geography of culture</strong> — and most don’t even realize it.</p><h3>HQ Culture vs. Remote Reality: The Growing Divide</h3><p>Let’s talk about HQ employees for a second.</p><p>In companies that still maintain a physical headquarters, <strong>the in-office crowd experiences work differently from their remote counterparts.</strong></p><p>🏢 They have <strong>hallway conversations</strong> that don’t make it into Slack.<br>🍽️ They enjoy catered lunches, coffee breaks, and after-work drinks.<br>🚪 They have <strong>direct access to leadership</strong> — informal check-ins that shape career trajectories.</p><p>Meanwhile, a remote employee working from their apartment in Barcelona?</p><p>🖥️ <strong>Every interaction is scheduled.</strong><br>💬 <strong>Every conversation is intentional.</strong><br>👀 <strong>Every promotion opportunity depends on visibility in meetings.</strong></p><p>And if a company doesn’t actively recognize these gaps, <strong>they become culture fractures.</strong></p><p>This doesn’t just impact morale — it shapes <strong>who gets heard, who gets promoted, and who feels truly part of the company.</strong></p><h3>Multiple HQs, Multiple Identities</h3><p>For global companies with multiple HQs, the problem is even more complicated.</p><p>Take a company with major offices in <strong>New York, London, and Singapore.</strong></p><p>Each office has its own:<br>🌍 <strong>Leadership presence</strong> — Executives tend to favor their home office.<br>📆 <strong>Work schedules</strong> — Time zone gaps limit real-time collaboration.<br>🎭 <strong>Cultural differences</strong> — What’s normal in one office might feel foreign in another.</p><p>The result?</p><p>Instead of one unified company culture, you get <strong>three micro-cultures</strong> operating under the same brand. Employees in London might feel closer to their local leadership than the CEO in New York. Singapore might feel like an entirely separate company.</p><p>And when decisions are made? The headquarters with the most influence (or time zone overlap) <strong>gets the final say.</strong></p><p>This isn’t just about distance. It’s about <strong>who gets to shape the company’s identity.</strong></p><h3>The Isolation of Fully Remote Employees</h3><p>Now, let’s talk about <strong>fully remote teams.</strong></p><p>For some companies, remote work is the default. There’s no central office, no HQ, no watercooler moments — just Slack channels, Zoom calls, and an occasional in-person meetup.</p><p>At first glance, this seems like the most <strong>equal</strong> structure. No one is in HQ, so no one is left out, right?</p><p>Not exactly.</p><p>Without <strong>shared physical spaces,</strong> culture becomes harder to define. It turns into:</p><p>📆 <strong>More meetings.</strong> Because there’s no casual interaction, everything needs to be scheduled.<br>📣 <strong>More structured engagement.</strong> Virtual happy hours, team-building exercises, and “forced fun” become substitutes for real connection.<br>🔄 <strong>More turnover.</strong> Employees feel less attached to the company, leading to <strong>quicker churn</strong> and a lack of long-term loyalty.</p><p>In fully remote setups, <strong>workplace culture has to be manufactured</strong> — and companies are still struggling to get it right.</p><h3>The Emotional Cost of Fragmented Culture</h3><p>At its core, workplace culture is about <strong>belonging.</strong></p><p>A strong culture makes employees feel:<br>✔️ Seen<br>✔️ Heard<br>✔️ Connected to something bigger than their tasks</p><p>But in a <strong>geographically fractured workplace,</strong> employees experience different levels of <strong>inclusion, recognition, and engagement.</strong></p><p>🔹 The HQ crowd gets to feel like the heart of the company.<br>🔹 Remote employees risk feeling like <strong>outsiders looking in.</strong><br>🔹 Multiple HQ teams struggle to feel aligned under one vision.<br>🔹 Fully remote workers have to fight against <strong>loneliness and cultural disconnect.</strong></p><p>Culture isn’t about policies. It’s about <strong>shared experiences.</strong> And when those experiences vary drastically based on location, companies end up with employees who feel like they work for <strong>entirely different companies.</strong></p><p>The question isn’t whether this problem exists.</p><p>It’s <strong>what companies are going to do about it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78e8bcc39361" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>