<?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 Nikkie Ella on Medium]]></title>
        <description><![CDATA[Stories by Nikkie Ella on Medium]]></description>
        <link>https://medium.com/@nikkie.ella?source=rss-788dd7d1bf19------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*qosKLUvuV1p7wqtUwUck_g.jpeg</url>
            <title>Stories by Nikkie Ella on Medium</title>
            <link>https://medium.com/@nikkie.ella?source=rss-788dd7d1bf19------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:00:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nikkie.ella/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[11 Weeks, 11 Lessons: My Summer As A Product Design Intern at Workday]]></title>
            <link>https://medium.com/@nikkie.ella/11-weeks-11-lessons-my-summer-as-a-product-design-intern-at-workday-cb5ba48839ef?source=rss-788dd7d1bf19------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb5ba48839ef</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[workday]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Nikkie Ella]]></dc:creator>
            <pubDate>Thu, 21 Sep 2017 14:31:06 GMT</pubDate>
            <atom:updated>2017-09-21T14:31:06.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JHmKc3f9OwqktfTha0XoUw.jpeg" /></figure><p>The end of summer marked the end of my time as a Product Design intern for Workday. This was my first internship in the Bay Area and my first time working for a company a little larger than 30 people (exaggerating of course). I remember one of the first things I did after being accepted into the program was read up on the various experiences of design interns.</p><p>These personal anecdotes allowed me to set some expectations about what I could possibly learn within a 12 week program (11 for myself since I needed to leave early for a study abroad program). Needless to say my expectations were blown away and I learned more than I could’ve imagined in such a short amount of time. I decided to narrow down my experience (or shall I say User Experience?) to 11 things I learned<strong> </strong>when interning at Workday! (Because having 11 lessons in 11 weeks sounds very productive. 😉)</p><p>The things that I have listed here are mainly related to design, the workplace, and just life lessons in general! Without further ado let’s get started!</p><h3><strong>1. The Importance of Bringing the Story Back</strong></h3><p>When you are a designer not only do your designs have to speak for themselves, they also have to entice dialogue amongst your stakeholders. Conversations with managers, developers, or even other designers are central to being a designer, itself. Whenever you present your designs, it is essential to open with the right context and to tell a story that focuses on their purpose.</p><p>Don’t worry about being too repetitive! Revisiting your personas, use cases, and scenarios can clear up initial questions and ultimately save you time in the long run. This is a great exercise to conduct during design reviews so that everyone in the room knows what persona you’re designing for. You also avoid the common occurrence of receiving critique that comes from personal bias.</p><p>For me personally, I enjoyed doing this because I was constantly reminded about who and what I was designing for in the first place. I was able to scale back as well as dive deeper when I needed to. Eventually I had all the physical artifacts in relation to the design story, including persona descriptions, journey maps, what-if statements, etc. If need be I would print them out before meetings or have them as the initial slides to a presentation. Try to develop this habit early on!</p><h3><strong>2. Low-Fidelity is King</strong></h3><p>Regardless of where you stand on the debate between low and high fidelity, I learned the hard way that a young designer (especially for myself who was more interested in interaction design) should believe in the power of low-fi. Low-fidelity designs are great because you can crank up ideas quickly and as a result, test them quickly. It allowed me to focus on interaction as a whole and not to worry about specific content phrases or pixels/visuals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/0*s85cp6oZ374u6VXF." /><figcaption>Rapid paper prototyping session.</figcaption></figure><p>There was a point during the early stages of the internship where my partner and I stressed over small details that shouldn’t have been be a concern in the first place. Taking a step back from a computer and just using a pencil and paper helped bring the focus back. My favorite part of low-fidelity designing is that there’s little to no drawback to it. The work and time put into the low-fidelity designs means I won’t get emotionally attached and upset if they end up getting trashed! (Which should never happen, more on that in point #6) With the evolution of Sketch plugins and faster workflows I am very curious to see where my stance on this changes in the future but for now, long live low-fi!</p><h3><strong>3. “Fall in Love with the Problem, Not the Solution” (Aka Iterate!)</strong></h3><p>The statement above was a quote from my manager, who quoted someone else, who probably quoted someone else (in a very Michael Scott fashion). As a designer who’s early in my career, I became very focused on wanting to instill high impact change at a very large scale. I had this illusion in my head that I would have this amazing solution for my intern project and at the end everyone would be holding hands, singing kumbaya. Unfortunately, this wasn’t the case and I ended up learning two things.</p><p>The first was that I was wrong. The second was that if you don’t love having to deal with unending problems at different scales or difficulties, then you should not be a designer.</p><blockquote><strong>Ultimately, if you fall in love with the solution, you will never strive to improve the problem.</strong></blockquote><p>I realized that as a product designer I could be creating blue sky concepts one second and the next taking lego pieces (my metaphor for existing design patterns) and trying to fit those into a solution. Designing might mean scratching a idea you’ve worked on for weeks or going back to an interaction that is months old. It was fundamental to fail quickly and often. Most importantly, I needed to iterate as much as I could. Ultimately, if you fall in love with the solution, you will never strive to improve the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*nfeew_AHtUPpsqXCq0jO8g.gif" /></figure><h3><strong>4. Prototype Tools Are an Amazing Conversation Tool</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RLIE0VMcX6wFmz0z1E7v8A.png" /></figure><p>I’ll say this up front, Framer and Principle are total game changers. These tools allow you to take blue sky ideas and breathe life into them. They both allow you to get a message across to show certain interactions and how certain animations function. It beats showing screenshots or getting nauseous by quickly scrolling through Sketch artboards by a long shot.</p><p>There are certain limitations to them however:</p><ul><li>In my experience, creating nonlinear flows that rely on previous inputs are still tough, especially for screen-based prototype tools.</li><li>Speaking of time, the learning curve for both tools are pretty high. Principle is a lot easier if you have some background animating with After Effects. Framer is easier to learn if you know how to code in Javascript — you code using Coffeescript. Both have great <a href="http://principleformac.com/tutorial.html">documentation </a>and <a href="https://www.facebook.com/groups/framerjs/">communities</a> if you ever need help.</li><li>Creating prototypes on both can take a lot of time and preparation, so it is definitely best used in the later stages once things are hashed out!</li></ul><p>Regardless, I am very excited to see how these tools will develop and fit in the design process.</p><h3><strong>5. Design Collaboration Software Can Use Some Work</strong></h3><p>Pair designing in the workplace needs to be efficient and quick. Similar to coding and how Github handles things, there needs to be a way for designers to always have the most up-to-date files and record changes that have been made on the same layers/artboards.</p><p>Unfortunately, my intern partner and I didn’t have such a tool.</p><p>As result of this, we had a cluttered collection of Sketchfiles with names like <strong><em>file copy copy final(3).sketch,</em></strong> tons of miscommunication, and diverging of ideas. Fortunately, we figured out our own groove and everything worked out. But it raised the question…how can we collaborate better with design files?</p><p>Figma didn’t have the robust tools we needed from Sketch and was buggy to the point of being unusable. Later a coworker showed us Abstract, a GitHub for Sketch files, which looked very promising. Unfortunately, we weren’t able to use it because we needed pro accounts but the idea is great! (I have actually started using it for my Sketch files to keep track of progress and artboard changes after the internship.) This problem will be an intriguing point of development within the next couple of years.</p><p><a href="https://blog.prototypr.io/git-repository-for-designers-abstract-sketch-9138cf6ab9b1">GIT repository for designers as you’ve never seen: Abstract (+ Sketch)</a></p><h3><strong>6. Never Trash Your Designs!!</strong></h3><p>One of the first pieces of advice I received from my intern buddy was to never trash my designs — digital or physical. Although a solution to a design problem might not be feasible at the current moment, who’s to say it won’t be in the near future? Not throwing away my designs proved to be very useful for my intern partner and I, as we ended up revisiting old ideas when we hit a creative wall in the later stages.</p><p>Remember that you create every iteration for a reason. Even if the value isn’t clear initially, it could be a building block to something in the future!</p><p>Always make sure to keep track of older concepts by physically scanning sketches and organizing them accordingly.</p><h3><strong>7. Always Consider Inclusive Design (Accessibility FTW!)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z-GEVKDxLl1hE0MC." /><figcaption>Our designs being tested by an actual blind user</figcaption></figure><p>A little over the halfway point in my internship, my intern partner and I were challenged to incorporate accessibility within our designs. We were specifically asked to consider designs that help visually impaired people who use screen reading software. I honestly had no idea what that would entail and truth be told it was a very stressful thought.</p><p>I immediately started looking up online resources and found the <a href="https://www.w3.org/WAI/intro/wcag">Web Content Accessibility Guidelines (WCAG)</a> and <a href="http://webaim.org/">WebAIM</a>, which I had no idea existed! Riding this momentum, I went to the accessibility section on my MacBook, turned on the VoiceOver feature, and began navigating through various experiences with my eyes closed. I was amazed not only at how much information screen reading users have to take in, but also at the alarming number of web experiences that do not consider them. This motivated my partner and I to question the placement of every element within our design. We drew out what the flow would be like if we had to individually “tab” through elements.</p><p>Needless to say, we learned so much about the visual side of inclusive design and the code hierarchy involved (tags, headers, nav elements, etc.). Now I’m constantly trying to see how I can make my designs more inclusive, while finding inspiration from the pioneers of accessible design.</p><p>Now sit back and get inspired by this Microsoft Design video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJzVgtfokboY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJzVgtfokboY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJzVgtfokboY%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/bce26c4e3c870bb93df2940d3b6d113f/href">https://medium.com/media/bce26c4e3c870bb93df2940d3b6d113f/href</a></iframe><p>I definitely encourage everyone to question everyday designs to see if they really are inclusive, and challenge yourself to incorporate it in your own designs!</p><p><a href="https://uxdesign.cc/how-design-can-help-with-inclusion-9d71a60d6359">How design can help with inclusion</a></p><h3><strong>8. Content is Underrated and is a Vital Part of UX</strong></h3><p>Months ago I would design elements with content that reflected my personality. This included but was not limited to: lots of exclamation points, a positively aggressive tone, and the occasional use of slang.</p><p>That doesn’t cut it in the workforce and is poor practice.</p><p>Brands are brands for a reason and that needs to be reflected in all avenues — design included. I was fortunate enough to participate in an accelerated content workshop that taught me Workday’s voice, tone, and style standards. For a global company, one phrase could have a completely different connotation from one country to the next! This is why content is essential.</p><p><a href="https://medium.com/@kaseyjwang/content-strategy-in-design-thinking-1e15a194b4d9">Content Strategy in Design Thinking</a></p><p>Having multiple eyes on my work during “Content Clinics” was vital in helping me get a feel of how to make my designs more representative of Workday. It also made me go back to my personal work and reflect on my own design principles and how I can better represent my content.</p><h3><strong>9. Feedback is a Gift AND an Art</strong></h3><p>I, like any young designer early in their career, WAS sold on the idea that my designs are either:</p><ul><li><strong>The one and only solution.</strong></li><li><strong>Are terrible and no one should see them.</strong></li></ul><p>This contradiction is why one of my goals for my internship at Workday was to learn how to not only receive feedback but to give it effectively. I wanted to be comfortable sharing my designs with anyone — from a fellow intern to the creative director. The initially stages were not easy because my ego was getting bruised and quite frankly, I was just asking the wrong questions.</p><p>A lot of receiving feedback is based on context and what you’re asking for from the peanut gallery. Simply asking, “What do you think?” won’t get you anywhere. You have to tell the story (Back to point #1) and have them ask you questions about why you made certain decisions or if some use cases were considered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zREn8nBw8j_EAze0." /><figcaption>Asking for feedback during an Intern Hackathon session.</figcaption></figure><p>There are also different stages to ask for certain kinds of feedback. For example, I don’t necessarily care about visual feedback when I’m testing interaction elements.</p><p>As for giving feedback, it’s all about getting straight to the point. Good intentions should be assumed in critique sessions and deep dives! At the end of the day, it’s just about repetitiveness and getting used to it. The beauty of feedback is getting perspectives you might not have considered and growing that base for yourself.</p><h3><strong>10. Play Hard, Work Harder</strong></h3><p>I’ll be honest, my first couple weeks of Workday I was glued to my computer from 8:30 A.M.-5:30 P.M., just taking breaks during lunch. However, my desk was right across from the ping-pong room. This being my first internship at a bigger company, in the tech capital of the world, I wasn’t very familiar with the “work hard, play hard” culture. I felt like I was brought in to do my job and to do it well.</p><p>Eventually, I learned that there they offer all these amenities because work can get very stressful. I actually found that I worked best once I started taking small breaks during my creative struggles or after long meetings. Once you understand that balance, you maximize performance!</p><p>Also, ping-pong is really fun and is a very serious thing at Workday…so if you have any plans to work there, start practicing now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qGyF2QDt0hK2PpI9JKy_8g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nGyJfoPs3ZFFMqhjRDWpvw.jpeg" /></figure><h3><strong>11. A Great Work Environment Really Makes a Difference</strong></h3><p>Part of what made working at Workday such a pleasure, and what made it so hard to leave, was definitely the people. From the very first day, I felt comfortable and that feeling grew quickly.</p><p>It was about little things, like having our desks arranged in rows instead of cubicles, happy hours, and 1-to-1 meetings that made me feel like part of a family instead of just a team. When you’re in that kind of environment, the work just doesn’t feel like work anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xYKwX1kyY0Hou4Z56I8JIQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jVV6nHtW0eymlMa3IIU9Ew.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1HA3d-tC-hH65OKFrbZ9jg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UIjhRMZehVlGmH7U175uJw.jpeg" /></figure><p>Special shoutout to my fellow product design interns, El Risktakers, the Student Talent Performance Team, and all those that I’ve gotten to know personally throughout the past 11 weeks — it’s been a pleasure! I really hope that wherever I work in the future, I get that type of environment every day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vUSon-1enYSQ1j5Mjth5oQ.jpeg" /></figure><p>And that is it! I really hope that whether you’re looking for your first internship or well into your design career that you got something out of this. I learned a lot more than what was listed here and hope to apply all these lessons in my journey as a UX designer. I consider myself very fortunate to be a part of a program that treated its interns like actual employees and facilitated growth in various ways.</p><p>Thank you again to the wonderful design team at Workday!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb5ba48839ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>