<?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 Jennifer Heins on Medium]]></title>
        <description><![CDATA[Stories by Jennifer Heins on Medium]]></description>
        <link>https://medium.com/@heinsj?source=rss-c745ae7674e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TdcOev1Sou8uGXMA64AeGw.png</url>
            <title>Stories by Jennifer Heins on Medium</title>
            <link>https://medium.com/@heinsj?source=rss-c745ae7674e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:35:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@heinsj/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[Multi-potential-ite]]></title>
            <link>https://medium.com/@heinsj/multi-potential-ite-194033766e3c?source=rss-c745ae7674e------2</link>
            <guid isPermaLink="false">https://medium.com/p/194033766e3c</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[personality]]></category>
            <category><![CDATA[potential]]></category>
            <dc:creator><![CDATA[Jennifer Heins]]></dc:creator>
            <pubDate>Thu, 24 Feb 2022 22:53:53 GMT</pubDate>
            <atom:updated>2022-02-25T20:08:09.003Z</atom:updated>
            <content:encoded><![CDATA[<p>This TED Talk by Emilie Wapnick, called <a href="https://www.youtube.com/watch?v=4sZdcB6bjI8">Why some of us don’t have one true calling</a>, inspired me to look at my career journey from a different perspective. Emilie talks about being excited and digging into something new, getting bored, and then moving on to the next new thing, all in search of a true calling. She finally realized that one true calling is not in her nature. Instead she embraced the fact that she is interested in many things and there are some real strength in that.</p><p>So now, as I usually do, I reflect on my own life experiences. I would not have said that I resemble Emilie because I don’t jump from one new thing to the next in the way she described. However, as she talked about the strengths, it got me thinking. Here are the three strengths she highlighted:</p><ol><li>Idea synthesis — innovation sits at the intersections between fields / interests</li><li>Rapid learning — used to being a beginner, not afraid to try new things, many skills are transferable across disciplines and we bring everything we have learned with us.</li><li>Adaptability — morph into whatever you need to be in a given situation</li></ol><p>The strength of adaptability really caught my attention because I know that is one of my strengths. So I reflected back on my career starting right after college.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*swtcerRVlxtUgmVWbDQJMg.jpeg" /></figure><h3>Jen of all trades</h3><p>If I go back to the beginning of my career, I started right out of college at a small company that helped large manufacturing companies manage their Six Sigma projects. (1) I started part-time doing random word processing. (2) At that point the company started building software to track projects, and I took on writing the product documentation. (3) While trying the software to see how it worked, I found issues and told the developer about them. At this point we were ready to start rolling out the software to our customers. (4) I knew the software in and out so it made sense for me to create learning materials. (5) Oh and by the way, that also made me the logical candidate to travel around and educate various directors and managers on how to use the software. (6) During classes I observed how users worked with the software and saw potential to make it easier. When I returned home from training, I would write up my findings and open defects. (7) On top of that, I proposed improved workflows, new features, and an updated appearance to help it feel more modern. (8) After training was done and people went back to work, some users ran into issues or questions and when they called I picked up the phone and helped them or opened issues. The more people called the less patient I was for waiting for fixes and improvements. (9) And so it seems, my natural inclination was to jump in and learn how to make some of the changes myself. The changes I made started simple and grew from there. I loved being able to make changes that were easy for me and let the developer focus on the more complex technical changes.</p><p>In summary, at my first job out of college, I held these roles, without even knowing it:</p><ol><li>typist</li><li>technical writer</li><li>tester</li><li>education creator</li><li>instructor</li><li>researcher</li><li>designer</li><li>support</li><li>developer</li></ol><p>It was just natural, that when I saw a gap and/or need that I would attempt to fill it. I wasn’t afraid of failing because I was helping out, no one was expecting me to be an expert. My help was always appreciated and honestly, people were usually impressed because they knew it was new for me. I’m pretty sure impressing people was one of the things that spurred me on to continue to expand my role and skills.</p><h3>Capitalizing on adaptability</h3><p>I capitalized on the skills I learned in my first job and got a job at IBM, where I was able to continue to expand my roles and grow my skills.</p><p>Over my career at IBM I’ve held many roles that I grew into. Sometimes I saw an opportunity and innovated, and other times my managers would put me on projects that needed someone who could come in, get organized, figure out what needed to be done, and do it. Here’s an overview of the roles I’ve had over my career at IBM:</p><ol><li>information developer</li><li>information architect</li><li>content and design manager</li><li>program director of all information for a suite of products</li><li>content designer</li><li>user experience designer</li><li>user experience design lead</li><li>front-end developer, UI architect, and scrum master</li><li>user experience designer with product management tendencies :)</li></ol><p>Compared to Emilie I didn’t get bored, stop, and shift directions. My journey has been to learn, do, expand, learn, do, expand, on and on. Being able to do this in one career field and at one company has been an amazing experience. My journey has allowed me to see the big picture of software development, have empathy for all the people along the process, and be able to contribute my unique perspective and ideas to any problem we are trying to solve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=194033766e3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Administrators are users too]]></title>
            <link>https://medium.com/@heinsj/administrators-are-users-too-59b0a26f70a5?source=rss-c745ae7674e------2</link>
            <guid isPermaLink="false">https://medium.com/p/59b0a26f70a5</guid>
            <category><![CDATA[administrator]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Jennifer Heins]]></dc:creator>
            <pubDate>Wed, 09 Feb 2022 16:10:51 GMT</pubDate>
            <atom:updated>2024-11-15T13:15:46.109Z</atom:updated>
            <content:encoded><![CDATA[<p>A colleague recently shared the article “<a href="https://www.smashingmagazine.com/2022/01/software-administration-ux/">Don’t Underestimate the Software Administration UX</a>” with our organization and it struck a cord with me. The article does a good job of explaining why we as UX Designers should not ignore or diminish the work we do to improve Administrator’s experiences.</p><h3>An underserved minority</h3><p>Throughout my career I have volunteered to take on, the not so sexy, work to document and design administration experiences. I was motivated because I recognized:</p><ul><li>Administrators are an underserved minority, that everyone needs</li><li>The concepts are more technical and I like knowing how things work</li><li>Designers are not interested in doing the work, which could be due to the technical nature or perceived lack of innovation opportunities</li></ul><p>Too often I heard, “it’s OK if the documentation isn’t that clear, Administrators will understand” or “it’s OK that there are extra steps in the process because it only effects Administrators and they might not need to perform the task often”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*EsNgxgyxyO8ks09zkWDJYA.png" /></figure><h3>Foundation of the solution</h3><p>Consider solution administration as the foundation of a house. Everything else builds on top of it. System administration is the foundation of your solution.</p><p>Here are key examples of the foundation Administrators support:</p><p>1. Administrators handle <strong>deployment, configuration, and roll out</strong>, which must be completed before any users can adopt the software.</p><p>2. Administrators often handle <strong>onboarding of new users and services</strong>. While they might not be adding hundreds of services a day, they could be onboarding hundreds of users, depending on the size of the company or organization.</p><p>3. Administrators often are the <strong>help desk</strong>, which means the quicker an Administrator can fix a problem, the quicker the user is unblocked.</p><p>4. Administrators are responsible for <strong>integrating the various tools</strong> used in a company or organization. If integration is not built in, is difficult, or must be manually created, this all detracts from user’s perceived usability of the solution.</p><p>5. Administrators are tasked with <strong>upgrades and migrations</strong>, which must be completed before any users can take advantage of enhancements you’ve made in the product.</p><p>6. Administrators are responsible for <strong>data integrity and security</strong>, which are essential if users are to trust the software. Lack of trust often leads users to do more manual work, such as extracting data and working with it outside of the software.</p><p>7. Administrators are consulted when a company or organization is considering to <strong>keep or change software solutions</strong> and all of the above points will contribute to whether they are a promoter or demoter of your product.</p><h3>Administrators are users too</h3><p>Administration tasks are often at the top of customer pain point lists so don’t underestimate the value brought by improving these experiences. Administrators are users too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59b0a26f70a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TikTok inspired Enterprise design principles]]></title>
            <link>https://medium.com/@heinsj/tiktok-inspired-enterprise-design-principles-d58064aa131c?source=rss-c745ae7674e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d58064aa131c</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jennifer Heins]]></dc:creator>
            <pubDate>Mon, 25 Oct 2021 17:42:36 GMT</pubDate>
            <atom:updated>2024-11-15T13:16:36.567Z</atom:updated>
            <content:encoded><![CDATA[<p>I enjoy looking for design ideas and innovation in unexpected places. In this case, looking for ideas in the hot consumer application TikTok. TikTok feels like it’s at the polar opposite end of the design spectrum from where our complicated enterprise products reside.</p><p>Yet, with a little creative thinking, this Tiktok case study, <a href="https://growth.design/case-studies/tiktok-feed-psychology">The Psychology Behind TikTok’s Addictive Feed</a>, shows us a few design principles that can be applied to enterprise products. Here’s what I observed:</p><h3>Immersive experience</h3><ul><li>Allow a user to immerse themselves in the outcome of what they are creating. Allow them to configure / customize directly in the output and see immediate impact.</li><li>Don’t jump a user back and forth between configuration / customization and validation of their changes.</li><li>A good example of this is between Keynote and MS Office. Keynote allows you to immediately see the effect of changes you make while MS Office often makes you interact with a popup that you have to dismiss before seeing its effect.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*Jwrw4RE2dU1Fru-QY-xScg.jpeg" /></figure><h3>Well timed suggested interaction demo, that is non-intrusive</h3><ul><li>A subtle interaction demo would be a welcome shift away from a popup with words that I just don’t have time to read.</li><li>A user can comprehend an in-context visual so much faster than having to shift gears from what they are doing to read something they didn’t ask for.</li><li>An example in an enterprise product could be demonstrating that a column in a table can be moved, especially if it’s triggered after the user adds a column. Or demonstrating that a card can be moved on a canvas. Plenty more examples here.</li></ul><h3>Sticky content / options</h3><ul><li>Every time a user interacts with an application they are telling us something about themselves. We can learn from their choices, remember, and suggest in the future to save them time.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d58064aa131c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Semi-homemade design innovation]]></title>
            <link>https://medium.com/@heinsj/semi-homemade-design-innovation-cc54cab6420e?source=rss-c745ae7674e------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc54cab6420e</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jennifer Heins]]></dc:creator>
            <pubDate>Mon, 25 Oct 2021 17:40:11 GMT</pubDate>
            <atom:updated>2021-10-25T17:40:11.711Z</atom:updated>
            <content:encoded><![CDATA[<p>In cooking, making something “homemade” or from scratch means starting at the beginning by using nothing but fresh ingredients rather than prepackaged products. The phrase “semi-homemade” is used to describe a process where you start with a prepackaged, ready-to-go, set of ingredients and expand on them.</p><p>When I read or hear an interesting presentation, I find myself conjuring up “semi-homemade” ideas and designs. I can’t help but want to expand on the inspiring ideas I have just consumed. My extended outcome was not derived from my raw research and sketches but rather I humbly expand on someone else’s amazing work that planted the seed in my mind.</p><p>I hope to share my “semi-homemade” ideas here while also giving deserving attention to the inspiring work that got me there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc54cab6420e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>