<?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 Gillian Massel on Medium]]></title>
        <description><![CDATA[Stories by Gillian Massel on Medium]]></description>
        <link>https://medium.com/@gillian.massel?source=rss-9400487bf661------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Bs1TBNUwCjPEVSauKOZOfA.jpeg</url>
            <title>Stories by Gillian Massel on Medium</title>
            <link>https://medium.com/@gillian.massel?source=rss-9400487bf661------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:30:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gillian.massel/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[Content hierarchy in action]]></title>
            <link>https://medium.com/@gillian.massel/content-hierarchy-in-action-84a9529da33a?source=rss-9400487bf661------2</link>
            <guid isPermaLink="false">https://medium.com/p/84a9529da33a</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Gillian Massel]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 16:38:51 GMT</pubDate>
            <atom:updated>2020-07-08T16:38:51.957Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A person designs a content hierarchy on a piece of paper, alongside a laptop, coffee mug, and headphones." src="https://cdn-images-1.medium.com/max/1024/1*sAQxDZwMATJ9rJyLB2dDPA.jpeg" /><figcaption>Photo credit: <a href="https://burst.shopify.com/@sarahpflugphoto?utm_campaign=photo_credit&amp;utm_content=Free+Stock+Photo+of+Globe+And+Plants+On+Desk+%E2%80%94+HD+Images&amp;utm_medium=referral&amp;utm_source=credit">Sarah Pflug</a>, Burst.</figcaption></figure><h4>Without a clear content hierarchy, our designs went from bad to worse. Here’s how we used content hierarchy to fix it.</h4><p>It’s not always easy to point out a content strategist’s effect on design. Sure, we can write nice words — but writing effective UI copy is only one of <a href="https://ux.shopify.com/product-content-at-each-stage-of-a-project-55195190d8b5">many ways</a> a content strategist can improve your designs. If your content strategists are only writing copy, then you’re not tapping into the many other valuable skills they bring to the table.</p><p>One of those skills is content hierarchy. Content hierarchy is the strategic ordering of information on a web page, where the most important information receives the most emphasis, and the least important information receives the least emphasis. Normally the most important stuff goes at the top, and the least important stuff at the bottom. But there are other design tricks you can use to emphasize some pieces of content over others — tricks such as font size, spacing, visual treatment, color, etc.</p><p>Content hierarchy is something you should do before you start wireframing, but after you’ve identified your user’s needs. Content hierarchy is <strong>not </strong>the final words that are shown to the user in the interface.</p><h3>What happens when you don’t define a content hierarchy?</h3><p>Content hierarchy is one of the most effective ways of making sure that users will be able to find the information they need to accomplish their task. If you don’t define a clear content hierarchy before you start designing, then you’re likely going to end up emphasizing the wrong information. I know this because it’s exactly what happened to me when I worked on a <a href="https://en.wikipedia.org/wiki/Multi-factor_authentication">two-step authentication</a> setup experience for Shopify. Let’s take a look.</p><p>This was our first iteration of the two-step setup experience. As you can see, it was very focused on the <strong>TASK</strong> we wanted the user to accomplish.</p><figure><img alt="A screenshot of the initial draft of the two-step authentication screen." src="https://cdn-images-1.medium.com/max/1024/1*4VZxKAOFxlPK03hj__xUQQ.png" /></figure><p>Now this wasn’t a terrible first attempt. But it did make some pretty big assumptions.</p><p>First, this design assumed that all users had a pre-existing knowledge of two-step authentication. Second, our design also assumed that all users would definitely want to do this. Why wouldn’t you want to make your account more secure?!</p><p>Thankfully, our user researcher pointed out that we were making these assumptions. She suggested that we try and educate users more about two-step authentication but also give them a way to skip this step if they didn’t want to set up two-step authentication right away.</p><p>But instead of taking a step back and reconsidering how this new information should fit into the existing design, I kind of yolo’d it and said:</p><blockquote><strong>“Let’s just add a link!”</strong></blockquote><p>(Seriously tho’ — how many people have done this?)</p><p>So we added two hyperlinks: the first hyperlink took users to help documentation that explained two-step authentication in more detail. The second hyperlink let them skip the setup and continue logging in.</p><figure><img alt="A screenshot of a revised two-step authentication flow with added hyperlinks." src="https://cdn-images-1.medium.com/max/1024/1*G-j1ktu_5VmI0uQ4uRAcvw.png" /></figure><p>Satisfied with our solution to the problems identified by our user researcher, we patted ourselves on the back, and sent our designs away for usability testing. Unsurprisingly, these were the results:</p><blockquote><strong>Users didn’t understand what 2-step authentication was</strong></blockquote><blockquote><strong>Users didn’t realize they could skip this step</strong></blockquote><h3>What went wrong?</h3><p>We had anticipated these problems and tried to fix them before usability testing, but users were still struggling. It didn’t make sense! Everything they needed was right there in front of them. Why couldn’t they see our helpful hyperlinks?!</p><p>That’s when I realized….</p><p>This wasn’t a word problem. The copy was clear, concise, and easy to understand…</p><p>And it wasn’t a functionality problem either. In one way or another, the design had all the information users needed to complete the task…</p><p>This was an <strong>emphasis problem.</strong></p><p>All the right information was there, but it wasn’t showing up when it was most needed. Secondary information — such as the type of two-step authentication methods you could choose from — was being prioritized over primary information that was more important to users.</p><p>Basically, there was <strong>no content hierarchy</strong> and everything was in the wrong order.</p><h3>The problem with the current hierarchy</h3><p>Thoroughly humbled by our user feedback, I took a step back and took a hard look at the current design to try and figure out the root cause of the problem.</p><p>I realized that users actually had two decisions to make even though we were treating these decisions like one.</p><p>The first decision was whether you wanted two-step authentication at all. The second decision was which two-step method you wanted to use.</p><p>But in our current design, these decisions were in the wrong order!!! Choosing which two-step method you want is clearly a secondary decision, but in terms of visual weight and order on the page, it was coming first.</p><figure><img alt="The same screenshot of the two-step authentication flow, noting the decisions to be made." src="https://cdn-images-1.medium.com/max/936/1*JBQmf1IvRpT3CznNxsLWZQ.png" /></figure><p>On top of that, these two decisions needed very different types of information. In order to decide if you wanted two-step authentication in the first place, the user needed to know:</p><ul><li>The benefits of two-step authentication</li><li>How it works</li><li>Is it right for my business?</li></ul><p>In the current design, this decision was woefully under-supported. Most of the information needed to make this decision was buried in the help documentation instead of being emphasized up front.</p><h3>Content hierarchy to the rescue</h3><p>Now that I understood what was wrong with the content hierarchy, I knew what I had to do to fix it. First we needed to re-arrange the page so that the decisions were in the right order. Then I needed to make sure that I was including the right information to support the first decision (whether to turn on two-step authentication or not).</p><p>Working with my designers, we reorganized the content on the page to better meet our users needs.</p><figure><img alt="A screenshot of the first screen of the revised two-step authentication flow." src="https://cdn-images-1.medium.com/max/994/1*PyrdhqU-jk8AoCUi-ywVBw.png" /></figure><p>Then, if a user decided to select “Turn on two-step,” we show them a modal that explains what authentication methods they can choose. (We also added a third option — security keys!)</p><figure><img alt="A modal allowing users to select they’re preferred method of authentication." src="https://cdn-images-1.medium.com/max/882/1*Qqv3TiwwQFsJTtRC5OsKJA.png" /></figure><p>Now our design had a clear content hierarchy. Now the content was prioritized in a way that met user needs.</p><p>And we had the results to back it up. After we shipped this solution, <strong>62 percent </strong>of users turned on two-step authentication when they previously hadn’t enabled it for their store.</p><p>If that isn’t an effective content hierarchy, then I don’t know what is.</p><h3>Lessons learned</h3><p>I learned a lot of things from working on two-step authentication, but the most important realization was just how critical content hierarchy is in user experience design. Without it, we wouldn’t have achieved our business goals or met our users’ needs. Changing button colors, re-writing copy, adding icons — none of those things would have improved the experience if we hadn’t fixed the fundamental content hierarchy problem first.</p><p>On top of that, here are some other lessons I learned that I intend to apply to future projects:</p><ul><li>When you need to introduce a new piece of content, take a step back and see how it fits in to the existing hierarchy. In my case, I just jammed some links into the design, without actually thinking if it was the right place to put that content.</li><li>More than two actions on a page can be a tripwire to help you identify whether you have a content hierarchy problem. At one point, our designs had <em>six</em> different actions that users could do. Too many actions on a page can be a sign that you haven’t grouped or prioritized tasks.</li><li>Iteration is part of the process. Sometimes you have to get it wrong to get it right! At Shopify, we’ve built in ways to get feedback — from user researchers, co-workers, and even real-life users — in order to iterate and improve our designs. That’s how I was able to identify these content hierarchy problems and fix them before we shipped.</li></ul><h3>How do you use content hierarchy to solve design problems?</h3><p>Now that I’ve personally experienced the effect content hierarchy can have on design, I’m obsessed. If you have other examples or stories about content hierarchy and design, I’d love to hear ‘em! You can <a href="https://twitter.com/GillianMassel">tweet at me</a>, or email me at <a href="/service/mailto:gillian.massel@shopify.com">gillian.massel@shopify.com</a>.</p><p>Interested in solving content hierarchy problems at Shopify? We’re hiring content strategists! Check out Shopify’s spiffy <a href="https://www.shopify.com/careers/search?specialties%5B%5D=6/&amp;utm_source=uxblog&amp;utm_medium=post&amp;utm_term=a86d6">careers page</a> for more information.</p><p><em>Special thanks to the incredible designers — </em><a href="https://twitter.com/Yang_Chen1"><em>Yang Chen</em></a><em> and </em><a href="https://www.linkedin.com/in/komaljaved/"><em>Komal Javed</em></a><em> — who worked with me on this project. And thanks to our user researcher — </em><a href="https://twitter.com/FloridaDoci"><em>Florida Doci</em></a><em> — who helped us check our assumptions in the first place.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84a9529da33a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop “feeding” your users]]></title>
            <link>https://medium.com/@gillian.massel/stop-feeding-your-users-a859730a86d6?source=rss-9400487bf661------2</link>
            <guid isPermaLink="false">https://medium.com/p/a859730a86d6</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-skills]]></category>
            <dc:creator><![CDATA[Gillian Massel]]></dc:creator>
            <pubDate>Thu, 24 May 2018 17:39:04 GMT</pubDate>
            <atom:updated>2019-06-19T17:36:09.998Z</atom:updated>
            <content:encoded><![CDATA[<h4>Feeds are a popular design pattern, but it’s time we came up with something better.</h4><p>What do Facebook, Instagram, Youtube, Twitter, and LinkedIn, all have in common?</p><p>They use crazy powerful machine learning to help users sort through a ton of content to find things they actually want to see.</p><p>Oh yeah. And they all share a common design pattern:<strong> feeds.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xl_prUwCe6aCPJtrQncJ7w.png" /><figcaption>From Facebook to Youtube–feeds are EVERYWHERE!</figcaption></figure><p>Feeds are the most common way to design a <strong>recommender system</strong> (that’s a fancy term for software that uses machine learning to predict what users are most interested in seeing.) Feeds either link to more content, or allow the user to consume content without leaving the interface. Feed length varies from product to product, but they are almost always designed to facilitate scrolling, sometimes to infinity!</p><p>Feeds were designed to solve a noble and important problem: information overload. Ninety percent of the information in the world today was created in the last two years alone. Every day, <a href="https://www.forbes.com/sites/bernardmarr/2018/05/21/how-much-data-do-we-create-every-day-the-mind-blowing-stats-everyone-should-read/#4ced766460ba">2.5 quintillion bytes</a> of new content get added to the noise. How is anyone supposed to find what they need without drowning in all that!?</p><p>Enter machine learning. It promises to sort through all that information so you don’t have to. For Google or other search engine products, that means finding the content that most likely relates to your search query. For Instagram and Facebook, it means finding posts from people you care most about. For Spotify, it’s music. For Netflix, it’s movies. For Goodreads, it’s books. For Steam, it’s video games.</p><p>Machine learning is almost ubiquitous in digital products these days. Anytime a user has to sort through a lot of information, machine learning is usually there, working quietly in the background. And anytime machine learning is working quietly in the background, it almost always shows up as a feed in the front-end design.</p><blockquote>Anytime machine learning is working quietly in the background, it almost always shows up as a feed in the front-end design.</blockquote><p>At Shopify, I work on one of our machine learning products called Shopify Home. And, you guessed it, it’s a feed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lunu0exOu8F2j3pNO-g_BQ.png" /><figcaption><em>Shopify Home is a feed of cards with insights and tips for how to grow your business.</em></figcaption></figure><p>But the longer I’ve spent working on Shopify Home, the more I’ve realized that feeds create user experience problems too. Machine learning is evolving and becoming more powerful everyday, but the way we <strong><em>design</em></strong> machine learning interfaces is stuck in 2006 — the year Facebook first launched News Feed.</p><h3>Why feeds are bad design patterns</h3><p>Technology should speed up or eliminate mundane, tedious, or repetitive tasks so we have more time for things that really matter. At Shopify, this means helping our users manage their business more efficiently, so they can focus on the kind of work that makes entrepreneurship feel great — like inventing new products or building meaningful relationships with their customers.</p><p>But I’m increasingly skeptical that feeds actually save anyone time. Have you ever logged in to Facebook to look up the address of the party you’re going to tonight, only to lose 20 minutes scrolling through the News Feed before you realize what you’re doing?</p><p>Even though the address of the party is arguably the most important thing for Facebook to show you, it never shows up at the top of your News Feed! As <a href="https://journal.thriveglobal.com/how-technology-hijacks-peoples-minds-from-a-magician-and-google-s-design-ethicist-56d62ef5edf3">Tristan Harris</a> (a former product philosopher at Google) explains, this happens because, “Facebook wants to convert every reason you have for using Facebook into their reason, which is to maximize the time you spend consuming things.”</p><p>This means that feeds often pull users into content consumption and away from the task they’re trying to accomplish. That’s fine if they’re on the bus to work or if they’re just chilling on the couch, but if your product exists to help users get shit done, then feeds can actually get in the way of helping them to complete their tasks.</p><p>Feeds also create a heavy cognitive load for users. When we did user testing on Shopify’s Home feed for example, many participants remarked that there was “a lot to take in” and that they “weren’t sure what they should look at.”</p><p>Users feel this way because feeds usually show a long, uninterrupted string of objects that look very similar. Like a “Where’s Waldo” picture, feeds are information dense and visually undifferentiated — which creates a higher <a href="https://www.nngroup.com/articles/minimize-cognitive-load/">cognitive load</a>. And if the cognitive load is high, then users are more likely to feel overwhelmed and anxious. Often this means they’ll leave or go somewhere else, potentially missing a nugget of relevant information that’s buried in all the noise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TvPX4SwUcUL1AbHgF4tYQ.jpeg" /><figcaption><em>This picture has a high cognitive load because you have to find something in a sea of things that look exactly the same.</em></figcaption></figure><p>A final problem with feeds is that there’s very little predictability or information permanence. Because content is constantly moving around, users are forced to consume information they are most interested in right away lest it disappears. This creates a “now or never” situation that compromises the user’s autonomy. So instead of letting users consume at their own pace, feeds force them to engage immediately by making it difficult to retrieve content at later time.</p><h3>A better way of designing feeds</h3><p>Machine learning technology certainly isn’t going anywhere, but that doesn’t mean we need to keep recycling the same old design pattern. It is possible to create an interface powered by machine learning that doesn’t look or behave like an infinitely scrolling feed.</p><p>Thankfully, there are some brilliant people out there who are starting to think about ways to tackle the user experience problems created by feeds.</p><p>One of my favourite features about Google Now is the <strong>[More stories]</strong> button at the bottom of the feed. It’s a small touch, but it creates a “bounded experience”: a little bit of friction that prevents the user from getting lulled into the time-wasting stupor of an infinitely scrolling feed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*3ens4qdKB_RivzQi2vTptw.png" /></figure><p>Similarly, Netflix’s “broken” or “segmented” feed tries to address the problem of heavy cognitive load. In this design, movies are grouped together under different categories (Documentaries, Comedy, TV shows, etc.), which helps users narrow in on the content they are most interested in without needing look at everything at once. There’s still a lot of content competing for your attention at once, but it’s slightly more manageable than consuming everything at once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r0ENW3yUItufxDnkc5X_Vg.png" /></figure><p>But is there a way to ditch feeds all together?</p><p>The closest step I’ve seen in this direction is on the host calendar page in AirBnb.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m_-TKVxGac3weO03b0IyQA.png" /></figure><p>On the right hand side of the booking calendar, AirBnb surfaces <a href="https://medium.com/airbnb-engineering/how-we-deliver-insights-to-hosts-7d836520a38">insights</a> to help hosts better manage their listings. These insights are powered by machine learning, but they’re designed as contextual tips rather than a long scrolling feed. Users can tab through the tips one at a time, easing the cognitive load and putting an end to endless scrolling.</p><p>The AirBnB host calendar is a great example of a machine learning design that’s assistive without overwhelming, and empowering without being time consuming.</p><p>The content you need appears right when you need it, and you don’t have to scroll to find it.</p><h3>Design better feeds at Shopify</h3><p>Are you interested in designing machine learning products that have a great user experience? Then I would <strong>love</strong> to work with you at Shopify! Check out Shopify’s spiffy <a href="https://www.shopify.com/careers/search?specialties%5B%5D=6/&amp;utm_source=uxblog&amp;utm_medium=post&amp;utm_term=a86d6">careers page</a>, <a href="https://twitter.com/GillianMassel">tweet at me</a>, or email me at <a href="/service/mailto:gillian.massel@shopify.com">gillian.massel@shopify.com</a>.</p><p><em>Special thanks to Penny Allen and Gabriel Muniz Antonio for their user research that inspired this post.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a859730a86d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Shakespeare to Shopify: How I transitioned from English Lit to High Tech]]></title>
            <link>https://medium.com/inside-shopify/from-shakespeare-to-shopify-how-i-transitioned-from-english-lit-to-high-tech-fb0a8b91a45f?source=rss-9400487bf661------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb0a8b91a45f</guid>
            <category><![CDATA[university]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[internships]]></category>
            <dc:creator><![CDATA[Gillian Massel]]></dc:creator>
            <pubDate>Thu, 20 Aug 2015 17:00:02 GMT</pubDate>
            <atom:updated>2015-08-21T13:09:21.575Z</atom:updated>
            <content:encoded><![CDATA[<h4>Being a Humanities major is a tough thing these days…</h4><p>Whether you’re studying Philosophy, History, Languages, Religion, or the Performing Arts, there’s no shortage of people to remind you of the shortage of career opportunities for humanities majors. Ever since I declared my major in English Literature, I’ve had friends, family, and even friendly strangers I’ve met in the street ask me, “What are you going to do with an English degree?”</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FT4f-4CajQyg%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DT4f-4CajQyg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FT4f-4CajQyg%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/314a24d2e9d370a6403f053c78b685c1/href">https://medium.com/media/314a24d2e9d370a6403f053c78b685c1/href</a></iframe><p>I always had a hard time answering these kinds of questions because my decision to study English Literature had nothing to do with the career prospects at the end. Like most humanities majors, I enjoy learning for learning’s sake, and I was drawn to English because I’m interested in how literature can help us understand the complicated and messy business of being human. Oh, and because I was really good at finding sex jokes in Shakespeare.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*y7sezpBCi3bIvxRVd1vUhw.png" /><figcaption>Romeo &amp; Juliet 5.3 Heart-wrenching tragedy or raunchy sex comedy?</figcaption></figure><p>So when I graduated with a BA in English and was suddenly faced with the fact that the outside world might not “value” my degree in the same way I did, I balked and went to grad school. But that just delayed the inevitable. After finishing my Masters degree, I was confronted once again by the spectre of eternal unemployment. So I did what most recent grads do: I moved back in with my parents and started churning out dry, humourless cover letters in response to dry, humourless job postings.</p><p>One day, I was browsing the Internet when I came across an article about a successful tech startup running out of Ottawa. The company was called <a href="http://www.shopify.com/">Shopify</a>, but I hadn’t heard of them until that moment. I checked out the hiring page on their website and was pleasantly surprised to find that they had a posting for a marketing internship. But what really struck me was the <em>way </em>the internship was described. The description was actually funny! It was light-hearted and personable. After a month of wading through stale job descriptions, I suddenly felt like there was someone on the other side of my computer screen who wanted to get to know me as a person — and not as the bullet points on my resume.</p><p>I was inspired. I started furiously typing into the small white application box. If anyone was going to let me be creative with my cover letter, it was these guys.</p><p>This is what I submitted:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*rA1hfVHMwCwq7D_oI8x0Pg.png" /></figure><p>It was certainly unorthodox to say the least.</p><p>Whether my application made the right impression or not, it was enough to get me in the door for an interview with one of Shopify’s recruiters. I came fully prepared to stammer my way through the interview, drawing loose (<em>ahem,</em> bullshit) connections between my two English degrees and the requirements of the internship. But we didn’t talk about my experience or qualifications. In fact, we didn’t even talk about the job at all. Instead we talked about where I grew up, my family, my interests, and my hobbies. I gave a rather long-winded explanation of <a href="https://en.wikipedia.org/wiki/Water_polo">water polo</a> (which is a sport that I love). I may have even professed my deep and undying love for poutine and labrador retrievers. Our conversation felt more like the kind two people might have on a first date, rather than in a formal interview.</p><p>The next four interviews went largely the same way. Each person I met with didn’t seem to care that I didn’t know anything about marketing, or that I had no idea what SEO meant or what the hell went into creating a brand identity or increasing conversion rates. It seemed Shopify wasn’t interested in what I didn’t know; they were interested in my potential to grow and my willingness to learn.</p><p>This is when I realized that my English degree had more value than I thought. All the time that I thought I was mining Milton for spiritual enlightenment or deconstructing gender in Jamaica Kincaid, I was really teaching myself how to doggedly love the process of self-improvement. As much as I loathed writing second or third drafts of my essays, I secretly relished the criticism my professors gave me because it meant that they were helping me to become the best I could be. That kind of passion, commitment, and devotion has <em>value</em>. I think Shopify recognized that value, which is why I am still working here today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*_ke-9FIGiSNqIoC94w505w.jpeg" /><figcaption>Having a room like this in the Shopify office doesn’t hurt either. Photo credit: Andrew Reeves.</figcaption></figure><p>Part of me will always miss the joy of purchasing new books at the start of a school semester (I’m a huge nerd, I know), but my internship at Shopify helped me to convert my studies into a practical skill set that I can continually add to and improve upon. Plus, instead of making me regret my decision to pursue two (yeah that’s right, two!) degrees in English, working at Shopify has actually helped me to recognize the value of a humanities degree. It seems a tad cliche, but if studying what you love helps you to cultivate a passionate mindset, then you’d be surprised just how far Shakespeare can take you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb0a8b91a45f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-shopify/from-shakespeare-to-shopify-how-i-transitioned-from-english-lit-to-high-tech-fb0a8b91a45f">From Shakespeare to Shopify: How I transitioned from English Lit to High Tech</a> was originally published in <a href="https://medium.com/inside-shopify">Inside Shopify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>