<?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 CTO Academy on Medium]]></title>
        <description><![CDATA[Stories by CTO Academy on Medium]]></description>
        <link>https://medium.com/@andrew-69589?source=rss-4af0a760ec34------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*jzl4QKpVLF6khqbb</url>
            <title>Stories by CTO Academy on Medium</title>
            <link>https://medium.com/@andrew-69589?source=rss-4af0a760ec34------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:38:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrew-69589/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[What do senior technology leaders need in a leadership development programme?]]></title>
            <link>https://andrew-69589.medium.com/what-do-senior-technology-leaders-need-in-a-leadership-development-programme-e3717aa8996a?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3717aa8996a</guid>
            <category><![CDATA[cto-program]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Thu, 14 May 2026 13:04:56 GMT</pubDate>
            <atom:updated>2026-05-14T13:04:56.539Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s no shortage of leadership development available for senior technology leaders.</p><p>From highly regarded executive programmes to specialist courses, the quality is often high.</p><p>So the challenge for those looking to upskill their technology leaders is rarely about availability.</p><p>It’s almost always about <strong>fit</strong>.</p><p>So what skills do senior tech leaders need to deliver impact in today’s environment?</p><p>The most effective technology leaders develop a <strong>hybrid capability</strong>.</p><p>They can operate commercially, influence across the organisation, and translate complexity into decisions.</p><p>So it’s about being kept informed and updated around technology.</p><p>It’s absolutely about strategy, communication, and stakeholder management.</p><p>But they are only part of the picture.</p><p>What is often overlooked is the role of <strong>personal development</strong>.</p><p>How a leader thinks.<br>How they respond under pressure.<br>What drives their decisions?<br>How aware and aligned they are with their core values.</p><p>This is where factors like</p><p>Mindset<br>Curiosity<br>Critical thinking<br>Emotional intelligence<br>Intrinsic motivation</p><p>All play a crucial part in achieving success in those senior technology roles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FIcWDz7cRiRVTaMACpzYTg.png" /></figure><p>Whilst you can categorise these as “soft” skills.<br>We prefer to call them “core” skills.</p><p>They are the capabilities that determine whether a leader can apply everything else effectively.</p><p>Without this foundation, knowledge doesn’t translate into impact.</p><p>A leader can understand the latest technologies.</p><p>They can articulate strategy.</p><p>They can impress in conversation.</p><p>But still struggle to influence, align, and drive meaningful change.</p><p>This is where the opportunity lies around training and leadership programmes</p><p>Not just in developing what leaders know —</p><p>But in shaping <strong>how they think, operate, and lead</strong>.</p><p>Because when that shifts —</p><p>Everything else follows.</p><p>And the organisation sees the impact where it matters most:</p><p>In decisions, alignment, and execution.</p><p><strong>visit </strong><a href="https://cto.academy/"><strong>cto.academy </strong></a><strong>for more insight</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3717aa8996a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 signs your organisation has an alignment problem (even if no one is calling it that)]]></title>
            <link>https://andrew-69589.medium.com/3-signs-your-organisation-has-an-alignment-problem-even-if-no-one-is-calling-it-that-45ed2bab2135?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/45ed2bab2135</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[cto-academy]]></category>
            <category><![CDATA[chief-technology-officer]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Tue, 05 May 2026 10:16:29 GMT</pubDate>
            <atom:updated>2026-05-05T10:16:29.023Z</atom:updated>
            <content:encoded><![CDATA[<p>Many organisations can feel out of sync long before it’s clearly understood.</p><p>Progress is slower than expected.</p><p>Decisions feel harder than they should be.</p><p>Teams are working — but not always moving forward.</p><p>It doesn’t look like a single problem but a series of disconnected issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d204aXhM-vnrZM70FnhORg.png" /></figure><h3>1. The same conversations keep happening</h3><p>Decisions are made.</p><p>Then revisited.</p><p>Then reopened again a few weeks later.</p><p>Meetings feel repetitive. Alignment feels temporary.</p><p>People leave with different interpretations of what was agreed.</p><p>Over time, this creates hesitation, which slows everything down.</p><h3>2. Work moves forward — but momentum doesn’t build</h3><p>Projects can progress.</p><p>Milestones are often hit.</p><p>But there’s no real sense of acceleration.</p><p>Each phase feels like it’s starting from scratch.</p><p>Energy is spent re-explaining, re-aligning, re-prioritising.</p><p>Not because people aren’t capable, but because alignment isn’t holding.</p><h3>3. Frustration shows up in subtle ways</h3><p>You hear it in tone, not just words.</p><p>“It’s more complicated than that.”</p><p>“We’ve already tried that.”</p><p>“That’s not how it works.”</p><p>Different parts of the organisation begin to lose confidence in each other.</p><p>Not dramatically.</p><p>But enough to create friction.</p><p>Individually, none of these is critical.</p><p>Together, they create something more serious:</p><p><strong>A hidden drag on performance.</strong></p><p>What makes this difficult is that it doesn’t clearly sit anywhere.</p><p>It’s not obviously a process issue.</p><p>It’s not clearly a skills gap.</p><p>It’s not something a new system will fix.</p><p>But it is something that can be addressed.</p><p>Because at its core, this is about how people across the organisation:</p><ul><li>Understand problems</li><li>Make decisions</li><li>Stay aligned over time</li></ul><p>And when that improves —</p><p>The organisation doesn’t just feel better.</p><p>It <strong>starts moving faster</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45ed2bab2135" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Biggest risk in your organisation isn’t technology. It’s misalignment around technology.]]></title>
            <link>https://andrew-69589.medium.com/biggest-risk-in-your-organisation-isnt-technology-it-s-misalignment-around-technology-d458a36b99b1?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/d458a36b99b1</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership-training]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[capability-building]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 15:11:39 GMT</pubDate>
            <atom:updated>2026-04-29T15:13:34.671Z</atom:updated>
            <content:encoded><![CDATA[<p>Organisations are investing more than ever in technology — AI, data platforms, new operating models. And yet, the outcomes often fall short.</p><p>McKinsey estimates that <strong>around 70% of digital transformations fail to deliver expected value</strong> (<a href="https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/unlocking-success-in-digital-transformations">source</a>). The usual explanations are complexity, execution, or culture.</p><p>But in practice, the root issue is more fundamental:</p><p><strong>The business and technology are not aligned in how they understand the problem.</strong></p><p>At the top of the organisation, strategy is framed in terms of:</p><ul><li>Growth</li><li>Efficiency</li><li>Customer value</li></ul><p>Further down, execution is shaped by:</p><ul><li>Systems</li><li>Architecture</li><li>Delivery constraints</li></ul><p>Both perspectives are valid but they are rarely connected by a shared understanding of what matters most.</p><p>It’s a schism — driven by a lack of <strong>situational awareness</strong> (see<a href="https://semaphore.io/blog/wardley-maps"> Wardley Mapping overview</a>), no common view of how value is created and delivered, and ultimately, value moving too slowly through the organisation (as described in Jonathan Smart’s work on<a href="https://www.mindtheproduct.com/better-value-sooner-safer-and-happier-by-jonathan-smart/"> Better Value Sooner Safer Happier</a>).</p><p>This misalignment shows up in very practical ways:</p><ul><li>Decisions take longer than they should</li><li>Priorities shift mid-delivery</li><li>Technology is seen as a bottleneck rather than an enabler</li></ul><p>Not because teams lack capability —</p><p>But because they are working from different assumptions.</p><p>This is where most organisations focus on structure, process, or tooling.</p><p>But those interventions don’t address the real issue.</p><p>Because this isn’t a technology problem.</p><p><strong>It’s a leadership capability problem.</strong></p><p>And this is where the opportunity sits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OBhBXetucCZuP_C9x4wCxg.png" /></figure><p>Organisations that align business and technology effectively don’t just avoid failure — they <strong>outperform</strong>.</p><p>Research from McKinsey shows that top-performing companies tightly integrate business and technology to drive performance (Rewired to Outcompete).</p><p>Similarly, findings from the <em>Accelerate</em> (DORA) research show that high-performing organisations achieve <strong>both faster delivery and greater stability</strong> when alignment is strong (<a href="https://cloud.google.com/devops/state-of-devops">State of DevOps report</a>).</p><p>In other words:</p><p>They don’t just build better systems.</p><p>They <strong>execute better as a business</strong>.</p><p>Until organisations develop leaders who can align business intent with technical reality —</p><p>They won’t just move slower.</p><p>They’ll be outperformed by those who don’t.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d458a36b99b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Our Hiring Strategy Changed, When We Went For Growth]]></title>
            <link>https://andrew-69589.medium.com/how-our-hiring-strategy-changed-when-we-went-for-growth-d2373b783662?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2373b783662</guid>
            <category><![CDATA[hiring-strategy]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[interview-tips]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Mon, 15 Mar 2021 12:12:45 GMT</pubDate>
            <atom:updated>2021-03-15T12:12:45.299Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Hiring and examining candidates for senior tech roles" src="https://cdn-images-1.medium.com/max/999/0*bQ9WqTFuJ7iUmLBu.jpg" /></figure><p>Back in 2012, I started a two-man agency in Manchester with aspirations of becoming the goto company for helping SMEs achieve digital transformation.</p><p>We had to start with the basics which meant websites, apps, print … yep, you name it, we probably had a tender for it at some point.</p><p>We were soon given the green light on multiple projects and within a week we were hiring and had become employers, expanding the team slowly and organically. When opportunities came in, we would assess the skills needed and recruit to win.</p><p>Naturally, we created a core set of skills within the agency and tried to align our resources with future work and by 2018 we were ten people, landing projects in PIM, eCommerce and a few entrepreneurs with exciting app ideas.</p><p>That’s how we met Will, a young quantity surveyor working in the rail industry. He had a potential game-changer of an app idea.</p><p>After a few months of prototyping and some passionate pitches to Angel investor groups, Will landed a sizable round of funding. There was a natural fit for us to continue working on what we’d built together, so we combined forces.</p><p>With myself as CTO, Will as MD, and a core set of employees, we pivoted to become a fully-fledged SaaS platform.</p><p>We were practically a new business with investor money in the bank and able to hire new people with a clear focus on growth. This time though our hiring focus had changed, with skill sets and hiring out of necessity were no longer the priority.</p><p>We now felt that we wanted people who could fit in, click with others and were genuinely excited by the problem we were solving. Hiring had taken on a very different dynamic and it felt like our recruitment strategy was starting again from scratch.</p><p>For lots of reasons the past couple of years has been very enlightening for me and not least in the area of recruiting for growth with a very clear focus on the type of people we wanted to hire.</p><p>So I wanted to write an article with my personal experience of what really matters when you’re making those early hires …</p><h3>1. Check Your Responsibilities.</h3><p>As a first time employer, you’ll have new responsibilities. Whether employees report to you directly or not, you should always be aware of your duties as part of the senior management team. I know the CTO Academy community is global so different countries will have different resources to help but here in the UK, an excellent place to start is the government website. Read more here: <a href="https://www.gov.uk/get-ready-to-employ-someone">https://www.gov.uk/get-ready-to-employ-someone</a>.</p><p>On the other hand, this is the opportunity to relinquish (partially) some of the responsibilities youhave daily. But from personal experience I know it’s one of the most challenging things to cometo terms with throughout your career. This is your baby. You have a vision of perfection; it could be related to the tech stack, the code quality, or a different business area entirely. Nobody will be able to reach the standard you probably hold yourself, at least straight away.</p><p>In <a href="https://www.amazon.com/Alliance-Managing-Talent-Networked-Age/dp/1625275773"><em>The Alliance — managing talent in the networked age</em></a>, authors Reid Hoffman, Ben Casnocha, and Chris Yeh refer to hiring as a tour of duty. It is a declaration of trust and a call to arms with a clear set of objectives and expectations. I recommend giving this book a read, as your expectations of a new hire are likely to be unrealistic. For example, you and other founders will be working crazy hours because this business is your life right now; you are all in until the end. Non-founding members may be passionate about your vision and excited about the company. Still, at the same time, it’s just a job, and they will probably move on.</p><p>Unclear expectations can be problematic. For instance, a vague or broad job description doesn’t give an employee any meaningful direction. It could result in the wrong person being hired or hiring someone at the wrong time, costing the business more in the long term. In rowing, this error in timing is known as catching a crab; a rower’s oar can become stuck in the water and acts as a brake, slowing the boat down. A severe crab can eject a rower or even capsize the boat — direction and timing are equally important.</p><p>To be clear about what you expect from a new employee, write a job description as if it were a reflection of their first year. Work backwards through the year to set<a href="https://www.managers.org.uk/wp-content/uploads/2020/03/CHK-231-Setting_Smart_Objectives.pdf"> SMART objectives</a> (Specific, Measurable, Achievable, Relevant, Timely) along the way. If the results don’t align with your company’s goals, then it could be that the job’s scope is too broad or you’re hiring too early.</p><h3>2. Company values and culture.</h3><p>A well-defined set of values underpinning your business culture and strategy will help motivate people. Having an immutable set of expectations around the way everyone communicates and behaves will ensure you can effectively deal with problems for the difficult times ahead. You should always be able to look at core values and ask, “Does this situation align with them?”.</p><p>Being a CTO, one of your goals is to create a functional team of professionals. This doesn’t necessarily mean hiring based on skills; I’ve seen some of the most senior-level engineers crippled by their attitude toward one another. A functional team is a diverse group of people whose greatest competencies are professionalism, respect, and a growth mindset. Their skill sets all differ, as will their career and walk in life.</p><p>Your challenge is finding them and creating an environment that upholds company values and meets its objectives. You also need to defend their time and inspire them to be creative without the prospect of being blamed for getting something wrong or thinking outside of the box.</p><p>New businesses are chaotic as there are just too many things to do. There are also many unknowns. Sometimes, the only way forward is to try, hack it, get all <strong>hands on</strong> deck. I emphasise the word “sometimes” because all the time isn’t sustainable; you need a rhythm.</p><p>“Creativity, progress, and impact do not yield to brute force.”- from <a href="https://www.amazon.com/Doesnt-Have-Be-Crazy-Work/dp/0062874780">It doesn’t have to be crazy at work by Jason Fried and David Heinemeier Hansson.</a></p><p>If you ensure that your values and culture support knowledge sharing and continuous process improvement, you can let the team get on with it. To quote our ops director on his perception of Agile, “its process, practice, practice, practice, process, practice, practice …”</p><h3>3. Finding and Interviewing candidates</h3><p>My advice for finding candidates is that unless you have time to burn, then use a recruiter. Finding one is pretty straightforward; just go to your email or LinkedIn inbox. If by some miracle you’ve avoided detection, you can always do a quick search for one.</p><p>When using recruiters, check the terms and negotiate; working with them exclusively, for instance, can yield better rates and better quality CVs sent through. If you want to use multiple for better coverage, any more than three on the same role is a bit much. There’s only a finite number of candidates out there, and recruiters can speak to a lot in a day. Whatever your approach, keep them all informed.</p><h3>Before interviewing</h3><p>Reading CVs can be monotonous; this is where recruiters are helpful. Walking them through your job description and setting expectations will save many hours. The best recruiters in my experience are those that a) actually send you quality CVs b) send snippets of their conversationswith candidates c) act as ambassadors to your company.</p><p>When checking a CV, I look for mentions of achievements or responsibilities at each company, the dates and length of time between roles and mentions of activities/hobbies outside of work. You can quickly build up several questions based on a few key bullet points.</p><p>Over the past year, I’ve had applications claiming more experience than on the CV. I’ve even hadtechnologies listed that didn’t exist at the time of their employment. Checking dates, I would say,is essential.</p><h3>During interviews</h3><p>“Why does your company exist?”.</p><p>“Where do you see the company in two years?”.</p><p>“Why should I come to work for you?”</p><p>All three are reasonable and valid questions from a candidate. I’ve never had the last one asked directly, though it’s kind of the elephant in the room being a small business.</p><p>For this reason, I start interviews with a candidate friendly elevator pitch and talk briefly about my company’s aspirations. By setting some context, I find that I address the questions above, encouraging a more engaging interview. In the past year, I’ve discovered that pitching first has taken the edge off any nerves candidates have had from coming into a video call with strangers.</p><p>If working with a new recruiter, interviews can reveal how much of an ambassador of your company they are. In the past, I have asked candidates how much recruiters have told them about the role before pitching.</p><p><em>As an aside, if you’re conducting interviews by video conference, stick to a maximum of two people from your side; any more can be overwhelming no matter how friendly you might be.</em></p><p>Keeping the interview as a casual conversation can be a challenge at times. Asking open questions such as “What do you think about X?” instead of “Can you do Y?” generally helps the conversation flow.</p><p>Questions I like to ask engineering candidates focus on problem-solving, conflict resolution, being a team player, thirst for learning, root cause analysis vs kicking the can, and willingness to fight fires.</p><p>I always ask why a candidate has chosen to move on from their previous role in the first interviews. You can tell a lot about a person’s integrity, personal objectives and character from their response. Bad-mouthing a previous employer, for example, is a red flag for me.</p><h3>After the interview</h3><p>Straight after an interview is the best time to reflect and make a decision. My only advice here is to go with your gut. Typically if I come out of an interview and don’t think, “Yes, I’ll hire this person or take them to the next stage”, then I don’t dwell on it. It’s no.</p><p>I always aim to give feedback within the same working day, then if the answer is no, everyone can swiftly move on. Giving constructive feedback, however, is a must. Think about the person on the receiving end and their perception of your company after. Even if that person was rude and the worst candidate you had ever encountered, you still have a chance to offer some value to them.</p><p>If all goes well and you find the ideal employee, congratulations! Send an offer letter and an employment contract to them. Confirm their start date and check their references. If there is a negotiation on their employment package, remuneration, career development spend, holidays, and working hours are all cards, you can play. Be sure to check the impact on your business before promising anything.</p><h3>4. Onboarding and 1:1s</h3><p>Onboarding can be more than just a tick box exercise of introductions, tools and training. An excellent way to bring someone new to the business and keep them motivated is to create a 90-day plan and schedule regular 1:1s. By setting objectives in their first few days, your employee will know their path instead of getting lost in day-to-day tasks. The first few goals can be low hanging fruit like “Read the employee handbook” to get them started; after that, create more challenging objectives.</p><p>By week two or three, they should have a grasp of the day to day and be progressing through the tasks and/or objectives you’ve set them. At this stage, using output as a performance indicator is probably not the best idea. Instead, I would opt for performance review through their approach towork, learning, and professional relationships with others.</p><p>Over the years, I’ve had 1:1 meetings as walking sessions over coffee or en-route to lunch. Getting away from the office is excellent for keeping it casual. It’s essential to get feedback during this time and learn as much as possible about what problems people are having operationally and look mostly forward rather than backward.</p><p>More recently, Sanjay at the CTO academy has helped me structure weekly 1:1s. A lot of emphasis is now placed on objective setting, wins, losses and learnings. Whenever an employee comes to me with a loss, we’ll try to figure out what we’ve learned from the loss together and turn it into a win for them.</p><p>Mixing in peer 1:1s can also help establish better working relationships, providing timely feedback between colleagues. I found this very valuable for working out how an entirely new role fits into the engineering team.</p><h3>Final Thoughts</h3><p>In conclusion, hiring new colleagues is an opportunity to grow your business objectively, rather than through numbers alone.</p><p>Finding a skillset is easy; you can quickly extend your team’s capabilities through contracting or freelancers.</p><p>However, attitudes and behaviours are the seeds of something much bigger, and you can reap the benefits by creating the right environment, setting expectations, and supporting the growth of individuals in the team.</p><p>Article written by <a href="https://www.linkedin.com/in/paul-d-clegg/?originalSubdomain=uk">Paul Clegg</a>, CTO at <a href="https://www.raildiary.com/en">Raildiary</a> in Manchester.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2373b783662" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Effective Hiring for Technical Talent]]></title>
            <link>https://andrew-69589.medium.com/effective-hiring-for-technical-talent-b86b0cd7d1a9?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/b86b0cd7d1a9</guid>
            <category><![CDATA[hiring-strategy]]></category>
            <category><![CDATA[aptitude-test]]></category>
            <category><![CDATA[talent-management]]></category>
            <category><![CDATA[talent-acquisition]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Tue, 09 Mar 2021 08:54:13 GMT</pubDate>
            <atom:updated>2021-03-09T08:54:13.033Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Tips for effective hiring in tech" src="https://cdn-images-1.medium.com/max/1024/0*2jsiCZwD04pAj5-7.jpg" /></figure><p>Whether we like it or not, part of being a technical leader is mastering the time-consuming, and sometimes painful recruiting and hiring process.</p><p>To be successful as a technical leader you need an exceptional technical team but the good news as a leader, is that you own the responsibility to build and grow that team.</p><p>While some companies have developed good processes for hiring technical teams, startup and small/mid-size companies often lack well-defined hiring strategies or use processes that aren’t effective for assessing technical hires.</p><p>We have all made hiring mistakes that proved costly and painful so I view it as business critical for technical leaders to establish and implement an effective hiring process for building high performance technical teams.</p><p>Earlier in my career as a senior software engineer, I was hired by the Peter Norton Computing Group, recently acquired by Symantec.</p><p>They had the largest concentration of technical talent that I had seen up to that point in my career so I found it exciting to work with a group of such experienced technical talent and strong motivation, something of a “dream team”.</p><p>While one of my childhood nicknames in elementary school was “the brain,” I was far from the smartest person in the room at Peter Norton. It was sufficient enough for my ego to believe that, in a small meeting, I might be a close second.</p><p>As a result of that experience I learned a few things about the technical teams I wanted to be a part of:</p><ul><li>I preferred working with other senior software engineers over entry-level engineers.</li><li>I enjoyed working with other highly self-motivated people.</li><li>I loved working with very intelligent and talented people and teams.</li><li>I felt great satisfaction with the success in the marketplace that exceptional teams produce.</li></ul><h3>Hiring for Talent</h3><p>It also led me to a philosophy about hiring for technical teams.</p><p>Fundamentally, when hiring software engineers and all other things being equal, I value talent (i.e., innate ability) over skill (i.e., learned ability).</p><p>Borrowing from the Agile Manifesto, while there is value in skills, I value talent more.</p><p>As a technical leader, I’ve discovered and adopted 2 tools that I have found useful in hiring for technical talent:</p><ol><li>“Firing Squad” Technical Interview</li><li>Aptitude Assessment Test</li></ol><h3>“Firing Squad” Technical Interview</h3><p>As part of their hiring process the Peter Norton Group used a panel interview called the “firing squad”.</p><p>This was not your typical subjective panel interview, which I’ve never really liked.</p><p>The firing squad technical interview is different in that it is purely technical in content and more objective than the typical panel interview.</p><p>As I grew into becoming a technical leader and eventually CTO, I incorporated the firing squad technical interview into my own hiring process and found it to be effective in helping select intelligent and talented individuals.</p><p>Let me explain the process and objectives as it relates to interviewing technical candidates.</p><p><strong>Suggested Process</strong></p><ul><li>Hiring manager and selected technical staff (usually 3–4 developers) meet together with the candidate.</li><li>Participating technical staff should have previously reviewed the candidate’s resume and have a good idea of the type of person we’re looking to hire.</li><li>Participating technical staff should have a broad representation of technical skill sets, so that they can effectively drill down on all relevant technical areas.</li><li>The candidate is informed that we’re going to ask questions of a technical nature to get a better feel for his/her technical strengths and weaknesses. They will be told it’s ok to respond with “I don’t know,” venture a guess (e.g., “I’m not sure, but I would think…”), or think through the question and problem out loud.</li><li>Participating technical staff will ask technical questions, starting at a high level and then drill down on the specific topic until the topic is exhausted. Here is an example of a drill down into one specific topic:</li></ul><p><em>“Your Resume mentions that you have some experience with SQL. Would you tell us more about your work in this area?”</em></p><p><em>“Can you give us an example of an SQL query?”</em></p><p><em>“Ok, so it sounds like you’re familiar with SQL queries. Can you explain what a Join is?”</em></p><p><em>“How about a Left Outer Join?”</em></p><p><em>“Ok, so if a row from the first/left table doesn’t have a match, does it show up in the result?”</em></p><ul><li>Asking general computer science questions can be useful in assessing the candidate’s technical capability (e.g., “what is inheritance?”), however, it is generally not beneficial to do research to come up with questions and answers. The collective knowledge of the interviewing team should be sufficient to assess the relevant technical capability of the candidate.</li><li>Move from topic to topic until running out of time or exhausting relevant topics.</li><li>After the candidate has left, each team member shares their thoughts and opinions of the candidate (i.e., what they liked/disliked).</li></ul><p><strong>Target Objectives</strong></p><ul><li><strong>H</strong>ow much of the candidate’s resume is fluff vs. real (e.g., did they just work on a project that used JavaScript or did they write JavaScript code, and how proficient are they?).</li><li>Insight into how the candidate thinks (i.e., we’re not just hiring for skills, we’re hiring for talent).</li><li>Insight into the personality of the candidate and how they interact with others.</li><li>How the candidate responds under pressure.</li><li>Opportunity for the candidate to get to know members of our team and give them a feel for our personalities and how we interact with each other. The candidate is evaluating fit from their perspective as well.</li></ul><p><strong>Special Notes</strong></p><p>The firing squad technical interview is an unfair match-up by design.</p><p>No candidate comes out with a perfect score.</p><p>A key objective is to go beyond assessing the candidate’s learned skills and see how they think (i.e., innate ability).</p><p>The idea is NOT to beat up the candidate. Once it is clear the candidate is unable to effectively drill down further on a certain topic, move on to another topic rather than continue to ask questions they are unable to address.</p><p>In practice the firing squad takes more time with a more knowledgeable and more talented candidate.</p><p><em>IMPORTANT: Remember that while we have a need to assess the technical capability of the candidate, we want to do this in a professional and friendly manner. If we decide to hire the candidate, we don’t want them to decline because they think we are jerks.</em></p><h3>Aptitude Assessment Test</h3><p>Later in my career, I was introduced to an additional tool — an aptitude assessment test.</p><p>There are numerous aptitude assessment tests out there, but the one I’ve used is oriented toward software engineers.</p><p>The test describes a simple hypothetical computer language, and then asks multiple choice questions related to this hypothetical language.</p><p>The 20 questions on the timed test gradually introduce additional syntax, semantics, operators, etc. for this hypothetical language, and subsequent questions build upon prior information provided about the language.</p><p>While prior experience with computer languages would likely be advantageous, it is not required as the test itself provides everything needed to answer the questions. Which makes sense, since it is an aptitude test, not a skills or knowledge test.</p><p>Before using the aptitude assessment test with candidates, I wanted a better feel for what the scores might mean. I took the test myself and invited other members of our technical team to take it if they wanted to. The test scores from internal team members were very closely aligned with my own personal experience of their talent.</p><p>The person I considered to be the most talented member of the technical team achieved a perfect score. We also had a contractor working for us who was a retired military helicopter pilot, and more recently a retired database administrator (DBA) from a U.S. National Laboratory. His background and work experience were non-traditional for a software engineer, but I knew him to be very intelligent, talented, and an excellent problem solver.</p><p>He scored higher than many of the more traditional software engineers on our technical team, which I found consistent with his observed job performance.</p><p>Interestingly, he later told me that the military had pilot candidates take a similar aptitude assessment test to screen their helicopter pilots.</p><p>One aberration to the internal test results was a talented member of the team who scored lower than I expected, but I believe his higher anxiety personality likely made him a poor test taker. Whatever the reason, it’s important to note that a single metric can’t definitively determine future performance.</p><h3>Summary</h3><p>The firing squad technical interview and aptitude assessment test are just two ways to help gauge technical talent.</p><p>The extremely intelligent and talented team member who got a perfect score on the aptitude assessment test also went through our firing squad technical interview about 8 years previously. He had just recently graduated from a college of computer science and had some intern experience. We were looking for a Java developer, but his experience was primarily with C#.</p><p>On paper, he was an unremarkable candidate — a wild card candidate that I tend to bring in for interviews. Despite his minimal real-world software engineering experience, he worked through the technical questions and problems, often with educated guesses.</p><p>We observed his thought process as he figured out answers on-the-fly and correlated his C# knowledge to Java-specific questions. He knocked that interview out of the park and impressed us.</p><p>Despite some reservations from team members that he lacked Java experience, we hired for talent that day and found a “diamond in the rough.” He was one of the best hires I ever made.</p><p>Interviewing and hiring for technical teams is a challenge, made harder by the fact that resumes often lie.</p><p>The firing squad technical interview and aptitude assessment test are not silver bullets, nor are they the end-all-be-all in assessing candidates. You also need to consider other traditional factors when hiring for our technical teams, such as cultural fit.</p><p>Hiring for exceptional talent helps build exceptional teams.</p><p>The firing squad technical interview and aptitude assessment test are useful tools to have in the toolbox for building high performing technical teams.</p><p><a href="https://cto.academy/">CTO Academy</a> provides leadership courses and coaching for technology leaders around the world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b86b0cd7d1a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing The Negative Team Member]]></title>
            <link>https://andrew-69589.medium.com/managing-the-negative-team-member-9ee0cdf2a4fd?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ee0cdf2a4fd</guid>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Tue, 02 Mar 2021 13:58:49 GMT</pubDate>
            <atom:updated>2021-03-02T13:58:49.148Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Negative Face and how negativity affects team dynamics" src="https://cdn-images-1.medium.com/max/1024/0*qhk2dT4n88tRZNnC.jpg" /></figure><p>It’s a remarkable human foible that we can spot the 1 negative person in 100 smiling faces.</p><p>Anyone who has performed on stage or delivered a presentation will recognise the sensation of spotting that face in the crowd who looks far from impressed or engaged with what you’re saying.</p><p>It’s the same in a business environment and particularly during this Zoom era where you immediately spot the individual with the negative body language, lack of engagement, constant fidgeting.</p><p>I recently presented to 80 people and just one individual caught my eye and cast doubt in my mind, as he performed every negative body movement known to man.</p><p>It’s no different when presenting to a team where the negative body language of an individual can have an impact on how you perform and deflect a significant proportion of your energy and focus away from other positive responses.</p><p>But it’s also a potential signal of a deeper and more destructive presence in your team with an individual who has nothing positive to say, irritates colleagues, and makes the working environment difficult for everyone.</p><p><strong>How do you respond to this behavior?</strong></p><p><strong>What feedback should you be giving?</strong></p><p>How do you mitigate the damage someone like this can inflict?<br>How do you differentiate between someone just being awkward or downright toxic?</p><p>And there is a clear difference between the two because the toxic individual is likely to be spreading that negativity around the team and organisation as “There’s a pattern of de-energizing, frustrating or putting down teammates,” says Christine Porath, author of <a href="https://www.amazon.com/Mastering-Civility-Manifesto-Christine-Porath/dp/1455568988">Mastering Civility: A Manifesto for the Workplace.</a></p><p>Hopefully you can spot someone with a toxic attitude before you hire them but attitudes can change and for lots of reasons they might have recently become a nuisance, started rejecting good ideas, putting down bad ones, generally pushing back against everything and everyone.</p><p>You might have inherited them when taking on the job and their attitude has been entrenched within the team dynamic for some time.</p><p>The nuclear option is of course to fire them and rid yourself of the problem as soon as possible. Some people just can’t be changed.</p><p>Whilst the firing option might be superficially attractive you clearly need to explore more positive responses both in terms of the individual involved but also what signals your response will be giving other members of the team.</p><p>Here are some steps you might want to consider when handling the negative team member</p><h3><strong>It’s Your Job To Find Out More</strong></h3><p>You need to take a closer look at the behavior and try to understand what might be causing it.</p><p>What is the source of their unhappiness?</p><p>Nobody wants to spend their days at work being miserable and it’s your job as their manager to show sufficient empathy and understanding about what else might be impacting them at work.</p><p>Struggles outside of work?<br>Frustrated with colleagues or with a lack of opportunity?</p><p>Can you meet with them privately and explore the real issues behind the negativity? Can you offer them coaching or even counselling, if the issues are more deep seated.</p><p>Manage people with compassion and you will generally get to the bottom of the issue and you could turn a toxic colleague into a deeply loyal one.</p><h3><strong>Double Check It’s Not You</strong></h3><p>You need to check your own biases first and understand if your managerial style and decision making is playing any role in their behaviour, particularly if their behaviour has changed whilst working with you and your team.<br>Could you be the cause of their discontent?</p><p>“A lot of times people will say someone’s negative, but my first question is, “So what does that mean?” — Stacey Gordon, Career Coach at <a href="https://www.themuse.com/coaching">The Muse</a>, “It could be that they’re behaving in a certain way that you may not approve of, but that doesn’t necessarily mean that they’re a destructive or bad employee. It just means that you haven’t properly defined standards with your team”</p><p>You also need to reflect on how you react to their behaviour and that you’re not making a bad problem worse.</p><p>We’ve all been there as managers as a combination of exasperation and stress leads to us becoming negative in response.</p><h3><strong>Time For Some Constructive Criticism?</strong></h3><p>Often they might be unaware of their impact on others or even the negative bubble they’ve got themselves into, particularly if the source of their troubles are external.</p><p>Delivering feedback is always challenging, particularly with difficult team members, so make sure it’s very specific about the issues that concern you.</p><p>You need to be able to deliver direct and honest feedback, within the framework of trying to help them, as well as you and your colleagues.</p><p>Situations like this are why it’s crucial to build a culture of trust and communication within your team, where critical conversations are handled skillfully and can take place without making a bad situation worse.</p><p>Don’t go hard with the negative, try to address this from a personal development perspective of understanding any issues and creating a measurable and clearly defined plan for them to engage again.</p><h3><strong>Talk Them Through The Impact</strong></h3><p>Obviously there can be situations where they are totally unresponsive to any gestures of empathy and constructive feedback.</p><p>You might need to alert them to what they could lose if this behaviour continues, this is not just about the immediate impact on their state of mind and team culture, but short term misbehaviour can have long term consequences and it’s the potential losses that sometimes stimulate changes in behaviour.</p><p>What really matters to them now, or in the past?<br>What could they be losing if they continue like this?</p><h3><strong>Regularly Check-In</strong></h3><p>If you can move forward positively then it’s important to maintain open channels of communication and for this not to be a one-off, short term fire fighting exercise.</p><p>It’s a huge drain on your time and distraction for the team to deal with these situations so you need to be clear about an ongoing programme of support that includes regular check-ins and time set aside to measure progress.</p><h3><strong>Where Necessary, Take Action</strong></h3><p>Alas there are limits to what you can offer and how much you can spend trying to manage this individual into a more positive space and not everyone will be capable or willing to change.</p><p>Research indicates that a small minority of people actually enjoy the power and disruption this kind of behaviour can bring.</p><p>If you have tried to help but they’re unwilling to change, act swiftly because every day their toxicity leaks into the team, is a day of diminished harmony, performance and potential loss of your star performers.</p><p>Who wants to spend their working day with Mr Grumpy?</p><h3><strong>Prepare For The Worst, Record Everything</strong></h3><p>If you do act swiftly and in particular if you decide to fire this individual, make sure you have recorded everything.</p><p>Most employment tribunal cases here in the UK are not lost because of the managerial decision made by the company, they are lost because the managers failed to follow the correct process.</p><p>If the relationship has moved into awkward mode then you need to be documenting clearly what has taken place and what steps you took to help.</p><p>You need to understand clearly your firing procedure and the employment legislation in your jurisdiction, to ensure you follow the correct process. This should be mapped out in a company manual and if not, add it now.</p><p>You need to establish a pattern of behaviour, the steps you too to address it and a detailed note of meetings, conversations, formal complaints that took place with this individual.</p><p>Protect yourself and your company against the risk of future litigation.</p><h3><strong>Start To Remove The Toxicity</strong></h3><p>In the meantime if they fail to change but have to remain, try to create space between them and the rest of your team. People having to work closely with a toxic team member are more likely to develop negative working habits also, either because of it or as a defensive mechanism against it.</p><p>You might need to create physical space or re-allocate them to different projects.</p><p>With the current WFH situations, it’s physically easier to create that space and reduce the number of clashes between this individual and team members, minimising the cognitive loss as a result.</p><p>Potentially other team members require help and coaching in how they can manage this individual, you certainly don’t want them getting a sense your time is being overly absorbed with managing the negativity.</p><h3><strong>Don’t Let Them Pull You In</strong></h3><p>Which leads me to conclude with the simple point that you have to manage yourself and your own time through these situations.</p><p>It’s very easy to be drawn into their negative orbit and be distracted from what else matters and your own peace of mind.</p><p>I return back to that moment on stage when you spot the individual with folded arms, focus instead on the vast majority of the audience who are wildly applauding and supportive.</p><p>Surround yourself with positive people, energy and situations that give you a positive charge — exercise, great food, good sleep. Staying healthy and proactive is crucial for your state of mind and you never know, might inspire that toxic colleague to step up or step out.</p><p><strong>CTO Academy Leadership Skills Programmes</strong><br>Visit our <a href="https://cto.academy/courses-pricing/">courses</a> and <a href="https://cto.academy/coaching/">coaching </a>pages to find out more about our leadership training and how to become more effective technology leader.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ee0cdf2a4fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Active Listening When Managing A Team]]></title>
            <link>https://andrew-69589.medium.com/active-listening-when-managing-a-team-ed93c545cecd?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed93c545cecd</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[active-listening]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 11:01:49 GMT</pubDate>
            <atom:updated>2021-03-01T11:01:49.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Active Listening How-To Guide" src="https://cdn-images-1.medium.com/max/1024/0*9zVRsXHDFUX_Bd65.jpg" /></figure><p>For today’s article, our author <a href="https://www.linkedin.com/in/fragouzoe/">Zoe Fragou</a> actively listened to all her tech-coachees when they told her they don’t know how to actively listen to their own team members.</p><p>However, they usually listen to her, which can only mean that active listening is not a skill, but most probably a matter of motivation: you are capable of listening to what you want to hear or insulate from whatever you don’t.</p><p>The problem is that more often you need to listen to things even if you are not in the mood too, because they might be important or they might be coming from a significant source. But even if that wasn’t the case, you wouldn’t really know it, since you didn’t really listen, did you?</p><p>Active listening is very different to hearing and it is what differentiates an effective leader from an average manager. While the first is always present in the moment, the other is usually not.</p><p>So before sharing some tips that will help you become a better listener, first we need to look at typical listening mistakes during a discussion.</p><ol><li><strong>You get distracted</strong></li></ol><p>At one point during the conversation, you start thinking about a bug in your code, or the film that you saw, or what you did last weekend. However, if you don’t suffer from ADHD (which in any case is very rare in adults), it means that you can self- regulate and actively choose to stay in the conversation.</p><p><strong>2. You start thinking of your answer before the other person has finished talking</strong></p><p>This is also very common. You choose one of the first points made by the other person and mentally start creating your response, losing all the following points being made that could differentiate your eventual response anyway.</p><p><strong>3. You think you know what the other person is going to say, therefore, you interrupt them</strong></p><p>You are so sure you know the other person (or every person), that you have pre- decided on their behalf what they’re going to say, and you interrupt them so you can answer upfront and save time. Even if you are right 9 out of 10 times, this tenth time it’s bluntly rude and not the approach a collaborative leader would take.</p><p><strong>4. You come to conclusions too soon</strong></p><p>Let’s say that someone is telling you a story. Too soon in the conversation, based on your instinct/ knowledge of the person/ what usually happens, you come to specific conclusions concerning who’s to blame, who’s the victim, what is the motive here etc. At that point, you stop processing all the data given, leading the other person towards your opinion of what happened, instead of actually trying to understand what is being said.</p><p><strong>5. You judge</strong></p><p>Virginia Johnson (the famous sexologist) was once asked how she feels when she hears weird things from her patients. Her answer was: “when a patient gets in my office and tells me he’s in love with a whale, I ask them how the whale feels about it”.</p><p>For a small person, a small problem is a big problem. You have the right not to engage, or you have the right to actively listen and try to help. The right you don’t have, is make the other person feel bad for sharing something with you.</p><p>Now that we’ve highlighted some of the common mistakes, let’s look at how you can improve, shall we?</p><p>The key, like I’ve already mentioned, is motivation: how much do you want to actually communicate with the other person? If you are serious about becoming a more active listener, the following tips are a good start:</p><ul><li><strong>Show empathy:</strong> Try to put yourself in the other person’s shoes while you are talking to them. How would you feel? Do you understand what they’re going through? Connect emotionally with what is being discussed, instead of trying to process it logically.</li><li><strong>Ask questions:</strong> Engage. The more questions you ask, the more focused you stay and the more details you acquire about what is being discussed.</li><li><strong>Never interrupt:</strong> It is the most impolite thing and the most problematic in a communication as well. Let the other person fully complete their thoughts and then start answering. If you believe the other person needs to improve their communication and perhaps make it more concise, then deal with that in a feedback environment separately.</li><li><strong>It’s ok to ask for some time</strong>: Telling someone “I can’t talk right now, I apologize, but my head is on something else, can we please discuss in a while?”, is not a bad thing. It shows self-awareness, respect, and confidence. If you are not in a mood because you are distracted, it is better to acknowledge it and reschedule than start a discussion that might lead to the other person feeling disrespected or undervalued.</li><li><strong>Not every conversation is about feedback:</strong> The fact that someone is talking to you, does not necessarily mean that you need to answer something back. Sometimes, you just need to listen carefully, without expressing an opinion afterwards. People talk for many reasons: get something off their chest, give information, interact. Not sharing your thoughts can be a very active decision, instead of a passive behavior. Also, not everything needs to be addressed on the spot. If you don’t feel ready to give an answer because you need more time to actively process what you’ve listened to, you can always say: “I need some time to think about it and I will let you know how I see it”.</li></ul><p>Last but not least, I still haven’t mentioned the reasons for being an active listener.</p><p>The obvious part is it’s the right thing to do, the best for business, the best for your team and your employees/ colleagues whose voices need to be heard.</p><p>The least obvious part is that it’s the easiest way for self-growth. You can learn from everyone. Every single person has at least one thing to share with you that you didn’t already know about.</p><p>Instead of focusing on what you do know, try searching for the elements that you don’t. Each person is a unique world with perspectives you can’t second guess or even imagine.</p><p>Embrace this fact, connect, and you will live more than one life.</p><p>Isn’t this an extraordinary possibility?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed93c545cecd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top ten things to look at to get remote working, working.]]></title>
            <link>https://andrew-69589.medium.com/top-ten-things-to-look-at-to-get-remote-working-working-24647395a43?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/24647395a43</guid>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Fri, 26 Feb 2021 12:41:54 GMT</pubDate>
            <atom:updated>2021-02-26T12:41:54.145Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Remote working and its challenges" src="https://cdn-images-1.medium.com/max/312/1*qfMid5j3_uTkpO7jq1MXYA.jpeg" /></figure><p>We’re lucky at CTO Academy to work with tech leadership coaches around the world and this week we’ve got a great article from <a href="https://www.linkedin.com/in/owenmevans/">Owen Evans</a> based down in New Zealand which looks into what can go wrong with remote working, and how to make it right.</p><p>“A lot of us have spent 2020 adapting to the new normal and a lot of us have found remote working for the first time. I’ve been there for a few years and worked in organisations that have embraced remote first mentality before it was cool required by a pandemic. Here are the top ten things my teams work on when working remotely ….</p><h3>1. Learn to write</h3><p>One of the core competencies of teams working well remotely is being able to write well and persuasively. You need to rely on ideas and information purchasing through the organisation without relying on cooler chats and coffees, or serendipitous meetings.</p><p>But the amazing positive from the whole organisation writing things down to communicate is there’s a great breadcrumb style trail of how decisions got made. Everything is easily recorded and archivable as it’s already in written form.</p><p>Get used to how to get ideas from genesis to development in a written form, work on brainstorming in the open, writing down half formed ideas and opening them up to collaboration.</p><h3>2. Embrace Asynchronous Decisions</h3><p>This leads from good written communication, but when you’re remote working you can’t always be 100% cognisant of all the distractions everyone else is going through. As such communication should be on a more asynchronous nature. Ask yourself if you need an answer to that question now, or just need an answer. Do you have other tasks you can work on while you wait, is the urgency you feel just your own psyche playing out. If you can embrace asynchronous decision making you can open yourself to moving many things forward at once, including more diversity in decision making (a lot of people need more thought than you might realise to make a good case for their thoughts on decisions and as such get crowded out of realtime, meeting based, decisions)</p><h3>3. Set clear goals</h3><p>Clarity of goal making is one thing that sets productive teams apart from those that aren’t. with remote working you can’t rely on a carrot and stick mentality and force people to align to certain work, you have to be clear about what good looks like for their own output so they can make decisions themselves.</p><p>Team owned OKRs work well (as long as the team gets to make them and buy into them themselves) and invest in data driven dashboards. Also make sure there’s someone accountable for setting and reviewing goals for the team (in an engineering team this should be a primary function of the engineering manager)</p><h3>4. 1 on 1 meetings for growth</h3><p>Remote work can feel disconnected from an organisation. You need to work hard to reconnect individuals to a whole. It’s also a reinforcer for the idea that you need to repeat a message 4 times to ensure everyone’s heard it. Make sure your managers are empowered and trained in good 1 on 1 practice, that they’ve understood how to grow teams and team members and are able to convey messages from their own managers to their team.</p><h3>5. Repeat the message</h3><p>This is stated above but worthy of it’s own point. If you’ve read the seminal parable “five dysfunctions of a team” you’ll know that your primary team is not the team you manage but the team of fellow managers around the organisation. Your role is to help disseminate information to the team you manage alongside this group. Repeat messages many times. Lean on tools like <a href="https://allhands.app/">All Hands</a> to get a core message across to a wider organisation without it having to be in realtime. Repeat, repeat, repeat.</p><h3>6. Agenda is key to a productive meeting</h3><p>On top of 1 on 1s remote work tends to overload people with meetings when a company first switches to remote work, if you haven’t embraced asynchronous decisions yet you end up overly worrying about check ins and catch ups on projects, you fill people’s calendars with Zoom meetings and burn everyone out.</p><p>Instead you should set the challenge that if you can’t set a meeting agenda then the meeting shouldn’t happen. You should default to shorter time and add follow ups if they’re needed (they rarely are). Embrace optional attendants and make it clear your letting them know the meeting is happening but not expecting them there. People will burn out if you let them or inundate them with meetings so stop it.</p><h3>7. Remote working is not working from home</h3><p>OK so the pandemic is slightly different, but usually remote working is not actually working from home. I vary my schedule to make sure I can work from Cafe’s or co-working spaces or the beach (it’s summer here is a write this so I’m looking longingly at the sea). The real reward for good remote working is that it can be “work from anywhere”. The only caveat to that I have is that time zones are still hard, and I don’t have a fix for that sorry.</p><h3>8. Be OK with not being OK</h3><p>It’s important to allow people to bring themselves to work, their real selves. Remote working breaks down a bunch of the usual barriers to work vs home life and it can be a real struggle for some. You also don’t get all the social queues that people might be struggling unless you give them space to make sure it’s ok to express it. As such you should model this vulnerability from the top. I try and coach CTOs or mangers to occasionally admit when they’re lacking motivation and be ok with it. Admit that the sun is shining and they want to go get an ice cream, or they have kids that just need them for a couple of hours and so need to check out. If you don’t admit this from the top down, no one will feel safe to express these things</p><h3>9. Celebrate the wins</h3><p>Sometimes you don’t get to celebrate or see the wins as well as you would in an office, you don’t see a cake turn up or donuts or everyone wearing silly hats. I make sure I take time for frivolity and celebration within the teams I manage, silly hat Friday’s, making sure people take time out to have a dinner if the team has done well, enjoy a well earned break if the team has been crunching through a project a bit. It’s more important than ever to celebrate every win you get as a team as it can help break the isolation</p><h3>10. Trust the process</h3><p>Getting a team used to all these things takes time, there are going to be road bumps along the way. Trust your team, trust in those who you’ve hired to do a job, trust that you’ve got this. It’ll take time to be smooth but the payoff is amazing”</p><h3>CTO Academy Leadership Coaching</h3><p>If you’re interested in finding out more about CTO Academy leadership skills training and indeed, about getting coaching from Owen and the team, have a look at our <a href="https://cto.academy/">website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24647395a43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What type of leader are you — Emotionally Intelligent or a Dark Triad?]]></title>
            <link>https://andrew-69589.medium.com/what-type-of-leader-are-you-emotionally-intelligent-or-a-dark-triad-bd41dffa8a2f?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd41dffa8a2f</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[emotional-intelligence]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[organizational-psychology]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Thu, 25 Feb 2021 08:10:48 GMT</pubDate>
            <atom:updated>2021-02-25T08:10:48.302Z</atom:updated>
            <content:encoded><![CDATA[<h3>What type of leader are you — Emotionally Intelligent or a Dark Triad?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/0*SOqv7rgMrzbupzAm.png" /></figure><p>Emotional intelligence (“EQ”) in the workspace is a leadership topic and conversation that become particularly hot in recent years but which some technology leaders struggle with.</p><p>But what exactly is emotional intelligence and why does it come so high up the list of key attributes for effective technology leaders?</p><p>Most people will tell you it’s the ability to ‘step into the other person’s shoes’ and to show empathy for their situation. That’s partially true. Empathy is one of the core skills embedded in the EQ skillset. However, it is not the only one.</p><p><a href="https://www.danielgoleman.info/">Daniel Goleman</a>, one of the most dedicated writers around the concept of emotional intelligence, defines it as:</p><p><em>“the ability to perceive emotions, to access and generate emotions so as to assist thought, to understand emotions and </em><strong><em>emotional</em></strong><em> knowledge, and to reflectively regulate emotions so as to promote </em><strong><em>emotional</em></strong><em> and intellectual growth.”</em></p><p>To distill this down into four key dimensions;</p><ul><li>How well I understand myself and my emotions</li><li>How well I understand other people’s emotions</li><li>How well I control myself</li><li>How well I control the environment and manage relationships</li></ul><p>When you consider these four attributes one can easily understand the importance of emotional intelligence in the workplace, and especially its connection with effective leadership.</p><p><strong>EQ leaders</strong> are the ones able to proactively anticipate and mitigate against team burnout, the ones that will voluntarily promote and mentor key people without feeling threatened and who want to help their team reach its maximum potentiality and to flourish inside and outside the organisation.</p><p>However… if we were to ask now if an emotionally intelligent leader naturally = better leader and here we define ‘better leader’ in terms of productivity and deliverables?</p><p>While an emotionally intelligent leader is clearly better for organisational wellbeing and bonhomie, does it mean they are necessarily more productive and effective as well?</p><p>There has been significant research into the subject with conclusions emerging that you might find surprising vs. standard expectations;</p><ul><li>Job satisfaction doesn’t always correlate with job performance</li></ul><p>I know. It is hard to believe. After all these years of training in positive psychology, team building and happiness in the workspace, research has concluded that a happier employee does not always mean a more productive employee.</p><ul><li>Emotional Intelligence doesn’t always correlate with job performance either</li></ul><p>Meaning, a person can be emotionally very intelligent and still underperform.</p><p>Moreover, it seems that where there’s yin — there’s also yang.</p><p>Where there’s light, there’s also darkness.</p><p>Because on the opposite side of the EQ leaders we have the dark triad of leadership and three traits that are so often acquainted with each other that they create what we call in statistics: <em>a factor</em> (imagine a package deal of traits!).</p><p><strong>Welcome to our dark friends …. Narcissism, Psychopathy and Machiavellianism</strong></p><p><em>Narcissism</em> is characterised by grandiosity, pride, egotism, and a lack of empathy.</p><p>The narcissist always demotes other people and thinks they are the best. In contrast to the other dark traits, narcissists most of the time have some emotional intelligence which allows them to manipulate, control and abuse others emotionally towards their benefit.</p><p>Also, while the common belief is that narcissists actually have low confidence, don’t bet on that. The difference between a narcissist and a really confident person, is that the narcissist always compares themselves with others, deeply believing they’re better, worth more and deserve it all.</p><p><em>Psychopathy</em> is characterised by continuous antisocial behaviour, impulsivity, selfishness, callous and unemotional traits and remorselessness.</p><p>Psychopathy is a gene; therefore, a person can be born with a predisposition for psychopathic behaviours. Depending on the environment of their upbringing, this person might manifest these behaviours clearly or hide them inside socially accepted contexts, for example, aggression during sports.</p><p><em>Machiavellianism</em> is characterised by manipulation and exploitation of others, an absence of morality, unemotional callousness, and a higher level of self-interest.</p><p>The term comes from the Italian philosopher Machiavelli who wrote the book ‘<em>The Prince</em>’ and whose motto was the famous quote: <em>the end justifies the means</em>.</p><p>While Machiavellianism resembles psychopathy, it’s not genetically inherited, but a matter of choice and mindset.</p><p>This means that while the person could be different, they actively choose to be Machiavellian.</p><p>It is very intriguing to try and change someone like this when you meet them, since these people are often highly seductive; my advice however is, don’t. If someone actively chooses to be a Machiavellian, that’s not a sign that you can help them, that’s a sign to run like the wind!</p><p>The <strong>dark triad leaders</strong> are most of the time highly productive, results–orientated and very career- focused. They thrive in competitive fast environments, especially when there are objective job evaluation criteria. Their management style can be pacesetting at the best, commanding at the worst.</p><p>And now, time for the big question:</p><p>Assuming that your leadership character is still forming, what would you choose?</p><p>To be an empathetic leader with democratic management style or a dark triad leader who is certainly effective and is climbing fast the career ladder?</p><p>The truth is that both types of leaders can thrive or fail. We have seen both.</p><p>But if your focus is about generating healthy, long-term relationships, based on respect and appreciation, then there is only one option.</p><p>While research has shown that job satisfaction does not always correlate with great performance, meaning employees do not always have to be happy to be productive, it does correlate with:</p><ul><li><strong>Retention</strong> (staying in a job)</li><li><strong>Low absenteeism </strong>(the rate for unjustified missing days)</li><li><strong>Work commitment </strong>(the loyalty that makes you overdeliver)</li></ul><p>That means that while your employees could be miserable and still meet all the expectations, if you want to keep them in the long run, if you want them to show up for work every day and be passionate to achieve all company goals…. They need to be happy as well.</p><p>Therefore, even if despite all the pressure you put them under someone in the team still manages to achieve an impact, then at one point either this person will suffer from burn–out or walk out.</p><p>Unfortunately, we live in a political and cultural environment where aggressive leadership qualities are sometimes able to prosper, but it’s generally only in short bursts because in the end you have to bring people with you. Enabling work–life balance and a healthy corporate culture is not a theory anymore, it’s what we all need and the more the years pass, the less tolerance we’ll be showing towards abusive behaviours, no matter how much talent exists to counterbalance them… so choose your character wisely.</p><p>Find out more about how <a href="https://cto.academy/">CTO Academy</a> can help with your leadership skills and effectiveness.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd41dffa8a2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning To Learn From Failure]]></title>
            <link>https://andrew-69589.medium.com/learning-to-learn-from-failure-bf9392ac063e?source=rss-4af0a760ec34------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf9392ac063e</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[coaching-skills]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <dc:creator><![CDATA[CTO Academy]]></dc:creator>
            <pubDate>Wed, 24 Feb 2021 13:05:43 GMT</pubDate>
            <atom:updated>2021-02-24T13:05:43.771Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/241/0*Zv976EvfUAdb6dgN.jpg" /></figure><p><strong>“Success is stumbling from failure to failure without any loss of enthusiasm” — Winston Churchill</strong></p><p>It’s always easy to see people at the top of their tech career or sporting discipline, where they make success look “relatively” straight forward, and presume it’s been a gilded path to the top but of course, it never is.</p><p>Skill, mindset, luck, application are all key ingredients but perhaps the one that cuts a consistent thread through all of those at the top, is their ability to absorb failure as just another learning channel and a fundamental to helping you grow an effective skill set in your chosen path.</p><p>I was reminded of this at home recently when introduced for the first time in my life to the skipping rope!</p><p><strong>Getting hit on the head by my Jump rope</strong></p><p>Like many others one of my new year resolutions is to stay fit and part of my plan was to start using a skipping or jump rope!</p><p>“How hard would that be?” as I pressed buy now on Amazon. I could not have been more wrong.</p><p>My first few attempts were a complete fail and I was quickly thinking about returning the rope until my 12 year old son picks up the rope and goes straight into a boxers skip as if it were the most natural thing in the world (how many of us suffer similar humbling experiences with our kids?)</p><p>That’s all the motivation I needed to persevere.</p><p>Fast forward to mid January and I am still absolutely terrible but each time I fail and the rope hits my feet, legs or quite often, the back of my head, I feel more determined not to give up, to keep persevering and to watch another 2 hours of YouTube videos on skipping technique.</p><p><strong>So what??</strong></p><p>Well this experience inspired this article.</p><p>As the rope hit my head for what felt the Nth time this morning and I let out a small scream of frustration whilst resetting the rope again, I released that learning to jump rope has a lot of synergies to my life at work as a CTO.</p><p>My working environment is (and TBH always has been) about constantly absorbing failures and learning from them… so instead of the rope hitting my head it might be some code failing a unit test for the fifth time, or a document you have spent all week writing being ripped to shreds by your executive team mates.</p><p>What do we, as leaders, do in these times of failure; we stop, take stock of the feedback and quickly adapt based on the learning. As technology leaders we have got to a place in our careers where we can do much of this naturally and instinctively, and therefore quickly. We have found our own tools that allow us to remember the context of what we were trying to do, pick apart the feedback (be it from the unit test or the redline/comments in the doc) and then translate that into change or adaptation of what we were trying to do.</p><p>If you’re like me then you still let out a small scream when something hits the buffers, but I have trained myself, through experience, where I can negotiate those negative emotions and small setbacks, transforming them into the energy and processes to move on with what I was trying to do.</p><p>And hopefully muscle memory retains that experience and feedback for next time (though I do recommend sometimes making a note of particular incidents and solutions) to help you avoid or minimise the risk of something similar happening again. The British cycling team once achieved huge global success but making tiny adjustments and improvements they called ‘The Aggregation of Marginal Gains’ — a philosophy I aspire to achieving with my performance and that of my team.</p><p>Personally I love a working environment which uses feedback loops and the ability to learn from mistakes and self improve. I get a huge kick out of it now.</p><p>I have also been very fortunate in my career to have great leaders and mentors who provided me the feedback and philosophy to take the hits but continue to move forward.</p><p>The effective coaches never shied away from telling me the hard truths and to adopt the growth mindset.</p><p>From past COO’s, CFO’s, NED’s to members of my past and current team, I have got to a place where I try to learn from everyone and everything around me.</p><p><strong>Our responsibility as leaders</strong></p><p>This then takes me to the role and responsibility we have as tech leaders or managers.</p><p>If what I’ve said is important to you (and hopefully it is) and you find yourself talking to your teams about “failing fast”, “failing forward”, “resilience” etc. It is your job to provide the systems, process and tools to enable your team with the feedback loops and confidence to learn and improve.</p><p>It doesn’t really matter how big or mature your team may be, as a leader and manager of people we need to set them up to win. This means that when they fail, we need to be there to help them get up, dusted off and in a position to move on.</p><p>In very early start-ups when you can feel the breath of your colleague in the chair next to you this can be as simple as an arm around the shoulder and a quick round of pair programming.</p><p>But there should be learning for you as well because when things do fail you may need to look at putting in more formal steps to help guide the process</p><p><strong>Culture is Key</strong></p><p>Create an environment and a culture where everyone feels safe to fail. Now you have probably heard or read this hundreds of times, but what does it mean?</p><p>Simply make sure your team knows that it’s OK to fail.</p><p>Make sure they truly understand they are not going to get fired or a 10 minute rendition from the urban dictionary flying at them.</p><p>Re-enforce to the team that failing is OK as long as it’s followed up with transparency, honesty and learning</p><p>Culture starts at the top so you need to lead by example. Be open with the team when you fail and what kind of remedy and process you use to learn from it.</p><p>I will often publicly detail my failures in our Tech team meeting. I go through my errors and what I did about it.</p><p>This didn’t happen overnight. I used to think this would show me to be a weak leader but it’s actually the opposite and the team has always appreciated this element of my leadership.</p><p>This is most evident when you get the team putting their hands up on mistakes and watching their teammates swarm the issue… no better feeling as a manager than seeing that swarm.</p><p>I also make a point to raise the other failures happening around the business. I will talk to my team about situations that are happening that they may not be aware of and then show them what as a business we are doing (or did) to address a particular issue. I believe it is super important that your team has visibility of what’s happening elsewhere in the business, particularly if it could have a direct impact on their work and career.</p><p><strong>Everything Needs Process</strong></p><p>Like every techie I love process and these are 3 simple steps to help support a culture of how to manage the learning process from setbacks;</p><ol><li>Pull the Andon cord (https://www.sixsigmadaily.com/what-is-an-andon-cord/). Create a virtual Andon cord. Make it OK for the team to stop everyone working and get the help and support they need. This could be as simple as a message in your team Slack or Teams channel, or a quick phone call to your manager, but raise the issue and get others to go and support the person that needs help</li><li>Review incidents and have an incident process. For many start-ups you will think this is overkill. But by having a very simple process that allows incidents to be managed and communicated will mean your team have a support system to fix an issue and it will mean that management have a way of getting updates on an issue, without sitting on top of the engineer that is trying to fix something</li><li>Use the 5 whys process after an issue has occurred (<a href="https://buffer.com/resources/5-whys-process/">https://buffer.com/resources/5-whys-process/</a>). It does not matter if the issue was a failure in production, or a problem with a process that creates lots of manual work, running an open and honest 5 whys session will always help you discover some of the underlying issues. I love this process and I am a huge champion of it, but that does not mean I want to fix everything that we uncover. Typically at the end of the a 5 whys session, we only look to ‘fix’ 30–40% of what we discover. This may not sound a lot, but the difference it makes and the ongoing gains you get is huge.</li></ol><p><strong>Final thoughts</strong></p><p>Building the culture and resilience where it is OK to fail for you and your team is hard and it takes time.</p><p>Failing is essentially a real time training that helps you become more resilient and effective as a team, but like all training it’s an ongoing process and you will have many ups and downs as a leader to understand the nuances of how, when and where the manage failure.</p><p>From my experience the key takeaways …</p><ol><li>Be open about failures</li><li>Put in systems and process to be the framework as failures occur</li><li>Be the support system for your team to learn and move forward</li><li>Find your own support system, so you can better help your team</li><li>Find a coach for you and key employees, who can provide a sounding board for how to manage this process.</li></ol><p>Next for me, is to watch another 2 hours of YouTube videos on jump rope 😉</p><p>_________________________________________________________________</p><p>Visit our <a href="https://cto.academy/corporate/">corporate page</a> for more information or get in touch with our CEO to find out more andrew@cto.academy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf9392ac063e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>