<?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[Auth0 - Medium]]></title>
        <description><![CDATA[Simplifying the complexity of identity design. - Medium]]></description>
        <link>https://medium.com/auth0-design?source=rss----640ea82476da---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Auth0 - Medium</title>
            <link>https://medium.com/auth0-design?source=rss----640ea82476da---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:57:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/auth0-design" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Design Spotlight: An interview with Ali Salem]]></title>
            <link>https://medium.com/auth0-design/design-spotlight-an-interview-with-ali-salem-745659320a32?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/745659320a32</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[design-interview]]></category>
            <category><![CDATA[design-leadership]]></category>
            <dc:creator><![CDATA[pavi.design]]></dc:creator>
            <pubDate>Mon, 26 Jun 2023 14:04:15 GMT</pubDate>
            <atom:updated>2023-06-26T16:10:51.208Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/a0f92448896b">Ali Salem</a> is a Toronto-based Staff Product Designer dedicated to crafting seamless design systems. When he’s not weaving his magic to enhance the consistency of design features and elevating customer experience, you’ll find him venturing outdoors, pursuing a Master of Design, or playing the latest Call of Duty game 🎮.</p><p><em>This interview was monitored by </em><a href="https://medium.com/u/11d7966fc0c6"><em>Pavi Designs</em></a><em> (Sr. Product Designer).</em></p><figure><img alt="Headshot of Ali centered in the middle against an abstract illustration" src="https://cdn-images-1.medium.com/max/1024/1*2OjuncLgfNUMUh-g_vmdfQ.png" /><figcaption>Headshot of Ali centered in the middle against an abstract illustration</figcaption></figure><h4>Hi Ali, tell us about yourself.</h4><p>Believe it or not, I’m one of those rare people who genuinely like doing their taxes. And, being from Canada, it’s like embracing the cold winter with open arms! A little more about me — I relocated to the Toronto Area in 2018 after a six-year stay in Dubai, UAE. Despite these moves, I still hold my Egyptian roots close to my heart and visit Cairo every year to connect with my family. I’m an outdoor enthusiast who loves exploring new places and experiences alongside my wife, Esraa. Yet, when the latest Call of Duty game is released, you’ll likely find me indoors, controller in hand!</p><figure><img alt="Ali loves cats. Here’s a photo of his cats Pixel and Mishmish meeting each other for the first time." src="https://cdn-images-1.medium.com/max/1024/0*vciM7iPkOXyNB3Vm" /><figcaption>Ali loves cats. Here’s a photo of his cats Pixel and Mishmish meeting each other for the first time.</figcaption></figure><p>I’m currently leading Auth0’s design system, <a href="https://www.npmjs.com/package/@auth0/quantum-product">Quantum</a>, with the help of our talented design system working group. We’re continuously on the lookout for ways to enhance the consistency and efficiency of how we design and build features, ensuring our customers have a reliable and intuitive experience. I’m also pursuing my Master of Design in Strategic Foresight and Innovation at OCAD University, with an aim to understand the complex relationship between people, businesses, and innovation.</p><h4>What led you into design systems?</h4><p>In 2016 I was working at one of the leading telecommunications companies in the Middle East, called Etisalat. I became interested in design systems because I saw an opportunity to enhance how my team and I were working together. We were creating designs for various screen sizes, from smartphones and tablets to huge 120-inch touch displays — each bringing its distinct challenges and insights to the table.</p><p>Part of my job was managing our UI component library, and my goal was to help our team work quicker by getting rid of repetitive tasks — like designing the same button or input field multiple times. In the midst of this, I began to realize how all our work was interconnected. A small change in one place could make a big difference somewhere else. This experience was my first encounter with the concept of systems thinking, which helped me see that all our work is part of a bigger picture. Systems thinking has now become a key part of how I approach my work and tackle problems.</p><h4>Who or what inspires you?</h4><p>I find inspiration in many things, but these four really stand out to me.</p><ul><li><strong>Quality and attention to detail:</strong> There’s just something about a well-made product that makes you realize how much thought is put behind it. It reminds me that if we put our hearts into our work, we can create something truly special. Examples include: German cars from the ’80s and ’90s, as well as many Apple products like the Mac Pro and Pro Display XDR.</li><li><strong>Hard work:</strong> Seeing people put their all into what they’re doing, pushing through tough times and still going strong, motivates me immensely.</li><li><strong>Art — especially music and cinematography:</strong> It’s amazing how artists can take a blank canvas and transform it into something that tells a story or makes you feel a certain way. It helps me think creatively and approach problems from new angles. Music, in particular, helps me connect with places and recall great memories with loved ones. As I spend a significant amount of time on YouTube, I find myself drawn to content creators who apply creative storytelling in their work. <a href="https://www.youtube.com/@casey">Casey Neistat</a> stands out in this respect, using filmmaking techniques to create dynamic and highlighly engaging narratives out of simple everyday events.</li><li><strong>Kindness:</strong> Whenever I see someone doing a kind deed, no matter how small, it makes me want to do better in my own life. It reminds me that our work should not only serve functional purposes, but also contribute to making the world a gentler, more compassionate place.</li></ul><figure><img alt="A photo of the Apple Pro Display XDR and Mac Pro which highlight great attention to detail" src="https://cdn-images-1.medium.com/max/1024/0*QFMHCJ0aUMcH5B17" /><figcaption>A photo of the Apple Pro Display XDR and Mac Pro which highlight great attention to detail</figcaption></figure><h4>How do you maintain your creativity?</h4><p>Steve Jobs once famously said, “Creativity is just connecting things,” and I couldn’t agree more. In my opinion, the more experiences we expose ourselves to, the greater our capacity for creativity becomes. It’s almost like our brains are vibrant boxes of Lego, filled with countless pieces waiting to be connected. The more we collect these pieces — whether they be facts, experiences, or memories — the more skilled we become at constructing something truly remarkable.</p><p>I believe curiosity is an essential ingredient in acquiring knowledge as part of the creative process. It’s a powerful motivator, driving us to explore, discover, and gain a deeper understanding of the world around us. I try to dedicate a portion of my day to learning about new topics, often delving into short articles or immersing myself in informative documentaries on YouTube or Netflix. I also found that experiences involving other people are particularly impactful. Meeting individuals from different walks of life, engaging in challenging discussions, and even resolving conflicts have all given me new perspectives.</p><p>Lastly, I consider myself incredibly fortunate to leverage my master’s degree program at OCAD University to test out fresh ideas and venture into unexplored visual territories. The inspiration for these projects often stems from the numerous experiences I encounter in my everyday life.</p><figure><img alt="Design explorations by Ali as part of his Master of Design program at OCAD University" src="https://cdn-images-1.medium.com/max/1024/0*DhEQXaj4G2tzJd7f" /><figcaption>Design explorations by Ali as part of his Master of Design program at OCAD University</figcaption></figure><h4>Can you show us your workspace and walk us through your typical workday?</h4><p>For sure! I like to maintain simplicity in my workspace, as it helps me stay focused and productive. For quick note-taking and capturing thoughts on the go, I always keep a trusty notebook by my side. Later, I transfer those notes to Notion, my go-to note-taking app.</p><p>As for my daily routine, I’m a morning person, usually up and about between 6:30 and 7:00 AM. I like to kick off my mornings by catching up on the latest news and browsing through Twitter and Reddit to stay updated. On most days, I go for short walks to energize before starting my day at around 8:30 AM.</p><figure><img alt="A photo of Ali’s office setup" src="https://cdn-images-1.medium.com/max/1024/0*Rn3rivUvH02XFeUs" /><figcaption>A photo of Ali’s office setup</figcaption></figure><p>My day is a balanced mix of meetings, planning, and hands-on work. I make it a point to dedicate some time each week to update our design system roadmap and capture opportunities in our backlog. This practice helps us maintain focus and stay on course. One of my favorite weekly events is our design shareouts and critique sessions. It’s a great opportunity to keep up with our team’s work and ensure we’re all on the same page.</p><p>When the workday ends, my wife and I try to make the most of the long summer days by taking leisurely walks, cooking dinner together, or simply relaxing outdoors. These moments make each day special, helping me unwind, prepare, and look forward to the next day.</p><h4>What is one design system component that has been a challenge to design or implement?</h4><p>That’s an easy one: tables. They are incredibly tricky as they come in all shapes and sizes and can be packed with interactive features like sorting, filtering, expanding, and collapsing. They are also often difficult to implement responsively, especially using native HTML markup. We try our best to simplify and abstract components in our Figma library, but tables can really test our patience.</p><h4>Let’s say time travel exists. What’s one piece of advice you would give yourself at the start of your career?</h4><p>Embrace the imposter syndrome. Stepping into the world of design at the age of 13 was an exciting learning journey. However, as I dove in deeper, I began to feel like an outsider — a feeling that was amplified by the absence of a structured educational background in design. But then, I slowly began to realize that this unsettling feeling is actually a sign of growth. It means I’m pushing myself and my creative abilities further and recognizing my potential.</p><p>Here’s a follow-up piece of advice — don’t wait around for a Master Yoda to offer reassurances. Every design you create or project you contribute to is a learning experience and an opportunity to refine and expand your skills. Feeling uncertain or out of place can be a natural part of the creative process. Don’t resist these feelings! Instead, lean into them and recognize them as proof of your dedication to improving your craft. Remember, all great designers had to start somewhere and face their own self-doubt. Your journey as a designer is unique. It’s not about waiting for someone to validate your skills, but about taking charge, exploring, and refining your creative potential.</p><h4>What are you currently reading or listening to?</h4><p>I recently came across a book called “Bunker: Building for the End Times” by Bradley Garrett. This book delves into the concept of bunkers, which are secure places constructed to shelter humanity from significant catastrophes such as diseases, climate change, or war. Interestingly, this resembles the vaults featured in one of my all-time favourite role-playing games, <a href="https://fallout.bethesda.net/">Fallout</a>, developed by Bethesda. The game is set in a world ravaged by nuclear war and offers a unique combination of retro and futuristic settings. It includes large underground shelters built by a group called Vault-Tec, designed to protect people from nuclear fallout.</p><figure><img alt="The cover of “Bunker: Building for the End Times” by Bradley Garrett" src="https://cdn-images-1.medium.com/max/1024/0*hxl9zNOgYCgTcitu" /><figcaption>The cover of “Bunker: Building for the End Times” by Bradley Garrett</figcaption></figure><p>Garrett’s book explores the increasing trend of individuals preparing for major disasters, a practice often dubbed as “prepping” or gearing up for “Doomsday.” According to Garrett, these bunkers embody our deepest fears, and their signs can be spotted everywhere — in shopping centres, gated communities, and even the cars we drive. But most notably, these bunkers exist in our minds, implying that we’re constantly thinking about how to maintain our safety — pretty wild!</p><p>On a different note, I absolutely enjoy listening to synthwave music. It’s the ’80s vibe that really gets me.</p><h4>What would you tell others who want to get into designing for design systems?</h4><p>I believe it’s essential to recognize that your contributions to a design system can go well beyond designing individual UI components. In fact, a well-implemented design system can profoundly shape the design methodologies within your company. It can affect not only the process of design decision-making but also influence team collaboration and, ultimately, the way products are built. For instance, our design system working group engages with cross-functional teams to identify and implement design patterns that further enhance consistency in our experiences.</p><p>The systems thinking approach, which I previously touched upon, plays a pivotal role here. This approach moves away from handling individual problems in isolation. Instead, it encourages us to grasp the interconnectedness and interdependencies among different parts of the product. By recognizing patterns at a holistic level and considering the potential impacts of changes to one area on the others, we can contribute to building robust design systems that better serve our teams.</p><figure><img alt="Closing image with the word, Spotlight, centered against a light purple gradient with abstract patterns" src="https://cdn-images-1.medium.com/max/1024/1*qzQqpH8N1mNKwMvfuuRq-g.png" /><figcaption>Closing image with the word, Spotlight, centered against a light purple gradient with abstract patterns</figcaption></figure><h4><strong>Where can people connect with you?</strong></h4><p>Please join me on <a href="https://twitter.com/alisalem">Twitter</a> or <a href="https://www.linkedin.com/in/alixsalem">LinkedIn</a>. I’m always up for a good talk about design systems, Formula 1, or video games. Looking forward to chatting!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=745659320a32" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/design-spotlight-an-interview-with-ali-salem-745659320a32">Design Spotlight: An interview with Ali Salem</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Sociology to UX Research]]></title>
            <link>https://medium.com/auth0-design/from-sociology-to-ux-research-2f788954ee9c?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/2f788954ee9c</guid>
            <category><![CDATA[social-science]]></category>
            <category><![CDATA[sociology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Tianyi Qian]]></dc:creator>
            <pubDate>Mon, 15 May 2023 21:21:18 GMT</pubDate>
            <atom:updated>2023-05-15T21:21:18.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rx5jOYdYx4jbcPjVFziQdw.png" /><figcaption>An isometric illustration of UX Research tools and ideas.</figcaption></figure><blockquote>“We are not going in circles, we are going upwards. The path is a spiral; we have already climbed many steps.”</blockquote><blockquote>– Siddhartha <em>by Hermann Hesse</em></blockquote><p>Making a career pivot to UX research is hard work, and surprisingly, my background in sociology hasn’t made this transition any easier, considering UX research borrows heavily from social sciences research methods. Having struggled myself as I endeavoured to define my own career path, I want to share with you the struggles that I encountered in defining my own career path as a sociology student and the story of how I discovered UX research. I hope aspiring UX researchers coming from similar backgrounds will find this article useful.</p><h4>The Missing Piece</h4><p>What I struggled with the most when I started out to look for a job after college was, well, it was very difficult to pinpoint how to translate my skills and talent in working out abstruse theories into a practical role in the job market.</p><p>My safe bets were data science, law school, or Ph.D. UX research did not end up on that list because I wasn’t aware of this field.</p><p>UX research remained an unknown foreign land on my career exploration map for the next 3 years until 2020, the year I graduated from my master’s program.</p><p>Looking back, I realize, UX research has been the missing piece to the puzzle. It didn’t exist as a career option when I made the decision to apply for graduate school in 2019.</p><p>My college friends seemed to have more of a clear idea of what they wanted to do. Some majored in business; others majored in economics, statistics, etc. I remember in my senior year, I met a young woman at one of my sociology classes. She also majored in sociology, but she shared with me that she planned to do a computer science minor because it’s easier to find jobs.</p><p>When I went to career fairs, I felt disconnected and struggled to find anything relevant to my skills. The best I could find were teaching English and business consulting, but none sparked my interest.</p><p>Thinking about it now, it’s very surprising that there was so little mention of UX research as a career option when I was a student in sociology, although there are so many similarities between UX research and sociology. Even as I tried to search for options after graduation, it still felt like swimming in a giant ocean with an abundance of options. I knew I could make a case for advertising, for instance, but it felt far off. All I knew was I was passionate about research and sociology, and the closest path that I could think of was to apply for grad school.</p><p>The anxiety of defining my own career path became real when I was waiting for my grad school application decisions. I stayed with my parents in China then. It was a very anxiety-inducing period. As rejection letters started to pile up, my parents became increasingly worried about me not being able to get accepted to any graduate programs and started to persuade me to look for jobs in China.</p><p>When I finally used my parents’ referral and asked the connection about any opportunities to work at their organization, they were surprised that I would even consider working at their organization. They seemed to think I’m capable of something much better. It was a strange thing to be told when I had little clue about where I could work. But luckily, before this anxiety became too taxing, I received the welcome package to University of Chicago’s graduate program. What a relief, I thought. I could finally have some peace and go back to study again in the US.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVJjDRxHug7AHCq0mVqQUw.png" /><figcaption>Decorative image: an illustration of a pencil on a gradient background of green and yellow.</figcaption></figure><h4>An Accidental Discovery</h4><p>Going to graduate school was a wonderful, albeit strange, experience during the pandemic. My graduate program was short but packed with best-of-class research training in the social sciences. I needed to take classes in theory and methods, write a master’s thesis, think about my next step, and somehow figure out all these in one year.</p><p>But things quickly turned around. As I started to understand what it took to do academic research, I realized I was not yet committed to academic research and a Ph.D. route. This actually made things easier because crossing out one path opened up multitudes of possibilities. Life started again, and now in a different direction. I started to apply for positions and go to career fairs with the goal of finding a position in data analysis while wrapping up my MA thesis.</p><p>And I suppose what happened next is the anticlimax of my story. Three months into my job hunt, a random encounter with a recruiter on LinkedIn officially kicked off my career in UX research. The recruiter was looking for a candidate to hire for a mixed-method UX researcher role. The actual job interview didn’t land me the offer, but it gave me a peek into what this field was about, and that’s how I first encountered UX research. Not through conversations with career counselors or career conferences at school, but through a totally random encounter with a tech recruiter. This unfolded a whole new chapter in my life. I cared not about the results of the job interview because what mattered was that I discovered a new land, but at the same time, I found it familiar and inviting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MkIG5gDGaRVqSY226pcwsA.png" /><figcaption>A pull quote which states: I encountered UX research not through conversations with career counselors or conferences but through an unexpected encounter with a tech recruiter.</figcaption></figure><p>Filled with excitement about my discovery, I started to look for resources to learn more about UX research. I took UX research courses on LinkedIn Learning and Coursera. I also started to leverage what I learned through leading projects when I found out that founders at the start-up where I interned were interested in doing a UX research project to validate their value propositions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HmwteodnKcB0OGlkwhtT9Q.png" /><figcaption>Decorative image: an illustration of binoculars on a gradient background of pink and yellow.</figcaption></figure><h4>Building My Story as a UX Researcher</h4><p>But once I decided to start a career, I realized that although I knew about the similarities between UX research and sociology, the recruiters that interviewed me, especially recruiters vs. UX research managers, didn’t understand the connections between my major and UX research. They might have been looking for candidates who had a major in Human-computer interaction or psychology, etc. The relevance of Social Science to UX research was less understood from recruiters’ perspective, esp. for agency-filled contractor positions.</p><p>So it became apparent to me that I needed to translate my skillsets to recruiters and share that not only was my graduate research experience relevant to UX research, but it’s also an invaluable addition to my training as a UX researcher.</p><p>For instance, I tried to translate my research projects at grad school into UX research projects both on my resume and during job interviews. When describing a research project during an interview with a recruiter, I tried to break it down into three sections: the goal (what I set out to study), the what and why (what I did and why I chose particular research methods), and the results (implications of research). In my current job, I find that we follow similar structures when delivering research findings, which is not surprising.</p><p>Bringing experience with research methods is great if you have done research in grad school using these methods. Perhaps the most common methods used in UX research are usability tests, interviews, and surveys. If you have any research projects where you can directly speak to these experiences, it will be a great addition to your UX research repertoire and definitely something you should bring up in your job interview.</p><p>In my MA thesis, I didn’t draw on surveys or interviews, so I tried to bring up my internship experience with the startup, where I did customer interviews and other UX research projects I did with non-profits that could help demonstrate my familiarity with qualitative research since that was my focus during the job hunt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A1X0le31pLhyMzvLz6nkyw.png" /><figcaption>Decorative image: an illustration of a compass on a blue gradient.</figcaption></figure><h4>Resources for Your UXR Journey</h4><p>I hope you find inspiration in my story, and I hope my article has sparked some interest in learning more about UX research.</p><p>To learn more about UX research methods and when to apply them, I encourage you to check out Nielsen Norman Group’s article on <a href="https://www.nngroup.com/articles/which-ux-research-methods/">When to Use Which User-Experience Research Methods</a>. I would also recommend you check out <a href="https://www.youtube.com/c/AonaTalks">Aona’s YouTube Channel</a>, which shares many great tips on how to start your career as a UX researcher as well as on how to prepare for job interviews.</p><p>I mentioned qualitative research in the last section. However, if you are interested in learning about quantitative UX research and what that encompasses, I recommend you check out <a href="http://r-marketing.r-forge.r-project.org/slides/Notes%20on%20Quant%20UX%20at%20Google.pdf">this doc</a> by Chris Chapman, which gives a good overview of its role requirements.</p><p>There are also many ways to keep up with the rest of the research community. <a href="https://joinlearners.com/">Joinlearners.com</a> is a great resource. They host annual UXR conferences and their <a href="https://uxrconf23.joinlearners.com/">next conference</a> is in June this year. Research slack communities, such as <a href="https://researchops.community/">Research Ops+</a>, are also great places to meet awesome people.</p><p>Lastly, I would also encourage you to connect with UX researcher alumni in your network. These conversations are excellent ways to understand more about the day-to-day work of a UX researcher.</p><p>I’m happy to share more about my experiences and maybe some tips on preparing for job interviews in future blog posts.</p><p>Happy reading and keep learning! Until next time!</p><p>My special thanks to <a href="https://medium.com/u/33e0feb2fa7a">Monica Bajaj</a> and Vidhya Ranganathan for inspiring me to write my own story; my thanks to <a href="https://medium.com/u/11d7966fc0c6">Pavi</a>, who has been my emotional support in making this article possible. I also want to thank Matthew Pereira, <a href="https://medium.com/u/154308986c54">Carolyn</a>, <a href="https://medium.com/u/9d43b9ec2480">April Cheng</a>, and Anshuk Chhibber for their candid feedback on my drafts. You rock!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f788954ee9c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/from-sociology-to-ux-research-2f788954ee9c">From Sociology to UX Research</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing products across interfaces]]></title>
            <link>https://medium.com/auth0-design/designing-products-across-interfaces-9c80ae87578f?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/9c80ae87578f</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[auth0]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ankur Chauhan]]></dc:creator>
            <pubDate>Mon, 17 Apr 2023 15:25:35 GMT</pubDate>
            <atom:updated>2023-04-17T15:25:34.948Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8B7Y2n4plLS_lhK6_N07g.png" /><figcaption>An isometric illustration of various developer tools and interaction points</figcaption></figure><p>In recent years, we’ve seen more and more products focus on a specific type of audience — <strong>developers</strong>. These products are designed to cater specifically to the needs of developers and provide them with tools and features that can streamline their workflows. The success of these products lies in their ability to simplify the development process, making it more efficient and productive for developers. Notable examples of this line of products include Vercel, Cloudflare, Stripe, and Auth0, each offering an extremely specialized and unique set of features and functionalities. The rise of developer-focused products is a testament to the growing demand for specialized tools that cater to the unique requirements of developers. These products may address different needs from those of the average user but that doesn’t imply that good user experience isn’t valued.</p><p>Designing the user experience for such products, though, may require a little more effort than products with a wider target audience. Designers may require a lot of specialized knowledge and experience with these tools before they contribute to the user experience for these products in a meaningful way. This indirectly implies a longer time to onboard new designers. Additionally, this is not limited to developer-focused products — as software takes over more parts of our day-to-day lives, the same can easily be applied to any product that has a large surface area and may be built to be used by a multitude of audience types.</p><h3>Bridging the gap</h3><p>How might we consider bridging the gap between this inherent complexity and the skills designers bring to the table? I’ll try my best to share a few common threads, in hopes they spark some ideas for building better product experiences.</p><p>Great, now let’s imagine for a moment that we’re building a comment management system similar to <a href="https://disqus.com/">Disqus</a> (which allows you to comment on websites, anonymously or not).<strong> </strong>I hope most digital designers are familiar with the good ol’ concept of commenting on various forms of media across the web.</p><p>What’s the first thing that you want to spend time thinking about — probably some form of visualization of what the thing we want to build is, right? Well, maybe a few of you reading this will point out that isn’t the <strong>first thing</strong> but to have this guide be a little focused, I’m going to avoid going into all aspects of building a product. Visualization, thus, will likely be the first step to help us understand all the things we may need to build for a successful product — and it’s something everyone can start working from.</p><figure><img alt="Example of a customer application using our comment messaging system" src="https://cdn-images-1.medium.com/max/1024/0*RTGXk-peXV_5tsGn" /><figcaption>Example of a customer application using our comment messaging system</figcaption></figure><p>Now that we have a visual representation of the product, let’s break it down into what a basic user journey might look like for someone using a third-party application/site/platform that uses this product as its comment management system:</p><p><strong>Step 1</strong> — Person X consumes content on the end-user platform.</p><p><strong>Step 2</strong> — The comment management system loads existing comments in the background. If no comments exist, it renders an empty state.</p><p><strong>Step 3</strong> — Person X writes a comment and hits “Comment”.</p><p><strong>Step 4</strong> — The comment management system posts the comment in the background. If the user is logged in, the comment management system posts their username with the comment.</p><p><strong>Step 5</strong> — The comment management system renders a loading state and pulls for new comments.</p><p><strong>Step 6</strong> — The comment management system renders the new comment in the list.</p><figure><img alt="User journey of the interaction between end-users (using a third-party application) and our product" src="https://cdn-images-1.medium.com/max/1024/0*zYKGBt09VTfL1d9S" /><figcaption>User journey of the interaction between end-users (using a third-party application) and our product</figcaption></figure><p>Great. We’re making progress and hopefully, all of this makes sense so far. Remember the visualization we were started with? That’s only the user interface and since we’re going to be building a comment management system that integrates into different applications or websites, we may want to consider the API (<a href="https://developer.mozilla.org/en-US/docs/Glossary/API">application programming interface</a>: an interface that allows different applications to communicate with each other in a streamlined way) and/or the CLI (<a href="https://clig.dev/">command line interface</a>: an interface that only supports text-based commands and runs within a terminal on your operating system) for this particular product. The people that will be integrating this system may be developers and they may want to understand if they can extend the system a little bit. Additionally, we may want to utilize the common practice of <a href="https://en.wikipedia.org/wiki/Eating_your_own_dog_food">dogfooding</a> to help us get feedback as we build the product. We’d probably want to look under the hood of the user journey we’ve been building so far, so let’s take a look at that next.</p><h3>How to translate from one to the other?</h3><p>If we were to think about an API for this UI, we’d probably start exactly where our user journey does. A person would navigate to our customer’s application and based on the customer’s implementation of our product within their application, our comment management system would be loaded up in the background. At this point, we probably need our comment management system to request a list of all the comments for a particular page from the customer’s (third-party application) environment or isolated workspace in the comment management product. If we don’t do this — we’d just show an empty block for our product with no actual data…and that’s probably not great.</p><p>To represent this, you can follow the visual representation below to see what this interaction would look like behind the scenes. Our comment management system will make a <strong>“GET”</strong> HTTP request in the background to a specific URL, which will act as a secure middle layer between our product’s user interface and a database where our product’s data is stored.</p><figure><img alt="Step 1: API makes a request to retrieve comments in the background as the user navigates to a page with comments" src="https://cdn-images-1.medium.com/max/802/1*t5dVmUOaUrmjlwViYlL68A.png" /><figcaption>Step 1: API makes a request to retrieve comments in the background as the user navigates to a page with comments</figcaption></figure><p>To learn more about HTTP request methods, you may have a look at the MDN documentation here: <a href="https://developer.mozilla.org/docs/Web/HTTP/Methods">https://developer.mozilla.org/docs/Web/HTTP/Methods</a></p><p>The API will make a request in the background to its database to get all the comments available. As these requests are being made, we may want to inform the person viewing the page that we are awaiting data — this is exactly where the ever-welcome loading state interface comes into play, illustrated below.</p><figure><img alt="Step 2: User sees loading state while application is making a request to get data in the background" src="https://cdn-images-1.medium.com/max/802/0*nxqItL8cAp4bg9uq" /><figcaption>Step 2: User sees loading state while application is making a request to get data in the background</figcaption></figure><p>Once the database is able to successfully return a response, the API can pass the data along to the user interface, which will be able to style and render the data the way we want to visualize it in our product. This final handshake between the database, API and UI is represented below.</p><figure><img alt="Step 3: The database responds to the API and the API sends the response forward to the UI." src="https://cdn-images-1.medium.com/max/723/0*QzE51-YvAaDxdBYz" /><figcaption>Step 3: The database responds to the API and the API sends the response forward to the UI.</figcaption></figure><p>Hopefully, we can start to observe some clear patterns in how each interface is communicating with the other and why it’s important for us to define the experience to be able to manage the various intermediate states that may occur in between the interactions. And this is just step 2 of our user journey so far!</p><p>If we continue to build out the rest of the user journey, we’ll see that we need to use other request methods for this. This will help us understand the different ways that the user interface, the API and the database are tied closely together.</p><p>Let’s start mapping out the rest of the user journey, starting with the person adding a new comment. This will require our comment management system to take the user input in the comment field and pass that information to the API, eventually being added to our database along with the other comments on the article. Our comment management system will now make a <strong>“POST”</strong> HTTP request in the background to the same URL from the previous request to push the information entered to our API and eventually create a new database entry in the comments table in our database. If everything goes smoothly, we should receive a response from the API saying that an entry for the person’s comment was created in our database. You can refer to the diagram below to visualize this new request and the query to insert the data into our database.</p><figure><img alt="Step 4: As the user submits the comment, the API sends a request to the database to insert the comment into the table of comments. Once this is successfully completed, the API responds with a success message and details about the comment, so the UI can share feedback with the user." src="https://cdn-images-1.medium.com/max/802/1*9TrSC79BWy7hhIBXL4mu1g.png" /><figcaption>Step 4: As the user submits the comment, the API sends a request to the database to insert the comment into the table of comments. Once this is successfully completed, the API responds with a success message and details about the comment, so the UI can share feedback with the user.</figcaption></figure><p>To begin wrapping up our user journey, we’ll need to show the updated list of comments with the person’s newly added comment with a new total. For this, our comment management system will need to refresh the list of comments using the same <strong>“GET”</strong> HTTP request to get the latest comments from our database. While the system is making this request, we’ll show provide the same feedback to the person that we’re awaiting some data by displaying a loading state in the user interface.</p><figure><img alt="Step 5: User sees loading state while application is making a request to get data in the background" src="https://cdn-images-1.medium.com/max/802/1*IOOcAjBMsnkdjYZXI7FYNQ.png" /><figcaption>Step 5: User sees loading state while application is making a request to get data in the background (UI, API, Database Preview)</figcaption></figure><p>Finally, we should receive a response from our API, we’ll be able to render the received data as seen in the diagram below. And with that we’ve closed out our user journey for listing and adding comments.</p><figure><img alt="Step 6: The database responds to the API and the API sends the response forward to the UI with the new comment and a new total number of comments." src="https://cdn-images-1.medium.com/max/802/1*tlYAOzK9OOwagxXuNZlygQ.png" /><figcaption>Step 6: The database responds to the API and the API sends the response forward to the UI with the new comment and a new total number of comments.</figcaption></figure><p>Once we begin to look at the different interfaces through the same lens, we see patterns for how to design exactly what a person may need to view, how the system handles this in the background and the different connections you may need to consider. This also brings up a good point around how important it is to consider state when designing an interface, since there is an extremely close relationship between user feedback and responses from any system — this is key to building a great user experience.</p><h3>Thinking about a different audience</h3><p>Alright. Now that we got one user journey out of the way, let’s look at another side of our imaginary product — the part that an application builder or developer may need to deal with when they add the comment management system to their application. What are the things they’d need to do to integrate this system with their application? How do they go about this?</p><p>The first and most important part that our product would need to provide is an SDK (software development kit) or a CLI (command line interface), which are two different ways that a developer can integrate the comment management system into their application wherever they need it to be plugged in. The SDK is a collection of helpers that can be added into the application directly that allow the developer to easily access methods that the product may offer. For example, the developer may want to have an easy way to render the comment system below an article or they may want to add a custom loading state when the system is awaiting data. The CLI is a way for the developer to have access to the product’s tools via an operating system’s terminal (or command line) — similar to the user interface for a product’s management tool, replacing the UI with text based commands. This can be useful for quickly getting information about how the product is running in the background, for example to get activity logs of the actions being performed in the customer’s environment of our product. These helpers augment how someone can integrate and add the product to their own offering.</p><p>Let’s imagine that our customer is building their application and have made the decision to integrate our comment management system into their application. Since we offer a SDK for NodeJS applications (you may learn more about <a href="https://www.codecademy.com/article/what-is-node">NodeJS here</a>). And hopefully, it is deployed to a cloud-based package management system (meaning you can use it to download packages like our SDK from the internet) like <a href="https://www.npmjs.com/">NPM</a> (Node Package Manager). We can assume that a developer may be able to see documentation on our website that points to this SDK, which they can install using NPM right into their application. This step performs a few updates and adds a few files to the local folder for their application:</p><figure><img alt="Step 1: Application builder installing the SDK to their local application folder from the NPM registry using the NPM CLI." src="https://cdn-images-1.medium.com/max/802/1*lItacXZ0PYK5Ehha_2GEsg.png" /><figcaption>Step 1: Application builder installing the SDK to their local application folder from the NPM registry using the NPM CLI.</figcaption></figure><p>Once they’ve got the SDK installed, they may want to provide some environment variables to point the SDK to their own environment within our product — this is how an application can potentially authenticate with the product and let it know what to send back (for example — only the customer’s comments and not any customers’ comments). You can see what this looks like below:</p><figure><img alt="Step 2: Application builder adding their credentials for our product into a separate file with variables to reference in their application" src="https://cdn-images-1.medium.com/max/802/1*wGonIUsUVHgn5Kmqg2xAfw.png" /><figcaption>Step 2: Application builder adding their credentials for our product into a separate file with variables to reference in their application</figcaption></figure><p>The next thing a customer may want to render is the UI for our comment messaging system under each article, they may design their page in whatever language they are building the front-end of their application with. On the skeleton for the article, they can <strong>import</strong> our SDK and plug it in right below the contents of the article. Additionally, if our SDK offers a nice way to handle data loading, they can add some conditional logic to render a loading UI while the system is awaiting data.</p><figure><img alt="Step 3: Application builder importing our SDK into a page of their application and using helpers for conditionally rendering loading and error states" src="https://cdn-images-1.medium.com/max/802/1*a628HfAdSYB5rlXmZP5szQ.png" /><figcaption>Step 3: Application builder importing our SDK into a page of their application and using helpers for conditionally rendering loading and error states</figcaption></figure><h3>Final Thoughts</h3><p>Once we begin building interfaces and experiences with their relation to the other services like APIs, SDKs and databases in a system, we can start to map out the different ways people may want to interact with different parts of the product experience. This can help us think about building more consistent patterns across various products, so that users can switch between their contexts and not be lost or confused. Design can, thus, help shape and inform the overall structure and architecture of different interfaces that are crucial for user interaction. Once designers are more aware of the impact of these decisions across the board, it should empower them to create a better overall experience for the products they’re building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c80ae87578f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/designing-products-across-interfaces-9c80ae87578f">Designing products across interfaces</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Spotlight: an interview with Jourdan Nyhof, Product Design Manager]]></title>
            <link>https://medium.com/auth0-design/design-spotlight-an-interview-with-jourdan-nyhof-product-design-manager-d4c93686e137?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/d4c93686e137</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[design-culture]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-leadership]]></category>
            <dc:creator><![CDATA[pavi.design]]></dc:creator>
            <pubDate>Mon, 06 Mar 2023 14:55:14 GMT</pubDate>
            <atom:updated>2023-03-06T14:55:14.806Z</atom:updated>
            <content:encoded><![CDATA[<p>We chat about Jourdan’s journey into Product Design Management, how she fosters team culture, and inspiration through her muse, Hank 🐶.</p><p><em>This interview was monitored by </em><a href="https://medium.com/u/67ab99f0b30"><em>Austin Couillard</em></a><em>, Sr. Brand Designer and </em><a href="https://medium.com/u/11d7966fc0c6"><em>Pavi Designs</em></a><em>, Sr. Product Designer.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Txcowd_o4e2qlh1Gm4avxg.png" /><figcaption>Headshot of Jourdan centered in the middle against a gradient</figcaption></figure><h4>Hi Jourdan, tell us about yourself.</h4><p>For starters, I’m a fair weather runner and french fry connoisseur 😊. I live in Waterloo, Ontario (where I’ve lived most of my life) with my partner Greg and little dog Hank. My hobbies revolve around Canada’s seasonal climate, so depending on the time of year you can either find me reading a book by the lake, or cross country skiing through the forest.</p><p>I currently work at Okta as a Product Design Manager for the Developer Experience (DX) product area, which is a set of related problems and experiences that the company devotes specific attention toward improving. My team designs products for the developers who are implementing and managing Auth0. In addition to our administrative dashboard, the DX domain builds our partner ecosystem, documentation site, and design system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qp9R5LGTRcOrKAxkk8DRZw.png" /><figcaption>A zoom screen capture from a teambuilding cooking class</figcaption></figure><h4>How did you get into product design management? Were you a designer previously?</h4><p>My first job in Product Design was at a startup. Working on a small team meant wearing a lot of hats. Not only was I working as a full-stack product designer, but I also had responsibilities in project management, customer support, and sales. This experience gave me a deeper understanding of how our different teams worked together to achieve lofty business objectives. In my next role as a Design Lead with another startup, I managed a small team of designers responsible for the UX of the company’s core product offering. This was a much more strategic role, and it was also the first experience I had making forward-looking decisions.</p><p>These roles not only helped me develop technical expertise, but they also involved a variety of business units and product markets that offered critical learning experiences to becoming a design manager. Through this process, I felt the importance of prioritizing and building trusting relationships with my peers. This helped ease what can sometimes be a difficult transition to leading a team you were previously a part of. Trust, accountability, and strategic alignment are critical to any manager’s success.</p><h4>What surprised you when you first became a manager in your career?</h4><p>Ironically, what surprised me most about transitioning from “Designer” to “Design Manager” was how little time I spent <em>actually </em>designing. My priorities shifted from creating user solutions to fostering an environment where my team can add as much value as possible. Don’t get me wrong, I still love working on a solution alongside my team. However, as a manager, my first and most important responsibility is to lead, support, and advocate for my team. That being said, there are many parallels between my current role and the roles I previously held. Namely, I still view my primary job as “problem solving,” and with that follow similar methods of discovery and iteration to be successful. Further, I am still accountable to delivering great design. However, this accountability is no longer only personal; I am now accountable for the work of my team and the value it creates in the organization as well.</p><h4>What’s it like working at Okta?</h4><p>I love working at Okta, and I attribute that largely to my team. The design team is filled with talented, high-performing designers and managers. That means we’re always (and I mean <em>always</em>) looking for ways to work more effectively and contribute more strategically across the organization. Although this pursuit can be difficult to keep up with, it’s the result of a culture that cares deeply about our mission both as a company, and as a design team. As such, I’ve come to appreciate the challenges we face because it ensures constant opportunity to learn and improve. I also know that I have the support and trust from my team to <em>fail</em>. For every success I’ve had as a manager, there were as many missed shots and course changes along the way. At Okta, you have the freedom and autonomy to <em>try; </em>the value of which cannot be understated. Last, but not least, working here is fun. I truly feel like my colleagues care about me and that makes it feel less like ‘work’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fgCnTgvpBoZa_BV_ljGNLw.png" /><figcaption>Okta design leaders on a hike together</figcaption></figure><h4>What are you currently reading or listening to?</h4><p>I am part of two book clubs which demand the majority of my reading time. The first is our UX book club at Okta that many of our designers participate in. At the beginning of the quarter we vote on a book to read and then get together at the end of the quarter to discuss it. We recently read <em>Nudge</em> by Richard Thaler and Cass Sunstein, and <em>Ruined by Design</em> written by Mike Monteiro. Next up is <em>Laws of Simplicity </em>by John Madea. Our conversations are light and the learnings don’t always apply directly to our work. This is intentional. The book club environment holds space for each designer to share their unique perspectives and takeaways from each book.</p><p>The second book club I’m in is with my family. We read all kinds of books, and it’s interesting to see the titles chosen by each member. We’ve recently been working our way through the <em>A Court of Thorns and Roses</em> series by Sarah J. Maas. It’s a fantasy fiction series about a mythical world ruled by fairies with different magical powers. If you want to get lost in a good story, I highly recommend it.</p><h4>Can you show us your workspace and walk us through your typical workday?</h4><p>I would consider myself a morning person so my work days usually start with an early morning workout or run. My partner owns a fitness coaching business so I try to squeeze some time in our gym when there’s space available. I also try to eat a big breakfast before work because once the workday starts, I never know when I’ll get a chance to eat lunch!</p><p>The first thing I do when I get online is catch up on anything I may have missed from the night before. Because we’re a distributed team working in multiple time zones, I’ve had to adapt to staying on top of async communication, mainly slack. I spend a lot of time on calls during the day meeting one-on-one with my team and collaborating cross-functionally on different initiatives. Most of my deep work time is spent making sure that my team has everything they need to be successful, and that our focus is aligned to the priorities of the business. As soon as work is done for the day, I get started making dinner. After dinner, my partner and I take our dog, Hank, for a long walk through the neighborhood and catch up on our days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrucBEyk8lcWgr_AhO16qg.png" /><figcaption>An image of Jourdan’s office setup including her dog Hank</figcaption></figure><h4>What are your go-to beverages throughout a work day?</h4><p>My go-to drinks are coffee and sparkling water. There’s usually one of each on my desk at all times.</p><h4>How do you maintain a healthy mindset or practice with work?</h4><p>There are two key things that really help me deliver my best work and manage stress. The first is starting my day with exercise. By the time I start work I know that my workout is already behind me, and I’m fully focused and awake before my first meeting. The second thing is taking some time to decompress and transition out of the “work day” when it ends. When I was first adjusting to working from home, I was having a hard time detaching from work and really missed the quiet reflection that I had previously enjoyed during my commute home. I find that some planned solitude and silence is especially important as a manager because I spend so much of the day talking on calls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V7dND7N4aQiUdtQK" /><figcaption>A snowy outdoor scene at sunset</figcaption></figure><h4>Let’s say time travel exists. What’s one piece of advice you would give yourself at the start of your career?</h4><p>The one piece of advice I would give myself is to take responsibility over my own growth and development right away. Early in my career, I hid from feedback and actively avoided career conversations. At the time, I thought my managers were going to just let me know whenever they decided I’d demonstrated the right skills to be promoted, or tell me if I wasn’t meeting expectations. As a result, I spent a lot of time guessing where I should focus my development and learning. Now, I have a strong appreciation for honest and constructive feedback, and I make sure that I’m aligned with my manager about key areas for my professional development.</p><h4>At Okta, what are your team’s go-to methods for connecting and getting to know each other?</h4><p>There really is no replacement for in-person quality time when it comes to connecting with one another. I believe that showing a genuine interest in your peers goes a very long way to building trust and fostering healthy collaboration, both of which are especially important on a design team. On my team, we start our weekly meeting with a 5-minute “About Me” presentation from someone on the team. It is up to the presenter what they want to share. It can be anything — something new that they learned, how they’ve been spending their weekends, or a trip they recently went on. These presentations usually lead to a deeper conversation and some friendly joking before we start with our meeting agenda.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnLrToo3KIWFdP7SsbpLYA.png" /><figcaption>A photo collection of things the design team enjoys such as roadtrips and food.</figcaption></figure><h4>What would you tell others who want to get into product design management?</h4><p>Start by learning about how the product design manager role that you’re interested in is different from the role that you’re currently in. Once you’ve identified the differences, look for opportunities to demonstrate the skills needed to bridge the gap. It may be things like adjusting to longer-term thinking, building mentorship skills, or finding operational changes that can make the team more effective. If you can strengthen those skills in your current role, you’ll be better prepared when an opportunity to become a Product Design Manager comes up. Secondly, I would strongly recommend letting your manager know that product design management is a career path that interests you. Being upfront about your interests will help your manager give you better feedback, and potentially provide opportunities to develop the skills necessary for your career goals. There may be initiatives that you can partner with your manager on, or even lead yourself. If you don’t ask, you might never know!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8QU-FiT4ltgDuOVtJmz7cg.png" /></figure><h4>Where can people connect with you?</h4><p>I’d love to hear from you on <a href="https://www.linkedin.com/in/jourdan-nyhof-32a85a66/">linkedin</a> :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4c93686e137" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/design-spotlight-an-interview-with-jourdan-nyhof-product-design-manager-d4c93686e137">Design Spotlight: an interview with Jourdan Nyhof, Product Design Manager</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build influence without authority as an individual contributor]]></title>
            <link>https://medium.com/auth0-design/build-influence-without-authority-as-an-individual-contributor-b339c6536970?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/b339c6536970</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[pavi.design]]></dc:creator>
            <pubDate>Tue, 21 Feb 2023 18:03:00 GMT</pubDate>
            <atom:updated>2023-02-21T18:03:00.095Z</atom:updated>
            <content:encoded><![CDATA[<p>Redirecting a moving train</p><figure><img alt="Collage of illustrations of team members raising their hands, sailing a boat, and launching a rocket" src="https://cdn-images-1.medium.com/max/1024/1*MPyqHEkjUfwKFQ7QeXVNWA.png" /><figcaption>Collage of illustrations of team members raising their hands, sailing a boat, and launching a rocket</figcaption></figure><p>You may have found yourself in a situation where you needed to persuade others to see things your way without the backing of formal authority. There’s no perfect formula to solve this, but I’ll share what’s worked for me. Let’s redirect the train together, all aboard!</p><h3>Catching the train</h3><p>A few years ago, I joined a project where we didn’t have a Product Manager, and the developers were building something based on designs from a different project. Jumping into this partway, I had no idea where to start. I realized I was trying to catch a train moving in the opposite direction, and there were two things I could’ve done:</p><ol><li>Jump on and take a back seat as a passenger</li><li>Halt the train to help redirect it</li></ol><figure><img alt="Illustration of a person trying to catching a moving train" src="https://cdn-images-1.medium.com/max/1024/0*XlCfIRFPGSdioUkQ.png" /><figcaption>Illustration of a person trying to catching a moving train</figcaption></figure><p>I barely knew the team. How might I get them to trust me and influence change in our work?</p><p>Back in the days when we were in the office, you’d greet people as you saw them in the office. You may have lunch with your team, grab a coffee, and chat about things that aren’t work-related. Remote work changed this for us. No one distracts me at my desk apart from Benji (my dog) scratching the door. These days we need to make a conscious effort and be intentional in exchanging pleasantries.</p><figure><img alt="Illustration of two people greeting each other" src="https://cdn-images-1.medium.com/max/1024/0*fNe0o8A7-rEk4dAy.png" /><figcaption>Illustration of two people greeting each other</figcaption></figure><p>Before working remotely, I’d never thought much about pleasantries and talking about the weather (that’s a thing). The switch made me realize these in-between conversations are the essential glue that keeps the team together. It initially started with questions like <em>how are you doing? How was your weekend?</em> But what made a difference was remembering what a team member said during that conversation, and following up.</p><p>I’ll always remember this phrase from Dale Carnegie’s book, <a href="https://www.goodreads.com/work/quotes/2370171"><em>How to Win Friends &amp; Influence People</em></a>.</p><blockquote><em>Little phrases such as “I’m sorry to trouble you,” “Would you be so kind as to — ?” “Won’t you please?” “Would you mind?” “Thank you” — little courtesies like these oil the cogs of the monotonous grind of everyday life.</em></blockquote><blockquote><em>―</em><strong><em>Dale Carnegie</em></strong></blockquote><p>When you stop oiling the cogs, it dries up and hurts itself. Oiling the team bond and exchanging courtesies is just as important.</p><figure><img alt="Illustration of two people having a conversation" src="https://cdn-images-1.medium.com/max/1024/0*5QeyU5uX6DNNbmTG.png" /><figcaption>Illustration of two people having a conversation</figcaption></figure><h3>Bring the wagons together</h3><p>Some may recall the stories of <a href="http://en.wikipedia.org/wiki/Thomas_the_Tank_Engine"><em>Thomas the Tank Engine</em></a><em>; the</em> carriages and wagons never wanted to cooperate or collaborate. The wagons always wanted to go their way, and do whatever they<em> </em>wanted, never mind the trouble it caused others. There are a few things we can do to mitigate this.</p><h3>Shared ownership</h3><p>Taiichi Ohno, industrial engineer and manager at Toyota, introduced the Andon cord, which authorized every employee on the assembly line to halt production when they immediately noticed a problem or defect. We can also put this into practice with projects, empowering the team to raise their hand and say when something is not working. For instance, I frequently shared my work progress with the developers as I was exploring ideas. I invited the team to share their critique async and in sync, which encouraged them to raise red flags and, in some instances, made us return to the drawing board to understand the user flow better.</p><figure><img alt="Illustration of a team launching a rocket together" src="https://cdn-images-1.medium.com/max/1024/0*FZ5vk29H2Lx8S_k8.png" /><figcaption>Illustration of a team launching a rocket together</figcaption></figure><p>At first, I got caught up in thinking that as a person leading the project, all the heavy lifting and responsibility fell on my shoulders. But this quickly caught up with me, and I felt like I was slowly starting to sink.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VQQGGBHFTq-yngpc.png" /><figcaption>Illustration of a person sinking into the water</figcaption></figure><p>Instead, I started to take a step back and make space for others to own a task. I paused to ask if anyone wanted to own the job before jumping the gun. <strong>Pausing is powerful</strong>, for example, I use 8 second pauses to create space for hearing thoughts.</p><p>I also started encouraging team members to take turns leading retros and syncs. This instantly made a difference and empowered the team to own important aspects of the project. <strong>Ownership isn’t a singular word. It’s a teamship</strong>. Involving the team throughout the design process (discovery, research, prototypes, iterations, and testing) encouraged shared ownership, advocating for the user experience, and increased feedback engagement via slack and during sync calls.</p><h3>Team Culture</h3><p>Fostering team culture is a key aspect to collaboration. But did you know you can influence culture without formal authority? <strong>Rather than seeking the culture, be the culture you seek</strong>. In my previous career as a Biochemist, I was so frustrated with the toxic team culture, and accepted it as it was. After shifting into design, I started seeking fun opportunities. When I couldn’t find it, I initiated rather than waiting for someone to own it.</p><figure><img alt="A collage of photos of teams participating in activities in both real life and remote" src="https://cdn-images-1.medium.com/max/1024/0*pfowv7jxCrjWTWdm.png" /><figcaption>A collage of photos of teams participating in activities in both real life and remote</figcaption></figure><p>Taking that first step is tough, but diving into the unknown and discomfort first is what makes us leaders and owners. In this case, make the space for folks to share their perspectives and thoughts without being seen as a conflict. This helps build trust through honest and direct communication. The game changer for me was <strong>active listening</strong>, taking the time to understand my team, constantly practicing it, and staying neutral. It helped folks feel I was playing on the same side as them.</p><p>There’s no cookie cutter solution, however this is what I tried and what worked for me. What do you have to lose other than an opportunity to learn? If you’re curious to learn more, check out my talk from <a href="https://www.youtube.com/watch?v=Gjh2V3VKsWM">DesignX Remote Design Week</a>.</p><h3>Resources</h3><ol><li><a href="https://www.youtube.com/watch?v=Gjh2V3VKsWM">DesignX Remote Design Week talk</a></li><li><a href="https://www.goodreads.com/work/quotes/2370171">How to Win Friends &amp; Influence People</a> by Dale Carnegie</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b339c6536970" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/build-influence-without-authority-as-an-individual-contributor-b339c6536970">Build influence without authority as an individual contributor</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Evolution of Auth0's (Ops-first) Research Practice]]></title>
            <link>https://medium.com/auth0-design/the-evolution-of-auth0s-ops-first-research-practice-cc024d23ee6b?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/cc024d23ee6b</guid>
            <category><![CDATA[organizational-structures]]></category>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Brad Orego (they/them)]]></dc:creator>
            <pubDate>Mon, 06 Feb 2023 19:46:18 GMT</pubDate>
            <atom:updated>2023-02-06T19:46:18.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*st2OJcBNl9mj2Idqrj9P9w.jpeg" /></figure><p>It’s hard to believe it’s been over a year since I last wrote about what we’ve been working on at Auth0. We’ve heard a lot from Research @ Auth0 team in that time, including <a href="https://medium.com/auth0-design/automating-researchops-57137aa19c65">Increasing ResearchOps Impact Through Automation</a>, <a href="https://medium.com/auth0-design/getting-started-with-inclusive-research-5971cdd8de48">Getting Started with Inclusive Research</a>, <a href="https://medium.com/auth0-design/onboarding-on-an-ops-first-research-team-87905a5588d8">Onboarding to an Ops-First Research Team</a>, and <a href="https://medium.com/auth0-design/the-evolution-of-auth0s-insights-repository-e94a78145245">The Evolution of Auth0’s Insights Repository</a> in case you missed them 👀</p><p>Recently, though, <strong>a lot has changed for both the team and the company</strong>, and I wanted to talk about what’s happening and why. Before we get too far into that, let’s provide some context about where we’ve come from and where we are now 📆</p><h3>The Early Days</h3><p>If we go all the way back to the beginning of 2020, I joined Auth0 to prove a hypothesis: that <a href="https://medium.com/auth0-design/why-were-building-an-ops-first-research-practice-bfe42dc8c957">building a Research function by focusing on Research Operations first</a> was the best way to do so (especially at a hypergrowth startup). Over the past 3 years, I think we’ve successfully proven that hypothesis:</p><ul><li>In 2019, Auth0 completed 3 research studies. In 2020, that number grew to 12, 19 in 2021, and 27 in 2022 🚀</li><li>The number of people/teams who engage in research has grown from 6 to 42 📈</li><li>Our insights repository has 550+ entries and our Research Program has 1800+ participants 💪</li><li>Our playbook includes 56 pages, 26 videos, and 9 tools, and 380+ Auziros have completed our Research Onboarding course 📚</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ls1AT9usgMjdxS0K-6HoWQ.png" /><figcaption>Summarizing the impact of our Ops-First approach</figcaption></figure><h4>Where we are now</h4><p>3 years is basically forever in the tech world; doubly so in a startup setting. Auth0 today is not what Auth0 was in 2020:</p><ul><li>The company grew from a ~500-employee Series E startup to a ~1100-employee pre-IPO unicorn 🦄</li><li>In May 2021, the acquisition by Okta was completed, and we began a gradual and ongoing merger.</li><li>The team that works on Auth0 now operates as an independent business unit within Okta where our sole focus is on Customer Identity 👤</li></ul><p>Heading into 2023, it was time for a change. We need to evolve our research practice to meet the needs of our business with renewed focus and clarity. We’re not a startup anymore: we have a very good idea of what we should be working on, but we have a fuzzy picture of what the solutions should look like. Democratized Research no longer serves that need. It’s time for something new 🔭</p><blockquote>Democratized Research excels in situations where you need to cover a large surface area at a shallow depth with limited resources (i.e. basically every startup ever).</blockquote><h3>Shifting Our Focus</h3><p>Based on the needs of the organization and the current resources we have available, <strong>we’re migrating from a Democratized Research model to a Centralized-Agency model</strong>. This represents the best match between what we can offer and what the company needs 🤝</p><blockquote>N.B. If you’ve never struggled with having inadequate resources (budget, people, etc), you can skip most of this section. For the rest of us in the real world, read on to learn about what this means and why we’re doing it.</blockquote><h4>What’s Changing</h4><p><strong><em>Personnel.</em> </strong>Throughout the past 3 years, we’ve invested heavily in democratization and in ResearchOps. This was evident in how we staffed the team: 2 dedicated ResearchOps teammates plus a Research Strategist. <strong>This made sense when we were supporting dozens of People Who Do Research</strong> (PWDR), but going forward we’re <strong>shifting most of our staff over to dedicated Researcher roles</strong>. After the transition, we’ll have a team of four Researchers with one person staying in Operations 👥</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s16EXeR-QW5Z-S2bYJXmdA.jpeg" /><figcaption>What our team looks like before and after these changes</figcaption></figure><p><strong><em>Process. </em></strong>When running an ops-first, democratized research function, the majority (if not the entirety) of the research that happens is self-service, driven by your PWDR. What this typically means is your Research Roadmap is virtually non-existent: <strong>you can service every request, but your ability to control which requests come in is limited 📋</strong></p><p>Going forward, we not only get to decide which projects we take on (versus which are delegated to self-service; more on that later), we have to have a way to let people know what order we’ll be picking projects up. Enter our <strong>triage and prioritization process</strong>. Basically, as requests come in, they either immediately go into our self-service pipeline or wind up somewhere on our backlog. The position on that backlog depends upon a variety of factors, including business priorities, scope, team capacity, etc. <strong>This backlog lives in Jira where anyone at the company can view it 🔍</strong></p><p>If the requester doesn’t like their anticipated delivery date, they can either <strong>plead their case to have it reprioritized, or they can work with us to reduce the scope</strong> until it falls back into the self-service process. This way, nobody’s ever completely stuck 🔓</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MjnKPsa6TULGeNw0vCRr0A.jpeg" /><figcaption>A snapshot of the new process for managing our backlog.</figcaption></figure><p>We’re also making some changes to how we do research, including implementing a peer review process for our Researchers. As a democratized practice, it’s hard to have solid peer review because <strong>strategy and expertise were centralized under one person</strong>. Now with a team of researchers, it makes sense to <strong>provide opportunities to give and receive feedback directly from each other</strong>, both strengthening the research we do and helping develop the team 🌱</p><h4>What’s Not Changing</h4><p>Any time there’s change happening, I like to give people a clear picture of what we’re planning to change, and <strong>sometimes more importantly</strong>, what’s not changing. Our Ops-First approach has a few major facets, and for the most part, those aren’t going anywhere. Notably:</p><ul><li><a href="https://medium.com/u/5c35300d9ee9">Rodrigo Dalcin</a> (our Ops Lead) will <strong>continue to meet with each Product team every month</strong> to keep tabs on them and share updates from the Research team 📰</li><li>We’ll continue our monthly knowledge-sharing rituals: <strong>Research Deep Dives</strong> (60-minute workshops or lecture-demonstrations on a specific topic within Research) and <strong>Research Readouts</strong> (5-minute summaries of all the research that’s completed in the past month) 🧠</li><li>We still have a <strong>single point of entry for engagement with Research</strong>: our Insights Request Form 🚪</li><li>We’ll still have a <strong>self-service research process</strong>, though with re-scoped levels of support to balance the needs of our Research team with the needs of our PWDR ⚖️</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jFyOxJ45vc7IzZnqE2iwHg.jpeg" /><figcaption>The place where it all begins: our Insights Request form</figcaption></figure><h4>Does this mean Democratization is Dead?</h4><p>Not at all! Nobody said Democratization was the be-all, end-all answer to how to structure a Research function. I still stand by the belief that it’s the <strong>best way to <em>start</em> building a team</strong> (unless you walk into a situation with a huge charter and a lot of buy-in at all levels of the business), and we’ll <strong>continue to reap the long-term benefits</strong> (standardized processes, strong Research culture, existing toolkit, clearly defined responsibilities, seamless onboarding, etc) for years to come.</p><blockquote>If anything, the natural evolution of building Ops-First is to move on to another model: prove the value of Research by supporting a broad team with limited resources while preparing your team for scale.</blockquote><p>That being said, we also aren’t shutting down the self-service branch of our research engagement process. We won’t have the bandwidth to service every request, but continuing to support self-service means we can <strong>empower teams to tackle some of the smaller/simpler projects themselves</strong>. If you’ve ever found yourself frustrated because you feel like you’re stuck doing low-impact work, <a href="https://medium.com/auth0-design/why-were-building-an-ops-first-research-practice-bfe42dc8c957">democratization can help</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*OVEj4HwhBIuWMls2JNVF5w.gif" /><figcaption>Democratization. Do it.</figcaption></figure><h3>Why are we doing this?</h3><p>It’s February 2023. Like many companies in the technology sector, we’re facing reality. In an ideal world, we’d grow the team while keeping our current level of service for Democratized Research, but with limited resources, the most responsible thing to do is to shift our focus 🔀</p><p>It’s not all gloom and doom though: there are a variety of benefits to this approach. One of the biggest drawbacks of Democratized Research is your Research team has relatively little control over the Research Roadmap. If you aren’t the ones doing the research, it doesn’t necessarily make sense to say no to anything. <strong>By centralizing, we gain a lot of control over what research gets done</strong>, including any strategic initiatives we want to take on ourselves (i.e. Consumer Auth Archetypes, which we’ll be launching later this year) 🏆</p><p>Centralizing also allows us to build a deeper understanding of customers and end-users in a few key areas. We may lose some visibility over things we’ve decided are less relevant to the current business goals, but for the topics that are in the spotlight, we can <strong>increase the volume of research and tighten the focus of it, leading to a more thorough understanding of the problem space 🔬</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IOli0casJEzqt93W631OUQ.jpeg" /><figcaption>Breadth vs. Depth in research coverage</figcaption></figure><p>We’ve decided to go with an Agency model because it provides the right balance for us: <strong>reap the benefits of increased focus and depth while also maintaining flexibility to work on the top priorities and the largest needs</strong>. As much as I’m a proponent of Continuous Research, most teams don’t <em>need</em> to do research constantly, so we can deliver insights to one team and let them act upon them while we pick up work on something else 🔁</p><h4>What’s next?</h4><p>I’m confident this is the right move for our organization right now, and we’ve already begun to implement some of the changes (notably, personnel changes, updating our documentation, communicating all of the differences, and engaging with teams under the new model), however that’s not nearly the end of it. After all, as Mike Tyson said…</p><blockquote>everybody has a plan until they get punched in the mouth.</blockquote><p>Or, more eloquently (and <a href="https://quoteinvestigator.com/2021/05/04/no-plan/">originally</a>) put by Helmuth von Moltke: <strong>no plan survives first contact with reality</strong>. So we’ll make adjustments as we go and learn from what’s working and what isn’t. And, of course, we’ll continue to share the journey here as well as in other places. Speaking of which…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r--NEmqvL36yg4PE.png" /></figure><p>Check out Great Question’s <a href="https://www.peoplewhodoresearch.com/">People Who Do Research</a> virtual conference on February 8th, where I’ll both give a talk about the history of Research @ Auth0 and sit on a panel about building an Ops-First Research Practice. We’re already well over 500 attendees, so get your tickets now. See you there! 🎉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc024d23ee6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/the-evolution-of-auth0s-ops-first-research-practice-cc024d23ee6b">The Evolution of Auth0&#39;s (Ops-first) Research Practice</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Between two Product Designers;]]></title>
            <link>https://medium.com/auth0-design/between-two-product-designers-cdc0adfb2949?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/cdc0adfb2949</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Sarina]]></dc:creator>
            <pubDate>Mon, 30 Jan 2023 14:02:30 GMT</pubDate>
            <atom:updated>2023-01-30T14:02:30.346Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> and <a href="https://medium.com/u/35560d046d0">Sarina</a> sit down for a table tennis-style interview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ub4iLK8TdTORXGwjuRsmzQ.png" /><figcaption>Decorative image; an illustration of graphic white lines, flowing from right to left. On top of the white lines, there are two cylindrical gradients on the opposite ends of horizontally stacked verticals is a photo of each person smiling.</figcaption></figure><h4>Forward;</h4><p>The article is written by two product designers who have decided to share their perspectives and working styles in order to emphasize that there is no one or right way to utilize design. They aim to provide a well-rounded insight into real examples of working styles by discussing the importance of effective communication, critical thinking, and sharing work in the design process. The article is an experiment in sharing multiple perspectives on design, rather than the perspective of one singular person as seen in other medium articles on design.</p><h3><strong>It’s all about communication;</strong></h3><p><strong>Can you share a time when you switched up your communication style?</strong></p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — “It’s funny to think the time that I switched up my communication style involved no direct communication. I switched up my communication style by not meeting (digital or virtual) for 2 weeks. The goal of this challenge week was to get creative; <a href="https://medium.com/@Jeem/articulating-design-decisions-takeaways-7cf0d314cd41">to think about the quality of communication and the quantity</a>. Using tools like Loom, Vidyard, and Slack video recording helped me communicate in both an auditory and visual way without having to have meetings. It was a great method that allowed quality documentation and sped up the communication process.”</p><p><strong>Does your communication style change throughout the design process?</strong></p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> — “Towards the initial phase of a project, most communication is about the vision and purpose. Understanding why we are working on this, who we are building for, and how we might be able to achieve our goals. Once established, the communication shifts into the nitty gritty details of the design and implementation. Communicating specific points around the visual and interactive elements of the design and working with engineers to ensure intended implementation.”</p><p><strong>What&#39;s your most effective communication method?</strong></p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — “When working in groups such as a triad or a product focus area, communication is most effective when everyone is in the room. The reduction of multiple areas in which communication crossover happens is the best communication method.</p><p>When you have everyone in the same room at the same time using one source of truth, it enhances and strengthens alignment. Thinking about effective communication, I have always found the best solution is to question: how can we stay effectively aligned as a group?”</p><figure><img alt="Decorative image; an illustration of a pencil on a gradient back ground of green and yellow" src="https://cdn-images-1.medium.com/max/1024/1*LzmwCyy0v1Fxv3DJgvTRng.png" /><figcaption>Decorative image; an illustration of a pencil on a gradient background of green and yellow.</figcaption></figure><h3>Critical thinking sounds fancy but it&#39;s not;</h3><p><strong>Share a resource available to you that deepens your critical thinking.</strong></p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> — “One of the best resources available to designers at Auth0 is our insights repository (set up by our fantastic research operations team). There is great feedback and information from the interviews we conduct, and the research team is always willing to work with designers to conduct new studies to have all the information we need to work on a project.”</p><p><strong>… And how did you get better at critically thinking?</strong></p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — “The best way I found to strengthen how to think critically about solutions is through Systems thinking. Working on design systems helped me to think systematically and widen my range of understanding of the product.</p><p>This not only helped me to strengthen my critical thinking but help me to think efficiently about the problems and solutions I was designing. Because I had a mental inventory of components and how they are implemented, I could make better decisions about effective and efficient solutions. It also helped me to communicate better with stakeholders because I understood the product constraints.”</p><h3>Literally, sharing is caring;</h3><p><strong>Tell me about the outlets that are in place for you to share your work.</strong></p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> — “The design team here at Auth0 has set up multiple areas for designers to share and get feedback on their work. One example is our work-in-progress channel on slack, where we can throw any idea or design to get some eyes and quick feedback on any stage of our design work. I also have sessions with my PM and some engineers on the team to ensure I capture feedback that’s not only from the design team.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v-ioZ3XGIQr3lDgblU_xQQ.png" /><figcaption>Screenshot of written text sent from a Slack message.</figcaption></figure><p><em>Image Description; “Morning team! I’ve been working on designs for the notification migration. For some context, support center is deprecating and now needs a new home to display all in-app notifications (announcements, API misuse, billing…). For the MVP we are looking to create a notification dashboard page, which displays all notifications, that is accessible from the notification panel. Feedback I’m looking for specifically:</em></p><p><em>1. Overall flow, 2. I’ve dusted off some old ideas to update the notification cards and panel to call out some actions and create some grouping, 3. Any edge cases that are missing or overall concerns. Here is the link to the file, feel free to drop comments in Figma or this thread”</em></p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — “1:1 with PM.<strong> </strong>I’ll say it once, and I’ll say it again <a href="https://medium.com/ux-planet/how-product-managers-can-work-effectively-with-product-designers-a5175dcb9e51">your product manager should be your best friend</a>! They are a wealth of knowledge and can help you stay in the loop with business objectives, roadmap priorities, and get ahead of customers&#39; needs to work smarter, not harder. Sharing your work with your PM helps to ensure alignment and thoughtful scope, tremendously speeding up the process.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vsa0jvh-d_hADH624GnLSQ.png" /><figcaption>Decorative image; an illustration of a lamp on a gradient background of orange and pink.</figcaption></figure><h3>You give and you get;</h3><p><strong>Where in your design process do you lean on feedback and what kind?</strong></p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> — “Two areas of the process stand out to me in collecting feedback. The first is the initial ideation stage, where I lean on my PM and engineers. I present my ideas and do a quick sanity check to ensure nothing seems too out of the ordinary. Also, leaning on engineers to better understand the technical limitations of the project. The second area is when designs are close to completion. This is where I will rope in other designers to verify that the current design is consistent with other experiences in the product and that I’m not missing any critical details.”</p><p><strong>What type of feedback do you like to give to your peers?</strong></p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — <em>“</em>Someone once told me as feedback; that I should try to be a lazy designer. (Shout out to the best mentor, you know who you are) Being a lazy designer means you are freeing up your time by using a lean UX practice, ensuring you deeply understand the problem and highlighting solutions based on scope.</p><p>When giving others feedback about being a “lazy designer”, I like to consider and ask how are you helping yourself to spend less time on a solution and more time on the things that help to ensure it’s the right solution. To do this I like to give feedback on; what data and research are used to validate/measure your solution and its successes pre and post-release.”</p><h3>Pixelated performance;</h3><p><strong>Working from home changes how you perform and work, what have you noticed?</strong></p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> — “Being in the office helped create organic conversations and it was easy to nudge the person beside you for some quick feedback or thoughts on a topic. With being at home I think it’s important to stay connected with your team by checking in frequently and sharing work more often through means of slack or setting up meetings.”</p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — <em>“</em>Interestingly enough, I’ve not worked from home. I started my career as a product designer just before the pandemic. It’s forced me to be better at being a good communicator and staying organized to ensure I communicate with stakeholders clearly and concisely. As a neurodivergent person, working from home allows me to utilize my time to ensure I was not exhaustively using my brainpower. This ultimately helps stay creative and have enough space to think critically!”</p><h3>Pleasure or Pain;</h3><p><strong>Do you view pressure as a good or bad tool…elaborate on why?</strong></p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> — “This depends on the situation. I believe pressure can push you to your limits and enables you to think and act quickly which allows for faster problem-solving. With that being said, some problems I feel need more time and attention where you may need several stakeholders&#39; opinions and a better understanding of the problem which may take time. Adding pressure to those situations may lead to a messy and rushed result.”</p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — “Have you ever heard of the idea that starting on a blank page is a lot harder than starting off with a prompt?</p><p>I use pressure as a constraint to help me guide my practice by being able to say yes or no to something because of costs, time and other resource limitations. By pressure creating limitations and constraints, it helps me think critically about what really matters and how to be able to use lean UX as a way of working in an iterative and agile approach.”</p><figure><img alt="Decorative image; an illustration of a digital application window on a gradient background of yellow and orange" src="https://cdn-images-1.medium.com/max/1024/1*uvFN3UoW6qXI2mPji7mLOQ.png" /><figcaption>Decorative image; an illustration of a software window on a gradient background of yellow and orange.</figcaption></figure><h3>No “I” in, lead or we or team;</h3><p><strong>What can you define as a team player?</strong></p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> —<em> </em>“A team player in my eyes contributes not only to their individual work but supports other team members in their efforts. Lending a hand, providing feedback, and being a soundboard to bounce ideas off is just a few of the things an excellent team player does.”</p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — <em>“</em>I can only define someone as a team player based on my learnings through the countless mistakes I’ve made (haha). That being said;</p><ul><li>Staying aligned with your teammates and within your objectives helps you as an individual and helps your teammates out. In the end, alignment is about moving together as a team.</li><li>Being transparent in your process and how you work helps to build an understanding of how you tackle problem shaping and solutions. It helps to give insight and knowledge to your stakeholders, ultimately helping with alignment.</li></ul><p>To summarize, if someone is constantly thinking through how they are <a href="https://medium.com/user-experience-design-1/how-to-use-ux-documentation-to-collaborate-effectively-24ef6f271740">creating alignment and transparency, they own their processes and craft</a> = a team player.”</p><p><strong>Explain how being an individual team player is important.</strong></p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a> — “If all team players were to solely focus on their own initiatives it would enable a lack of consistency throughout the product and create an environment where collaboration does not exist. Understanding other team members’ work, why their work is important, and how you can help creates cohesiveness within the team. Collaborating as a team player allows for new perspectives and approaches to solving problems that may not be evident when solving problems independently.”</p><p><strong>In what ways has being a team player affected your design craft?</strong></p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — “I think being a team player has helped me own my decision-making processes and helped me get closer to my team to build trust, consistency, and autonomy.</p><p>I think a lot of designers often start out as perfectionists, and by focusing on being a team player through transparency and alignment, I have been able to work faster and smarter and also spend time building my own design skills.”</p><p><strong>What are some things you do with your team outside of your day-to-day work to stay connected?</strong></p><p><a href="https://medium.com/u/35560d046d0">Sarina</a> — “One of the things I like to do is create 1:1 coffee chats to catch up with what my teammates are up to inside and outside of work. Also like sharing external resources like articles or videos related to my teammates’ work to stay connected.”</p><p><a href="https://medium.com/u/a7d1bee6912a">Anojen Jeyapalan</a>— “The team does a lot to stay connected from sharing music to meeting up with others in the same area. Fortunately, we’ve been able to come together as a team to have in-office days and socials where we are able to stay connected. At some of our office meetups, we spent time watching hackathon finals, getting some good eats together and even playing some mini golf!”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vCuJBtZrsOv7L9J4iAHN7A.jpeg" /><figcaption>Decorative image; an illustration of graphic white lines, flowing from right to left. On top of the white lines, there are two cylindrical gradients on the opposite ends of horizontally stacked verticals is a photo of a group of 3 people smiling and playing mini put</figcaption></figure><p>Follow <a href="https://medium.com/u/9ef9638b3092">Auth0</a> and <a href="https://medium.com/u/7b847836aa03">Okta</a> on medium for more content about our teams and products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdc0adfb2949" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/between-two-product-designers-cdc0adfb2949">Between two Product Designers;</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we optimize a large design system component]]></title>
            <link>https://medium.com/auth0-design/how-we-optimize-a-large-design-system-component-1e07eb09f448?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/1e07eb09f448</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[design-operations]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Amie Chen]]></dc:creator>
            <pubDate>Mon, 19 Dec 2022 16:07:05 GMT</pubDate>
            <atom:updated>2022-12-19T16:07:04.873Z</atom:updated>
            <content:encoded><![CDATA[<p>A Case Study</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p6PXF86-UYZ3v4zib4Imig.png" /><figcaption>How we optimize a large design system component</figcaption></figure><p>As our design system grows, a few components stand out like a sore thumb. They share the same characteristics: slow, massive, sometimes buggy and yet, broadly adopted. For Quantum (Auth0’s design system), it’s the Text Field component.</p><p>As one of the most robust components in our design system, the Text Field had 2205 variants. It also used <a href="https://www.figma.com/best-practices/creating-and-organizing-variants/using-variants-effectively/">Base/Master Component</a>, which is easy to start with but can quickly get out of hand. Therefore, when Figma’s <a href="https://help.figma.com/hc/en-us/articles/5579474826519-Explore-component-properties">Component Property</a> feature was released, it was clear that the Text field component could greatly benefit from this new feature.</p><p>As the person who spearheaded this project, my main goal was to reduce the number of layers and variants, remove the base component, without changing anything visual.</p><h3>Result</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1xDW6j9jRPGprExWDE0QyA.png" /><figcaption>Before &amp; After</figcaption></figure><p>Before the optimization, the whole design system had 71,615 layers. After optimization, the number dropped to 4165. I also reduced 2205 variants to 24 variants. It was a significant change, and I noticed a nice boost in performance when loading the file too.</p><h4>How did we have so many variants for a single component?</h4><p>Before Figma’s Component Properties were released, our strategy was to create every possible variant, so it’s easy for designers to choose between them and see what’s available. This helped the quick adoption of our design system, but led to several bulky components.</p><p>We could have instructed designers how to toggle elements in hidden layers, but that isn’t as convenient and straightforward as laying every possibility under the sun. It’s a trade off that we deem acceptable at the time.</p><h3>The process</h3><p>It was a daunting task to even think about optimizing such a component. After a few grunts, sighs, and a bunch of coffee, I started refactoring the Text Field component. Since the previous strategy was using a base component with hidden layers, all instances shared the same structure. I created a brand-new instance where all layers were turned on, and then detached it to make a brand-new component in a new branch.</p><p>At first, I took full advantage of component properties. I loved how the Boolean Property surfaces (almost) all the component properties’ visibility to the design panel. I loved how easy it is for end users to swap icons and replace text, without opening layers upon layers. However, I quickly realized two problems:</p><ol><li>The number of properties in the design panel quickly got out of hand. It was hard to find a property, even with some sly naming. It was a toggle switch hell.</li><li>By relinquishing all the controls to users, our design system now has a usability issue: it became unclear when to use some controls, and when not to use others. This can easily introduce inconsistency, and makes our design system hard to use.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aK2y87esqe3i0Kykmiwrjw.png" /><figcaption>A cleaned-up version of properties in design panel.</figcaption></figure><p>The team and I came up with a hybrid solution. We combined the usages of both component properties and variants. Shared properties like title, require asterisk, start &amp; end icons were exposed as component properties; whereas layers like Error Text and Helper Text are nested in certain variants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JxSiMkjQ71J_BNbDTjP66g.png" /><figcaption>Error Text only shows in the Error state</figcaption></figure><p>For example, since the error state variant is the only one that uses the error text layer, we didn’t expose it as a component property. Instead, the error text layer was nested in the canvas and users would have to drill in manually. This middle ground approach allows designers and developers to know what a component can do and can’t do, and also provides guidance about how they should use a component, with only a minor sacrifice in productivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ecMhBCGRRKmObsGF9riNA.png" /><figcaption>The new Text Field component</figcaption></figure><p>Following this plan, I ended up with 12 component properties and 24 different variants for the Text Field component. The number of properties in the design panel was a lot more manageable: properties are scannable and findable again.</p><h4>Why not Base Component?</h4><p>One great thing about the previous way of using Base Component was that every possible option was available to see right on the canvas. The pain point, however, was that the sheer number of options makes the component hard to maintain. Adding a design element (e.g., an icon) to a component that has ~2000 variants was not only error-prone but also discouraging to design system contributors.</p><h3>What I learned so far</h3><h4><strong>A tool always comes with some caveats</strong></h4><p>Now that Figma opened everyone’s eyes with component properties, I wanted more: not only a better way to organize properties for findability, or to resize the design panel, but also how we could use it on a large, complex component without generating a sea of properties.</p><h4><strong>Short labels</strong></h4><p>Since the design panel is not yet resizable, it’s better to use short and succinct labels for each property. I omitted all default verbs like “show, swap, toggle” to avoid a full panel of labels like “Show star….”.</p><h4><strong>Figma Branch</strong></h4><p>Using Figma branches allowed me to have a peace of mind that the production file stays untouched throughout the optimization process. It also allowed our design system working group to test and discuss ideas without messing anything up.</p><h3>What’s next</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0ENPM2bEdvKbjNP0McVcg.png" /></figure><p>This is only a part of the story. We’re also planning to align the components API with our code counterpart’s API. What we expose in the property panel should be in sync with the code’s API. Also, our design system working group has an ongoing initiative to optimize these large components.</p><h4>Resources</h4><p>If you’re curious to learn more about design systems in general, check out these resources below.</p><ul><li><a href="https://help.figma.com/hc/en-us/articles/5579474826519">Create and use component properties</a></li><li><a href="https://help.figma.com/hc/en-us/articles/360040528173-Reduce-memory-usage-in-files">Reduce memory usage in files</a></li><li><a href="https://medium.com/eightshapes-llc/crafting-ui-component-api-together-81946d140371">Crafting components API, together</a></li></ul><p>And if you want to learn more about Auth0’s design system and its contributors, please don’t hesitate to reach out or comment below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e07eb09f448" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/how-we-optimize-a-large-design-system-component-1e07eb09f448">How we optimize a large design system component</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Increasing ResearchOps Impact Through Automation]]></title>
            <link>https://medium.com/auth0-design/automating-researchops-57137aa19c65?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/57137aa19c65</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[operations-research]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[research-process]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Rodrigo Dalcin]]></dc:creator>
            <pubDate>Fri, 18 Nov 2022 19:21:39 GMT</pubDate>
            <atom:updated>2022-11-28T16:37:42.735Z</atom:updated>
            <content:encoded><![CDATA[<h4>How our small research operations improved efficiency and increased org-wide awareness by automating key steps in our research process.</h4><figure><img alt="Featured illustration with diverse elements representing research and automation (e.g. pencil, clipboard, user interface, timer)." src="https://cdn-images-1.medium.com/max/1024/1*Z5YwS3eKRchHXr_5qMKZkg.png" /></figure><p>Research Operations (or ResearchOps) is often considered a tactical role/practice, sometimes requiring a lot of back-and-forth between parties and eating up chunks of time. This not only can be tedious for your Ops team but becomes increasingly troublesome when the demand for research in your company continues to grow despite your team’s limited capacity.</p><p>Here are some of the key tasks we’ve decided to automate in order to free up some of our bandwidth and how we leveraged existing tools to do it.</p><h3>Identifying the Problem</h3><p>In our day-to-day work, we spent a significant amount of time on fairly repetitive tasks: performing check-ins, running after stakeholders for updates, and conducting post-project retrospectives with researchers. For a lot of teams, this is good enough for ResearchOps: tactical support and enablement. Instead, we view ResearchOps as a strategic practice, so being stuck on manual work severely limits our impact.</p><p>This tactical workload also kept us from being more timely and proactive during the early stages of the research process, especially when it came to responding to research requests and recruiting study participants (which has downstream effects on research velocity). Beyond that, it kept us from thinking more strategically: how to break down silos, shorten the feedback loop, and share knowledge across product teams.</p><h3>Uncovering Opportunities</h3><p>Once we discovered how much of an impact this was having on our Operations team, we set out to identify automation opportunities that could be categorized under three main buckets:</p><ul><li>Keeping track of Research Projects</li><li>Ensuring everyone knows their current project status</li><li>Sharing and activation of research findings</li></ul><p>In order to identify the necessary triggers, actions, conditions, and desired outcomes, we mapped different workflows for each of the above categories. We then implemented these using <a href="https://www.workato.com/">Workato</a>, an automation platform that is thoroughly documented and integrates nicely with our existing toolset (notably Jira and Slack). Because Slack is Auth0’s main communication platform, we decided to drive most of the interactions through it. Slack also provides an abundance of integration and extension capabilities.</p><figure><img alt="A display of different flowcharts used to brainstorm researchOps automation opportunities." src="https://cdn-images-1.medium.com/max/1024/1*QJOjhAU-IO1Ql6aR5lR46w.png" /><figcaption>Some of the flows we mapped out.</figcaption></figure><p>After a few iterations, we wound up with four workflows. Here’s what life looked like before and after each:</p><h4>Processing Research Requests</h4><p><strong>Before automation</strong><br>Most often than not, one-off notifications from Jira were being ignored and forgotten depending on our workload priorities. This resulted in bottlenecks and delays when responding to research requests.</p><p><strong>After automation</strong><br>When a request for a new research project is submitted, both the Reviewer (usually our Research Strategist) and the Requester are greeted by a chatbot confirming the form submission. Going forward, whoever the project is currently waiting on will get another DM from the bot every 48 hours. This ensures that requests are reviewed in a timely manner and helps avoid bottlenecks in our pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nabq7kFxEJuuFIjGhiwmWw.png" /><figcaption>The automation powering our reminders, and an example of one of those messages.</figcaption></figure><h4>Supporting Participant Recruitment</h4><p><strong>Before automation</strong><br>Auth0 is an Enterprise SaaS company, meaning our Customer Success team has a strong say in how we engage with those sometimes-multi-million-dollar accounts. This, coupled with the CS team sometimes lacking enough context or having competing priorities (after all, their job is to keep customers happy, not help us recruit), would often delay our projects for multiple weeks.</p><p><strong>After automation</strong><br>As soon as a request is submitted, the ResearchOps team is notified so they can review the request and begin to prepare a Recruiting Plan. The Insights Request also contains an embedded recruitment criteria form that we can directly map to our customer database, increasing recruiting accuracy. Alongside these process improvements, we were able to establish rules of engagement for which customers can be contacted directly without getting CS involved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CCZ-fv08dFsEmpub4QsoHg.png" /><figcaption>The recruiting questions on our Research Plan template and some of the automation pieces.</figcaption></figure><h4>Sharing Research Findings</h4><p><strong>Before automation</strong><br>A lack of standardization of how Research Findings were communicated across the organization contributed to the issue of siloed research. Different formats, different channels, different cadences; nobody knew where to look or what to look for.</p><p><strong>After automation</strong><br>Workato &amp; Slack to the rescue once again! Researchers receive a form in Slack halfway through their study prompting them to share progress and updates. Once research is complete and added to our Insights Repository, Workbot compiles a summary and shares it in a few key channels in Slack.</p><p>Keeping everything in Slack reduces context switching and helps provide teams with timely updates. It also provides a lightweight way for everyone in the company to see what research is happening, learn more about our customers, and engage with a variety of our product teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXxWkcdRYDXj4omVaG8lUA.png" /><figcaption>How our Research Sharing automation works and examples of the messages generated.</figcaption></figure><h4>Tracking Research Impact</h4><p><strong>Before automation</strong><br>One of the drawbacks of running a heavily democratized research practice is you don’t always get to close the loop. The best way we had of capturing the results and impact of the variety of Research that happened at Auth0 was a bi-annual Research Engagement survey, leading to both sparse and infrequent updates.</p><p><strong>After automation</strong><br>A couple of weeks after finishing every project, Researchers are prompted to fill out a form with questions about the outcome of their research, what impact it had on their team, and what feedback they have for us on the process. Having a constant stream of updates has drastically improved not only our impact tracking but also our overall Research process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7UHUNczcJ9ZIQO3xZ05pHQ.png" /><figcaption>Impact tracking workflow and Slack form.</figcaption></figure><h3>Reaping the Benefits</h3><p>In as little as weeks after implementing these automations, we began to notice improvements:</p><ul><li>First, the Operations team, now freed from (some of) the burden of tactical support work, leveraged their new bandwidth to address research requests in a more timely manner, significantly decreasing the average first response time for request tickets in Jira.</li><li>The automated reporting also increased awareness of research findings across different teams, generating some buzz in Slack with each bot post.</li><li>At our next Research Engagement survey, we saw an increase in the perceived value of automated workflows as well as an increase overall in research engagement and satisfaction.</li></ul><figure><img alt="Screenshots demonstrating positive impact of researchOps automation (e.g. infographics and Slack comments)" src="https://cdn-images-1.medium.com/max/1024/1*F9q48eLHI0A0od8yt-fOPw.png" /><figcaption>Measurable impact of researchOps automation</figcaption></figure><h3>Great! Let’s automate everything!</h3><p>Not so fast. The one thing automation will never replace is human interaction. While we’ve seen a lot of benefits, we’ve also noticed some drawbacks. People will tend to deprioritize messages coming from a chatbot in Slack, resulting in lower engagement, particularly for notifications taking place after research has been wrapped up (such as retros or post-mortems). This increases friction in tracking research impact across the organization.</p><p>We’ve also realized quickly that, as soon as our processes change or evolve, this creates new opportunities for automation. Your process should evolve to meet the changing needs of your People Who Do Research (PWDR).</p><h4>What’s next</h4><p>With all of this in mind, we are currently planning our next batch of automated workflows. These will reflect recent changes in our recruitment process as well as the implementation of research KPIs defined to track the velocity of each step in our research process. Increased visibility will help us home in on the opportunities which have the greatest impact.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57137aa19c65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/automating-researchops-57137aa19c65">Increasing ResearchOps Impact Through Automation</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started with Inclusive Research]]></title>
            <link>https://medium.com/auth0-design/getting-started-with-inclusive-research-5971cdd8de48?source=rss----640ea82476da---4</link>
            <guid isPermaLink="false">https://medium.com/p/5971cdd8de48</guid>
            <category><![CDATA[inclusive-research]]></category>
            <category><![CDATA[auth0]]></category>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[accessibility-research]]></category>
            <dc:creator><![CDATA[Carolyn Shetter]]></dc:creator>
            <pubDate>Mon, 17 Oct 2022 14:53:21 GMT</pubDate>
            <atom:updated>2022-10-18T17:43:34.028Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Beginner’s Guide</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LelPPvScabE2U_seHk9CIQ.png" /></figure><p>Diversity, equity and inclusion (DEI) initiatives are getting a lot of buzz in the corporate world right now, but not everyone is taking action to make their products inclusive to all. For Auth0, our design team has focused resources on improving the accessibility of our products. My team, the research team, was encouraged by the design team’s efforts.</p><p>What started out as an initial dip into the waters of inclusive recruiting became an experience that demonstrated how our research team could grow overall. As the person who spearheaded this project, I struggled at first to find information to move this work forward. I found a handful of Medium articles that shared a lot of general insight, but I was looking for step-by-step guides. I hope this article can serve as a resource for other researchers and operations professionals who want to start the journey to create a more inclusive research practice.</p><h3>How It Started</h3><p>I found a few folks who were also interested in accessibility within research by attending <a href="https://uxrconf22.joinlearners.com/">UXR Conf</a> in June. I reached out to them on LinkedIn and learned about their experiences.</p><p>I had two conversations: one with a former researcher at Thomson Reuters, Divya Pal, and another with an accessibility researcher at ServiceNow, Jaime Young. They both helped me get my bearings and prioritize what I should focus on first. We discussed everything from recruitment tools and training to networking and executive sponsorship.</p><h3>What I Have Learned So Far</h3><h4>Connect With Others Who Are Doing the Work</h4><p>My colleague, Divya, worked at Thomson Reuters as a researcher. Reuters is an interesting example. They have a lot of accessibility resources in comparison to most companies. Specifically, they have accessibility specialists for each product team, and those specialists had connections with different nonprofit partners. They were able to leverage these relationships to source participants for research studies.</p><p>Networking internally has also been helpful for us at Auth0. I recently connected with Ed Armstrong, a copywriter, who is also interested in accessibility work. He has worked closely with our social impact team for a large nonprofit in the UK, Community Integrative Care. They work with folks with different kinds of accessibility needs and disabilities. Graciously, they want to help us make our product more inclusive. Although we don’t know exactly what this will look like, it is encouraging to have organizations who want to work with us as much as we want to work with them.</p><h4>Recruitment Tools Can Be Helpful</h4><p>In the research space there are a myriad of tools that help recruit different audiences for research. Our team’s first inclination was to discover any tools that specialized in recruitment of people with disabilities or accessibility needs.</p><p>The only option I found was <a href="https://makeitfable.com/">Fable</a>, a fantastic company that has a several hundred person candidate pool of people with disabilities. My team had considered using the tool, but ultimately it did not work for our needs. Jaime, my colleague from ServiceNow, uses Fable in her practice.</p><figure><img alt="A screenshot from the home page of Fable, the inclusive recruiting tool." src="https://cdn-images-1.medium.com/max/1024/1*6ouYVn59bVuBtDI2x0d7uQ.png" /><figcaption>Fable helps companies complete accessible and inclusive research with the general population.</figcaption></figure><p>Jaime and I have the same experience of working at companies that primarily have products that are meant for very technical people, and for us at Auth0 that means developers. While ServiceNow does use Fable, they tend to use it for general population research and not for customer research. General population research is often open to anyone, whereas customer research has specific requirements for participants. For Auth0, our requirements often include that participants are developers of a certain amount of experience and technical skill. Therefore, my team opted to not use Fable because we do not have a need for general population research. However, Fable did give us a lot to think on regarding how we would treat folks with disabilities or accessibility needs in our panel.</p><p>Fable values their panel participants and pays them a competitive wage. They treat the panel like a community and want participants to feel valued and understood. Our team realized that we cannot treat people with disabilities as a number, and that they offer something that no other group can give us. Our conversation with Fable has affected how we view and treat people with disabilities and accessibility needs. I highly recommend their services if their candidate pool fits your needs.</p><h4>Executive Sponsorship Helps</h4><p>One of the things I learned from Jaime at ServiceNow was the importance of executive sponsorship.<strong> </strong>The more you can create a business case for this work, the more support you’ll have. For example, find company wide goals and see how creating an inclusive research practice could positively impact them.</p><p>Gaining executive sponsorship keeps the momentum of inclusive research going. When you hit roadblocks or there’s turnover there will be someone to continue to push the work forward. It is also helpful for creating buy-in: if an executive owns the project the more likely others will jump on board and want to accomplish your goals.</p><p>For us at Auth0 that means looking at our vision for the fiscal year and aligning our objectives with the overall goals of the company. For example, our mission for the next few years is to grow active users. Accessibility work can improve the experience of all users as well as draw in new ones. This is one way we can encourage leadership to support our objective to become an inclusive research practice.</p><figure><img alt="Quote from the article: Gaining executive sponsorship keeps the momentum of inclusive research going." src="https://cdn-images-1.medium.com/max/1024/1*HGtCrB96CjqJzgTw4gI4Ug.png" /></figure><h4>Training Matters</h4><p>The importance of training is something I heard emphasized in multiple conversations about inclusive recruiting, but it is often overlooked. At Auth0, we use a democratized research model. Democratized research practices open up research to all who are interested. Our team helps designers, product managers, product marketers, and pricing and strategy experts complete research. For us to have a true inclusive recruiting practice we would need to have formalized training for all potential researchers, not just our team specific researchers.</p><p>My research into accessibility training showed that these efforts are generalized and unhelpful<strong>. </strong>Most programs covered what accessibility means and how to be WCAG compliant. There is a need for specific training on how to conduct research with people with disabilities and accessibility needs. Divya mentioned in her time doing research at Reuters she did not always feel prepared for interactions with folks with accessibility needs in her research. A challenge she faced was with moderating sessions with those who use screen readers.</p><p>Training is easy to overlook at the beginning of the inclusive research journey. However, inclusive research practices need to look at the whole picture, not just a snapshot in time of the process. In order to have quality interactions with people with disabilities or accessibility needs, training needs to be put in place to make researchers and participants comfortable.</p><h3>Where We Are Now</h3><p>We have made progress, but we are still in the beginning stages of our practice becoming more inclusive. We have made some small tweaks that have already made an impact.</p><p>For instance, we improved our panel questions that focus around inclusivity and accessibility to be more open and less diagnosis-based. In the past, we used a more clinical definition of accessibility needs. These related to how people used computers. This included motor impairments, cognitive impairments, mental impairments and visual impairments. Now, we use a more open definition of accessibility needs or disabilities that allow for more nuance, as can be observed in the image below.</p><figure><img alt="Side by side images of our past question regarding accessibility needs and our current identity-based disability question." src="https://cdn-images-1.medium.com/max/1024/1*4tkAvSMKF-4NBJ0yWO5d8w.png" /><figcaption>To the left is our old language, and the right our new inclusive language.</figcaption></figure><p>This change in language had a drastic effect in a recent developer survey. We had 602 respondents, and 12.5% of them identified as someone with an accessibility need or disability. For reference, our research panel beforehand showed that approximately 1% of our candidates had an accessibility need.</p><p>Finally, we are excited to continue our inclusive research journey with Community Integrative Care in the UK. The partnership with research is still in its infancy, but we are excited for what is to come in the future.</p><h3>Special Thanks</h3><p>I wanted to take this opportunity to give a special thank you to <a href="https://www.linkedin.com/in/divya-pal/">Divya Pal</a> and <a href="https://www.linkedin.com/in/jaimeyoung51/">Jaime Young</a> for their support and knowledge. Their support helped me continue to pursue this work, including writing this very article. Thank you for all that you do to push this work forward!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5971cdd8de48" width="1" height="1" alt=""><hr><p><a href="https://medium.com/auth0-design/getting-started-with-inclusive-research-5971cdd8de48">Getting Started with Inclusive Research</a> was originally published in <a href="https://medium.com/auth0-design">Auth0</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>