<?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 k r smith on Medium]]></title>
        <description><![CDATA[Stories by k r smith on Medium]]></description>
        <link>https://medium.com/@krsmes?source=rss-25247aa8d11------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*uuFW9Q9mLWP2RlLn.jpeg</url>
            <title>Stories by k r smith on Medium</title>
            <link>https://medium.com/@krsmes?source=rss-25247aa8d11------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:05:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@krsmes/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 Tech Lead]]></title>
            <link>https://medium.com/@krsmes/the-tech-lead-18b9aab4a0ed?source=rss-25247aa8d11------2</link>
            <guid isPermaLink="false">https://medium.com/p/18b9aab4a0ed</guid>
            <dc:creator><![CDATA[k r smith]]></dc:creator>
            <pubDate>Fri, 27 Mar 2015 16:15:21 GMT</pubDate>
            <atom:updated>2015-03-28T14:42:59.434Z</atom:updated>
            <content:encoded><![CDATA[<p>If I have one dirty little secret to being a tech lead, it is this: I don’t do it.</p><p><em>I’m a lazy person. I don’t like stress. I’m old enough to know that most problems resolve on their own.</em></p><p>Any decently sized team will have two competing personalities on it. One person that thinks they should be the tech lead, but they should not. And one person who does not think they are capable of being a tech lead, but they are.</p><p>These personalities are relative, sometimes it is obvious, sometimes it is more subtle.</p><p>As a <em>designated </em>tech lead I try to identify two people on my team that are the extremes of those two personalities. If I can keep the lid on the person that thinks they should be tech lead (but they really shouldn&#39;t) and take the lid off the person who is full capable of providing technical leadership (but are sure they are not ready) then I’m set.</p><p><em>That’s it.</em></p><p>The technology, the atmosphere, the seating arrangement, the cadence, the deadlines… all of that is secondary to making sure that each individual’s capabilities are being used to their maximum potential.</p><p><em>But how?</em></p><p>From my experience I can tell you that the most difficult aspect of this is getting the maximum potential out of the person who thinks they should be the lead. The reason they should not be the tech lead is simply lack of experience (nothing to do with age) — they haven’t gotten burned enough, or in the right ways. This is the person that unknowingly steps on the rest of your team’s toes, or makes promises that can’t be met, or has an ironically rigid definition of agility, or thinks agile means anything goes.</p><p>It is not your job to squash this person and put them in their place. “Keep a lid on it” refers to keeping things under control, from boiling over, not shutting them down. It is your job to let them lead to the extent they are capable. At the point they start crossing boundaries it’s your job as <em>designated </em>tech lead to override and take the hit for doing so. This ability is called tact.</p><p>The second most difficult aspect, and more time consuming than the first, is getting the maximum potential from the more than capable but undervalued person (and usually, undervalued by their own self). This is likely a quieter person, but not always. It is someone who has been around long enough to have many necessary experiences under their belt — but in too many cases they have been burned by these experiences to the point of making them overly skeptical. (In other cases this person just thinks they are more junior than they really are. From your perspective you can recognize what they can not see.)</p><p>It is not your job to set this skeptic up, but to prop them up. By leaning on these individuals for very specific decisions and responsibilities you can bring them from the edge and give the confidence they need. It is your job to get to know them and push them just enough out of their comfort zone. Then, as the <em>designated</em> tech lead, take the hit for doing so. If things go poorly, take responsibility; if things go well, give away the credit. This is called humility.</p><blockquote><strong>Note: these two personalities balance each other. If you end up with a small enough team that you can only identify one of the two then in all likelihood you’re the other one.</strong></blockquote><p>Grow your own replacements — and I mean this literally: if at all possible join a project as team member under the leadership of someone you used to ‘lead’… and then continue to focus on their success from that new vantage point.</p><p><em>Easier said than done.</em></p><p>Yes, you’ll screw it up. You won’t communicate perfectly. You’ll make some decisions that turn out to be wrong and will have to backtrack. You’ll step on someone’s toes at just the wrong time. You’ll be at a loss for the right answer at a critical point. You’ll come across to someone in a way you never intended. You’ll end up on a project that is doomed. But say you have a team of six: you have six leaders at various stages of development, plus yourself — just co-ordinate and support each other.</p><p>Acknowledge that these people on your team who are supporting you <strong>are </strong>smarter than you. They all bring something unique to the table — be lazy: extract and use it.</p><p>If you can balance the above two personalities, you’ll have little else to do to carry out a project successfully.</p><p>I believe leadership is about identifying who needs to be toned down and who needs to be amplified and then doing so with tact and humility.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18b9aab4a0ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>