<?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[Practical Empathy - Medium]]></title>
        <description><![CDATA[How to lead people and be a manager - Medium]]></description>
        <link>https://medium.com/practical-empathy?source=rss----f607fd2a90ef---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Practical Empathy - Medium</title>
            <link>https://medium.com/practical-empathy?source=rss----f607fd2a90ef---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:35:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/practical-empathy" 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 work to “close” a candidate began months ago]]></title>
            <link>https://medium.com/practical-empathy/the-work-to-close-a-candidate-began-months-ago-97acdd6410d?source=rss----f607fd2a90ef---4</link>
            <guid isPermaLink="false">https://medium.com/p/97acdd6410d</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Joe Greenheron]]></dc:creator>
            <pubDate>Fri, 25 Oct 2019 21:29:34 GMT</pubDate>
            <atom:updated>2021-05-25T21:06:08.324Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pIMwlLUc3Nk6zQlS7HQhLg.jpeg" /><figcaption>Actual recent Scrabble tiles</figcaption></figure><p>I’ve recently “closed” a couple candidates. By “closed”, I mean “was brought into a candidate’s life at the ‘offer’ stage, as one last contact to nudge them to accept.”</p><p>It’s not something I’ve done much in the past¹, so like anything else new and important, I’ve been figuring out how to get better at it. After a particular “close” phone call, I thought about what the ideal conversation would have sounded like.</p><p>My theory is that it comes down to two things:</p><ol><li><strong>Integrity</strong>: Be yourself and tell the truth (good advice for any walk of life!)</li><li><strong>Quality</strong>: Tell the candidate what they want to hear to increase the odds of accepting the job</li></ol><p>The only stuff at the intersection of these two is the results of <strong>the effort you’ve already put in to make your team an awesome place to work</strong>.</p><p>So focus on whatever that means to you, now, and by the next time you’re closing a candidate, you can be yourself, tell the truth, <em>and</em> increase the odds of the candidate accepting the job.</p><p>Seems simple, almost tautologically so. The complexity is in figuring out what is that vision of your perfect team², being honest about where the team is now, and putting in the labor to move things in the right direction. How to do that is a post for another day.</p><p><strong>Update, 2 years later</strong>: if you really do need to close a candidate today and are just reading this now, here’s a template (pick any/all that apply):</p><ul><li>Tech has not yet disrupted this $N billion dollar industry. [Current problems in industry, e.g. highly inefficient].</li><li>[Similarities between the candidate’s current job/industry and yours]. You’ll hit the ground running on day one</li><li>You’ll help save the planet by [environmental or social mission]</li><li>You’ll get to work with awesome people, including [names of people on interview loop that candidate has met]</li><li>You’ll get rich, given that we will IPO and become the largest company in this industry</li></ul><p>¹ I have more experience as hiring-manager, where you have the benefit of being point-of-contact with the candidate for most of their journey through the pipeline, but the disadvantage is that by the “offer” stage, you’ve (ideally) already told them everything great about your company.</p><p>² I’m not trying to claim that any team I’ve ever supported is perfect. Just that — all other things being equal — the closer the team is to that ideal vision, the better the team is functioning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97acdd6410d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-empathy/the-work-to-close-a-candidate-began-months-ago-97acdd6410d">The work to “close” a candidate began months ago</a> was originally published in <a href="https://medium.com/practical-empathy">Practical Empathy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From inbox-zero to todo-list-zero]]></title>
            <link>https://medium.com/practical-empathy/from-inbox-zero-to-todo-list-zero-cb273137d1a7?source=rss----f607fd2a90ef---4</link>
            <guid isPermaLink="false">https://medium.com/p/cb273137d1a7</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Joe Greenheron]]></dc:creator>
            <pubDate>Fri, 06 Sep 2019 22:36:48 GMT</pubDate>
            <atom:updated>2025-12-26T18:16:40.805Z</atom:updated>
            <content:encoded><![CDATA[<h3>From inbox-zero to todo-list hero</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6lao6wc0ZhUoREIUFdVQg.png" /><figcaption>The most Type-A calendar you’ll ever see</figcaption></figure><p><em>[Preamble to software engineers or anyone else on </em><a href="http://www.paulgraham.com/makersschedule.html"><em>maker-time</em></a><em>: you keep doing you, the following might sound absurdly overengineered. I wrote this article with managers in mind]</em></p><h3>Inbox-Zero</h3><p>I have a confession to make: <em>I’m the type of person who gets to inbox-zero daily</em>. I sheepishly admit this, because in a world where <a href="https://globalnews.ca/news/3343760/the-cult-of-busyness-how-being-busy-became-a-status-symbol/">busy equals productive</a>, it almost seems like a dereliction of duty to not have an inbox bursting at the seams.</p><figure><img alt="Gmail window showing “No new mail!”" src="https://cdn-images-1.medium.com/max/747/1*dzPO06G29wHVFkljiAFvKQ.png" /><figcaption>Proof of Inbox Zero</figcaption></figure><p>Mission Accomplished, right? Inbox-Zero is the pinnacle of productivity achievements.</p><p>Well, here’s a second confession: my inbox-zero is more of <em>a productivity sleight-of-hand</em>, as I ruthlessly move emails that require my time and attention to my to-do list, which conveniently sits beside my inbox¹:</p><figure><img alt="Gmail window showing “No new mail!” with three tasks lists next to it, each showing to-do items." src="https://cdn-images-1.medium.com/max/1024/1*rgF-jeH-sPFSNxMzKVqkcA.png" /><figcaption>To-do lists are grouped by the “Urgent-Important Matrix” from 7 Habits of Highly Effective People²</figcaption></figure><p>So inbox-zero doesn’t mean sitting on the beach with a cocktail. It simply means I’ve triaged all incoming requests (for now) and have a sense of everything I need to do. (I push my own items directly onto my to-do lists, bypassing the inbox, by sending mail to a secret email address³).</p><h3>Todo-list-Zero</h3><p>Back when I was making the transition from Tech Lead to Actual Manager, my manager gave me some advice which seemed outlandish at the time: “<em>as a manager, every item on your to-do list is an exception</em>.” She meant it as an extreme lesson in delegation, in other words:</p><ol><li>try to delegate everything</li><li>but keep the things on your own to-do list that you can’t delegate</li><li>and see those as an opportunity to get better at delegation. (i.e. an opportunity to uplevel your people at new tasks, in the future)</li></ol><p>Now that I’ve been managing for a while, I still see the wisdom in this, and I also take a second lesson from her advice:</p><p><em>Items on your to-do list are unfunded mandates unless they’re also on your calendar.</em></p><p>You can prioritize, bucket, and color-code your to-do list at nauseum but unless you make the time to actually DO them, the list is worthless as a productivity tool.</p><p>As a manager, your time is your most precious resource⁴. You’re constantly getting pulled into meetings, and unless you take control over your calendar, you’ll find it completely full of low-leverage activities. <strong>Your time belongs to you and nobody else</strong>. This applies equally to the CEO and the entry-level employee.</p><h3>“Your calendar is SO full, how can you cope?”</h3><p>I hear this from people trying to book meetings with me. The silly thing about the statement is that everyone fills their day with “work” (in the broadest definition of the word) so a new meeting will necessarily preempt something else. The only difference is that I’ve made it explicit by filling up my calendar with the blocks of time I think I’ll need to complete the highest priority tasks on my to-do list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6lao6wc0ZhUoREIUFdVQg.png" /><figcaption>Salmon color = time spent on my team’s goals and/or improving its culture</figcaption></figure><p>You’ll note that I also use color-coding so I can see at-a-glance whether or not I’m spending my time on things that are helping me achieve my and my team’s goals. If an incoming invite doesn’t cleanly map to a calendar color, it’s a signal that it’s probably not valuable for me to spend my time on.</p><h3>Summary/Philosophy</h3><p>To sum this up:</p><ol><li><strong>Your time belongs to you</strong> and nobody else. Even if you work for a salary.</li><li><strong>Inbox Zero</strong>: Stuff in your inbox that needs your attention should go immediately onto your to-do list.</li><li><strong>Todo List Zero</strong>: Stuff on your to-do list that needs more than a moment to resolve should get onto your calendar.</li><li><strong>Block out time</strong> in advance for #3, at the time of day where you get your best work done (figure this out if you don’t already know). Also block out time for self-initiated tasks: time to do nothing but think, time to learn and read, etc.</li></ol><p>My closing thought is whether Step 2 is even necessary. Is there a good system where emails/slacks/whatever go directly onto one’s calendar? I may experiment with this, but I think the to-do list is still necessary in order to prioritize and generally provide a buffer between incoming requests and the expenditure of one’s time.</p><p>Thank you to Joanne Zhu for listening to me think out loud about this and help guide my thinking on the topic.</p><p>¹ I use a simplified version of <a href="https://www.dansilvestre.com/gtd-gmail/">GTD Gmail</a></p><p>² <a href="https://www.forbes.com/sites/ericjackson/2012/07/24/the-only-thing-you-need-to-remember-about-the-seven-habits-of-highly-effective-people/#53f0d68f67f7">Here’s a good TLDR of the entire book, and an explainer on why the “Urgent-Important Matrix” is the most important concept of the book</a></p><p>³ See the link in footnote 1 for how to set this up.</p><p>⁴ As a <em>mortal being</em>, time is your most precious resource. Unlike money (and most other valuable things) you can never earn it back.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb273137d1a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-empathy/from-inbox-zero-to-todo-list-zero-cb273137d1a7">From inbox-zero to todo-list-zero</a> was originally published in <a href="https://medium.com/practical-empathy">Practical Empathy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The state of hiring an Engineering Manager in 2019]]></title>
            <link>https://medium.com/practical-empathy/the-state-of-hiring-an-engineering-manager-in-2019-6b72d5247f7c?source=rss----f607fd2a90ef---4</link>
            <guid isPermaLink="false">https://medium.com/p/6b72d5247f7c</guid>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Joe Greenheron]]></dc:creator>
            <pubDate>Fri, 24 May 2019 18:16:01 GMT</pubDate>
            <atom:updated>2019-07-16T16:33:27.144Z</atom:updated>
            <content:encoded><![CDATA[<h4>5 things I learned by spending four months job-hunting for a Software Engineering Manager role</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s9Wkz3AGIsMqGbmLmxKwZA.jpeg" /></figure><h3>How to hire a bodyguard</h3><p>Hiring knowledge-workers is difficult. People on a hiring-team get a few hours with a candidate, and then they’re forced to decide whether they want to spend 8–10 hours a day sitting next to this person, 5 days a week, for the next few years of their lives.</p><p>If I wanted to hire a bodyguard, the most important thing I’d need to know is whether they’d take a bullet for me. But I can’t determine that with certainty in a meeting room. And given 60 minutes together, it’s hard to even simulate a situation in which I could know for sure how a potential bodyguard would react in a life-or-death situation.</p><p>Most software development isn’t life-or-death but the analogy is apt. You have one most important thing you’re looking for in a candidate: it might be general like “do they fit with — and improve — our values?”, or specific like “we need to hire a subject matter expert in Foo.” You need to gauge their fit for this one thing with very limited data, over the course of a few hours.</p><p>For interviewing engineers, we (as an industry) have mostly moved from “can they write code on a whiteboard?” as the prevailing proxy, to a post-whiteboard-coding world where we’ve improved the realism of the process (e.g. with coding homework challenges and pair-programming interviews), at the expense of standardization (a great trade-off to make).</p><h3>The 5½ things I learned</h3><p>Management is a discipline that requires a referent: some outcome (e.g. a goal or project) or process (e.g. onboarding) to be managed. (“<a href="https://thegeekyleader.com/2014/09/28/you-manage-things-you-lead-people/">You manage things, you lead people</a>”) This makes it even harder to evaluate in the sterile world of interview loops.</p><p>So when I decided to throw my hat into the Engineering Manager (EM) ring a few months ago, I had no idea what to expect. First off, this was my first time interviewing as an EM, since I grew into a management role at my former company (i.e. I interviewed there as a software developer, and transitioned to management).</p><p>Here’s what I learned (scroll to the end for the basic facts about # of interviews I did, etc.)…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3jA8_xJofzC_InFseiZncg.jpeg" /></figure><h4>1. I got more info about each company’s interview process than I imagined I would</h4><p>One thing that’s drastically improving over time is the “information asymmetry” between the employer and job-seeker. In ancient interview experiences (circa 2013 and earlier), you’d get a date and a place to show up, and that’s about it unless you asked for more info.</p><p>This time, before almost every interview loop, I got lots of info about who was going to be interviewing me, and sometimes even what they’d be asking. I often got a list of the company values (most companies also post these publically on their websites).</p><p>Many companies offered a one-pager about “what to expect during your interview”, covering everything from what’s for lunch to what I should wear. It’s almost like every recruiter in the industry got tired of candidates asking “Will you please give me more info about what to expect?” and decided to preempt the question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-6U6SqZlh3msQi13JTX8w.jpeg" /></figure><h4>2. There isn’t a standard interview process</h4><p>EM interview loops are still all over the place. Maybe that’s a good thing? Orgs can decide what they want to optimize for, and index for that in the interview process?</p><p>Props to Stripe for having the most fascinating EM loop by far. It was capped by a grueling full-day at their SF headquarters, but what was interesting was that the format kept changing throughout the day (I knew this ahead of time, See #1 above). The first couple hours were traditional behavioral/<a href="https://www.themuse.com/advice/star-interview-method">STAR</a> questions (“Tell me about a time when…”).</p><p>And then shit got real. The next couple hours were role-plays, testing my leadership and managerial aptitude in the most realistic simulation possible. (I don’t want to give away too much here.)</p><p>The final two hours were split between a standard “how would you build a …?” architecture question (which was misleadingly billed as a collaborative “Design Discussion,” but my interviewer didn’t really collaborate with me so I did all the work myself!), and ended with me giving a presentation to a small panel about something I’d built in the past. (98point6 also does this.)</p><p>By the end of the day, I’d talked with 12 Stripe employees. When you add that to the recruiter and hiring-manager phone screens, and a mini-loop in their Seattle office, I had contact with 17 people from Stipe by the time they made their decision!</p><p>Overkill, perhaps, but if you want to de-risk a hiring decision, this is how you do it. (<a href="https://stripe.com/atlas/guides/scaling-eng#recruiting-and-hiring">Read more about how Stripe approaches hiring</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eOLVl5V9Wddh_r5EVeaneA.jpeg" /></figure><h4>3. Few firms over-indexed on vocational skills</h4><p>I’ll leave this company anonymous, since I don’t think the following is their fault. They just didn’t know what they were looking for (they wanted a unicorn: an experienced EM with strong coding skills, who could spin up a new business-unit, and simultaneously open their new Seattle engineering office. If you know of someone who can do all this, I have a great company to connect you with).</p><p>After an hour with their CEO — who gave me one of the best product demos I’ve seen in a long time — I was subjected to two hours of <em>deep</em> technical questioning, stuff like CDNs and finding neighbors in a cartesian system.</p><p>This might be the exception that proves the rule. Most companies had the philosophy of “you need to be technical enough to add value to the work your team does, but we’re hiring you for your team-building skills” and the content of the interview reflected that.</p><p>Some companies had so little technical content in their process, I was a bit worried that the system might give false-positives to an experienced bullshit artist. Again, I won’t name names, though there was a company that did a full-day loop and only spent about 20 minutes on technical content (the standard architecture question, “How would you design a…?”)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wORcoscGRSewTpKqhhgexQ.jpeg" /></figure><h4>4. Instead, it’s values <strong><em>Values</em></strong> VALUES (Advice nugget #1)</h4><p>Instead of vocational skills, the zeitgeist in hiring right now (especially for management roles) is “values fit.” If I could give one suggestion to EM interview candidates, it’s to <strong>internalize the company’s values and work them into the discussion as much as possible.</strong></p><p>If the values aren’t on the company’s website and the recruiter doesn’t send them to you, ASK! They’ll likely be all over the walls when you get to the office. Convoy even has them on laminated card in all of their meeting rooms. Shame I spent the entire evening before my interview there memorizing them :)</p><h4>5. Focus on the value you’ll add (Advice nugget #2)</h4><p>An alternate definition of “value” comes into play as well, and leads to my second second piece of advice (this isn’t anything new and it will always be good advice): <strong>find the BIGGEST problem the org is facing</strong> (the sooner the better, ideally in your first conversation with the recruiter), and <strong>position yourself as the person who will solve that problem</strong>.</p><p>When you think about it, <a href="https://www.forbes.com/sites/georgebradt/2011/04/27/top-executive-recruiters-agree-there-are-only-three-key-job-interview-questions/#6a9ee78c6f35">there are really only three interview questions</a>:</p><ol><li>Are your strengths a match for this job? (Can you do the job?)</li><li>Is your motivation a match for this job? (Will you love the job?)</li><li>Are you a fit for the org’s culture and values? (Can I work with you?)</li></ol><p>Crafting your message around solving the org’s biggest problem answers the “Can you do the job?” question in a big way.</p><p>Although they come disguised as various unique issues, there are really a finite number of “biggest problem patterns” that an org faces (scaling, org structure, tech debt, product/market fit, etc). Once you find the problem, use <em>their language</em> when you talk about your experience solving it in the past.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NlPXfUlVnxNyNLRg_dxNLQ.jpeg" /></figure><h4>Bonus: Remote loops are a thing</h4><p>I interviewed for two remote roles: Healthify and 7 Cups. The former is based in NYC with about a 50/50 split between HQ and distributed. The latter is fully distributed. Both are awesome companies.</p><p>The “loop” for remote companies is a bit different, since you might interview with one person at a time, then get a follow-up with the recruiter, then schedule your interview with the next person, etc. This may spread the interview over the course of a couple weeks, making it harder to connect the dots between the answers to your questions (<strong>Advice nugget #3</strong>: think of some good questions to ask <em>everybody</em> you talk to, and triangulate your answers) or know how you’re performing.</p><p>The obvious benefit to this is that you spread out the energy-draining full day loop over a longer period of time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5l6uIry_E7qVxotS-xJcUg.jpeg" /></figure><h3>Conclusion</h3><p>I interviewed (in-person or via teleconference) at 8 companies over the course of four months. If you include companies where I did a phone-screen but didn’t proceed further, it was 14 companies in all. I ended up getting 2 offers (so far…)</p><p>This was accurate as of mid-2019, but with a discipline that’s as new and dynamic as Engineering Management, things are likely to change quickly (for the better, I hope). The only constant is change.</p><p>Hope this helps someone prepare for an EM interview. I’m happy to provide more information or details about particular companies that I didn’t feel comfortable telling to the entire internet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b72d5247f7c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-empathy/the-state-of-hiring-an-engineering-manager-in-2019-6b72d5247f7c">The state of hiring an Engineering Manager in 2019</a> was originally published in <a href="https://medium.com/practical-empathy">Practical Empathy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to decide if you should become an engineering manager]]></title>
            <link>https://medium.com/practical-empathy/how-to-decide-if-you-should-become-an-engineering-manager-67ad956bd523?source=rss----f607fd2a90ef---4</link>
            <guid isPermaLink="false">https://medium.com/p/67ad956bd523</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Joe Greenheron]]></dc:creator>
            <pubDate>Mon, 06 May 2019 04:08:05 GMT</pubDate>
            <atom:updated>2019-05-06T04:13:27.414Z</atom:updated>
            <content:encoded><![CDATA[<h4>Don’t over-index on how much (or little) coding you think you’ll be doing as a manager.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G-SBaBvArv4MI8-qvXffGg.jpeg" /><figcaption>“Harana” by Natsue Makino</figcaption></figure><p>There are lots of articles written about what to do after you’ve decided to transition from engineer to engineering manager (see below), but not so many about how to make the decision in the first place. (I did find <a href="https://medium.com/@mvndrz/eng-mgmt-ep1-should-i-become-an-engineering-manager-beba99db4662">this one</a> which was a great read)</p><p>The conventional wisdom is to ask yourself the question “When I get to work in the morning and open my laptop, do I want to see an IDE or a spreadsheet?” In other words, do you want to continue writing code or not?</p><p>This is a dangerous way to decide since it puts the most traumatic part of the transition front-and-center: not writing (as much) code. Each new manager has to come to terms with writing less (or no) code in their new role, but it doesn’t need to happen right away.</p><p>Personally, I made my peace when I realized that management is a form of leverage (this’ll sound familiar to folks who’ve read <a href="https://www.goodreads.com/book/show/324750.High_Output_Management">High Output Management</a>): writing software is a high-leverage way to solve problems at scale, and when done well it can solve a lot of problems. Managing a team of software engineers — creating an environment where they can do their best work together — is much higher leverage, when done well.</p><p>So instead of focusing on whether or not you want to continue coding, instead focus on whether you want to learn and grow in the key skills of managing a team:</p><ul><li>hiring, training, and mentoring your team</li><li>fostering an environment of psychological-safety</li><li>providing clear measurements of — and tools for — success</li><li>constantly and consistently setting expectations</li></ul><p>You don’t need to be any good at this stuff right away. You do need to dedicate yourself to setting goals, failing, learning from failures, and being vulnerable as you take on a new role.</p><p>Think this is your path? Here are some great resources:</p><ul><li><a href="https://www.officevibe.com/complete-guide-new-manager">New Managers: The complete guide</a>: An incredible guide for new managers who seek to better understand their new role. Take the “New Manager Preparation Checklist” and follow up with your current manager, making sure you’re getting the support you need (this path can feel lonely sometimes) while you set clear and explicit expectations from the get-go.</li><li><a href="https://medium.com/@orenellenbogen/team-lead-here-is-what-your-boss-isnt-telling-you-yet-still-expects-of-you-69f0e174e534">What your boss isn’t telling you but still expects of you</a>: as a team lead, it’s your job to enable your company’s scalability.</li><li><a href="https://designerfund.com/bridge/thrown-into-management-lessons-learned-leading-thumbtacks-design-team/">Cheat-sheet for new leaders</a>: quickly build trust and keep the team engaged</li><li><a href="https://medium.com/@rands/the-new-manager-death-spiral-51a806b252dd">The New Manager Death Spiral</a>: management isn’t a promotion</li><li><a href="https://blog.newrelic.com/culture/measuring-manager-success/">Measuring Manager Success</a>: the biggest difference between being a manager and being a developer is in how you measure your success. The key to making processes work is to make incremental changes, measure them, and then improve them.</li><li><a href="https://www.quora.com/Management/What-are-common-mistakes-three-more-or-less-that-new-or-inexperienced-managers-make-What-could-be-done-differently/answer/Ian-McAllister">Common mistakes new leaders make</a>: covers mistakes in Performance Management, Career Development, Hiring, and much more.</li><li>Read the book “<a href="https://www.goodreads.com/book/show/33369254-the-manager-s-path">The Manager’s Path</a>”</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67ad956bd523" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-empathy/how-to-decide-if-you-should-become-an-engineering-manager-67ad956bd523">How to decide if you should become an engineering manager</a> was originally published in <a href="https://medium.com/practical-empathy">Practical Empathy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What does scientific research have to say about great leadership?]]></title>
            <link>https://medium.com/practical-empathy/what-does-scientific-research-have-to-say-about-great-leadership-505c8be0838c?source=rss----f607fd2a90ef---4</link>
            <guid isPermaLink="false">https://medium.com/p/505c8be0838c</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Joe Greenheron]]></dc:creator>
            <pubDate>Fri, 26 Apr 2019 21:15:47 GMT</pubDate>
            <atom:updated>2019-04-26T21:30:41.770Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RVcyGyiQJEoAZSnqn8AZYA.jpeg" /></figure><p>Few scientific studies have been done about leadership in tech companies, probably because it’s so hard to quantify and it’s difficult to design a study that includes participants from multiple organizations. Few companies are large enough to have the critical-mass of leaders necessary to get a sample size that allows researchers to make statistically-significant conclusions about their findings.</p><p>Despite all that, I know of at least two tech companies that have done large research studies about their managers:</p><ol><li>Google’s “<a href="https://hbr.org/2013/12/how-google-sold-its-engineers-on-management">Project Oxygen</a>” studied managers and found 8 common traits shared among the most successful</li><li>Facebook’s VP of People did <a href="https://www.businessinsider.com/facebook-best-managers-exhibit-these-7-behaviors-2016-1">a similar study</a> and found 7 common behaviors.</li></ol><p>Let’s take a look at what they have to say…</p><h3>Google’s Project Oxygen</h3><p>I can summarize the findings of this study in a TLDR: “love your people.” Project Oxygen identified 8 traits common to their best managers. Like love, the identified behaviors are rooted in action, so it’s difficult for managers to fake them.</p><p>Here they are in order of importance…</p><ol><li><strong>Be a good coach</strong>: Provide specific, constructive feedback which balances positive and negative. Have regular 1:1s, present solutions to problems tailored to employees’ specific strengths.</li><li><strong>Empower the team and don’t micromanage</strong>: Balance giving freedom to employees and being available for advice. Give “stretch” assignments to help the team tackle big problems.</li><li><strong>Express interest/concern in team members’ success and well-being</strong>: Get to know employees as people, with lives outside work. Make new members of the team feel welcome.</li><li><strong>Be productive and results-oriented: </strong>Focus on what the team needs to achieve, and how team members can help achieve it. Help the team to prioritize work. Use seniority to remove roadblocks.</li><li><strong>Be a good two-way communicator — listen to the team and share information: </strong>Hold staff meetings and be straightforward about messages and goals. Help your team connect the dots (to other teams, the company’s vision/mission, etc.). Encourage open dialogue, and listen to employees’ issues and concerns.</li><li><strong>Help employees with career development</strong>: Discuss goals at 1:1s and how they relate to long-term career path. (This sounds similar to #1)</li><li><strong>Have a clear vision and strategy for the team</strong>: Even in the midst of turmoil, keep the team focused on goals. Involve the team in setting your mission and vision, and making progress towards them. (I call this “<a href="https://www.inc.com/rhett-power/work-on-your-business-not-in-your-business.html">Work <em>on</em> your business, not <em>in</em> your business</a>”)</li><li><strong>Have key vocational skills that help advise the team: </strong>Prioritize conducting work side-by-side with team members, when needed.<br>Understand specific challenges of the job. (Interestingly this one is last on the list.)</li></ol><h3>Facebook’s research</h3><p>Facebook didn’t give their study a codename like Google, but their results are no less fascinating. They found 7 behaviors that stood out among their best managers:</p><ol><li><strong>Care about your team members: </strong>Make personal connections with your employees and actually want to see them succeed.</li><li><strong>Provide opportunities for growth</strong>, to constantly learn and develop your employees’ skills.</li><li><strong>Set clear expectations and goals: </strong>performance ratings should never be a surprise. Constantly let all employees know what is expected of them, as both individuals and members of a team.</li><li><strong>Give frequent, actionable feedback: </strong>Build a level of trust and transparency so your reports can adapt quickly and become more productive and effective.</li><li><strong>Provide helpful resources: </strong>without micromanaging, be aware of where each of your employees are at so you can remove roadblocks, provide insight or assistance.</li><li><strong>Hold your team accountable for success: </strong>employees<strong> </strong>need to know that you’ll adjust their responsibilities accordingly depending on their performance.</li><li><strong>Recognize outstanding work:</strong> the most engaged employees work in an environment where impactful results are celebrated.</li></ol><h3>Meta-analysis</h3><p>A few themes jump out that are common to both Google and Facebook:</p><ol><li><strong>Coaching/caring</strong>: Help everyone on your team with career development, provide opportunities for growth</li><li><strong>Two-way communicator</strong>: listen and share, provide frequent actionable feedback</li><li><strong>Empower your team</strong>: hold your team accountable for success, recognize outstanding work, advise — and provide resources to — team members without micromanaging them.</li><li><strong>Have a vision and strategy</strong> for the team, be results-oriented, and help the team prioritize work.</li></ol><p>Lastly, it’s interesting that the strength of vocational/technical skills didn’t show up until the last item on Google’s list and isn’t present at all in Facebook’s results. Yet Engineering Manager interview loops still over-index on vocational experience, at the expense of the above traits that are scientifically correlated with success. You can coach a basketball player on shooting free throws, but you can’t coach them on being taller.</p><p>If you’re looking for a framework to improve your skills as a leader, you could do worse than one that’s backed by science!</p><h3>Bonus! Pitfalls</h3><p>Google’s research also identifies three pitfalls for managers. Be careful you’re not doing any of these:</p><ol><li><strong>Trouble making a transition into a team</strong>. This is often the case when a fantastic engineer is promoted to management without having the skills to do their new job (<a href="https://docs.google.com/document/d/105zJa4amlYs_60lf1uSSmASNP7w1ADZh65K8Go5z8Ac/edit">If this describes you, I can help</a>). But even experienced managers hired from outside the org may not understand the unique aspects of managing at your org.</li><li><strong>Lack of a consistent approach to performance management or career development. </strong>It’s critical to help employees understand how these things work at your company, and to coach them on their options for development. Be proactive, don’t wait for employees to come to you with these topics.</li><li><strong>Spending too little time managing and communicating</strong>. Setting context is your job, so you should do a lot of it. Unless your team is saying things like “Stop giving us so much helpful information about our business objectives!” you’re probably not communicating enough.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=505c8be0838c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-empathy/what-does-scientific-research-have-to-say-about-great-leadership-505c8be0838c">What does scientific research have to say about great leadership?</a> was originally published in <a href="https://medium.com/practical-empathy">Practical Empathy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Leaders Eat Last” Book Report]]></title>
            <link>https://medium.com/practical-empathy/leaders-eat-last-book-report-ff21afbd1ca8?source=rss----f607fd2a90ef---4</link>
            <guid isPermaLink="false">https://medium.com/p/ff21afbd1ca8</guid>
            <category><![CDATA[simon-sinek]]></category>
            <category><![CDATA[neuroscience]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Joe Greenheron]]></dc:creator>
            <pubDate>Mon, 15 Apr 2019 21:59:49 GMT</pubDate>
            <atom:updated>2019-04-15T21:59:49.621Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1yeb8tBT_ANpxnFcHIaqRQ.jpeg" /></figure><p>This isn’t even a “book” report since I didn’t read the book by that title, I just watched <a href="https://www.youtube.com/watch?v=ReRcHdeUG9Y">a 45 minute TED-ish talk by the author</a>. But I think I got the gist of the message, and here it is:</p><p>Humans survived in part due to four brain chemicals: Endorphins, Dopamine, Serotonin, and Oxytocin.</p><p>The first two can be triggered on one’s own:</p><p><strong>Endorphins</strong> mask pain. They were an evolutionary advantage because the masking of pain allowed us to hunt food over long distances. Today, most of us don’t need to run to catch food, but just listening to a runner describe their “runner’s high” makes you realize how little we’ve evolved physiologically in the past 100,000 years, even though everything around us has changed.</p><p><strong>Dopamine</strong> is the pleasure derived from getting something done. It’s very addictive. Just think of how people write already-completed tasks onto a to-do list, just so they can cross off the task immediately, releasing dopamine. This tendency is hijacked by app developers to get you to use their apps more (it usually takes the form of the ubiquitous “red circle with a number of unread messages” that you can’t help but click on).</p><p>The other two brain chemicals require social interaction to be released:</p><p><strong>Serotonin</strong> is<strong> </strong>the<strong> </strong>“relationship chemical”. It’s the feeling of public pride, it produces confidence (just watch a graduation ceremony) or “naches” if you’re related to Yiddish speakers. It has an aspect of social and familial obligation. We’re driven to “win one for the coach” and to “make our parents proud”.</p><p>Relationship strength can faked, using false signals. Money is used as a proxy for trustworthiness, so a conspicuous display of wealth confers a higher status. But those fancy material objects weren’t necessarily gained via strengthening social relationships.</p><p>Serotonin — and the drive to strengthen relationships — keeps social order: we evolved to favor strong relationships so that all members of a group would trust each other. Otherwise it’s just survival of the fittest.</p><p>Within a social group that has bonds between all members, the survival of the group is a collective concern. There needs to be a shared sense of who is going to protect us from outside threats. These are the Alphas. We constantly assess who is Alpha, as they get to eat and mate first. This is why we try to raise our own status, so we can eat/mate first. This is why fake Rolexes exist.</p><p>Being an leader comes at a cost: Alphas run towards danger and put themselves at risk to protect the group. This is why the bank failures of the late 2000’s were such an outrage. Not only did a bunch of people we thought we could trust ended up losing all our money, but they were the fancy and aggressive Alphas, who were compensated so highly because they were put in a position of trust. Instead, the ended up golden-parachuting out of the crashing economy, while the rest of us lost our jobs and homes.</p><p>The final chemical is <strong>Oxytocin</strong>,<strong> </strong>which is released during moments of<strong> </strong>love, trust, and friendship. It signals that we’re safe. That someone’s got my back. You can get it from physical contact, which is why shaking hands is important. Both parties get oxytocin, even witnesses get it by watching a handshake! If you ever want a reminder how we’re no different from other primates, try to close a deal with someone for a large transaction. When they offer their hand to shake yours, decline the handshake and watch the deal fall apart.</p><p>You can also get Oxytocin from being generous with your time and energy (gifts of money won’t work). It must be a true sacrifice on your part, which is why an email saying “great job!” usually rings hollow but a small thoughtful gift for a job well done is something that the recipient might keep forever. Is this starting to sound like leadership?</p><p>Oxytocin has many benefits: it boosts the immune system and inhibits addiction. It takes time to build up in your system, which is why most people don’t get married after their first date.</p><p>Let’s apply the above to the business world: external dangers are constant (e.g. competition), but internal dangers (inside the company) are variable, and determined by leaders. When groups feel safe, they can work together to face external dangers.</p><p>Leaders decide:</p><ol><li>Who gets in the circle of safety/belonging and who stays out</li><li>How big the circle should be. Is everyone inside, or just an “inner circle” of top execs?</li></ol><p>The best Leaders make sure everyone under them feels safe, so those people make those under <em>them</em> feel safe, on down the line, so that everyone at the company can look externally: making customers feel safe.</p><p>Oh, there’s one more chemical worth mentioning: <strong>Cortisol</strong></p><p>It’s released during times of stress and anxiety. It triggers the “fight or flight” response. It stiffens muscles and raises heart-rate. It’s even communicable in social groups.</p><p>That extra energy required to heighten our awareness saps energy from our other biological systems: growth, immune system, etc.</p><p>Unsafe environments cause constant drips of Cortisol and suppress Oxytocin. Our body’s stress systems were designed to handle a brief but intense period of do-or-die stress: there’s a tiger chasing me and I either outrun/outsmart it, or I’m eaten.</p><p>A situation like that has a clear resolution after minutes or even seconds. Today’s stressful situations (a bad boss, a toxic relationship, poverty) play out over the course of months or years, and rarely reach a resolution. Our bodies simply aren’t built to handle that type of stress, which is why it’s so physically and mentally detrimental.</p><p>That’s why <strong>Leadership isn’t a position, it’s a choice to protect and sacrifice for those around you so they feel safe and not stressed. </strong>Leadership is an action:<strong> </strong>it’s the act of giving to others, and they will give to others in turn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff21afbd1ca8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-empathy/leaders-eat-last-book-report-ff21afbd1ca8">“Leaders Eat Last” Book Report</a> was originally published in <a href="https://medium.com/practical-empathy">Practical Empathy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The hardest conversation]]></title>
            <link>https://medium.com/practical-empathy/the-hardest-conversation-480d03c73a6f?source=rss----f607fd2a90ef---4</link>
            <guid isPermaLink="false">https://medium.com/p/480d03c73a6f</guid>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Joe Greenheron]]></dc:creator>
            <pubDate>Fri, 05 Apr 2019 21:35:13 GMT</pubDate>
            <atom:updated>2019-04-05T21:35:13.606Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zct2sZl_DqSrUD3Pi9ecIQ.jpeg" /><figcaption>Hostess bows to guest in a traditional tea ceremony. Japan, Oct 2017</figcaption></figure><p>Conventional wisdom in management is that the hardest conversation to have with an employee is the “termination”, where you’re letting an employee know that this is their final day at your company, usually due to an uncorrected performance problem.</p><p>I don’t want to minimize the challenges of having this conversation. It’s the worst conversation a manager can have. It’s soul-crushing. It never gets easier.</p><p>But the “termination” discussion is only the <strong>second-hardest conversation</strong> a manager can have with an employee. The hardest conversation is the one that precedes the termination, which I call the <strong>“job in jeopardy”</strong> (JIJ) conversation.</p><p>Here’s why:</p><p>If a manager screws up the termination discussion, the consequences could be pretty bad: the employee won’t leave the company with the dignity they deserve; the manager won’t communicate their own role in the situation (e.g. were they not coaching the employee effectively enough?).</p><p>But no matter how bad it’s botched, the result is mostly the same: the employee gathers their stuff, and is escorted out of the building. The manager gathers the remaining team, explains what happened, and reassures them that they’re not next.</p><p>On the other hand, the JIJ conversation is the last chance to pull up on the yoke before <strong>the plane crashes into the ground</strong>. In other words, the difference between a perfectly executed JIJ and a botched one is HUGE.</p><p>In the perfect situation, the manager is clear with the employee about what specifically needs to change about their performance and why (<strong>context</strong>), what change looks like (<strong>goals</strong>), the consequences of either path (turnaround or not), and pledges <strong>support</strong> through the process. And lets the employee know they can fix this!</p><p>In the botched situation, none of the above happens because, e.g., the manager is stuck thinking that <a href="https://firstround.com/review/radical-candor-the-surprising-secret-to-being-a-good-boss/">ruinous empathy</a> is the kindest way to approach this problem. That’s what the brains of conflict-adverse folks trick their mouths into believing, but the opposite is true: clear is kind.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=480d03c73a6f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-empathy/the-hardest-conversation-480d03c73a6f">The hardest conversation</a> was originally published in <a href="https://medium.com/practical-empathy">Practical Empathy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First post]]></title>
            <link>https://medium.com/practical-empathy/first-post-96507e7623b?source=rss----f607fd2a90ef---4</link>
            <guid isPermaLink="false">https://medium.com/p/96507e7623b</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Joe Greenheron]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 22:17:03 GMT</pubDate>
            <atom:updated>2019-04-05T18:44:16.609Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s always a blog post about writing a blog post</h4><blockquote>Establish a reputation in your field as someone who delivers measurable results vis-a-vis improving revenue or reducing costs.</blockquote><p>— <a href="https://www.kalzumeus.com/2012/01/23/salary-negotiation/">Patrick McKenzie</a> (patio11)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TSuLSmer36dvDTDiUBQZKA.jpeg" /></figure><p>I’ve spent many years working on the “delivers measurable results” part of that formula, but not so much on the “establish a reputation in your field” part. Mostly because the latter is often a distraction from the former.</p><p>Most excuses to not be blogging crumble under even basic scrutiny:</p><ul><li>“I don’t have any time!” … I’m at level 70 on Wordscapes so I clearly have time for something.</li><li>“I don’t have anything interesting to say that hasn’t already been said (better) by others!” … this one’s worth digging deeper into…</li></ul><p>Maybe I have something worth sharing? I’ve spent years curating <a href="https://docs.google.com/document/d/1R1O0OEsQpZcBcLheRlomDrmR2tyEpdRNFnjbLALmbH4/edit">the Tech Leadership Field Guide</a>, mostly without any fanfare, and recently thought to myself “What if I turned all that great content into a book?” The first problem is that 99% of it isn’t my content, so that might get me into legal trouble in book form… but not in blog form!</p><p>So here goes a deeper dive into many of the best topics from the Field Guide. If just one person learns just one thing and it saves them from making just one of the many mistakes I’ve made along the way from Software Engineer to Team Lead to Engineering Manager to Director of Engineering — it’ll have been worth the writing.</p><p>BTW, the name of this blog is a poke at “Tactical Empathy”, a silly concept from an otherwise amazing book called “<a href="https://info.blackswanltd.com/never-split-the-difference">Never Split The Difference</a>”. “Tactical empathy” is like the “truck nuts” of interpersonal skills: totally unnecessary because the original works just fine, but around anyway because men are too insecure to talk about the original.</p><h3>ronnie chen on Twitter</h3><p>I once attended a workshop led by a FBI hostage negotiator about negotiating and his BIG SECRET was &quot;tactical empathy&quot; aka regular empathy but For Men™ and anyways I still think about that a lot</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96507e7623b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-empathy/first-post-96507e7623b">First post</a> was originally published in <a href="https://medium.com/practical-empathy">Practical Empathy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>