<?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 Melinda Seckington on Medium]]></title>
        <description><![CDATA[Stories by Melinda Seckington on Medium]]></description>
        <link>https://medium.com/@mseckington?source=rss-4c40e6b00775------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FyfAJiMAKOHLsc8s8QPL3g.jpeg</url>
            <title>Stories by Melinda Seckington on Medium</title>
            <link>https://medium.com/@mseckington?source=rss-4c40e6b00775------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:03:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mseckington/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[The Art of Communication Design: Define Your Goals]]></title>
            <link>https://medium.com/@mseckington/the-art-of-communication-design-define-your-goals-121b17146bd0?source=rss-4c40e6b00775------2</link>
            <guid isPermaLink="false">https://medium.com/p/121b17146bd0</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[internal-communications]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Melinda Seckington]]></dc:creator>
            <pubDate>Thu, 12 Oct 2023 11:14:41 GMT</pubDate>
            <atom:updated>2023-10-16T17:36:55.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mpm60kTeFC3_Ttk07v02fw.png" /></figure><p><strong>Last month I gave this talk at DevRelCon London. This blog post series is a slightly adapted version of my speaker notes, so that it’s split out across multiple posts and hopefully reads better as articles.</strong></p><p><strong>This is the 2nd post in the series.After you read this you might want to read the entire series:</strong></p><ul><li>Part 1: <a href="https://medium.com/@mseckington/the-art-of-communication-design-intro-54a822efab34"><strong>Intro</strong></a></li><li>Part 2: <a href="https://medium.com/@mseckington/the-art-of-communication-design-define-your-goals-121b17146bd0"><strong>Define Your Goals</strong></a></li><li>Part 3: <a href="https://medium.com/@mseckington/the-art-of-communication-design-identify-your-audience-76d8fe864a11"><strong>Identify Your Audience</strong></a></li></ul><p>Before doing anything else, your first step is to ask yourself: what is the main goal of your comms? What is the purpose of your comms?</p><p>Understanding what your goal is, will help frame all the next steps and will allow you to make sure that each part of the comms all contribute to that main goal.</p><p>This may seem like a given, but if you don’t take time to define this, that’s often when your comms can become messy, unfocused or unclear. Or what I’ve also seen is mixing up too many messages that aren’t really about the same thing.</p><p>Writing the goal down will also help team members all get on the same page and ensure that everyone has a shared understanding of what is being planned. I’ve had a few times before where we all thought we were doing something for the same reason, only to discover that wasn’t the case. Start with writing out a goal to ensure you’re all moving in the same direction for the same reasons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RidpyiGXC8hMSxWqJNHj4A.png" /></figure><p>So first exercise: write down in a one-liner your main goal of what you want to do. Why are you planning on communicating something in the first place?</p><p>Also think about whether there are secondary objectives. This will also help clarify whether it’s something that actually belongs and fits in with the main comms or whether it is something different.</p><blockquote><strong>Examples:</strong></blockquote><blockquote>“To inform community members that we’ll be sunsetting a service.”</blockquote><blockquote>“To announce a new process for performance reviews.”</blockquote><blockquote>“To convince people to come to our hackathon.”</blockquote><blockquote>“To let teams know that the company strategy has changed and that budget has been cut.”</blockquote><p>So here are a couple of examples to show how you might phrase your goal. They’re all simple one liners about the goal of the comms.</p><p>The next step is asking: what are those comms trying to achieve? This may seem like the same question as the previous one, but what we want to do here is to determine what the effect of the comms will be.</p><p>One way I like looking at this is to start with this concept from Stephan McGarvey:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qk0KWgMx-vTi7cvxA5XA4Q.jpeg" /></figure><p>At the start of your comms, your audience will be in a certain current state and by the end of it you want them in a specific desired state.</p><p>What effect will your comms have had? This is about defining the desired outcomes. What is the angle of the message you’re trying to get across?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RFNe2umfLhQqxBMFO1908w.png" /></figure><p>So the next exercise is defining the desired outcomes. What effect will your comms have had? What angle should your messaging focus on?</p><p>So again here are a couple of contrived examples:</p><blockquote><strong>Examples:</strong></blockquote><blockquote>“For users to migrate to the new service.”</blockquote><blockquote>“For users not to get angry about the old service sunsetting.”</blockquote><blockquote>“For everyone to understand what the new performance review process is.”</blockquote><blockquote>“For community members to sign up for our hackathon.”</blockquote><blockquote>“For teams to understand what changes are being made within the company.”</blockquote><p>The key here is defining what actual effect the comms will have had. In a way, it’s looking at what you’re going to measure to understand whether your comms were actually successful? What truly matters here for you? This will allow you to be more deliberate and focus on what matters the most.</p><p>Let’s take a closer look at that first example: the goal there was <em>“To inform community members that we’ll be sunsetting a service”</em>, while two possible outcomes could be <em>“For users to migrate to the new service”</em> or <em>“For users not to get angry about the old service sunsetting”</em>. You may want to prioritise both of these outcomes, but maybe one of them is more important to you. This will effect how you design all the next steps and how you shape your final messaging.</p><p>This is also where you can align your outcomes with your team goals or objectives or OKRs, especially if you have something that needs to be measured. Like the example above, you can also have several outcomes for your comms outcomes. But: be careful with trying to do too much with one thing. Sometimes different outcomes will complement each other nicely, but it can happen that they are conflicting messages that may end up being only more confusing.</p><p>You might also be tempted to immediately go into detail here, and define specifics of specific pieces of communication, but right now in this exercise, we want to remain high level. There will be more exercises coming up where we dive into the details.</p><p>And that’s the first step: define your goals and outcomes. Just doing this will already help you start thinking more intentionally of what you’re trying to achieve with your comms.</p><p>Continue on for the next step:<strong> </strong><a href="https://medium.com/@mseckington/the-art-of-communication-design-identify-your-audience-76d8fe864a11"><strong>Identify Your Audience</strong></a>. In this post we’ll be looking at understanding who your target audiences are.</p><p><strong>This blog post is part of The Art of Communication Design series:</strong></p><ul><li>Part 1: <a href="https://medium.com/@mseckington/the-art-of-communication-design-intro-54a822efab34"><strong>Intro</strong></a></li><li>Part 2: <a href="https://medium.com/@mseckington/the-art-of-communication-design-define-your-goals-121b17146bd0"><strong>Define Your Goals</strong></a></li><li>Part 3: <a href="https://medium.com/@mseckington/the-art-of-communication-design-identify-your-audience-76d8fe864a11"><strong>Identify Your Audience</strong></a></li><li>Part 4: Design Your Comms Plan — Still to be published</li><li>Part 5: Design Each Message — Still to be published</li></ul><p><strong>Enjoyed this post and want more? Follow me on </strong><a href="https://mastodon.social/@mseckington"><strong>Mastodon</strong></a><strong>. You might also like: </strong><a href="https://missgeeky.com/2017/08/04/the-art-of-slide-design/"><strong>The Art of Slide Design</strong></a><strong>, </strong><a href="https://medium.com/@mseckington/employee-evangelism-make-your-team-badass-366d92967573"><strong>Employee Evangelism: Make Your Team Badass</strong></a><strong>, </strong><a href="http://missgeeky.com/2016/05/09/miss-geeky-blogging-tips/"><strong>Blogging tips: How to start writing</strong></a><strong>, </strong><a href="https://medium.com/@mseckington/how-i-got-into-conference-speaking-aae4375521b9"><strong>How I got into conference speaking</strong></a><strong> and </strong><a href="https://medium.com/@mseckington/imposter-syndrome-how-we-act-and-work-together-eed045444f3"><strong>Imposter Syndrome: How we act and work together</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=121b17146bd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of Communication Design: Intro]]></title>
            <link>https://medium.com/@mseckington/the-art-of-communication-design-intro-54a822efab34?source=rss-4c40e6b00775------2</link>
            <guid isPermaLink="false">https://medium.com/p/54a822efab34</guid>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Melinda Seckington]]></dc:creator>
            <pubDate>Tue, 10 Oct 2023 11:44:42 GMT</pubDate>
            <atom:updated>2023-10-17T15:40:48.385Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n61TYv1tvrS5nSMUGe66CQ.png" /></figure><p><strong>Last month I gave this talk at DevRelCon London. This blog post series is a slightly adapted version of my speaker notes, so that it’s split out across multiple posts and hopefully reads better as articles.</strong></p><p><strong>This is the 1st post in this series. After you read this you might want to read the entire series:</strong></p><ul><li>Part 1: <a href="https://medium.com/@mseckington/the-art-of-communication-design-intro-54a822efab34"><strong>Intro</strong></a></li><li>Part 2: <a href="https://www.seckington.com/the-art-of-communication-design-define-your-goals/"><strong>Define Your Goals</strong></a></li><li>Part 3: <a href="https://www.seckington.com/the-art-of-communication-design-identify-your-audience/"><strong>Identify Your Audience</strong></a></li></ul><p>Communication is something that we all do on a daily basis and most of us know that there are times where we could have communicated better.</p><p>We communicate in so many different ways, in so many different channels. We send emails and slack messages. We have face to face meetings and 1:1s. We do presentations, workshops and demos. But beyond that we also have so many different people that we want to communicate with: there’s lots of different languages, different cultures, different backgrounds. And there are different ways of perceiving and interpreting messages.</p><p>Sometimes you need to take the time to understand what it is you want to get across, so that you can design whether it will have the right impact.</p><h3>What is communication?</h3><p>Let’s take a step back and look at what communication is:</p><blockquote><strong>Communication:</strong></blockquote><blockquote>the imparting or exchanging of information by speaking, writing, or using some other medium.</blockquote><p>In most cases, we define communicating as a way to impart or exchange information through some type of medium.</p><p>So how do we enable a more effective exchange of information?<br> <br>We need to be able to be more deliberate, more intentional with what we’re communicating to allow that exchange.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XCP0hwCnpOkDF_n0mu0WNA.png" /></figure><h3>Coordinating complexity</h3><p>The way I’ve applied this to my own work has often been when we know we have something tricky or complex to communicate, where we know we need to take a step back and consider how do we want to do this. Things that require more than an off the cuff email.</p><p>The scope and size of these comms can vary a lot though. On one side of the spectrum you’ll have bigger events, like rolling out a new process/service/product/initiative, where the complexity in communication comes from coordinating the different types of messages you need to send in the lead up to an event. Depending on your context, you might be using different channels or speaking to different audiences, where the coordination needs to happen over weeks or months.</p><p>On the other side, you may have comms with a quick turnaround like internal team or strategy changes. You might only have a week to do the actual comms, but the complexity comes in planning who needs to know, maybe staggering information, and tweaking the messaging depending on who you’re talking to.</p><p>In other cases, the complexity may come from dealing with sensitive information, where it’s key that you’re only informing certain people or you really need to figure out how it will land with someone and what effect it might have on them.</p><p>In all these cases though, it’s this idea that because you have complexity, it’s worth taking the time to take a step back and be deliberate in how you design what you’ll be communicating.</p><p>And that’s basically what a comms plan is for: helping you coordinate and navigate the complexity of your comms.</p><h3>Increase understanding</h3><p>This is all with the intent to increase understanding. You want to take the time to be deliberate and design your comms, so that what you’re communicating will have a better effect.</p><p>Now you might be thinking I don’t really have to deal with these type of complex communications. I’ve not really been in a position where I’ve had to do that. And that’s okay, not every role will require this.</p><p>But I think especially in people focused roles, like Engineering Management or DevRel, there may be more situations where you can apply a bit more deliberate thinking about comms to what you do, even if it might not be as complex as the situations I just described. Learning how to do this, being prepared to apply this process, will help ready you for when you ever need to communicate something more complex.</p><p>Over the next few posts, I’ll be sharing a couple of steps that you can take when thinking through something you want to communicate, to help you design more effective comms plans.</p><p>Continue on to read the first step: <a href="https://www.seckington.com/the-art-of-communication-design-define-your-goals/"><strong>Define Your Goals</strong></a><strong>.</strong></p><p><strong>This blog post is part of The Art of Communication Design series:</strong></p><ul><li>Part 1: <a href="https://medium.com/@mseckington/the-art-of-communication-design-intro-54a822efab34"><strong>Intro</strong></a></li><li>Part 2: <a href="https://www.seckington.com/the-art-of-communication-design-define-your-goals/"><strong>Define Your Goals</strong></a></li><li>Part 3: <a href="https://www.seckington.com/the-art-of-communication-design-identify-your-audience/"><strong>Identify Your Audience</strong></a></li><li>Part 4: Design Your Comms Plan — Still to be published</li><li>Part 5: Design Each Message — Still to be published</li></ul><p><strong>Enjoyed this post and want more? Follow me on </strong><a href="https://mastodon.social/@mseckington"><strong>Mastodon</strong></a><strong>. You might also like: </strong><a href="https://missgeeky.com/2017/08/04/the-art-of-slide-design/"><strong>The Art of Slide Design</strong></a><strong>, </strong><a href="https://medium.com/@mseckington/employee-evangelism-make-your-team-badass-366d92967573"><strong>Employee Evangelism: Make Your Team Badass</strong></a><strong>, </strong><a href="http://missgeeky.com/2016/05/09/miss-geeky-blogging-tips/"><strong>Blogging tips: How to start writing</strong></a><strong>, </strong><a href="https://medium.com/@mseckington/how-i-got-into-conference-speaking-aae4375521b9"><strong>How I got into conference speaking</strong></a><strong> and </strong><a href="https://medium.com/@mseckington/imposter-syndrome-how-we-act-and-work-together-eed045444f3"><strong>Imposter Syndrome: How we act and work together</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54a822efab34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Employee Evangelism: Make Your Team Badass]]></title>
            <link>https://medium.com/@mseckington/employee-evangelism-make-your-team-badass-366d92967573?source=rss-4c40e6b00775------2</link>
            <guid isPermaLink="false">https://medium.com/p/366d92967573</guid>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[continuous-improvement]]></category>
            <category><![CDATA[developer-evangelism]]></category>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[public-speaking]]></category>
            <dc:creator><![CDATA[Melinda Seckington]]></dc:creator>
            <pubDate>Wed, 02 Nov 2016 16:30:01 GMT</pubDate>
            <atom:updated>2016-11-02T16:30:01.824Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A couple of months back I gave a talk at The Lead Developer called How To Succeed at Hiring Without Really Trying. This is pretty much the blog post version of my script/speaker’s notes for it! Check out </strong><a href="http://www.slideshare.net/mseckington/how-to-succeed-at-hiring-without-really-trying"><strong>the full slides</strong></a><strong> or watch </strong><a href="https://vimeo.com/album/4045988/video/173611607"><strong>the video</strong></a><strong>.</strong></p><p>Imagine: you’re shopping for groceries and need to buy strawberries. You have two options. The first one comes in this completely closed off box — you can’t look into it, there’s no pictures on the packaging — you have no idea how the strawberries actually look like. The second option: a transparent plastic box with some handy labels on it: you know immediately what the nutritional value is, where the strawberries are grown and you even get some a nice recipe for strawberry pie to try. And you can exactly see what strawberries you get.</p><p>Which box do you choose?</p><p>Now of course choosing what company to work at isn’t on the same level as choosing which strawberries to buy. But in the same way, we should be thinking about how we expose and promote our teams as places where people want to work. Not doing anything and remaining a black box that no one can look into doesn’t help at all. So how can we be those strawberries that everyone wants to choose?</p><p>For the past 2 years, I’ve taken a lead within FutureLearn to do exactly this type of stuff — I’ve been responsible for trying to raise awareness about our company within the tech and design community.</p><h3>How to define what I do?</h3><p>In the past I’ve always struggled trying to explain what it exactly is that I do and finding the right phrase or word or title that encompasses it. Developer evangelism. Developer outreach. Developer relations. Developer advocacy. All these terms are used within our industry to describe these roles that are much more outward facing, but none of them felt quite right to describe what we were trying to do here.</p><p>The way I see it this area typically is about creating a relationship between your company and potential customers — you have a product, be it a platform, apis, tooling — it’s something that you want developers to use. There’s a <a href="http://www.leggetter.co.uk/2016/02/03/defining-developer-relations.html">good overview</a> from Phil Leggetter about the different goals and approaches within developer relations, but in the end all of them are about shaping that space, so you can have conversations with those outside of your company about your product.</p><p>And that doesn’t quite work here for 2 reasons: 1) it’s not the product we’re trying to evangelize, it’s our team, and 2) we’re actually not just targeting developers, we’re targeting the wider product team, so also designers, UX researchers, product managers. It’s about more than just developers.</p><p>So the phrase I’ve started using recently to capture this is <strong>employee evangelism</strong>. In the same way that developer evangelism is about creating that conversation between your company and the outside world, employee evangelism is about creating that conversation between your employees and the potential employees outside the company. It is about raising awareness about the team — and comes from the team directly.</p><p>Rather than having a single person be the employee evangelist, you want the entire team to contribute to this evangelism, making sure that this loop is constantly happening:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iz1nFD0NQHrJrmDi." /></figure><p>Now we have other people on the team who take care of the hiring process, and I like to think that everyone on our team does awesome stuff, so my focus tends to be on getting people to share that awesomeness with the community. I’ve always seen this as a team role: I’m not the only person in the company going out and talking at all the events, I’m not the only person writing all the blog posts. This has been very much about supporting our entire team to do all this, helping them learn the skills they need for this and helping create the type of environment where everyone feels encouraged to contribute.</p><h3>How to encourage your team?</h3><p>Now that I’ve defined what I’ve do, I want to look at what you can do to encourage and support your team to practice this type of evangelism.</p><p>A couple months back I read Badass: Making Users Awesome from Kathy Sierra and in it she explains how the best way to get your product being used by people, is understanding that it’s not necessarily about your product, it’s about making your users awesome. If they feel they are being badass, when using your product, they’ll be more passionate and motivated to share what they can do with your product.</p><p>Kathy goes on to create a framework of sorts to help your users become badass. And I realised that most of what she describes in there can be adapted to how we can encourage our teams. How we can make our teams badass.</p><p>Using her book as a base I’ve adapted it specifically for getting your team to share more, but I think it can applied to a lot of other ways of making our teams better. I want to focus on 4 areas, and I think all of these combined can help you encourage your team:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3MaBUF-M_druL-_E." /></figure><h3>Give them a compelling context</h3><p>This is about creating that right type of environment where people feel like they can share. Start with the company culture first. Now let’s go back to our strawberry example.</p><p>Remember the packaging of the transparent box? The retailer could have put anything they wanted on it — nutritional benefits, the claim that they’re the best strawberries in the world, adorable recipes. In the end though the main thing that matters: whether or not they are good and tasty strawberries. Whether or not they’re the type of strawberries a person would buy again. Whether or not they’re the type of strawberries a person would tell their friends to go buy.</p><p>So: <strong>be great</strong>. The first thing about getting your team, writing or talking about your company is having something that’s worth sharing, something that’s worth getting excited about. If you want potential employees to see what a great company it is to work at, then it does need to be a great company or at least have elements of greatness within it. If there isn’t a single thing that you can think of that is great, that is worth sharing with others, then most probably your focus should be on fixing that first.</p><p>The second thing is to <strong>be authentic</strong>. The stories that your team will tell need to come from them — you can’t give them a script or a brief and tell them to go and evangelise. It needs to have that human voice.</p><blockquote><em>“On their deathbed, nobody will say: If only I’d engaged more with brands.” — Kathy Sierra</em></blockquote><p>Remember this is about employees starting conversations with potential employees. It’s not The Brand having those conversations, it’s actual humans</p><p>Third, <strong>be open</strong>. Be willing to share information and stories and data about your company. Not every company will be able to share everything — but get a good understanding of what things your team can talk about and share, and make sure they’re aware that they can.</p><h3>Give them a compelling reason</h3><p>The second area we need to look at is giving each person a compelling reason. With this I mean look at the personal motivations for each team member. What will drive each of them to share what they do with others? I’ll give a couple examples of what I think are the most common motivations.</p><p><strong>Helping others</strong> — these are the people that share what they know, cause it will directly help someone else. They might not necessarily want to stand in the spotlight, but they know that if they do, they can make someone’s life easier.</p><p><strong>Building confidence in communication</strong> — in most of our day-to-day work we rely on communication to others . Doing a blog post or giving a talk or workshop are extreme examples on that spectrum, but becoming a better speaker or writer will help people in their job, and for some this is the main reason why they will want to get better at it.</p><p><strong>Building personal reputation</strong> — these are the people that want to stand in the spotlight and have the focus on them. A variant of this are the people that want to be experts in a specific thing — they want to show that they have mastered a specific topic.</p><p>These aren’t the only motivations that people have, but I think these are the most popular 3 especially when it comes to getting your team to share what they do. Understanding which of these apply to each team member ties in with helping them actually build the skills they need and understanding what types of stories and problems they want to share.</p><h3>Help them keep wanting to</h3><p>Now that we know what each team member’s goal is how do you encourage them to keep working on this? I think there are 2 sides to this:</p><p>First: <strong>what makes them stop?</strong> You need to understand what each person’s fears and blockers are. I often hear things like I’m not an expert, I can’t write, nothing I do is worth sharing. They’re all valid fears and reasons why someone will stop or will never get started. But once you know what their fears and blockers are, you can help them come up with a plan to overcome them.</p><p>The flip side of this is: <strong>what pulls them forward?</strong> Make them set a goal, like speak at a conference in a year’s time or write a full length blog post in 2 months time and help them break this big goal into more manageable chunks. I haven’t quite done this with my team yet, but am in the process of creating some progression paths for writing, speaking and workshops, so that people can pick and choose from these when setting their personal goals with their line managers.</p><p>Finally: <strong>lead by example</strong>. Make sure your team is not only aware of the things that you do, but also how you got there. For instance, when I started this 2 years back, I hadn’t ever spoken at a conference before. Even now I still get super nervous giving talks. So I know the types of fears my team were feeling — I’ve been there — but constantly sharing with them what my journey has been and how I deal with my fears and nerves, it shows my team that this is just as attainable for them as it was for me.</p><h3>Help them actually get better</h3><p>The final and largest area to look at is how to help your team actually get better. How do you help them improve their skills?</p><p>The first part of this is <strong>perpetual exposure</strong>. This is the idea that to become better at something, to become an expert at something, you need to be exposed to high quality examples of the things that you’re trying to get better at. In this case of getting people to share things make sure your team is exposed to good examples of other people sharing.</p><p>So to start: <strong>have a library</strong>. This doesn’t have to be just books, but also blog posts, articles, screencasts, videos, basically any content that is worth sharing with your team. What are good examples of content that other people have created? Besides that we’ve also got lists of recommended material to help people get started with public speaking and writing.</p><p>Another thing we organise is <strong>Talks We Love</strong> — in this we watch a recorded video of a talk together that one person on the team really enjoyed or found useful, followed by a discussion on things we might want to do ourselves.</p><p>Beyond highlighting external content, you also need to try to <strong>highlight existing good internal content</strong>. Our teams are already creating content: just think about good commit messages, or emails or slack messages explaining things. Most of the time it just requires someone pointing out to them ‘did you consider turning that into a blog post? Or a talk? Or a workshop?’. Be that voice that champions the work that they’re already doing.</p><p>The second part of helping your team get better — is <strong>giving them the time and space for deliberate practice</strong>. Rather than throwing them in the deep end — you need to allow them to build these skills gradually. I’ll give a few examples of how we support practice with speaking and writing. They’re not the only things we do, but it’s just to give you a sense of what types of activities and support you should be thinking of.</p><p><strong>Lightning Talks</strong>: These happen every 4–6 weeks and anyone in the company can give a quick 5 minute talk about anything they want. This is a great way to get people to recognise that they have something worth talking about and it gives them the experience and confidence to do more talks.</p><p><a href="https://about.futurelearn.com/blog/making-futurelearn/running-a-learning-hour/"><strong>Learning Hours</strong></a>: In these one person on the team, teaches something they think other people might find useful. These tend to be more hands-on and workshop like. And these can be about anything — past learning hours have been about command line tools, how to run retrospectives and understanding database indexes better. Rather than learning to speak in front of a larger audience — this allows people to practice these skills in front of a smaller group of people they’re already working with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nELHhIatsqHaNk4I." /><figcaption><em>A FutureLearn Learning Hour</em></figcaption></figure><p><strong>Conference Club</strong>: This is an internal meetup for everyone that wants to speak at conferences to get together and help each other with everything that goes into creating a conference talk. So coming up with talk ideas, helping write proposals, giving feedback on practice runs. It’s making sure that people aren’t doing this completely by themselves.</p><p><strong>Collaboration blog posts</strong>: We pick a specific topic, like <a href="https://about.futurelearn.com/blog/international-womens-day-2016/">women that inspire us</a> or <a href="https://about.futurelearn.com/blog/language-we-love/">foreign words that we like</a>, and ask for paragraph submissions. So rather than having to commit to a full length blog post, we get people started with writing small snippets.</p><p><strong>Internal Blog</strong>: Another thing we have is our internal blog, for sharing problems or stories with the wider team. Again rather than having to publish something immediately for the entire world, we basically provide a stepping stone inbetween.</p><p>So give your team the time and space to practice these new skills. These won’t grow overnight and you need to create a supportive environment if you want to get everyone involved.</p><h3>What was the effect on our team?</h3><p>So what was the effect of all this on our team? Now when I started this role we barely had anyone from our product team writing blog posts or speaking at events. Here are some stats of where we got to now.</p><p>Not including the people that joined our team recently, about 35% of our team have now done an external talk. That percentage rises to 60% when we take into account the lightning talks and to 78% when we add the learning hours. With blog posts we’ve got 75% of our team that have written full length blog posts, and 89% when we include the collaboration posts. And the awesome thing is, if we combine this all, this means that everyone in our team is sharing their knowledge in some way.</p><p>Tying it back to the start of this post — from the last round of hiring, 50% of the interviewees explicitly mentioned having seen a talk or read a blog post. This wasn’t us asking them if they had — this is the percentage of people that brought it up themselves in their conversations with us. So the actual number might actually be higher.</p><h3>Final thoughts</h3><p>If there’s one thing you take away from this blog post, let it be this: Every team can do this, but more importantly I think every team should do this.</p><p>While I think employee evangelism is great for your company, in the end it’s about making our community great. Embedding these type of practices within every company means that we get more people sharing what they do, and what they love. If we want to see more diverse speakers at events, if we want to see more diverse writers share their stories, we need to support everyone to learn these skills and as tech leads we are in positions to change this.</p><p>So I want you all to think about this — the next time you came across something that one of your colleagues have done that could help someone else, help them to share it with the world. And maybe next year thanks to you, they will be somewhere on a stage sharing that story and trying to make the community a better place.</p><p><strong>Enjoyed this post and want more? You might like: </strong><a href="http://missgeeky.com/2016/05/09/miss-geeky-blogging-tips/"><strong>Blogging tips: How to start writing</strong></a><strong> , </strong><a href="http://missgeeky.com/2016/01/26/how-i-got-into-conference-speaking/"><strong>How I got into conference speaking</strong></a><strong> and </strong><a href="https://medium.com/@mseckington/imposter-syndrome-how-we-act-and-work-together-eed045444f3"><strong>Imposter Syndrome: How we act and work together</strong></a><strong>.</strong></p><p><strong>Curious about how we do more things at FutureLearn? Read our </strong><a href="https://about.futurelearn.com/blog/?category=making-futurelearn"><strong>“Making FutureLearn” posts</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=366d92967573" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Time to Talk: Anxiety & I]]></title>
            <link>https://medium.com/@mseckington/time-to-talk-anxiety-i-9e9bc11e4561?source=rss-4c40e6b00775------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e9bc11e4561</guid>
            <category><![CDATA[anxiety]]></category>
            <category><![CDATA[mental-health]]></category>
            <dc:creator><![CDATA[Melinda Seckington]]></dc:creator>
            <pubDate>Fri, 05 Feb 2016 10:04:53 GMT</pubDate>
            <atom:updated>2016-02-05T10:07:04.283Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://missgeeky.com/2016/02/04/time-to-talk-day-anxiety-i/"><em>This article first appeared on MissGeeky.com</em></a><em>.</em></p><p>Today it’s <a href="http://www.time-to-change.org.uk/">Time to Talk Day</a>, a campaign to make people aware of mental health issues and to get people talking about them. I’ve dealt with a lot of anxiety in the past 15 years or so, but have to admit I’ve never talked to a professional about it or even really considered it a mental health “issue” I have. Looking back though I’m realising maybe I should have — maybe I could have made it easier for myself if I had. I guess part of me just thought that this is what being a grown-up means, that everyone experienced these things but I just wasn’t good enough at coping with them. And that in itself is why I’m writing this — if it helps only one single person out there, that alone means this post was worth writing.</p><h4>Being “perfect” and Imposter syndrome</h4><p>I think my anxiety started in the final years of high school. Before those final 2 years, I thought school was pretty easy. I’ve got an awesome short term memory, so memorising stuff for exams wasn’t very challenging, and I always considered myself in the top of the class. In those final years though, things changed — I still was getting high marks and performing well, but it took way more time and effort than it did before and I put a ton of pressure on myself to be that ‘perfect’ student again. I started feeling anxious and bad whenever I got a bad grade, leading to me putting even more pressure on myself, creating this continuous loop of pushing myself maybe a bit too hard.</p><p>And that only got worse when I went to university. I decided to study Computer Science without having programmed anything before in my life (well, except for my graphical calculator) and I was overwhelmed by the amount of stuff my peers already knew. Compared to them, I felt so inadequate — maybe I had made the wrong decision and I should have studied something else? Despite feeling like that, I kept pushing myself trying yet again to be that ‘perfect’ student even though I knew I could never be as good as my peers. And thanks to all my hard work, I did keep getting high marks for exams and assignments. I knew I wasn’t bad, but somehow I felt like it was just luck, that one day someone would expose me for the fraud I actually was.</p><p>At its worse, it would come on as full-on episodes of anxiety — I’d be sitting in the computer lab with a ton of other students around me, reading through the latest practical assignment and just freeze, knowing I didn’t know how to solve this problem. My chest would go all tight, my face and neck would go all red and splotchy, and the sound of my way-too-loud beating heart would drown out all the noise around me.</p><p>I now know that this is what is called Imposter Syndrome, but at the time I thought I was the only one feeling like this. Realizing that most people I know, even those who are way more experienced than I am, have dealt with imposter syndrome was a huge eye-opener to me. Hearing how I wasn’t the only person that has this and talking to others about their own experiences has been the main thing that has helped me deal with this type of anxiety. Knowing that most of us are ‘imposters’ and just trying the best we can has taken away that feeling that I don’t belong.</p><p>Throughout the years it’s gotten a whole lot less, but I’ll still have days where I don’t feel good enough — that I’m not doing the best I can. I’ll get stuck in loops of self doubt and blame for not having done more. It’s not quite Imposter Syndrome, but it still is anxiety about how I assume I should be. Especially after a day that hasn’t gone quite as I thought it would, I’ll get easily stuck in thinking of all the other ways I could have done something, replaying events over and over in my head.</p><h4>The Worst Case Scenario Thinker</h4><p>Tied to that is that there’s always this part of my brain that for any situation will try to come up with all possible outcomes — going down every path, be it good or bad. I’ll imagine all the ways past conversations could have gone, or how future conversations might go and (from a code perspective) come up with most edge cases before it’s needed. It’s a great skill to have (especially for work and board games), but only when I can reign it in and actually turn it into something I can act on.</p><p>In the worst case scenario though my worst case scenario thinker will focus way too much on the negative, coming up with a ton of unlikely and bad scenarios, causing me to freeze up and get massive panic attacks based on ‘what might happen’. I’ve had lots of sleepless nights where my mind has gone down the rabbit hole of doom and dread, conjuring up the worst things I can think of.</p><p>Nowadays it mainly happens to me when I’m doing stuff not part of my routine, like when I’m going on holiday. I’ll get super anxious just thinking about all the things I’ll forget to pack, how I’m going to miss my flights, how the airline will lose my luggage, how my flat will be burgled while I’m away, how the pet sitter will forget to feed my cats, how I’ll get lost and not find my way back to my hotel, how my bag, passport and money will be stolen, how… etc etc. I know most of it is unlikely and won’t happen, but it’s so easy to get trapped in thinking of all the negative that ‘could’ occur.</p><h4>Understanding, compartmentalising and reflecting</h4><p>For me, there have been 3 things that have helped a lot with how I deal with anxiety. The first is <strong>understanding</strong>. Identifying when I’m having a panic attack and understanding why it’s happening and what has triggered it, means I can try to stop my mind from going down the rabbit hole. I find the psychology of emotions fascinating (my master’s thesis was on facial expression recognition), and being able to learn what our brains do when we experience anxiety has helped me a lot (I find a good place to start is <a href="http://www.amazon.co.uk/Emotional-Intelligence-Matter-More-Than/dp/0747528306/?tag=missgeeky-21">Emotional Intelligence</a> from Daniel Goleman).</p><p>The second thing is <strong>compartmentalising</strong>. I’ll always have these parts of my brain that will pipe up at completely the wrong moments and I’ve accepted that they will always be there. I’ve realised though that I don’t always have to listen to them at that moment: I’ll acknowledge they’re there, then mentally shove it in a box and put it aside to open up later. I’ll never completely forget about that box though, and I will always get around to dealing with those thoughts and issues, but I’ll do it at a time when it works for me (rather than say in the middle of the night when I’m trying to sleep).</p><p>The third is <strong>reflecting</strong>. I wrote an entire article about doing <a href="http://12devsofxmas.co.uk/2015/12/day-1-christmas-is-a-time-for-reflection/">personal retrospectives for 12 Devs</a> during Christmas, so won’t go into too much detail here. Reflection for me is sitting down and taking the time just to think about all the things I’ve done and what I could have done differently. It’s a time to open the box with all the thoughts I had and to go through them. The main thing is doing it when it feels right to me — when I feel I have the right type of mind to deal with the issues.</p><p>I know these are just the things that I do and I have no idea whether or not they will help anyone else, but it might help just hearing how other people deal with stuff. I also know my version of anxiety isn’t as extreme as it can be for others, yet it will be more than what most people typically encounter. Anxiety is something that I know I need to deal with on a regular basis, and I know it will never fully go away for me. But talking about it, however hard and embarrassing and weird it might be, does help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e9bc11e4561" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I got into conference speaking]]></title>
            <link>https://medium.com/@mseckington/how-i-got-into-conference-speaking-aae4375521b9?source=rss-4c40e6b00775------2</link>
            <guid isPermaLink="false">https://medium.com/p/aae4375521b9</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[speaking]]></category>
            <dc:creator><![CDATA[Melinda Seckington]]></dc:creator>
            <pubDate>Fri, 29 Jan 2016 11:22:28 GMT</pubDate>
            <atom:updated>2023-10-10T11:43:01.271Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve had several conversations in the past few weeks, where people are surprised to find out that I’ve haven’t been doing conference talks for that long. For some reason, most of them assumed that I’d been doing these talks for years and years, and that I’m a massively ‘experienced’ conference speaker. Spoiler alert: I’m not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z-4U3IJvJU8TF1mF9tQoYA.jpeg" /></figure><p>It’s only midway 2014 when I told myself I’d try to do a year of not saying ‘no’ to things that scared me, that I started putting myself forward as a conference speaker and started submitting talks to CFPs. That conference “season” I ended up doing Electromagnetic Field, DDD East Anglia, Hackference and Future of Web Apps; those were my first proper conference talks. It’s not that I hadn’t given presentations before that (I had done a handful of lightning talks the year before), but this was the first year that I was speaking at events where people actually paid to attend and see me (among others) speak.</p><p>I realized that even though I hadn’t been doing conference talks before that, I’ve managed to do a ton of different things in the past years to slowly build the skills I now rely on. Public speaking is a BIG SCARY THING (for me it was at least) and if you had told me 10 years ago that I would be doing it on a regular basis and actually enjoy it, I would have called you crazy. So I thought I’d share my experiences about how I got to where I am today. This isn’t going to be a post with clear actions on what to do to become better at public speaking (there’s enough of those out there), rather it’s a collection of thoughts, memories and stuff from me about it all.</p><p>To make a cheesy analogy (cause all good posts need a cheesy analogy): giving a conference talk is like jumping off a diving board doing back flips into the pool. Sure, some people might have the guts to just jump off the board and see what happens. Others might do it and be immediately awesome at it. Me though? I had to learn the basics like how to not drown and how to dive. Plus I needed to psych myself up to climb that ladder and get on the board in the first place.</p><h3>The Backstory</h3><p>I hated public speaking. I knew that I couldn’t get away from giving presentations, but for years I always dreaded having to do them. I don’t remember the number of presentations I had to give at high school and university, but I do remember never liking them and only giving them when given no choice. Whenever we worked in groups, I was completely happy with letting someone else stand in the spotlight and talk about our work.</p><p>Everything about talks terrified me: having to speak in front of strangers, having to speak in front of a lot of people, coming up with what you are going to say, making sure what you say is sensible and delivering what you want to say in the best possible way. There are so many aspects to giving a good talk and all of them felt terrifying to me. I was the type of person that already felt uncomfortable with speaking to a random shop assistant when doing groceries, so giving a talk? Yeah. Not. My. Thing.</p><h3>Attending meetups — how to talk to strangers</h3><p>In 2007 Cristiano and I moved to London. We didn’t know that many people here, so we started going to meetups, conferences and other tech events. I still remember when I went to my first GirlGeekDinner and being so so awkward at it: standing in the corner, having no idea who to talk to and doubting whether anyone would even want to talk to me.</p><p>I’m a massive introvert, so networking, meeting new people, talking to strangers: it doesn’t come naturally to me at all. The more you do it though, the easier it gets. Even now I notice that when I haven’t done a meetup with new people for a few weeks, I need to get back into the right how-to-network mindset, like it’s a muscle I haven’t flexed for a while. Similarly if I’ve done too many events in too short a time, I’ll reach a certain point where I just don’t have the energy anymore to be social and deal with new people. And that’s okay. But you need to build it up, keep at it, and figure out what your own limits are.</p><h3>BarCamp — you don’t need to be an expert</h3><p>In that same year I got introduced to the idea of BarCamps, an unconference. Unlike normal conferences, where there are special speakers and a curated schedule announced before the day, with a BarCamp the schedule and sessions are created by all the attendees. Cristiano had been to BarCampLondon2 and we had both gotten tickets to BarCampBrighton later that year. At the time though I didn’t completely understand what a BarCamp was and what it meant I needed to do: only the day before did I realize that I HAD to do a session, which I interpreted as “give a talk” (later on I found out that “doing a session” could also be things like running a discussion or a show-and-tell; it didn’t necessarily have to be a presentation). I couldn’t deal with it: having to give a presentation with less than 24 hours notice? I broke down in tears and refused flat out to do it.</p><p>Despite that, the next day I still attended the BarCamp, fully expecting and dreading the disappointment of others when they found out I didn’t want to present. And then I actually went to some sessions… BarCamp is one of the most supportive and useful events that I’ve been to; it’s all about sharing what you know with others, no matter how knowledgeable you are on the subject. BarCamp taught me that everyone has something worth talking about: you don’t need to be an expert to talk about the things that interest you. Besides that, the informality of the event creates a relaxed and fun environment, meaning there’s no pressure to give the “perfect” talk.</p><p>From 2007 to 2010 I attended all the BarCamps that I could, attempting to do sessions at all of them. Most weren’t very good or that well prepared (case in point: <a href="https://vimeo.com/1102660">this video</a>), but despite that I know that people enjoyed them. Plus every single time, I got just that little bit better at speaking in front of people.</p><p>That first BarCamp I went to? I ended up making some slides during the overnight and gave a last minute talk on the second day.</p><h3>Hackdays — how to present in front of a lot of people</h3><p>The other type of event I started attending around the same time were hackdays (also known as hackathons, although I personally really prefer the term ‘hackday’, but that’s a post for another time). At these you form teams for an entire weekend/24 hours to hack something together. At the end of the 24 hours, everyone gets together to present what they’ve built. And depending on the type of hackday, there are various prizes people can win.</p><p>Hackdays are a great place to try out new stuff and learn new skills. Just like with BarCamps, most people are extremely supportive and willing to help you learn. The first couple of hackdays I went to I ended up forming a team with friends and let them do the presenting. But as I went to more of them, I ended up having more ideas and hacks that I was did on my own. There were several early hackdays though where I didn’t end up presenting what I built, mainly cause I didn’t think my hacks were good enough. Why show how little I got done? Eventually though I realized that didn’t matter: you had an idea which you worked on for an entire weekended and you should show what you have done!</p><p>Doing these short pitches is one of the things that got me comfortable with speaking in front of lots of people. You typically only have a 1 or 2 minutes to talk through your idea, meaning you learn to focus on getting your point across quickly.</p><h3>Writing blog posts — how to tell a story</h3><p>I admit: not every blog post on this blog is of the highest storytelling quality, but doing this blog for the past 8 years has taught me a couple of things. Firstly, the ability to recognize what makes a good blog post. There’s a little voice in the back of my head constantly going “Wouldn’t that work as a post?” or “What would happen if you combine this idea with that one? New blog post!”. With almost everything I come across a part of me is thinking about how to turn it into a story. And the same applies when considering talks. Not every blog post works as a talk, and not every talk works as a post. But being able to identify there’s a story there that’s worth telling is the same in both cases.</p><p>The second thing is the ability of actually telling that story. Throughout the years I’ve slowly learnt what I like and look for in blog posts, and how to apply that to my own posts. The key things I’ve found is understanding who your audience is, why they should be reading your post and what are they taking away from it. From there, you can derive the main structure of your post, framing the story in the right way. I could do an entire post on storytelling alone, but being able to write blog posts and tell a good story has been super useful in creating talks.</p><h3>The Future</h3><p>I guess what I’m trying to get at with this post is this: right now you might feel like you’re never ever going to want to willingly give a presentation. There might be different reasons and fears keeping you from doing them. Figuring out exactly what fears you have though means that you can come up with smaller and easier ways to get over them. Scared of talking to people you don’t know? Start going to meetups with friends and try to talk to 1 new person. Scared of talking in front of a lot of people? Try to find something lowkey that allows you to talk in front of a big group.</p><p>We need more diverse speakers in our industry. But that also means we need more people and more events to help create those speakers.</p><p>So here’s my slightly belated New Year’s Resolution: I want my 2016 to be all about helping others get into public speaking. To start things off, I’m mentoring next Saturday at ScotlandJS’s <a href="http://scotlandjs.com/cfp/#diversity_workshops">Diversity Workshop</a> at the FutureLearn offices. If you have a talk idea and what help developing it, <a href="http://scotlandjs.com/cfp/#diversity_workshops">sign up</a> and come along! Even if you don’t have an idea or don’t feel like you’re ready to give a talk yet, feel free to come to the event — doing the workshop doesn’t mean you’re committing to giving a talk.</p><p>Besides that I’ll be organizing another <a href="https://twitter.com/barcamplondon">BarCampLondon</a> this year with Geeks of London. We don’t have a date, a venue or any sponsors yet, but I know how much BarCamp helped me in the past and I think it’s an event our community needs. I’ll also be organizing more <a href="https://twitter.com/thundercloudldn">Thunderclouds</a> this year to get more people comfortable with and learning how to do lightning talks.</p><p>Finally I’d love to hear from all of you! What are the things that you want help with or have questions about? Feel free to reach out <a href="https://twitter.com/mseckington">on Twitter</a>, send me <a href="/service/mailto:melinda@missgeeky.com">an email</a> or reply here in the comments.</p><p>Giving a talk can be a big scary thing, but maybe if we all pitch in and help out, we can make it not that big and not that scary.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aae4375521b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Imposter syndrome: how we act and work together]]></title>
            <link>https://medium.com/@mseckington/imposter-syndrome-how-we-act-and-work-together-eed045444f3?source=rss-4c40e6b00775------2</link>
            <guid isPermaLink="false">https://medium.com/p/eed045444f3</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Melinda Seckington]]></dc:creator>
            <pubDate>Thu, 01 Oct 2015 16:09:52 GMT</pubDate>
            <atom:updated>2016-02-09T14:24:51.408Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post first appeared on the </em><a href="https://about.futurelearn.com/blog/imposter-syndrome-how-we-act-and-work-together/"><em>FutureLearn blog</em></a><em>.</em></p><p>As developers, we’re constantly learning: we’re expected to keep track of new technologies, languages and frameworks. We’re expected to work with old technologies, languages and frameworks. We’re expected to fix weird never-seen-before-bugs. We’re expected to solve problems that don’t necessarily have one unique solution.</p><p>There’s an overwhelming amount of things we could know, and everything we do requires us to learn and adapt.</p><p>When we experience imposter syndrome, that feeling of not belonging and thinking we don’t know enough, it’s caused by the assumptions that we make about the rest of the world: we make assumptions about how and what we think the world expects us to be, to act and to know.</p><h3>Imposter syndrome is not just a personal issue</h3><p>Part of this is a personal issue: there are plenty of things we each can do to stop feeling that way. But knowing how many people experience imposter syndrome, I think this is wider than that: this is an issue we should be dealing with as a community. What can we each do to help others not feel that way? How do we remove these assumptions people make about what they’re expected to know?</p><p>I think this can be primarily solved by highlighting the state of not-knowing. Starting off by knowing nothing, making mistakes and learning as you go is all part of the process. Especially as developers, having the space and time to do all that helps us make new assumptions of what we think we should know.</p><p>What I think this comes down to is having a culture of learning where people can learn and fail. So how do we create that culture?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*9kyfy5guKPcsLYoan14r4A.png" /></figure><p>Unsurprisingly, most of our team at FutureLearn are interested in learning more and in better ways. Our company mission of providing the best learning experiences to everyone, anywhere, is not only about our product, but is also reflected in the way our team works.</p><p>Giving people the space and time to learn and fail has been essential for creating a sustainable development team. As our company has grown, our culture of learning has evolved to what it is now, embodying the ideas and values of everyone that works here.</p><p>I think we can look at this from two different perspectives: the way we act and work together and the different types of events we organise to support learning. In this post, I’ll focus on the way we act and work together, while in an upcoming post I’ll talk about the events we organise to support this.</p><h3>How we act and work together</h3><p>So I want to share six values or principles or whatever you want to call them about how we act and work together. Now we’ve never made these explicit values in our product team, since we believe that these should be a given for every team. They’re not something that are unique to our company or our team, although they are all things that we do and try to uphold.</p><h3>1. Embrace failure</h3><p>From a very early age, we’re taught: failure is bad. Failure means you didn’t study or you were lazy, or that you’re just not smart enough. We’re taught that failure is something to be ashamed of. And that’s just wrong.</p><p>Making mistakes and failing is all part of learning something new and we should accept that it will happen. Just think about the first time you learnt how to read, or learnt how to play a new instrument, or how to ride a bike. Did you do all those things perfectly the first time you did them?</p><p>Every mistake, every failure is part of the learning experience. This shouldn’t be a surprise to those of you that do test-driven development (TDD) or behaviour-driven development (BDD) — you don’t just want to make your tests pass, you need to see them failing as well. So this isn’t only about embracing and accepting failure, but it’s about actively seeking it out as well.</p><h3>2. There are no stupid questions</h3><p>This is something that I struggled a lot with. I thought asking questions and admitting I don’t know something was a sign of defeat. A sign that I was a fake, that I didn’t belong. Tied up with this is googling something if you don’t know it. I always thought good developers had just memorised everything there is to know, but that’s not true.</p><p>As I said before, the state of not-knowing is part of the process. There will always be times when we look at a bug or a new feature and go “I have no idea where to start on this”. Good developers know when to ask questions and when to ask for help.</p><p>But this also means that you should never look down or make fun of questions that others might have. You should never stop asking questions, but more importantly you should never stop answering them.</p><h3>3. Trust people to do the right thing</h3><p>We believe that everyone we’ve hired is working to the best of their abilities. Nobody is actively working against us and trying to destroy everything. We trust that people, our team members, are working towards a common goal and will make sensible decisions.</p><p>In some cases the “right thing” is <strong>not</strong> to work on something or to ask for help with something. You trust that they know their own abilities. Giving people this trust, also builds their confidence that they are making the right decisions. It takes time to do this, to learn how to make good decisions, but you end up with smart proactive people rather than mindless drones that just do what they’re told.</p><h3>4. Treat people like grown-ups</h3><p>This goes hand in hand with the previous one, but is more focused on permissions. We don’t require everyone to ask permission to do things. Since we trust that they’ll be doing the right thing, we shouldn’t need to put any rules or restrictions in place to stop them from doing things.</p><p>One example of this is how we deal with committing code and pull requests. We don’t require them for every single thing that someone commits. Rather, we leave it up to each developer to decide whether they think it requires a pull request — are there specific questions they want answered, or do they want feedback on it — it’s up to each person to make that decision.</p><h3>5. Don’t focus on job titles</h3><p>We think it is important that people are not confined by their job title. We don’t want anyone thinking “I can’t do X because I’m only a developer”, where X could be “lead a team”, “run a retrospective”, “manage our infrastructure” or “work on a back-end story” etc. Everyone on the team is encouraged to work on the skills they want to have, even if they might not have them yet.</p><p>For instance, we try not to differentiate between “junior”, “mid-level” or “senior”, or even between “back-end” or “front-end”. We don’t expect you to be the best at something to be the one to do it. As long as you know who to turn to and who to ask questions to if you do get stuck.</p><h3>6. Give constructive feedback</h3><p>Giving feedback and helping others improve themselves is a good thing, but you need to be constructive. Give feedback that allows people to understand the changes they need to make.</p><p>For example, rather than purely saying that you don’t like someone’s commit messages, give examples of exactly what you don’t like about their commits: are their commit titles too short? Are their messages not descriptive enough? Make sure your feedback is directly actionable by the person receiving it.</p><p>These are just six values that we believe create a culture where people feel comfortable with learning and failing. They are not the only things we can do, but we think these form a good base for creating the right type of environment to enable learning. How would <strong>you</strong> create a culture of learning? How would you help others deal with imposter syndrome?</p><p><strong>Want to know more about the way we do things at FutureLearn? Check out </strong><a href="https://vimeo.com/139069166"><strong>the video of my talk</strong></a><strong> about our culture of learning or take a look at more of our “</strong><a href="https://about.futurelearn.com/blog/?category=making-futurelearn"><strong>Making FutureLearn</strong></a><strong>” posts.</strong></p><p><em>Originally published at </em><a href="https://about.futurelearn.com/blog/imposter-syndrome-how-we-act-and-work-together/"><em>about.futurelearn.com</em></a><em> on October 1, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eed045444f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How and why we ran an internal hackday at FutureLearn]]></title>
            <link>https://medium.com/@mseckington/how-and-why-we-ran-an-internal-hackday-at-futurelearn-c709ce4a08a7?source=rss-4c40e6b00775------2</link>
            <guid isPermaLink="false">https://medium.com/p/c709ce4a08a7</guid>
            <dc:creator><![CDATA[Melinda Seckington]]></dc:creator>
            <pubDate>Mon, 11 Aug 2014 09:26:11 GMT</pubDate>
            <atom:updated>2014-08-11T09:26:54.029Z</atom:updated>
            <content:encoded><![CDATA[<p>I should have seen it coming that the first post I’d write on the <a href="https://about.futurelearn.com/blog/run-internal-hackday/">FutureLearn blog</a> would be about a hackday. Hackdays and I… we have a long history to put it mildly. I’ve been regularly attending them for the past seven years. I’ve been organizing them at Geeks of London for the past four, including the 500 person <a href="http://hacked.io/">HACKED</a> last year. I’m one of the supporters of the <a href="http://hackdaymanifesto.com/">Hackday Manifesto</a>. And even my own previous startup was hatched at one. So yeah, me and hackdays, we go a long way back.</p><blockquote><strong>hackday </strong>[hak-deɪ] noun<br>1. <em>A one or two day event where developers, designers and other interested parties come together to build stuff.</em></blockquote><h3>What is a hackday?</h3><p>Hackdays come in all shapes and sizes. Some are extremely competitive, some have prizes, some are for good causes; but at their core they all come down to the same thing: put a bunch of people together for a limited amount of time to come up with something awesome. I’ve always found that a hackday is whatever you as an attendee want it to be and for me hackdays have been always about learning. Learning how to work with new technologies, learning how to work with new people, learning how to work quickly and learning how to build awesome stuff. I’ve always felt that at hackdays you’re surrounded by a ton of other brilliant people, all willing to help out and teach you whatever it is you want to know, and I wouldn’t be where I am today without them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*KvHlk2zkjYFr7aTOHVzq4Q.jpeg" /></figure><h3>Why run a hackday?</h3><p>Ever since I started at FutureLearn I knew we had the right culture and a great team to make an internal hackday work. I’ve always been interested by the idea of doing an internal hackday, but I had previously only done large external ones where the organizational focus is quite specific (in short: venue, sponsors, data, food, prizes). With an internal hackday the focus is slightly different and organizing the FutureLearn one was an interesting, new challenge.</p><p>The main thing we first needed to consider was: why? Why are we running this hackday? What do we get out of it? Our main goal was to give the whole team the space to be creative and explore interesting and innovative ways of improving FutureLearn. We wanted to see what ideas people come up with when you give them absolute freedom to work on whatever idea they were most passionate about, allowing them to let their imagination run wild. An extra side goal was to show each other the talent and creativity among our team, and to give people the opportunity to work with colleagues they might not get to deal with on a day-to-day basis.</p><h3>Include everyone</h3><p>The second thing we needed to pin down was: who? Should we keep it to just the product team or should we invite the entire company? We very quickly decided it should be anyone that wanted to attend: the more diversity of backgrounds and roles among the hack teams, the more interesting hacks we’d get.</p><p>This also led to us making it clear to everyone early on that you didn’t have to know how to code to participate in the hackday. Unlike the more traditional hackdays, our hacks were allowed to be sketches and whiteboard scribbles, as long as you showcased your idea in some creative way.</p><p>Besides that, we wanted to also involve the people in the office that for some reason or another couldn’t participate in the entire hackday. We did this by inviting everyone in the office that day to attend the free lunch and the final hack presentations. This way everybody could see what people were up to that day, even if they couldn’t attend themselves.</p><h3>Create a hackspace</h3><p>The next issue we needed to look at was: where would we hold the hackday? Should we get an external venue, or should we host it ourselves?</p><p>Initially we wanted an external venue that would inspire all the hackers to be creative and think about FutureLearn innovatively. While that still remains a nice sentiment, we realized that the hackday would benefit more from getting the interaction from everybody within the company (as mentioned above), even those that couldn’t participate in the full day. Holding the hackday in our own offices was a much more effective way of showing to everybody the conversation and interaction that went on, and an easier way to encourage them to attend the hack presentations at the end of the day. We were also hoping that seeing the bustle and buzz around the hackday would motivate them to participate next time.</p><p>A side benefit of that was that we knew our offices inside-and-out, and didn’t have to deal with the headaches most external venues create, like sorting out wifi, seating and insurance. We knew what was possible in our hack venue, because that’s where we work everyday.</p><p>What we didn’t want happening though was that the hackers would sit at their normal desks next to the people they’d normally sit, and get drawn back into doing the work they’d normally do. Instead we grabbed the normally quiet breakout area and turned that into a dedicated hackspace for the day. That area already included whiteboards, and we added several small islands of tables to allow small teams to huddle around and work together. Taking people out of their usual work environment meant again that the hackday allowed for people to work a bit differently than they usually would.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3XhJzjsKYpfYG2bLbf6lhQ.jpeg" /></figure><h3>Define the hackday</h3><p>Once we knew why, for who and where we were running the hackday, we started looking at some of the logistics around it. Should the hackday be one or two days? What day of the week should it be? What should the format of the day be? Should we have presentations? Should we have judges? Should we have prizes?</p><p>Since this was still an experiment and weren’t sure how people would react to it, we chose to keep the event simple to allow as many people as possible to come along. We chose a single normal working day, with the hackday running during standard office hours. The day would start with a short kick-off presentation, explaining the rules of the hackday, and would end with presentations from all the teams that created hacks. We settled on a simple but fun prize (tickets to a British Library exhibition) to be determined by popular vote of everyone that attended the presentations.</p><h3>Give time to prepare</h3><p>With the hackday only being a single day, we knew that we weren’t actually giving people that much time to hack on their idea. We didn’t want people wasting valuable hack time on the day, doing stuff they could have done beforehand. That known, we tried to give everyone enough time in the weeks before to prepare for the day.</p><p>We started by emailing everyone a few weeks before with details about the event. The main call to action in there was for people to come up with ideas and share them on one of the huge whiteboards we had set up for this. Within a few days the board was covered with ideas, allowing people to start choosing what they wanted to hack on.</p><p>A week before the event we started to encourage people to form teams already, and to figure out what other tools they might need to pull off their hack. That way during the hackday itself some teams could get hacking immediately.</p><h3>Be clear what happens with the hacks</h3><p>At the end of the day, 16 hacks got presented. Some were hugely ambitious, while others had more of a let’s just ship it feel. The winning hack “Moments of Celebration” tapped into a shared feeling that although celebration is part of the product vision it’s not really part of the product yet. What every team wanted to know was, what would actually happen with these ideas?</p><p>Before the hackday we made it clear to everyone that anything created during the hackday would be considered and have a chance to end up in the actual product. Since then, the product team has gotten together to review and reflect on the hacks created that day to discuss exactly what is happening with the hacks. Some of the hacks have better defined possible solutions to problems already outlined on our roadmap. Some have helped us understand things more as to the potential benefit and cost of developing the feature. And others have gotten us thinking about things that are missing. Suffice to say, the hackday has had a direct effect on some of the work we’re focusing on in the upcoming months.</p><h3>Next time</h3><p>When we do it again (and I’m pretty sure we will do it again), there are a couple of things I’d change. Even though we tried to prepare people, it was tricky for some to form teams and figure out what they wanted to work on that day. There was a lot of discussion happening in the morning, and most people only started hacking after lunch, which meant there wasn’t a lot of time to actually create something. This could be solved by allowing the event to span two days, and in the future we might experiment with that format. Another change would be to add more prize categories; with the range of interesting hacks, it was difficult to only reward one team. Having more categories would allow us to commend more teams for creating awesome hacks.</p><p>All in all, I think we can say the hackday was a success. It was great seeing what people came up with when you give them complete freedom on what to work on, and seeing how they work together with people they normally wouldn’t. We ended up with a wealth of interesting and fun ideas, some of which are being integrated into the site much sooner than I think they would have been done without the hackday.</p><p>As I said at the start of this post, for me hackdays have always been about learning. It’s part of FutureLearn’s company culture for us to always be learning and doing hackdays like these are yet another way to do that. What did I learn this time? That internal hackdays can be even more fun and useful than external ones… especially when you have a talented team to back them.</p><p><em>This post was first published on the </em><a href="https://about.futurelearn.com/blog/run-internal-hackday/"><em>FutureLearn blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c709ce4a08a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>