<?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 Leonard Stellbrink on Medium]]></title>
        <description><![CDATA[Stories by Leonard Stellbrink on Medium]]></description>
        <link>https://medium.com/@leonst?source=rss-5fba49083d85------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7b5UOZJskqoFNg_Rsk2rRw.png</url>
            <title>Stories by Leonard Stellbrink on Medium</title>
            <link>https://medium.com/@leonst?source=rss-5fba49083d85------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:46:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leonst/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[Better Decision Making for Engineering Managers]]></title>
            <link>https://medium.com/@leonst/better-decision-making-for-engineering-managers-d074e6841ae4?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/d074e6841ae4</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Wed, 29 May 2024 13:07:27 GMT</pubDate>
            <atom:updated>2024-05-29T13:07:27.729Z</atom:updated>
            <content:encoded><![CDATA[<p>As an engineering manager, you have to make many important decisions every day. These decisions can affect your projects, your team’s success and your engineers careers. You might need to choose the right technology, set project deadlines, manage resources, or solve team issues. Because you make so many decisions, having good ways to think through problems is very helpful.</p><p>Mental models for decision making are tools that help you understand and solve problems more clearly and effectively. By using these models, you can make better decisions, handle challenges more easily, and lead your team to success.</p><p>To introduce you to my favorite 9 mental models for decision making I’ll share the general concept, application and a practical example with you. That way you have a practical guide for your next big or small decision to make. Save this article so you always have a decision model handy that helps you in the best way possible.</p><h3>First Principles Thinking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHLfDJIWV7-kvODBFfmd3Q.png" /></figure><p>First-principles thinking involves breaking down a complex problem into its most fundamental parts to understand the core components. By focusing on these basic elements, you can question assumptions, challenge established norms, and rebuild solutions from the ground up using fundamental truths. This approach helps uncover innovative solutions and create more efficient processes.</p><p>Encourage your team to dissect problems to their core elements when tackling complex issues. For instance, if you’re looking to optimize your software development process, break down each stage of the workflow to understand essential activities and resources.</p><p>When optimizing your CI/CD pipeline, identify the fundamental components like source control, build automation, testing, and deployment. Understand the core requirements of each component and find the most efficient tools and practices to streamline the process.</p><p>A real-world example of first-principles thinking is how Elon Musk approached the problem of building affordable rockets at SpaceX. Traditionally, rockets were extremely expensive, costing hundreds of millions of dollars each. Instead of accepting this high cost as a given, Musk broke the problem down into its basic elements.</p><p>He asked fundamental questions about what materials are required to build a rocket and what those materials cost on the commodity market. By identifying that the raw materials — such as aluminum, titanium, copper, and carbon fiber — constituted only a fraction of the total cost of a traditional rocket, Musk realized that he could significantly reduce expenses by manufacturing the components in-house and rethinking the design and assembly processes.</p><p>This approach allowed SpaceX to develop the Falcon 1 rocket for about $9 million, a fraction of the industry standard at the time, revolutionizing the space industry and enabling more frequent and cost-effective space missions.</p><h3>Confidence Determines Speed vs. Quality</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*13UROYibY9x4rLPwA_gUFQ.png" /></figure><p>Your confidence level in understanding a problem should dictate the balance between speed and quality in decision-making. When you have a high level of confidence in your understanding of a problem and its solution, you should prioritize quality, taking the time to ensure that the solution is robust and thorough. Conversely, when you are less confident and need to gather more information or test assumptions, it’s better to prioritize speed.</p><p>This allows you to quickly iterate, learn, and adjust your approach based on feedback and new insights.</p><p>As an engineering manager, assess your team’s expertise and the criticality of the problem at hand before deciding on the approach. For high-confidence issues like known bugs or performance bottlenecks, allocate resources for a comprehensive solution to ensure robustness and reliability. For areas with less certainty, such as integrating a new framework or experimenting with a novel feature, encourage rapid prototyping and incremental testing.</p><p>This adaptive approach not only conserves resources but also fosters innovation and continuous learning within the team. Regularly review outcomes to adjust your strategy, ensuring a balance between speed and quality that aligns with project goals and organizational priorities.</p><h3>Second order thinking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wv4NEjrizTOKgScycfqtsg.png" /></figure><p>Second-order thinking involves considering the long-term consequences of your decisions by continuously asking, “<em>And then what?</em>” This approach goes beyond the immediate outcomes to explore the ripple effects of your actions. By thinking several steps ahead, you can anticipate potential challenges and opportunities that might arise as a result of your decision.</p><p>Encourage your team to think beyond immediate results. When making decisions, ask them to consider the potential long-term impacts on the project, team, and organization.</p><p>For example, when selecting a technology stack, evaluate not only the immediate benefits but also the future maintenance, scalability, and compatibility with other systems. This foresight can prevent unforeseen problems and promote sustainable growth.</p><h3>Scientific Method</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvgbRZ_iYn62TGvFw-0JQQ.png" /></figure><p>The scientific method uses a structured approach of hypothesis testing and experimentation to solve problems and validate ideas.</p><p>This process begins with careful observation and the formulation of a specific, testable question. After gathering background information, a hypothesis is constructed — essentially an educated guess about the expected outcome. This hypothesis is then tested through controlled experiments, where data is collected and analyzed to determine whether the hypothesis holds true. The results of the experiments either support or refute the hypothesis, leading to conclusions that inform further experimentation or adjustments.</p><p>For example, If you hypothesize that a new project management tool will improve team efficiency, you can pilot the tool with a small team, collect data on productivity and satisfaction, and analyze the results to decide whether to roll it out more broadly.</p><p>This methodical approach ensures that decisions are based on evidence and logical reasoning, reducing uncertainty and increasing the likelihood of successful outcomes.</p><h3>Decision Matrix</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mpl-6r_1b93qy1jXcuuAeA.png" /></figure><p>A decision matrix helps compare options based on weighted criteria to determine the best choice.</p><p>This tool involves listing your options and the criteria important for making your decision, then assigning a weight to each criterion based on its significance. Each option is scored against each criterion, and these scores are multiplied by the corresponding weights. The weighted scores for each option are then summed to provide a total score, making it clear which option best meets the criteria overall.</p><p>Use a decision matrix for complex choices that involve multiple factors. When selecting a new project management tool, list criteria such as functionality, cost, ease of use, and support. Assign weights to each criterion based on importance, score each option, and calculate the weighted scores to determine the best choice.</p><p>This systematic approach ensures a balanced evaluation and helps justify decisions to stakeholders.</p><h3>Reversible vs. Irreversible Decisions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7f6clcTAMVJBjq6H5Bk-jw.png" /></figure><p>Classify decisions to optimize decision-making speed. Reversible decisions are those that can be easily undone or altered, allowing for quick action and experimentation without significant long-term consequences. Irreversible decisions, on the other hand, have lasting impacts and are difficult or impossible to change once made, necessitating a more deliberate and cautious approach.</p><p>By distinguishing between these two types of decisions, you can allocate your time and resources more effectively.</p><p>Combat analysis paralysis by implementing a decision-making framework that categorizes decisions based on their reversibility. Start by training your team to quickly identify whether a decision is reversible (a “two-way door”) or irreversible (a “one-way door”). For reversible decisions, set shorter deadlines and encourage rapid execution and iteration. For irreversible decisions, allocate more time for thorough analysis and stakeholder consultation to ensure the best possible outcome.</p><p>Additionally, establish a decision-making hierarchy where routine and low-risk decisions are delegated, freeing up time for more critical issues. This approach not only speeds up the decision-making process but also empowers your team to take initiative and learn from their experiences, fostering a more agile and responsive work environment.</p><h3>Devil’s Advocate Position</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wm_Bw0MOq9b1qBYDoGwYpw.png" /></figure><p>Counteract confirmation bias by considering opposing viewpoints or encouraging dissenting opinions. This involves intentionally challenging your assumptions and the prevailing perspective to uncover potential flaws and alternative solutions.</p><p>By adopting or assigning someone to take the devil’s advocate role, you force a thorough examination of the decision at hand. This practice can reveal hidden risks, weaknesses in the argument, or overlooked opportunities, leading to more balanced and robust decision-making.</p><p>To effectively implement the Devil’s Advocate position in your team, create a culture where constructive criticism is valued and dissenting opinions are encouraged. Designate specific team members to take on the role of Devil’s Advocate during critical decision-making meetings. Ensure this practice is seen as a valuable part of the process rather than a challenge to authority. Regularly rotate this responsibility to provide diverse perspectives and prevent any single viewpoint from dominating.</p><p>By institutionalizing this practice, you’ll uncover hidden risks, validate assumptions, and ultimately arrive at more robust and well-considered decisions. This approach not only improves decision quality but also fosters an environment of open dialogue and critical thinking.</p><h3>Pre-Mortem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w1tqJFZ8k2Q1GuNuAoOaRw.png" /></figure><p>Assume your decision has failed and work backwards to identify potential causes. This technique involves envisioning a scenario where your project or decision has not succeeded, and then analyzing what might have led to this failure.</p><p>By identifying potential pitfalls and challenges in advance, you can address them proactively and improve your chances of success.</p><p>Incorporate pre-mortem sessions as a standard part of your project planning process. Schedule a dedicated meeting before significant project milestones where team members collectively envision the project failing and brainstorm potential reasons for the failure. Encourage an open and honest discussion, ensuring all voices are heard and all aspects of the project are scrutinized. Document these potential pitfalls and develop action plans to mitigate identified risks.</p><p>This proactive approach helps in uncovering blind spots, refining strategies, and improving overall project resilience. Additionally, it promotes a culture of anticipatory thinking and continuous improvement, ensuring that your team is better prepared to handle challenges and deliver successful outcomes.</p><h3>Backward Chaining</h3><p>Backward chaining involves starting with the end goal and working backward to determine the necessary steps to achieve it.</p><p>This method requires you to clearly define your desired outcome first, and then identify the sequential actions needed to reach that outcome from your current position. By visualizing the end result and mapping out the pathway in reverse, you can ensure that every step taken is purposeful and directly contributes to achieving the goal.</p><p>For example, if your objective is to release a new software feature by a specific date, backward chaining would have you first outline the final deliverables, then determine the testing, development, design, and planning phases required to meet that deadline. This approach helps in creating a realistic timeline, identifying critical dependencies, and allocating resources effectively, ensuring that you stay on track to meet your objectives.</p><p>By working backward, you can anticipate potential obstacles and make necessary adjustments early in the planning process, enhancing the overall efficiency and success of your project.</p><h3>Conclusion</h3><p>As an engineering manager, mastering decision-making is crucial for the success of your projects, team, and organization.</p><p>The mental models discussed provide you with practical tools to navigate complex challenges effectively. Incorporating these models into your daily practices, you can make more informed, balanced, and strategic decisions.</p><p>This not only enhances your ability to solve problems and innovate but also fosters a proactive and resilient team culture. Continuously applying these models will help you lead with confidence, drive your team toward success, and achieve your organizational goals with greater efficiency and foresight.</p><p>Want to become a better Engineering Manager?<br>Get more Engineering Management articles sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d074e6841ae4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mark Twain’s Perspective on Engineering Management]]></title>
            <link>https://medium.com/@leonst/mark-twains-perspective-on-engineering-management-e0f8ca44c0b1?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0f8ca44c0b1</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mark-twain]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Sun, 19 May 2024 12:20:39 GMT</pubDate>
            <atom:updated>2024-05-19T12:20:39.510Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SDphrrkpIa_Q0gg02m5ykw.jpeg" /></figure><p>As an engineering manager, I’ve found that leading a team requires both technical skills and strong leadership. The wisdom of Mark Twain, one of America’s greatest writers, can actually be very helpful for engineering managers. Twain’s insights about people, perseverance, and communication are relevant to the challenges and duties that engineering leaders face every day.</p><p>In engineering management, it’s crucial to motivate your team, encourage innovation, and communicate effectively. Mark Twain’s humor and wisdom offer a unique view on these important aspects of leadership. His thoughts on human behavior and progress can help you create a productive and positive work environment. By using Twain’s principles, you can improve your leadership style, ensuring your team is both inspired and efficient.</p><p>I will discuss four of Twain’s most impactful quotes and explain how they can be applied to engineering management. This will show how his timeless wisdom can lead to better leadership and more successful projects.</p><h3>Getting Ahead by Getting Started: Projects and Milestones</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JhEsG5v1sdXyJjF0RHgYaw.jpeg" /></figure><p>One of the most important lessons I’ve learned from Mark Twain quotes is that <strong><em>“The secret of getting ahead is getting started”</em></strong><em>.</em> In engineering management, this principle is crucial, especially when it comes to handling projects and milestones. The vast scope of engineering projects can often feel overwhelming, leading to delays and inaction. Breaking down a project into smaller, manageable milestones makes the task seem more achievable and sets the stage for continuous progress.</p><p>Here are practical ways to get ahead by getting started:</p><h4>Break Down Projects into Manageable Milestones</h4><p>When launching a new product, start with an initial phase like research and development. Set a clear milestone, such as completing a feasibility study or developing a prototype.</p><p>Achieving this first milestone provides a tangible goal for the team, moving the project forward and boosting confidence and motivation. Each subsequent milestone becomes a stepping stone, making the overall project less daunting.</p><h4>Identify Initial Steps to Create Momentum</h4><p>Outline the initial tasks that need to be accomplished, even if they are small. This could include gathering requirements, conducting market research, or setting up a project timeline.</p><p>Identifying and completing initial steps creates momentum that propels the project forward. It prevents the team from falling into the trap of overplanning and overthinking.</p><h4>Set Clear and Achievable Goals</h4><p>Create a detailed project plan with defined milestones. Outline the key tasks, deadlines, and responsible individuals for each milestone. This task can easily be delegated to project leads.</p><p>A clear project plan provides a roadmap for the team, helping to maintain focus and track progress. It also makes it easier to identify potential issues early on and make necessary adjustments.</p><h4>Regularly Review and Adjust Milestones</h4><p>Schedule regular progress reviews to assess whether the project is on track. Use these meetings to adjust milestones as needed based on new information or changes in the project scope.</p><p>Regular reviews ensure that milestones remain relevant and attainable. They provide opportunities to course-correct and keep the team’s efforts aligned with the overall objectives.</p><h4>Celebrate Milestone Achievements</h4><p>Recognize and celebrate the completion of each milestone. This could be through a team meeting, a celebratory email, or small rewards.</p><p>Celebrating achievements reinforces the importance of each milestone and keeps the team motivated. It provides a sense of accomplishment and progress, encouraging the team to continue striving towards the next goal.</p><h4>Foster a Proactive Approach</h4><p>Encourage team members to proactively identify and address potential issues before they become major setbacks. Use tools like risk assessments and contingency planning.</p><p>A proactive approach helps in managing uncertainties and complexities effectively. It ensures that the team is prepared to handle challenges and keeps the project on track.</p><h3>Cheering Others to Boost Morale</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lgSrPTISpCYvjw7fWrLLYg.jpeg" /></figure><p>A motivated team is a productive team. As Mark Twain wisely noted, <strong><em>“The best way to cheer yourself up is to try to cheer somebody else up”</em></strong>. Supporting and recognizing the efforts of each team member goes a long way in fostering a positive work environment. Addressing their concerns, celebrating their achievements, and promoting a culture of collaboration and trust can significantly boost morale. When the team feels valued, they perform at their best.</p><p>Here are some practical ways to create a supportive and encouraging environment:</p><h4>Regular Recognition and Praise</h4><p>Implement a system where team members can publicly recognize each other’s contributions during weekly meetings. This can be done through a “Kudos” board where anyone can post a note of appreciation for a colleague’s hard work.</p><p>This not only boosts the morale of the person being praised but also fosters a culture of mutual respect and appreciation. It reminds everyone that their efforts are noticed and valued.</p><h4>Addressing Concerns Promptly</h4><p>Set up regular one-on-one meetings with your team members to discuss their concerns and feedback. This could be as simple as a weekly check-in where team members can speak openly about their challenges.</p><p>By actively listening and addressing concerns, you show that you care about their well-being and professional growth. This builds trust and helps in resolving issues before they escalate.</p><h4>Celebrating Achievements</h4><p>Organize small celebrations for project milestones or individual achievements. This could be a team lunch, a shout-out in the company newsletter, or even a simple email highlighting the accomplishment.</p><p>Celebrating achievements, no matter how small, reinforces a sense of accomplishment and motivates the team to continue striving for excellence.</p><h4>Encouraging Peer Support</h4><p>Create opportunities for team members to mentor each other. For instance, pairing up a senior engineer with a junior engineer on projects can help the junior learn and grow while giving the senior a sense of fulfillment and responsibility.</p><p>This promotes knowledge sharing and strengthens the bonds between team members, leading to a more cohesive and supportive team dynamic.</p><h4>Fostering a Collaborative Environment</h4><p>Use collaborative tools and techniques such as regular brainstorming sessions, cross-functional projects, and open communication channels like Slack for quick, informal interactions.</p><p>Encouraging collaboration helps break down silos and ensures that everyone feels they are part of a team working towards common goals. It also makes it easier to share successes and learn from each other.</p><h4>Leading by Example</h4><p>Show appreciation and cheerfulness in your daily interactions. A simple “thank you” or “great job” can go a long way.</p><p>When you model positive behavior, it sets the tone for the entire team. Your actions will encourage others to follow suit, creating a ripple effect of positivity and support throughout the team.</p><h3>Challenging the Status Quo</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPycc9nxsqrXKAJVfLdATA.jpeg" /></figure><p>Innovation often springs from challenging the status quo. As Mark Twain wisely said, <strong><em>“Whenever you find yourself on the side of the majority, it is time to pause and reflect”.</em></strong> In engineering management, it’s crucial to foster an environment where critical thinking and unconventional solutions are encouraged. Promoting diverse perspectives and independent thinking can lead to groundbreaking innovations. It’s essential to create a culture where questioning and experimentation are valued, especially in the face of the pervasive statement, “We’ve always done it this way.”</p><p>Here are some practical ways to challenge the Status Quo:</p><h4>Encourage Critical Thinking</h4><p>During project planning meetings, allocate time for team members to question existing processes and suggest alternative approaches. Create a safe space where team members feel comfortable expressing their ideas, no matter how unconventional they may seem.</p><p>This practice ensures that team members are not just following routines blindly but are actively thinking about how to improve processes and outcomes. It helps to identify inefficiencies and sparks innovative solutions.</p><h4>Challenge the “We’ve Always Done It This Way” Mentality</h4><p>When someone uses the phrase “We’ve always done it this way,” use it as an opportunity to explore new methods. Ask probing questions like, “What would happen if we tried a different approach?” or “Can we identify any recent advancements that might improve this process?”</p><p>Challenging this mentality helps to break down barriers to innovation and encourages the team to continuously seek better ways of doing things. It shifts the focus from maintaining the status quo to striving for excellence and improvement.</p><h4>Promote Diverse Perspectives</h4><p>Assemble cross-functional teams for projects to bring in diverse viewpoints. Include team members from different backgrounds, experience levels, and departments.</p><p>Diverse perspectives can lead to more creative solutions and help the team see problems from different angles. This approach fosters a culture of inclusivity and broadens the range of ideas and solutions considered.</p><h4>Create Innovation Challenges</h4><p>Organize regular innovation challenges where team members can present new ideas and solutions. Offer incentives for the best ideas and provide resources for experimentation and prototyping.</p><p>Innovation challenges stimulate creative thinking and provide a platform for team members to showcase their ideas. It encourages a proactive approach to problem-solving and keeps the team engaged and motivated.</p><h4>Foster a Culture of Experimentation</h4><p>Implement a “fail fast, learn faster” approach. Encourage small-scale experiments and pilots to test new ideas quickly. Provide a framework for evaluating these experiments and learning from both successes and failures.</p><p>A culture of experimentation reduces the fear of failure and encourages continuous learning and improvement. It allows the team to rapidly iterate and refine ideas, leading to more effective and innovative solutions.</p><h3>The Importance of Clear Goals</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0XYXDvk3rWvfI4Ct0_M6Q.jpeg" /></figure><p><strong><em>“Having lost sight of our goals, we redouble our efforts”.</em></strong> Mark Twain’s quote underscores a common pitfall in engineering management: working harder without a clear direction. When your team loses sight of their goals, their efforts, no matter how intense, can become misguided and inefficient. Ensuring that goals are clear, well-communicated, and consistently revisited is crucial for maintaining focus and achieving success.</p><p>Here are practical ways to make sure your team always have a clear direction:</p><h4>Set Clear, Specific Goals</h4><p>At the start of each project, define clear and specific objectives. Use SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound) to ensure that goals are well-defined.</p><p>Clear goals provide a roadmap for your team, ensuring everyone knows what they are working towards. This focus prevents wasted effort on tasks that do not contribute to the desired outcomes.</p><h4>Communicate Goals Effectively</h4><p>Hold a kickoff meeting at the beginning of each project to explain the goals and how they align with the overall mission of the organization. Provide written documentation for reference.</p><p>Effective communication ensures that all team members understand the goals and their importance. It aligns the team’s efforts and fosters a sense of shared purpose.</p><h4>Regularly Review and Adjust Goals</h4><p>Schedule regular check-ins and progress reviews to assess whether the team is on track to meet the goals. Use these meetings to adjust goals as needed based on new information or changes in the project scope.</p><p>Regular reviews keep goals relevant and attainable. They provide opportunities to course-correct and ensure that the team’s efforts remain aligned with the objectives.</p><h4>Use Visual Management Tools</h4><p>Implement visual management tools such as Gantt charts to track progress towards goals. Display these tools in a common area where the team can see them daily.</p><p>Visual tools provide a constant reminder of the goals and the team’s progress. They help in identifying bottlenecks and ensuring that efforts are directed towards achieving the set objectives.</p><h4>Empower Team Members to Own Goals</h4><p>Assign specific goals to individual team members or sub-teams and empower them to take ownership. Provide them with the autonomy and resources needed to achieve these goals.</p><p>When team members take ownership of goals, they are more invested in achieving them. This empowerment boosts motivation and accountability.</p><h4>Celebrate Milestones and Achievements</h4><p>Recognize and celebrate when the team reaches significant milestones or achieves goals. This could be through a team lunch, public recognition, or small rewards.</p><p>Celebrating achievements reinforces the importance of the goals and motivates the team to continue their efforts. It also provides a sense of accomplishment and progress.</p><h4>Define and Communicate Team Vision</h4><p>Create a clear, compelling vision statement for your team that aligns with the organization’s broader mission. Share this vision regularly in team meetings and integrate it into everyday conversations.</p><p>A clear team vision helps in unifying the team’s efforts towards a common goal. It provides direction and motivation, ensuring that everyone understands their role in achieving the broader objectives.</p><h4>Establish and Track Metrics</h4><p>Develop key performance indicators (KPIs) to measure progress towards your goals. Use dashboards to track these metrics in real-time and share updates with the team.</p><p>Tracking metrics provides objective data on the team’s progress, helping to maintain focus and accountability. It allows for timely interventions if the team is falling behind and celebrates progress when milestones are achieved.</p><h3>Conclusion</h3><p>Mark Twain’s insights offer great advice for engineering managers who want to lead their teams well. His thoughts on people, hard work, and communication are very relevant to the challenges engineering leaders face every day.</p><p>From understanding the importance of getting started and setting clear, achievable milestones, to recognizing the value of cheering others to boost morale, Twain’s principles are timeless. Encouraging innovation by challenging the status quo and making sure goals are well-defined and regularly reviewed are key practices that can improve your team’s performance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0f8ca44c0b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This Month in Engineering Management April 2024]]></title>
            <link>https://medium.com/@leonst/this-month-in-engineering-management-april-2024-a1d24510becb?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1d24510becb</guid>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Tue, 07 May 2024 11:07:15 GMT</pubDate>
            <atom:updated>2024-05-07T11:07:15.224Z</atom:updated>
            <content:encoded><![CDATA[<h4>Everything that happened in Engineering Management in April 2024</h4><p>Welcome to the April 2024 and fourth edition of <em>This Month in Engineering Management</em>! After some more time of parental leave and putting my son in daycare (which is a process in itself). I start to find time again to write. First though let me share what I read regarding Engineering Management last month.</p><p>Let’s check out what happened this month in Engineering Management:</p><h3>Your Team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*adGNiB3B8IOlSAyV" /></figure><h4><a href="https://medium.com/management-matters/fun-ways-to-use-the-meeting-scribe-role-for-leadership-development-437a8b3f8b52">Fun Ways to Use the Meeting Scribe Role for Leadership Development</a></h4><p><a href="https://medium.com/management-matters/fun-ways-to-use-the-meeting-scribe-role-for-leadership-development-437a8b3f8b52">Fun Ways to Use the Meeting Scribe Role for Leadership Development</a></p><p><strong>Key Lesson: T</strong>he role of a meeting scribe, often overlooked, can be a powerful tool for developing leadership skills. By assigning scribe duties strategically, you can give employees a chance to practice essential leadership behaviors such as organizing meetings, setting agendas, managing discussions, and overseeing follow-up tasks. This approach allows them to demonstrate their potential and readiness for managerial roles in a low-stakes environment, while also gaining the confidence of their peers.</p><h4><a href="https://medium.com/@oguzkilic/diversity-and-inclusion-in-engineering-teams-2320817a7277">Diversity and Inclusion in Engineering Teams</a></h4><p><a href="https://oguzkilic.medium.com/diversity-and-inclusion-in-engineering-teams-2320817a7277">Diversity and Inclusion in Engineering Teams</a></p><p><strong>Key Lesson</strong>: By bringing together a variety of perspectives and backgrounds, teams can generate more innovative solutions and perform better overall. To capitalize on this diversity, it is crucial for leaders to adopt inclusive practices that ensure all team members feel valued and are actively involved in decision-making processes. Such practices not only enhance team dynamics but also contribute to the overall effectiveness and success of the organization.</p><h3>Your Career</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bekxKEZIgOmqt3SW" /></figure><h4><a href="https://medium.com/@munawarnoorani786/introverts-in-leadership-68ae064272ba">Introverts in Leadership</a></h4><p><a href="https://medium.com/@munawarnoorani786/introverts-in-leadership-68ae064272ba">Introverts in Leadership</a></p><p><strong>Key Lesson:</strong> As an engineering manager, it’s important for you to recognize that the traditional extroverted model of leadership is not the only effective approach. Introverted leaders, often overlooked, bring unique strengths that are highly beneficial in leadership roles. You should appreciate the quiet, thoughtful, and introspective qualities that introverts possess, which enable them to listen deeply, think critically, and make well-considered decisions. These qualities allow them to create inclusive environments where all team members feel valued and heard. If you are an introvert that will help you see yourself in a leadership position and what leadership qualities you have as an introvert.</p><h4><a href="https://medium.com/@glamiacy/lessons-ive-learned-as-a-leader-the-ladder-of-leadership-5a22b5a7e7bd">Lessons I’ve Learned as a Leader — The Ladder of Leadership</a></h4><p><a href="https://medium.com/@glamiacy/lessons-ive-learned-as-a-leader-the-ladder-of-leadership-5a22b5a7e7bd">Lessons I’ve Learned as a Leader — The Ladder of Leadership</a></p><p><strong>Key Lesson:</strong> The “Ladder of Leadership” teaches you to enhance your team’s problem-solving skills by guiding them through a series of steps designed to clarify their understanding and intentions before taking action. By encouraging your team to articulate their perspective, analyze options, and propose solutions, you not only foster their independence and confidence but also improve alignment and accountability within the team. This approach not only builds a more self-sufficient team but also elevates your own leadership by shifting from direct problem-solving to facilitating and mentoring your team’s decision-making process.</p><h3>Your Tech</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3Mfb7Wh34Dy4FloI" /></figure><h4><a href="https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-can-make-your-aws-bill-explode-934a383cb8b1">How an empty S3 bucket can make your AWS bill explode</a></h4><p><a href="https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-can-make-your-aws-bill-explode-934a383cb8b1">How an empty S3 bucket can make your AWS bill explode</a></p><p><strong>Key Lesson:</strong> Always ensure your S3 buckets have unique names to prevent misconfiguration issues and unauthorized access. Explicitly specify the AWS region in your requests to avoid unnecessary charges from request redirections. Additionally, enable access logging to monitor and respond to unauthorized access promptly. These steps will help you manage costs effectively and enhance security, protecting your projects from unexpected charges and potential data leaks.</p><h4><a href="https://medium.com/@srinathperera/how-to-approach-software-architecture-a-first-principle-perspective-3b865d35bb9b">How to approach Software Architecture? A First Principle Perspective</a></h4><p><a href="https://medium.com/@srinathperera/how-to-approach-software-architecture-a-first-principle-perspective-3b865d35bb9b">How to approach Software Architecture? A First Principle Perspective</a></p><p><strong>Key Lesson</strong>: You should focus on designing systems that are adaptable and can evolve over time, emphasizing the importance of making early architectural decisions that are hard to change later. It’s crucial to start with a flexible, minimum viable product and iterate based on user feedback. However, equally important is deep thinking about critical components such as APIs, databases, and integration points, which are difficult to modify once set.</p><h3>Your Processes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4CSML8ee486IHZj_" /></figure><h4><a href="https://ehandbook.com/how-to-drive-maximum-revenue-sequencing-your-projects-f1da4519f0e2">How to Drive Maximum Revenue: Sequencing Your Projects</a></h4><p><a href="https://ehandbook.com/how-to-drive-maximum-revenue-sequencing-your-projects-f1da4519f0e2">How to Drive Maximum Revenue: Sequencing Your Projects</a></p><p><strong>Key Lesson:</strong> Instead of dispersing your team’s efforts across multiple projects simultaneously, which can make them feel busy but delay real business progress, focus on completing fewer projects at a time. This concentrated approach allows you to launch products quicker and start generating value sooner, which is crucial in contexts where early wins compound over time. Begin with low-risk projects that require minimal new development and can be delivered swiftly, ensuring early victories that bolster revenue and set a strong foundation for tackling more complex challenges.</p><h4><a href="https://medium.com/management-matters/why-should-every-manager-use-situational-leadership-e7e6ec298c5b">Why should every manager use Situational Leadership?</a></h4><p><a href="https://medium.com/management-matters/why-should-every-manager-use-situational-leadership-e7e6ec298c5b">Why should every manager use Situational Leadership?</a></p><p><strong>Key Lesson: </strong>it’s crucial for you to recognize that relying solely on one leadership style, much like only having a hammer in your toolkit, limits your effectiveness in managing a diverse team. The Situational Leadership Theory emphasizes that no single leadership style is superior; instead, you should adapt your style based on the readiness and the task-specific needs of each team member. This approach enables you to be more flexible and responsive, enhancing your ability to lead effectively across different situations. By varying your leadership style — from directing to delegating, coaching to supporting — you can better meet individual team members where they are, helping them to develop and succeed in their roles.</p><p>Don’t want to to miss an edition of <em>This month in Engineering Management</em>? Get them sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1d24510becb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This Month in Engineering Management March 2024]]></title>
            <link>https://medium.com/@leonst/this-month-in-engineering-management-march-2024-8c2f17579071?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c2f17579071</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Sun, 07 Apr 2024 13:02:45 GMT</pubDate>
            <atom:updated>2024-04-07T13:28:57.207Z</atom:updated>
            <content:encoded><![CDATA[<h4>Everything that happened in Engineering Management in March 2024</h4><p>Welcome to the March 2024 and third edition of <em>This Month in Engineering Management</em>! I’m a bit late with this edition because of a dental surgery and the time I needed to recover. Gum Craft — only soup for a week and you can barely speak. I start to feel better and don’t want you to be waiting for this month’s Engineering Management highlights.</p><p>First quarter is over! Time to run a retrospect and check in with everybody how it went! If you haven’t yet, check your roadmap how the planned projects vs realized projects look like.</p><p>Let’s check out what happened this month in Engineering Management:</p><h3>Your Team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*adGNiB3B8IOlSAyV" /></figure><h4><a href="https://medium.com/@leonst/build-your-teams-communication-foundation-e8665e50383d"><strong>Build your Team’s Communication Foundation</strong></a></h4><p><a href="https://medium.com/@leonst/build-your-teams-communication-foundation-e8665e50383d">Build your Team’s Communication Foundation</a></p><p><strong>Key Lesson: </strong>You should implement tools like a communication charter and team README to enhance understanding and coordination. The communication charter serves as a roadmap for navigating the complexities of asynchronous communication, establishing core hours, and setting expectations for availability and meeting scheduling. On the other hand, the team README personalizes the remote working experience, detailing each member’s background, preferences, and interests, fostering empathy and a cohesive team culture. Together, these tools ensure that despite physical distances, your team remains connected, informed, and aligned, laying the groundwork for a productive and harmonious work environment.</p><h4><a href="https://medium.com/@leonst/spring-cleaning-as-an-engineering-manager-9ca9fa27b6c0">Spring cleaning as an Engineering Manager</a></h4><p><a href="https://medium.com/@leonst/spring-cleaning-as-an-engineering-manager-9ca9fa27b6c0">Spring cleaning as an Engineering Manager</a></p><p><strong>Key Lesson</strong>: As an engineering manager, you should embrace the spirit of spring cleaning to assess and streamline workflows, prioritize tasks in alignment with organizational goals, declutter digital spaces, and foster continuous improvement. Implementing practices like evaluating current workflows, automating repetitive tasks, simplifying communication channels, and using the Eisenhower Box for task prioritization can lead to a more focused and effective team. Regularly decluttering digital workspaces helps maintain a clear and efficient working environment. By doing so, you not only improve the current state of affairs but also set the stage for sustained team performance and well-being.</p><h3>Your Career</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bekxKEZIgOmqt3SW" /></figure><h4><a href="https://medium.com/@leonst/whats-success-for-engineering-managers-dad81ea00cc7">What’s Success for Engineering Managers?</a></h4><p><a href="https://medium.com/@leonst/whats-success-for-engineering-managers-dad81ea00cc7">What’s Success for Engineering Managers?</a></p><p><strong>Key Lesson:</strong> You, as an engineering manager, should strive to cultivate an environment where team members are empowered to make decisions, solve problems independently, and continuously learn and grow. This involves shifting from a directive approach to one that supports and guides, fostering a culture where feedback is a tool for growth and every member feels valued and motivated. Success is measured not just by immediate outcomes but by the team’s ongoing development, their ability to innovate, and their alignment with organizational goals.</p><h4><a href="https://medium.com/@leonst/lessons-from-soulcycle-for-engineering-managers-b71ced3585d3">Lessons from SoulCycle for Engineering Managers</a></h4><p><a href="https://medium.com/@leonst/lessons-from-soulcycle-for-engineering-managers-b71ced3585d3">Lessons from SoulCycle for Engineering Managers</a></p><p><strong>Key Lesson:</strong> as an engineering manager, you can significantly benefit from adopting a leadership style that prioritizes clear vision, community, and quality. SoulCycle’s success story demonstrates the power of creating a supportive, inclusive community and offering high-quality experiences, which can be translated into engineering management by fostering a team culture that values collaboration, continuous improvement, and user-focused outcomes. By focusing on building a self-sufficient team, emphasizing quality in work processes, leveraging technology to streamline tasks, and nurturing a strong team identity, you can lead your team to achieve greater innovation and success.</p><h3>Your Tech</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3Mfb7Wh34Dy4FloI" /></figure><h4><a href="https://medium.com/bitgrit-data-science-publication/a-roadmap-to-learn-ai-in-2024-cc30c6aa6e16">Roadmap to Learn AI in 2024</a></h4><p><a href="https://medium.com/bitgrit-data-science-publication/a-roadmap-to-learn-ai-in-2024-cc30c6aa6e16">Roadmap to Learn AI in 2024</a></p><p><strong>Key Lesson:</strong> You want to learn about AI? But you don’t know how or where to get started? This guide emphasizes hands-on, project-oriented learning, where practical experience takes precedence over theoretical exploration. Begin by coding AI algorithms from scratch, executing research papers, and engaging in side projects that utilize AI to tackle genuine problems. the result is a top-down learning method to learn AI.</p><h4><a href="https://medium.com/@techworldwithmilan/how-does-single-sign-on-sso-work-31ffa1afcc63">How does Single Sign-On (SSO) work?</a></h4><p><a href="https://medium.com/@techworldwithmilan/how-does-single-sign-on-sso-work-31ffa1afcc63">How does Single Sign-On (SSO) work?</a></p><p>Key Lesson: Ever wondered how signing in with your Google Account to other services works? You’ll gain insights into choosing the right SSO protocol that aligns with your organization’s needs and technology stack, ensuring a seamless and secure user experience. Understanding the intricacies of SSO implementation will empower you to make informed decisions that can significantly impact your team’s operational efficiency and data protection strategies.</p><h3>Your Processes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4CSML8ee486IHZj_" /></figure><h4><a href="https://medium.com/@leonst/the-power-of-engineering-management-handoff-documents-2bcaa64cfedc">The Power of Engineering Management Handoff Documents</a></h4><p><a href="https://medium.com/@leonst/the-power-of-engineering-management-handoff-documents-2bcaa64cfedc">The Power of Engineering Management Handoff Documents</a></p><p><strong>Key Lesson:</strong> As an engineering manager, you should develop and maintain a Standing Handoff Document. This document is crucial for ensuring continuity and efficiency, especially during transitions or absences. It serves as a comprehensive guide that details your team’s current projects, priorities, individual member profiles, processes, and meetings, enabling anyone stepping into a leadership role to quickly understand and effectively manage the team. Regularly updating this document ensures it remains an accurate reflection of the team’s state, facilitating better decision-making, smoother collaboration, and continuous alignment with strategic goals.</p><h4><a href="https://medium.com/one-to-n/manager-of-managers-health-checks-ba95626bca48">Manager of managers — health checks</a></h4><p><a href="https://medium.com/one-to-n/manager-of-managers-health-checks-ba95626bca48">Manager of managers — health checks</a></p><p><strong>Key Lesson: </strong>As an engineering manager, you can enhance your team’s efficiency and effectiveness by implementing a health check framework. By systematically collecting and analyzing data from various sources, including performance metrics and stakeholder feedback, you can make informed decisions, identify and address issues proactively, and drive continuous improvement within your team. Investing just 30–45 minutes each month for these assessments can provide you with critical insights into team dynamics and productivity, enabling you to manage proactively, cultivate a culture of accountability and growth, and ensure alignment with broader organizational goals.</p><p>Dont’t want to to miss an edition of <em>This month in Engineering Management</em>? Get them sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c2f17579071" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build your Team’s Communication Foundation]]></title>
            <link>https://medium.com/@leonst/build-your-teams-communication-foundation-e8665e50383d?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8665e50383d</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Sun, 31 Mar 2024 14:07:01 GMT</pubDate>
            <atom:updated>2024-04-07T01:03:50.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lClVe4veFUo7yCWqxYhZSg.jpeg" /></figure><h4>Key Communication Tools to Implement For Your Team</h4><p>Communication is essential in the tech industry, yet it’s often a skill that developers learn on the job.</p><p>This oversight can lead to significant issues, as seen in the Deepwater Horizon oil rig disaster, where misunderstandings and miscommunications contributed to one of the worst environmental disasters in history. This example starkly illustrates how critical clear communication can be and the devastating impact when it fails.</p><p>If your team operates across various time zones, you’ve likely faced challenges firsthand. Time differences can lead to delays in responses, misunderstandings, and a breakdown in the workflow if not managed properly.</p><p>To address these issues, you can implement two key tools: The communication charter and the team README.</p><ul><li><strong>The communication charter</strong> acts as a guide, helping your team navigate the complexities of working across various time zones and ensuring that everyone is clear about expectations regarding availability and response times. It sets the foundation for how your team interacts, outlining the best practices for asynchronous communication and collaboration.</li><li><strong>The team README</strong>, on the other hand, provides a personal touch to your remote interactions. It contains detailed information about each team member, including their backgrounds, interests, and communication preferences. This tool helps in humanizing the digital workspace and fosters a sense of connection and understanding among team members who may never meet face-to-face.</li></ul><p>Together, these tools form the cornerstone of your team’s communication strategy, ensuring that despite the physical distances, everybody remains connected, informed, and aligned. They are not just tools but the very foundation of your team’s structure, enabling you to build a strong, cohesive, and effective (remote) working environment.</p><p>To better understand this approach, let’s explore the communication charter and team README in more detail and their roles in improving your team’s communication across various time zones.</p><h3>The Communication Charter</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jp_KiD5cUrJ1W_sLDqe-Eg.jpeg" /></figure><p>Think of the communication charter not just as a set of rules, but as a roadmap guiding you and your team through the complexities of asynchronous communication.</p><p>In the global work environment of today, where your team may be scattered across various time zones, mastering effective asynchronous communication is essential. The charter helps ensure that all team members, no matter where they are, know how and when to exchange information, provide updates, and seek support.</p><p>This shared understanding is crucial for keeping work processes seamless and enabling effective collaboration, even when team members are not working simultaneously.</p><h3>Communication Charter content</h3><h4>Core Hours</h4><p>Core hours in your communication charter are the specific times during the workday when you expect all team members to be available for meetings and collaborative efforts.</p><p>This arrangement is essential for ensuring that your team, regardless of different time zones, has a reliable period each day for scheduling meetings, discussions, and other real-time activities. It reduces scheduling conflicts commonly faced by teams spread across various locations, facilitating smoother planning and execution of group tasks.</p><p>By setting core hours, you also honor the individual work-life balance, allowing team members to organize their workday predictably.</p><h4>Availability</h4><p>It’s crucial for you to ensure that your team communicates their availability effectively, particularly in a remote setting. By using tools like Google Calendar, you can have your team members mark their working hours and lunch breaks, making it easy for everyone to see when they are available for meetings and collaborative tasks.</p><p>Encourage your team to update their status on platforms like Slack for short-term absences, providing instant visibility into who is immediately available. For longer periods of unavailability, such as out-of-office times or personal time off, having your team notify through designated channels and updating shared calendars is essential.</p><p>This practice allows you to manage the team’s workload efficiently and prevent any scheduling conflicts.</p><h4>Focus time</h4><p>It’s important for you to encourage your team to block out time for focused work, especially for tasks that require deep concentration.</p><p>By scheduling these focus periods on shared tools like Google Calendar, and integrating these with communication platforms like Slack, you can help ensure that your team’s focus time is visible and respected by others. This practice not only minimizes interruptions but also enhances productivity and allows for more efficient completion of complex tasks.</p><p>It’s a key part of creating a work environment that respects and facilitates the need for uninterrupted time, ultimately leading to better outcomes for your team and projects.</p><h4>Scheduling meetings</h4><p>When planning social events or recurring meetings, organizers should aim to find times that accommodate all participants.</p><p>If finding a universally suitable time proves challenging, alternate between times that favor different regions to demonstrate fairness and consideration for everyone’s schedules. This approach ensures that no single group consistently faces the inconvenience of early morning or late-night meetings.</p><p>By prioritizing equitable scheduling, you foster a more cohesive and respectful team culture, which is crucial for maintaining high morale and effective collaboration across different geographies.</p><h4>Communication within the team</h4><p>Designate specific channels for different types of interactions, such as a channel for general updates where the team can also receive notifications from other teams, and a separate one for daily standups.</p><p>Project-specific channels ensure focused discussions related to particular initiatives, while social channels allow for more casual, non-work-related conversations that help build team camaraderie. Additionally, having a dedicated channel for alerts, especially for on-call purposes, ensures that critical notifications are noticed and addressed promptly.</p><p>This organization of communication streams not only keeps information flow manageable and relevant but also supports the efficiency and effectiveness of your team’s collaboration.</p><h4>Standups</h4><p>Incorporating both synchronous and asynchronous standups caters to the diverse schedules and time zones of your team.</p><ul><li><strong>The synchronous standup</strong> via a video call, allows for real-time interaction and immediate feedback.</li><li><strong>The asynchronous standup</strong>, conducted through a platform like Slack, gives team members the flexibility to contribute at a time that suits them best.</li></ul><p>Balancing these formats ensures that all team members, regardless of their location, can stay informed and engaged with the team’s progress and challenges.</p><h4>Meetings</h4><p>Foster a flexible approach to scheduling individual and group meetings, ensuring they are productive and respectful of everyone’s time.</p><p>When impromptu calls extend beyond their planned duration, be proactive in scheduling a follow-up to continue the discussion without overrunning the current meeting time. It’s essential to include an agenda with meeting invites to set clear expectations and provide any necessary pre-read materials, enhancing the meeting’s efficiency.</p><p>Additionally, documenting these meetings and storing them in a shared drive, along with sending concise summaries to relevant channels, ensures that all team members, including those who couldn’t attend, stay informed. This practice not only aids in keeping everyone on the same page but also facilitates seamless handovers and continuity in long discussions, contributing to the team’s overall productivity and coherence.</p><h4>Projects</h4><p>You play a crucial role in ensuring that each project your team undertakes is well-documented and easily accessible.</p><p>Establishing a centralized location for project information, like a wiki page, allows team members and stakeholders to quickly find and reference project details, status, and updates. Regularly updated meeting notes and documentation alongside the project’s page keep everyone aligned on progress and decisions.</p><p>For projects involving external stakeholders, maintaining consistent communication through scheduled updates is essential. This approach not only keeps stakeholders informed but also builds trust and transparency, ensuring that all parties involved have a clear understanding of the project’s direction and any potential impacts on their interests.</p><h4>Investigations</h4><p>It’s vital to establish a systematic approach for handling investigations of issues or incidents within your team.</p><p>Using a tool like JIRA to track and document these investigations ensures that all relevant information is captured and accessible in one place, serving as the ‘source of truth.’ When an issue arises, promptly creating a JIRA ticket helps in organizing the details and discussions related to that issue.</p><p>Summarizing these discussions, especially those from lengthy conversations in communication platforms like Slack, and linking them to the JIRA ticket, allows for a comprehensive view of the issue, its context, and the team’s responses. This methodical approach not only streamlines the problem-solving process but also improves transparency and accountability within your team.</p><h4>Code Reviews</h4><p>Ensuring that your team adheres to a structured code review process is critical for maintaining code quality and facilitating knowledge sharing.</p><p>Encourage your developers to provide comprehensive details in their pull requests, including the rationale behind changes, testing methods used, and any additional context that might help reviewers understand the submission. This detailed approach minimizes the need for back-and-forth questions and helps in identifying potential issues more effectively.</p><p>As for the reviewers, prompt and thorough feedback not only accelerates the review process but also contributes to the continuous improvement of the codebase. When direct completion of a review isn’t possible, facilitating the search for an alternate reviewer ensures the process remains uninterrupted.</p><p>Moreover, suggesting future optimizations can help streamline the review process and expedite deployment.</p><h3>Implementing the Communication Charter</h3><p>Your role in implementing the communication charter is critical to its success and the overall efficiency of your team. To effectively integrate the charter into your team’s daily operations, follow these practical steps:</p><ul><li><strong>Familiarize Your Team with the Charter</strong>: Start by ensuring that every team member understands the charter’s contents and its importance. Organize a session to walk through the charter, highlighting key components like core hours, communication channels, and meeting protocols.</li><li><strong>Integrate into Meeting Scheduling</strong>: Apply the charter’s guidelines when scheduling meetings. Ensure that meetings are set within core hours to accommodate different time zones, and use the preferred tools and platforms as outlined in the charter for setting up these meetings. This will help in minimizing conflicts and maximizing participation.</li><li><strong>Standardize Project Documentation</strong>: Implement the charter’s recommendations for project documentation. Encourage the use of shared platforms for documenting project progress, decisions, and changes. This could involve setting up project pages, using consistent templates, and ensuring that all documentation is accessible to relevant team members.</li><li><strong>Embed Charter Practices in Daily Workflows:</strong> Make the charter’s guidelines a part of your team’s standard operating procedures. This includes regular checks on communication channels, adherence to availability schedules, and use of project management tools. Reinforce the use of these practices in daily standups or weekly meetings.</li><li><strong>Monitor and Adjust: </strong>Continuously monitor how well the charter is being integrated into team operations. Be open to feedback from your team and be prepared to make adjustments to the charter itself or how it’s implemented to better suit your team’s needs.</li><li><strong>Reinforce through Leadership</strong>: Lead by example by consistently following the charter’s guidelines yourself. Your adherence to the charter demonstrates its importance and encourages your team to follow suit.</li></ul><p>By taking these steps, you not only ensure that the communication charter becomes an integral part of your team’s operations but also foster a culture of clear, effective communication that can significantly improve your team’s collaboration and productivity.</p><h3>Team README</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TGiCicOi8NqvVRSwDV1HPQ.jpeg" /></figure><p>As an engineering manager, implementing a team README has substantial benefits for enhancing team dynamics and communication efficiency. A well-crafted team README not only serves as a resource for logistical and operational information but also plays a crucial role in building a more empathetic and cohesive team environment.</p><p>The benefits you and your team get out of a team README:</p><ul><li><strong>Enhancing Empathy and Understanding</strong>: The team README provides a platform for team members to share personal insights, such as their backgrounds, work preferences, and interests. This information fosters empathy and understanding among team members, as they gain a more comprehensive view of their colleagues as individuals, not just as coworkers. By appreciating the diverse experiences and perspectives within the team, you can facilitate more nuanced and considerate interactions, leading to a more inclusive and supportive work culture.</li><li><strong>Tailored Communication Strategies</strong>: The README allows team members to express their preferred communication styles and needs. Understanding these preferences enables you to tailor communication strategies that align with individual working styles, enhancing the effectiveness of team interactions. For example, if a team member prefers detailed written communication over impromptu phone calls, knowing this preference can lead to more productive and respectful exchanges. This tailored approach not only respects individual work habits but also optimizes the overall communication flow within the team.</li></ul><p>By fostering an environment where team members feel understood and valued, the team README becomes an invaluable tool in building a positive and effective team culture. It encourages open communication, reduces misunderstandings, and enables more effective collaboration. As an engineering manager, leveraging the team README to its full potential can significantly contribute to the well-being and productivity of your team.</p><h3>Team README Structure</h3><ul><li><strong>Introductory Map:</strong> Start with a visual map showing where team members are located. This not only highlights the geographical diversity of your team but also aids in understanding the time zone logistics that affect meeting planning and daily communication. Recognizing where everyone is based fosters a sense of global team unity and helps in scheduling considerations.</li><li><strong>Background Information Slide</strong>: Compile slides that encapsulate each member’s personal history, professional journey, and photographs. This segment helps team members to appreciate the varied paths that have led each individual to their current role, enhancing mutual respect and understanding of each other’s expertise and experiences. It serves as a foundation for recognizing the diverse skill sets within the team, facilitating better collaboration.</li><li><strong>Personal Interests Slide</strong>: Sharing personal interests and family life can significantly boost team rapport. This section allows team members to discover common hobbies and life experiences, fostering personal connections. These connections can lead to stronger team bonds and a more supportive work environment.</li><li><strong>Communication Preferences Slide</strong>: Detailing how each member prefers to communicate is essential for streamlining interactions. Whether someone prefers emails for detailed discussions or quick syncs over calls, understanding these preferences allows for more effective and considerate communication. It guides team members in choosing the appropriate medium and approach for interacting with one another, minimizing misunderstandings and enhancing overall communication efficiency.</li></ul><h3>Implementing the Team README</h3><p>Implementing the team README is a dynamic process that actively involves each team member, ensuring that the document remains a living, evolving representation of the team. Here’s how you can effectively put this into practice:</p><ul><li><strong>Initial Creation by New Members</strong>: Upon joining the team, each new member should be tasked with creating their own slides for the team README. This process allows new team members to introduce themselves in a structured yet personal manner, sharing their professional background, personal interests, and communication preferences. Additionally, they should place themselves on the introductory map, providing a clear visual of their geographical location relative to the rest of the team.</li><li><strong>Continuous Updates and Reintroductions</strong>: As the team evolves, with new members joining and others possibly changing roles or locations, it’s important for all team members to regularly update their slides. This ensures that the information remains current and relevant, reflecting any significant changes in professional focus, personal interests, or communication styles.</li><li><strong>Presentation of Slides</strong>: Whenever a new member joins, not only will the newcomer present their slides, but existing team members should also take the opportunity to present their updated slides again. This practice serves multiple purposes: it allows longstanding team members to reintroduce themselves and share any updates, and it gives new members a comprehensive understanding of their colleagues.</li></ul><p>By implementing the team README in this manner, you not only facilitate a thorough onboarding process for new team members but also reinforce the team’s culture regularly. This approach ensures that every team member, regardless of when they joined, has a deep understanding of their colleagues, which in turn, enhances collaboration and team harmony.</p><p>Want to become a better Engineering Manager?<br>Get more Engineering Management articles sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8665e50383d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons from SoulCycle for Engineering Managers]]></title>
            <link>https://medium.com/@leonst/lessons-from-soulcycle-for-engineering-managers-b71ced3585d3?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/b71ced3585d3</guid>
            <category><![CDATA[tech-lead]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Sun, 24 Mar 2024 12:58:13 GMT</pubDate>
            <atom:updated>2024-03-24T12:58:13.956Z</atom:updated>
            <content:encoded><![CDATA[<p>I look at everything I hear or read from the perspective of Engineering Management. The closest comparison that comes to mind is a music producer or DJ that can’t listen to music in a relaxed way anymore because they try to identify the melody or a specific synthesizer that was used.</p><p>The same happened when I listened to one of my favorite podcasts: <a href="https://open.spotify.com/show/5Ob5psTjoUtIGYxKUp2QVy?si=d146cae8c1ba470a">The Prof G Pod with Scott Galloway</a>. In one of the recent episodes Scott <a href="https://open.spotify.com/episode/7jRRaeDj0EfewFOKZeR9Vm?si=888ead89a71b45f7">interviewed the founders of SoulCycle</a>. It was very interesting to listen to their founding story, their Leadership approach and what made SoulCycle what it is today.</p><p>Their unique approaches to get SoulCycle off the ground can also be applied to your skill as an engineering manager.</p><p>I’ll give you a short rundown of the story behind SoulCycle and we pedal through four areas that every engineering manager can benefit from. Let’s start from the beginning:</p><h3>The Story behind SoulCycle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GSnRcMdbSaoOO56l" /></figure><p>SoulCycle’s story began with Elizabeth Cutler and Julie Rice, who wanted to change how people saw fitness in New York City. They didn’t like the usual gym scene, where everyone just focused on working out alone and burning calories.</p><p>They imagined a place where exercise was more about being together and feeling good, both physically and mentally.</p><p>They started SoulCycle as a fresh idea at a time when trendy fitness brands and social media like Instagram were just starting. SoulCycle was different because it made working out feel like being part of a friendly community.</p><p>It wasn’t just about getting fit; it was also about feeling better and being around supportive people.</p><p>Cutler and Rice turned the usual gym business upside down. They made sure fitness instructors were well taken care of and could give everyone a great experience. They found their first studio space through Craigslist, and even though it was hard to find and had no signs, it quickly became popular.</p><p>The welcoming and friendly atmosphere they created became a big part of what made SoulCycle special.</p><p>Using technology also helped a lot. It made signing up for classes easy and helped people fit exercise into their busy lives. This matched their idea that staying active should be an easy and important part of everyone’s day.</p><p>Over ten years, SoulCycle grew from just one studio to a well-known brand. This shows how important it is to have a clear goal, care about your community, and be open to new ideas. The success of SoulCycle proves that when you really care about bringing people together and giving them a great experience, you can make a big difference in an industry.</p><p>The founding story and concept of SoulCycle provide valuable lessons for you as an engineering manager. Let’s pedal through four crucial areas where SoulCycle’s journey can improve your leadership skills.</p><h3>Leadership and Vision</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zXVmlEz-uzT18HTv" /></figure><p>As a software engineering manager, you can draw inspiration from SoulCycle’s founders, who demonstrated the impact of effective leadership coupled with a clear vision. Their ability to articulate and embody the core values and goals of SoulCycle was key to its widespread success and influence.</p><p>Your role as a leader involves more than just managing tasks and timelines; it’s about inspiring your team and guiding them toward a shared vision. Here’s how you can apply this in your management practice:</p><ul><li><strong>Craft and Communicate a Clear Vision</strong>: Develop a clear and compelling vision for what your team aims to achieve. Develop that vision together with your product manager. This vision should not only align with the company’s objectives but also resonate on a personal level with each team member. It’s about storytelling and regular communication of that vision.</li><li><strong>Lead with Purpose</strong>: Show your team the ‘why’ behind their work. When team members understand the purpose of their efforts, they are more likely to be engaged and committed to achieving the vision.</li><li><strong>Be a Role Model</strong>: Demonstrate the values and standards you expect from your team. Leadership is as much about setting an example as it is about providing direction.</li><li><strong>Foster a Culture of Excellence:</strong> Encourage a mindset of continuous improvement and high performance. Challenge your team to set ambitious goals and provide them with the support and resources they need to achieve them.</li><li><strong>Empower and Trust Your Team</strong>: Give your team the autonomy to make decisions and take ownership of their work. Trust is a powerful motivator and builds confidence within the team.</li><li><strong>Set Up Open Lines of Communication</strong>: Ensure that you are approachable and available for your team. Open communication helps in addressing issues promptly, aligning efforts, and reinforcing the team’s vision and goals.</li></ul><p>I wrote a dedicated article outlining 9 ways to increase autonomy in your software engineering team:</p><p><a href="https://medium.com/@leonst/unleashing-potential-the-engineering-managers-guide-to-autonomy-b88a7959fa60">The Engineering Manager’s Guide to Autonomy</a></p><p>By embodying these principles, you not only lead your team more effectively but also provide a sense of purpose and direction, motivating them to achieve excellence and contribute meaningfully to the organization’s success.</p><h3>Quality over Quantity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ctjTrd0O-rrXMFm7" /></figure><p>As a software engineering manager, you can learn from SoulCycle’s approach of prioritizing quality to ensure lasting success and customer satisfaction. SoulCycle chose to focus on delivering a premium, high-quality experience rather than expanding its services hastily.</p><p>This commitment to quality helped establish its reputation as a leading fitness brand.</p><p>In the context of software engineering, this principle translates to valuing high-quality code and robust testing over the rapid release of new features or products. Here’s how you can apply this to your management practices:</p><ul><li><strong>Emphasize Code Quality</strong>: Encourage your team to write clean, maintainable, and efficient code. This not only reduces the likelihood of bugs and issues in the long run but also facilitates easier updates and maintenance.</li><li><strong>Implement Thorough Testing Procedures</strong>: Ensure that comprehensive testing is an integral part of your development process. This includes unit testing, integration testing, and user acceptance testing to catch and fix problems before they reach production.</li><li><strong>Adopt Sustainable Development Practices</strong>: Promote practices that ensure the long-term health of your software and team. This includes regular code reviews, technical debt management, and ensuring a manageable pace of work to prevent burnout.</li><li><strong>Prioritize User Experience</strong>: Like SoulCycle’s focus on customer experience, prioritize the end-user experience in your software. This means listening to user feedback and making iterative improvements to enhance usability and satisfaction. It’s key to work together with Product and Design.</li><li><strong>Make Informed Release Decisions</strong>: Rather than pushing for rapid releases, make strategic decisions about when to launch new features or products based on their readiness and quality. This might mean delaying a release to ensure it meets your quality standards.</li></ul><p>By prioritizing quality over quantity, you not only uphold the integrity and reliability of your software but also build trust with your users and establish a reputation for excellence in your field.</p><p>A side effect is also that high code quality results in engineering velocity that doesn’t degrade over time.</p><h3>Leveraging Technology</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-cJzut4ywYAcsyj6" /></figure><p>As an engineering manager, you can take a cue from SoulCycle’s strategic use of technology to simplify class booking, which significantly contributed to their success. They harnessed technology to remove barriers, making it easy for customers to integrate fitness into their lifestyle.</p><p>In the same vein, you can leverage technology to enhance your team’s efficiency and workflow.</p><p>Here’s how you can apply this principle with practical examples:</p><ul><li><strong>Automate Routine Tasks</strong>: Just as SoulCycle automated the class booking process, identify tasks within your team’s workflow that can be automated. This could include setting up continuous integration and deployment pipelines, automating code reviews, or using Slack bots to handle repetitive administrative tasks.</li><li><strong>Enhance Collaboration Tools</strong>: Utilize collaboration platforms that streamline communication and project management. Tools like Slack, Jira, or Asana can help keep your team aligned and facilitate smoother project tracking, much like how SoulCycle’s booking system streamlined customer interactions.</li><li><strong>Use Data to Drive Decisions</strong>: Implement analytics tools to gather data on project progress, team performance, and product usage. This data can guide decision-making, similar to how SoulCycle used customer feedback and booking trends to optimize their offerings.</li><li><strong>Improve Remote Work Efficiency</strong>: With the rise of remote work, use technology to create a seamless virtual office environment. This can include cloud-based development environments, virtual meeting spaces, and online collaboration tools, ensuring that your team can work effectively from anywhere.</li></ul><p>By leveraging technology to streamline and improve processes, you not only make your team’s life easier but also enhance the overall productivity and satisfaction, leading to better outcomes and a more successful team.</p><h3>Brand and Culture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JJp075BhZy3K5nn4" /></figure><p>As a software engineering manager, you play a crucial role in shaping the brand and culture of your team, much like how SoulCycle’s success was deeply intertwined with its distinct brand identity and culture. A strong brand isn’t just for outward marketing; it also reflects the internal values and ethos that drive your team’s operations and interactions.</p><p>Creating a positive and distinct culture within your software engineering team can significantly impact engagement, loyalty, and productivity.</p><p>To do this effectively, you need to ensure that the culture you foster aligns with the broader goals and values of your organization. Here’s how you can approach this:</p><ul><li><strong>Define and Communicate Your Team Vision</strong>: Clearly articulate the vision and values of your team. What do you stand for? What makes your team unique? Communicate these principles consistently and ensure they are reflected in your team’s daily work and interactions.</li><li><strong>Lead by Example</strong>: Your actions and behaviors set the tone for the team’s culture. Demonstrate the values you want to instill through your own work ethic, treatment of others, and decision-making processes.</li><li><strong>Encourage Ownership and Responsibility</strong>: Empower team members to take ownership of their projects and responsibilities. This fosters a sense of pride and investment in their work, which is essential for building a strong team culture.</li><li><strong>Foster Inclusivity and Collaboration</strong>: Promote an environment where all team members feel valued and included. Encourage collaboration and open communication to ensure diverse perspectives are heard and considered, enhancing creativity and innovation.</li><li><strong>Recognize and Reward</strong>: Acknowledge and celebrate achievements, both big and small. Recognition not only boosts morale but also reinforces the behaviors and outcomes that align with your team’s culture and goals.</li><li><strong>Continuously Evaluate and Adapt</strong>: Culture is not static; it evolves with your team and organization. Regularly assess the health and alignment of your team’s culture with your stated values and goals, and be prepared to make adjustments as needed.</li></ul><p>By actively building and nurturing a culture that resonates with your team’s identity and organizational values, you create a more cohesive, motivated, and productive environment, much like the vibrant and engaging atmosphere that has driven SoulCycle’s success.</p><h3>Conclusion</h3><p>The journey of SoulCycle offers a treasure trove of insights for engineering managers looking to lead with impact and innovation. From the story of its inception in the streets of New York City to its rise as a fitness phenomenon, SoulCycle’s ethos of community, quality, and forward-thinking can deeply resonate with the principles of effective engineering management.</p><p>By embracing the lessons of clear vision and leadership, prioritizing quality over quantity, leveraging technology for operational efficiency, and cultivating a strong brand and culture, you can steer your team toward remarkable achievements. Just as SoulCycle transcended the conventional gym experience to create a thriving fitness community, you too can transform your engineering team into a powerhouse of creativity, productivity, and success.</p><p>Ride the wave of these lessons, and you may find your team reaching new heights of excellence and innovation, much like the mark left by SoulCycle in the fitness industry.</p><p>Want to become a better Engineering Manager? <br>Get more Engineering Management articles sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b71ced3585d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of Engineering Management Handoff Documents]]></title>
            <link>https://medium.com/@leonst/the-power-of-engineering-management-handoff-documents-2bcaa64cfedc?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bcaa64cfedc</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Mon, 18 Mar 2024 11:02:15 GMT</pubDate>
            <atom:updated>2024-03-18T11:02:15.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ZF5cwB2xZbxk8u0rsJcIw.jpeg" /></figure><h4>Not just a tool for managing absence or transitions</h4><p>Recently, I experienced one of my life’s most significant experiences: The birth of my son. When going on parental leave I needed to come up with a strategy and process how to make sure my software engineering team will be taken care of well.</p><p>In general my team is very self sustainable but in case something comes up, whoever steps in needs something they can work with to navigate the team. This led to me creating my first Engineering Management Handoff document.</p><p>The creation of this document and seeing it in action transformed my perspective. Not only did it ensure the continuity of work in my absence, but it also highlighted the value of having such a document as a permanent feature, not just a one-off solution. It became clear that this standing document was not just a lifeline for me but a tool to enhance clarity, collaboration, and efficiency within the team.</p><p>In this article, I’ll share why every Engineering Manager should develop and maintain a Standing Handoff Document, drawing from my first hand experience.</p><h3>Understanding Team Handoff Documents</h3><p>A Standing Handoff Document is a versatile tool that helps you keep track of your team’s activities at all times. It’s not just any file or report; it’s a dynamic document that provides a comprehensive view of your team’s work, including current projects, team interactions, and key processes.</p><p>This document is continuously updated to reflect the changes in your team’s work, ensuring it accurately represents the team’s current state.</p><p>The purpose of this document is multi-layered. It primarily serves as an in-depth guide for you, the manager, allowing you to stay connected with your team’s operations and needs. It becomes especially crucial during times of change, such as when you go on leave or when a new leader steps in. With this detailed and updated record, the new leader can assume their role confidently and lead the team effectively.</p><p>But this document isn’t just for you or your immediate successor. It’s a valuable resource for anyone working with your team. It provides insights into the team’s processes and facilitates smoother collaboration and decision-making.</p><p>Regular updates to the document ensure that it remains relevant and trustworthy, offering a detailed and accurate picture of your team’s activities.</p><p>In summary, the Standing Handoff Document is an invaluable asset for you and your team. It captures the ongoing narrative of your team’s journey, ensuring continuity, fostering transparency, and enhancing the overall effectiveness of your team’s management and operations.</p><p>Let’s explore the crucial elements that make up this essential tool in the next section.</p><h3>Crucial Elements of a Standing Handoff Document</h3><h4>The 5 Most Important Things</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWkYfe5ttkgHK86P5yKk4A.jpeg" /></figure><p>In the Standing Handoff Document, I start with the “5 Most Important Things” section that is crucial for highlighting the team’s top priorities.</p><p>These priorities, which can vary over time, are selected based on their immediate impact on the team’s success and strategic goals.</p><p>Here’s a list that typically constitutes the most critical areas of focus:</p><ul><li><strong>Critical Projects</strong>: These are the projects that are vital for the team’s success and often have a significant impact on the organization’s goals. Creating awareness for these projects ensures that the team is focused on work that delivers the most value.</li><li><strong>Urgent Deadlines</strong>: Timelines that are approaching fast and require immediate attention fall into this category. Meeting these deadlines is crucial for maintaining the momentum and success of the team’s projects.</li><li><strong>People Development</strong>: Prioritizing the growth and development of team members is essential. This could include project opportunities, mentoring, or other initiatives that help team members enhance their skills and contributions to the team.</li><li><strong>Resource Needs</strong>: Identifying and securing the necessary resources, whether it be additional engineers, budget increases, or technology tools, is critical for the team to effectively carry out its projects and initiatives.</li><li><strong>Potential Risks</strong>: Recognizing and planning for potential risks that could impact the team’s ability to meet its objectives is essential. Proactively managing these risks helps in safeguarding the team’s progress and success.</li></ul><p>By focusing on these five crucial areas, you can align the team’s efforts on the most impactful activities and ensure that it is well-prepared to tackle challenges and seize opportunities even when you’re gone.</p><h3>Team Overview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ct1tB92pmkXQY8EOEHEa6g.jpeg" /></figure><p>The next crucial part of your Standing Handoff Document is the Team Overview. This section gives you a detailed picture of your team members, including their roles, skills, and what they’re currently working on. It serves as a directory, helping you understand the resources you have in your team and how each person contributes to the team’s goals.</p><p>Elaborate on each team member with the following detailed information:</p><ul><li><strong>Job Title</strong>: Clearly state each person’s official position or role within the team, which helps in understanding their responsibilities and authority level.</li><li><strong>Skills Summary</strong>: Enumerate the specific skills and areas of expertise that the team member brings to the table. This might include technical competencies, leadership qualities, and experience in particular areas, which are crucial for task allocation and project planning.</li><li><strong>Current Tasks/Projects</strong>: Detail the specific assignments or projects each team member is currently engaged in. Include the scope of their responsibilities and their role in these projects to give a clear picture of their day-to-day work and how it contributes to the team’s objectives.</li><li><strong>Support Requirements</strong>: Describe any specific support or accommodations they need to work effectively, such as special equipment, software, or assistance in certain tasks.</li><li><strong>Career Development Status</strong>: Offer a concise overview of their current position in their career path, including recent achievements, ongoing training or education, and short-term and long-term career goals. Link to a more detailed career development plan if available, ensuring this is kept in a secure document for privacy reasons</li></ul><p>Additionaly add each team members<strong> working Style and Needs</strong>:</p><ul><li><strong>Preferred Communication Methods</strong>: Note whether they prefer emails, calls, in-person meetings, or instant messaging for daily communication.</li><li><strong>Feedback Preferences</strong>: Mention how they like to receive feedback (e.g., written, verbal, one-on-one, in group settings) to foster effective and constructive interactions.</li><li><strong>Work Hours</strong>: Indicate their typical working hours, highlighting any non-standard schedules for remote or part-time members, to facilitate better coordination and meeting planning.</li></ul><p>In essence, the Team Overview isn’t just a roster of names and jobs; it’s a comprehensive guide that shows you and any engineering manager how to effectively interact with and support your team members.</p><h3>Current Projects</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JvBTKijRIy-cbaTZHa-Agg.jpeg" /></figure><p>The “Current Projects” section is a key part of your Standing Handoff Document. It gives you a close look at what your team is working on right now. In this section, you’ll find detailed information about each project’s goals, how it’s doing, and important things that affect the progress.</p><p>Include the following details for each project:</p><ul><li><strong>Project Goals</strong>: Define the main objectives and what the project aims to achieve, showing its importance and alignment with organizational goals.</li><li><strong>Project Link</strong>: Provide a link to the project page for additional details, such as technical scoping, detailed planning documents, product-related documents, and designs.</li><li><strong>Current Status</strong>: What has been completed so far, milestones reached, remaining tasks and goals.</li><li><strong>Key Stakeholders</strong>: List the people and groups involved, both within and outside your team, highlighting their roles in the project.</li></ul><p>In summary, the “Current Projects” section is like a complete guide to what your team is working on.</p><p>It gives everyone involved the information they need to understand, keep track of, and help in successfully finishing each project. This ensures that your team’s work is coordinated and focused on achieving the right results.</p><h3>Processes and Meetings</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JYud8zdJWlZASVQvOmjtPQ.jpeg" /></figure><p>In the Standing Handoff Document, the “Processes and Meetings” section is crucial. It outlines the team’s standard ways of working and the schedule of their regular meetings. Here’s how to detail it:</p><ul><li><strong>Processes</strong>: This part should describe the routine procedures your team follows to carry out their work and complete projects. It includes the steps for starting new tasks, ensuring the quality of work, and wrapping up projects. <br>By documenting these procedures, you make it clear for yourself and anyone who might step in to manage the team, showing them how things are done and what’s expected at each project phase.</li><li><strong>Meetings</strong>: This subsection should list the consistent meetings your team holds, such as daily briefings, weekly status updates, or monthly planning sessions. <br>Explain the purpose of these meetings, how often they occur, and who typically attends. For each type of meeting, include what is usually discussed, the main objectives, and any preparation or follow-up tasks required.</li></ul><p>By describing the processes and meetings in the document, you provide a clear picture of how the team operates daily and how they communicate and make decisions.</p><p>This information is valuable, especially for new managers or when transitioning leadership, as it helps maintain the team’s workflow and communication without interruption, ensuring a smooth continuation of operations.</p><h3>Product-Based Metrics and Dashboards</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFrbnhmY5lncd7Qc2TJBNA.jpeg" /></figure><p>In your Standing Handoff Document, the section on Product-Based Metrics and Dashboards is crucial if you’re in a product-focused team. It tracks key performance indicators (KPIs) like revenue, signups, user engagement, and retention rates. These metrics are essential for evaluating the product’s success and your team’s impact on the company’s goals. Work together with your product manager to create this section.</p><p>You should clearly define each metric, explaining what it measures and its importance. For example, include revenue metrics such as total sales and average revenue per user, and analyze signups to gain insights into customer acquisition.</p><p>Your document should feature dashboards that provide real-time or regular updates, with instructions on how to access and interpret them. These dashboards are key for identifying trends, spotting opportunities for growth, and addressing potential issues.</p><p>Make sure these metrics align with your team’s and the company’s objectives, showcasing your team’s contribution to the product’s success and the company’s financial health. Also, document the process for tracking and analyzing these metrics, including data collection methods, review frequency, and who is responsible for monitoring.</p><p>This section is vital for ensuring strategic alignment, helping you understand how your work contributes to the company’s broader goals. It supports informed decision-making with data-driven insights and allows for effective performance tracking, enabling your team to adapt to market changes and enhance product success and customer satisfaction.</p><h3>Conclusion</h3><p>The Standing Handoff Document is not just a tool for managing absence or transitions; it’s a strategic asset for any engineering manager. It encapsulates the essence of your team’s journey, providing a roadmap for sustained success and growth. I encourage every engineering manager to embrace this practice, not only to facilitate smoother transitions but to enhance the overall management and operation of their teams.</p><p>Want to become a better Engineering Manager? Get more Engineering Management articles sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bcaa64cfedc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spring cleaning as an Engineering Manager]]></title>
            <link>https://medium.com/@leonst/spring-cleaning-as-an-engineering-manager-9ca9fa27b6c0?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ca9fa27b6c0</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Mon, 11 Mar 2024 11:01:39 GMT</pubDate>
            <atom:updated>2024-03-24T14:02:50.684Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vy5uIkUOzT9BvxTqEt5J1A.jpeg" /></figure><h3>Spring Cleaning as an Engineering Manager</h3><p>When I was a kid, spring in our apartment meant deep cleaning. I can still remember the smell of our home getting cleaned from top to bottom. We would open all the windows to let in fresh air and get rid of the old, musty winter air. We cleaned every inch and spot and got rid of stuff we didn’t need. It was all about starting fresh.</p><p>Now, as an Engineering Manager, I bring that same idea of starting fresh into my work every spring. It reminds me to look over how my team does things and find ways to do them better.</p><p>It’s the perfect time to throw out old ways that aren’t working and make our work more straightforward and focused. Let me share how I take that feeling of spring cleaning from my childhood and use it to improve our team’s work and processes, making everything more clear and efficient.</p><h3>Streamline Processes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qXXu_e-b5bLbnDP-OQHkzw.jpeg" /></figure><p>Initiating spring cleaning with streamlining your processes can lead to significant improvements in efficiency and productivity. Here’s how you can approach this:</p><h4>Evaluate Current Workflows</h4><p>Begin by mapping out existing workflows for different processes such as project management, bug tracking, backlog management, release management and incident response. Identify each step and its purpose.</p><p>This clear map helps you see where there are unnecessary repetitions, delays, or confusing parts. Identify any steps that are no longer necessary or that duplicate other efforts. Discuss with your team why these steps were initially included and whether they currently add value.</p><p>If your team uses Agile methods but finds that standups are too frequent and lack a clear purpose, think about cutting down the number of stand-up meetings from every day to three times a week. In these meetings, concentrate solely on major issues and top priorities.</p><p>If you find that your team’s response to incidents is slow or disorganized due to unclear roles or steps, you can improve this by establishing a clear incident management protocol.</p><p>One part of that protocol is a clear communication channel dedicated to incident management, like a specific Slack channel or Microsoft Teams group, where all incident-related communication takes place. This ensures that all information is centralized and accessible, reducing confusion and overlap in responses.</p><p>Additionally, implement a standard incident post mortem to be completed after every incident, ensuring that each response is documented and lessons learned are captured for continuous improvement.</p><h4>Implement Automation</h4><p>Survey your team’s daily routines to identify tasks that are repetitive and take up a lot of time but are essential, such as running tests, entering data, or creating reports. Explore which tools and software can automate these processes to save time and reduce the likelihood of mistakes.</p><p>For teams that need to generate regular reports, automate the process using business intelligence tools like Tableau, Google Looker or comparable tools. By setting up dashboards or scheduled reports, you can reduce the need for manual compilation and allow team members to access updated data in real-time as well as saving your team time creating manual reports.</p><p>Analyze your current Continuous Integration Pipelines for inefficiencies or bottlenecks that could be streamlined. For instance, you might find that your build times are longer than necessary due to outdated dependencies or unnecessary build steps. Optimizing these can significantly reduce wait times and improve productivity.</p><h4>Simplify Communication Channels</h4><p>Excessive meetings and emails can drain time and energy. Streamline communication by setting clear guidelines for when to use emails, instant messaging, documents and meetings.</p><p>For example, use instant messaging for questions, documents for detailed discussions that need documentation, emails for updates for broader groups and meetings for collaborative decision-making.</p><p>Here are two ways you can improve meetings:</p><ul><li><strong>Define Meeting Objectives</strong>: Ensure that every meeting has a clear agenda and objectives outlined in the invite. If there’s no clear purpose, consider whether the meeting is necessary.</li><li><strong>Action Item Follow-ups</strong>: Conclude meetings with clear action items and owners, summarizing them in a follow-up message or email.</li></ul><p>Encourage the use of concise, clear language and establish protocols for different types of communication. Implement regular check-ins to gather feedback on communication practices and identify areas for improvement.</p><p>By systematically addressing each of these areas you can significantly improve team efficiency and productivity. Remember, the goal is not to overhaul everything overnight but to make thoughtful, incremental changes that streamline processes and remove unnecessary burdens from the team.</p><h3>Reassess Priorities</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Ra-5BL5WHapc2Vz_kgabg.jpeg" /></figure><p>The arrival of spring is an ideal time for you to take a step back and reassess the priorities of your team. Get a fresh perspective that can be leveraged to realign and reevaluate the tasks and projects on your team’s plate. Here are practical examples of how you can prioritize tasks effectively:</p><h4>Align Tasks with Organizational Goals</h4><p>Spring is a great time to ensure that your team’s tasks are aligned with the overarching goals of the organization. Conduct a review of current projects and tasks and evaluate how they contribute to the organization’s objectives.</p><p>For instance, if your organization aims to enhance customer satisfaction, prioritize tasks related to improving the user experience or reducing bugs and errors in your products. Always keep an close eye on the metrics your organization focuses on and the metrics your team’s projects are improving.</p><p>Work together with your product manager to make sure your team and the organization are moving into the same direction.</p><h4>Implement the Eisenhower Box</h4><p>The Eisenhower Box, also known as the Urgent-Important Matrix, is a powerful tool for prioritizing tasks.</p><p>It helps distinguish between what needs immediate attention (urgent) and what contributes to long-term goals (important). Here’s how you can apply it:</p><ul><li><strong>Urgent and Important (Do first):</strong> These are tasks that need immediate attention and also contribute to long-term objectives. For example, addressing critical bugs in a software release or responding to customer issues that impact many users. Prioritize these tasks to be done as soon as possible.</li><li><strong>Important, but Not Urgent (Schedule):</strong> These tasks are important for long-term success but do not need immediate action. This can include refactoring code for better maintainability, documenting processes, or planning future projects. Schedule these tasks after the urgent ones but ensure they are completed to avoid future crises.</li><li><strong>Urgent, but Not Important (Delegate):</strong> These are tasks that require immediate attention but do not necessarily contribute significantly to long-term goals. An example could be addressing non-urgent bug reports that don’t affect the current sprint’s goals or handling minor code refactoring that isn’t critical to project completion. These tasks should be delegated to appropriate team members who have the capacity, or consider automating routine checks and updates.</li><li><strong>Neither Urgent Nor Important (Eliminate):</strong> These tasks do not contribute to your goals and do not need immediate attention. Identify activities like unnecessary meetings, redundant reporting, or excessive email checking, and eliminate them from your schedule.</li></ul><p>By reassessing your priorities you can ensure that your team is not just busy, but productive, focusing on tasks that truly advance the team’s and organization’s objectives. Prioritizing tasks and projects effectively leads to better resource allocation, clearer focus and ultimately more successful outcomes.</p><h3>Declutter Digital Workspaces</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4vnA7drKqTUURw8UDeLZQ.jpeg" /></figure><p>Digital workspaces, much like physical ones, can become cluttered with unused files, outdated information, and old projects. Leading to decreased productivity and increased frustration. Here’s how you can lead the charge in decluttering digital workspaces:</p><h4>Review and Organize Files</h4><p>Start by reviewing the files and documents stored on shared drives and repositories. Archive old projects, delete redundant files, and organize active documents into clearly labeled folders. Encourage team members to clean their personal digital workspaces as well.</p><p>For shared design assets and product specifications, work with product managers and designers to categorize and store them in accessible, clearly labeled folders. Use a system that makes sense to all parties involved, such as organizing by project name, date, or version number. This not only aids in finding documents quicker but also in maintaining consistency across different versions and iterations of a project.</p><p>Develop and agree on a set of naming conventions for files and folders that everyone, including product managers and designers, adheres to. This could involve including the project name, date, version number, and type of content (e.g., mockup, specification, user research, technical specifications) in the file name. A clear and consistent naming convention reduces confusion and saves time when searching for specific documents.</p><h4>Clean Up Communication Channels</h4><p>Take the time to go through your team’s communication channels, including email, Slack, Microsoft Teams, or any other platforms used. Start by archiving old channels that are no longer active or relevant. Encourage your team to leave channels and groups that they’re no longer using or that are no longer relevant to their current work. This can drastically cut down on unnecessary information and help everyone find important messages and files more easily.</p><p>When organizing your communication channels, make sure each channel has a clear description that outlines its purpose. This helps team members understand where to go for specific types of discussions and information. Additionally, pin important resources to the top of each channel, such as links to relevant wiki pages, key documents, or project briefs. This ensures that essential information is easily accessible and not buried under newer messages.</p><p>As part of your project management process, make it a standard practice to archive project-specific channels once the project is completed. This not only helps in decluttering the digital workspace but also marks a clear end to the project, allowing team members to shift their focus to new tasks without the old ones hanging around in their digital space. Future communication regarding the feature that a finished project added should happen in the team channel as part of the on-point process.</p><h4>Revitalize Your Team’s Issue Tracking Systems</h4><p>Start by identifying issues that lack sufficient descriptions or have only brief summaries. These tickets can create confusion and slow down workflow, as team members spend extra time seeking clarification.</p><p>The issue’s creator needs to update it with clear, concise, and informative descriptions to ensure everyone understands the tasks at hand without needing to ask for additional details.</p><p>Next, address very old issues still lingering in the system. Let the creator of an issue determine whether these are still relevant; if they are, reassess their priority and update their status and details as necessary. For those that are no longer applicable, close them out to clear the clutter. This helps keep the team focused on current and pressing tasks, rather than being bogged down by outdated ones.</p><p>This process can easily be delegated to someone in your team and doesn’t need to be done by yourself.</p><p>By decluttering digital workspaces, you help create a more organized, efficient, and less stressful environment for your team.</p><p>A clean digital space can lead to improved focus, faster information retrieval, and ultimately, a more productive and happy team. Use the spring season as a catalyst to promote good digital hygiene practices within your engineering team.</p><h3>Embrace Continuous Improvement and Routine Maintenance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LsAwJaHudL32Td8YO_8jzA.jpeg" /></figure><p>Remember that spring cleaning isn’t just a one-time event; it’s about setting the foundation for ongoing improvements. Encourage your team to make decluttering, prioritizing, and organizing part of their daily habits. This regular upkeep helps avoid clutter and keeps everything running smoothly.</p><p>Institutionalize the best practices you’ve developed, from meeting guidelines to incident response protocols. This helps standardize processes and eases the integration of new team members.</p><p>Regularly review and tweak these practices to address new challenges and avoid slipping back into old habits. Celebrate successes and maintain an open environment for feedback and innovation to keep everyone invested in improving workflows.</p><p>Also, try to make maintenance tasks enjoyable and rewarding, enhancing team morale and motivation. By embedding these habits into your everyday routines, your team will continue to operate efficiently, not just after a spring clean but all year round.</p><p>Did you like this article? Want to become a better Engineering Manager? Get more Engineering Management articles sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ca9fa27b6c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s Success for Engineering Managers?]]></title>
            <link>https://medium.com/@leonst/whats-success-for-engineering-managers-dad81ea00cc7?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/dad81ea00cc7</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Sun, 03 Mar 2024 15:06:01 GMT</pubDate>
            <atom:updated>2024-03-03T15:06:01.599Z</atom:updated>
            <content:encoded><![CDATA[<h4>What real success looks like for Engineering Managers</h4><p>As you step into the role of an engineering manager, defining success can often feel like navigating uncharted waters. Many new to this position find themselves asking a critical question: <em>What does success look like for an engineering manager?</em></p><p>It’s a common scenario I’ve seen among my mentees — they often start without a clear idea of what achieving success as an Engineering Manager really means.</p><p>Drawing from my own experiences and countless conversations with fellow Engineering Managers, insights from books and articles and working together with mentees, I’ve come to a definition that might also resonate with you:</p><blockquote>True success for an Engineering Manager lies in the ability to create a team that operates independently: A self-sufficient team.</blockquote><p>Let me guide you how to define success for you and your team and how to build a self-sufficient team as an Engineering Manager.</p><h3>The Evolution of Leadership in Engineering</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H1f8E71MaXWhNl1YoQPMjA.jpeg" /></figure><p>In the past, engineering leadership often followed a top-down approach, where decisions were made at the top and directives were passed down for execution. This model, while effective in certain contexts, left little room for team members to think for themselves or to share their own ideas.</p><p>However, as projects have become more complex and technology has rapidly advanced, the limitations of this approach started to show.</p><p>Enter the era of empowering leadership: A paradigm that values and nurtures the autonomy of team members, encourages their continuous growth and mastery of skills and aligns their work with a meaningful purpose.</p><p>This shift acknowledges that the challenges faced by engineering teams today require a diverse set of skills: Creative problem-solving, and a deep sense of ownership over one’s work. As an Engineering Manager, embracing this shift means moving away from being the sole source of answers and direction.</p><p>Instead you’ll become a facilitator who empowers the team to find solutions and drive innovation.</p><h3>Defining Success for an Engineering Manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-UUkd89VmMfLdMMzLg09yg.jpeg" /></figure><p>Defining what success means in your role is a common dilemma. Is it about completing projects on time? Is it about driving innovation? Or is it something more? I’ve come to realize that success goes beyond these traditional metrics.</p><p>Success for an Engineering Manager is not solely measured by the tangible outcomes of projects or the frequency of technological improvements. Instead, it’s deeply rooted in the ability to cultivate a team that thrives on autonomy and resilience.</p><p>This means building a team capable of operating independently, without the constant need for direction or oversight. It’s about creating an environment where team members are empowered to make decisions, solve problems on their own, and own the results of their work.</p><p>But how do you measure such a nuanced aspect of success?</p><p>It’s about looking beyond the black and white of project deadlines and product launches to the gray areas where growth, development, and team dynamics play crucial roles.</p><p>A successful Engineering Manager creates an environment where mistakes are learning opportunities and every team member feels valued and motivated to give their best. The shared aim goes beyond just finishing tasks to gradually improving and growing.</p><p>This approach to defining success may require a shift in mindset. It means valuing the process as much as the outcome, recognizing the importance of each team member’s journey towards mastery and autonomy. True leadership is about enabling others to find their path to success.</p><p>In essence, defining success as an Engineering Manager involves setting a vision for what a self-sufficient, resilient team looks like and then working tirelessly to turn that vision into reality. It’s about measuring your effectiveness not just in terms of what your team can achieve today but in their potential for growth, innovation, and independence tomorrow.</p><p>Let’s explore how to build such a team, focusing on the critical elements of autonomy, mastery, and purpose, and redefine success in engineering leadership together.</p><h3>How to build a Self-Sufficient Team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3nYPWzARaJQYirO5Iqtn8A.jpeg" /></figure><p>Building a self-sufficient team involves fostering an environment where team members are empowered to take initiative, learn and grow, and align their efforts towards a shared vision.</p><p>Let’s break down how to cultivate these critical elements: Autonomy, Mastery, and Purpose.</p><h4>Autonomy</h4><p>Granting your team the autonomy to make decisions and solve problems independently is a cornerstone of a self-sufficient team. This doesn’t mean leaving them to fend for themselves but creating a supportive backdrop where they feel confident to take the lead.</p><p>Begin by delegating tasks with clear outcomes yet flexible processes, allowing team members to approach problems in ways that best suit their skills and creativity.</p><p>Building trust is essential in this process. Trust comes from a place of understanding that you, as a manager, believe in their capabilities. Regular check-ins, providing constructive feedback, and celebrating successes are ways to reinforce this trust.</p><p>It’s about balancing guidance with freedom, so your team knows you’re there to support them but also trusts them to make the right calls.</p><h4>Mastery</h4><p>A self-sufficient team is continuously learning and improving. Encourage mastery by identifying opportunities for each team member to enhance their skills and knowledge. This could be through formal training, workshops, or hands-on projects that challenge them just beyond their current capabilities.</p><p>Providing resources and opportunities for professional growth shows your team that you’re invested in their long-term development, not just the immediate needs of the project or the company.</p><p>It’s about recognizing the potential in each team member and giving them the tools and time to reach that potential. This commitment to their growth can significantly boost motivation, engagement and ultimately the team’s overall capability.</p><h4>Purpose</h4><p>Aligning the team’s efforts with organizational goals and values gives their work meaning and direction. A shared vision motivates and guides the team, helping them understand how their individual contributions fit into the bigger picture.</p><p>To foster this sense of purpose, regularly communicate the team’s goals, how they align with the company’s objectives, and the impact of their work on the organization and its customers.</p><p>Creating a narrative around the team’s work that connects to a larger mission or cause can inspire and unify the team. It’s about making the connection between day-to-day tasks and the broader impact, ensuring each team member feels they are part of something meaningful.</p><p>Building a self-sufficient team is a dynamic and ongoing process. It involves empowering your team with the autonomy to make decisions, fostering an environment of continuous learning for mastery, and uniting the team around a shared purpose.</p><p>As an Engineering Manager, your role is to guide, support, and inspire your team to achieve their best, not by directing their every move but by creating a culture where they can thrive independently. This is the essence of true success in engineering management.</p><h3>Your Role as Engineering Manager in a Self-Sufficient Team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Y1FtSREShl9jGh8PhiVzA.jpeg" /></figure><p>As an Engineering Manager, your role within a self-sufficient team changes significantly. No longer the sole source of answers and direction, your job shifts towards being a mentor and coach.</p><p>You become a facilitator who enables the team to navigate challenges and seize opportunities on their own. This transformation requires a balance of providing support without micromanaging and empowering your team while ensuring they have the guidance they need to succeed.</p><p>Here’s how you can fulfill this role effectively:</p><h4>Becoming a Mentor and Coach</h4><p>Your primary function shifts from directing tasks to developing people. This means taking the time to understand each team member’s strengths, weaknesses, and professional aspirations.</p><p>Regular one-on-one meetings become a space for feedback and growth discussions, rather than status updates. Your aim is to help each individual unlock their potential, guiding them through challenges and celebrating their achievements.</p><p>It’s about asking the right questions rather than providing all the answers, encouraging reflection, and self-discovery within your team.</p><h4>Facilitating Growth</h4><p>A key part of your role is to create opportunities for your team to grow. This involves identifying challenging projects that push team members out of their comfort zones in a supportive environment.</p><p>Encourage cross-functional collaboration to broaden their perspectives and skills. Recognize and leverage their unique talents by assigning tasks that align with their interests and career goals. This will foster a sense of ownership and engagement in their work.</p><h4>Providing Strategic Direction</h4><p>While day-to-day decisions might be in the hands of your team, you play a crucial role in setting the strategic direction. This involves clearly communicating the vision, goals, and priorities of the projects, team and organization.</p><p>Help your team understand the ‘why’ behind their work and how it contributes to the broader objectives. This clarity helps them make informed decisions and align their efforts with the overall mission, ensuring that autonomy doesn’t lead to misalignment or confusion.</p><h4>Creating a Feedback Culture</h4><p>Constructive feedback is the backbone of continuous improvement.</p><p>Cultivate an environment where feedback flows freely and positively, not just from you to your team members but among the team members themselves. Encourage a mindset where feedback is seen as a gift, an opportunity to grow rather than a critique.</p><p>Regular retrospectives where the team can reflect on what went well and what could be improved are invaluable for fostering a culture of openness and continuous learning.</p><h4>Identifying Key Performance Indicators (KPIs)</h4><p>Start by setting clear, measurable goals that reflect the team’s autonomy and overall effectiveness.</p><p>These KPIs should go beyond traditional metrics like project deadlines and include aspects of team dynamics to track the team’s progress and efficiency. By tracking these indicators, you can gauge how well your team functions independently, highlighting areas where they excel and identifying opportunities for further growth:</p><ul><li><strong>Velocity</strong><br>Velocity tracks the volume of work completed in a specific timeframe, reflecting the team’s productivity and efficiency. Consistent velocity indicates a stable and predictable development process, aiding in planning and resource allocation.</li><li><strong>PR (Pull Request) Size</strong><br>Monitoring PR size helps understand the team’s code integration habits. Smaller PRs are generally better, as they are easier to review, test, and merge, leading to more efficient teamwork and higher code quality.</li><li><strong>Deployment Frequency</strong><br>This KPI measures the rate at which new features or updates are released. Higher deployment frequency indicates an agile and responsive development cycle, allowing for quicker feedback and improvements.</li><li><strong>Change Failure Rate (CFR)</strong><br>CFR assesses the percentage of deployments that fail and require remediation. Reducing CFR is key to improving code quality and deployment practices, ensuring smoother and more reliable product releases.</li><li><strong>Mean Time to Recovery (MTTR)</strong><br>MTTR measures how quickly the team can resolve system failures or issues. A lower MTTR signifies a more efficient problem-solving capability, crucial for maintaining system reliability and minimizing downtime.</li></ul><p>Create a dashboard and share it with the team so everybody knows when one of the KPIs is dropping.</p><p>This is not only defining performance metrics for the team but also promotes accountability without your direct presence. Your team might have specific metrics that also make sense to track, especially if they are crucial for your team’s mission.</p><h4>Celebrating Milestones and Achievements</h4><p>Recognizing and celebrating achievements is vital, especially for a team working autonomously.</p><p>Acknowledging milestones, breakthroughs, and even small wins reinforces positive behaviors and motivates your team to strive for excellence. Make it a point to celebrate these moments, whether through team meetings, shout-outs in company channels, or individual recognition.</p><p>This not only boosts morale but also solidifies the team’s sense of purpose and achievement. Ask your team members how they would like to be recognized, some people prefer to be celebrated in a private setting.</p><h4>Encouraging Ownership at Every Level</h4><p>Ownership starts with a sense of personal responsibility for the outcome of one’s work. Encourage your team members to take charge of their projects, from planning stages through to execution and review. This involves giving them the freedom to set their own goals, make decisions, and take calculated risks.</p><p>When team members feel like they truly ‘own’ their part of the project, they are more motivated, engaged, and likely to go the extra mile to ensure success.</p><h4>Encourage Peer Support and Collaboration</h4><p>Promote an environment where team members feel comfortable seeking support and advice from their peers. This not only reduces their reliance on you for answers but also strengthens team cohesion and fosters a collaborative spirit.</p><p>Encourage your team to share knowledge, skills, and experiences. Peer support networks can be incredibly effective in solving problems and generating new ideas. This will further enhance the team’s ability to operate independently.</p><h3>Transitioning to Less Hands-On Management</h3><p>Transitioning to a less hands-on management approach does not mean stepping back entirely. Rather, it’s about shifting focus from direct control to strategic guidance, from solving problems for your team to empowering them to solve problems themselves.</p><p>By setting clear expectations, providing the necessary resources, and establishing a culture of ownership and accountability, you pave the way for your team to achieve remarkable things.</p><p>Success as an Engineering Manager is about creating a strong, capable team that thrives under your guidance and continues to excel, even in your absence. It’s about setting a standard for excellence, inspiring your team to reach new heights, and ultimately, contributing to the broader objectives of your organization.</p><p>What’s your definition of success as a Engineering Manager? Share it in the comments.</p><p>Did you like this article? Want to become a better Engineering Manager? Get more Engineering Management articles sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dad81ea00cc7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This Month in Engineering Management February 2024]]></title>
            <link>https://medium.com/@leonst/this-month-in-engineering-management-february-2024-917b47535f6c?source=rss-5fba49083d85------2</link>
            <guid isPermaLink="false">https://medium.com/p/917b47535f6c</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <dc:creator><![CDATA[Leonard Stellbrink]]></dc:creator>
            <pubDate>Thu, 29 Feb 2024 23:40:28 GMT</pubDate>
            <atom:updated>2024-02-29T23:59:58.787Z</atom:updated>
            <content:encoded><![CDATA[<h4>Everything that happened in Engineering Management in February 2024</h4><p>Welcome to the February 2024 and second edition of <em>This Month in Engineering Management</em>! I recevied some feedback and try to already include it in this month’s edition. If you have feedback, don’t hesitate to <a href="http://www.linkedin.com/in/leonards">contact me</a> or add a comment.</p><p>Already 1/6 of the year is over! Your yearly plan is hopefully running full steam ahead and the fog of the early year phase has lifted. Full productivy ahead!</p><p>Let’s check out what happened this month in Engineering Management:</p><h3>Your Team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*adGNiB3B8IOlSAyV" /></figure><h4><a href="https://medium.com/@leonst/an-uncomfortable-way-to-improve-your-one-on-ones-as-an-engineering-manager-aec11a820f79">An Uncomfortable Way to Improve Your One-on-Ones as an Engineering Manager</a></h4><p><a href="https://medium.com/@leonst/an-uncomfortable-way-to-improve-your-one-on-ones-as-an-engineering-manager-aec11a820f79">An Uncomfortable Way to Improve your One-on-Ones as an Engineering Manager</a></p><p>The article explains how you, as an engineering manager, can transform your one-on-one meetings by introducing moments of silence. You might find that embracing silence leads to deeper insights, allowing your team members, especially the more introverted ones, to open up and share innovative ideas.</p><p>By incorporating silent pauses, you create an environment that fosters thoughtful reflection and encourages all team members to contribute more meaningfully. <a href="https://medium.com/@leonst/an-uncomfortable-way-to-improve-your-one-on-ones-as-an-engineering-manager-aec11a820f79"><strong>Read more</strong></a>…</p><h4><a href="https://medium.com/@i-ads/software-mentoring-five-important-lessons-to-remember-efcd34736616">Software Mentoring: Five Important Lessons To Remember</a></h4><p><a href="https://i-ads.medium.com/software-mentoring-five-important-lessons-to-remember-efcd34736616">Software Mentoring: Five Important Lessons To Remember</a></p><p>In this article, you will discover five critical lessons to improve your mentoring approach as an Engineering Manager, drawing from the author’s experience. You’ll learn the importance of setting clear expectations early, steering without over-controlling the mentoring process, respecting individual learning styles, initiating crucial conversations, and tracking progress effectively.</p><p>These strategies will help you provide more effective support and create a conducive environment for your mentees’ growth, enhancing your skills as a mentor and leader in the software development field. <a href="https://medium.com/@i-ads/software-mentoring-five-important-lessons-to-remember-efcd34736616"><strong>Read more</strong></a>…</p><h3>Your Career</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bekxKEZIgOmqt3SW" /></figure><h4><a href="https://medium.com/@leonst/5-lessons-from-guy-kawasakis-think-remarkable-for-engineering-managers-df7af227873d">5 Lessons from Guy Kawasaki’s “Think Remarkable” for Engineering Managers</a></h4><p><a href="https://medium.com/@leonst/5-lessons-from-guy-kawasakis-think-remarkable-for-engineering-managers-df7af227873d">5 Lessons from Guy Kawasaki’s “Think Remarkable” for Engineering Managers</a></p><p>Guy Kawasaki’s new book “Think Remarkable” is out and contains valuable lessons for your career and personal life. The article explores 5 lessons that can redefine your approach to leadership, innovation, and personal growth. Whether you’re looking to master the art of the pitch, inspire your team to greater heights, or balance execution with visionary thinking, there’s something here for you.</p><p>One key lesson from the article regarding Managing Up:</p><blockquote>Make your manager look good<br>Make yourself indispensable<br>Bring solutions, not problems and questions</blockquote><p><a href="https://medium.com/@leonst/5-lessons-from-guy-kawasakis-think-remarkable-for-engineering-managers-df7af227873d"><strong>Read more</strong></a>…</p><h4><a href="https://medium.com/@leonst/maximizing-book-learnings-as-an-engineering-manager-78903a54290a">Maximizing Book Learnings as an Engineering Manager</a></h4><p><a href="https://medium.com/@leonst/maximizing-book-learnings-as-an-engineering-manager-78903a54290a">Maximizing Book Learnings as an Engineering Manager</a></p><p>Advancing in engineering management requires to read books and articles. Learn how you can make the most of the books and articles you read!</p><p>It provides a 7 step guide how you can soak up all the knowledge and bring it into your day-to-day role as an engineering manager. I Highly recommended to read this article first before you start any book from the <a href="https://medium.com/@leonst/best-engineering-management-books-2024-377ad23e4af5">Best Engineering Management Books 2024</a> list! <a href="https://medium.com/@leonst/maximizing-book-learnings-as-an-engineering-manager-78903a54290a"><strong>Read more</strong></a>…</p><h3>Your Tech</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3Mfb7Wh34Dy4FloI" /></figure><h4><a href="https://medium.com/@mikecvet/platform-monopolies-and-the-decay-of-leverage-affeea13d92a">Platform Monopolies and the Decay of Leverage</a></h4><p><a href="https://mikecvet.medium.com/platform-monopolies-and-the-decay-of-leverage-affeea13d92a">Platform Monopolies and the Decay of Leverage</a></p><p>As an engineering manager, understanding the dynamics of internal software platforms can significantly impact your team’s productivity and satisfaction. This article will guide you through recognizing the signs of a platform becoming a monopoly within your organization and the potential decay in value versus cost over time.</p><p>It provides actionable insights on how to maintain a platform that not only meets the specific needs of your developers but also fosters continuous innovation and alignment with industry trends, ensuring your team wants to use the platform rather than feeling obligated to do so. <a href="https://mikecvet.medium.com/platform-monopolies-and-the-decay-of-leverage-affeea13d92a"><strong>Read more</strong></a>…</p><h4><a href="https://medium.com/javarevisited/10-reasons-to-learn-system-design-in-2024-fa795d301f62">10 Reasons to Learn System Design in 2024</a></h4><p><a href="https://medium.com/javarevisited/10-reasons-to-learn-system-design-in-2024-fa795d301f62">10 Reasons to Learn System Design in 2024</a></p><p>As an engineering manager looking to enhance your team’s skills and your own, staying up to date with system design can be pivotal. This article provides you with ten practical reasons to grasp system design, from increasing scalability and optimizing problem-solving skills to becoming indispensable in tech interviews.</p><p>By embracing system design, you not only elevate your technical capabilities but also prepare yourself for future leadership roles and ensure your projects are adaptable to emerging technologies. This knowledge will empower you to guide your team more effectively and make informed decisions in the ever-evolving tech landscape. <a href="https://medium.com/javarevisited/10-reasons-to-learn-system-design-in-2024-fa795d301f62"><strong>Read more</strong></a>…</p><h3>Your Processes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4CSML8ee486IHZj_" /></figure><h4><a href="https://medium.com/@leonst/accomplish-any-goal-as-an-engineering-manager-66f89736155c">Accomplish Any Goal as an Engineering Manager</a></h4><p><a href="https://medium.com/@leonst/accomplish-any-goal-as-an-engineering-manager-66f89736155c">Accomplish Any Goal as an Engineering Manager</a></p><p>In last month’s “This month in Engineering Management” I added the <a href="https://medium.com/@leonst/how-to-define-your-goals-for-2024-as-an-engineering-manager-49ff60ee64d1">How to Define your Goals for 2024 as an Engineering Manager</a> article. It is about how to set your yearly goals as an engineering manager. But knowing what your goals are is just the beginning.</p><p>The bigger challenge is figuring out how to actually reach those goals. This article provides a structured process helping you accomplish your goals. <a href="https://medium.com/@leonst/accomplish-any-goal-as-an-engineering-manager-66f89736155c"><strong>Read more</strong></a>…</p><h4><a href="https://medium.com/ux-planet/why-designers-fail-to-integrate-into-agile-teams-0c22b9095db8">Why designers fail to integrate into Agile teams</a></h4><p><a href="https://uxplanet.org/why-designers-fail-to-integrate-into-agile-teams-0c22b9095db8">Why designers fail to integrate into Agile teams</a></p><p>As an engineering manager, you’re probably familiar with the challenges of integrating designers into Agile teams. This article explores why designers often struggle in Agile environments, highlighting the constraints of rigid frameworks like Scrum that limit creative freedom and deep thinking.</p><p>It offers insights into how you, as a leader, can create a more inclusive space for designers by incorporating practices from Design Thinking and Lean UX, thus enhancing collaboration and innovation in your team. Understanding these dynamics can help you foster a more productive and harmonious relationship between designers and developers, ultimately leading to better product outcomes. <a href="https://medium.com/ux-planet/why-designers-fail-to-integrate-into-agile-teams-0c22b9095db8"><strong>Read more</strong></a>…</p><p>Dont’t want to to miss an edition of <em>This month in Engineering Management</em>? Get them sent straight to your inbox, subscribe <a href="https://medium.com/@leonst/subscribe"><strong>here</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=917b47535f6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>