<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Donna Choi on Medium]]></title>
        <description><![CDATA[Stories by Donna Choi on Medium]]></description>
        <link>https://medium.com/@donnachoi?source=rss-33be53ecea7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*-MftcKSRvSDc_zx5xn8XnQ.jpeg</url>
            <title>Stories by Donna Choi on Medium</title>
            <link>https://medium.com/@donnachoi?source=rss-33be53ecea7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:17:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@donnachoi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Case Study: Home Loan Processing on the Sofi Mobile App]]></title>
            <link>https://medium.com/swlh/case-study-loan-processing-on-the-sofi-mobile-app-5a9786c61685?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a9786c61685</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Mon, 21 Sep 2020 22:59:42 GMT</pubDate>
            <atom:updated>2020-09-22T02:51:36.527Z</atom:updated>
            <content:encoded><![CDATA[<p>Getting a home loan can feel opaque and intimidating to the average person. With pages and pages of legal jargon to navigate (not to mention large sums of money on the line!), it can feel overwhelming to understand what is happening, why, what questions to ask, and how to protect yourself.</p><p>I became a first-time homeowner several years ago and refinanced my mortgage twice since then. I’ve worked with two different lenders: one operating primarily through phone and email, the other (Sofi) operating largely through their software. While going through my refinance with Sofi, I was pleasantly surprised by the digital-first experience and became interested in exploring how their loan processing experience could be further improved.</p><p>This case study focuses on the loan processing experience within the Sofi mobile iOS application. I decided to focus on the mobile app because that’s largely where I interact with Sofi products, plus I wanted to brush up on my native mobile app design thinking.</p><h3>Initial research and identifying pain points</h3><p>I started by conducting UX teardowns of Sofi’s current mobile loans experience, as well as that of other personal finance applications. I also interviewed people who have recently refinanced home loans to understand their pain points, and refreshed my knowledge of mobile app user research and best practices by reviewing <a href="https://www.nngroup.com/reports/mobile-website-and-application-usability/?lm=state-mobile-ux&amp;pt=article">NNGroup’s report on mobile app/web UX</a>.</p><p>Based on this initial research, I identified a high-level user story: as a person who is currently refinancing their home loan with Sofi, I<strong> want to use the mobile app to</strong> <strong>check the status of my loan</strong> and <strong>browse for information that will help me save money, reduce risk, and make better decisions about this and future loans</strong>. Based on this user story, here are the key pain points I identified with the current mobile app loans experience.</p><p><strong>Pain point #1</strong>: Not enough transparency about my loan status. For example, what is actually happening during the “processing” phase, what do I need to prepare to submit to my lender, and how can I help ensure that the closing date isn’t delayed?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7siKaLVBPgaTpeecg3piYQ.png" /><figcaption>Current loan processing timeline, which appears near the bottom of the loan view.</figcaption></figure><p>The loan processing timeline isn’t granular or informative enough, and while the To-Dos section provides a record of documents that I’ve submitted or received, it doesn’t include records for approvals or verifications from my lender, or of messages exchanged with my loan officer.</p><p><strong>Pain point #2</strong>: Loan navigation can feel cumbersome. My loans dashboard deemphasizes my existing/in-progress loans, making it harder to get to my in-progress loan and distracting me with sales pitches for new loans I’m not particularly interested in at the moment.</p><figure><img alt="Current loans dashboard view" src="https://cdn-images-1.medium.com/max/1024/1*9ygZQpbzSrs615bcCua_Jg.png" /><figcaption>Current loans dashboard</figcaption></figure><p>In addition, navigating within my in-progress loan can be confusing, with a hamburger menu offering redundant navigation items and emphasizing unlikely mobile calls-to-action (eg. will users really be uploading W2s from their phones?).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JmmcnHZ8GiFVDEPuyB3CBg.png" /><figcaption>On the left: loan hamburger menu. On the right: document upload CTA.</figcaption></figure><p><strong>Pain point #3</strong>: Not only do I find sales pitches for new loans to be distracting, but if I <em>were</em> interested, these pitches don’t give me a soft entry point to learn more about how these loans will benefit me, the right time to buy, and why I should trust Sofi. Is there a way to highlight selling opportunities while also providing some kind of unique value to the user and building brand credibility?</p><h3>Design iteration and user testing</h3><p>I went through several design iterations and tested them with a user before landing on the solutions described below.</p><p><strong>Solution #1</strong>: Improved loan navigation, with a clearer path to my existing loans from the loan dashboard and more lightweight navigation within my in-progress loan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YJCOCxTeQOZxNC9KjKQGZw.png" /><figcaption>On the left: my loan dashboard. On the right: in-progress loan view.</figcaption></figure><p>The hamburger menu has been removed, replaced by summary views with links to full views below each summary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*nbj1PRoPPijoAT_Qtx3WTg.gif" /><figcaption>Navigating from the loan dashboard to my in-progress loan.</figcaption></figure><p>The loan timeline is pulled up to the top of the screen and supplemented with information relevant to completing the process successfully, such as estimated closing dates and cash-to-close. The hypothesis behind this reprioritization of information is that users checking on their in-progress loan are often first interested in dynamic information like status updates and tips to prepare for next steps, and then will follow with less dynamic or more granular information such as loan details, loan comparisons, or detailed activity breakdowns.</p><p><strong>Solution #2</strong>: More transparency into my loan status and activity. There are three top-level statuses in my loan progress timeline, which I can click into in order to see a status definition, a more granular breakdown of steps within each status, and tips for what I should and shouldn’t be doing at this stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Ra390onSyr8cxBAAKwWLzA.gif" /><figcaption>Getting information about my loan status.</figcaption></figure><p>My activity timeline includes a record of documents submitted (and a path to view uploaded docs), messages exchanged between myself and my loan officer, and approvals or verifications from my lender.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tKuRqhbTs59tONW_t5QI6w.png" /><figcaption>On the left: truncated Activity summary in my Loan view. On the right: Activity detail.</figcaption></figure><p><strong>Solution #3</strong>: The loans dashboard now includes a new feature, the loans watchlist, in addition to educational articles for users to browse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zavF8E7StaplulA54-puXQ.png" /><figcaption>On the left: list of loans that I’m watching. On the right: detail of loan watchlist item.</figcaption></figure><p>The loans watchlist allows users to watch interest rates for loans based on their personal criteria, plus receive recommendations from Sofi about the right time to take out the loan based on rates and other factors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*2EFRLAyLB72xZin05NgLAQ.gif" /><figcaption>Viewing my loan watchlist item.</figcaption></figure><p>This feature empowers users with unique, credible information, since interest rates over time can be an opaque yet key data point for determining which lender to go with and when. Currently, users must rely on information from a loan officer or continuously fill out interest rate estimators and loan applications.</p><p>The hypothesis is that by providing transparency into interest rates over time, Sofi differentiates itself and builds brand credibility by providing valuable, unique knowledge currently unmatched by other lenders.</p><p>This feature could also be useful from a business standpoint because it provides a soft entry point for a loan application. After all, the data that a user enters to create a watchlist item is effectively the same data that they would use to start an application.</p><h3>Reflection and open questions</h3><p>This case study allowed me to exercise my mobile app design thinking and deep dive into a problem space that I’ve become familiar with in the last several years. It also left me with lots of open questions, such as:</p><ul><li>The shift to a more digital loan processing experience is, I expect, rife with legal and institutional barriers. It is also a shift to a world that could leave behind consumers with less tech access or savvy. What are those legal and institutional barriers? Who makes up Sofi’s target markets, and what are steps the team can take to broaden access?</li><li>The loans watchlist concept has many unknowns, namely: what are potential business costs or barriers to making interest rates more transparent? Does the consumer value outweigh potential business costs? How much do most consumers (vs. power users) care about this information?</li><li>What are other user needs and pain points with loan processing and education? What are other tools beyond the loans watchlist that could empower the user with information and build brand credibility?</li></ul><p>Thanks for reading! If you have your own stories about loan processing, I’d love to hear. Please leave a comment or email me at <a href="/service/mailto:donnachoi30@gmail.com">donnachoi30@gmail.com</a>. You can also find me at <a href="http://donnachoi.com/">http://donnachoi.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a9786c61685" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/case-study-loan-processing-on-the-sofi-mobile-app-5a9786c61685">Case Study: Home Loan Processing on the Sofi Mobile App</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Job Search at Stack Overflow]]></title>
            <link>https://medium.com/swlh/case-study-job-search-at-stack-overflow-ba63f417be1d?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba63f417be1d</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[search]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Thu, 17 Sep 2020 22:02:41 GMT</pubDate>
            <atom:updated>2020-09-20T00:04:40.254Z</atom:updated>
            <content:encoded><![CDATA[<p>During my tenure at Stack Overflow, one of my team’s major goals was to increase job applications submitted through our product. We knew that search was the primary path through which people found and applied to jobs, yet we hadn’t invested in improvements in years. I was tasked with researching and designing areas that would improve the job search experience by helping users quickly and easily find jobs that they’d want to apply to.</p><h3>Current state</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*kelQFrgllVvE_YEO-opAnA.gif" /><figcaption>Current state for job search</figcaption></figure><p>I started by analyzing the current state of job search, digging into usage analytics, and reviewing existing qualitative feedback. I identified a few key problem areas:</p><p><strong>Problem #1</strong>: Easy-to-use, desirable filter options were either not available or accessible only through advanced syntax search, which saw very low usage and required users to enter complex queries to run even the most basic searches. Based on our existing knowledge of our users, we hypothesized that compensation, benefits, and technologies were the most important filtering options that were currently missing or hard to discover.</p><p><strong>Problem #2</strong>: Job alerts, which allowed users to get email updates when new jobs matching their search criteria were published, were extremely hard to discover. They were hidden at the bottom of the search results view and available only to logged-in users within certain states of search. As a result, subscriptions were low. We hypothesized that if job alerts were more discoverable and available to more users, subscriptions would increase, followed by the number of job applications.</p><p><strong>Problem #3:</strong> Keyword search didn’t match common sense user expectations. For example, if a user typed “remote jobs” in the keyword field, search would return jobs that contained an exact match of “remote jobs” in the job title or description, rather than returning jobs tagged with “remote” metadata. We hypothesized that keyword search was the easiest, most direct path for users to search and filter for jobs (easier, still, than a filter UI), so we wanted to ensure that users using keyword search would benefit from the quality of filtered search results.</p><h3>Design, research, repeat</h3><p>We conducted multiple rounds of design iteration, user research, and experiments in order to suss out our job search solution. Here were a few things we learned and iterated upon along they way:</p><ul><li>User research told us that technology and compensation were the most important qualities that users wanted to filter against. However, benefits filters were not as useful as we had hoped, partially because of the lack of quality, specific benefits data that users felt they could trust. As a result, we visually prioritized technology and compensation filters, and visually deprioritized benefits filters.</li><li>An experiment told us that “job collections”, which were pre-defined, popular job search queries that we surfaced to users at the top of the search results view, did not drive any particular increase in job views or applications. As a result, we scrapped the “job collections” concept and focused on user-directed filters like core search, filtering, and sorting.</li><li>User research told us that clearing and editing existing search queries had some clumsy interactions, and that it needed to be much simpler to see one’s existing query, add or remove criteria, and clear all criteria.</li></ul><p>Following multiple iterations and rounds of research, here’s where we landed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HGroWJzXBGOvD99RatqWFA.png" /><figcaption>Job search with filters pane and prominent “Create alert” button</figcaption></figure><p>The Search button was rendered redundant thanks to Ajax-driven search results, where results would automatically run if the user took certain actions with their keyboard or mouse. Usability research allowed us to finesse these search result micro-interactions so that users weren’t left confused about the lack of the Search button or frustrated by overly frequent, unexpected search result updates. Additionally, through a series of experiments, we continuously improved keyword search.</p><p>In place of the Search button, we added a prominent “Create alert” button, which was now available to everyone (including unregistered users!) in a highly discoverable location. We saw an exponential increase in newly created job alerts and a resulting increase in job applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hFbMB9Mdg-i6dF_uFfjQpQ.png" /><figcaption>Creating a job alert</figcaption></figure><p>We also implemented a rich set of filter options, including technologies, salary, equity, experience level, and benefits filters. The filter pane was further improved by my colleague Paweł Ludwiczak, who made the pane more accessible through keyboard navigation optimizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*XY0HKmEXqzMZymNFDLkjAA.gif" /><figcaption>Filter options</figcaption></figure><h3>Further iterations</h3><p>Following this release, the team, led by Piper Lawson and Courtny Cotten, continued to improve job search. For example, filter categories became fully exposed on the search result view, rather than obscured behind a filter button. The search button was also brought back, as subsequent feedback taught the team that its absence led to some user confusion.</p><h3>Reflection</h3><p>Working on job search was a great learning experience, as was observing my colleagues’ continuous learning and iteration on this feature area. I, like, many users, take high quality search for granted thanks to the high bar set by Google Search. I learned how difficult it is to get search <em>just right </em>and to find the balance between giving users control and making assumptions on their behalf.</p><p>Thanks for reading! If you have your own stories about search, I’d love to hear. Please leave a comment or email me at <a href="/service/mailto:donnachoi30@gmail.com">donnachoi30@gmail.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba63f417be1d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/case-study-job-search-at-stack-overflow-ba63f417be1d">Case study: Job Search at Stack Overflow</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Identity and visual design for Japanese Language Stack Exchange]]></title>
            <link>https://medium.com/design-bootcamp/case-study-identity-and-visual-design-for-japanese-language-stack-exchange-2dec4598fec3?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2dec4598fec3</guid>
            <category><![CDATA[japanese-language]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Wed, 16 Sep 2020 18:53:03 GMT</pubDate>
            <atom:updated>2020-09-18T04:37:16.419Z</atom:updated>
            <content:encoded><![CDATA[<h4>A question and answer site for students and enthusiasts of the Japanese language.</h4><p>During my tenure at Stack Overflow, I was tasked with designing an identity and visual design for <a href="https://japanese.stackexchange.com/">Japanese Language Stack Exchange</a>, a question and answer site for students and enthusiasts of the Japanese language.</p><h3>Research and concept development</h3><p>When developing early concepts, I drew inspiration from user feedback, Japanese art and writing, and Japanese aesthetic philosophy.</p><p>First, I scoured existing ideas from the community for the site’s design aesthetic. I was interested in learning about their design ideas as well as the metaphors and experiences that inspired their ideas.</p><p>One thing that resonated with me was the nuanced, challenging experience of learning a new language. As a semi-fluent Korean speaker, I’ve often found myself communicating in basic vocabulary, removed of the embellishments and nuances that intuitively came to me in English. While frustrating at times, I experienced depth and beauty in this simplicity. I could say to my relatives, “thank you for your kindness.” I could not easily embellish that with jokes or comments that I might otherwise deploy to fill space or deflect from the weight of that sentiment.</p><p>I became interested in visualizing this simplicity — what does it look like when you pare communication down to its most fundamental components, and how does that translate to a site design?</p><p>I started exploring ways to translate these ideas into a visual experience. I learned about <a href="https://en.wikipedia.org/wiki/Wabi-sabi">wabi-sabi</a>, a Japanese design philosophy that values simplicity and intimacy in art.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yMY8iUHknbyJ9RkyftUToQ.png" /><figcaption>Mood board of Japanese art, characters, and patterns.</figcaption></figure><p>I drew inspiration from the minimalist forms, geometric line work, and cool, desaturated colors of Japanese patterns, writing systems, and architecture. I used these to iterate on first concepts for Japanese Language Stack Exchange.</p><h3>Initial identity and site design</h3><p>For the logo, I wanted to convey the linear elegance of Japanese writing systems. As the site’s main signature, the red logo is designed to resemble a Japanese chop. For the typeface, I took inspiration from Japanese characters as well as the stereotypical “Chopsticks” font, paring the letters down to the their most minimal form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bfQdMCWYvIU6edTaaIS9vg.png" /><figcaption>Initial concept for Japanese Language logo</figcaption></figure><p>I also applied traditional Japanese patterns and a cool, desaturated color palette to the site design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4QWJIbjPNedDl00qzNTC7g.gif" /><figcaption>Initial concept for Japanese Language site design</figcaption></figure><p>I designed swag for the site as well, which Stack Overflow would provide to community members for excellent community stewardship or during contests and giveaways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CBHlyKph9LFKGU-bTRiQ6A.png" /><figcaption>Swag for the Japanese Language site</figcaption></figure><h3>User feedback and more iterations</h3><p>The initial concepts were <a href="https://japanese.meta.stackexchange.com/questions/1564/japanese-language-new-site-design/1570">proposed</a> to the Japanese Language community and iterated upon by my colleague, Paweł Ludwiczak. Users had difficulty interpreting the initial logo concept and some of the iconography, so these were updated based on their feedback and ideas. Some custom elements of the site design were also pared back as part of a broader effort at Stack Overflow to standardize site designs across the Stack Exchange network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*X1JGgRr6D8uKma-2eYviDQ.gif" /><figcaption>Shipped iteration for the Japanese Language site</figcaption></figure><p><a href="https://japanese.stackexchange.com/">The Japanese site design is live</a>. I’m excited to have had the opportunity to contribute to this community and look forward to seeing it grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2dec4598fec3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-identity-and-visual-design-for-japanese-language-stack-exchange-2dec4598fec3">Case study: Identity and visual design for Japanese Language Stack Exchange</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Giving feedback early and often]]></title>
            <link>https://uxdesign.cc/give-feedback-early-and-often-1a1f8a4d19ab?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a1f8a4d19ab</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Thu, 18 Jun 2020 23:12:09 GMT</pubDate>
            <atom:updated>2020-06-30T11:12:58.078Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Awesome vs. less awesome" src="https://cdn-images-1.medium.com/max/1024/1*iqOjC5Kbzo4G0dPmvzrC-g.png" /><figcaption>Photo by<a href="https://unsplash.com/@jontyson?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"> Jon Tyson</a> on Unsplash</figcaption></figure><p>You’ve asked your manager for feedback. They tell you that you’re doing great and that everyone loves working with you. Then performance evaluation season rolls around, and your review contains some surprising feedback: one of your team members thinks you’re difficult to work with, and another believes the caliber of your work is poor. Needless to say, you won’t be getting that raise you were hoping for.</p><p>Some of us have had this experience or heard horror stories about it. Some of us work at companies with underdeveloped feedback systems, where we receive feedback long after the fact or not at all, limiting our opportunities for improvement. Still others are the ones responsible for delivering feedback, but we don’t know how and just really, really want our reports to<em> like </em>us.</p><p>When I became a manager, I struggled with the last point. Back when I was a designer, my feedback ethos was simple: praise colleagues in public, offer critique in private. Most of the feedback I offered was positive and product-oriented (“Yay, the new feature looks great!”). I delivered constructive feedback occasionally, but usually when it was actively solicited or if something egregious had happened.</p><p>My feedback ethos had to evolve when I became a manager. It was now my responsibility to deliver balanced feedback to my reports in a timely, evidence-based manner. This feedback and my reports’ ability to act on it directly affected their compensation and livelihoods. Here are some lessons that I learned during my time managing a small design and research team at Stack Overflow, which operates under the <a href="https://en.wikipedia.org/wiki/Servant_leadership">servant leadership</a> philosophy.</p><p>✅ <strong>Deliver feedback </strong><a href="https://hbr.org/2009/04/feedback-that-works"><strong>early and often</strong></a>. Small, incremental bits of feedback are more manageable for your report than a list of the things they’ve done wrong in the last year. This approach also ensures that you are catching and redirecting problems early.</p><p>❌ <strong>Don’t save feedback for annual performance reviews</strong>. This robs your report of the chance to act upon the feedback, and may make them feel blindsided or resentful.</p><p>✅ <strong>Gather the facts before delivering feedback. </strong>If someone expresses concern about your report, ask them questions like: “Can you walk me through the sequence of events?” or “Where did this happen, and was anyone else involved?” This helps you understand the scope and severity of the issue, and will help you communicate the feedback to your report in a calm, evidence-based manner.</p><p>❌ <strong>Don’t relay hand-wavy feedback</strong>. There is a huge difference between telling your report that their team members think the quality of their work has been poor lately versus telling them that team members have observed that their last report contained serious methodological errors. The former is too broad to be actionable and is likely to trigger a defensive response. The latter is specific and fact-based. It’s a starting point for a conversation about what went wrong in the last report, and how your report can improve their approach moving forward.</p><p>✅ <strong>Be </strong><a href="https://firstround.com/review/humans-hate-being-spun-how-to-practice-radical-honesty-from-the-woman-who-defined-netflixs-culture/"><strong>direct</strong></a><strong> with your feedback</strong>. If you have something constructive to say, lead with that.</p><p>❌ <strong>Don’t bury constructive feedback in a compliment sandwich</strong>. This can mislead your report and cause them to miss the most important bits.</p><p>✅ <strong>Give your report a chance to offer their version of events — and </strong><a href="https://medium.com/swlh/how-managers-can-deliver-more-effective-feedback-96d97cbe7797"><strong>really listen</strong></a><strong>. </strong>Once you have aligned on the actual events, show your support by offering to problem-solve with them.</p><p>❌ <strong>Don’t take a one-sided approach</strong>. Don’t monologue or let your report hijack the conversation. When it comes time to problem-solve, don’t put the responsibility solely on yourself or your report. Work together to come up with next steps.</p><p>✅ <a href="https://firstround.com/review/humans-hate-being-spun-how-to-practice-radical-honesty-from-the-woman-who-defined-netflixs-culture/"><strong>Practice what you plan to say</strong></a><strong> (especially if you’re delivering constructive feedback for the first time!)</strong>. It can be helpful to write down an outline of the conversation in advance. If the situation allows, read it verbatim if you have to. Another option is to role-play the conversation with a friend or trusted colleague.</p><p>❌ <strong>Don’t ad-lib it, unless you’re very confident with your ability to deliver constructive feedback to your reports</strong>. As a manager, your words carry a lot of weight. A small foot-in-mouth moment can have severe unintended consequences by damaging your report’s trust in you, their colleagues, or their own abilities.</p><p>✅ <strong>Observe and deliver feedback about “invisible” contributions like communication, inclusion, and time management</strong>. This helps ensure that you’re encouraging a well-rounded skill set and placing value on skills that are often overlooked or underappreciated on technical teams.</p><p>❌ <strong>Don’t focus solely on work outcomes, like things shipped or research reports released.</strong> This may be new for you if you come from a technical role that is focused on hard deliverables. However, getting in the habit of noticing soft-skills contributions will help you become a <a href="https://firstround.com/review/thoughts-on-gender-and-radical-candor/">more inclusive manager.</a></p><p>✅ <strong>Regularly invite your report to give constructive feedback about you</strong>. Not only is feedback useful for your growth, but this approach helps to build trust and rapport with your report. By inviting and accepting feedback, you are communicating that you value their perspective. This can help your report be more open and trusting when they hear constructive feedback from you.</p><p>❌ <strong>Don’t assume that your report will provide unsolicited feedback.</strong> It can be intimidating to give managers and higher-ups constructive feedback, and your report may have fears that doing so will damage their career or standing with you.</p><p>Learning to deliver feedback proactively, directly, and compassionately was a valuable lesson from my time as a design and research manager at Stack Overflow. I’ve carried this with me to my new role at RStudio. Being a manager helped me become a more patient, empathic contributor and leader. Although I’m no longer managing, I’m eager to apply these lessons at a company that is in the early stages of <a href="https://www.nngroup.com/articles/ux-maturity-stages-1-4/">UX maturity</a>.</p><p>What’s been your experience delivering feedback as a new manager? What have you learned along the way, and what do you wish you’d known when you started?</p><p>Thanks for reading! If you have any feedback or questions, please share in the comments below or email me at donnachoi30@gmail.com.</p><p>🙏 <em>There’s a lot of great literature out there about giving effective feedback. Here are a few that helped me tremendously during my time as a manager:</em></p><ul><li><a href="https://www.amazon.com/Making-Manager-What-Everyone-Looks/dp/0735219567"><em>The Making of a Manager</em></a><em> by Julie Zhuo</em></li><li><a href="https://www.linkedin.com/learning/giving-and-receiving-feedback/the-art-and-science-of-feedback"><em>Giving and Receiving Feedback</em></a><em> by Linkedin Learning</em></li><li><em>First Round’s </em><a href="https://search.firstround.com/topics/feedback"><em>treasure trove of articles about feedback</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a1f8a4d19ab" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/give-feedback-early-and-often-1a1f8a4d19ab">Giving feedback early and often</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build products with expert users]]></title>
            <link>https://uxdesign.cc/how-to-build-products-with-expert-users-b3ea409ecfa2?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3ea409ecfa2</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Mon, 23 Dec 2019 21:35:41 GMT</pubDate>
            <atom:updated>2019-12-31T01:58:43.720Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*icYSz3ZPfgtcFaw0z7OU5g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Austin Distel</a> on <a href="https://unsplash.com/s/photos/expert?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Users who are knowledgeable and excited about your product offer unique challenges. They deeply understand the ins and outs of your product and are overflowing with ideas about how to make it better. They’re smart, articulate, and persuasive. They want your time and attention, and they expect to guide the direction of the product.</p><p>Your team may have differing opinions about what to do with these expert users. Some consider them to be the heart of your user base and believe staff should do more to listen, engage, and include them in decision-making. Others are cautious about over-indexing on expert user feedback, believing it leads to myopic decision-making that serves the most elite users at the expense of others.</p><p>How do you nurture and serve your expert users while firmly balancing their needs against those of less vocal users? How do you build a healthy, constructive relationship between staff and expert users? What if your team has limited time and budget for community relations and user research?</p><p>These are questions that we’ve grappled with at Stack Overflow. Historically, we’ve had a highly involved expert user base that worked closely with the team to drive product development. As our community has grown, our approach to product development has evolved — and with it, so has the role of the expert user.</p><p>Below are tips for building products with expert users, based on lessons learned from Stack Overflow’s (occasionally rocky) journey toward building a healthy, balanced relationship with expert users.</p><h3>#1. Be transparent and show your process as much as possible</h3><p>Expert users often want visibility into how you work and why you make certain decisions. Sharing research insights — whether that’s qualitative research findings or quantitative analyses — is a great a way to do this. Not only does this give expert users visibility into the process, but it also helps to build trust in decision-making by demonstrating that you’re using evidence to make decisions.</p><p>Sharing your research also enables expert users to become more knowledgeable, empathetic contributors. By seeing your research, they can offer richer feedback. They can also better empathize with decisions that they disagree with because they have visibility into <em>why </em>you made those decisions. This is valuable because expert users are often your greatest evangelists.</p><p>Be as specific as possible when sharing your process, and avoid anything that could be interpreted as fluff.</p><p>✅ <strong>Do</strong>: “Users generally favored the new search feature. They particularly appreciated how quickly results loaded and how easy they were to scan. Some users were concerned about the privacy of their search activity.”</p><p>❌ <strong>Don’t</strong>: “People liked the new search feature a lot. They had great things to say about it.”</p><h3>#2. Be mindful of the time and energy your team invests in expert users</h3><p>They’re expert users for a reason! They’re smart, articulate, and persuasive. Members of your team may form friendships with these users, relate to them, and simply be excited to engage with savvy users who care about what your team does. Isn’t it a relief that people want to learn about your process and read your research? Why not spend as much time as you can making these users happy?</p><p>Engaging with expert users can be emotionally fulfilling in a way that typical research or product development may not be. Because of this, you may find yourself spending the bulk of your time listening to and talking with users who ultimately make up a tiny fraction of your user base. However insightful, they are not representative of the full range of perspectives that your team needs to hear.</p><p>Look for the most impactful, cost-effective ways to engage with your expert users, and focus on those.</p><p>✅ <strong>Do</strong>: develop realistic commitments and stick to them. Create a regular, proactive cadence for engaging with expert users. Adjust your approach based on feedback and the capacity of your team.</p><p>❌ <strong>Don’t</strong>: commit to things that are unsustainable or will be done irregularly. Don’t reactively do everything that expert users want. Don’t try to convince every expert user to see things your way or engage in long, time-consuming debates.</p><h3>#3. Empower your team to remember the big picture</h3><p>The best way to keep your team aware of the big picture is to balance expert user feedback with lots of other data. Not only do you want to <em>show</em> your team that expert users are one input out of many, but you also want your team to feel some ownership over research with non-expert users.</p><p>If you have specialized researchers on your team, encourage them to invite team members to research sessions and roundtable discussions. Amplify their work wherever you can. If you don’t have specialized researchers, have team members run research with non-expert users and report on the findings.</p><p>✅ <strong>Do</strong>: research with lots of other user segments, empower your team to run their own research projects, and amplify research work.</p><p>❌ <strong>Don’t</strong>: simply tell your team to ignore expert users.</p><h3>#4. Build workflows for expert users</h3><p>Even if expert users make up a tiny fraction of your user base, it doesn’t mean that they aren’t important. At Stack Overflow, a very small segment of users do most of the heavy lifting it takes to curate and moderate content on the site. Their work ultimately benefits all users.</p><p>Help expert users with their work by building workflows, features, and shortcuts just for them. Dedicate a portion of your team’s time to the expert user’s experience. When you’re building something new, consider how the expert user will be affected, even if they aren’t the end user. Changes to the general user experience often have downstream impact on expert users that aren’t immediately apparent.</p><p>✅ <strong>Do</strong>: create workflows and features to make their work easier and more pleasant. Offer customizations where appropriate.</p><p>❌ <strong>Don’t</strong>: over-index on pet use cases or hypothetical scenarios. Don’t clutter general user experiences with expert user features.</p><h3>#5. Show gratitude</h3><p>Expert users are human too! They’re volunteering time to your product when they could be doing something else. Show appreciation by thanking them for their time, ideas, and passion. If your team has the capacity, reward expert users with free swag, fun contests, and <a href="https://en.wikipedia.org/wiki/Easter_egg_(media)">easter-egg features</a>.</p><p>✅ <strong>Do</strong>: offer a sincere “thank you” whenever you can.</p><p>❌ <strong>Don’t</strong>: overcompensate by doing everything expert users want.</p><p>Growing a healthy, productive relationship with expert users is a challenging, rewarding pursuit. It’s easy to over-index on their feedback, but it’s just as easy to be overly dismissive. I’ve done both in my time at Stack Overflow, and I’m still making mistakes and trying to find the right balance.</p><p>What’s been your experience working with expert users? What is your expert user community like, and how does your team engage with them?</p><p>Thanks for reading! If you have any feedback or questions, please share in the comments below or email me at donnachoi30@gmail.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3ea409ecfa2" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-build-products-with-expert-users-b3ea409ecfa2">How to build products with expert users</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: improving the question closing experience]]></title>
            <link>https://medium.com/@donnachoi/case-study-improving-the-question-closing-experience-ea430f857f6?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea430f857f6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Fri, 20 Dec 2019 19:39:41 GMT</pubDate>
            <atom:updated>2020-10-08T19:05:09.157Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Case study: improving the question closing experience at Stack Overflow</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w_QZgNc5xVv9tMAu0vYj_Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@aleksdahlberg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Aleks Dahlberg</a> on <a href="https://unsplash.com/@aleksdahlberg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You’re stumped on a coding problem. You’ve tried everything: scoured the internet, pinged your colleagues for help, and troubleshot for hours. Finally, you decide to ask your question on Stack Overflow — surely someone in this community of 50 million programmers can help you, right? So you publish a question and wait hopefully for a response.</p><p>Within minutes, however, your question is closed by community members and marked with a large yellow banner, letting you and others know that there’s something wrong with the question. Closing also prevents your question from being answered by others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-lTdhwsjzksY0yhO" /></figure><p>About 20% of questions posted on Stack Overflow are closed every day. As you might expect, this is an oft-cited negative experience for users. Not only does it prevent them from getting the help they need, but it contributes to the perception that Stack Overflow is exclusive and deters people from participating further in the community.</p><p>So why does question closing exist if it causes distress to users? Why not get rid of it entirely and let people ask what they’d like?</p><p>Closing questions is an important part of content curation. It helps ensure a high standard for content quality on the site. This is critical for attracting and retaining people willing to answer questions. People answering questions need to be able to generally expect that the questions they see are well-written, easy to understand, and non-duplicative content. Therefore, they expect people to abide by specific rules when asking questions on Stack Overflow. Questions that don’t abide by those rules are often closed.</p><p>How can we ensure that people asking questions get the help they need, while also empowering those curating the site to maintain a high bar for content quality? Earlier this year, the Community team at Stack Overflow set out to answer this question. Here’s my take on our approach.</p><h3>Our goals</h3><p>We set out with the following UX goals:</p><ul><li>To make the question closing experience friendlier and more useful for question askers; and</li><li>To make it easier to edit and reopen closed questions.</li></ul><p>We planned to measure progress toward these goals by tracking the question editing rate and mentions of “overmoderation” in monthly site satisfaction metrics.</p><h3>Preliminary research</h3><p>We started out by conducting an audit of the current question closing experience, mapping out workflows and their underlying logic. This was important because the system contained intricacies not fully documented or understood by the team. We needed a detailed view of the system in order to make useful changes without breaking the parts that worked.</p><p>In addition to the audit, we dug into qualitative feedback archives, as well as question closing and reopening stats, to learn about the workflow’s current performance, where it worked, and where it didn’t.</p><p>We found that the question editing and reopening rate was very low, even though this was the recommended course of action for users whose questions were closed. We attributed this to a fragmented workflow with dense, confusing guidance. Question askers had to expend significant effort to understand what they could do about their closed question. It was not clear that reopening their question was a viable option.</p><h3>Solution</h3><p>We came to our design solution through several rounds of iteration and user testing. Below are the core changes we’re making.</p><p><strong>When a question is closed, it’s hidden from the public. </strong>One of the primary reasons that getting a question closed is such a negative experience is because it’s <em>embarrassing</em>. Allowing this to take place in public increases stress for the question asker during an already stressful time.</p><p>Under the new experience, a closed question is hidden from the homepage and other public locations. Not only does this give the question asker time to parse feedback privately, but it also reduces noise for people seeking to answer questions. The homepage and other locations where people look for questions to answer are no longer cluttered by closed questions that can’t be answered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4xXQ6J3mjmzgIxqAYwhqg.png" /></figure><p><strong>Automated guidance is built directly into the workflow.</strong> Right now, there isn’t much readily available help for people who get their questions closed. If they want to find out more about what this status means and what they can do about it, they’ll need to dig through dense pages of documentation and user forums, or rely on the goodwill of a community member to guide them.</p><p>The new experience provides built-in guidance at key touchpoints: on the closed question, by email notification, and during the editing process. Users don’t need to leave their workflow in order to learn about how to address their closed question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*octBYYlscnRgj88spPsfRQ.png" /></figure><p>Automated guidance also reduces opportunities for user-to-user friction. Instead of two users potentially clashing due to frustration or miscommunication, there is clear, neutral guidance offered by the product. This supplements or replaces ad hoc guidance from community members, allowing them to redirect energy to answering questions or performing other curation tasks.</p><p><strong>A new editor with detailed guidance for closed questions</strong>. Asking or editing a question properly on Stack Overflow requires knowledge and skill, but the previous editor offered no guidance and a cluttered, confusing interface. People hoping to edit their closed question would need to do their own research.</p><p>The new question editor offers a simplified interface, detailed guidance about how to edit a closed question properly, and tips for how to write a question that is likely to get answers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qC9OZeB-oI9E0vB_V1HbEw.png" /></figure><p><strong>Sufficiently edited questions are automatically reopened. </strong>The previous experience didn’t offer an explicit path to reopening a question. A small chunk of edited questions are manually reopened, but the rest languish unseen, even after being edited. Even if a question does get reopened, it is often left unanswered because by then, it’s no longer “new.” New questions are ranked at the top of question lists and are most likely to be seen by people looking for questions to answer.</p><p>Under the new experience, questions are automatically reopened once they’ve been sufficiently edited. If the system detects potential abuse, the question is kicked back to the manual reopening process. Reopened questions are also bumped to the top of question lists and are therefore more likely to be answered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qmYXY9MoxnlwqK9U1_WMIQ.png" /></figure><h3>What do users think so far?</h3><p>We tested this solution with two user segments: less experienced users who are likely to ask questions, and more experienced users who are likely to curate or answer questions.</p><p>Overall, we found that both segments saw clear benefits in these changes. This would help question askers get the answers they needed while reducing noise and workload for curators and answerers.</p><p>“It would be helpful to not feel like I have to write so much… guiding [question askers] myself. I believe most people will welcome this.” — Content curator</p><p>“A closed question becoming hidden is a good idea, gives you the opportunity to fix things offsite. It can be a bit embarrassing.”</p><h3>Next steps and reflection</h3><p>The new question closing experience is rolling out incrementally through a combination of A/B tests and phased releases. We’ll be closely monitoring performance and gathering qualitative feedback at key milestones.</p><p>Beyond these improvements, I hope that we can continue to invest in this experience by simplifying rules about posting a question and making our guidance smarter.</p><p>🙏Thanks for reading! If you have your own stories about building product for online communities, I’d love to hear. Please leave a comment or email me at donnachoi30@gmail.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea430f857f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we conduct research on the community team at Stack Overflow]]></title>
            <link>https://uxdesign.cc/how-we-conduct-research-on-the-community-team-at-stack-overflow-78b6ef66f173?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/78b6ef66f173</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Thu, 12 Dec 2019 00:06:03 GMT</pubDate>
            <atom:updated>2019-12-13T01:06:49.518Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1lJ8EUAL-qtGXFch_bR2ZQ.jpeg" /></figure><p>If you work on a product that’s ever benefited from research — whether that’s talking directly to users, analyzing experiment data, or any number of other research methods — you know how indispensable these inputs are for making the right decisions.</p><p>But how do you decide which methods to use and when? How do you know if you’re spending the right amount of time on research? How do you know when it’s time to change your research methods?</p><p>These are questions that the Community team at Stack Overflow has been grappling with, particularly in the last year. While we certainly don’t have all the answers, I’d like to share:</p><ul><li>What our research used to be</li><li>What it is now</li><li>How it continues to evolve</li></ul><h3>The early days</h3><p>If you were an early user of Stack Overflow, you may remember when our research process looked something like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OmtL32Rz6eqdwT2jPHF04Q.png" /></figure><p>Meta feedback involved direct exchanges between users and staff members on Meta, a site where users discussed the site, shared ideas, gave feedback, and talked to staff. These conversations led to the Stack Overflow of today, and we learned a lot while working with this small group of highly motivated users for many years.</p><h3>Our current approach: scrappy and mixed-method</h3><p>As our community has grown, our research needs have become more complex. With 50 million people coming to the site every month — all with unique needs and backgrounds — our team and its research approach have evolved to keep up with this ever-growing complexity. We’ve added folks to the team with specialized research skills, like UX researchers and data scientists, while people like product managers, designers, community managers, marketers, and developers contribute research as well.</p><p>Together, we conduct mixed-methods research that helps us create a holistic picture of how we’re doing. This collective research seeks to answer questions like:</p><ul><li>What do users need?</li><li>What do customers need?</li><li>Are our ideas and decisions on the right track?</li><li>How are our products and features performing?</li></ul><p>This mixed-method approach allows us to hear from a variety of inputs throughout the life cycle of a product or feature, from early conception to post-launch.</p><p>However, our small team can’t always conduct all of the research we’d like — which is where the “scrappy” element of our research approach comes in. Generally, the greater the cost and impact of a project, the more research energy we’ll devote to it. This matrix visualizes how we might decide the amount of research that goes into a project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5X4p-PE-ZiTnpcP2rc37rQ.png" /></figure><p>Today, our research process might look something like this for a high-impact, high-cost project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YNbber6UTqF-qNi_ybZMTw.png" /></figure><p>Think of each method as a puzzle piece, and the outcome as the completed puzzle. I’ll talk more in detail below about our methods and why we use them.</p><h3>Method #1: surveys</h3><p>Surveys are one of our favorite sources of both qualitative and quantitative feedback. We currently use surveys for:</p><ul><li><strong>General site satisfaction</strong>. This is used to gauge trends in satisfaction and helps us identify directional improvements. We use this data to inform our roadmap.</li><li><strong>The beginning of a project. </strong>This help us vet early ideas and point us in the right direction. We use survey data, as well as other inputs, to help us identify requirements and design.</li><li><strong>The end of a project</strong>. Once we ship, we can see how people are feeling about the new feature and identify changes for future iterations.</li></ul><p>⚠️ <strong>Why surveys?</strong> Surveys are a great way to get a high volume of qualitative feedback, which we can use to understand macro trends as well as micro issues for things like usability and copy. We can also target surveys to specific audiences, so that we are gathering data from people who’d be affected by the outcome of a particular project.</p><h3>Method #2: user research</h3><p>Qualitative research helps us understand the <em>why </em>and<em> how </em>of user behavior, allowing us to get<em> </em>deeper insights than we might through other methods. Generally, these are semi-structured discussions that take place by video call or in writing — where we’ll talk in-depth with users about a specific topic, feature, or design. We generally conduct these throughout the beginning and middle phases of projects. We use a few different sub-methods, depending on the project:</p><ul><li><strong>User interviews</strong>. We have conversations with people who may be affected by a given change. Since Stack Overflow is an online community where groups of people interact with each other, our conversations are not limited to the end user. For example, if we are updating the question asking form, not only do we talk to people asking questions, but also those answering and moderating questions.</li><li><strong>Meta feedback</strong>. We monitor Meta for bug reports and small usability/copy issues after shipping changes to the site. Note that this may change based on what the next iteration of Meta looks like, as mentioned in <a href="https://stackoverflow.blog/2019/11/25/introducing-the-loop-a-foundation-in-listening/">the previous chapter</a> of The Loop.</li></ul><p>⚠️ <strong>Why user research</strong>? We get deeper insights than we might through other methods. Like surveys, we can target user research to specific audiences, and will talk to a range of groups affected by a given product change.</p><h3>Method #3: quantitative data</h3><p>While qualitative data helps us understand <em>why</em>, quantitative data helps us understand <em>how many</em>. We use data analysis and A/B tests to provide insight into how our decisions scale, as well as how changes we make contribute to site usage and overall performance goals. Sub-methods include:</p><ul><li><strong>General data analysis</strong>. This is used to understand patterns in site usage across various user segments.</li><li><strong>A/B tests</strong>. We test as much as we can, particularly areas that impact core interactions on the site.</li></ul><p>⚠️ <strong>Why quantitative data? </strong>Statistical analysis allows us to see how (or if) earlier research insights scale and how the changes we make impact top-line performance goals.</p><h3>Method #4: secondary research</h3><p>Today’s Stack Overflow doesn’t exist in a vacuum. When we consider changes to the site, we want to understand the broader contexts of our users, as well as any historical insights that led us to the current state of the site. This helps ensure that we’re not reinventing the wheel or ignoring hard-learned lessons from the past. Sub-methods include:</p><ul><li><strong>Comparative site analysis</strong>. We look at other sites to understand patterns and standards that users are learning offsite. This awareness helps us understand how to make a user’s entry into Stack Overflow as seamless as possible.</li><li><strong>Archive research.</strong> We scour Meta and talk to various staff, particularly community managers and developers, to learn how and why a feature arrived at its current state.</li></ul><p>⚠️ <strong>Why secondary research? </strong>We can learn from broader offsite patterns as well as research from previous iterations on the product.</p><h3>Reflection</h3><p>How we talk to and learn from our users has changed a<em> lot</em> over the years. By broadening our research approach, we’ve lost some of the trust and familiarity of regular, frequent exchanges with a small, passionate, and generous group of people on Meta. At the same time, we’ve brought more rigor and precision into our research approach, which means we have more confidence when making decisions.</p><p>Our research approach is constantly evolving. We’re now expanding our research toolbelt to include a working group (a hand-selected group of folks we’ll gather feedback from regularly). We want to continue not just listening to our users, but improving <em>how </em>we do so.</p><p>How does your organization conduct research? How has your organization’s research changed over time, and what have you learned from these changes?</p><p>This is cross-posted on the <a href="https://stackoverflow.blog/2019/12/11/the-loop-1-how-we-conduct-research-on-the-community-team/">Stack Overflow blog</a> and has been adapted for Medium.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78b6ef66f173" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-we-conduct-research-on-the-community-team-at-stack-overflow-78b6ef66f173">How we conduct research on the community team at Stack Overflow</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Holistic vs. feature design: how to stop shipping only individual features]]></title>
            <link>https://uxdesign.cc/holistic-vs-feature-design-how-to-advocate-for-holistic-design-49f2ffe53273?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/49f2ffe53273</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Sat, 09 Nov 2019 19:08:56 GMT</pubDate>
            <atom:updated>2020-10-08T21:20:08.234Z</atom:updated>
            <content:encoded><![CDATA[<p>You’ve been asked to design a new feature. You’re not sure that this feature will work without broader changes to the product. However, no one has asked you to design a new feature <em>and </em>a sweeping overhaul of the product. In fact, when you’ve pitched broader changes alongside a feature design in the past, your stakeholders expressed skepticism and dismissed your proposal as <a href="https://en.wikipedia.org/wiki/Scope_creep">scope creep</a>.</p><p>Still, you can’t help but feel that these broader changes are sometimes necessary — even if you’ve been having trouble convincing your stakeholders to see things your way.</p><p>At Stack Overflow, I’ve often grappled with the question of <em>when</em> and <em>how </em>designers should advocate for more holistic design changes (and therefore, larger scope). Below are tips to help you decide whether to advocate for holistic designs changes, and if so — how to do so effectively.</p><h3><strong>#1. Identify the holistic changes you want to make and why</strong></h3><p>Be as specific as possible, and tie these changes back to the feature’s success metrics.</p><p>Say you’ve been asked to redesign a bookmark feature. You’d like to redesign the article page that the bookmark lives on, as well as how users are notified about new bookmarks on their articles. At this point, can you hone in on very specific problems and changes? Can you tie those back to feature or business success metrics?</p><p>—</p><p><strong>✅ Do: </strong>I want to redesign the <em>left column</em> on the article page because there are currently 8 actions to choose from, and this prevents users from engaging with the most important actions (one of which is bookmarking).</p><p><strong>❌ Don’t: </strong>I want to redesign the article page because it’s bad UX.</p><p>—</p><p><strong>✅ Do: </strong>I want to redesign the author byline because it doesn’t adhere to our design patterns and therefore creates unnecessary cognitive overhead for the user.</p><p><strong>❌ Don’t: </strong>I want to redesign the author byline because the design is outdated.</p><p>—</p><p><strong>✅ Do: </strong>I want to add a notification feature so that users can be notified when someone has bookmarked their post. User research tells us that users are encouraged to post more articles if they see that others are bookmarking their posts.</p><p><strong>❌ Don’t: </strong>I want to add a notification feature because we don’t have one right now and we need one for bookmarks.</p><h3><strong>#2. Assess constraints</strong></h3><p>How much time do you have? Is there a hard deadline and limited resources? If the answers are “yes” and “yes”, then this is probably not a good time to advocate for sweeping overhauls.</p><h3><strong>#3. Prioritize the changes that are most likely to be high impact, low cost</strong></h3><p>This is especially important if your org has <a href="https://www.nngroup.com/articles/ux-maturity-stages-1-4/">low design maturity</a> or is strapped for resources. Tools like this impact-effort matrix may be helpful while prioritizing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*glGw9m6mXG5LqxBrXf6g4g.png" /></figure><p>Cut the things that can’t be explicitly tied back to feature or business goals. Then cut the things that are likely to be expensive to build if resourcing is a significant constraint. <em>Then</em> cut the things where the benefit is a small experience gain (vs. fixing a broken UX).</p><p>Here, I’ve taken the changes outlined above and assigned a priority to each of them.</p><p>—</p><p><strong>🖌 Proposed change</strong>: I want to redesign the <em>left column</em> on the article page because there are currently 8 actions to choose from, and this prevents users from engaging with the most important actions (one of which is bookmarking).</p><p>⚠️ <strong>Priority</strong>: High</p><p><strong>🤔 Priority reason</strong>: The cost of this change appears to be low since this is a redesign of a section of a page and doesn’t seem to involve new feature work. At the same time, it sounds like the impact on feature performance could be high because this change affects a direct, primary path to engagement with the bookmark feature.</p><p>—</p><p><strong>🖌 Proposed change</strong>: I want to redesign the author byline because it doesn’t adhere to our design patterns and therefore creates unnecessary cognitive overhead for the user.</p><p>⚠️ <strong>Priority</strong>: Low</p><p><strong>🤔 Priority reason</strong>: This appears to be low cost since it’s a redesign of an existing section of a page, but it sounds like it won’t have an impact on the feature or business performance. Since this is low cost work with usability gains, however, it may still be worth advocating for or separating into a small, separate project. A change like this is more likely to be accepted if your org already has high design maturity and values things like design patterns and reducing cognitive load.</p><p>—</p><p><strong>🖌 Proposed change</strong>: I want to add a notification feature so that users can be notified when someone has bookmarked their post. User research tells us that users are encouraged to post more articles if they see that others are bookmarking their posts.</p><p>⚠️ <strong>Priority</strong>: Medium</p><p><strong>🤔 Priority reason</strong>: This sounds like a costly change (new feature work) but with a potential for high impact because it may increase the volume of posts per user (an overall business goal!)</p><p>In cases like this, try to equip yourself with as much data as you can in order to best understand the actual cost and impact. Can you ask developers to provide a <a href="https://blog.trello.com/t-shirt-sizes-project-estimation-technique">t-shirt estimate</a> for build? What qualitative or quantitative data do you have to help understand the potential impact?</p><p>Prioritization is <em>hard</em>, especially when you are convinced in your heart and soul that your redesign is simply better for users, costs and impact be damned.</p><p>But when thinking about problems like this, try to put yourself in your Product Manager or stakeholder’s shoes. If they are anything like the ones I work with, they don’t hate design. They are just making constant, hard decisions about priorities and resourcing. You can help them — and in the process, take more control of your design’s destiny — by preemptively thinking about impact, cost, and priorities.</p><p>Thanks for reading! If you have any feedback or questions, please share in the comments below or email me at <a href="/service/mailto:donnachoi30@gmail.com">donnachoi30@gmail.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49f2ffe53273" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/holistic-vs-feature-design-how-to-advocate-for-holistic-design-49f2ffe53273">Holistic vs. feature design: how to stop shipping only individual features</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips for Leading a Design Project]]></title>
            <link>https://uxplanet.org/tips-for-leading-a-design-project-a638f5a71884?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a638f5a71884</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Wed, 17 Jul 2019 17:35:26 GMT</pubDate>
            <atom:updated>2019-12-19T22:48:00.655Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n3k1vnINuOsUyfpeFe5-uQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jaysung?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jehyun Sung</a> on <a href="https://unsplash.com/s/photos/leadership?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Tips for leading a design project</strong></h3><p><strong>If you’re a product designer, you probably lead design projects every day, even if “lead” isn’t in your job title. </strong>Whether that’s by gathering user insights to identify the next thing your team could work on, designing solutions to user pain points, or running design reviews, the opportunities to lead your team and influence the direction of your product are present throughout the design cycle. In her book, <a href="https://www.amazon.com/Making-Manager-What-Everyone-Looks/dp/0735219567">The Making of a Manager</a>, Julie Zhuo writes:</p><blockquote>“Over time I’ve come to learn that leadership is a quality rather than a job. While the role of a manager can be given to someone (or taken away), leadership is not something that can be bestowed. It must be earned. People must want to follow you.”</blockquote><p>With this in mind, myself and my colleague, <a href="https://medium.com/@tedgoas">Ted Goas</a>, have compiled tips and insights for leading design projects based on our experiences at Stack Overflow.</p><h3>Starting your project</h3><p>Start a project by gathering as much information as possible and talking with your product lead. They may not know all the answers (or have thought deeply about them), so it’s up to you to help lead them to useful answers. The questions below can help guide your conversation. If your team doesn’t have a product lead, consider talking to the people on your team responsible for project management and/or your product’s goals.</p><ul><li><strong>“What’s the goal?</strong>” This is the project’s <strong>north star</strong>. As requirements, edge cases, and opinions pile up over time, the goal helps you focus.</li><li><strong>“What problems do you want to solve, and who do they affect?”</strong> This helps you understand<strong> why</strong> we want to make a change, and <strong>who</strong> this will affect.</li><li><strong>“How do you envision this working and looking like?”</strong> This helps you understand the product lead’s vision and potential requirements. Remember that <strong>your goal is to understand their vision (and maybe poke holes in it)</strong>, not necessarily to execute it as described.</li><li><strong>“What are potential concerns, risks, or sticky areas of the project?”</strong> This helps you prioritize design problems and identify additional discovery you might need. This is <strong>an area that your product lead may not have thought deeply about</strong>, so coming prepared with discussion points can help drive the conversation.</li><li><strong>“What is the project timeline? Where do you expect it to be in a week, a month?” </strong>This helps you understand <strong>how much time you have, what’s already in motion, and how to plan for your project</strong>. Also an opportunity to push back on a timeline, if needed.</li><li><strong>“What do we know so far?”</strong> This deepens your knowledge of the project and saves you from doing <strong>repeat discovery.</strong></li><li><strong>“Who are stakeholders and potential collaborators in this project?”</strong> This helps you understand <strong>who you should talk to next</strong>.</li></ul><h3>Planning your approach</h3><p><strong>Decide what discovery you’ll need to do, and bring in the appropriate people. </strong>Not all projects require extensive discovery. Below are common discovery methods we use at Stack Overflow, when they’re most useful, and how long they generally take us.</p><ul><li><strong>UX teardowns</strong>: Use when there are <strong>established or related patterns you can learn from</strong> (hint: almost always), and those patterns are easily accessible (generally harder for paid products). 🕓 <em>1–2 days</em></li><li><strong>Stakeholder interviews</strong>: Use when you need to understand <strong>what we already know and/or have tried</strong>. Stakeholders can include people from project teams (eg. Community) and/or functional teams (eg. Architecture). 🕓 <em>1 week</em></li><li><strong>User research:</strong> Use when you need feedback about <strong>UX, UI, and copy</strong>, and the project is important enough to warrant an extra week or more. 🕓<em> 1 week (per round of research)</em></li><li><strong>Expert interviews</strong>: Use when your project has lots of <strong>history, controversy, and/or complexity</strong>. Generally, this means talking to Community (for public Q&amp;A) or Customer Support (for paid products). Make sure to prepare questions, as you would for a user interview. 🕓 <em>1 week</em></li><li><strong>Data analysis</strong>: Use when you have questions about “<strong>how many” and “how often.</strong>” 🕓 <em>2 weeks (small requests will take less time, but budget at least 2 weeks for most requests, and more for bigger ones)</em></li><li><strong>Journey mapping</strong>: Use when you want a <strong>big picture understanding</strong> of the user’s experience. This may include off-site things like user emotions or external touchpoints. 🕓<em>1 month (this includes the lead-up to journey mapping, which may include user research, data, etc.)</em></li></ul><h3>Communicating with your team</h3><p>The product and engineering team at Stack Overflow is fully remote and distributed across the world, so we don’t always have opportunities to meet. That’s why we take special care to make sure that our meetings are a good use of everyone’s time.</p><p>For designers, meetings are an opportunity to share information, discuss complex issues, and get alignment from a group of people. Schedule regular design reviews and check-ins with your product team. Regular design reviews give people space to share ideas and make decisions in real-time. More meetings up-front can also mean less surprises later. Use this valuable time to your advantage by setting a clear agenda, moderating the meeting, delegating work, and following up with next steps.</p><p>💡<strong>Tips for running effective meetings</strong></p><ol><li><strong>Invite carefully.</strong> Invite only who needs or wants to be there. Don’t keep someone if they’re not needed the whole time. A meeting where folks are not actively participating is not fun.</li><li><strong>Set an agenda and goals. </strong>Start each meeting by recapping the agenda and what you hope to accomplish by the end.</li><li><strong>Take notes during the meeting.</strong> Doing this means you have the most complete knowledge of the meeting and are best equipped to guide its outcomes.</li><li><strong>If the meeting veers down a rabbit hole, firmly guide it back</strong>. Saying, “Let’s revisit this later” or “let’s move on” is usually all you need.</li><li><strong>Set aside at least 10 minutes at the end to talk about next steps and roles.</strong> If there were open questions during the meeting (remember that rabbit hole from earlier?), make sure someone is assigned to resolve it.</li><li><strong>Follow-up in writing after the meeting with next steps, roles, and timeline. </strong>People leave meetings and forget things or remember them differently. This protects your project from that, plus it never hurts to reinforce that people are on the same page.</li></ol><h3>Guiding design implementation</h3><p>At Stack Overflow, product designers are ultimately responsible for the design that ends up in the browser. For some designers that means handing off a detailed design spec, for others it means pushing code directly. Regardless of your direct involvement in code, take an active role in working alongside engineering to implement designs as envisioned.</p><p>💡<strong>Tips for working with engineering</strong></p><ol><li><strong>Lead the communication. </strong>Pull engineers in early, talk about your design decisions, ask them for feedback. Speak their language and understand their concerns. A good design-dev relationship starts here.</li><li><strong>Maintain documentation.</strong> Update functional specs with decisions and open questions after meetings and notable chat conversations. Update research summaries as interviews are conducted. Incomplete or outdated documentation can lead people to building the wrong things. Keep your designs and specs up-to-date so it continues to be a source of truth for your team.</li><li><strong>Don’t forget the details</strong>. Remember things like <a href="https://stackoverflow.design/product/components/empty-states">variable states</a>, <a href="https://stackoverflow.design/product/base/transitions">interactions</a>, <a href="https://stackoverflow.design/product/components/inputs#validation-examples">validation styles</a>, and <a href="https://stackoverflow.design/content/principles">microcopy</a>. The more detail the better.</li><li><strong>Understand HTML/CSS/JS, </strong><a href="http://blog.froont.com/9-basic-principles-of-responsive-web-design/"><strong>responsive design</strong></a><strong>, and </strong><a href="https://medium.com/@matuzo/writing-css-with-accessibility-in-mind-8514a0007939"><strong>accessibility</strong></a><strong>.</strong> Product designers don’t need to be expert coders, but some basic knowledge goes a long way in shipping a high quality product.</li><li><a href="https://uxdesign.cc/the-importance-of-design-qa-in-digital-product-design-c3f3d128270"><strong>Be proactive in QAing designs</strong></a><strong>.</strong> Help ensure a test plan exists and ask for access to development sites so you can proactively test features. If you find bugs and can’t fix them yourself (totally normal!), report the issues to your developer team.</li></ol><h3>Increasing your impact</h3><p>You can increase your impact by <strong>ensuring that your work ties to product strategy and goals, following up on outcomes of your work, and listening to and sharing the needs of stakeholders and users</strong>. The tactics below are potential ways to do this, but this isn’t about a specific tactic or conversation. <strong>It’s about making a habit of connecting your work to the big picture, seeking out and sharing info throughout your week, and using this information to identify themes over time.</strong></p><ul><li><strong>Set up a recurring 1:1 with your PM. </strong>Dedicated time with your product lead means you’ll<strong> better understand the team’s direction</strong>. What ideas are they batting around, what questions are they struggling with?</li><li><strong>Join research sessions, or conduct exploratory research.</strong> This helps you <strong>understand the general tone and needs of users</strong>. Research sessions are packed with data, and often only a portion of that data is immediately usable. Capture the unused data in your brain!</li><li><strong>Check your metrics regularly </strong>(and if you don’t know already, find out where they are and how to interpret them!)<strong>. </strong>Helps you <strong>check your assumptions</strong>, <strong>follow-up on projects </strong>you shipped, and <strong>keep track of the big picture</strong>.</li><li><strong>Keep up with the conversation on-the-ground</strong> (at Stack Overflow, that includes the Community Managers and Support team). Helps you <strong>follow-up on projects</strong> you shipped, and <strong>understand the general tone and needs of users.</strong></li></ul><h3>Conclusion</h3><p>Thanks for reading! To learn more about Stack Overflow’s design team, <a href="https://medium.com/stack-overflow-design">check out our blog</a>. If you’d like to share your own insights about leading design on your team, please leave a comment or email me at <a href="/service/mailto:donnachoi30@gmail.com">donnachoi30@gmail.com</a>.</p><p><em>Thanks to </em><a href="https://twitter.com/TedGoas"><em>Ted Goas</em></a><em> for contributions to this post.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a638f5a71884" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/tips-for-leading-a-design-project-a638f5a71884">Tips for Leading a Design Project</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Updating Navigation for Stack Overflow, Enterprise, and Stack Exchange Sites — Stack Overflow Blog]]></title>
            <link>https://medium.com/@donnachoi/updating-navigation-for-stack-overflow-enterprise-and-stack-exchange-sites-stack-overflow-blog-62cf0a2bff6a?source=rss-33be53ecea7------2</link>
            <guid isPermaLink="false">https://medium.com/p/62cf0a2bff6a</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Donna Choi]]></dc:creator>
            <pubDate>Thu, 08 Feb 2018 07:00:32 GMT</pubDate>
            <atom:updated>2020-09-04T23:57:01.619Z</atom:updated>
            <content:encoded><![CDATA[<h3>Navigation for Stack Overflow and the Stack Exchange network</h3><p><em>This blog post was </em><a href="https://stackoverflow.blog/2018/02/08/information-architecture-navigating-stack-overflow-enterprise-stack-exchange-sites/"><em>originally published</em></a><em> to the Stack Overflow blog. It refers to “Channels”, a product which is now called “Teams.” This post is part of a series on how we’re making Channels, the thinking behind the product, and insight into the process. Read “</em><a href="https://stackoverflow.blog/2017/12/04/designing-channels/"><em>How We’re Designing Channels</em></a><em>” and “</em><a href="https://stackoverflow.blog/2017/11/09/why-channels/"><em>Why Channels</em></a><em>” for more background info.</em></p><p>In his post, <a href="https://stackoverflow.blog/2017/12/04/designing-channels/">How We’re Designing Channels</a>, Kurtis wrote that this project required a change to Stack Overflow’s information architecture. We created several prototype navigations, narrowed to two, and tested with a group of users. This brought us to the following design direction, with content navigation on the left side:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o2t_jX7BXgw_c45O.png" /></figure><p>We’re confident that this design will serve Channels users, but what about the greater Stack Overflow, Stack Exchange communities, and Enterprise? Our design explorations were guided by the following questions:</p><ul><li>How will the new <a href="https://en.wikipedia.org/wiki/Information_architecture">information architecture</a> support <strong>existing Stack Overflow users</strong>? How will it impact important workflows like reviewing posts or answering questions?</li><li>How will this scale to <strong>Stack Overflow Enterprise</strong> and the <strong>Stack Exchange network sites</strong>? How can people transition seamlessly between Stack Overflow and other sites without having to learn new patterns?</li><li>What about people using <strong>smaller screen sizes</strong>? Adding a vertical left navigation increases the page width, and how will we support people across a range of screen sizes and devices?</li><li>Is the new information architecture <strong>inclusive and accessible</strong>? How will this impact people using screen readers or with other accessibility needs? How can we leverage this moment of change to improve the site’s accessibility?</li><li>How will the new information architecture scale as the site <strong>grows and changes over time</strong>?</li></ul><p>In this post, I’ll talk about our approach to answering these questions. First, though, I want to step back and explain <em>why</em> it’s important for us to be thinking about these needs simultaneously.</p><h3>Background</h3><p>You may remember that we <a href="https://stackoverflow.blog/2017/02/14/why-stack-overflow-redesigned-the-top-navigation/">updated</a> the navigation design last year. Our approach was to focus on the already complex needs of Stack Overflow, and solve Enterprise and network site solutions soon after.</p><p>Through that project, we learned that — despite many similar or overlapping use cases — there were major differences that were not easy to resolve. As a result, it took us longer than expected to ship navigation to network sites, and we still haven’t updated Enterprise sites.</p><p>This means there’s been extended or unresolved fragmentation between Stack Overflow and our other sites. This is problematic because there’s a lot of overlap between people using Stack Overflow, Enterprise, and network sites. For example, about 70% of users joining network sites already have a Stack Overflow account.</p><p>More generally, fragmentation means that shipping basic improvements to Enterprise and network sites becomes increasingly costly as differences accumulate over time.</p><p>This time, we wanted to make sure that we were considering Enterprise and network site use cases early, as well as ensuring that basic improvements like accessibility and responsiveness can benefit our 150+ communities and Enterprise clients as quickly as possible.</p><h3>How We’re Addressing These Needs</h3><p>We started by broadly considering use cases across our product offerings: Stack Overflow, network sites, Enterprise, and soon — Channels. This approach helps us avoid fragmentation and allows improvements to flow quickly to all of our users. I’ll explore these use cases in further detail below.</p><p>First, here’s a recap of the basic design solution, with content navigation on the left side:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DxkFJR693emPTDUx.png" /></figure><p>Next, I’ll layer in the principles and use cases that have guided our designs so far.</p><h3>Principle #1: Flexibility</h3><p>The new information architecture had to be flexible enough to support a broad range of use cases and screen sizes, including:</p><ul><li>User has joined Stack Overflow only</li><li>User has joined Stack Overflow and a private channel</li><li>User has joined Server Fault only (or a different network site)</li><li>User is viewing on a tablet or mobile</li></ul><p>Let’s see what the navigation looks like for each of these use cases.</p><p>User has joined Stack Overflow only:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6eVlfFkG-Xx60xTl.png" /></figure><p>User has joined Stack Overflow and a private channel:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vN4JX2buXcy5sbAT.png" /></figure><p>User has joined Server Fault only (or a different network site) :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T2RmlXHQVluUe_j0.png" /></figure><p>User is viewing on a tablet or mobile:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/0*_QzXr498saPZvobj.png" /></figure><h3>Principle #2: Scalability</h3><p>The new information architecture also needed to scale reasonably over time. People should be able to expect a coherent experience as the site grows and changes. Here are some hypothetical scenarios that we can use to approximate the use cases that the information architecture needs to consider:</p><ul><li>A new product offering that is a separate entity from Stack Overflow</li><li>A new feature on Stack Overflow</li></ul><p>Next, let’s see what the navigation looks like for these hypothetical scenarios.</p><p>A new product offering that is a separate entity from Stack Overflow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K0WiWuow2xKeWn27.png" /></figure><p>A new feature on Stack Overflow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6e-9O2e-b08lnPVI.png" /></figure><h3>Principle #3: Accessibility</h3><p>We know that Stack Overflow and our other sites could better support people with differing abilities. That’s why the new information architecture also needed to support our effort to make Stack Overflow accessible to all.</p><p>We are learning from the <a href="http://www.microsoft.com/design/inclusive">Inclusive Design</a> approach, and also piloting a collaboration with the <a href="https://www.washington.edu/accesscomputing/">University of Washington AccessComputing initiative</a> to identify improvements that bring our sites closer to conformance with the <a href="https://www.w3.org/TR/WCAG20/">W3C Web Content Accessibility Guidelines 2.0 Level AA</a>. We are also interested in hearing additional recommendations from you, if you encounter barriers that WCAG AA doesn’t address.</p><p>While all of these changes may not be ready on day one, we are taking this opportunity to improve access for all of our users.</p><h3>What We’ve Learned So Far</h3><p>In December, we launched Channels Alpha and kicked off research with Enterprise and high-rep Stack Overflow users.</p><p>We asked questions about their day-to-day workflows on Stack Overflow, showed them mockups of the new information architecture, and discussed potential disruptions to their workflows. Overall, we learned that <strong>this change caused minimal impact to their workflows</strong>. Any concerns about the extra screen width this would introduce were alleviated with knowing that the site will become responsive.</p><p>We’ll also be testing with network site users in the upcoming months.</p><h3>Next Steps</h3><p>We’ll be rolling out these changes in the near future. In the meantime, please look for future posts sharing our design, research, and product process for Channels. If you have any questions for the team or me, feel free to drop them in the comments below. Note that these designs are <em>not</em> final, and we’ll continue to iterate as we receive feedback. Let us know what you think.</p><p><em>Originally published at </em><a href="https://stackoverflow.blog/2018/02/08/information-architecture-navigating-stack-overflow-enterprise-stack-exchange-sites/"><em>https://stackoverflow.blog</em></a><em> on February 8, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62cf0a2bff6a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>