<?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 Andrew Weaver on Medium]]></title>
        <description><![CDATA[Stories by Andrew Weaver on Medium]]></description>
        <link>https://medium.com/@andrewweaver?source=rss-3d7e86baa5ff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dDf8SLZkJLfveuvBtPfEpw.jpeg</url>
            <title>Stories by Andrew Weaver on Medium</title>
            <link>https://medium.com/@andrewweaver?source=rss-3d7e86baa5ff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:14:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrewweaver/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[Leadership Opinion: Are you a Thermostat or a Thermometer?]]></title>
            <link>https://medium.com/@andrewweaver/leadership-opinion-are-you-a-thermostat-or-a-thermometer-27a0257ef33d?source=rss-3d7e86baa5ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/27a0257ef33d</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[tech-leadership]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Andrew Weaver]]></dc:creator>
            <pubDate>Fri, 01 Apr 2022 10:42:56 GMT</pubDate>
            <atom:updated>2022-04-01T10:42:56.686Z</atom:updated>
            <content:encoded><![CDATA[<p>My dad is a retired electrical engineer, and I inherited the “engineer” gene from him.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X6YZvh2f3IPvN6mkveNjpw.jpeg" /></figure><p>He tells the story that when I was a young boy he caught me standing on a chair with a screwdriver in hand, taking apart the thermostat which controlled heating in our home. I was apparently very curious to know how a thermostat (or any device) worked…</p><p>Some years later and as an experienced CTO and now, leadership coach, I’d like to explain the difference between thermostats and thermometers and more importantly for the context of this audience, how it applies to leadership and the teams we lead.</p><p><strong>First, An Explanation …</strong></p><p>A thermometer is a device that measures temperature and provides a means of reporting this temperature in a meaningful way.</p><p>A thermostat is a device that likewise measures temperature but then performs actions so that the temperature is maintained near a desired level.</p><p>A thermometer is primarily <strong>acted upon</strong> and just reports the temperature, while a thermostat’s primary function is <strong>to act</strong> upon the measured temperature and adjust it to the desired level.</p><p><strong>Now, How It Connects To Leadership</strong></p><p>As humans, we are blessed with the capacity and power of independent action.</p><p>We are agents <strong>to act</strong> and not merely objects to be <strong>acted upon</strong>.</p><p>You can likely identify those on your team who are more like a thermometer, those who are more like thermostats, and those who flip flop between thermometer and thermostat, depending on the circumstance.</p><h4>While there is a clear value in a thermometer, I value a thermostat more.</h4><p>As a CTO, I value members of the team who keep me informed of all significant developments in my domain in a timely fashion, whether it be good news or bad news.</p><p>However, members of the team who go beyond just keeping me informed and who proactively act to solve issues are valued even more.</p><p>While most engineers (and technical team members) inherently like to fix technical issues, they are not always naturally adept at independently resolving issues outside the technical domain or issues they consider to be outside their control.</p><p>As a technical leader, it is your responsibility to help your team members become thermostats instead of thermometers.</p><p>You have likely achieved your role as a leader in part due to being more thermostat than a thermometer.</p><p>If you are a new CTO or technical leader, you may still be adjusting to your new role and understanding what authority your role has.</p><p>As a result, you may sometimes fall back into thermometer mode, diligently keeping the CEO or your manager informed of significant issues, but not feeling comfortable with taking independent action without prior approval from the CEO or your manager.</p><p>In order to more effectively help your team become thermostats, it is helpful to understand the circumstances that cause you to behave more like a thermometer than a thermostat as they are often the same as those of your direct reports.</p><p>As a leader, you need to know what goes on in your domain and be informed by your direct reports of all significant developments.</p><p>Likewise, your own manager needs to know what goes on in his or her domain and be informed of all significant developments.</p><p>But, if you primarily just inform (report temperature) without taking independent action to resolve issues (change the temperature), you are more like a thermometer than a thermostat.</p><p>You have likely heard of the old rule of <em>“don’t bring up a problem unless you have a solution.”</em> — which is essentially stating that you should be a thermostat, not a thermometer.</p><p>Note that a thermostat that significantly delays taking action after knowing the temperature is not at the desired level, is not a very good thermostat.</p><p>It’s important to timely report all significant problems to your manager even if you don’t know the cause or have a solution to the problem, but you should have a plan of action already in progress.</p><p>I prefer to restate that old rule as<em> “don’t bring up a problem unless you have a proposed solution or a plan of action.”</em></p><p>In my experience, a common reason for team members and leaders to be thermometers is the perception that an issue is outside of their control, not part of their responsibilities, or above their pay grade.</p><p>While this may be somewhat true, it is rarely 100% true.</p><p>I recently read an article that referenced the concept of <a href="https://www.liberatingstructures.com/7-15-solutions/"><strong>15% Solutions</strong></a>. It promotes a focus on what each person has the freedom and resources to do now, rather than what they cannot change.</p><p>15% Solutions shows that<em> “there is no reason to wait around, feel powerless, or fearful.”</em> Regardless of the situation, we have the ability to be agents <strong>to act</strong> and not just be an object to be <strong>acted upon</strong>, even if our own actions amount to just 15% of a solution.</p><p><strong>In Summary …</strong></p><p>We each have the capacity and power of independent action.</p><p>We each have the capacity to be thermostats that primarily <strong>act</strong>, and not merely be thermometers that are <strong>acted upon</strong>.</p><p>As technical leaders, it is our responsibility to create more thermostats in our teams.</p><p>As we build teams with a “thermostat attitude” and lead by example with our own “thermostat attitude,” our individual 15% Solutions become 100% team solutions.</p><p>A team full of thermostat members is much more effective than a team with just a thermostat leader.</p><p><strong>Author</strong></p><p>Article written by <a href="https://www.linkedin.com/in/jim-mortensen/">Jim Mortensen</a>, Fractional CTO/COO, Experienced Leadership Coach including CTO Academy Members based around the world.</p><p><strong>A quick word on CTO Academy</strong></p><p>At CTO Academy, we provide online leadership courses, coaching, and community to global technology leaders.</p><p>Our latest online course <a href="https://cto.academy/are-you-a-thermostat-or-a-thermometer/?utm_source=organic&amp;utm_medium=medium.com&amp;utm_campaign=andrew_medium_article&amp;mtm_campaign=andrew_medium_article&amp;mtm_keyword=thermostat_thermometer">The Digital MBA for Technology Leaders</a> is for senior tech leaders or those aspiring to become one. It will help you to bridge that gap between the technical and the commercial.</p><p>If interested in finding out more, you can book a discovery call with me, the CEO, Andrew Weaver.</p><p>Book that call <a href="https://andrew-ctoa.youcanbook.me/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27a0257ef33d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CEO and CTO: United By A Different Language]]></title>
            <link>https://medium.com/@andrewweaver/ceo-and-cto-united-by-a-different-language-765df29c042b?source=rss-3d7e86baa5ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/765df29c042b</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Andrew Weaver]]></dc:creator>
            <pubDate>Wed, 30 Mar 2022 08:29:56 GMT</pubDate>
            <atom:updated>2022-03-30T08:29:56.087Z</atom:updated>
            <content:encoded><![CDATA[<p>“England and America are two countries separated by one language”</p><p>This quote is widely attributed to George Bernard Shaw but we’ve given it a CTO Academy twist by describing that crucial relationship between CEO and CTO as ….</p><blockquote>‘Two executives united by a different language’</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3DqahdVyo-A8dsr8PlBxiw.jpeg" /></figure><p>We’ve worked with hundreds of technology leaders from around the world and no matter the geography or sector, the challenges they face are often quite consistent and many revolve around communication.</p><p>And if there is one relationship that can particularly suffer as a result of poor communication, it’s the business-critical relationship between CEO and CTO.</p><p>Typically these issues stem from the different perspectives and demands of the personalities and roles.</p><h4><strong>Without falling into too many stereotypes about these roles …</strong></h4><p>The CEO tends to be spinning numerous plates, ideas, initiatives, negotiating various bumps in the road whilst (hopefully) achieving the momentum required.</p><p>Whilst the CTO is driving the technology strategy but is traditionally more introverted, systematic, and in need of structure and clarity.</p><p>A case of … Star Gazer meets Shoe Gazer?</p><p>But the best leaders adapt, focus on each other&#39;s strengths, and help to fill in any of the gaps.</p><p>They learn to understand the nuances of these different personalities so that the CEO: CTO axis can become a critical success factor around which the rest of the organization can depend and thrive.</p><p><strong>So where is the focus (and potential conflict) for both roles?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*24ZI_NWaqe4vXz652TfJPg.png" /></figure><p>Throw into this mixture of competing agendas that fail to communicate with each other and you see why some CEO: CTO relationships (and the companies they’re leading) suffer from conflict.</p><h4>Effective CEOs and CTOs understand this potential for conflict and how best to manage the strengths and weaknesses of their colleagues.</h4><p>CEOs should have a good understanding of the market and customer needs, but are not always so good at the detail or sometimes, even that comfortable with the technology.</p><p>The CTO needs to bridge that gap between the tech and the business so that they can meet and manage the CEO&#39;s aspirations and expectations. They also have to develop some diplomatic and communication skills, that are not always part of their natural skill set.</p><p>So it’s why CTOs need to develop the emotional intelligence to read people and situations. In doing so they will be better attuned to the working style (and secret sauce) of their CEO.</p><p>Both need to understand how and where those contrasting outlooks might create potential for conflict that impacts the development and progress of the company/product (not to mention the stress of working together) and always look to establish an honest and communicative relationship.</p><p>Whether this is based on a weekly or more irregular meeting, both sides need to build those strong communication channels that are driven by an understanding of the factors impacting their ability to achieve the best results.</p><p>They might not become friends, but they don’t need to become enemies.</p><p>They need to understand the mutual pressures and styles of working.</p><p>They need to appreciate and enjoy the fact they’re two talented people, united by a different language.</p><p><strong>A quick word on CTO Academy</strong></p><p>At CTO Academy, we provide online leadership courses, coaching, and community to global technology leaders.</p><p>Our latest online course <a href="https://cto.academy/the-digital-mba-for-technology-leaders/?utm_source=organic&amp;utm_medium=medium.com&amp;utm_campaign=andrew_medium_article&amp;mtm_campaign=andrew_medium_article&amp;mtm_keyword=ceo_cto">The Digital MBA for Technology Leaders</a> is for senior tech leaders or those aspiring to become one. It will help you to bridge that gap between the technical and the commercial.</p><p>If interested in finding out more, you can book a discovery call with me, the CEO, Andrew Weaver.</p><p>Book that call <a href="https://andrew-ctoa.youcanbook.me/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=765df29c042b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[11 Steps To Make 1–2–1’s More Effective]]></title>
            <link>https://medium.com/@andrewweaver/11-steps-to-make-1-2-1s-more-effective-8b1d51ded5d3?source=rss-3d7e86baa5ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b1d51ded5d3</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[one-on-one]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[tech-leadership]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Andrew Weaver]]></dc:creator>
            <pubDate>Mon, 28 Mar 2022 18:03:10 GMT</pubDate>
            <atom:updated>2022-03-28T18:03:10.445Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>‘We have two ears and one mouth, so that we can listen twice as much as we speak’ — Epictetus</strong></h4><p>One consistent question that emerges during our coaching sessions with tech leaders from around the world is, “How can I be more effective when conducting 1:1s with my team?”</p><p>Elizabeth Grace Saunders, author of <a href="https://hbr.org/product/how-to-invest-your-time-like-money/15043E-KND-ENG">How to Invest Your Time Like Money</a> says …</p><p>“One-on-ones are one of the most important productivity tools you have as a manager. They are where you can ask strategic questions such as, are we focused on the right things? And from a rapport point of view, they are how you show employees that you value them and care about them.”</p><p>Just for the sake of clarity: DR = Direct report</p><h3>Tips From CTO Academy Coaches</h3><p>Starting with the advice provided above by Epictetus, we asked our coaching network for some deeper insight on what makes an effective 1:1 session for tech leaders;</p><h4>1. How To Start Well</h4><p>Like everything else in life, first impressions count - and how you start your 1:1s will help shape how successful they turn out.</p><p>The key to starting any session is to make your DR realize it’s about them, not about you or the company but them.</p><p>Keep it simple and open with something like … “tell me what’s important for you at the moment?” or “tell me your wins, losses, and what you’ve learned from each?”A couple of our coaches mentioned being inspired by Bill Campbell (<a href="https://www.amazon.com/Trillion-Dollar-Coach-Leadership-Playbook/dp/0062839268">Trillion-Dollar Coach</a>) in starting each session very personally. Ask how they are doing and make notes of key personal information that will help prompt you to follow up during one of the following sessions … “<em>one of my DRs mentioned that his son had a passing out ceremony in 2 months so I kept a note and mentioned it as the start of the following session. Without that note I probably would have forgotten to mention it but that I did, had a big impact”</em></p><h4>2. Have Genuine Interest In Other People</h4><p>Conducting truly effective sessions with your DRs needs cognitive agility but it’s fundamentally about people and having a genuine desire to help individuals in your team to articulate and negotiate short-term concerns, as part of a long-term plan.</p><p>It’s about helping them develop and grow for the business, for their role, and most importantly, for themselves.</p><h4>3. Be Consistent and Reliable</h4><p>Fix a routine to avoid the sessions being seen as ad-hoc and squeezed into the few gaps in your diary.</p><p>A fixed schedule helps all parties prepare properly and avoid easy excuses for cancellation.</p><p>And whatever you do, avoid that last-minute cancellation not least because it will give the impression you have more important things to do. Whilst it might be one of the multiple sessions for you this week, it’s potentially the most important one for the person sitting opposite. Never overlook that fact.</p><p>Remember also that building good relationships doesn’t happen overnight, it’s about building trust and small steps leading to large gains.</p><p>In sporting parlance, it’s the aggregation of marginal gains.</p><h4>4. Agendas and Actions Plans</h4><p>By stating clear actions plans at the end of each session, you’re creating an agenda and momentum for the next one. It also helps provide structure and avoids a meandering conversation.</p><p>Liaise in advance about the key points and priorities.</p><p>A rushed and poorly scheduled meeting can lead to important issues being missed and frustration about the effectiveness and point of that meeting.</p><p>And whilst you provide the structure, the reporting tools, the targets (maybe based around OKRs, KPIs, etc.) it’s important to provide them with the autonomy of owning the core agenda.</p><p>If you are worried about them owning the agenda then have another look at your recruitment policy because you need to be building a team of experts who demand autonomy.</p><p>“We hire people to tell us what to do, not the other way round” — Steve Jobs</p><h4>5. Be Present</h4><p>This moment matters to the other person. They might have spent a significant amount of time preparing and potentially worrying about this session.</p><p>So you need to be present throughout.</p><p>Avoid arriving distracted, fiddling with your mobile, finishing other calls or tasks.</p><p>Give that person in front of you 100% of your time and make them the only one in the world that matters to you at that precise moment.</p><p>If something else is genuinely impacting on your focus then be honest and admit it, maybe offer them the opportunity of delay or cancellation.</p><h4>6. Their Place in The Big Picture</h4><p>The level of detail you dive into will be dictated by the relationship and the regularity but it’s important to differentiate these sessions from your standard conversations or the annual appraisal.</p><p>It should be primarily about helping them focus on their growth and development. Try to avoid it being too much about the micro and the day-to-day.</p><p>“<em>One agenda item I have with each DR is to ask ‘what escalation do you have for me and how can I support you to win?” — </em>Sanjay Mistry, CTO Academy Coach</p><p>It’s also useful to encourage them to set up a process wherein advance of the sessions they start detailing the key issues or problems they need to raise, to go through in their own mind any roadblocks so the session can quickly dive deep and be as effective as possible.</p><h4>7. Build a Culture of Transparency</h4><p>An effective 1:1 isn’t just about that private session in isolation, it should be part of a wider culture of open, supportive, and collaborative communication within the company.</p><p>If they arrive at each session with that wider culture and confidence behind them, then you’re onto an early winner.</p><h4>8. Feedback: Get It, Don’t Give it</h4><p>It’s also not really the time or place to be giving them too much feedback, though channels and opportunities need to be created to do so. Feedback is generally best given after a specific event or situation and shouldn’t be stored up until sometime later when details can be lost and it might be turned into a more attritional conversation.</p><p>If feedback is to be exchanged, then it should only be one way and that’s in your direction. Feedback about the role, the tasks, the company, your leadership. This is why it’s important they lead the agenda and that you have a culture of openness and confidence in providing constructive feedback.</p><p>If in any doubt about the impact of radical transparency, I recommend you read <strong>No Rules Rules</strong> about the leadership culture and performance impact at <a href="https://www.amazon.es/No-Rules-Netflix-Culture-Reinvention/dp/0593107381">Netflix</a>.</p><p>Read that book and you’ll never think of feedback in the same way again.</p><h4>9. How Often and How Long?</h4><p>This clearly comes down to your individual demands and requirements so we plugged into some external expertise for guidance around this topic ….</p><p>“<em>I recommend no less than a weekly 1:1 with every report for thirty minutes, and more time if needed. Even if you sit next to someone and see him every day. 1:1s, let you discuss topics that may never come up otherwise</em>” — Julie Zhuo, VP of Product Design at Facebook and author of The Making of a Manager.</p><p>Sticking with the Facebook crowd, Mark Zuckerberg and Sheryl Sandberg have publicly stated they meet twice per week</p><p>“<em>We’ve had this tradition where every week we start the week and end the week just meeting one-on-one together and reflect on everything that’s going on, giving each other feedback</em>” said Zukerberg.</p><p>“<em>We always know that we’re going to talk things through and we’re going to get on the same page. And when we’re not on the same page, we’re going to keep talking it through</em>,” <a href="https://www.youtube.com/watch?v=zNZB4J9o6Hg">said</a> Sandberg. “<em>I do one-on-ones with the people working on my team, Mark does one-on-ones, and it reverses down. I think it’s helped the company a lot</em>.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*kw-qoyWFQjUIia7H.png" /></figure><p>Andy Grove, formerly of Intel and credited with being a key voice in the art of good management argued that the skill of creating and maintaining a business could be summed up in a single word: “managing.” And that’s precisely what frequent one-on-ones with your team empower you to do.</p><p>Gove says that a minimum of one hour is required because “<em>anything less in my experience tends to make the subordinate confine himself to simple things that can be handled quickly. They must feel that there is enough time to broach and get into thorny issues</em>”.</p><p>What is equally important as the duration of each session, is to try and build downtime around the meeting schedule that enables you to prepare and absorb effectively.</p><h4>10. Celebrate Wins, However Small</h4><p>How much have we needed to celebrate every small win in 2020 but it’s a principle you need to take into these 1:1 sessions.</p><p>Make sure you spot and acknowledge their achievements and particularly when set against the longer term objectives you’re both heading towards.</p><p>Use that celebration to help reflect on their journey, potentially for both of you because most effective relationships are about the benefits of mutual learning.</p><h4>11. How To End Well</h4><p>With A Smile.<br>With An Action Plan.</p><p>With A Confirmation Of Next Meeting.</p><h3>Putting Our Words Into Action</h3><p>We Conclude With An Action Plan and 11 Steps Towards Effective 1:1 Sessions</p><ol><li>How to start well</li><li>Have a genuine interest in other people</li><li>Be consistent and reliable</li><li>Prepare agendas and action plans</li><li>Be present</li><li>What’s their place in the big picture</li><li>Build a corporate culture of transparency</li><li>Feedback: Get but don’t give</li><li>How often and how long?</li><li>Celebrate wins, however small</li><li>How to end well</li></ol><p><strong>A quick word on CTO Academy</strong></p><p>At CTO Academy, we provide online leadership courses, coaching, and community to global technology leaders.</p><p>Our latest online course <a href="https://cto.academy/the-digital-mba-for-technology-leaders/?utm_source=organic&amp;utm_medium=medium.com&amp;utm_campaign=andrew_medium_article&amp;mtm_campaign=andrew_medium_article&amp;mtm_keyword=better_one_on_ones">The Digital MBA for Technology Leaders</a> is for senior tech leaders or those aspiring to become one. It will help you to bridge that gap between the technical and the commercial.</p><p>If interested in finding out more, you can book a discovery call with me, the CEO, Andrew Weaver.<br>Book that call <a href="https://andrew-ctoa.youcanbook.me/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b1d51ded5d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 Tips on The Bottleneck of Code Reviews]]></title>
            <link>https://medium.com/@andrewweaver/9-tips-on-the-bottleneck-of-code-reviews-c85debd7cdf3?source=rss-3d7e86baa5ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/c85debd7cdf3</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[tech-leadership]]></category>
            <dc:creator><![CDATA[Andrew Weaver]]></dc:creator>
            <pubDate>Fri, 25 Mar 2022 17:44:08 GMT</pubDate>
            <atom:updated>2022-03-25T20:46:46.437Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*LtCqhw0c1k999uNzRO2pNQ.jpeg" /></figure><p>When fellow CTO Academy member <a href="https://www.linkedin.com/in/andre-duis/?originalSubdomain=de">André </a>asked the CTO Academy community for assistance with the bottleneck of code reviews, it sent the cogs whirring.</p><p>It’s a problem I’m facing with my own teams and have been for some months. So it was almost comforting to hear another tech leader facing the same issues.</p><p>I had experienced efficient code review practices before, so the question led me to articulate what had worked in the past.</p><p><strong>Here are some thoughts … (thanks also to </strong><a href="https://www.linkedin.com/in/nathandanielsen/"><strong>Nathan Danielsen</strong></a><strong> and </strong><a href="https://www.linkedin.com/in/ahmetk/?originalSubdomain=tr"><strong>Ahmet Kara</strong></a><strong> for their input to this article)</strong></p><h4><strong>1. Well Specified Tickets</strong></h4><p>It was a large cooperation, so the team had a project manager and business analysts involved that would make sure each ticket was well-refined with a clear scope.</p><p>This had the benefit of the developer assigned to the ticket knowing exactly what to develop and that anyone collecting the ticket for code review knew the scope of what they needed to look at.</p><p>Not all teams have the luxury of a business analyst and project manager but where possible, try and bring more than just technical input into ticket specification where it might help.</p><h4><strong>2. Keep Work Atomic</strong></h4><p>Keep the scope of tickets and pull requests in check.</p><p>This kept pull requests small. It reduced the side effects of the work being done and made reviewing the code itself much faster.</p><p>Pull requests with &gt;1000 lines of changes are a red flag and no one is going to read through that many lines of code.</p><h4><strong>3. Aim For Complete Code Coverage With Tests</strong></h4><p>Include both unit tests and integration/end-to-end testing.</p><p>Every new piece of work should have associated unit and integration tests as part of the review. This enables a high amount of confidence in the work being reviewed and allows for easy automation.</p><p>Ensure time for this testing has been included in your estimates and sprint planning.</p><h4><strong>4. “Right to Left” Working</strong></h4><p>We had a sprint board with the columns “ready for dev”, “in progress”, “peer review”, and “done”.</p><p>We adopted a process of “Right to Left” working.</p><p>It’s tempting as a developer to create a PR, drag your ticket to the peer review column on the sprint board, and go immediately left to see what’s in ready for dev. Instead, we’d go right.</p><p>When you submitted a piece of work, you first checked the peer review column.</p><p>If there was work there that needed reviewing, you did it BEFORE looking in ready for dev.</p><h4><strong>5. Automated Linting (ND) and Static Analysers</strong></h4><p>Make heavy use of linting / style checking tools, especially in a pre-commit hook.</p><p>Styling feedback on CRs isn’t a good use of time and static analysis tools can provide even deeper insights in to code quality such as amount of duplication, code smells, and the aforementioned code coverage.</p><h4><strong>6. Code Review Guidelines (ND)</strong></h4><p>Set up some code review guidelines on what a good code review is and what isn’t.</p><p>Sometimes a checklist has been helpful in normalizing what requires a look and what doesn’t.</p><p>Using markdown in the pull request, and Github’s (or equivalent) PR templates automate the writing process. Include a “how to test” section, including new dependencies, database migrations, or reproduction steps.</p><p>This stops the reviewer from fumbling around in the dark to even get the branch up and running.</p><h4><strong>7. Not All Reviews Are Created Equal (ND)</strong></h4><p>Does that one line change really need two developers for approval?</p><p>Security and pricing changes will need more/more senior review over small CSS changes.</p><h4><strong>8. Pairing Up (ND)</strong></h4><p>Instead of having async code reviews, try having engineers pair up to look at CRs together, or alternatively pair up on writing the code in the first place.</p><p>While this on the face of it doubles the man hours required on a piece of work, the level of knowledge sharing, and increase in quality of code makes it a worthwhile investment.</p><h4>9. Time</h4><p>Ensure time is given for code review in your estimates.</p><p>In many teams it’s all too common for every possible man hour of the sprint was filled with tickets.</p><p>If you have 5 people on a team, and each day is two points, it’s tempting to fill the sprint with 100 points of tickets. No time for meetings, discussion, or code reviews. In the team where the review process worked well, we calculated the number of points the team could handle in a sprint and immediately cut it in half.</p><p>This allowed team members to feel like they had TIME to code review and correctly set expectations for management.</p><p>Treat code reviews like an investment. Investing an hour of time now to avoid 3 hours of rework later. Use metrics to track the number of story points tackled in a sprint.</p><p>If it&#39;s high, but code reviews are not being done, dial it back. Give 20% time to code reviews and revaluate your metrics after a trial period.</p><p>Where it worked, it was also a team that was very process orientated as a whole. So, no one thing acted as a silver bullet for solving the problem. I certainly don’t profess to be an expert, but that team was the best experience I’ve had as a developer and I can count on one hand the number of times I undertook rework.</p><p>The struggle I’m finding now is building habits.</p><p>We’re a young team, both in our time together and levels of experience.</p><p>Getting the team to build the habit of, and confidence to the code review is proving to be an ever-present challenge.</p><p>We’ll be implementing many of these solutions as we move forward, ensuring buy-in from the team each step of the way.</p><p><strong>CTO Academy</strong></p><p>At CTO Academy, we provide online leadership courses, coaching, and community to global technology leaders.</p><p>Our latest online course <a href="https://cto.academy/the-digital-mba-for-technology-leaders/?utm_source=organic&amp;utm_medium=medium.com&amp;utm_campaign=andrew_medium_article&amp;mtm_campaign=andrew_medium_article&amp;mtm_keyword=bottlenecks_code_reviews">The Digital MBA for Technology Leaders</a> is for senior tech leaders or those aspiring to become one. It will help you to bridge that gap between the technical and the commercial.</p><p>If interested in finding out more, you can book a discovery call with me, the CEO, Andrew Weaver.<br>Book that call <a href="https://andrew-ctoa.youcanbook.me/">here</a>.</p><p>Written by <a href="https://www.linkedin.com/in/andrew-ryan-61a0a267/">Andrew Ryan</a> — Engineering Manager @ Intuety.io for CTO Academy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c85debd7cdf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you get over the fear of being self-employed/being your own boss?]]></title>
            <link>https://medium.com/@andrewweaver/how-do-you-get-over-the-fear-of-being-self-employed-being-your-own-boss-88a683ac9be8?source=rss-3d7e86baa5ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/88a683ac9be8</guid>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[start-up-india]]></category>
            <category><![CDATA[fear-of-failure]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Andrew Weaver]]></dc:creator>
            <pubDate>Fri, 24 May 2019 06:04:26 GMT</pubDate>
            <atom:updated>2019-05-24T06:04:26.687Z</atom:updated>
            <content:encoded><![CDATA[<p>To this question posted recently on Quora …</p><p><strong>This depends on where the fear comes from?</strong></p><p>Let’s look at 4 of the most common fears — in no particular order;</p><p><strong>1. Fear of the unknown</strong></p><p>What’s it like?</p><p>How does it work?</p><p>What if, what if, what if …</p><p>You won’t know how it feels until you do it but, you can jump blind or you can jump with a greater degree of certainty by researching and understanding intimately the market and/or idea you’re launching.</p><p>Too many people jump into the unknown blindfolded. They like the idea of being their own boss. They want the freedom. They think they have a great “idea”. But they haven’t committed the time and care to research properly.</p><p>Setting up a kids clothes shop on a street with 4 others will be tough.</p><p>Launching an online marketplace thinking it’s easy street, won’t be.</p><p>Like all things in life that have an element of risk, you mitigate that risk by your due diligence beforehand.</p><p><strong>2. Fear of insecurity</strong></p><p>Yep, it’s definitely an insecure world but then again, so is employment. Since the financial crisis in particular, what job is secure? What you get with self employment is greater control. Not total control but definitely more of it.</p><p>The insecurity (particularly at the start) is mainly about money so I refer you to the answer above, and another to come … mitigate as much as you can against the wild unpredictability of your income during those early days (the boss always gets paid last) and the lack of a safety net will be a struggle to start with, but you get used to it and being your own boss creates a freedom that can offset most if not all of it.</p><p><strong>3. Fear of failure</strong></p><p>This is a big one for many people.</p><p>What if I fail?</p><p>What will it look like?</p><p>What will my friends and family think?</p><p>You almost certainly be rejected on a constant basis — you get used to dealing with rejection when working for yourself.</p><p>You might well fail at times and some people who succeed in self employment, have one of more traumatic failures behind them but their success was shaped as much by what they learnt with their failures, than anything else.</p><p>The key here is that failure does not define you. Your strength and courage to become self-employed is what defines you. Dealing with the occasional vicissitudes of self employment will shape you, but failure should never daunt you.</p><p><strong>4. Fear of financial hit</strong></p><p>Don’t under estimate the impact on your personal income when starting a business. Unless you’re super lucky and immediately start to generate bags of revenue in your business, you are likely to suffer a significant drop in income to start with and you need to brace yourself for this.</p><p>You need to be sure you can live on what you have (and your family as well).</p><p>Do not jump from secure employment until you have got some cover with income and have projected a worse case scenario for at least the 1st 12 months.</p><p>Halve your forecasts, double your costs.</p><p>Don’t under estimate the time it will take for your business to be driving sufficient amounts of cash to (a) pay you anything and (b) pay you anything like you earn now.</p><p>Being your own boss is fantastic, liberating, life enhancing.</p><p>But ‘fear’ or anxiety is locked into the experience so prepare well, understand the risks … and go for it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88a683ac9be8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jump off the cliff, Then start assembling the plane]]></title>
            <link>https://medium.com/@andrewweaver/jump-off-the-cliff-then-start-assembling-the-plane-c3811c010faf?source=rss-3d7e86baa5ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3811c010faf</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Andrew Weaver]]></dc:creator>
            <pubDate>Wed, 18 Apr 2018 15:07:55 GMT</pubDate>
            <atom:updated>2018-05-21T07:46:38.895Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*Db0GBCNLjOJvHpP8D0Db8A.jpeg" /></figure><p>If you’re new to the start up world or indeed, the wider world of entrepreneurship, then you can do worse than listen to the podcast <a href="https://www.google.co.uk/search?client=safari&amp;rls=en&amp;q=masters+of+scale&amp;ie=UTF-8&amp;oe=UTF-8&amp;gfe_rd=cr&amp;dcr=0&amp;ei=SsvAWu3bCsaN8QfuuIGIBg">‘Master of Scale’.</a></p><p>Hosted by Linkedin founder Reid Hoffman, it’s a slickly produced insiders view of what it takes to make it big, from someone who knows and who continues to invest in multiple early stage companies.</p><p>One of Reid’s great metaphors for the attitude required of successful entrepreneurs, is that launching a start up is a bit like “jumping off a cliff and only then, starting to assemble the plane”. You might have a big idea, you’ve seen a market opportunity but the difference between those who sit on ideas and those who go for it, is that the latter are prepared to jump, with little or no idea what’s going to happen when they hit mid air. Like a coyote cartoon, where you race across the cliff edge, then start pedalling hard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*hSFRB8nt7IQppTDN.jpeg" /></figure><p>Because launching and making a success your start up or business in general, requires many things not least and probably most importantly, grit and tenacity. Throw in a little luck and a lot of good timing and you have the standard ingredients required but, if the going gets super tough (and it will) and, you happen to have parachute handy then you’re likely to grab for it. No parachute, and it’s amazing how inventive you can become.</p><p>One of the major issues for anyone aspiring to board level management or indeed, creating and launching a company themselves is a fundamental change of mindset from being part of a company, to being the driver of that company. It’s about shifting from re-active, to pro-active. If you’re working for a forward thinking company then hopefully, you’re already part of the decision making process, wherever you are in that organisation but, more than likely whilst climbing the ladder you’ll be dealing with strategy coming down from above. Reach that top table and suddenly it’s you setting the agenda, driving the strategy, convincing the outside world, taking responsibility. It’s super exciting, potentially rewarding but, it requires a certain skill set and nerve, that not everyone has.</p><p>Can it be learnt? Absolutely on one level in terms of the fundamentals you need to understand but ultimately, whilst everyone approaches the world of start ups and fast growth companies with their own unique perspective, the one unified characteristic for most, is sheer bloody minded grit and determination. To look for the opportunity, to build the product, to remove the doubts and naysayers, to negotiate the obstacles, to lead the team.</p><p>But let me tell you, there is no greater motivation in the morning, than looking down and realising your plane building skills need more work.</p><p><em>Article was originally written on behalf of </em><a href="http://www.cto.academy/"><em>www.cto.academy</em></a></p><p><em>(Helping great developers, become high value CTOs)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3811c010faf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Everyone is a bit broken … so manage with compassion”]]></title>
            <link>https://medium.com/@andrewweaver/everyone-is-a-bit-broken-so-manage-with-compassion-99fe07d69d19?source=rss-3d7e86baa5ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/99fe07d69d19</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[compassion]]></category>
            <dc:creator><![CDATA[Andrew Weaver]]></dc:creator>
            <pubDate>Sun, 08 Apr 2018 08:42:50 GMT</pubDate>
            <atom:updated>2018-04-08T08:43:04.554Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*c-K8aujaBEwIWTvq2DPc8Q.jpeg" /></figure><p><strong><em>“Everyone is a bit broken … so manage with compassion”</em></strong></p><p>Credit for the “everyone is a bit broken” quote goes to Professor Vikas Seth, delivered via a fantastic <a href="https://www.youtube.com/watch?v=hrSq-85D8dg">Ted talk</a> that looks at vulnerability and how everyone around you, is going through the same or similar shit.</p><p>The challenge within teams and in management roles, is that not many people are prepared to acknowledge this truth and behaviour is sometimes misinterpreted, with communications, relationships and team dynamics often suffering from a fundamental lack of honesty.</p><p>The start up world can suffer from this more than most, be it pride, a “fake it till you make it” culture or simple lack of self awareness.Strip down these facades and you’ll find that most senior people in most companies suffer from vulnerability and their own version of the <a href="https://www.fastcompany.com/40421352/the-five-types-of-impostor-syndrome-and-how-to-beat-them">imposter syndrome</a>.</p><p>I was once blindly unaware that many of my fellow travelers suffered from some of these insecurities, often making the assumption that all around me were floating serenely towards their natural destiny of success and acclaim.</p><p>My lightbulb moment came when chatting late night with an eminent QC, some small lagers having stripped away the pretence as he admitted that despite significant recognition and success within his world of work and play, he still suffered every day from the fear of a hand on his shoulder and someone exposing him for the fraud he clearly must be.</p><p>Widespread research and high profile admissions cement the fact that it exists at all levels. Starbucks CEO, Howard Schultz, <a href="http://www.nytimes.com/2010/10/10/business/10corner.html?_r=1">once admitting</a> that “Very few people, whether you’ve been in that job before or not, get into the seat and believe today that they are now qualified to be the CEO. They’re not going to tell you that, but it’s true.”</p><p>Those who experience impostor syndrome will often feel like they’re the only ones. But the reality is that many of us are or have been struck with the same feelings of vulnerability. It might impact in micro ways, such as walking into a networking environment and assuming you’re the only one who struggles with small talk (the rest of us do, don’t worry) or on a macro level of under selling yourself.</p><p>Understanding and working with others is an important element of making progress within a company, and for bringing others with you. Successful senior managers and entrepreneurs understand that there is always more than meets the eye with people you meet on this journey and that understanding and working with issues like vulnerability, both for yourself and others, will make a huge difference to the environment you’re hoping to shape around you.</p><p>Understanding people is one of the major challenges for being a success in business. Understanding that everyone is a little broken, is an important stepping stone towards managing with compassion.</p><p><strong>Further Reading</strong></p><p>“Feeling like an imposter? You can escape this syndrome” : <a href="https://bit.ly/2xQuZYV">https://bit.ly/2xQuZYV</a></p><p>“5 Types of Imposter Syndrome : How to Beat Them” : <a href="https://bit.ly/2qXiqHR">https://bit.ly/2qXiqHR</a></p><p><strong>Changing The Perception of Mental Health</strong></p><p>Doing some great work here in the UK : <a href="https://sanctus.io/">https://sanctus.io</a></p><p><em>[edited version of an article that first appeared on </em><a href="http://www.cto.academy/"><em>www.cto.academy</em></a><em> — online learning platform helping great developers, become high value CTOs]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99fe07d69d19" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>