<?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 Jack Sheppard on Medium]]></title>
        <description><![CDATA[Stories by Jack Sheppard on Medium]]></description>
        <link>https://medium.com/@madebysheppard?source=rss-ad8d0bc49599------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xciYCilX7Uo16Y73Op0Suw.png</url>
            <title>Stories by Jack Sheppard on Medium</title>
            <link>https://medium.com/@madebysheppard?source=rss-ad8d0bc49599------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:39:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@madebysheppard/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What’s left for design?]]></title>
            <link>https://medium.com/@madebysheppard/whats-left-for-design-345d1d4a03c3?source=rss-ad8d0bc49599------2</link>
            <guid isPermaLink="false">https://medium.com/p/345d1d4a03c3</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[Jack Sheppard]]></dc:creator>
            <pubDate>Tue, 03 Sep 2024 10:07:52 GMT</pubDate>
            <atom:updated>2024-09-03T10:07:52.205Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why Designers should become Product Managers</h4><p>Something has been happening in the tech industry for a few years. A subconscious land-grab and slow, steady descent into a world where design isn’t done by designers. A systematic down-skilling of the entire profession.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*teL-qx_GF9QBmvQGa6fDeA.png" /><figcaption>“A matter of perspective” from <a href="https://www.designthinking.lol/comics/matter-of-perspective">Design Thinking</a></figcaption></figure><p>For a long time, probably, design has been in a tug-of-war between a technical problem-solving profession and an artistic and creative pursuit of aesthetics. Obviously the two go hand in hand but still there’s a continuous discussion about what design really means.</p><p>In fact there’s a kind of technicalisation of design, a move away from defining and closer to assembling the building blocks. Maybe this is a by-product of the reskilling of another profession — the full stack developer. Who of course can exist, but in reality that usually means deprioritising front-end. A job slowly becoming a designer’s responsibility. See the evolution of figma, the popularity of tools like framer and webflow.</p><p>But while this has been going on, so has something much more interesting and, depending on your point of view, worrying. I’m not sure where it started (I have my suspicions, but that’s a conversation to have in a darkened room out of prying eyes and eavesdropping ears).</p><p>That is the democratisation of design. On the surface that doesn’t sound like a terrible idea. Upskill people to be able to make design decisions, empower non-design people to be involved in the creative process. Sounds great. Solves a lot of headaches. But it also devalues the nuanced skill or ability to solve problems at a creative level.</p><p>Delivering services is a team sport. Most of us have moved on from “I’ve done my job, so you do yours, then they can do theirs” and now, ideally, we all do what needs to be done for the greater goal.</p><p>So where are those skills going?</p><h3>Producting our way out of design</h3><p>I am a designer by trade. But over the past 5 years I’ve spent more and more of that time working in design management or product roles. Taking my first PM role felt weird. I wouldn’t identify myself as a product manager, but actually over that time what i recognised was that the things I had missed as a designer I was doing as a PM.</p><p>I was making decisions about what users need to achieve their goals, I was prioritising them, I was sketching them and articulating it. The only thing I wasn’t doing was laying it out in a design tool. Making the aesthetic decisions. But then those were things that I was contributing to and signing off. Which at least for my team was comfortable, i hope, given my background.</p><p>I’ve had the pleasure of working with some excellent product managers in my career. But I have never met a designer without a PM horror-story. Usually someone taking up a seat and stealing credit for a designer’s hard work.</p><p>But in reality designers are less and less empowered to actually make those impactful decisions.</p><p>At this point it’s probably fair to say that I’m talking about design at scale in large organisations. Things are more than likely different for smaller businesses and boutique designers. I personally know people who design and build amazing looking websites themselves and never work with PMs. But let’s face it: the money and the stability are in big organisations and the structures and problems that come with them.</p><p>It is a Product Managers role to plan. To think about a roadmap. To communicate with stakeholders and teams to give them cover to do a good job. But more and more it feels like, at least in my experience, that means removing big decisions in favour of freeing someone up to “do the pictures”. That’s not to belittle the visual design of a product but we’ve all grown up in an industry that touts “form follows function”. Meaning, what the thing looks like is not as important as what it is or how it works.</p><p>The result is a working pattern that is telling designers “no no, this is my decision to make and it’s more important than the work that you’re going to do”. Yes, simplified, but also the reality.</p><p>This isn’t an attack on Product as a discipline. It’s an important one. As a designer I don’t want to plan the roll out of a huge piece of technology. But I do want to be present if not responsible for how we solve a user’s problem.</p><p>A good PM that is doing their job, and a good designer that is doing their job, are two sides of one coin. One structures, and plans, and prioritisies, the other explores and defines. A PM will distill research and discovery into practical tools that a designer can explore. Then together they can decide what comes first.</p><p>If a team is built up of segments of a dial, that dial has shifted. Which is fair and entirely understandable. But I want to advocate, not for turning the dial back, but for reassessing what those segments are.</p><p>The solution? I think designers need to explore Product Management as a career move. Not everyone wants to manage people but I don’t think that senior IC levels are the only solution. Maybe they are to some, but there needs to be another viable option.</p><p>Again, no beef with technical product managers or those that chose product management as a career on day one, but why not designers. Why not see product as an extension of design, and not a counterpart?</p><p>It’s easier said than done. I know. But growth isn’t easy. It doens’t mean hanging up your design chops, it means understanding that our role as designers has changed. If we want to keep that seat at the table and to be understood as more than people who make rectangles on bigger rectangles then why not join them, because we’re never going to beat them.</p><h3>So what is left for design?</h3><p>Honestly? Not much, if you ask me. The over componentisation and this shift to remove big decisions from designers isn’t going to end. And with AI improving and tools getting more powerful the more menial tasks of design will be out of the window too.</p><p>What will be left?</p><p>Hopefully a creative and design led product industry. Or at least better representation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=345d1d4a03c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Giving and receiving feedback effectively]]></title>
            <link>https://medium.com/design-bootcamp/giving-and-receiving-feedback-effectively-7d6af616c066?source=rss-ad8d0bc49599------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d6af616c066</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[resources]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Jack Sheppard]]></dc:creator>
            <pubDate>Mon, 16 Nov 2020 12:31:40 GMT</pubDate>
            <atom:updated>2020-11-21T15:36:39.684Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aGRMWdpLQCuBluVdxy-PiQ.png" /></figure><p>Everyone hates putting their work ‘out-there’ to be criticised. But constructive feedback helps teams make sure they are delivering the right thing while meeting the expectations of teams and stakeholders.</p><p>Unfortunately, though poorly given feedback is easily ignored and poorly received feedback can affect the trust given to teams. More often than not feedback isn’t asked for or given at all.</p><p>Because it’s so important, I think it’s time we stop being so afraid of it and take it seriously.</p><h3>What do we mean when we say feedback?</h3><p>“Feedback” is one of <em>those</em> words. Say it enough times and it begins to lose all meaning. But really we’re talking about involving the people who share responsibility for our work. It could be a client, it could an internal team, it could your boss.</p><p>Think about feedback as having two major types. Broad and focused.</p><h3>Broad feedback</h3><p>Broad feedback could consist of overall thoughts on a project, how it works or how it looks. In general you might ask by sharing your work or a link to a prototype, and you might send it to teammates, stakeholders or anyone. And frequently you might get it without asking.</p><h4>Pros</h4><ul><li>An opportunity to hear from people outside of your team</li><li>Casual and low effort</li><li>Implemented at your own discretion</li></ul><h4>Cons</h4><ul><li>Often unsolicited</li><li>Could be difficult to know how important the feedback is</li><li>Might be received too early or too late</li></ul><h3>Focussed feedback</h3><p>Focussed feedback usually comes in the form of established workshops, sometimes a ‘crit’ or a design review.</p><p>In a focussed discussion you might include a specific group of people, generally with some experience in contributing to your project or similar projects. The idea is that this kind of critique session is that they are ‘peer to peer’ reviews, they should be focussed and there is less room for interpretation.</p><h4>Pros</h4><ul><li>Focussed on a specific aspect of the thing being reviewed</li><li>Feedback from ‘qualified’ people</li><li>Timely</li></ul><h4>Cons</h4><ul><li>Unstructured sessions can be unhelpful</li><li>Critique often devolves into criticism</li><li>Pressure to implement all feedback received</li></ul><p>Both of these have their upsides but they’re vastly outweighed by the downsides. So a more structured session with clear boundaries will help solve some of those problems.</p><h3>Asking for feedback</h3><p>Start by setting the precedent as early as possible that your team will reach out for feedback and that interested parties should let you know if they’d like to give some. It might sound mean but find a way to articulate that unsolicited feedback is likely to be ignored.</p><p>You can take back control of the situation by being specific and structured in the way you ask for feedback, which in turn will make it much more useful for you. Spend some time planning how you will reach out to people for feedback.</p><p>I like to work backwards from the end result.</p><h4>Why do you want feedback?</h4><p>What you are trying to achieve with asking for feedback will tell you who to invite and what kind of session you might want to run.</p><p><strong>If you are</strong> trying to solve a problem you are stuck on or just looking for an alternative solution, <br><strong>Then you might</strong> run a design crit<br><strong>With</strong> other product teams</p><p><strong>If you are</strong> keeping everyone interested in the project up to date<br><strong>Then you might </strong>have a show and tell, or send out a weekly update email<br><strong>With</strong> stakeholders</p><p><strong>If you are</strong> hoping to let others input and be involved in the design process<br><strong>Then you might </strong>organise a design workshop<br><strong>With</strong> absolutely anyone</p><h4>What do you want feedback on?</h4><p>Be specific and purposeful about what you want feedback on. Aim for it to be a single slice of your work making sure there is little opportunity to feedback on something else.</p><p>It could be something like:</p><ul><li>a customer journey</li><li>a screen layout</li><li>the look and feel of a product</li><li>Specific patterns or components</li></ul><p>Once you’ve decided what you’d like people’s thoughts on write a few questions for them to answer. If you’re asking people to send you feedback without a focussed session, email them the questions.</p><p>They could be something like:</p><ul><li>“What are your thoughts on this registration process?”</li><li>“What do you think of the visual design of this screen?”</li><li>“Does this user journey make sense?”</li></ul><p>Try to be specific with your questions, limiting the opportunity for people to feedback on something that isn’t ready or relevant right now. If they do though, politely suggest that isn’t the focus of the session but you will make a note of it for later (like physically, on a post-it, so they can see you are taking them seriously.)</p><h4>Who do you want to involve?</h4><p>Once all that has been decided it will be easy for you to decide who are the most appropriate people to invite for feedback.</p><p>Limiting the number of people you’re getting feedback from at any one time will make it easier to digest, spot themes and manage. Little and often is probably easier to manage than a lot at once.</p><h3>Giving good feedback</h3><p>Giving feedback sounds easy but in reality if you’re not clear and you’re not mindful it could cause more confusion and outright anxiety. So here are some things to think about when offering up your feedback.</p><h4>Opinions are useful but not as useful as facts</h4><p>If you can back your feedback up with data, research or another provable fact then you should do it. That doesn’t mean your opinions or feelings are invalid, though, just make it clear that’s what they are and make peace with the fact that they might not be resolved.</p><h4>Positive feedback is as useful as, if not more than, negative feedback</h4><p>It is easier to offer negative feedback and that means that positive feedback is rare. It’s called <a href="https://en.wikipedia.org/wiki/Negativity_bias">negativity bias</a>.</p><p>But positive feedback helps people understand what they are doing well and what they should do more of. It also has a significant impact on the wellbeing of both the person receiving the feedback <em>and</em> the person giving it. A positive mindset reduces stress and <a href="https://www.independent.co.uk/life-style/positive-thinking-lifespan-increase-early-death-premature-mental-health-active-a7852656.html">increases lifespan</a>.</p><h4>Clarity</h4><p>A lot of time can be spent translating and deconstructing vague feedback, time that can be spent on much more important things.</p><p>When offering your thoughts be clear. Explain what you mean and the reasons you feel that way. Back it up with detail.</p><h4>Be mindful, be respectful and be kind</h4><p>Consider whether what you are saying will be useful to what’s been asked of you and be aware to stay on topic. The person running the session should be in control and this is a good opportunity to sit back and take it in.</p><p>It is likely that the person getting feedback is going to get it from more than just you. That is something to be mindful of.</p><p>Feedback is important, but asking it can be scary and giving it can sometimes be unhelpful or uncomfortable. Create the right environment, be structured and set boundaries when you ask for it. When giving feedback be mindful and respectful of the person asking for it.</p><p>If nothing else remember to be kind, you might just live longer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d6af616c066" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/giving-and-receiving-feedback-effectively-7d6af616c066">Giving and receiving feedback effectively</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 things I learned by founding —and  then quitting — a tech start-up.]]></title>
            <link>https://medium.com/@madebysheppard/5-things-i-learned-by-founding-and-then-quitting-a-tech-start-up-2ec4e0c100c?source=rss-ad8d0bc49599------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ec4e0c100c</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Jack Sheppard]]></dc:creator>
            <pubDate>Mon, 22 Jun 2020 06:01:01 GMT</pubDate>
            <atom:updated>2020-06-22T06:01:01.369Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 things I learned by founding —and then quitting — a tech start-up.</h3><p>In 2018 I resigned from a startup that I co-founded in 2015. It was a difficult decision and meant calling it a day on 3 years of long nights of hard work and throwing away what was a potentially groundbreaking idea.</p><p>The whole experience taught me a lot about myself, how I see the teams that I work with and what ‘success’ really means. It also seriously affected my happiness, my health and my commitment to the people in my life.</p><p>Here are some thoughts on my experience and the 5 main things I learned in those three years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_j9J0y83-id1AeW7KWYwjQ.jpeg" /></figure><h3>Background</h3><p>I met Oliver in 2013 or 2014. We both worked for a digital agency in Manchester. I was a design lead and he was business development manager, I was serious and stoic and introverted and he was lighthearted, outgoing and ever chatty. I think in another life we probably would never have given each other the time of day, but I’m glad we did. After all of this I still very much count Oli as a friend and am filled with — pride isn’t the right word — joy that he has found huge success post-Situation.</p><p>An ex-footballer, Oli pulled me aside one day asking to run through his business idea, and was interested in whether I could help him visualise it.</p><p>One thing led to another and we were talking about growth, investment, national release. Oli’s idea was a service that allows football scouts to review profiles, footage and game dates for budding football players. Born out of witnessing top-tier players struggle to get back into the system after injury, we felt the service could be opened up to everyone. In essence, why can’t the kids at the local park have their shot at becoming signed by professional or semi-professional teams.</p><p>A conversation with the FA, discussions with a well known premier league player and a suspect mates-rates cash injection later our sights turned to the US. We figured that the breadth of sports and the scale of the US might make for a more niche and interesting challenge. We had discussions with the Molson Family — co-owners of the Molson Coors empire, and owners of NHL team Montreal Canadiens — about investment, we were also in conversations with the NBA’s Lakers.</p><p>It was exciting and we were hopeful.</p><p>Through connections Oli had made, at this point he had relocated to LA, we had an investor lined up and additions to the team in the form of an old football friend of his that relocated to play college soccer, and a friend of his that promised experience of running a tech start-up.</p><p>We were incorporated, we had certification of shares, contracts, and everything needed to make us a legitimate business with a bright future.</p><p>It all came to a head a year or so later for reasons that would be unfair for me to discuss in detail — legal reasons that I will touch on in a bit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uCX_CTMvf27DWhwE9MBuWg.png" /></figure><h3>The top 5 things this experience taught me</h3><h4>1. A good idea is only half the battle</h4><p>We had a very good idea with very tangible and measurable outcomes and a realistic and achievable plan for growth. At a basic level we were helping athletes connect directly to teams.</p><p>However, a good idea alone does not make a business.</p><p>You can break the investment journey down into 3 stages:</p><ul><li>getting investment,</li><li>establishing yourself in your market</li><li>growth.</li></ul><p>What I wish I had understood before all of this is that in most cases you are designing a product for investment. Yes it needs to be based in a valid market need and yes it needs to be researched with real human beings, but at the very beginning you are doing it to impress a person in a suit with a big wallet. Users be damned.</p><p>Investors are out to make money, that is their business, and since they’re giving you a lot, they want to have input.</p><p>A reality can exist where you have control over your product or service’s destiny — and my advice would be to etch your business model and plan in stone: get in writing that your investment will allow you to continue on that path. You can be agile and you can pivot — but right now you need facts.</p><p>Otherwise without it, it could be your downfall, as it was ours.</p><h4>2. Trust is the most important thing to your success</h4><p>Entering into business with people that you don’t necessarily know, and receiving significant amounts of money to do it, relies on a complex and fragile system of trust.</p><p>Most importantly there needs to be a shared, and agreed, understanding amongst you and your team. Not only about what you’re doing and who for but why and how you’re doing it. This forms a foundation for trust.</p><p>On top of this there are investors and customers who are trusting you to live up to a promise. Without consideration and mindfulness it would be easy for them to lose trust.</p><p><strong>For teams<br></strong>Agree roles and responsibilities and (I’m sorry) OKRs or something along those lines.</p><p>Regularly check in with each other and offer support and discuss concerns with care and with kindness. It’s not the 1980s, kindness has a place in business now.</p><p>Appoint someone you trust to control the purse strings. And devise a process for spending money.</p><p><strong>For investors and important people<br></strong>Give ample opportunity to ask questions and provide feedback in a structured environment. Control your own (sorry again) ‘narrative’.</p><p>Send monthly roundups, or presentation decks, outlining what you’ve accomplished and where you are on the timeline. They should be bored by your progress, not anxious about your lack of it.</p><h4>3. Sticking to an MVP is almost impossible but important</h4><p>An MVP doesn’t mean unfinished but the most value you can provide with the minimum release. You can’t deliver 100% in one go, it’s unsustainable and, to be frank, as much as you think you might, you do not know where you are going to end up anyway. Zuckerbot had no idea he was building the Facebook Empire, he just thought he was perving over campus women.</p><p>The mistake we made was giving in to the pressure of bells and whistles early on. It was impossible for us, and this is not a criticism, down to the lack of maturity of the board members.</p><p>Find an investor that understands tech, or perhaps avoid investors that have no knowledge or experience in investing in tech products. The business model for a digital service is vastly different to that of physical ones.</p><p>Define what your initial product will be and how it will grow.</p><p>Aim for 100% but be honest about delivering 10% first.</p><h4><strong>4. Everyone wants a piece and they will lie to get it</strong></h4><p>When someone wins the lottery, they are advised not to tell anyone, not yet. Enjoy your new found wealth and think carefully about ‘coming-out’ to Uncle Paul — after all you’ve not heard from him since 1997.</p><p>A good idea is much like that. Be careful about who you open your door to, who you trust to help you on your journey. Don’t be ‘that guy’ that makes everyone and their dog sign an NDA before divulging your “Uber, right, but for fish”, but be aware that your business is sensitive right now. It’s a sapling.</p><p>On our journey we dealt with:</p><ul><li>An incubator agency that wanted to redesign our entire product, who attempted legal action when we exited our contract (with which there was no clause)</li><li>An ex-Premier League footballer (and millionnaire) only interested in a token investment but for a giant share of the business</li><li>Investment from a friend that needed repayment almost instantly</li><li>Countless ghosting from investment opportunities</li><li>American sports teams that were interested but only if it was exclusive to them</li><li>An investor with zero knowledge of technology</li></ul><p>..and many many more.</p><p>It is hard to spot the people that are out to take advantage of you, because they do it very, very well. But they are there. Trust your gut and be protective over the business you are growing — treat it like your favourite houseplant.</p><h4><strong>5. Know when to quit</strong></h4><p>Working 20 hour days is not healthy for anyone and quite honestly it isn’t necessary for success. Tech-bros love to tell you that’s what it takes and good for them, but it can quite literally destroy your life and your health.</p><p>The stress of juggling that along with the constant worry of the politics of the team we had built was taking its toll on me. Sleepless night after sleepless night.</p><p>I was managing design and engineering teams spread across North America, India and Australia. As well as stakeholders and investors.</p><p>What was fun quickly felt like work, and what was work then turned to dread and anxiety.</p><p>Oli is amazing at diffusing stressful situations, but ultimately without the trust of the rest of the team or a clear picture of what we’re trying to deliver, it was a sticking plaster for a much larger problem.</p><p>One evening I was summoned to an urgent call — two of the partners had gone silent for a few weeks. Oli and I caught up and it appeared there was some misappropriation of funds by one of our additional partners.</p><p>I was informed that Oli, my co-founder and friend was leaving the business to distance himself from the wrongful party and that I needed to make a decision on what I wanted to do next.</p><p>That day I tendered my resignation, effective immediately.</p><p>And that was that. 3 years of my life and blood sweat and tears gone. I wanted to run a business and back then I couldn’t imagine doing that without my co-founder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1GyNrdRtMNcSckidzIPb9A.png" /></figure><h3>Lessons learned</h3><p>All of this taught me some very valuable lessons. I learned the importance of needing more than a great idea, trust and of having a solid plan. I learned about trusting my gut and being weary of people’s intentions. I learned when to quit.</p><p>Most profoundly I learned that I have the skills, ability and mental fortitude to take a vague idea discussed over coffee to an international start-up valued at over $5m on day one.</p><p>But most of all I have learned that no amount of success, current or promised, and no amount of money is worth sacrificing your own happiness.</p><p>After quitting the start-up I focussed on my <a href="http://www.madebysheppard.com/">own business</a> — helping organisations design and deliver products and services that add value to people’s lives.</p><p>Oli has a new venture and I have complete and utter faith and confidence that it will be a resounding success.</p><p>I haven’t spoken to the other partners since the day I tendered resignation, but I do hope they learned some valuable lessons too, and I wish them the world of success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ec4e0c100c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The case for process-first design systems]]></title>
            <link>https://uxdesign.cc/process-first-design-systems-bdaeb10825f4?source=rss-ad8d0bc49599------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdaeb10825f4</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Jack Sheppard]]></dc:creator>
            <pubDate>Wed, 30 Oct 2019 10:53:06 GMT</pubDate>
            <atom:updated>2020-01-22T12:57:26.313Z</atom:updated>
            <content:encoded><![CDATA[<h4>Design systems help organisations stay consistent and empower individuals to work collaboratively — but they also help teams deliver better.</h4><p>At least in theory.</p><p>It seems like at the moment, organisations are so keen to have a (buzzword) design system that they build one that dictates how a few team members (often designers) think the organisation <em>should</em> work.</p><p>But a design system should reflect how they <em>already</em> work.</p><h3>Prioritising process</h3><p>Thinking about our design processes before pulling together patterns and components helps us see where we can streamline and improve how we work as a team. It not only helps to improve design overall but it’ll bring individuals together, create a collaborative environment and increase ownership at every stage.</p><p>My experience implementing design systems at <a href="https://coop.co.uk/designsystem">Co-op Digital</a> and Mettle (the challenger business bank from RBS), has shaped my view that the most useful and effective design systems are a ‘process-first’ design systems.</p><p>This post is about how and where to start if consistency is becoming more important to your organisation.</p><p>First, I want to bust a few myths about design systems.</p><h4>Myth 1: A pattern library is a design system</h4><p>A style guide or pattern library is just one <em>part</em> of your design system. Focussing on it is reactionary to the inconsistency in your products. It’s more efficient to solve the root cause of the inconsistency first — the process.</p><h4>Myth 2: Visual consistency is the goal</h4><p>Complete consistency is difficult and maybe impossible to achieve, especially when your organisation is juggling multiple products under the same brand.</p><p>Instead, like eyebrows, your products should be sisters not twins.</p><p>Your brand touch-points are the consistent elements to your products while everything else can vary to some degree. That’s ok.</p><h4>Myth 3: A design system should tell designers how to design</h4><p>A design system is a collection of guidance, processes and principles. It’s not hard and fast rules.</p><p>An effective system is led by emerging products and services, not dictated by them. It should set the tone and structure of how your organisation designs the things it does.</p><h4>Myth 4: A design system is only for designers</h4><p>Your design system should be relevant to everyone involved in making the products or services in your organisation, and yes, this includes designers.</p><p>The ‘design’ in design system is more about realising a product or service than it is the job your Designers do. For example, an architect designs a building, but they don’t supply the bricks, the regulations, the interiors etc. However, all of those things still contribute to the building design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lOp9iG_bWMX6sRBNuYmCNA.png" /></figure><h3>What is a system and how does it apply to design?</h3><p>A system is either a group of ‘things’ working together as part of a larger network, or an organised set of principles according to which something is ‘done’.</p><p>Both are about the interconnecting parts that rely on each other like ingredients for baking a cake.</p><p>So in that sense a <em>design</em> system is the principles and materials needed to design a product or service in a way that remains as consistent as necessary –not as consistent as <em>possible</em>.</p><p>Most design systems will contain guidance on:</p><ul><li>How to apply your brand; for example what your logo is or your colour palette and how they work within your products</li><li>Principles that your teams keep in mind while contributing to your products</li><li>How you learn from the people using your products</li><li>How you communicate with the people using your products</li><li>Solutions to common design problems</li><li>Assets or components used to solve those problems</li><li>Code used to build the assets</li></ul><p>The most comprehensive system might include much more but this depends on the team. It needs to reflect a team’s process.</p><h3>Where to start your design system</h3><p>There are hundreds of organisations tackling their own design systems to varying degrees of success and the temptation is to take inspiration from them. However keep in mind that they are solving design problems unique to their organisation, and they may not even be doing that very well.</p><p>Start with your users exactly as you would do when designing anything else. Your users are the people in your teams: designers, engineers, writers, managers, customers and stakeholders. By understanding their needs, you can begin to figure out what they need from a design system and how it can best benefit your organisation.</p><h4>Do internal research</h4><p>Learn about your team’s end-to-end process of starting a new piece of work: how decisions are made; who makes them, and what they need to make those decisions. Consider the process from inception through to the delivery of the final piece of work and how people work together.</p><p>Using this information you can then think about how to streamline and connect each process: where are there commonalities on ways of working? How does work move from one person to another?</p><p>The goal is to make each process collaborative and multidisciplinary.</p><h3>Implementing and delivering a design system</h3><h4>Map your process</h4><p>Now you’ve understood all the work that goes into making a product you can begin to map that process out. Try to generalise the process and map out each stage, creating opportunity for cross-team collaboration as you go.</p><p>Here is an example of a product process I’ve implemented:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3h5LKBZWvUPz8PgX" /></figure><p>It represents the major stages how a problem is solved from research through to implementation. There are multiple stages for review and to document each solution — this is the foundation for your design system.</p><h4>Create a space for it to live and grow</h4><p>Create a template for all the information you’re going to gather. This is where consistency <em>does</em> matter. Ideally you want everything you document to follow the same structure, have the same considerations and be consistent at every step. This is where you’re going to start to connect different disciplines and experiment with where your design system might live.</p><p>Here’s an example Trello card we used at Co-op Digital for documenting a pattern:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fTI27Arz_50OymHE" /></figure><p>You’ll notice that the problem needs to be articulated before the solution is considered, and even then the solution is dependent on user needs. In this organisation each pattern also has consideration for accessibility and research. Effectively, no guidance can exist without considering how accessible it is.</p><h4>Populating the design system</h4><p>Once you’ve established your process, and a space to collect documentation, you can begin to populate it as your products and teams evolve.</p><h3>Next steps</h3><h4>Filling in the gaps</h4><p>Perhaps you don’t have design principles and you feel they could benefit your team, or maybe you want to tighten the relationship between design and engineering.</p><h4>Test and learn</h4><p>Your design system will never be ‘done’ so re-evaluate where you’ve come from and where you’re going. It’s ok to remove content, it’s ok for something to fail, and it’s ok to start again if you need to.</p><h4>Bring the wider organisation in</h4><p>If your organisation is large there may well be a lot of people left out that could contribute. Perhaps there is a marketing team, a communications team, technical stakeholders, these are all valuable design resources.</p><h4>Create ceremonies</h4><p>Set aside time to discuss the design system, whether it’s to contribute to it, manage change or check-in with it’s users. I like to arrange a designated session once a week where new and old patterns can be discussed. Create an environment of decision making.</p><h4>Share what you learn (and what you’re struggling with)</h4><p>We’re all trying to be better at what we do so share the things you find and learn with the wider community. Lots of people would be interested to know how you get on and offer advice if you need it.</p><h3>Design systems: what are they good for?</h3><p>The main benefit of a design system isn’t in documenting your patterns and components but in streamlining your processes as a cohesive team.</p><p>By learning from the people that contribute to products at your organisation you can begin to instil a collaborative way of working by default, encourage everyone to be involved in design and free up Designers to solve broader problems with the side effect of helping them be more agile.</p><p>Written with lots of help from, and edited by, <a href="https://twitter.com/AmyMcNichol">Amy McNichol</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdaeb10825f4" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/process-first-design-systems-bdaeb10825f4">The case for process-first design systems</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get the most out of a design workshop]]></title>
            <link>https://medium.com/@madebysheppard/how-to-get-the-most-out-of-a-design-workshop-96db9eac2007?source=rss-ad8d0bc49599------2</link>
            <guid isPermaLink="false">https://medium.com/p/96db9eac2007</guid>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-workshop]]></category>
            <dc:creator><![CDATA[Jack Sheppard]]></dc:creator>
            <pubDate>Tue, 13 Mar 2018 17:09:52 GMT</pubDate>
            <atom:updated>2018-03-13T17:09:52.992Z</atom:updated>
            <content:encoded><![CDATA[<p>Designing stuff is hard. Collaboration, though, makes it easier.</p><p>The best way to collaborate is by holding workshops with your project’s stakeholders. It’ll help you gather insights, ideas, work out priorities and let you gauge their concerns or desires. Good collaboration will significantly improve the end product or service, all while strengthening relationships with stakeholders.</p><p>That said, this stuff can be hard too. ‘Collaborators’ can be uncooperative, the workshop can be unproductive and you might find it awkward to facilitate. I’ve run my fair share of design workshops and over the years they’ve become easier to facilitate and the outcomes more useful. I’ve been thinking about whether there’s a magic formula to running something engaging, collaborative and above all, worthwhile for everyone involved.</p><p>A lot of it comes down to planning and structuring the workshop carefully.</p><h3>Scene setting: creativity is collaborative</h3><p>So many of your stakeholders and even the rest of your digital team will turn up and be convinced they’re “just not creative”. And feeling that way is a real blocker for thinking outside the box and getting the most out of a workshop. It creates a ‘perfection bias’ — the idea that if it’s not perfect straight away, then it’s not right at all.</p><p>Yes, as the designer in the room you’re likely to be the only one who has the technical design skills, but helping workshop attendees to get out of the mindset that creativity is exclusive to designers is really important.</p><p>(Cringe, I know but) icebreakers are a great way to engage people’s creativity. Here are two of my favourites:</p><p><strong>Crazy eights — </strong>Give everyone five minutes to sketch eight different ways to get a golf ball inside a lemon. It’ll help people think creatively, not necessarily logically.</p><p><strong>One-handed paper aeroplane — </strong>Ask attendees to work in teams to make a paper aeroplane using their non-dominant hand. See whose plane flies the farthest. It’ll warm them up to collaborative working.</p><h3>Everyone’s here because their skills and knowledge are valued. Equally</h3><p>Making sure each person outside your digital team and even outside of design, feels valued is hard. But it’s not just difficult for you. Put yourself in someone else’s shoes.</p><p>If you’re a stakeholder and you’ve been asked to attend a design workshop, organised by a designer, it’d be easy to feel you’re being asked to do someone else’s work. Addressing this mindset at the start of a workshop is essential. You need to give attendees confidence. In the introductions, let everybody know why each person has been invited, what skills and expertise they bring. This’ll heighten each person’s confidence in their abilities, their ideas and just as importantly: confidence in you.</p><h3>Planning your workshop</h3><p>Before you send those invites think carefully about what you want to achieve, how you can do that and who’s best-placed to help you.</p><h4>Work backwards</h4><p>Start with the kind of insight you want to get out of the session. Is it user insight? Is it a list of opportunities? Is it a collection of ideas? With that in mind, consider how you’re going to get that. It could be ‘a day in the life’, journey mapping or a sketch workshop respectively.</p><h4>Invites list</h4><p>In general, you should invite stakeholders, owners, subject matter experts. Remember this is as much about maintaining relationships and designing openly as it is about gathering information.</p><h4>How many?</h4><p>Practically, make sure you have no more than 10 people. A golden rule is to only invite the amount of people you’d be comfortable with inviting to a dinner party.</p><h4>Breaks</h4><p>Adequate breaks are important. I’ve been in journey mapping workshops that take all day. If that’s the case then allow people to have structured breaks.</p><h4>Information for the invite</h4><p>Share your plans. Let everyone know the tasks you’ll be undertaking and the outcomes you’re expecting. Be ready to answer any questions.</p><h4>Prep for quiet times</h4><p>Prepare ideas or do some research ahead of the day. Inevitably, there will be quiet spots in the session.</p><h3>On the day of your workshop</h3><p>Make sure you have all the materials you need and your room prepped. Before people arrive I like to have a slide deck set up to prompt to discussions.</p><p>Consider putting slides together for:</p><ul><li>an introduction to the project</li><li>the goal of the session</li><li>prompts for discussion/sketches</li><li>thanks and next steps</li><li>who to contact</li></ul><p>A deck is also useful for setting ground rules. Manchester design event <a href="https://twitter.com/crftmcr">Craft</a> sets out a <a href="https://medium.com/@madebysheppard/craft-our-commitment-to-running-a-safe-diverse-and-welcoming-event-8659b9ce7e9c">code of conduct</a> and we (I’m co-organiser) expect all attendees to familiarise themselves with it before the event. It’s designed to help everyone feel welcome and comfortable.</p><h3>During your workshop</h3><h4>Remember, you’re the captain</h4><p>As the facilitator, people look to you as the leader of design and it’s true. You’re the one bringing people together to get a better grasp of something, that shows some excellent design chops. If you don’t know the people attending and are worried about your confidence consider your body language. Open body language conveys confidence.</p><p>(Amy Cuddy’s power pose theory is under scrutiny, but her <a href="https://www.ted.com/talks/amy_cuddy_your_body_language_shapes_who_you_are">TED talk is still super interesting</a>)</p><h4>Involve someone else</h4><p>There is nothing wrong with inviting someone else to help facilitate your session.</p><h4>Ask the right kind of questions</h4><p>Prompt people as much as you can. Provoke thought and ideas by asking hypothetical questions, but be careful not to drive people’s ideas too much, confirmation bias is a real thing.</p><h4>End the session if it’s not working out</h4><p>Running a workshop can sometimes feel like you’re playing teacher — occasionally people might be uncooperative. Sometimes, you’ll find you need more time to think, or that it is too early for the workshop or even that the room is missing someone/thing important. That’s all ok. There’s no shame in admitting this — it’s better than taking up people’s time.</p><h3>After the workshop</h3><h4>Not the end of the conversation</h4><p>Great, you’ve got all the insights you wanted. Thank every person for their specific contributions — acknowledge their skills and knowledge again. Keep them updated on what the insights were and what you’re going to do with them. Leave the door open for them to contribute further and give them the option of being updated about your progress.</p><p>You might need to run the session again with another group of people. That’s fine, if time permits, it’ll only give you more insight.</p><p>This is a method I’ve found helpful but there’s no magic formula — every workshop, every set of people is different. The important thing isn’t really running a ‘perfect’ workshop, it’s about engaging attendees effectively enough to get the best insights you can.</p><h3>Further reading:</h3><ul><li>Effective workshops by Alison Coward: <a href="http://bracketcreative.co.uk/book-effective-workshops/">http://bracketcreative.co.uk/book-effective-workshops/</a></li><li>Interviewing for Research by Andrew Travers (although not about workshops it’s still useful information for planning and figuring out the value of research): <a href="https://trvrs.co/book">https://trvrs.co/book</a></li></ul><p><strong>Workshop ideas:</strong></p><ul><li>Journey mapping: <a href="https://boagworld.com/usability/customer-journey-mapping/">https://boagworld.com/usability/customer-journey-mapping/</a></li><li>Empathy mapping: <a href="https://www.nngroup.com/articles/empathy-mapping/">https://www.nngroup.com/articles/empathy-mapping/</a></li><li>Design studio (sketching workshop): <a href="https://www.nngroup.com/articles/facilitating-design-studio-workshop/">https://www.nngroup.com/articles/facilitating-design-studio-workshop/</a></li><li>Icebreakers<br><a href="https://www.thebalance.com/top-ice-breakers-1918426">https://www.thebalance.com/top-ice-breakers-1918426</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96db9eac2007" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The crippling and anxiety inducing art of doing]]></title>
            <link>https://medium.com/@madebysheppard/the-crippling-and-anxiety-inducing-art-of-doing-432a04a997ab?source=rss-ad8d0bc49599------2</link>
            <guid isPermaLink="false">https://medium.com/p/432a04a997ab</guid>
            <category><![CDATA[doing]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Jack Sheppard]]></dc:creator>
            <pubDate>Wed, 28 Feb 2018 16:35:05 GMT</pubDate>
            <atom:updated>2018-02-28T16:39:52.375Z</atom:updated>
            <content:encoded><![CDATA[<p>The freedom of doing what you want to do, middle-fingers extended to the face of failure, is incredibly… well… freeing. It is infinitely desirable and unfortunately for many of us it’s just out of reach.</p><p>It is also a sack of festering rubbish.</p><p>Our desperate need for results. The constant pressure for validation. Not to mention the increasingly permanent digital ledger of our every social interaction. These are the batteries that power the megaphone of our doubting self.</p><p>There is no cure to that doubt by the way. No pill. No magic tweet. No hashtag. No Medium post.</p><p>Instead it’s a 10 step plan. Steps 1 through 9 are ‘do the thing’. Step 10? Repeat. And even then it doesn’t mean you’re going to be <em>good</em>. But fuck good. Who wants to be the best at something anyway? Think of the pressure.</p><p>Instead strive for ‘doing’.</p><p>The ability to use your voice, even to shout into the angry void of twitter melts, is a huge privilege and one that you should not waste.</p><p>So post your shitty drawing of a weird looking dog. Post it for you. Don’t post it for likes. Post it because in doing so you are doing more than 99% of us will ever get round to doing. Post it because the next drawing will be a little bit better. Then better after that.</p><p>Take that initiative and use it to show that one high-school bully that you don’t give a flying fuck. You like this picture of a dog and you’re going to share it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=432a04a997ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s been 15 years]]></title>
            <link>https://medium.com/@madebysheppard/its-been-15-years-bcbdd2f4730e?source=rss-ad8d0bc49599------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcbdd2f4730e</guid>
            <category><![CDATA[depression]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[mental-health]]></category>
            <dc:creator><![CDATA[Jack Sheppard]]></dc:creator>
            <pubDate>Fri, 13 Oct 2017 09:53:34 GMT</pubDate>
            <atom:updated>2017-10-13T09:53:34.700Z</atom:updated>
            <content:encoded><![CDATA[<p>A warning. This post mentions in detail some things that you might find uncomfortable. But bear with me.</p><h3>An anniversary</h3><p>This year marks a strange kind of anniversary for me, I have now been alive longer than I was before the moment I decided to take my own life. It’s weird to say out loud. It’s weird to say <em>at all</em>. Some of my closest friends will be finding this out for the first time, and some of my family will be rediscovering what I swept under the carpet so long ago.</p><p>I spent the majority of my early teenage years depressed. Life felt like a perpetually dark and wet Wednesday afternoon. The permanent feeling of 10 minutes into double maths. Or being number 172 at the post office when number 4 has just been called. I felt numb, cold, and alone. I couldn’t really imagine a future. It felt, to me at least, that my life was at an end.</p><p>15 years ago I devoured handfuls of paracetamol and ibuprofen all washed down with bottled water. I can’t remember what day or week or month it was but I remember those actions, the physical feeling, that taste, like it was this morning.</p><h3>The end</h3><p>It was a school day, I can’t remember which, it was the same as every other day. When school had finished I walked to the Lanes in Carlisle. This was the place where all my friends congregated, the outcasts and the outsiders. A church mass of faded black jeans, poorly dyed hair and bad home-piercings.</p><p>I’ll never forget the story of Mike giving himself a Prince Albert.</p><p>Anyway, it was a school day. With my hands shaking I finally went through with it. It’s not that I was planning it, actually it felt more like it was always going to happen. I had no say in the matter. It was a ritual. This was how my life was going to end.</p><p>I swallowed pill after pill until I physically couldn’t put another in my mouth. I was hunched over in a corner, hidden. Later on I would question how no-one noticed, maybe they did, maybe they didn’t care. Later again I would come to understand that they did care and that it was all in my head. Funny, that.</p><p>There isn’t any one thing I can pinpoint as responsible for how I felt. There are probably textbook examples apparent in my childhood: single parent, difficult relationship with my father, transient home life. Bullying. But there isn’t <em>one</em> big thing. I had a family that cared about me, a strong network of friends and was a perpetual B student.</p><p>In fact I had passions and dreams. I loved, and still do love, music. I immersed myself in comic books, films, animation. I dreamt of visiting Tokyo and living the life I read about and watched.</p><p>But you see in 2002 mental health wasn’t as widely spoken about as it is now. ‘Depressed’ was an insult, no-one applauded a celebrity for being outspoken, there was no support network. In fact later on in life I was told, more than once, not to mention my affliction when needing time off work for fear it would negatively affect my career. Yet here I am. With a job, and I’m mentioning it.</p><p>Anyway, it was a school day.</p><p>Almost immediately after stuffing my face with chalky white tablets, the taste of chemicals burning my tongue, I started to feel sick. I couldn’t risk the bus so walked 30 minutes home without saying goodbye to friends.</p><p>The walk took an hour.</p><p>I stopped. Started. Stopped again. My stomach was cramping. Finally I made it home. I mumbled something about feeling unwell and passed out in bed. That was all I really remember for around 2 days.</p><p>Rumour made it to school that the reason I was off was because I tried to kill myself. There was a phone call home. My mother was angry at me. Angry. I don’t blame her though, what are you supposed to feel when your youngest child, the baby, tries to commit suicide.</p><p>Eventually I came to, without the need for a trip to A&amp;E. I was back in school by the end of the week, unwell, weak, and left to deal with the aftermath alone. My friends were supportive by not acknowledging it. 15 years later I am still grateful for that. Others not so much. Jenny, tears streaming down her face, told my best friend that she loved me and would miss me. Jenny didn’t speak to me when she realised I was alive. The bullying stopped though.</p><p>It was months later after a teacher spotted my self harm that I eventually got the help that I needed. I was referred to a counsellor and spent the next 12 months taking afternoons off for therapy. It was in therapy that I learned that none of this was my fault. I had a chemical imbalance. 14 year olds aren’t <em>supposed</em> to deal with these things.</p><p>I have since learned that if I had washed those pills down with alcohol I would not have woken up.</p><h3>Not the end</h3><p>There is so much more to this story that one day I’ll talk about. Like the time Holly bought me clean razor blades because she knew I was going to self-harm regardless and it was best if I didn’t give myself blood poisoning. The time my then-girlfriend had a miscarriage at 18. Or the time I cried on Martin’s shoulder when I was 22 because the medication I was on was making me permanently nauseous.</p><p>There are also positive stories that would be remiss of me to ignore. Like Mr. Turnbull taking me out of PE to re-bandage my bloody arms. Like the Sister (catholic school, you see) that told me about her own struggle with mental health and confused sexuality. Like my brother, James, the fucking trooper, and his rain man insight and his unflinching ability to freely talk about his horrible experiences while never diminishing my own. And my mother, who finally stopped being angry at me.</p><p>My troubles with mental health will always be difficult to talk about. For the most part I am good, I am happy. It’s rare that I feel anywhere near as bad as I did 15 years ago and when I do I can recognise it early enough to take myself out of the situation and do what I need to do, to get back on form, to keep my head above water. But I will never think of myself as ‘cured’. I’m terrified that the next big thing is just around the corner.</p><h3>The beginning</h3><p>The first 15 years of my life were painful, but the 15 years since have been a rollercoaster and a whirlwind. Wonderful relationships have come and gone. My love of music allowed me to record music with friends. I went to film school. I visited Tokyo. And my career in design has introduced me to some amazing people. I’ve stood up and spoken to rooms of 100s of people and they’ve listened. To me. The quiet depressed 15 year old boy with poorly-dyed hair, home-piercings and faded black jeans. And you know what? I can’t wait for the next 15, and the next, and hopefully a few more after that.</p><p>Anyway, there’s no real point to why I’m saying any of this, except that this is my story. And I appreciate you taking the time to read it.</p><p>Oh and I’m fresh out of excuses as to why I won’t take paracetamol for this headache.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcbdd2f4730e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Craft: our commitment to running a safe, diverse, and welcoming event]]></title>
            <link>https://medium.com/@madebysheppard/craft-our-commitment-to-running-a-safe-diverse-and-welcoming-event-8659b9ce7e9c?source=rss-ad8d0bc49599------2</link>
            <guid isPermaLink="false">https://medium.com/p/8659b9ce7e9c</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[code-of-conduct]]></category>
            <category><![CDATA[craft]]></category>
            <dc:creator><![CDATA[Jack Sheppard]]></dc:creator>
            <pubDate>Fri, 06 Jan 2017 13:25:03 GMT</pubDate>
            <atom:updated>2017-01-06T13:25:47.627Z</atom:updated>
            <content:encoded><![CDATA[<p>Craft aims to be series of design events in Manchester that focus on the craft behind good design. It is born out of a feeling that we should discuss all kinds of design and we should learn from other people’s experiences not their portfolios.</p><p>I am no stranger to events in the tech and design industries. I have been lucky enough to speak at events all around Europe and even luckier to bring great minds to Manchester to speak at <a href="http://twitter.com/upfrontconf">events I have helped organise</a>. It is because of this that I appreciate the challenges we have in creating a space that people feel comfortable, happy, and able to speak out and share.</p><p>Out of all of the events I have spoken at or organised I can’t think of a single issue being raised about attendee/speaker/sponsor safety or comfort <strong>but that does not mean that it doesn’t happen</strong>.</p><p>Code of conducts are important but also a much argued about subject. I personally believe that it is counter productive to assume the worst but I also believe <strong>very strongly</strong> that a welcoming culture doesn’t come easy, it takes work and it takes — in some cases—enforcement.</p><p>That is why I want this to exist as a record of what we want to achieve with <a href="http://twitter.com/crftmcr">Craft</a> and how we are going to uphold our values.</p><h3>Our commitment</h3><p>Craft is a place where everyone is welcome. That is regardless of age, sex, gender, profession, experience, race, appearance, sexuality, religion, height, weight, shoe size, and anything else that makes us different, unique, and interesting.</p><p>Craft is a place where people are free to share their ideas, to disagree, to discuss, and to speak out about what they believe in, care about, and feel. That is with complete mindfulness of all of the things that make us different, unique, and interesting.</p><p>Craft is a place where we aim to provide a diverse range of speakers and contributors. We want you to be able to relate to our content regardless of all of the things that make you different, unique, and interesting.</p><p>Craft is a place for collaboration and contribution. It isn’t easy organising an event or to strike a balance and sometimes we will need help. We ask that you suggest anything you feel is necessary or appropriate with an understanding of that. We can’t wait to work with you.</p><p>We ask that everyone who attends or speaks or contributes to our event believes in and follows the same commitment we do. If you feel like someone is making you feel unwelcome, or you have any concerns, this is not something you should put up with. If you need or want our help or assistance please let us know.</p><p>If you yourself do not believe in our commitment and cause anyone to feel unwelcome or unsafe then you will be removed from the event.</p><p>Thank you for reading and I can’t wait to meet as many people as possible at one or all of our events.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8659b9ce7e9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>