<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sean Gillies (Posts about teams)</title><link>https://sgillies.net/</link><description></description><atom:link href="https://sgillies.net/tags/teams.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 31 Dec 2023 01:26:25 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Silos and opportunities</title><link>https://sgillies.net/2019/01/10/silos-and-opportunities.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;I've been reading and linking to Subbu Allamaraju's blog for more than
a decade. &lt;a class="reference external" href="https://m.subbu.org/the-value-is-in-dealing-with-the-messy-stuff-d535f5f42b39"&gt;The Value is in Dealing with the Messy Stuff&lt;/a&gt;
is a post about learning to see messy problems as opportunities and learning to
see silos as tools for solving messy problems. Mapbox, where I work, is exactly
at the stage where this mindset is helpful. Subbu uses team and silo almost
interchangeably, but I don't think it's intended that the reader equate them.
A team is part of an organization's model of how problems get solved and silos
are part of the observed reality of how problems get solved.&lt;/p&gt;</description><category>engineering</category><category>problems</category><category>teams</category><category>work</category><guid>https://sgillies.net/2019/01/10/silos-and-opportunities.html</guid><pubDate>Thu, 10 Jan 2019 15:39:11 GMT</pubDate></item></channel></rss>