<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="https://elezea.com/wp-content/themes/elz_2023/styles/pretty-feed-v3.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:slash="http://purl.org/rss/1.0/modules/slash/" >
  <channel>
    <title>Elezea by Rian van der Merwe - RSS Feed</title>
    <atom:link href="https://elezea.com/2019/04/remote-work-process-design/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2019/04/remote-work-process-design/</link>
    <description>A personal blog about product, technology, and interesting things that are worth sharing.</description>
    <lastBuildDate>Thu, 02 Apr 2026 17:43:52 +0000</lastBuildDate>
    <language></language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>https://wordpress.org/?v=6.9.4</generator>
          <item>
        <title>When you deliberately design your remote work process, it’s good for the whole team</title>
        <link>https://elezea.com/2019/04/remote-work-process-design/</link>
        <pubDate>Thu, 11 Apr 2019 18:57:12 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=6943</guid>
        <description>
          <![CDATA[Helen Mou and Kevin Ochal share some good tips for remote teams in “Making the Dream Work: Leading Distributed Product Teams.”]]>
        </description>
        <content:encoded>
          <![CDATA[<p>Helen Mou and Kevin Ochal share some good tips for remote teams in <a href="https://medium.com/reiterate/making-the-dream-work-leading-distributed-product-teams-c8788be7ce67">Making the Dream Work: Leading Distributed Product Teams</a>. Most importantly, I agree that if you are deliberate about how you design your work process, it’s good for the whole team — whether they’re remote or not:</p>
<blockquote>
<p>Instead of approaching distributed teamwork with the mindset of “we’re making it work, in spite of…” staying up late, working more hours, and spending more effort to be on a distributed team; we like to look at it as an investment in strength-building for your organization. Over time, this investment will build up your team’s trust battery, and create new habits, patterns, and behaviours that make any team — distributed or not — successful.</p>
</blockquote>
<p>Related reading from me: <a href="https://medium.com/elezea/remote-product-management-challenges-and-opportunities-3fd5cefcf6bc">Remote product management: challenges and opportunities</a>.</p>
          <br>
          <br>
          <hr>
          Thanks for still believing in RSS! Get in touch <a href="https://elezea.com/contact">here</a> if you'd like.]]>
        </content:encoded>
                      </item>
      </channel>
</rss>