<?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 Jeffrey Barron on Medium]]></title>
        <description><![CDATA[Stories by Jeffrey Barron on Medium]]></description>
        <link>https://medium.com/@jeffreyabarron?source=rss-13640722090b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vMaFKfy5MeAneXCle0Fpag.png</url>
            <title>Stories by Jeffrey Barron on Medium</title>
            <link>https://medium.com/@jeffreyabarron?source=rss-13640722090b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:52:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeffreyabarron/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[Measuring Team Performance is Hard]]></title>
            <link>https://medium.com/@jeffreyabarron/measuring-team-performance-is-hard-8691484c0a72?source=rss-13640722090b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8691484c0a72</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[measurement]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jeffrey Barron]]></dc:creator>
            <pubDate>Thu, 30 May 2024 21:50:15 GMT</pubDate>
            <atom:updated>2024-10-14T01:35:26.836Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*7dnGFUdPuD-CxK4gclQqGg.jpeg" /></figure><p>Measuring an engineering team’s performance is hard. Really hard. It makes sense how often it ends up with tracking lines of code, number of pull requests, or completed tasks and story points. They are easy to measure and easy to compare.</p><p>But these metrics suck at gauging the stuff that matters. They aren’t based on intended outcomes so it incentivizes the wrong things and leads to more noise than signal.</p><p>I explore a few questions instead:</p><ul><li>What are the intended outcomes?</li><li>What behaviors will lead to those outcomes?</li><li>How do I support and promote those behaviors?</li><li>How do I properly measure those activities?</li></ul><p>Are metrics based on these questions harder to measure? Absolutely! But they also lead to the strongest signal about the health of the team and the performance of individual engineers.</p><p>I’ve found success by organizing performance metrics into team and individual levels; then within each level are “topics” that categorize data that is most likely to be insightful.</p><h3>Team Level</h3><p><strong>Goal Achievement Rate</strong><br>The rate at which my team is hitting their goals indicates their consistency over time and can identify when something is not working as well as it could.</p><ul><li>Sprint Goal</li><li>Weekly Goals</li><li>Project Goals</li><li>Tech Debt Paydown Goals</li></ul><p><strong>Velocity or Flow</strong><br>I can track consistency over time and highlight abnormal periods of productivity by measuring workflow trends. Understanding these trends focuses my investigation towards possible root causes: high interruption rate, high ambiguity on work, etc.</p><ul><li>Velocity (sprints)</li><li>Cumulative Flow (kanban)</li></ul><p><strong>Regression &amp; Escalation Rates</strong><br>Measuring how often my team is affected by unplanned work is essential to either decrease the rate or accommodate these blips within normal operations.</p><ul><li><em>Regression Rate:</em> measures code and test quality; helps the team identify areas to improve quality</li><li><em>Escalation Rate:</em> measures deviations from planned work and its effect on goals; helps to adjust for the unknown</li></ul><h3>Individual</h3><p><strong>Relative Productivity</strong><br>Measuring how an engineer is doing relative to their historical performance, the rest of the team, and their skill level will highlight any need for mentoring sessions or adjustment to workload and processes. My intent isn’t to set quotas but to find persistent deviations in the trend of their work.</p><ul><li>Features/stories completed</li><li>Goal achievement rates</li><li>Contribution level on pull requests</li></ul><p><strong>Goal Progress</strong><br>Measuring an engineer’s progress on their career goals helps me empower them to grow their skills, advance their careers, and focus their learning with targeted, measurable goals.</p><ul><li>Short or long-term goals</li><li>Project or team level goals</li><li>Career level goals</li></ul><p><strong>Leadership &amp; Collaboration</strong><br>When I can capture qualitative feedback on how an engineer is leading and collaborating within the team I can identify goals or potential areas of improvement.</p><ul><li>What impact is an engineer having on the team and business?</li><li>Are they growing their sphere of influence and responsibility?</li><li>Are they successful at collaboration and mentorship within the team?</li></ul><p>While these aren’t the <em>only</em> ways to measure the performance of an engineering team, I’ve found they are a good starting point. Aligning metrics with the outcomes helps me preemptively guide the team through rough patches and make them more likely to be successful long-term.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8691484c0a72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Changing Processes With Minimal Blowback]]></title>
            <link>https://medium.com/@jeffreyabarron/changing-processes-without-blowback-342ce8fa58e1?source=rss-13640722090b------2</link>
            <guid isPermaLink="false">https://medium.com/p/342ce8fa58e1</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jeffrey Barron]]></dc:creator>
            <pubDate>Thu, 23 May 2024 01:35:52 GMT</pubDate>
            <atom:updated>2024-05-23T01:41:11.390Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been lucky enough to refactor processes used by my engineering team a couple times — from designing new workflows to figuring out the best way to apply agile methodologies. Normally this was because:</p><ul><li>I was the first Engineering Manager hire, or</li><li>I was replacing a hands-on lead or architect, or</li><li>I had an ambitious goal where the status quo wouldn’t work</li></ul><p>Here it was! The mythical “blank check”; I had buy-in to make any changes needed to achieve goals for the team. I could ignore everything, think big about how I believed things should work, and turn my abstract ideas into reality.</p><p><em>Or so I thought…</em></p><h3>Even Blank Checks Have an Available Balance</h3><p>In my rush to Make Everything Better™ I’d forgotten there are always natural limits to change. Every team and company has a pace at which you can <em>successfully </em>evolve processes. Yes, I can bend and stretch those limits, but breaking them causes more problems than it solves.</p><p>I failed to truly understand the space I had to operate within, missing the constraints I couldn’t immediately see but needed to adjust to. Answering key questions would have helped figure out a workable balance:</p><p><strong>How cohesive is the team?</strong><br>A team with a high level of trust often leads to openness to radical change; a newly formed team requires a slower transition.</p><p><strong>How adaptable is the team?</strong><br>A team with a history of process experimentation and adaptation can successful at integrate new approaches quickly.</p><p><strong>How open to change is the company?</strong><br>A company that leans towards inflexible processes makes changes harder to sustain and reduces opportunities to promote those ideas outside the team.</p><p>Answering these questions aligns new processes with what the team is ready for, what is most likely to be successful long term, and the right pace to rollout these changes.</p><p>In the end, as with development, iterative improvement outperforms “big bang” changes every time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=342ce8fa58e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflecting on a year of unemployment]]></title>
            <link>https://medium.com/@jeffreyabarron/reflecting-on-a-year-of-unemployment-d090c3503654?source=rss-13640722090b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d090c3503654</guid>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[unemployment]]></category>
            <dc:creator><![CDATA[Jeffrey Barron]]></dc:creator>
            <pubDate>Tue, 14 May 2024 02:34:32 GMT</pubDate>
            <atom:updated>2024-05-14T04:26:16.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*8L1TOSCi2FWDs2tAlD3gqA.png" /></figure><p>I’ve been unemployed for a year.</p><p>What better way to celebrate this anniversary than to reflect on how I got here, what’s happened since, and how I’ve found productive ways to navigate this time between full-time gigs.</p><h3>How It Started</h3><p>I’d survived a couple rounds of layoffs through May of 2023 but it’d taken a toll on me. I was exhausted, running past empty for months, and struggling to effectively lead my team. I was burnt out and knew it.</p><p>I resigned from my job without any real prospects because I needed to make a change before it got any worse. It’d take 3 months before I’d start to feel normal again; my energy level on the rise, I’d had good luck landing interviews, and I was hopeful for the first time in a long time.</p><p>Then I hit a wall.</p><h3>Lies, Damn Lies, and Statistics</h3><p>The job market only continued to get worse; multiple rounds of tech layoffs industry-wide created an influx of talented people applying for fewer and fewer positions. The raw numbers from my job search were downright demoralizing:</p><ul><li>Nearly 45% of the time I never got a response</li><li>Only 5% of applications led to an interview of any type</li><li>About 50% of my interviews were in the first 3 months</li></ul><p>It was easy to get lost in the noise of the data; the sheer volume of applications submitted alone was daunting. However, I found a silver lining within the chaos, a logical story that gave me a degree of solace.</p><blockquote>When I got an interview I had an 80% chance of making it past the first round and a better than 60% chance of making it to the final three rounds.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FQADXqcH4LM3k33lVkg%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExMHp0cmp3bmN0MzRtdnM3OTI2NHlpMTJ6N2twMTJ1YmlwZHEzeTV5biZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FQADXqcH4LM3k33lVkg%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZXViM29reXFzaGRkeGZxYWxkNWtwaGw5bTRzYXF2eHV2eHhydHFpdCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FQADXqcH4LM3k33lVkg%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/5796a830261f85cb9ba6290acda1a015/href">https://medium.com/media/5796a830261f85cb9ba6290acda1a015/href</a></iframe><p>Here was a quality based metric I could use to measure my job search — how effective was I at highlighting my experience and getting the next interview. Yes, getting my foot in the door was still elusive, but I had good success communicating my value to a potential new employer once I did. It was a sliver of hope, but it was enough.</p><h3>Dealing With Rejection</h3><p>I knew it was going to take a while to find a new role, but I could never have predicted it’d take more than a year! I had a safety net to keep me afloat while looking for the right role and didn’t need to take a job just to pay the bills. Not everyone was so lucky. Former co-workers, peers in tech, and people I’ve never met but whose despair and desperation was very real.</p><p>The search was an emotional rollercoaster with more downs than ups. The intermittent stream of impersonal rejection emails stung but were ultimately fleeting. Recovering after losing out on a job where I interviewed definitely took longer.</p><p>The deeper I got into the interview process, the more invested I become. I’d start to envision myself within that role and how I could be successful. Receiving a “no” at this point made me question my own knowledge and competency.</p><p>It’s amazes me how a small message sent out into the LinkedIn social void would prod me to keep applying, keep interviewing, keep trying to find the role for me. Each message reminded me that hiring is more about fit for that particular role and less about my skills or ability.</p><p>Yes, of course those things matter! Time invested honing my interview skills really helped highlight both. But I could wow during interviews and still miss out because of a candidate with slightly better alignment. I realized the differences between talented candidates was intangible and more akin to a coin toss.</p><h3>Ways I’ve Found To Cope</h3><p><strong>Rely on a support system</strong><br>I’ve needed to periodically vent in order to make it through the low points and a small group of supportive people have been available whenever I’ve needed them. They’ve generously listened, contributed their time and insight, reviewed resumes and cover letters, and gave me the confidence to keep at it.</p><p><strong>Set a routine</strong><br>Unemployment inherently lacks structure and I found myself easily spiraling into frustration and despair — “What’s the point of getting up today — I don’t have anything to do.” Setting a flexible daily routine with a few goals helps me regularly achieve small wins.</p><p><strong>Give myself periodic check-ups</strong><br>What would I tell someone on my team during a 1:1 if they were in the same position as me? Role playing helps me give perspective — separating myself from the situation lets me assess it from an external point of view. Plus it helps keep my mentoring skills sharp…at the risk of occasionally talking to myself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*2nJdHC1iiwDf5wF5AzRwzg.jpeg" /></figure><p><strong>Practice, practice, practice</strong><br>I was lucky to land contract development work that helped me get over the slump. It kept my coding skills sharp, motivated me to be productive, and challenged my technical ability. This feed me creatively and pushed me to expand my knowledge of algorithms, dig deeper into system design, and get back to writing on engineering leadership.</p><p><strong>Make mental health a priority </strong><br>My state of mind has taken a hit during this job search; I’ve had to be very aware and proactive in order to maintain a healthy balance. Enjoying the afternoon sun on the front porch or seeing a matinee movie on a Friday helps me reset and recharge. It’s not perfect — I still get stressed and down, but it gives me a little grace to offset the negative.</p><h3>Looking Forward</h3><p>It’s been a weird year. There are small things I’d have done differently — before and after resigning — but I don’t regret my choice. I’ve had time to reflect, refine my career priorities, reconnect with why I got into leadership, and plan for how I’ll improve when I finally land somewhere.</p><p>As of this writing I’m still trying to find my next role with a team of talented engineers where I can grow as a leader. There are signs the market is slowly improving — new roles for engineers, recruiters, and product managers are becoming more plentiful. I’m hopeful this will led to more opportunities for folks like me. 🤞</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d090c3503654" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do or Do Not: Principles for Leading Remote Teams]]></title>
            <link>https://medium.com/@jeffreyabarron/do-or-do-not-principles-for-leading-remote-teams-f6c35bfe5fe6?source=rss-13640722090b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6c35bfe5fe6</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Jeffrey Barron]]></dc:creator>
            <pubDate>Tue, 07 May 2024 03:19:35 GMT</pubDate>
            <atom:updated>2024-05-07T04:22:48.098Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*oqaPi4eIWjeamZTDit5cZQ.jpeg" /></figure><p>I’ve learned a few hard earned lessons about what works for distributed teams and what doesn’t. They’ve started to form foundational principles I use to help ensure my teams have the best opportunity to navigate collaborating and working remotely.</p><p>Is this a definitive bulletproof list of industry best practices? No, it is very much a work-in-progress that I’ve gleaned by leading distributed teams the past few years. However it does represent adaptable approaches I’ve found help avoid a few of the pitfalls and limitations while working remotely.</p><h3>Do</h3><ul><li><strong>Be Proactive</strong>: When I started leading remote teams I thought that “no news is good news” and “people will reach out if they need help”. These assumptions have proven to be off the mark. Communication and connection is <em>substantially</em> harder in a remote environment; things that you get for free in-person require proactive cultivation on remote teams. I now search for opportunities for the team to gel, create space for random interaction and connection, and actively look for signs of someone struggling.</li><li><strong>Prioritize Async Methods:</strong> I lean heavily on asynchronous ways of communicating and gauging progress to help maximize focus time for my team while accommodating time zone differences. Pulling status information from team tools like Jira or Github, monitoring Slack channels, or testing features independently increases the likelihood that my team is more productive. If workflows and systems aren’t setup to work async, but they should be, then my priority is to successfully transition them to work better for remote distributed teams.</li><li><strong>Set Clear Expectations:</strong> Clearly outlining my expectations of the team and each person on the team ensures there’s no ambiguity or uncertainty. Creating a foundation of cultural norms within the team is a necessary first step — the level of collaboration, how we’ll communicate asynchronously, and the mechanics of work help created a shared environment for everyone to operate in.</li><li><strong>Document, Document, Document:</strong> I feel the best long-term outcomes for remote teams come from instilling a culture of recording key information. Capturing decisions and actions ensures the free flow of information for across the team regardless of availability to attend virtual discussions. Documenting progress and changes using project management tools enables other members of the team to pick up and continue work if needed. All these steps contribute to reducing the burden or reliance on any one person, reduces the stress from FOMO, and empowers the team’s resiliency over time.</li></ul><h3>Do Not</h3><ul><li><strong>Avoid Sync Interactions:</strong> Some things just require being in the same space at the same time, even if that space is virtual. From brainstorming sessions to 1:1’s there are certain things that cannot be handled async. Understanding when it’s appropriate is crucial; just because you are remote doesn’t mean you have to be disconnected.</li><li><strong>Use Identical Communication Styles:</strong> To fully support my team I typically need to use different means and methods of communication with each person. Any member of the team could struggle with in-person conversations but excel in written form; another engineer could be a morning person and would benefit from shifting the schedule of 1:1&#39;s. It’s all about adjusting and adapting to achieve as much transparency as possible with each person on the team.</li><li><strong>Ignore Boundaries:</strong> Remote work is great for increasing the odds you’ll be “in the zone” more over the course of a day. However blurring the line between work and home can happen subtly and innocently. The key is creating conditions for someone’s best work while ensuring they are fully supported to maintain limits on their work availability.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6c35bfe5fe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crafting Team Roles Through Analogy]]></title>
            <link>https://medium.com/@jeffreyabarron/crafting-team-roles-through-analogy-21233b50c65b?source=rss-13640722090b------2</link>
            <guid isPermaLink="false">https://medium.com/p/21233b50c65b</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[roles-and-responsibility]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[teams-and-teamwork]]></category>
            <dc:creator><![CDATA[Jeffrey Barron]]></dc:creator>
            <pubDate>Mon, 06 Feb 2023 04:34:01 GMT</pubDate>
            <atom:updated>2023-02-06T04:34:01.067Z</atom:updated>
            <content:encoded><![CDATA[<p>Whenever I’m presented with a complex problem my brain immediately tries to generate a mental model to classify and categorize the component parts and help understand the cohesive whole. My favorite approach is using analogy to abstract away hyper-specialized terms or ideas in favor of representing them with generic replacements.</p><p>For example, when I wanted to assess the strengths and weakness of my engineering team I came up with the idea of using the <a href="https://medium.com/@refinedmadness/character-classes-for-software-engineers-b883fd825c83">character classes system in many role-playing games</a> as a model to group traits. By identifying key characteristics common in different types of engineers I could create a baseline template to build on top of. Using this baseline I was able to devise methods to level-up their skills and create approaches to build cohesive teams that work well together.</p><h3>Using a Football Team as an Analogy</h3><p>Recently I had the opportunity to devise roles and responsibilities for one of my project teams. By default my mind searched for an analogy with a reasonable close fit that I could use to construct a framework for understanding how to structure a team.</p><p>Since it’s currently playoff season for American football the first thing that sprung to mind was how a football organization is structured and how that is roughly aligned with how a software team might operate. I came up with a series of generic roles that matched and identified possible responsibilities those roles might handle.</p><h4>Team Owner</h4><p>Similar to the owner of a football team the Team Owner is the key stakeholder for the team, setting the high-level direction and vision that will act as the guiding star for the team. This role also oversees the “budget” — the number of people that are part of the team and the time available for any given project to be implemented.</p><h4>Coach</h4><p>The Coach is responsible for creating the conditions for the team to successfully operate and empowering them to achieve their goals. They do this by thoughtful selecting members for the team, instilling the right culture, devising the high-level strategy, and figuring out the best methods to measure success.</p><p>A team may require multiple people acting as aCoach — perhaps a Product Owner and an Engineering Manager that work in conjuction with each other. In this case you can utilize a hierarchical approach of a Head Coachwith additional Coaches that correspond to a specific focus or discipline. By consistently aligning a singular vision across all Coaches you can avoid the “multiple bosses” problem that can often present within a hierarchy.</p><h4>Coordinator</h4><p>Much like how NFL teams use various coordinators to zero in on specific parts of gameplay — the offense, the defense, etc. — the Coordinator role is tasked with translating team strategy to a series of concrete tactical actions. They focus the team on specific goals, help them navigate difficulties, remove blockers from their path, and generally ensure alignment across the various levels and disciplines within the team.</p><h4>Captain</h4><p>The Captain is the role responsible for acting as the implicit leader within the group; it is who the team naturally turns to for guidance and motivation. They oversee the day-to-day execution within the team, play a key part guiding the team towards decisions, set and motivate the team to achieve their goals, and ensure things are kept on track.</p><h4>Player</h4><p>The beating heart of the team is made up of individual Players who collectively are responsible for architecting, designing, developing, testing, and integrating solutions. They are charged with achieving the goals of the team through dedicated, consistent, and repeatable action. They do this through constant communication with each other, brainstorming and collaborating to ensure the best outcomes.</p><h3>But my team is different!</h3><p>The essential benefit of a well-constructed mental model is that it is flexible by nature and can easily scale up or down as needed to correctly align with your team. Since each individual part is a composable piece of a larger puzzle it can be mixed and matched in various configurations.</p><p>For example if your team is just 3 people you can combine roles to match the specifics of your situation — a person could be a Coach, Coordinator, and Captain all rolled into one. Or you could simply assign the Captain and Player roles to the appropriate people and begin to execute on the work using a small, lightweight, and cohesive team structure.</p><p>However, while you can remove specific roles to meet the needs of your team, often the essential responsibilities of each role will still need to be handled. You will need to think about strategy, the tactical day-to-day, executing on specific work, and work towards ensuring alignment between all parts of your team.</p><h3>Just the beginning</h3><p>The simple fact of having a mental model of team roles isn’t a solution to how to structure teams, it is just the base from which you can start to understand the full team dynamics at play. In the end the flexibility of the model can be expanded to accommodate new roles and can be iterated on to assure full alignment with the responsibilities of your organization.</p><p>You must do the hard work to actually implement the roles, ensure the responsibilities are met, and successfully achieve the goals of the team week after week. But it all starts with crafting a framework to understand and help communicate your intent. Mental models — especially analogies — can be a great tool to kickstart that process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21233b50c65b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Organizational Amnesia Destroys Your Effectiveness]]></title>
            <link>https://medium.com/@jeffreyabarron/how-organizational-amnesia-destroys-your-effectiveness-287446c0353e?source=rss-13640722090b------2</link>
            <guid isPermaLink="false">https://medium.com/p/287446c0353e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Jeffrey Barron]]></dc:creator>
            <pubDate>Fri, 15 Dec 2017 03:04:50 GMT</pubDate>
            <atom:updated>2017-12-15T07:39:11.334Z</atom:updated>
            <content:encoded><![CDATA[<p>A couple of months ago my dad was diagnosed with “mild neuro-cognitive disorder”, which is a doctor’s way of saying early-stage dementia. After taking a moment to process what this means for him and the family (and slightly freak out about whether there were hereditary implications), I started to wonder if it was possible for a <em>company</em> to experience issues with memory. Since a company has institutional memory, made up of the collective experiences of it’s employees, can’t that memory start to degrade or disappear entirely?</p><p>While viewing a company’s memory loss as dementia takes the analogy a bit too far, it’s entirely possible to be striken with organizational amnesia, or a temporary loss of memory. Forgetting key facts about the past, both recent and historical, drastically limits the ability to leverage opportunities for growth by learning from what’s worked, and more importantly, what’s failed spectacularly.</p><p>Reduction of institutional memory can affect a few different dimensions:</p><ul><li><strong>Procedural</strong>: internal processes/workflows and how they are executed</li><li><strong>Historical</strong>: what happened when, the reasoning and outcomes of decisions, etc.</li><li><strong>Subject Matter</strong>: how systems and infrastructure are engineered, business rules, etc.</li><li><strong>Cultural</strong>: how the company operates, how it views itself and presents that externally</li></ul><h3>Processes are the Scars of Past Mistakes</h3><p>As companies start to grow they begin to formalize processes and workflows to weed out inefficiency, increase transparency, and ensure lessons learned are rolled into how things get done going forward. However, especially during transition phases (a merger, a substantial growth period), all this due diligence work can be easily thrown out the window in a foolish effort to “make things go faster.”</p><h4>All these rules make us slower!</h4><p>Let’s say your normal routine is to follow the Scrum methodology and start projects with large Epics that are broken down into smaller Epics, and then finally Stories, followed by Tasks, until each feature is a size easily estimated. When confronted with a new challenging project, instead of following your defined best practice, you decide because this is a new knowledge area for your team, you can’t possibly follow the process since it’ll take too long. It will just go quicker by outlining a little upfront and reacting to the conditions on the ground as you go.</p><p>This rarely works as planned and assumes your initial processes weren’t constructed to facilitate the fastest path forward, accounting for all possible risks, while still being agile. What often happens is instead of going <em>faster, </em>your team moves slower because they have to do extra yak shaving to add support mechanisms during the execution of the project. You end up with more ad-hoc communication, more miscues and false starts, and more wasting of time since it’s unclear what direction the architecture can and should take. In the end, the “waste” you were supposedly trying to avoid is spent regardless, but spent in unknown amounts and unknown ways as the project progresses. If your processes are slow, make them better first; don’t throw out the entire thing just to fix something easily nipped or tucked.</p><h4><strong>What’s a deadline anyway?</strong></h4><p>I’m very much a proponent of Agile methodologies, Scrum in particular, and feel that forecasting delivery timeline using average velocity and Release Trains is one of the best ways to see reliable results. That said, I understand those timelines have to be mapped onto a calendar with dates at some point. But if your organization isn’t robust enough to do forecasting, you are often left trying to do your best by quoting deadlines for features and projects to stakeholders.</p><p>If this is your situation, Organizational Amnesia can rear its ugly head through deadlines that are quoted without an underlying basis in fact, that are untracked, and for which there are little to no consequence for missing. If you are able to quote any date to make a stakeholder happy, knowing full well they won’t remember it, and your team will pay zero penalty for it, the temptation can sometimes be too great to avoid. It may be great for your area and teams, but organizationally it’s extremely unhealthy.</p><p>I’m not advocating that deadlines should be used as a weapon by stakeholders to name-and-shame engineering, but rather that missing deadlines is an incredible data point that can be used to improve the efficiency of your teams. When deadlines are missed, there are often a series of root causes to be discovered during Retrospectives and steps taken to resolve those issues. If you aren’t keep track of this, you are losing that opportunity! Instead, your organization is accepting the same results you are getting now — unrealistic deadlines, rarely met.</p><h3>Meet the New Mistake; Same as the Old Mistake</h3><p>Each day, sprint, quarter, and year, your organization is generating a rich history, filled with inspired choices, drastically wrong decisions, amazing project launches, and horrible mistakes. If you aren’t capturing the key points of each of these successes and failures, your internal history is written in Orwellian terms — you have been and always will be right, no exceptions.</p><p>Keeping a realistic historical record to guide your future decision making helps avoid making the same mistakes over and over by adjusting your operations to make them more efficient over time. By codifying these lessons learned, and making introspection and retrospection a part of your normal operations, you are creating an environment that values the growth powered by taking risks and feeling safe to fail.</p><h3>Don’t Let Your Bus Factor Get Too High</h3><p>When an organization doesn’t emphasize the collection and dissemination of knowledge, they can easily fall victim to the loss of memory throughout the company, department, or team. A friend of mine had a wonderful term for this — <em>the Bus Factor</em>. If any employee were to be hit by a bus tomorrow, how drastically would it affect your operations? The higher their degree of knowledge, the lower their amount of knowledge sharing within their team, the greater their Bus Factor and the more risk your organization is accepting.</p><p>While you definitely want to keep your retention levels high, and the loss of expertise is potential rather than actual, you have to take preventative action to ensure to cover your organization from extended memory loss. Centralizing code and access credentials, utilizing close-to-the-code documentation, enabling self-discovery and navigation of systems and services, leveraging configuration-as code for infrastructure, utilizing standardized tools and frameworks, codifying the what and why’s around business rules are all methods to prevent a future loss of domain knowledge. By actively and purposefully creating documentation-friendly systems and processes, leveraging automation, and emphasizing knowledge sharing, you can reduce your Bus Factor and get the potential risk to manageable levels.</p><h3>The Dr. Jekyll &amp; Mr. Hyde Problem</h3><p>Nearly every company has a set of core values, guiding principles, another similar list of statements meant to capture the essence of the culture for that organization. Done right these are reflective of how the company operates, how it views itself, how it presents itself externally, and how it tackles every challenge and dilemma.</p><p>Unfortunately, this cultural foundation can easily be assaulted by Organizational Amnesia when companies start to forget what these values truly mean and how they should guide every aspect of daily operations. If one of your core values is an emphasis on transparency, but it’s more common for information to be withheld, hidden, or spun, your organization has a form of cognitive dissonance. You think you are being transparent and espousing transparency, but the reality is quite different on a daily basis.</p><p>If left untreated for too long, this memory loss can start to affect lower down in your organization, creating a morale problem and making your core values more of a joke than a guiding light. Your cultural compass is broken and your decision making will inevitably be compromised because of it.</p><h3>It’s Not Too Late</h3><p>While each of these areas can cripple the efficiency of a company, Organizational Amnesia can be treated and cured. But first it has to be identified and acknowledged. By applying the lens of brutal honesty to how your organization operates, what it emphasizes, and what it truly values, memory loss can be reversed and ultimately eliminated. All it takes is the will to accept reality in all its ugliness and do something about it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=287446c0353e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Character Classes for Software Engineers]]></title>
            <link>https://medium.com/@jeffreyabarron/character-classes-for-software-engineers-b883fd825c83?source=rss-13640722090b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b883fd825c83</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[dungeons-and-dragons]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[professional-development]]></category>
            <dc:creator><![CDATA[Jeffrey Barron]]></dc:creator>
            <pubDate>Sat, 09 Dec 2017 01:27:49 GMT</pubDate>
            <atom:updated>2017-12-09T01:28:57.321Z</atom:updated>
            <content:encoded><![CDATA[<h4>What RPGs can teach us about identifying and leveraging common traits</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ROLBB7HPPQb0ce-3BJvPyg.jpeg" /></figure><p>Many role-playing games speed character creation by having stock “character classes” as shorthand for common traits that are used as a template or starting point. For instance, the granddaddy of them all —<a href="https://en.wikipedia.org/wiki/Character_class_(Dungeons_%26_Dragons)">Dungeons &amp; Dragons</a> — uses classes like Barbarian, Cleric, Paladin, Wizard, etc., each with their own qualities and attributes based on that class.</p><p>I’ve had the opportunity to work with a number of software engineers during my career — some bad, some good, some great. Over time, I’ve started to use the idea of character classes as an internal guide to how to identify commonalities based on the modus operandi of each engineer. These classes act as a baseline snapshot for each person and are then tweaked based on their individual strengths and weakness. When it’s time to send your group on an “adventure” or “campaign”, these classes can be invaluable to ensure the makeup of your group is balanced and has the greatest chances of success.</p><p>Here are some of the character classes I’ve come across in my travels.</p><h3>The Good</h3><h4>The Problem Solver</h4><p>This engineer is a generalist, the stereotypical jack-of-all-trades with substantial breadth, who enjoys encountering new problems, learning new skills, and applying their deep knowledge and insight to deliver robust solutions. They can consume an incredible amount of information, deconstruct an issue, pinpoint what’s wrong, and quickly rebuild something better.</p><h4>The Master Craftsman</h4><p>This engineer has the skill and vision that comes from being taught through multiple failed experiments. They know what works, know their own limitations, can tell when to optimize, and when to allow a solution to be good enough. The depth of their knowledge, combined with their meticulous approach to how they tackle problems through the use of applied learning, allows them to handle just about any problem quickly and thoroughly.</p><h4>The Eager Apprentice</h4><p>This engineer is newer to the field, don’t have the depth or breadth of experience, but are excited to learn, grow, and try new things. With clear mentorship and significant opportunity, they can grow into accomplished team players.</p><h4>The Wise Teacher</h4><p>This engineer takes the skills of problem solving and craftsmanship and combines it with their innate tendencies to teach those around them. They are patient mentors and teachers, sagely applying a keen eye to assisting their team and growing their abilities.</p><h3>The Bad</h3><h4>The Cowboy</h4><p>This engineer is always the fastest, churning out code at an insane rate, knocking out task after task. However, the solutions they come up with are often half-baked, riddled with holes, not scalable or sustainable, and often range so far off the beaten path that only they can fix them in the future.</p><h4>The Know-it-all</h4><p>This engineer always has an answer, an opinion on everything, and is happy to tell you why you are wrong. These contributors are often off-the-mark, don’t actually know everything, are unaware of their own limitations, and aren’t team players due to trying to be right all the time.</p><h3>Leveling Up</h3><p>As with the original, character classes for engineers can be combined in ways both good and bad, with each able to be improved independently. As they gain engineer eXperience Points (XP), an Eager Apprentice rarely stays that way for too long and a Master Craftsman may start to expand into the mentorship that’s a hallmark of a Wise Teacher. But always beware the unholy combination of classes that conjure up the Cowboy Know-it-all!</p><p>Each of these character class definitions are truly just starting points — every individual will have different areas that are stronger than another person of the same class. But since the foundational approaches are consistent, you are able to use them to help chart a course for career growth that is individualized to each engineer’s unique strengths, patterns, and preferences.</p><p>There are more classes that exist out in the wild beyond what is listed here, ones that I’ve just simply not encountered previously. However, using elements of RPGs as a tool to gain insight into your team is both a flexible and useful approach to understanding how to improve the effectiveness of your engineering organization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b883fd825c83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Splitting Teams into Backend and Front-end Goes Wrong]]></title>
            <link>https://medium.com/@jeffreyabarron/when-splitting-teams-into-backend-and-front-end-goes-wrong-fb12330aae51?source=rss-13640722090b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb12330aae51</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jeffrey Barron]]></dc:creator>
            <pubDate>Fri, 08 Dec 2017 02:29:26 GMT</pubDate>
            <atom:updated>2023-02-05T00:44:10.619Z</atom:updated>
            <content:encoded><![CDATA[<p>Congratulations! Your engineering team has grown to the point where they must take on more engineers to simply keep up with maintenance demand, let alone tackling the tsunami of new features being requested. Each new team member adds additional overhead, communication becomes harder, and you <em>have</em> to find a way to make things more efficient.</p><h3>The Trap</h3><p>After reviewing your growing team you notice really good engineers who excel at front-end work (HTML, CSS, JS), some that are amazing at backend systems, and a few in-between. “I’ll create two teams — one for front-end work and another for backend development” you think. “Similar skill sets will be together and everything will be great!”</p><blockquote>Wrong.</blockquote><p>While you’ve done a great job assessing your <strong><em>team</em></strong>, you fallen into the trap of not reviewing your current portfolio of products <em>or</em> forecasting the types of work your new teams will be tasked with over the next 12–18 months. You now have no clue if you’ve set them up for success or failure because you can’t say if their work will be isolated or inter-connected. Lacking this awareness of the field your engineers will be operating on is a crucial mistake.</p><p>If you’re lucky, your oversight will cause minimal issues with shipping features. Or maybe you can compensate with Herculean efforts using project management and coordination. If you are unlucky, you’ve just screwed your teams, limited their throughput, and decreased your reliability and consistency.</p><h3>The Problem</h3><p>Even though your engineering organization is growing, your project management approaches, communication channels, and workflows may not have followed suit. A backend/front-end split can, and does, work, but it often requires a maturity level your new teams probably aren’t ready to pull off quite yet.</p><p>If your products are still tightly coupled, when your stakeholders request new features requiring multiple tiers of your stack — say a new payment type for your application — the separation of your teams into focus areas can create inefficiencies. Any change in requirements will ripple through multiple teams, creating additional work, and creating blockers between them as one team waits on another.</p><p>This problem doesn’t magically stop after a feature is launched. When a bug is discovered, you are lucky if it can be isolated to just a single team. Now a bug report has to be completed for multiple teams, code has to be written across multiple codebases, and depending on the sophistication of your original implementation, you may have to coordinate deployment as well.</p><p>Instead of an internal discussion you’ve used previously, you now must coordinate work across two or more teams using some type of project management process or creation of architectural documentation (i.e. contracts via API). If you don’t, the requested feature will take longer than expected, the project will be delayed, all due to a core problem having nothing to do with the complexity of the feature being requested.</p><h3>A Better Way</h3><p>In agile terms, the original sin is the creation of teams unable to operate autonomously, that are focused too narrowly on <em>their</em> speciality, and the creation of dependencies between teams that must be managed. A better way is to avoid the dependency in the first place.</p><ul><li>Break away from backend/front-end functional teams by using cross-functional product teams who have a mixture of skills (back and front).</li><li>Empower teams with full autonomy over their product(s).</li><li>Mature your architecture and processes to adapt to, and support, this new orientation.</li></ul><p>Perhaps your organization is too small or your product portfolio is too large to setup true long-term, cross-functional teams focused on products. Instead try utilizing project teams that live for the duration of the project, disbanding at the end of a successful launch. While you can’t ride this approach forever, it <em>can</em> be a bridge between skill teams and product teams, by making a few rest stops with project teams. This will help your engineers start to think about the success of a product first instead of the walls between pieces and teams of that product.</p><h3>But…but…but</h3><blockquote>“But my engineers are not cross-functional — they have specific strengths and can’t work on everything!”</blockquote><p>As with many things, Mike Cohn has already addressed this concern by highlighting that <a href="https://www.mountaingoatsoftware.com/blog/cross-functional-doesnt-mean-everyone-can-do-everything">while “multi-skilled” engineers are preferred, specialists are fine</a>. In the end, it’s the <strong><em>team</em></strong> that should ultimately be cross-functional, not every single member of that team. That said, your engineers are probably more adaptable than you give them credit for. Give them the opportunity to try out new things in a safe, supportive, collaborative environment and see if they don’t surprise you.</p><blockquote>“Sure, but how will I improve the skills of my engineers if they don’t work with other people with the same skills? Iron sharpens iron!”</blockquote><p>There are a number of ways to do this that have minimal effect on the shipment of features — regular engineering discussions, baseline standards and approaches, technical talks (lightning or otherwise), architectural deep dives, etc. Taken to an extreme you may end up implementing something akin to <a href="http://blog.crisp.se/2012/11/14/henrikkniberg/scaling-agile-at-spotify">Spotify’s idea of “Chapters”</a> where similar engineers are grouped across team boundaries and it’s their responsibility to organize and associate amongst themselves.</p><blockquote>“How will I determine the performance of the engineers I oversee if I don’t have them all in one team?”</blockquote><p>The key is attempting to separate <em>reporting lines</em> from <em>team structure</em> and the product/projects they oversee. Sure, you may have supervisors mentoring engineers across multiple teams. But this ensures that your engineers look to the right authority for guidance — your Product Owner (or equivalent) for their daily work; their supervisor for mentorship and career growth. Differentiation between types of focus (career growth vs. product/project) is healthy and often necessary.</p><h3>One Size Fits All?</h3><p>Does this mean having backend and front-end teams is always wrong? Absolutely not. In many cases, this type of team structure can be incredibly successful — but it requires all of your support systems (leadership, project management, technology) to be aligned to meet the task of coordination. And it <strong><em>has</em></strong> to be done intentionally with an eye towards how and what your engineering organization develops. Otherwise, you are likely setting your teams up for frustrating failures they can’t easily fix.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb12330aae51" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>