<?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 Joe Essey on Medium]]></title>
        <description><![CDATA[Stories by Joe Essey on Medium]]></description>
        <link>https://medium.com/@JoeEssey?source=rss-53b0830cc1a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qAu-qcFSk6IKU31milfNtA.jpeg</url>
            <title>Stories by Joe Essey on Medium</title>
            <link>https://medium.com/@JoeEssey?source=rss-53b0830cc1a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:45:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JoeEssey/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[Professional Pull Requests]]></title>
            <link>https://medium.com/popmenu-engineering/professional-pull-requests-6f9dd4ce06d1?source=rss-53b0830cc1a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f9dd4ce06d1</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[pull-request]]></category>
            <category><![CDATA[professional-engineering]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering-practices]]></category>
            <dc:creator><![CDATA[Joe Essey]]></dc:creator>
            <pubDate>Thu, 10 Mar 2022 16:19:30 GMT</pubDate>
            <atom:updated>2022-03-10T16:23:50.763Z</atom:updated>
            <content:encoded><![CDATA[<p>I remember going camping when I was a kid. My father was crazy about his checklist. The day before we’d go through and check it all off as we packed. Sometimes we changed quantities or added or removed items based on our previous experiences.</p><p>Popmenu Engineering knows this is the right way to do pull requests. Well there are a couple other things, but we really love the checklist.</p><h3>Clear Title</h3><p>When you can, use verb-first titles which describe how introducing the PR will meaningfully change the software. Keep it short and informational so you or others can refer back to it in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*w-W8bdAT9CSf0CNuewZbeg.png" /><figcaption>Verb-first PR title</figcaption></figure><h3>Concise Description</h3><p>Our goal here is to serve our audience, those reviewing your code for merge, or those coming back to understand why a change was made. Make it as easy as you can for them, because it might be future you.</p><p>Bullet points are always easier than a paragraph, and following the verb-first format of your PR title is more than adequate. Focus on the product or technology changes, depending on the scope and purpose of your change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*kW0uInQ6UcVBc1LYFMq0mQ.png" /><figcaption>Bullet points are key</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*MMaVnLaKLuPF09bUvjldDA.png" /><figcaption>Another great example, this time focusing more on technical changes</figcaption></figure><h3>Screenshots</h3><p>Again, we want to make reading our PR a simple and pleasant task. Screenshots and videos are critical. You can produce them as you do your final smoke test, that way others won’t have to run your code to see the changes. The images can even be used for knowledge base and support documentation. At Popmenu we add tons of screenshots to our PRs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*t02lW23iuNtGGOraZA3IMw.png" /><figcaption>Showing all the screenshots would make scrolling this article a pain</figcaption></figure><h3>The Checklist</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*tNp878peJTvNYfJRYeclew.png" /><figcaption>Here’s a quick idea, but we have about 25 items</figcaption></figure><p>This is the important part. There’s no silver bullet here, no ‘perfect checklist’ that will prevent <em>all </em>production issues and <em>all</em> efficiency or style mistakes. But you can learn as you go.</p><p>Each checklist item is described in detail in our application’s docs repo. Things change, and any engineer can propose changes to the checklist with a pull request.</p><p>Our checklist ensures:</p><ul><li>Adequate unit and feature testing of front and back-end applications</li><li>Thoughtful and careful database and configuration changes</li><li>Incomplete functionality is not exposed to end users</li><li>Application functions are protected appropriately by auth/auth</li><li>Changes are backwards compatible and do not disrupt other teams</li></ul><h3>Be Intentional</h3><p>Really, all you have to do is decide to treat your PRs as your last chance to make sure you’ve arranged your thoughts correctly and that you won’t embarrass yourself with a production issue. If you’re an engineer just starting out, make your own checklist if you have to. If you run a department or squad, add a <a href="https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository">Pull Request Template</a> on Github.</p><p>Don’t be like me. The first time I went camping on my own, I didn’t make a checklist. I brought 1 full and 1 half-full bottle of water in total and only had sneakers with no tread on the sole.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f9dd4ce06d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/popmenu-engineering/professional-pull-requests-6f9dd4ce06d1">Professional Pull Requests</a> was originally published in <a href="https://medium.com/popmenu-engineering">Popmenu Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enabling Autonomous Software Teams]]></title>
            <link>https://medium.com/popmenu-engineering/enabling-autonomous-software-teams-4aa5e9035f4f?source=rss-53b0830cc1a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4aa5e9035f4f</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[autonomy]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[teams-and-teamwork]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Joe Essey]]></dc:creator>
            <pubDate>Thu, 10 Mar 2022 14:38:24 GMT</pubDate>
            <atom:updated>2022-03-10T14:38:24.513Z</atom:updated>
            <content:encoded><![CDATA[<p>A core belief of Popmenu Engineering is that the people doing the work know best how to do it. We organize a Product Manager, UX Designer, and 2–5 Engineers on each of our “squads,” each of which are provided guidance and support from an Engineering Manager. <br> <br> The squads pick a name and a logo, some of my favorite are <em>Menu Poppin’ Power Rangers </em>and <em>Air Fried Steak</em>. More importantly though, they intentionally set ground rules and agree to schedules and communication preferences, amongst other day-to-day work details. The teams track their own progress and adjust these rules and processes accordingly.</p><figure><img alt="Air Fried Steak’s Logo" src="https://cdn-images-1.medium.com/max/500/0*DWlz2LZzDTnPu-Iq" /><figcaption>Air Fried Steak’s Logo</figcaption></figure><p>We believe you should bring work to people, and not people to work. Since you’ve built a high-functioning team, you will never work on projects that do not contribute to the core goals of our business. You’ll solve different kinds of problems, and probably get to use new technologies along with those you’re familiar with. We will trust your team to solve the business and technology problems that will bring Popmenu success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4aa5e9035f4f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/popmenu-engineering/enabling-autonomous-software-teams-4aa5e9035f4f">Enabling Autonomous Software Teams</a> was originally published in <a href="https://medium.com/popmenu-engineering">Popmenu Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Highest Five — Promoting a Culture of Sharing Recognition]]></title>
            <link>https://medium.com/salesloft-engineering/the-highest-five-promoting-a-culture-of-sharing-recognition-828665c47075?source=rss-53b0830cc1a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/828665c47075</guid>
            <category><![CDATA[recognition]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Joe Essey]]></dc:creator>
            <pubDate>Wed, 06 Feb 2019 15:55:32 GMT</pubDate>
            <atom:updated>2019-03-06T19:31:13.124Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Highest Five — Promoting a Culture of Sharing Recognition</h3><p>As a current or future leader, it is imperative that you understand how to promote a culture of sharing feedback in order to be part of a successful business. In this article, I will give my recommendations on how to embody the behaviors you wish to see in others, and how to influence your team to embody these behaviors themselves.</p><p>Knowledge workers, for example, software engineers, respond more positively to messages from their peers than to messages from their bosses. If your boss tells you that you’re not putting in the necessary effort, you might think she is pushing to get the most out of you. If your <em>teammate</em> tells you the same thing, you might feel a sense of guilt and failure to live up to commitments. The same goes for a positive message. You may feel that your boss is just kissing your butt to keep you working hard, but if your <em>teammate</em> shows their appreciation, you may feel delighted and you may bring renewed vigor to your work.</p><p>First, we’ll cover advice on how to embody behaviors that will express to your team that providing positive feedback is desirable and necessary. Then we’ll address how to tactically institutionalize the sharing of positive feedback among your employees.</p><h3>Promoting Positive Feedback through your Behavior</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7hTIP7Suk9MZXee1C5o4ZA.jpeg" /><figcaption>from anthillonline.com</figcaption></figure><p>An organization’s leadership team must embody the behaviors it wishes to promote. In my experience, a leader embodying the following behaviors will result in your team feeling empowered to give feedback themselves.</p><h4>Keep your Eyes Peeled</h4><p>To give positive feedback, you must have observed something positive. You should spend time near your team, randomly review some code, check out a QA plan, view a design specification, or read a product document. The quality of the work of your team reflects on you, so you should be doing some of this already for the sake of self-preservation.</p><p>Since you can’t see everything, make it a common practice to ask managers of other teams if they have observed anything deserving of praise. This is not only a great way to get feedback, but to lead your management team peers by example.</p><h4>Present Yourself as a Source of Meaningful Feedback</h4><p>Messages are more effective coming from a confident, engaged person. Before speaking take a moment to make sure your back and neck are straight, that you are smiling, and that you are prepared to project your voice. As you speak, do so loudly and make eye contact with all members of the group.</p><p>Doing these simple things will express to your audience that you are engaged and acting with authenticity.</p><h4>Recognize People Publicly</h4><p>Make a commitment to yourself and peers to publicly share one piece of positive feedback every week, or better yet every day. Giving praise in public can be uncomfortable. When I was getting started, I felt like I was being judged for being cheesy or ingratiating myself through flattery. If you happen to feel this way, it doesn’t matter. Who cares if they judge you? They’ll get over it the day they’ve earned some of your praise.</p><p>Traditionally, Western work culture discourages positive displays of emotion. It is my belief that deep down we all want to work in a place where we can be open and emotionally expressive. It is up to you to show your team that it’s not only okay, but preferred, to express the positive things you feel about your peers, and to do so in front of everyone.</p><h4>Be Specific</h4><p>“Good job,” “you’re doing great,” and “there is nothing you could do better” are low-value statements. Does the person giving me praise even know what I do!?</p><p>To give meaningful praise, it must be about a specific action or outcome where the person bears some responsibility. Try something like these:</p><p>“Julie, thank you for improving the performance of our longest running query. The reported issues for search have dropped from 5 daily to 0 in the last two weeks.”</p><p>“I want you all to give a round of applause to Gary. He’s an engineer, but he joined a sales meetup for fun. It turns out he’s pretty good at business development because one of the CEOs he met just scheduled a meeting with us!”</p><p>“Few peers have driven me to succeed the way Jamie has. It’s amazing how her mind is always on the most important thing that will bring us closer to our goal.”</p><p>Your employees will go home and tell the people they love, “remember that thing that was so hard, well my boss told my whole department that we only could have done it because of my special ability!” There is incredible power in being specific, but it won’t be easy. Make sure and write down all the cool stuff your teams and people do.</p><h4>When Praised, Deflect Credit to Others</h4><p>When you lead people, leaders above you will be aware if you are meeting the goals you’ve committed to (or they have committed you to). You will certainly hear about problems, and if you’re at a great company, you will be praised.</p><blockquote>In this moment your mindset should be that you are the least responsible person for the success of your team.</blockquote><p>You didn’t really do any of the important work. Sure you planned meetings and steered conversations, but you didn’t type a script, design a comp, or QA a feature. Give credit to those people. Even if you did pitch in a little bit, who cares?</p><p>When your boss, peer, or report praises you, immediately list the specific things your teammates did to accomplish the goal. Go a step further and say you were simply fortunate to be involved.</p><p>Now you are equipped to set an example for how to give positive feedback. That is the fundamental first step to transforming your culture. In the following section, we will examine intentionally influencing the culture of your department.</p><h3>Fostering Recognition within your Teams</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*80V_FU1U5DeSwyBQujkqlw.jpeg" /><figcaption>from naturaltraining.com</figcaption></figure><p>A leadership team setting an example is the most powerful form of influence available. That’s what we’ve set you up for, but how do you get your people to recognize one another? Try some of the following.</p><h4>Intentionally Teach Them</h4><p>In 1-on-1s or in a large group setting, share these ideas with your employees and peers. Give them good examples of what effective praise looks like, teach them to present themselves professionally, and ask them to look for people going above and beyond.</p><h4>Ask your Reports for Help</h4><p>Ask each of your direct reports to commit to publicly giving one piece of positive feedback every week. If they commit to it, check in with them each week and ask what the feedback was.</p><p>As an aside, asking directs for help is a technique I use to enact all types of organizational change. I simply state to my direct that I need a hand and explain why it will help them and the company. Hopefully, my reasoning is sound and I get some buy-in. If the person isn’t bought in, there’s no reasonable expectation that they will agree to the favor or follow through if they did.</p><h4>Create a Department-Wide Recognition Program</h4><p>By now you are exhausted by all of this new responsibility. I know, it’s hard to add a new set of tasks to your workday. What if you (partially) automated a solution, what would it look like? We came up with a way to institutionalize the sharing of positive feedback at SalesLoft.</p><h3>The Highest Five!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RDHEvn65Ged_K53egkNGCA.jpeg" /><figcaption>Sam Inyang handing off The Highest Five Trophy to its latest winner, Kyle Bock</figcaption></figure><p>Every two weeks an employee is recognized by their peers for having the greatest effect on our company’s success. How we choose the winner is the coolest part.</p><p>We created a slack channel called <strong>#the-highest-five</strong>. Anyone in the Product &amp; Development Organization can give a ‘High Five’ to their peer by typing a description of what they did to earn the honor. Every two weeks, the previous winner chooses the nomination they judge to be most deserving. This person earns The Highest Five and can look forward to choosing the next winner. There is a pretty cool prize selection too.</p><p>The program is successful and has expanded. We now include an activity where all the members of the team, about 80 of us, share our personal highlight from the last couple weeks. You know what happens there? Lots of people call out another person’s feats as their own personal highlight.</p><p>Take a look at some of the High Fives that have been posted lately:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*S9ZW8HCoryFBEpQAGOYAVQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*8ZDbP0Yphd6aWtJRd1Vh2w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*skSGUAYBAMDHVOBLxNQYuQ.png" /></figure><h3>Wrap</h3><p>Pretty simple stuff, right? If you want to bring more positivity and recognition to your team, remember this: Embodying a new behavior is not easy and you will need to remind yourself to act. Put an appointment on your calendar for this afternoon to share positive feedback with somebody, keep a journal of your peers and directs and the things they’ve done to impress you, and put yourself out there and compliment how quickly an engineer fixed a bug.</p><p>The point I’m trying to make is that you are in control of making this change, you don’t even have to be a manager, though it certainly helps. Just start and people are going to want to be a part of it. I’m impressed that you’ve finished this article!</p><p><em>Joe Essey is an engineering manager leading our performance and email workflow teams. When he’s not leading this amazing teams of engineers, designers and product owners, he’s exercising his creative muscle producing electronic music.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=828665c47075" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesloft-engineering/the-highest-five-promoting-a-culture-of-sharing-recognition-828665c47075">The Highest Five — Promoting a Culture of Sharing Recognition</a> was originally published in <a href="https://medium.com/salesloft-engineering">Salesloft Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Supercharged My Career Growth in About 18 Months: Transitioning from Player to Coach]]></title>
            <link>https://medium.com/salesloft-engineering/how-i-supercharged-my-career-growth-in-about-18-months-transitioning-from-player-to-coach-cd45d56fd95a?source=rss-53b0830cc1a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd45d56fd95a</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Joe Essey]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 20:28:32 GMT</pubDate>
            <atom:updated>2018-10-02T15:33:16.889Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ACzCcd1etXDLAWHgM5_zA.png" /></figure><p>Everyone has a unique story, and that makes it tough to define what is “the” path to becoming a leader. What I can do is tell you my story, and tell you my personal philosophy which helped transformed me from individual contributor to engineering manager.</p><h4>Early Days</h4><p>Like many of us in software, I had a roundabout journey. I failed out of college as a freshman in 2000. That was fine, I went back to my high school gig, plating fajitas at a lousy Mexican chain restaurant. I began taking the work seriously and got a degree in Culinary Arts, then worked my way up to sous chef at one of the most prestigious restaurants in Pittsburgh. I loved leading crews but the demands of the job were too great. I bounced around a couple other cooking and kitchen manager jobs for 10 years, before getting fed up with having little and working lots.</p><p>I enrolled in college, signing up for information science rather than CS because of weird community college credit transfer rules. This was a fortunate mistake! Instead of just diving deep in to algorithm and data structure courses, I got to take a bunch of business courses where I learned about finance, economics, and most importantly, management.</p><p>One of my courses was about transformational changes at large corporations, and one that got me particularly excited was <a href="https://www.channelnewsasia.com/news/cnainsider/outsider-rescued-nissan-brink-bankruptcy-carlos-ghosn-9462320">Carlos Ghosn saving Nissan through a cross-functional team approach</a>. Books have been published on the subject and I encourage you to at least familiarize yourself with the story.</p><p>This course led me to the conclusion: “What is the point of me going to work if I’m not leading these huge changes?” I left college with a modest goal of becoming a C-level executive or maybe a CEO in 10 years. I would do this via promotions in IT and then I’d swap over to finance or something after getting a great reputation.</p><h4>Hello World</h4><p>I landed my first tech gig in ops at a big insurance company. I legitimately did not know what “operations” meant but the money was so much better than a cook’s salary so I said OK! Then I made spreadsheets for a few weeks.</p><p>I followed one of my personal rules, which is to speak up when I want something. I told my boss that I wasn’t digging the ops job and he helped me get on an engineering team in a few weeks. Two years of intense learning later and I was ready to level up and work at a software company. I’d made the realization that an insurance company is not going to give me the opportunities I need to be a successful professional according to the goals I’d set for myself. I was stuck in New Hampshire, so if I can’t get out of it, I get in to it. I decided I would transform this company with the practices and technologies I had learned during nights and weekends.</p><p>That was a huge mistake. My M.O. was to give tons of open feedback about my coworkers while offering opportunities for improving. This made me unpopular, likely due to my lack of mastery of delivering such feedback. I often got in to heated disagreements with my manager or projects’ stakeholders, thinking I was doing the right thing. I look back and still think maybe I was doing the right thing, but that doesn’t even matter.</p><h4>New Opportunity</h4><p>My wife got a job in Atlanta and I breathed a great sigh of relief that I could leave and live in a city with lots of opportunity. I sat down with my manager to submit my resignation and had the most important conversation of my life, I really mean that. He said, “Hey Joe, I know you don’t want to hear this from me,” since our relationship had completely deteriorated by now. “The only thing that matters, the only thing, is whether or not you get along with your team, and that the team is on the same page working towards the same goal. If you have that, the work just comes in and gets done.” I thanked him for what I thought was silly advice and left, I may have even jumped and clicked my heels on my last day two weeks later.</p><p>I’ll write more about my next year in the future, but the short version is: I realized my boss was right and that I needed to fully focus on the people around me. Pivoting my attitude enabled me to land a full-stack gig at SalesLoft.</p><h4>4 Stages of Team Membership</h4><p>My colleague <a href="https://www.linkedin.com/in/cdanielandrews/">Daniel Andrews</a> has called the switch from engineer to manager “player-coach to coach-player.” I want to extend that metaphor to 3 transitions. Player -&gt; player-coach, player-coach -&gt; coach-player, and coach-player -&gt; coach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/662/1*SZZR2D2XMQMzuFasniNt0w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*2HB_3WfKIj9J7aOof2wBZw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNTt6Z3U-EV0gcFimNKU-A.jpeg" /><figcaption>Bill Russel served as a player, player-coach, and coach during his career — Bill as a player (left), during a year when he acted as a player-coach (middle), and as a coach (right)</figcaption></figure><p>These roles manifest as different job titles in different organizations. ‘Team Lead,’ for example, may be player-coach or coach-player depending on your company.</p><p><strong>Players</strong> are individual contributors. They take/choose assignments and execute on them. Players are fundamental pieces of a successful team. Executing thoroughly will set an example for adequate behavior and performance of their teammates.</p><p><strong>Player-coaches</strong> continue to deliver on assignments while taking on additional responsibilities like mentoring or providing plans and estimates to their stakeholders. This is where it begins to be important for people to consciously set a great example for their peers.</p><p><strong>Coach-players </strong>flip their concentration from player coaches. They are accountable for plans, estimates, and making sure work is assigned. They might lead meetings, or plan team events. One’s emphasis on setting a great example increases.</p><p><strong>Coaches</strong> are accountable for the success of their teams and people. You will often be the HR administrator of people. You will make sure that your people are growing and that they understand how meaningful their contributions are to the success of your team and company. You have to resist the urge to get your hands in the details. Setting a great example, in my opinion, is the most important part of this job.</p><p>Before we dig in further, I want to emphasize that it is immensely important for you to communicate to your manager that you are ready and eager for this journey. You need to remind them of it, and understand what your skill gaps are so you can aggressively fill them.</p><h4>Player to Player-Coach</h4><p>To begin your transformational journey, become a great follower. This doesn’t mean to just do what you’re told. You need to anticipate the needs of your team, your company, and your boss and then work to meet and exceed them. You must make realistic commitments and deliver on them. How many great leaders do you know that shirk on responsibility or fail to do what they’ve committed to? I don’t know any that miss more than rarely.</p><blockquote>You must deliver quickly, accurately, and consistently.</blockquote><p>This is the least complicated transition: volunteer and push yourself. Ask your boss if there are things she does that you could help with. Take ownership of the hardest things your team is doing. Push yourself until you find your limit. When you find your limit, bring others in to help you succeed and heap praise on them. Make it known that they made it happen, not you. This seems unintuitive, I get that. Your boss will know that even though another person helped you, you drove the effort to get help and didn’t give up.</p><p>Look for opportunities to mentor less experienced folks. This doesn’t have to be official. You will work on your reputation and your skills of teaching and encouraging folks.</p><p>At SalesLoft I worked with my manager, <a href="https://www.linkedin.com/in/matt-sales-3382769/">Matt Sales</a>, to take ownership of a significant project. I held meetings to determine product and technical approach, sat on a cross-functional business team representing engineering, and ensured my peers carried through on their commitments. Management’s confidence in me grew, and I continued to request more responsibilities from Matt, who helped me find them. Your manager may be thrilled if you offer some help. I also volunteered to mentor one of our support engineers at the first opportunity.</p><h4>Player-Coach to Coach-Player</h4><p>This is when the ‘how-to’ part of this essay breaks down. As you grow it’s really hard to talk about how to be successful. It is about embodying what you understand to be important to your self, company, and organization. People immediately look up to you, or better said look to you for behavioral cues. You need to be ‘on’ all the time when you’re at work. Not solving a problem is not an option. How you get it solved is up to you, sometimes what ‘solved’ means can be up to you. You need to start thinking about what people expect from your team, and you need to work on aligning those expectations with reality.</p><p>Here’s how it went for me. After proving I could do leadership tasks over a couple months, my manager effectively handed our team over to me. I even got a couple direct reports. I also led a department wide training session on effective communication in order to enhance my reputation as a professional who thinks about more that bits and bytes.</p><p>The engineering organization at SalesLoft fully supported my efforts to level up and we looked for opportunities to plug me in as a coach-player. I was unofficially given charge of my team. Around the same time the need for our next engineering manager arose, due to our department’s growth.</p><p>My manager was super-encouraging and suggested me for the job. The rest of the engineering managers at SalesLoft went to bat for me. This is no doubt due to my reputation of setting a great example of <a href="https://salesloft.com/company/">SalesLoft’s Core Values</a> and <a href="https://medium.com/salesloft-engineering/saleslofts-3-core-tenets-of-engineering-3c582ea21cf1">Core Tenets of Engineering</a>.</p><p>I became SalesLoft’s newest engineering manager, got some more direct reports, and was officially given ownership of my team.</p><h4>Your First Coaching Gig</h4><p>All right, I finally made it! I’m the boss and people are going to do things my way. Wait, what is my way? Oh, my team has a better way!</p><blockquote>Ahhhh! I have no idea how to spend my time!</blockquote><p>With some exceptions, any web search for ‘management books’ gives you 3 types. 1. Stories of folks who were successful that will apply to you in no way. 2. Generic advice about scheduling meetings and what a scrum is, and 3. Self-help. I say stick with self-help, honest.</p><p>I can’t emphasize how useful self-help books have been for me. When you’re a manager, someone has said <em>you </em>are what’s important. Not the code you produce, your bedside manner, or your eagerness to give honest feedback. It is about the weird, unique, specific collection of skills you bring to work.</p><p>To be a great coach, you need to understand that people admire you and that you’re already doing a lot of things right. Trust yourself and foster your own growth. Question your beliefs, ask questions to people you admire, and eagerly dismiss your assumptions. Think of the people you admire and find the gaps between your behavior and theirs. Address those gaps.</p><p>To be effective, I have a simple approach: Observe and do what’s right for the people and the company. Hear, see, and feel (emotionally) the people around you. Are you getting the impression that someone is blocked? Ask them. Was there a misinterpreted message that you think may have damaged a relationship? Ask them about it and encourage them to get back on the same page. How do you know what to do when you observe something? Ask yourself. That is your job. You are trusted to do what you know is right.</p><p>You’ll often be right, and you’ll often be wrong. Keep making decisions and growing these muscles. Make sure the people around you feel comfortable telling you about opportunities for your growth. Most importantly continue to behave like the people you look up to most.</p><h4>Wrap</h4><p>My 18 or so months at SalesLoft have enabled my growth like no experience in my life. I’m challenged by the greatness of my peers and everyone else in the organization. Every day I face a new problem that I am unprepared to solve. I lean on the experienced pros around me for support, and then trust myself to solve it.</p><p>I won’t be the last person to tell this kind of story at SalesLoft. <a href="https://salesloft.com/company/career-opportunities/">Join us and get to the next level</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd45d56fd95a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesloft-engineering/how-i-supercharged-my-career-growth-in-about-18-months-transitioning-from-player-to-coach-cd45d56fd95a">How I Supercharged My Career Growth in About 18 Months: Transitioning from Player to Coach</a> was originally published in <a href="https://medium.com/salesloft-engineering">Salesloft Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SalesLoft’s 3 Core Tenets of Engineering]]></title>
            <link>https://medium.com/salesloft-engineering/saleslofts-3-core-tenets-of-engineering-3c582ea21cf1?source=rss-53b0830cc1a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c582ea21cf1</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Joe Essey]]></dc:creator>
            <pubDate>Mon, 30 Jul 2018 21:51:25 GMT</pubDate>
            <atom:updated>2018-07-30T22:01:27.541Z</atom:updated>
            <content:encoded><![CDATA[<p>I am asked, often with skepticism, how do SalesLoft’s <a href="https://salesloft.com/resources/blog/2016/07/company-core-values-bringing-culture-to-the-popular-table/">5 Core Values</a> actually influence the work we do?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4EzyCbavWXU-m31CvFARUA.png" /></figure><p>It’s a great question that I usually answer with abstracts. Usually, I say “the Core Values are a set of filters in my mind, and each time I prepare to speak or take action I test my intentions against the Core Values filters. I may or may not modify my message or action. This ensures my actions fit the Core Values.” Easy-peasy, right?</p><p>Some folks are left unsatisfied by this answer. They say “how do they tie into writing appropriate unit tests?” Or “how do they affect making a decision to try new architectural patterns?”</p><blockquote>This is a story of a team fully embodying our 3 Core Tenets of Engineering, the mechanism that ties our Core Values to our day-to-day habits.</blockquote><p>Yes, you heard right. In order to tie our Core Values to engineering performance, we created guiding principles or our 3 Core Tenets of Engineering. This allows engineers to simply keep correct practices of teamwork and execution in mind while they do their work.</p><p><strong>The 3 Core Tenets of Engineering</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nFjYBsBrcFpmszjHJg_aMw.png" /></figure><ol><li>Write beautiful, extensible, elegant, simple code.</li></ol><p>2. Ship finished features fast. Get value to the customer or it’s not done.</p><p>3. Work together as a team. Take ownership, help others, pair program.</p><p>We will highlight the team that built SalesLoft’s “Meetings” feature. Meetings allow users to tie SalesLoft to their calendaring app of choice, and through it, propose and set calendar invites. This allows our users to accomplish all of their calendaring tasks without leaving SalesLoft or managing 3rd party tools! Let’s start with a quick intro to our team, HSA (Heavy Swearers Anonymous).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G3y8gjNdqPZ9Rp3hNzUwCw.png" /></figure><p><strong>Heavy Swearers Anonymous</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*N8Du5AIy9UIkEvCiFohogg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*MKyEM32vEUYz9OMtQMWg1A.png" /><figcaption>Cam Hilsman — Product Manager, Jody Rodd — Architect</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*2alpcNniKNtqCbNcKzJ18g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*0WQs9K60AHhNjzbirpzQiA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*AiULPfjUQ7neLk4E3qJiFg.jpeg" /><figcaption>Stephen Settle — Full-Stack, Peter Finn — UI Engineer, Vinaya Shrestha — Full-Stack</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*hoOFIeDrWkmFcn4Be7u4OQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*NAOhfp4uubj4LUwgW8OsKQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*XZiiawYqViVuPpujp_2ucA.jpeg" /><figcaption>Carina Gerry — Director, Engineering Quality, Dylan Wahlstrom — UX Designer, Jeff Thoensen — QA Engineer</figcaption></figure><p>Before we dig into why we were successful, let’s make sure we all know what success means here. A product implementation at SalesLoft is successful if:</p><ul><li>The feature delights customers.</li><li>The Product Department agrees that the work that’s been done fulfills their specifications.</li><li>The decisions made and the code written push the boundaries of what’s possible for SalesLoft Engineering.</li><li>The people who worked on the implementation understand and are proud of how their work connects to the overall mission of SalesLoft, and the to the missions of the people who use it.</li></ul><p>Meetings was a total victory. Customers love using it, Product’s expectations were exceeded, several of HSA’s experiments led to new ways of solving problems, they produced a ton of reusable, extensible code, and they are proud of their work. In fact, when we all got back together for this exercise there was a palpable energy that could only be a result of their deep connection to one another, to SalesLoft, and most importantly, to the users who will benefit from this feature.</p><h4><strong>Tenet 1: Write beautiful, extensible, elegant, simple code</strong></h4><p>Core Values: Focus on Results, Bias Toward Action</p><p>You might be thinking this should be self-evident. I agree, but if you’re like me then you’ve worked places where it isn’t. Let’s look at how this delivery team embodied this tenet.</p><p>Beauty + Simplicity = Elegance</p><p>“Elegance is beauty that shows unusual effectiveness and simplicity.” <a href="https://en.wikipedia.org/wiki/Elegance">From Wikipedia.</a></p><p>Simply put, in order to achieve elegance, team members must be equally focused on beauty (contextual readability) and simplicity (logical readability).</p><p>The practices HSA enacted to achieve this goal may be less satisfying than a list of tactical steps, it is an approach and attitude.</p><p><strong>Ground Rules:</strong><br>Before the work began, HSA decided they would not cut corners, period. At any point, a team member would be challenged if they were perceived to be doing so. By committing to the single responsibility principle, HSA also split out all of the logical components and loosely defined their interfaces. This allowed members to work independently with incomplete knowledge of other team members’ work. Engineers committed to submitting small pull requests, and the benefits of that are well documented. The team held one-another accountable through the implementation of the feature and reaped rewards beyond elegant code.</p><p><strong>Extensible Modules:</strong><br>Because of their ground rules, HSA was empowered to build reusable components and make architecture decisions that pushed SalesLoft engineering forward. I cannot emphasize the impact this project had on the organization. It brought us:</p><ul><li>Evidence that commitment to quality results in not only great code, but organizational improvement.</li><li>The first internal feature using the public API. SalesLoft is a believer in drinking our own champagne (Our sales team sells SalesLoft by using SalesLoft.) This effort proved that our API is good enough for our customers because it is good enough for us.</li><li>A successful implementation of microservice architecture. It was not the first at SalesLoft, but yet another victorious example of why microservices work for us.</li><li>We learned how to write reusable react components in the context of SalesLoft’s ecosystem.</li><li>One of those components is a beautiful date picker that’s used all over the application.</li></ul><p>An underappreciated bit of reuse and extensibility is in the domain knowledge gained. Jeff, the QA Engineer, became an expert in calendaring and timezones, and now is the go-to person to ask in the organization!</p><p>The secret sauce is commitment to a mindset of quality and innovation, and for team members to habitually hold each other accountable. Let’s explore our second tenet, where we strive for excellence in combining our engineering and product organizations.</p><h4>Tenet 2: Ship finished features fast. Get value to the customer or its not done</h4><p>Core Values: Put Customers First, Focus on Results, Bias Toward Action</p><p>The focus on getting value to the customer is what’s special about this tenet. Of course we strive to deliver finished work quickly, but who cares if it doesn’t help customers?</p><p>The team was able to fully focus on delivering meetings because the product and engineering managers strove to protect the team from unnecessary outside influence. The team members took ownership of pushing back if something fell through the cracks, and they were able to maintain full focus on delivering their project for its duration.</p><p>HSA was asked to deliver by a reasonable date. Their focus allowed them to begin working on stretch goals before the deadline came. For these, HSA estimated their own delivery schedule. No hard end date, no scope negotiations, no panicked adding of engineers near a deadline. This is effective, and has the fortunate side-effect of making the team excited to come to work and deliver!</p><p>HSA took their time to do strategic planning. They split the work such that each piece was independent and could be QA’d and placed into production without exposing partial functionality or affecting other systems’ behaviors. For example, they delivered integrations only for Gmail, then later came back and implemented integrations for Azure and Nylas. Focusing on small pieces also made any bugs found by QA easy to fix. Their planning was so detailed, in fact, that they had identified cases where 404s and 500s might happen in unusual scenarios. They did this before writing any code! Their plan was so tight, that after the first executive check-in, the co-founder found all future check-ins unnecessary.</p><p>A cherry on top was HSA’s relationship between design and engineering. Dylan, the designer would actively pair with engineers to remove communication barriers, he even went the extra mile to fix CSS bugs to help the rest of the team reach their goal. This epitomizes Team Over Self.</p><p>Every member on the team used their tools to ensure they were constantly focused on making our customers’ jobs easier by providing them with a calendaring solution. None of this awesome planning and project management matter if the people on the team are not invested in making each other successful. Let’s see how they kept one another in mind.</p><h4>Tenet 3: Work together as a team. Take ownership, help others, pair program.</h4><p>Core Values: Team Over Self, Focus on Results, Glass Half Full</p><p>Table stakes at SalesLoft is having a Team Over Self attitude, meaning putting the goals of the team over one’s own personal and professional goals. Here’s how that approach played out.</p><p>It starts with unconditionally treating one another with dignity and respect. Everyone understands that every decision and action made by other team members carries their best intentions.</p><p>On HSA, team members could take for granted that when a person owned work, they would deliver it. That doesn’t mean others wouldn’t help. Engineers pitched in with QA and planning. Product wrote code, paired with engineers, and helped with QA.</p><p>Requests for change occurred, from both within and outside. The team decided that some change would help them deliver value to customers, and some would not. They stood together to push back on non-valuable change. However, when a good suggestion was made, they would embrace it and do their best to get it to users quickly.</p><p>The team succeeded because they put their teammates’ and SalesLoft’s goals above their own. They held one another accountable and in the highest esteem.</p><p>HSA has done a great job of illustrating how SalesLoft’s Core Values influence the tactical work of individuals and delivery teams. We focus on writing exemplary code that we’re proud of. We get valuable, working features to users as quickly as possible. We do those things through a deep commitment to supporting and holding one another accountable.</p><p>Now when I’m asked, I can easily draw a connection between SalesLoft’s Core Values and the way we accomplish work day-to-day. I hope this story whets your appetite because we’re experiencing massive growth and we want you to <a href="https://salesloft.com/company/career-opportunities/">join us!</a></p><p><em>Joe Essey is an engineering manager leading License to Trill — our product team focused on our workflow engine suite of features. When he’s not leading this amazing team of engineers, designers and product owners, he’s exercising his creative muscle producing electronic music.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c582ea21cf1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesloft-engineering/saleslofts-3-core-tenets-of-engineering-3c582ea21cf1">SalesLoft’s 3 Core Tenets of Engineering</a> was originally published in <a href="https://medium.com/salesloft-engineering">Salesloft Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>