<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team Performance on Rough Edges</title><link>https://roughedges.dev/tags/team-performance/</link><description>Recent content in Team Performance on Rough Edges</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Apr 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://roughedges.dev/tags/team-performance/index.xml" rel="self" type="application/rss+xml"/><item><title>What Engineering Managers Are Actually For</title><link>https://roughedges.dev/posts/what-engineering-managers-are-actually-for/</link><pubDate>Sat, 25 Apr 2026 00:00:00 -0400</pubDate><guid>https://roughedges.dev/posts/what-engineering-managers-are-actually-for/</guid><description>&lt;p&gt;There&amp;rsquo;s a version of engineering management that shows up in a lot of technical writing: the EM as scorekeeper. They track metrics, run processes, attend meetings, and get out of the way of the engineers who do the real work. In this view, a great engineering team almost doesn&amp;rsquo;t need a manager – and a manager who does too much is probably just creating noise.&lt;/p&gt;
&lt;p&gt;That view is wrong, and the teams that operate on it tend to show it eventually.&lt;/p&gt;</description></item></channel></rss>