<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Disruptor - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Disruptor Articles feed</description>
    <item>
      <title>Article: Smashing Silos: Scaling up an Energy Tech Disrupter Remotely</title>
      <link>https://www.infoq.com/articles/scaling-energy-tech-disruptor-remotely/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Disruptor-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/scaling-energy-tech-disruptor-remotely/en/headerimage/generatedHeaderImage-1656344666217.jpg"/&gt;&lt;p&gt;Being a small EnTech disruptor in a rapidly evolving market can feel a bit daunting; add in an acquisition, a rebrand and twice the team members that you had a year ago and you have a recipe for growing pains. Here is how we leaned on our strengths and pulled experience from all directions to allow for team member fulfilment during a breakneck growth spurt.&lt;/p&gt; &lt;i&gt;By Rebecca Mahoney, Andy Molineux&lt;/i&gt;</description>
      <category>Disruptor</category>
      <category>Communication</category>
      <category>Distributed Team</category>
      <category>Innovation</category>
      <category>Scaling</category>
      <category>Organizational Debt</category>
      <category>Remote Developer</category>
      <category>Stories &amp; Case Studies</category>
      <category>Culture &amp; Methods</category>
      <category>article</category>
      <pubDate>Wed, 29 Jun 2022 07:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/scaling-energy-tech-disruptor-remotely/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Disruptor-articles</guid>
      <dc:creator>Rebecca Mahoney, Andy Molineux</dc:creator>
      <dc:date>2022-06-29T07:00:00Z</dc:date>
      <dc:identifier>/articles/scaling-energy-tech-disruptor-remotely/en</dc:identifier>
    </item>
  </channel>
</rss>
