<?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 Sheyda Sabetian on Medium]]></title>
        <description><![CDATA[Stories by Sheyda Sabetian on Medium]]></description>
        <link>https://medium.com/@sheydadesign?source=rss-2e622ff876d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cgD6iQGMt6J1yaLCvbbSnw.png</url>
            <title>Stories by Sheyda Sabetian on Medium</title>
            <link>https://medium.com/@sheydadesign?source=rss-2e622ff876d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:37:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sheydadesign/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[3 main things to ask yourself when
working on a visual brand refresh]]></title>
            <link>https://medium.com/design-bootcamp/3-main-things-to-ask-yourself-when-working-on-a-visual-brand-refresh-fab6efd5d990?source=rss-2e622ff876d------2</link>
            <guid isPermaLink="false">https://medium.com/p/fab6efd5d990</guid>
            <category><![CDATA[brand-refresh]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[brand-strategy]]></category>
            <dc:creator><![CDATA[Sheyda Sabetian]]></dc:creator>
            <pubDate>Mon, 19 Dec 2022 16:06:49 GMT</pubDate>
            <atom:updated>2022-12-20T04:50:12.341Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AM3cXeoA6c8hBw3aCXhUPA.png" /><figcaption><a href="https://www.instagram.com/sheyda.design/">@sheyda.design</a></figcaption></figure><h3>Did the brand strategy change?</h3><p>If you are thinking about refreshing your visual brand, most likely the brand strategy in your company has shifted. Is there a new vision or mission? Maybe new user benefits? This will be your north star when working on a visual refresh for your brand. Ask yourself <strong>what about the current brand doesn’t fit the new strategy anymore?</strong></p><h3>Where does your brand currently stand?</h3><p>How are you using your brand elements? Where do you use illustration and why? Same with colours, typography, etc. How are other brands approaching similar elements?</p><p>This is the right time to make mood-boards that will come in handy to understand your brand better. After this you can start the visual exploration of how you envision the brand refresh to look like. Maybe you need to change a lot to fit the new brand strategy, or maybe the changes are minor.</p><h3>Should you run user tests?</h3><p>Usually, the answer is yes. If you are going to make changes in your brand, run user tests to see if those new changes help people perceive your brand in line with the new strategy. They can be simple unmoderated tests and you can send them to a small amount of users. You can also send the same or similar test to non-users and compare the answers. This will help you understand how new users would perceive the brand vs how existing users would react to those changes on a brand they’re already familiar with.</p><p>Based on the test results, see if you need to work on more changes and run another test. Maybe the answers from the first tests will already give you enough information on what you need to set for your brand refresh. ✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fab6efd5d990" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/3-main-things-to-ask-yourself-when-working-on-a-visual-brand-refresh-fab6efd5d990">3 main things to ask yourself when
working on a visual brand refresh</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[How can designers and marketers collaborate better?]]></title>
            <link>https://medium.com/design-bootcamp/how-can-designers-and-marketers-collaborate-better-d8d525e0617d?source=rss-2e622ff876d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8d525e0617d</guid>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Sheyda Sabetian]]></dc:creator>
            <pubDate>Fri, 26 Aug 2022 13:12:48 GMT</pubDate>
            <atom:updated>2022-08-30T05:59:55.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BaQI2U0SiqML8F73MBma0A.png" /><figcaption>illustration by Catalina Williams / IG: @color_fuel</figcaption></figure><p>The struggle is real. As a graphic designer, and now lead, I’ve been working with marketing stakeholders for many years. It doesn’t matter where you work, or who you work with (it could be the nicest company ever and you’re working with the nicest marketing managers ever), you might struggle with feedback loops, missing information in briefs, misunderstandings, etc.</p><p>One thing I’ve seen happening very often is that the marketing manager or other stakeholders make a brief with what the designer considers missing information, This leads to the designer trying to decipher the meaning of it, which also leads to a design result that is not delivering what they were expecting, thus many feedback loops and frustration on both sides.</p><p>I’ve also noticed that many stakeholders who work with designers are lacking in design communication skills (particularly when writing briefs or providing feedback), and many designers lack the proper vocabulary to articulate their design decisions and defend their choices. They made the design that way for a reason, but in the end they lack either the confidence or vocabulary to properly articulate it, and as a consequence it almost always feels like the designer “loses” the argument and has to do the changes that the stakeholder is asking for.</p><p>This is why <a href="https://www.blinkist.com/">at my current workplace</a> I decided to start a set of workshops to educate stakeholders on how to better collaborate with designers, and another set of workshops for designers to be able to advocate for themselves and their design choices confidently</p><p>After these workshops, I have seen how some marketing stakeholders have changed from writing ambiguous briefs to providing some of the best briefs I’ve seen, which as a result has led to great design campaigns that required almost no feedback at all. I’ve also noticed how designers that barely spoke out about their design choices to stakeholders, changed to feeling more empowered and trusting when communicating to reach a better understanding with them. Of course, some issues will continue to happen and there’s no magic solution, but this is one that at least helped us lower some communication issues between teams.</p><p>Credit note: To make these workshops happen, I incorporated previous work from two former design leads at Blinkist (<a href="https://www.linkedin.com/in/nataliapiana/">Natalia</a> and <a href="https://www.linkedin.com/in/temi-adeniyi-b66ab842/">Temi</a>). They previously held workshops with stakeholders on giving better design feedback by identifying two causes behind poor critique — 1. emotional (subjective) feedback and 2. ambiguous feedback. Besides this, I also took some of the helpful tips from the book <a href="https://www.amazon.de/-/en/Tom-Greever/dp/1491921560">“Articulating Design Decisions”</a> by Tom Greever.</p><h3><strong>On how to help stakeholders collaborate better with designers</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-BY7UQcAGRSGshBAyxldcQ.png" /><figcaption>illustration by Catalina Williams / IG: @color_fuel</figcaption></figure><p>Ok, now you’ll want to reach out to approximately 3–5 stakeholders each time, preferably those that already work together or know each other. I don’t recommend doing this with large groups so that everyone feels comfortable and confident in sharing their ideas and thoughts.</p><p>Here’s how I structured it and how you can do it as well:</p><ol><li>First, prepare in a <a href="https://miro.com/">Miro</a> board a fictional brief and the resulting design (it can be any marketing asset: flyer, landing page, IG ad, etc.). You can grab an asset that you or your team have worked on, or you can grab something else from another company. <strong>The important thing here is that you show them a brief that has very clear objectives and target audience, and then the resulting design.</strong> You will ask them to grab post-it notes and write feedback on the design in the way that they normally do.</li><li>You can prepare some slides explaining what <strong>emotional and ambiguous feedback </strong>is and how to correct it, and end it with some practical advice in general about working with designers.</li></ol><p>Here are some of those slides I shared:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d2Z7VVtRn32FbmdNFc1F_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8qpy3IpUKKB_8oWTjZwtXw.png" /><figcaption>illustrations by Catalina Williams / IG: @color_fuel</figcaption></figure><p>The most important thing I communicated about fixing emotional and ambiguous feedback, is that they need to make sure that <strong>their feedback is coming directly from the brief they provided: what about the objectives of their brief, and the target audience is the design not achieving properly, and why?</strong> This will provide real context for the designer to better understand how to achieve the objectives better, or appeal to the specific target audience better.</p><p>Here are also some of the practical tips I shared about working with designers:</p><ul><li><strong>Ask lots of questions! </strong>This is the key to seeing things from our perspective and understanding our motivations.</li><li><strong>Don’t claim to be the user. </strong>You don’t represent the target audience any more than the designer. If you have any data that could back up something you believe in strongly, please share it. We’ll also aim to share the research and data on our side, too.</li><li><strong>Give us what we need to be successful. </strong>We need things from you to work effectively. Make those a priority (e.g. clear briefs).</li><li><strong>Give feedback in a timely manner</strong> — whether that’s specified check-ins or when the designer or creative requests feedback. Don’t provide feedback that suggests large changes during the later stages of the project.</li><li><strong>Focus on what works.</strong> This means removing the word “like” from feedback discussions in lieu of talking about what works and what doesn’t.</li><li><strong>Don’t provide solutions.</strong> Describe the issue that needs to be addressed and allow the designers to find the solutions.</li></ul><p>End the workshop by asking them to go back to the Miro board, read again the feedback they provided in the first exercise, and re-write them based on whether they thought they had made ambiguous or emotional feedback. We went over a few of them together, still having to correct some and explaining why. In the end, leave a space for them to let you know what they took from the workshop, and what they thought was missing from it as well so you can improve it on the next round of the workshop with other stakeholders.</p><p>Now, repeat this with a new set of people and wait for the magic to happen every time they have to write a brief or provide feedback next time! If you notice again that something’s off about the way they provide feedback, refer them to the link of the presentation you prepared. It would be nice if you leave this link in a very visible place for everyone who works with designers. For example, at Blinkist we placed it in the Asana backlog where they request tasks for designers, right under the brief template.</p><h3><strong>On how to help designers collaborate better with stakeholders</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gph2gNYE8gKtmIWlXowZrg.png" /><figcaption>illustration by Catalina Williams / IG: @color_fuel</figcaption></figure><p>I ̶b̶l̶i̶n̶k̶i̶f̶i̶e̶d̶ read and wrote the key takeaways from the book <a href="https://www.amazon.de/-/en/Tom-Greever/dp/1491921560">“Articulating Design Decisions”</a> by Tom Greever and made each chapter into a workshop session with my team. It’s a great book, and I recommend all designers to read it, and make their own set of workshops based on it with their team.</p><p>My team and I went over each chapter, similar to a book club, and discussed our thoughts. Then we did small exercises to practice how we would articulate our design decisions with stakeholders using real examples of projects we were working on then.</p><p>We practiced how to prepare for our responses by identifying the problems that our designs are trying to solve, defining our solutions, understanding how it affects the users, appealing to the business, and finding agreement with people.</p><p>Example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W7nymKfpRV08Mjogsiu7Dw.png" /></figure><ul><li><strong>Thank, Repeat, Prepare: </strong>Thank you for your time today. I appreciate you taking some time to provide feedback about your concerns on using black and white pictures. I will address some of the concerns you mentioned now and also talk about some of my own.</li><li><strong>Identify the problem: </strong>The objective of this project is to create a brand experience for these Guides that can highlight a more personality-driven experience. We also want users to feel excited when they see the Guides and to recognize them in the app.</li><li><strong>Define the solution: </strong>The photos we are using in the design are headshots of these Guides, zoomed-in so the users can look at their faces, and empathize with them. This way we’re making relevant the personality-driven experience that we’re aiming for. Making them black and white makes sure that the Guides look like one unified brand, as the pictures are taken all by different photographers and we don’t have control over the lighting, background, etc. At the same time, I added some color elements around the photos that give a vibrant look and feel and make the branding of the Guides distinctive, and exciting.</li><li><strong>Empathize with the user: </strong>The users will have a harder time recognizing that they’re looking at a Guide if we use colored photos, as it will lose the unified look you see here. This could potentially affect engagement with this new feature.</li><li><strong>Appeal to the business: </strong>If users recognize the branding of the Guides as soon as they see it, it will create familiarity and more people will wanna listen to them. By creating a unified brand for them, we are making it easier for them to recognize them, familiarise with them, and create excitement when they see a new one.</li><li><strong>Lock in agreement: </strong>Having the pictures in black and white helps to unify the brand in a way that will create familiarity with the users later on and they will recognize the Guides as soon as they see them. Do we all agree on that?</li></ul><p>In the end, we all gained a lot of knowledge, communication skills, and also a super cool Graduation certificate that I proudly present here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-iH9ULW3sXDWlNgXHGSTyg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8d525e0617d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-can-designers-and-marketers-collaborate-better-d8d525e0617d">How can designers and marketers collaborate better?</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[Blinkist covers revamp]]></title>
            <link>https://medium.com/design-bootcamp/blinkist-covers-revamp-fdf79ac96b82?source=rss-2e622ff876d------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdf79ac96b82</guid>
            <category><![CDATA[book-covers]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[illustration]]></category>
            <category><![CDATA[blinkist]]></category>
            <dc:creator><![CDATA[Sheyda Sabetian]]></dc:creator>
            <pubDate>Fri, 25 Jun 2021 15:30:00 GMT</pubDate>
            <atom:updated>2021-06-30T05:16:26.548Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study: on how we designed 4700+ covers in one month</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3WWO0VMiH9a7kf-ZG0ZP7w.png" /></figure><p><strong>Project duration:</strong> <br>Research: 3.5 months<br>Execution: 1.5 months</p><p><strong>Company:</strong> <br><a href="https://www.blinkist.com/">Blinkist</a></p><p><strong>Team:</strong> <br>Creative Circle</p><p><strong>My Role:</strong> <br>Project Lead</p><h3>Overview:</h3><p>I have been working at <a href="https://www.blinkist.com/">Blinkist</a> for over 2 years as a graphic designer. Ever since I started, the covers have been a considerable deal. Blinkist has a significant amount of titles, which means a serious amount of covers to produce as well (4700+ Blinks, without counting the Shortcasts and Collections). In the Creative Circle we decided it was time to give the Blink covers the treatment they deserve, as they are each made by so many people with a lot of dedication and love, and the covers should be a visual representation of all this effort as well. It’s worth mentioning that this project was done completely remote, with people from around the globe in different continents and in various timezones.</p><p>We were facing 2 main issues when tackling this project:</p><ol><li>We needed to create a sharper visual differentiation between content formats in the app, as <strong>some users weren’t able to visually differentiate between “Blinks”, “Shortcasts”, and Collections”.</strong></li><li>We also needed to differentiate between the covers within the Blink format, as <strong>some users had a hard time choosing a Blink to read or listen since the covers were comparable to one another.</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pR8GSEUZUx95qPkF_Ax9Zw.png" /></figure><h3>The method:</h3><p>There were 3 basic steps for the method I used in this project:</p><ol><li>Explore and prototype in <a href="https://www.figma.com/ui-design-tool/">Figma</a>.</li><li>Script, set up, and launch the tests either in <a href="https://www.usertesting.com/">UserTesting</a> (if they were unmoderated) or <a href="https://lookback.io/">Lookback</a> (if I moderated them).</li><li>Analyse, conclude, and draft the next steps. This was done in <a href="https://dovetailapp.com/">Dovetailapp</a>, which allows you to easily create tags and graphs for conclusions.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R6DcXX48yUFyWg2VoB1ZdA.png" /></figure><p>We tested this method 4 times, iterating the objectives and prototypes each time to further understand the problem and how to achieve a stronger solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bc5O1MQnsSC2Lhkv7cfwWw.png" /></figure><p>For this part of the project I have to make a minor pause and give a tremendous shout-out to <a href="https://www.linkedin.com/in/annebuettnerux/">Anne Büttner</a>, the senior researcher at Blinkist. She not only supported me in the first steps of the research methodology, but also took time to teach me how to set up and conduct tests, and how to use the proper tools for me to draft the analysis and conclusions of each test. She was also there as an observer in my first moderated test, where I was so apprehensive, but having her there made me feel confident that I could continue doing the research part of this project, and prospective projects by myself. Thank you, Anne!</p><h3>The process for the new Blink covers:</h3><h4>1. Find talent:</h4><p>We hired 25 freelancers to produce 4700+ covers. I reached out to various illustration agencies, until I found one called <a href="https://www.owlillustration.com/">Owl</a> that could meet our expectations and deadline. They sent an extensive list of illustrators from which we chose some that could fit the art direction that we needed for this project. I also reached out to other illustrators that I knew, and others that I didn’t know but follow on Instagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VUVAOwxKknHoflcriAE0HQ.png" /></figure><h4>2. Onboard talent:</h4><p>I created a set of guidelines on Figma that showed the freelancers step by step how to create the covers. I also made a video tutorial so that they could easily understand some key things on Figma (most of them had never used it before).</p><p>The guidelines included things like how to set up the background color, and which fonts to use. In terms of fonts, I selected a limited amount of 6 fonts that they could use and combine in the covers, and also some variations that worked well together. I wanted to remove any cognitive load for them to not have to think about colours and fonts and leave the most essential thing: the content. Now they just had to think about a concept to illustrate that could represent the content of the book.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17autEzo9K-foUhC57mafQ.png" /></figure><h4>3. Production:</h4><p>The freelancers produced their first 10 covers in a week. Then, <a href="https://www.linkedin.com/in/aitanabarredo/">Aitana Barredo</a> (our design freelance superstar) and I did the initial quality check. After we gave this first feedback, they produced around 100–300 covers each, depending on how fast they could work in the timeline we had.</p><p>We provided a spreadsheet that had all the information the freelancers needed: the name of the book, the author, the description, the color code for the background, and important: the name of the frame that would be the name of file when exported. As this process was automated when uploading them into the app, it was very necessary for the covers to have the same name as the early covers. If they didn’t, the admin tool from the app wouldn’t find them, and it would be as if they never existed. Most of the issues we had with missing covers stemmed from the frame name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jS_g32CFHWv3jilA4yhWjQ.png" /></figure><p>The 25 freelancers worked in one Figma file for all the covers in English, and another Figma file for all the covers in German. They each had a page in the Figma file with their name, which was essentially their individual workspace. Some of them would do the illustrations in <a href="https://www.adobe.com/products/illustrator.html">Adobe Illustrator</a> and then paste them on Figma, while others would draw their illustrations directly in Figma.</p><p>When they finished a cover, they would paste each cover into another page that corresponded with the first letter of the book title.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rARN4pvXcD9hCNVQ0E2Epw.png" /></figure><p><a href="https://www.linkedin.com/in/petrakemkova/">Petra Kemkova</a> from Owl agency (who was doing a bit of project management as well) set for us a <a href="https://slack.com/">Slack</a> project, where we had different channels in which we could communicate depending on the subject. We had one channel where they could find the brief and all the files and assets they needed, another channel where they could ask any question they had, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OMbm6cNMezh_jmGJP_Ktlw.png" /></figure><h4>4. Quality Check:</h4><p>Aitana and I would check every day the Figma pages where the freelancers were pasting their final covers, and we would either write them feedback if needed, or move the final covers to another Figma file that we named “Master file”. In the Master file we had all the final covers that only Aitana and I could access. The reason behind this was because when you have 25 people working in one Figma file, and all of them can edit and change things, it could easily turn into a catastrophe.</p><p>In the Master file, Aitana and I would also fix and change certain elements and details in some covers, like contrast, fonts, colors, and some shapes. These were cases where doing it ourselves would save us further time than giving feedback back and forth for slighter things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-HS4PfPndXIkVngBN4M4HQ.png" /></figure><h4>5. Exporting</h4><p>We also had the Master files separated in pages by letters, and the <a href="https://www.google.com/drive/">drive</a> where I uploaded all the covers was also in folders by letter. When we had made all the changes we needed for the quality check of the covers, I would grab all the covers in one page, export them, then check again that everything was right. Sometimes, some elements were outside of the frame, so when I exported them there would be maybe text or even the illustration missing from the cover. I had to check again all of them and in these cases export again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FdA4nXWTIOhmsqP2GFtaTQ.png" /></figure><h3>Labels for Content Differentiation</h3><p>After testing, we also realised we needed to add labels or tags with an icon and a color specific to each type of content format to allow better differentiation between the content. This way, the responsibility of differentiation relies not only in the covers but also on the UI.</p><p>This part of the project would also not have been achievable without the work of the amazing principal product designer from Blinkist, <a href="https://www.linkedin.com/in/justyna-kusa-90b31a76/">Justyna Kusa</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gdunpgh_Gn3hRxQkHgjCEg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y91V8CmKf6oqAyLd1003eQ.png" /></figure><p>All in all, it was a huge effort, but in the end it was beyond worth it! You can see some of the final results in the video below (and also in the <a href="https://www.blinkist.com/">Blinkist</a> app if you download it!)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEUUIroyPfBc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEUUIroyPfBc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEUUIroyPfBc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/66a7dffad69ce5db28c1e6c7f6dc919f/href">https://medium.com/media/66a7dffad69ce5db28c1e6c7f6dc919f/href</a></iframe><p>Last but not least, a tremendous shout-out to <a href="https://www.linkedin.com/in/koviljka/">Kae Neskovic</a> for all her support and advice during this project, to <a href="https://www.linkedin.com/in/chauncitoney/">Chaunci Toney</a> for helping me proofread this story, and to all the following people, without whom this project would not have been as amazing as it is, and as swift as it was.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LZk4IIJIrIVmsqr0oXRWow.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdf79ac96b82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/blinkist-covers-revamp-fdf79ac96b82">Blinkist covers revamp</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>
    </channel>
</rss>