<?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 Eleanor Mocchetti on Medium]]></title>
        <description><![CDATA[Stories by Eleanor Mocchetti on Medium]]></description>
        <link>https://medium.com/@ElsWebs?source=rss-ece4c84fac1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iDkSaQMa4vqcjjXd4i3mdg.jpeg</url>
            <title>Stories by Eleanor Mocchetti on Medium</title>
            <link>https://medium.com/@ElsWebs?source=rss-ece4c84fac1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:56:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ElsWebs/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[Product Vs Delivery — A modal that can cause a whole lot of pain]]></title>
            <link>https://medium.com/@ElsWebs/product-vs-delivery-a-modal-that-can-cause-a-whole-lot-of-pain-7af29f4635c2?source=rss-ece4c84fac1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7af29f4635c2</guid>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[delivery]]></category>
            <dc:creator><![CDATA[Eleanor Mocchetti]]></dc:creator>
            <pubDate>Mon, 03 Feb 2020 21:59:37 GMT</pubDate>
            <atom:updated>2020-07-31T12:23:21.321Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Vs Delivery — How separating responsibilities can have disastrous consequences.</h3><p>Have you ever been in a company where you have a product team responsible for how the product should work and make money, and a tech/delivery team responsible for delivery and quality? Ever noticed how this can cause problems?</p><p>It is reasonably common practice in large organisations to have this setup, with a product function feeding up to the business or a product department, and a separate tech function feeding up to tech/delivery. The problem with this method is that it creates a situation where there are competing objectives and motivations that cause us a whole lot of pain.</p><h3>The Scenario</h3><p>We’ve all seen it — a Product Owner who wants the world. Perhaps they don’t want to discuss an ‘MVP’ or prioritise the work. It might come across as ‘we need it all and I don’t care how you build it’. Perhaps you have a product owner who is used to putting pressure onto a development team to ‘get results’.</p><p>On the other hand you have a delivery person, or perhaps the tech team who spend their whole time pushing back. From the business’s perspective the estimates might seem huge, ‘how can a simple website take that long to build?’. Or maybe when they have delivered all the requested features the quality is terrible and there are so many bugs the system shouldn’t have been released at all.</p><p><strong>Sound familiar?</strong></p><p>So I’m going to break down how this can happen from a basic emotional intelligence viewpoint… How having two departments with distinctly different motivations kills a project. I will concentrate on the planning phase, but this affects the whole project life-cycle.</p><h3><strong>Delivery/Tech’s Chimp world</strong></h3><p>(Delivery/Tech often separate disciplines and motivations but in this article I will lump them together for simplicity).</p><p>Delivery/tech is generally under pressure to hit a deadline within a certain cost, having to meet business prescribed timelines. If there are bugs in the system, delivery and tech are also responsible for this.</p><p>A general fear in delivery then, following from these motivations, is not hitting the deadline (and being blamed for this).</p><p>Additionally, tech are worried that there are issues with the technical quality of a product when built. Or that the technical solution is in some way not appropriate. The last thing a developer wants is to have his professional integrity questioned. Most teams working in an environment like this will have seen their tech requirements de-prioritised by product in favour of features, only to release a product that is not functioning properly. Leaving tech to blame.</p><p>Lastly, Tech departments are often left supporting products that were rushed out and so are very difficult to maintain. They fear the knowledge that rushing to completion now will cause them years of pain as they try and unpicked bad code for years to come.</p><p><strong>What actions does this drive?</strong></p><p>If tech/delivery are told to deliver to a certain date, they may feel they have to plan around that date, rather than looking at what’s feasibly possible. This can lead to a project running over considerably, as the reality of development speed becomes apparent, or it can lead to a product being released that doesn’t work properly as it’s rushed out.</p><p>Another approach would be for delivery to push hard to get the backlog prioritised and some work simplified or de-scoped.</p><p>Tech will be concentrating on how to get the right technical solution and reduce risks of bugs hitting production. They want a fail safe system so technical issues aren’t laid at their door.</p><h3><strong>Product’s Chimp World</strong></h3><p>Product may have KPI’s that link to the product’s performance mainly about how much money that product makes for the business. If they don’t have these, then their product is likely needed to impress the senior stakeholders in the business, in some scenarios this can translate to — it needs to look good. (This may sound over simplistic, but I have seen this play out, and there is a lot of evidence to suggest that most businesses still make their decisions from the <a href="https://www.productplan.com/defend-product-roadmap/">HIPPO affect</a>, rather than provable stats).</p><p>Often they have invested a huge amount of time in the UX phase of a project and have a lot of emotional investment over how the end product should look.</p><p>On top of these motivations, Product Owners may have seen projects where after the first release the budget is dropped, and they never get to a release that is genuinely going to succeed as a fully fledged product. This can be exacerbated by IT projects often taking longer than originally anticipated.</p><p>So for product owners, the fear is that a product is released that doesn’t have enough features. They could also be additionally fearful that they only get one chance at release, and that they loose their budget after the first attempt. If they hit the release and all the features are in, but there are loads of bugs, they won’t normally get a lot of the blame.</p><p><strong>What actions does this drive for product?</strong></p><p>This makes product more interested in pushing to get their full vision achieved first time round. The idea of prioritisation can translate to choosing functionality that may never get delivered. And simplifying functionality can seem counter intuitive to the Product Owner’s own interests. They often also prioritise the product features over technical enablers or fixing bugs and code quality.</p><h3><strong>A Calamity Put Together</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D-FUelp4PNXScpgoH7NVsA.jpeg" /></figure><p>When you put these very distinct departments in a room to come up with a project plan what do you get?</p><p>If you are lucky, and you have a great working culture, people who put their personal objectives to one side, or if your organisation has very deep pockets, then you might be in with a chance. But in the real world you can get a project plan that is far larger than the business can afford.</p><p>The simplest idea can become massive, there might be a specifically complex user experience that requires changes to the APIs, the APIs then need extra automated tests to hit tech’s targets of quality, the team then add some extra time on top to allow for the fact that it needs tweaking a few times before it is signed off from a product perspective. Add in a specific new tech stack that the tech department have bought a new licence for and implement as company policy. Add into the mix massive amounts of ‘tech debt’ from the previous project that has never been prioritised as this doesn’t hit any of the Product Owner’s objectives, and the project has grown to an inconceivable size.</p><p>This massive project plan is then shown to a senior stakeholder, the senior stakeholder is shocked at the size, this just isn’t affordable! She sends it back to the team to look at again and get the cost and timelines down.</p><p>The development team look at their estimates. Each person in the room looks at the project plan from their bubble. Product feel they need to de-scope, even though they aren’t asking for much and tech are just really slow, tech feel they need to implement a poorer technical solution, which will do them no favours in their careers, let alone once it’s out and they are never able to re-factor. And delivery want anything that takes less time to deliver.</p><p>The team might come back with a more bearable project size for the business, but it’s likely still too large.</p><p>In reality, this problem often first rears its head in planning. And the ask from a business at this point, ‘can the product owner and tech team sit in a room and come up with a better simpler solution’ feels completely reasonable. But the different motivations behind the teams can make this really difficult.</p><p>Thinking of simple solutions to hit a goal, means thinking of different user experiences, that not only work brilliantly for users, but that are also reasonably simple to implement to hit timelines and budget constraints. If you have a product owner and UX team vested in a specific approach these conversations can be impossible.</p><p>Thinking of simple solutions means getting the development team to understand the ‘why’ of each user-story. In this scenario the tech team is not vested in why they are building something, they are there to deliver what they are told to, and to high technical standards. Any out-the-box thinking to get the business to a more cost effective implementation often requires a really positive attitude and creative thinking. The scenario outlined has created the opposite to a positive environment.</p><p>In a worse case scenario, the team feel that they should just estimate smaller, and then the issue is pushed back to 6 months down the line, when only half of what was needed has been built, but all the money has been spent.</p><h3>So how do we fix this?</h3><p>How do you get product, tech and delivery all pulling in the same direction?</p><p>For me this is the core to a great development team. Get the team all working behind one goal. (As an organisation grows, this becomes a harder and harder problem to solve — whence you see this more and more in large organisations.)</p><p>Some initial suggestions:</p><ul><li>Hone your emotional intelligence skills. Have you ever been in a room where you can see this playing out? Take your own goals off the table for a minute and really try and think about everyone else’s motivations. It will help you navigate a better solution for all.</li><li>Team objectives — give product and tech the same team objectives.</li><li>Give the Product Owner objectives that include cost/delivery and tech quality.</li><li>Move product and delivery to be disciplines in the same department, although even this setup can still have the same problems if you don’t do it right. You’ll need to do this along with other techniques.</li><li>Agile product leadership techniques — a strong product owner can bring the development team on the journey of where we are going, bringing developers into designing the solution.</li><li>Cultural changes in the organisation — a difficult and often painful journey for larger organisations. This article concentrates on changing personal motivations rather than culture. However, cultural change on things like positive action, rather than blame can help.</li></ul><p>There are many more things that those of you working in a more mature agile environment will think of. Like moving away from big bang releases, releasing small and regularly so that there is no fear that the project will just stop after the first release.</p><p>Lastly, and worth noting in and of itself. There is a trend that does come through in organisations that struggle with this. These organisations tend to have a belief that you can have an ‘agile’ development team, and that the rest of the organisation doesn’t take on any core agile principles. For me, these organisations need to fundamentally look at how they structure the wider business, and also change the culture of the organisation. This is a widely discussed topic on how more and more businesses need to be built around technology, rather than seeing them as a resource.</p><p>I have written this as it is a theme I have seen echoed over lots of companies I have worked with. Some of those businesses have made strides forward in changing these ways of working for the better.</p><p>Some good reads related to some of these topics:</p><ul><li><a href="https://www.amazon.co.uk/s?k=the+chimp+paradox&amp;adgrpid=52586602309&amp;gclid=Cj0KCQiApt_xBRDxARIsAAMUMu_m80v0kJWLDGLn-YpBkjYPI5SXBlzp7JhrLIp-AhaJNOzGUVnOJ6QaAoPsEALw_wcB&amp;hvadid=259022408379&amp;hvdev=c&amp;hvlocphy=9045999&amp;hvnetw=g&amp;hvqmt=e&amp;hvrand=15658901135506883797&amp;hvtargid=aud-857382801982%3Akwd-300246666130&amp;hydadcr=24403_1748879&amp;tag=googhydr-21&amp;ref=pd_sl_546vp03fl3_e">The Chimp Paradox</a> by Dr Steve Peters</li><li><a href="https://www.amazon.co.uk/Emotional-Intelligence-Matter-More-Than/dp/0747528306/ref=sr_1_1?crid=36VLC4G8R7F2I&amp;keywords=emotional+intelligence&amp;qid=1580763709&amp;sprefix=emotional%2Caps%2C159&amp;sr=8-1">Emotional Intelligence</a> by Daniel Goleman</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7af29f4635c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to recruit more women into tech: My top tips + how I came by them]]></title>
            <link>https://medium.com/women-in-tech-not-just-code/how-to-recruit-more-women-into-tech-my-top-tips-how-i-came-by-them-c404a3238281?source=rss-ece4c84fac1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c404a3238281</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Eleanor Mocchetti]]></dc:creator>
            <pubDate>Mon, 11 Feb 2019 18:03:58 GMT</pubDate>
            <atom:updated>2019-02-12T13:19:58.642Z</atom:updated>
            <content:encoded><![CDATA[<p>I am so thrilled that our industry has finally woken up to the challenge ahead of us. But how the heck did we get to a position where only <a href="https://www.recruitment-international.co.uk/blog/2017/08/only-17-percent-of-employees-in-uk-tech-sector-are-women-research-reveals">17% of the tech workforce</a> are women? When we look at programmers this diminishes further, with some studies suggesting just <a href="https://www.forbes.com/sites/lorikozlowski/2012/03/22/women-in-tech-female-developers-by-the-numbers/#3a3603f71760">5–10% of software engineers are women</a>. And even worse than this, we got to a point where the idea of a woman being a programmer has become a bit of an oddity.</p><p>Having started in this very odd situation 10 or so years ago, I have had some personal experiences that have really made me evaluate how I myself perceive and recruit female engineers and tech positions in general. The now well-known idea that women don’t big themselves up so much on their CVs, that they don’t tend to apply for those more senior positions, is only really half the story. For me, there are many hidden reasons and circumstances that cause this, that are not necessarily due to women inherently not believing in themselves. We need to change the circumstances which create this situation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*11_akq3WNX3QGyRM1CGXGQ.jpeg" /></figure><h3><strong>Getting a tech job when you don’t quite fit the bill…</strong></h3><p>Earlier on in my career, as a female engineer, and to be fair not really one of the lads, I didn’t ever have a lot of programmer mates outside of work. So, when first looking at the contract market, I realise now that I had a lot less guidance on salary expectation than my colleagues who had friends in the industry.</p><p>So, when deciding my first contract day rate, I phoned a number of recruitment agencies, told them my skill-set and CV and asked them to suggest a reasonable rate. After being warned by a few of them not to exaggerate my skill-set, as a number of the recruiters felt it unlikely I’d completed the work I said I had, they all suggested a similar day rate and I interviewed and duly took one of these roles.</p><p>You know what’s coming next — I had been put in at an incredibly low day rate. After quickly being promoted to manage the team, I discovered I had not been considered for the original contract position as my rate was too low. The only reason I was given an interview at all was that the recruiting manager had found my CV and asked the recruitment agent why I wasn’t being considered. The recruitment agent’s answer? I simply hadn’t asked for enough money to fit the recruitment agent’s criteria for this role. Ironically, this was a decision they themselves had made for me.</p><p>This, and many similar experiences, have led me to understand that we need to aim to overcome these biases — biases around our own recruitment practices, but also things that happen well before the candidate even gets to us as recruitment managers. Fortunately, I am in a wonderful position to really change how I recruit, and get better developers as a result. Having a first-hand appreciation for some of the odd conversations and challenges women have in this industry, I can work to get those CVs that might not have otherwise been sent to me, assess them on a fair footing and try to remove any of the gender-prone stereotyping.</p><p>Having recruited a number of dev teams over the years, here is my personal checklist for great recruiting:</p><h3><strong>Top Tips</strong></h3><p><strong>Open up the role to anyone — no matter how little money they are asking for</strong></p><p>It is amazing how many times I have seen people flinch when they have been told a candidate is asking for dramatically less than the going rate, and they will often ask the inevitable question — ‘so what’s wrong with them?’. In my experience, for both men and women, salary expectation and true ability bear very little relation to each other. Just as much as confidence and competence correlate — they don’t.</p><p>The issue of salary expectation, like all the issues discussed here, is not a female-only issue, rather that some women may be affected a little more as a group. I have also noticed that candidates from less privileged backgrounds can sometimes ask for less than market rate, simply because they have a much lower expectation of what a ‘good’ salary is.</p><blockquote>“Removing these cultural biases is key to getting the best candidates for the job &amp; given the right environment all sorts of people and personalities can thrive.”</blockquote><p>And although I shouldn’t have to say it: always offer your candidates the appropriate value for the job they are doing. We benchmark our salaries to ensure that when I recruit I must give a fair salary to anyone I offer to.</p><p><strong>Meet the basic criteria</strong></p><p>In a similar vein to the above, insist on having all CVs sent to you that meet the basic criteria of capabilities. This is a Telegraph tech policy and it enables you to make a true call on abilities, and stops CVs being filtered out before they get to you, that may have some great but modest women in the ranks.</p><p>The key to this is to keep mentioning it to your HR or recruitment agency, explaining the motivation. These things can get hidden in HR policies and forgotten about; make sure it is a key part of the conversations you have when briefing in the role.</p><p><strong>Recruit more than one level at a time</strong></p><p>If on a large recruitment drive, try wherever possible to open positions up to more than one level. Women do tend to apply for (or be put forward for) the less senior roles, but, more than once, I have interviewed a woman for a lower role and, after tech testing and assessment, we have found them to be at the more senior level and given them the more senior position and salary.</p><p><strong>Competence vs confidence</strong></p><p>For me, some of my best employees over the years have truly been great, partly because they haven’t really realised how good they are. With this modest desire to do better can come great things.</p><p>Yes, we really need confident people in our organisation and those people can lead us and drive us through to success. But it is important for me to keep in mind that men are generally socialised into being slightly more dominant and outwardly confident in their communication style. It’s all about being a man, ‘manning up’ not being a ‘sissy’ etc etc.</p><p>On top of this, a lot of female coders may have experienced a lifetime of odd comments and surprised faces when saying that apparently bizarre statement of ‘I code’. You can quickly imagine how women in tech might not be so forthcoming with their confident techy side.</p><p>It is easy in an interview to see confidence as a reflection of ability. Don’t. Be mindful that given the right environment all sorts of people and personalities can thrive. And those teams are better, they work better together, they give each other that wonderful ‘<a href="https://hbr.org/2017/08/high-performing-teams-need-psychological-safety-heres-how-to-create-it">psychological safety</a>’ that Google has made so famous.</p><p>Be mindful of this and try and break through this initial veneer in an interview situation. Dig into what each candidate is saying and concentrate on the content.</p><p><strong>Work closely with your recruitment agent (if you use one)</strong></p><p>This seems to be an obvious one, but worth keeping in mind. This is all about working together to make sure you can do everything possible to open your roles up to people who might not otherwise have been considered.</p><p><strong>The end result</strong></p><p>If you follow these ideas and keep in mind that you need to keep a more open mind, I do think you can have more success in recruiting female engineers.</p><p>Now, be wary — do not give anyone a free pass because they tick a gender diversity checkbox. This is about finding great talent by including the great candidates that may have otherwise been overlooked. In my experience this approach can really make your team better, but only if it is done with good objective consideration and care.</p><p><em>Eleanor Hunt is the Head of Technology for Mobile Apps at The Telegraph. You can follow her</em><a href="https://elswebblog.wordpress.com/"><em> blog here</em></a><em> or follow her on </em><a href="https://twitter.com/EH10000"><em>Twitter</em></a><em> and </em><a href="https://www.linkedin.com/in/eleanor-hunt-aa4b4557/"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c404a3238281" width="1" height="1" alt=""><hr><p><a href="https://medium.com/women-in-tech-not-just-code/how-to-recruit-more-women-into-tech-my-top-tips-how-i-came-by-them-c404a3238281">How to recruit more women into tech: My top tips + how I came by them</a> was originally published in <a href="https://medium.com/women-in-tech-not-just-code">Women in Tech Not Just Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Women in tech: why we need more and how we can make it happen]]></title>
            <link>https://medium.com/the-telegraph-engineering/women-in-tech-why-we-need-more-and-how-we-can-make-it-happen-8818f4f21091?source=rss-ece4c84fac1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8818f4f21091</guid>
            <category><![CDATA[female-leadership]]></category>
            <category><![CDATA[websummit]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[gender-equality]]></category>
            <dc:creator><![CDATA[Eleanor Mocchetti]]></dc:creator>
            <pubDate>Wed, 15 Nov 2017 12:57:53 GMT</pubDate>
            <atom:updated>2023-02-18T20:53:15.803Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been fortunate enough to spend the last week at Web Summit, meeting and listening to some fascinating people. I was encouraged to go this year by the organisers’ massive discount (almost 90% off) for women in tech, which was put out to encourage more female attendees. Not only did they do this, but they also created a tech lounge and curated a full women in tech programme tailored to help with issues that women more commonly face.</p><p>Firstly, I have to say how great it was to see a company so proactively doing this sort of thing. I have been in the tech industry for 10 years and although I love working with my male counterparts, I am aware of why we need to encourage a more diverse workforce.</p><p>Women are heavily underrepresented in this industry; <a href="https://www.recruitment-international.co.uk/blog/2017/08/only-17-percent-of-employees-in-uk-tech-sector-are-women-research-reveals">only 17% of the UK tech workforce are women</a>, with that proportion dropping dramatically when it comes to leadership roles. The Telegraph has a number of brilliant, active programmes to help increase staff diversity, but is always looking at ways to improve.</p><h3>Why does it matter for business?</h3><p>There are some well-quoted studies which suggest<a href="http://www.catalyst.org/system/files/the_bottom_line_corporate_performance_and_women&#39;s_representation_on_boards_(2004-2008).pdf"> that gender equality at board level is linked to higher profits</a> within companies.</p><p>There are also many examples that demonstrate how having male-orientated teams can be problematic for the end user. A good case in point is early airbags. Built and tested by an all-male team, the first airbags were designed using the standard male as a test case.<a href="https://medium.com/women-in-tech/women-in-tech-the-missing-force-e4709f348610"> This had the tragic consequence that women and children were killed in early deployments</a>. There are many examples, with less obvious consequences, of this kind of situation. Arguably, we just don’t know how many different ideas and design approaches might come to light if we have more women adding to those conversations.</p><h3>What can we do about it?</h3><p>One of the main factors for underrepresentation in the industry is that so few women get involved from an early age. To counteract this, The Telegraph have set up a school scheme to try to change the perception of tech specifically at school age. Additionally to this, I wanted to outline some of the things we can do within companies to address some of the issues that women face once they enter the workforce.</p><h3>Yearly reviews</h3><p><a href="https://www.facebook.com/WebSummitHQ/videos/1595387883860583/">Blake Irving gave a great insight into some of the things they have been doing at GoDaddy</a> to improve diversity in leadership roles. Women don’t apply as often for promotions as men. Studies have shown they tend to wait until they have an average of 80% of the required experience. For men this experience level is much lower before they start reaching for the next step.</p><p>To overcome this and ensure that the best people got those leadership positions, GoDaddy started a mandatory review across all employees so that everyone was considered for a promotion, not only those requesting it. This had a great effect. The number of women given promotions went up by 30% whilst having no negative impact on men’s. This is a simple practice that we could all use to make sure we really are looking at equal opportunities and leveraging the best talent over the organisation.</p><h3>Workshops and mentoring schemes</h3><p>We saw some excellent workshops at Web Summit that were open not just to women, but were geared around issues women tend to face a little more often. For example, there is evidence that shows women tend to be less strong at negotiating salaries. This is likely to be one of the contributors to the gender pay gap. So Web Summit put on workshops specifically around how to negotiate when discussing salary.</p><p>Mentoring is widely talked about as a great way for people to learn, get advice and opening up opportunities. Mentoring is much more difficult for women to get on an informal basis when working in an all-male environment. Simply put, mentors tend to mentor people who are very similar to themselves and with whom they can have a neutral social relationship. Male to female mentoring is just less likely to organically happen. This can easily be remedied by companies being vocal and aware of this issue. Whether it be putting in more formal mentoring schemes, or just opening up that conversation for women looking for those sorts of relationships.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y_qJEljU4iAin6NkhbRHfw.jpeg" /></figure><h3>Networking geared towards women</h3><p>Personally, this is the most important thing for me and what I enjoyed most about Web Summit. The Telegraph has the most diverse tech department that I have worked in, and so I am lucky to enjoy working with a whole host of people who are all very professional and great to be around. But over the past ten years, at a number of companies, I have often been the only woman in the room. And although I haven’t thought about it day-to-day, I have noticed that it has changed my behaviour. Most importantly it has meant that I haven’t been as open to the networking opportunities as my male counterparts.</p><p>Discussing this with other female colleagues, this isn’t an uncommon situation. There comes a point in the evening when the drinks have been rolling, conversation turns, and the woman in the group feels uncomfortable. Or often she just doesn’t have as much in common with an all-male group of colleagues. So I, like many other women, tend to shy away from work socials and events.</p><p>So there really is a place for events where you can meet and socialise with women in tech. Again, this doesn’t have to be an all-female environment; even a more balanced gender divide can really change an event.</p><p>The Telegraph has a women in tech group which is a network of men and women there to encourage discussion and support over these sorts of issues. This is again a simple thing that any organisation can set up, and can really open up the conversation and support women who can sometimes feel more isolated in this industry.</p><h3>What next?</h3><p>The suggestions above are some great examples of practical things that we can do to help in this area. But it will take a long time to bring the industry to a more balanced gender distribution. For me, the most important thing is to open up the conversation. We need to make sure this isn’t seen as an anti-man rhetoric, but rather, looking objectively at what barriers to entry women have and how we can overcome them to make the industry more inclusive.</p><h3>Interested and want to learn more?</h3><p>A really popular book at the moment is Sheryl Sandberg’s <a href="https://leanin.org/book/">Lean in.</a> This is a fascinating read and covers all sorts of topics on how to encourage more female leaders.</p><p>There is a ted talk on <a href="https://medium.com/women-in-tech/women-in-tech-the-missing-force-e4709f348610">“Women In tech: The Missing Force”</a> by Kern Catlin. This talk includes the example of the poorly designed airbags.</p><p>You can find a great <a href="https://www.facebook.com/WebSummitHQ/videos/1595387883860583/">Web Summit discussion on diversity Blake Irving and Jane Martinson</a>.</p><p>There are also some great women in tech groups on<a href="https://www.meetup.com/"> meetup.com</a> if you are interested in networking opportunities and workshops.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8818f4f21091" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-telegraph-engineering/women-in-tech-why-we-need-more-and-how-we-can-make-it-happen-8818f4f21091">Women in tech: why we need more and how we can make it happen</a> was originally published in <a href="https://medium.com/the-telegraph-engineering">The Telegraph Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>