<?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 Alexandra Prokhorova on Medium]]></title>
        <description><![CDATA[Stories by Alexandra Prokhorova on Medium]]></description>
        <link>https://medium.com/@sashaprok?source=rss-29c0b60055a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nFtnx0XinHkTqzcCx0MKBQ.png</url>
            <title>Stories by Alexandra Prokhorova on Medium</title>
            <link>https://medium.com/@sashaprok?source=rss-29c0b60055a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:20:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sashaprok/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[Product Design Team Rituals]]></title>
            <link>https://medium.com/algolia-design/product-design-team-rituals-f5b9606e4c9e?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5b9606e4c9e</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design-teams]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Tue, 28 May 2019 13:29:11 GMT</pubDate>
            <atom:updated>2019-05-28T13:29:11.206Z</atom:updated>
            <content:encoded><![CDATA[<h4>What we do to stay connected, empowered and learning</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kvwGrM_62LBXWLHxH_QwGw.png" /></figure><p>At Algolia, each designer works on a product squad that is composed of a product manager, product designer and developers. This means that as a team, we don’t work on projects together day-to-day. In order to keep a sense of unified team, to share knowledge and to support each other in our work, we created certain team rituals. These rituals are an embodiment of our <a href="https://medium.com/algolia-design/algolia-product-design-team-values-d1f885b7a70c">team values</a>, they keep us connected to each other and to the greater Algolia organization.</p><h4>Team Meeting</h4><p>All product designers meet on a weekly basis to discuss team matters. We begin each meeting by going through our <a href="http://joelcalifa.com/blog/trust-and-product-design/">Goalfest</a> document (borrowed from <a href="https://medium.com/u/dd7c5c87b0bc">Joel Califa</a>). In these discussions, we focus less on what we accomplished and more on the lessons learned. Often, we will share best practices about prioritization, project management, and communication. On occasion, we also use team meetings to work/ align team processes, such as planning new member on-boarding, establishing team values, discussing the hiring process, and so on. Most of all, this is a time for us to connect and feel like we are a team.</p><h4>Design Critique</h4><p>Weekly, we gather to show one another our ongoing projects. The goal is to ask for feedback and have an open conversation in safe place. I usually leave this meetings feeling inspired, excited, and humbled by the feedback the team provides. You can read more about how we run them <a href="https://medium.com/algolia-design/design-critiques-and-guidelines-for-sharing-design-work-776313411f4">here</a>.</p><h4>1:1s</h4><p>These are my favorite meetings of the week. As a manager, I meet with my team members once per week. To me, 1:1s are about relationship building and providing time for my team members to talk about what is important to them. Often we discuss career growth, challenges and blockers on specific projects, tricky situations, prioritization and so on. Most of all, this is a time for me to listen to my team and be a thought partner to them. This is also a great time to give and ask for feedback.</p><h4>Design Brainshare 🧠</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zF0VGkzXe90G0uSCHS81VQ.jpeg" /></figure><p>Each team member has his/her superpowers, which is why we recently kicked off this skill sharing lunch series. We meet during lunch time every other week. We either train others on a skill (e.g. how to present your design work, how to run a design sprint). Sometimes, we do a whiteboard design exercise instead to keep our UX skills sharp. In the past, we’ve also invited speakers from other companies to talk to us about things like design systems. The goal here is to spend time together informally, learn something, and have fun.</p><h4>UX Office Hours 🤓</h4><p>Weekly, we host UX office hours to provide colleagues across the organization design advice. These meetings keep us connected to folks we don’t always work with day-to-day. For example, account managers and sales folks often come to ask us how to pitch Algolia to clients (what UX conversations to have). Sometimes, developers come showing us a prototype they’ve built. This meeting has grown in popularity over time and is starting to become an institution.</p><h4>Introduction to Design Thinking</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uRIRrOGFsA7EmGnX11zd1A.jpeg" /></figure><p>Once a month, we run a 3-hour workshop for 8 of our Algolia colleagues. We run through a design exercise with the participants that showcases the end-to-end design thinking process. This is a hands-on way to show what design thinking is all about, to show its value and impart some valuable skills to our colleagues. I’ve noticed that after these sessions, participants feel inspired and excited to put their new skills to practice.</p><p><em>What rituals does your team have? What have you found most valuable in keeping you inspired and connected? Share in comments below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5b9606e4c9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/algolia-design/product-design-team-rituals-f5b9606e4c9e">Product Design Team Rituals</a> was originally published in <a href="https://medium.com/algolia-design">Algolia Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Algolia Product Design Team Values]]></title>
            <link>https://medium.com/algolia-design/algolia-product-design-team-values-d1f885b7a70c?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1f885b7a70c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Tue, 21 May 2019 07:50:09 GMT</pubDate>
            <atom:updated>2019-05-23T09:30:05.908Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*53knmPoqJXqGhVw6T5sHYg.png" /></figure><p>Algolia as a company already has a strong set of <a href="https://www.algolia.com/about/">core values</a>. They align the entire company on how we want to work and grow together. That said, we felt the product design team could create a set of our own values to help us further shape our behaviours and attitudes on the team. As our team scales at Aloglia (<a href="https://www.algolia.com/careers/?job=product-designer">we’re hiring!</a>), we want to ensure that we’re all on the same page when it comes to team values, process and mission. In Q4 of last year, the team came together and created a set of team values, which we will help us unify and be our guiding light in the sometimes dark space of rocket ship growth.</p><h3>How We Came Up With Them</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mu0j-7Krs8sFkGdk6bD3ww.png" /></figure><p>We came together as a team to work on this project as we often do. Each team member filled out a survey specifying what they thought we do well as a team, and what we could do better and strive for. Then, we printed out all of the responses and brought them to our team meeting. In the meeting, we grouped all of the responses into themes (in design speak, we created an affinity diagram). Then, we voted for our top values: a mix of those we do well already and those we would like to do better. This process made us reflect on the team we are and the team we wanted to become as we faced rapid growth.</p><h3>The Values</h3><h4>Aim Higher.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWgZUVM4w5oxfGQhG549EQ.png" /></figure><p>We don’t settle for mediocre design, experiences and practices. We aim high, and hold each other accountable by providing caring and candid feedback. In turn, we accept feedback with an open heart as a gift meant to help us grow and improve. Through failure, we learn, adapt and move forward. When thinking about improving experiences, we keep the big picture in mind. We don’t just check the boxes, we do what’s necessary.</p><h4>Dig Deeper.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u6sHZc6oUiNkK-KEm_4CNg.png" /></figure><p>Our favourite question is “Why?” We are curious, we listen and are ready to learn. We never settle for the first answer, and want to understand what the second and third answers are. We acknowledge that, sometimes, people voice problems through solutions and it’s up to us to uncover what their true needs are. Our design decisions are the result of exploration, and deliberate and intentional decision-making.</p><h4>Bias Toward Action.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xIOlFTq4KNP9HrDkCyEPGw.png" /></figure><p>Perfect is the enemy of the good. We look at the facts, recognise that we will never have all the information and make the best decisions to keep us moving forward. Inaction is not an option. When we feel stuck, we know it’s time to do something, like ask for help.</p><h4>Show, Don’t Tell.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7aeFmsBDmPrcU4W_ZHDn8w.png" /></figure><p>We are visual creatures and recognise that showing is more powerful than just describing. We make abstract things concrete and create a common understanding to achieve alignment in our team. We love to show our work and we do it often, regularly and early. We know that walking the walk is more important than talking the talk, so when it comes to our successes, we will be measured by outcomes rather than ideas.</p><h4>Welcome Others.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KKuqWk6Shvys-U0DCV37oQ.png" /></figure><p>Welcoming means being open to others’ opinions and thinking about other people. When designing, we remember that others experience the world differently from us and ask: “How can Algolia be accessible to them?”. We listen to our users and make sure that our work is infused with their voices. Additionally, we actively include our partners from across the organisation in the design process, because we know we are facilitators and stewards of the design process, but not dictators of solutions.</p><h4>One for All and All for One.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UTOmvaJpYT8DMp6ys4xXnw.png" /></figure><p>We are stronger together than when we act alone. Each of us is empowered to contribute to how the team works. We expect high standards and hold each other accountable. We share credit and celebrate wins. Being a team player to us means providing each other with caring and candid feedback. We know we are only as good as the people we surround ourselves with, so we aim to raise each other up.</p><h4>Living the Values</h4><p>We want to live and breathe our values, which is why we are getting creative about how we keep them top of mind on our team.</p><p>The values review is a standard part of our on-boarding process. We use them to set expectations and to drive behaviours on the team. You’ll often hear us say “Show, don’t tell” in our design reviews and workshops.</p><p><a href="https://medium.com/u/c4dcde3a6180">Clément Aupiais</a> got creative and made a values playlist composed of good and [some] bad 80’s hits:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Fplaylist%2F1ilQWy4o933RFjFlVv9Crm&amp;url=https%3A%2F%2Fopen.spotify.com%2Fuser%2Fgamebirby%2Fplaylist%2F1ilQWy4o933RFjFlVv9Crm&amp;image=https%3A%2F%2Fpl.scdn.co%2Fimages%2Fpl%2Fdefault%2F7ec4209d555987e0f10999ba3534aac8b6cee7af&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=spotify" width="300" height="380" frameborder="0" scrolling="no"><a href="https://medium.com/media/25a6ad3b14019e5811eb0c0431557312/href">https://medium.com/media/25a6ad3b14019e5811eb0c0431557312/href</a></iframe><p>How does your team live and breathe values? Tell us in comments below.</p><h4>Do these values speak to you? Do you think you embody them? <a href="https://www.algolia.com/careers/?job=product-designer">Join us</a>!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1f885b7a70c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/algolia-design/algolia-product-design-team-values-d1f885b7a70c">Algolia Product Design Team Values</a> was originally published in <a href="https://medium.com/algolia-design">Algolia Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Learned About Designing Tools for Developers]]></title>
            <link>https://medium.com/algolia-design/what-i-learned-about-designing-tools-for-developers-1970ba0fb3b5?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/1970ba0fb3b5</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Tue, 14 May 2019 08:15:51 GMT</pubDate>
            <atom:updated>2019-05-14T08:15:51.074Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_SnS4SKdCQRnxtVdOlbmWA.png" /></figure><p>Before I joined Algolia, I designed products that supported people in highly emotional contexts. For example, one product monitored contractions in pregnant women, and the other one was a pet GPS tracker. When I spoke to pregnant women or pet parents, the conversations were highly personal and full of emotional anecdotes (e.g. “The first time Sparky ran away…”, “I had preterm labor last time, so now I am always anxious”). Joining Algolia, I knew the product design work would be intellectually stimulating, engaging and complex. Yet, I was nervous about designing for a product that wouldn’t have such an emotional involvement in people’s lives. I wondered: would I be just as engaged? Almost two years in, I’d like to reflect on what it’s been like to design for developers, to think about DX (developer experience), and the many surprising ways I’ve found my work at Algolia rewarding and exciting.</p><h4>Developers are tough to crack, but when you do 🤩</h4><p>One of the things I learned quickly was that developers are extremely persistent. They dislike being stuck on a problem and most will go to extreme lengths to fix an issue. Also, because developer tools are generally neglected by design, I have found that most developers put up with less than ideal user experiences and consider it rather normal. This means that it’s very hard to get them to complain about anything! In user interviews, I’ve had to dig a lot to get user feedback about our product, but when I finally did get a nugget, it felt like true victory.</p><p>A technique that has worked well for me is to ask developers to actually solve a problem they’re working on using our tool or a tool of their choice. By seeing how they use it, it has allowed me to ask questions directly.</p><h4>Developers make many decisions beyond the technical</h4><p>As the people closest to the product building, developers make many decisions that ultimately affect the overall experience even if they have a whole team of designers and PMs behind them. The truth is, many developers are building the full search experience for their company. This means that building a product that helps developers make design and UX decisions is crucial. For example, when we provide filtering widgets that devs will implement, we need to ensure that they are built to the best UX standards.</p><blockquote>Our designers’ work goes well beyond designing the API Dashboard. We also design best practices for end-user search experience (widgets for front-end implementation), tools that provide a feedback loop about how well search is performing with users (analytics), and much, much more.</blockquote><h4>Developers love interfaces</h4><p>I work with many developers at Algolia, and early on, I started hearing “developers just want to use code.” In my research, I heard quite the opposite. Sure, there were some users who loved code and only code, but the vast majority of people I spoke to preferred interfaces. One of my favorite quotes was:</p><blockquote>“I am lazy, I am constantly trying to work myself out of a job, so clicking a few buttons is so much easier than going into code.”</blockquote><p>A well-designed API dashboard is a developer’s best friend as it saves them time and usually gives them a holistic overview of their API settings and any ongoing issues.</p><h4>Developers are designers’ best partners</h4><p>Developers I’ve spoken to usually light up when we start talking about dev products they like. In that sense, they are an incredible partner in product building. They may not know all the UX and UI best practices, but they are creative problem solvers. Some of our best design ideas have come from them. This is why I highly recommend including a developer user in design sprints and workshops (in addition to the devs on your squad). They will likely get a lot of satisfaction out of it, and your team will get great ideas.</p><h4>Investing in DX is crucial to keeping your user base</h4><p>Developers like to try new tools and see how they work. This is the reason Algolia has a free account option. We knew early on that the tinkerers of the dev world would like to try our product, and if they liked it, they would advocate for it internally. This is important, because they may dump your product as quickly as they adopt it if a better and easier-to-use alternative comes along. Which brings me to my next point.</p><h4>Documentation is a product and a differentiator</h4><p>Working on our <a href="https://blog.algolia.com/redesigning-our-docs-part-3-the-ux-ui-phase/">documentation re-design project</a>, I learned that documentation is a product in and of itself and good documentation can be a differentiator for your company. Think about how Stripe revolutionised the developer experience. They did it with an easily implementable product and a solid dashboard, but what many developers rave about are the docs. If your documentation is bad, most developers will still make your product work if they have to (see above about being extremely persistent), but they will do so begrudgingly. They will feel frustrated that they cannot easily fix issues, because your docs are hard to navigate or don’t provide enough information. And as soon as a competitor with better DX comes along, they will switch. Adapt Carl W. Buehner’s quote:</p><blockquote>They may forget what you said — but they will never forget how you made them feel.</blockquote><h4>By enabling a developer, I enable an organisation and millions of users</h4><p>This has been one of the most fulfilling parts of designing tools for developers and thinking about DX. Seeing Agolia’s search API enable some of the world’s largest brands’ search experiences (even if I can’t name them… thanks, NDA) has been extremely rewarding. Knowing that by giving developers tools to build amazing search engines and experiences, I am creating a whole cascade of positive effects. I am allowing organizations to achieve their key goals, such as increasing conversion, by helping their customers find the products they are looking for quickly. I am also improving the everyday search experiences for millions of people like you and me.</p><p>If this sounds exciting to you, come design with us! <a href="https://jobs.lever.co/algolia/9f410614-3a51-4a93-878f-dae1e2ddc7a3">We’re hiring</a>.</p><h4>More about designing for devs</h4><p>There are many great articles on how to design for developers and I did not want to repeat all of their points here, so check them out:</p><ul><li><a href="https://www.invisionapp.com/inside-design/designing-for-developers/">5 best practices when you&#39;re designing for developers | Inside Design Blog</a></li><li><a href="https://uxdesign.cc/designing-for-developers-e44280438e27">Designing for developers</a></li><li><a href="https://about.gitlab.com/2018/08/17/designing-for-developers/">How to design for (and with) developers</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1970ba0fb3b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/algolia-design/what-i-learned-about-designing-tools-for-developers-1970ba0fb3b5">What I Learned About Designing Tools for Developers</a> was originally published in <a href="https://medium.com/algolia-design">Algolia Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keeping Design Vibrant at a Dev-led (and any other) Company]]></title>
            <link>https://medium.com/algolia-design/keeping-design-vibrant-at-a-dev-led-and-any-other-company-44ff0d567424?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/44ff0d567424</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Thu, 08 Nov 2018 14:22:57 GMT</pubDate>
            <atom:updated>2018-11-15T09:55:01.113Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our story about growing design’s presence and value at a company, where developers have cache(t)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nbN-_GrH8u8SCETOyMnmRA.png" /></figure><p>It’s no secret <a href="http://www.algolia.com/">Algolia</a> was founded “by developers for developers”, and given our emphasis on breakthrough technology, it’s no surprise that early on the focus was on building out our engineering organization. The truth is, the product and design orgs are quite young at Algolia (1.5 years old). And while developers still make up the vast majority of our product building org, this doesn’t mean that design hasn’t found its home here, too!</p><p>Thinking about elevating design’s presence in an organization is not a new topic. In fact, in San Francisco, this topic has been regurgitated so many times, I am sure you Bay Area folks are all rolling your eyes right now. I am based in Paris, though, and here, the topic is alive and very relevant. I often get approached by designers from other Parisian start-ups asking for advice on what they can do to make design more valued, vibrant and visible.</p><p>Here are a few things we’ve tried at Algolia to communicate what designers do and to strengthen our design culture as a team.</p><h4>Take Up Physical Space</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CpNbvJ9vMHiwLNtdK3U3zw.jpeg" /></figure><p>We took the “make design visible” goal literally and occupied a free corner of the office to show our designs, research and to gather feedback. It was incredible how many conversations the new space sparked. Others in the office approached us to ask design-related questions or to simply learn about what we’re doing. It was a great opportunity for us to expand their understanding of what designers do day-to-day and how we think. It is also an opportunity to hear directly from some stakeholders and to provide them another outlet to express opinions.</p><h4>Show, Don’t Tell</h4><p>This is one of the mindsets from <a href="https://dschool.stanford.edu/resources-collections/getting-started-with-design-thinking">Stanford d.school’s Intro to Design Thinking workshops</a>, and we try to live it every day. Instead of just telling others what designers do, we try to show them by facilitating workshops, inviting them to user research sessions, and using the design process sporadically. For example, one time at a Product offsite we wanted to figure out which problem, as a product group, we should solve. After seeing that just chatting about it wasn’t moving us forward, one of our designers proposed the Note-and-Vote technique from the Design Spring methodology (also very well described by <a href="https://medium.com/u/7baf15e4c260">AJ&amp;Smart</a> in this <a href="https://www.youtube.com/watch?v=xNpVaNIUS4U">YouTube video</a>). The team was engaged and, in the end, we came up with a project to tackle. The organizer of the offsite thought it was a great way to cut down on back-and-forth chatting and to arrive at an outcome.</p><h4>Build Alliances by Providing Support</h4><p>Early on, we recognized that a key partner of design would be the client-facing teams, as they saw every day the kind of impact design thinking can have on client outcomes. We have developed several initiatives to help support these teams, so that, in return, they can advocate on our behalf as well.</p><p>One of our early initiatives was to establish UX Office Hours, where anyone could come to ask questions. At first, the attendees were primarily from sales and account management. However, over time, we have seen more and more people from other groups come, such as developers, PMs and marketers. We host them every 2 weeks on a first-come, first-serve basis. This is a great way for us to understand where the greatest design needs are in the organization and how we can address them. For example, after noticing a pattern of similar questions about best practices of search experience on e-commerce sites, our team held a “Special Edition Office Hours: Best Practices of E-commerce Search.” It was a huge success and delivered immediate value to the client-facing and marketing teams.</p><p>Another thing we did was to provide individual support to high-priority clients by conducting UX workshops and having UX reviews of their designs. While this was surely outside of our scope of work, it helped us build key relationships within the organization.</p><p>When it came time to advocate for more headcount or to move certain initiatives forward, we weren’t the only ones making the case for them. Our partners in other parts of the org helped convince decision-makers that design is a worthwhile investment.</p><h4>Welcome Everyone Into the Process</h4><p>When building a product, it is common sense to include other product building teams (devs and PMs) in the process by hosting regular design reviews, facilitating design sprints and actively encouraging an exchange of ideas. But what about those folks in the organization that don’t directly build products? How do we get them to understand the process and its value?</p><p>At Algolia, we wanted to move beyond our direct squads to show the value of human-centered design. We started to host monthly “Introduction to Design Thinking Workshops” (based on Stanford’s s.school <a href="https://dschool.stanford.edu/resources/gear-up-how-to-kick-off-a-crash-course">Crash Course</a>) open to anyone at Algolia. By getting their hands dirty and trying out the process, many of our colleagues realized that design is more than just pretty UI, and, more importantly, found tools they could apply to their day-to-day work.</p><h4>Start Within (Build a Strong Team)</h4><p>It is hard to build a vibrant design culture without a vibrant design team. This is why if you’re on the hiring side of things, it is essential to recruit folks who will not only produce great work, but will also drive the design culture forward. At Algolia, we have an amazing team of designers with different backgrounds, personalities and experiences. We are all united by passion for our company and for design. We are also all on-board with fighting the good fight in order to make sure design gets its proper place and recognition. Finally, we try to have a good time and support each other, which is essential when the going gets tough. Being able to rely on my team’s support has been essential in staying positive, looking on the bright side of things and thinking of great solutions to all sorts of problems.</p><p>While it takes ongoing effort to keep design vibrant and understood at a company, the positive results are absolutely worth it. It gives the team a sense of accomplishment and improves our day-to-day work environment. We also learn from the experiences, which is always important. If you’ve tried things that we haven’t though of, please share your ideas in the comments below! We are always looking for new ways to bring others at Algolia into our world.</p><p>If you think you want to join a team like this, get in touch. <a href="https://jobs.lever.co/algolia/9f410614-3a51-4a93-878f-dae1e2ddc7a3">We’re hiring</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44ff0d567424" width="1" height="1" alt=""><hr><p><a href="https://medium.com/algolia-design/keeping-design-vibrant-at-a-dev-led-and-any-other-company-44ff0d567424">Keeping Design Vibrant at a Dev-led (and any other) Company</a> was originally published in <a href="https://medium.com/algolia-design">Algolia Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Critiques and Guidelines for Sharing Design Work]]></title>
            <link>https://medium.com/algolia-design/design-critiques-and-guidelines-for-sharing-design-work-776313411f4?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/776313411f4</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Thu, 01 Nov 2018 11:17:56 GMT</pubDate>
            <atom:updated>2018-11-01T11:17:56.101Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-719WD8p3ni32HeGcPCTSw.png" /></figure><p>At <a href="http://www.algolia.com/">Algolia</a>, sharing design work is a basic expectation for designers and is considered an essential element of career progression. It challenges us to practice our core <a href="https://www.algolia.com/careers">company values</a>: candor, trust, humility, grit and care. And it not only improves the quality of our designs, but also provides team members and stakeholders the opportunity to align on vision, to learn and to grow. For a long time, we didn’t have set expectations about sharing work, but as our team began to grow, we wanted to formalize our practices for the benefits of consistency and on-boarding team members.</p><h3>General Tips and Guidelines</h3><p>This is how we set expectations for product designers at Algolia regarding sharing work:</p><ul><li><strong>Show often and early</strong>: You are expected to show your work at each stage of the design process, on a regular basis with your immediate squad, key stakeholders, and the design team.</li><li><strong>Use all the tools:</strong> There are many ways to show work: in weekly Design Critique attended by brand and product designers, in project design reviews, through digital channels, such as Slack and email. Try not to get stuck in a single mode of sharing and know which method will best give you the desired results.</li><li><strong>Don’t skip Design Critique</strong>: When you come, be prepared to contribute and share (see below).</li><li><strong>Use virtual channels for <em>non-critical</em> feedback only:</strong> Sharing in Slack channels or via e-mail are great ways to provide progress updates, “FYI” or optional feedback opportunities for broader stakeholders. If you need timely and critical feedback to move your project forward, please schedule a meeting with the folks from whom you need the feedback. Feedback is best received in a two-way exchange, and it will be more time-efficient in the end.</li><li><strong>Schedule a review cadence for your project team</strong>: You should be conducting <strong>in-person</strong> critiques with your squad. A good time to start them might be at the beginning of the Ideation phase of your project. Cadence is up to you, but weekly or bi-weekly is recommended. You can share progress via other channels between these review sessions.</li><li><strong>Help others improve their feedback skills</strong>: Especially non-designers may have trouble providing feedback in a form that is useful to you. Use this as a coaching and teaching opportunity to ensure the giver grows in this area and you get the feedback that helps you move forward.</li><li><strong>Provide great feedback:</strong> Lead by example by providing thoughtful and kind feedback to others.</li></ul><h3>Design Critique</h3><p>Design Critique is an essential part of our team process, because it allows us to help each other improve, grow and learn as designers.</p><h4>Rules of Engagement</h4><p>When we first started this practice, the designers collectively came up with “Rules of Engagement” for our critique:</p><ul><li>Come prepared to show something at every/most critiques, even if it is “not ready”. The best time to receive feedback is <em>early </em>in the process (sketching phase), so there is no such thing as showing a design “too early”.</li><li>Assume best intentions and accept feedback gracefully (<a href="https://zenhabits.net/how-to-accept-criticism-with-grace-and-appreciation/">read more here</a>);</li><li>Ask clarifying questions when you do not fully understand the design or a piece of feedback</li><li>Stay off devices!</li><li>Critique should be considered a high-priority meeting on our calendars and not missed, if possible.</li></ul><p>The structure of our critique was inspired by <a href="https://medium.com/facebook-design/critique-is-an-important-part-of-any-design-process-whether-you-work-as-part-of-a-team-or-solo-ef3dcb299ce3">Facebook’s approach</a>. There are three key roles in critique and each has a part to play.</p><h4>The Facilitator:</h4><blockquote>Fostering the right environment in critique is critical (get it?) as it can either lead to open-minded exchange or a sense of dread. It’s the facilitator’s job to ensure that the atmosphere remains focused, light-hearted and positive.</blockquote><p>Here are few things the facilitator does to achieve that:</p><ul><li><strong>Creates agenda: </strong>Asks participants ahead of time what they want to present, how much time they need and what kind of feedback they’re looking for.</li><li><strong>Keeps time: </strong>Sets a timer and sticks to it to ensure everyone gets a chance to show their work; if one project needs extra attention, encourage the person to schedule a separate deep-dive critique for just this project (this is very encouraged!)</li><li><strong>Fosters an inclusive environment: </strong>Starts with remote folks first.</li><li><strong>Enforces the guidelines: </strong>Reminds participants to remind us what type of feedback they are looking for and what the reviewers should focus on. Makes sure to whip folks on devices into shape.</li><li><strong>On-boards newcomers</strong>: When new team folks join the critique, the facilitator’s role is to bring them up-to-speed on best practices and rules of engagement.</li><li>Read more here: <a href="https://medium.com/facebook-design/critique-is-an-important-part-of-any-design-process-whether-you-work-as-part-of-a-team-or-solo-ef3dcb299ce3">Four Things Working at Facebook Has Taught Me About Design Critique</a> by <a href="https://medium.com/u/e184f9feff12">Tanner Christensen</a></li></ul><h4>The Presenter :</h4><p>Presenting is more than just doing as a walk-through of your design work. It is about providing the full picture to your audience and focusing their attention where it is most needed. Here is what an effective presenter does:</p><ul><li><strong>Provides context and goals: </strong>What’s the problem we’re trying to solve? What does success look like? What’s our time frame? What are the main constraints? For whom is this being designed?</li><li><strong>Asks for feedback: </strong>What type of feedback are you asking for? What should the reviewers focus on? Let your audience know where you need help and divert their attention away from things where you don’t (e.g. “I am not looking for visual feedback right now as I haven’t tackled that yet.”)</li><li><strong>Tells stories</strong>: Critique is a great opportunity to practice storytelling. Instead of just showing where different buttons are, walk through the designs explaining rationale and how it will impact your users’ lives.</li><li>Read more here: <a href="https://www.google.com/url?q=https%3A%2F%2Fmedium.com%2Fthe-year-of-the-looking-glass%2Fhow-to-present-designs-4a78c3ebca7b&amp;sa=D&amp;ust=1540177178794000&amp;usg=AFQjCNGg1I20zol2id66hGl_1qjOafe7sQ">How to Present Designs</a> by <a href="https://medium.com/u/b8a4e5ae7490">Julie Zhuo</a></li></ul><h4>The “Critiquers”:</h4><p>The critiquers have the most delicate job of all. They need to understand the problem, to clarify their own understanding of the solution and to provide actionable feedback in a respectful and kind manner. It’s not easy and requires practice! Here are a few things one can do to get there:</p><ul><li><strong>Stay present: </strong>Stay off your devices and give the presenter respect and undivided attention</li><li><strong>Ask clarifying questions</strong> instead of making assumptions</li><li><strong>Be specific</strong> about what’s working and not working</li><li>Evaluate designs and speak in term of their effectiveness from point of view of <strong>user needs &amp; project goals</strong></li><li><strong>Provide</strong> <strong>directional suggestions</strong>, but avoid problem solving</li><li><strong>Be kind</strong> and empathise with the presenter</li><li>If you have any feedback or ideas beyond the scope of feedback requested, write it down and discuss after the critique.</li><li>Read more here: <a href="https://zenhabits.net/how-to-give-kind-criticism-and-avoid-being-critical/">How to Give Kind Criticism, and Avoid Being Critical </a>from <a href="https://zenhabits.net/">Zen Habits</a></li></ul><p>Design Critique is one of my favorite meetings of the week. At Algolia, it is a dynamic, fun and creative moment in our busy schedules. I learn a lot from the designers in the room all of whom have various strengths and talents. It is a great opportunity for us to get a glimpse of what each of us is working on and the progression of our projects over time. I am confident that without critique the quality of our work would suffer and the sense of trust and care we build a a team as well.</p><h3>More resources:</h3><ul><li><a href="https://www.google.com/url?q=https%3A%2F%2Fplaybook.uie.com%2Fblog%2Fwhat-goes-into-a-well-done-critique&amp;sa=D&amp;ust=1540177178794000&amp;usg=AFQjCNFAokiqTrLOjlth_SBhTTPS6XdX0w">What Goes Into a Well Done Critique</a> by <a href="https://medium.com/u/b90ef6212176">Jared M. Spool</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=776313411f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/algolia-design/design-critiques-and-guidelines-for-sharing-design-work-776313411f4">Design Critiques and Guidelines for Sharing Design Work</a> was originally published in <a href="https://medium.com/algolia-design">Algolia Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips from a design hiring manager: become a better designer (and human) while job-hunting]]></title>
            <link>https://uxdesign.cc/tips-from-a-design-hiring-manger-use-the-job-hunting-process-to-become-a-better-designer-b631e2102156?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b631e2102156</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Tue, 30 Oct 2018 08:51:52 GMT</pubDate>
            <atom:updated>2018-11-03T06:26:18.287Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FI1WhxLv2EuQqW2AHDQyXw.png" /></figure><h4>How to shifting your mindset about the design interview process can help you become a better candidate and designer.</h4><p>Job hunting is not a comfortable process for most of us. It’s been more than a year since I’ve joined Algolia, and I still often reflect on the process that got me here. I remember while in the midst of it, I sometimes felt frustrated, self-doubting, and confused. With some distance now and being on the other side of the table as a hiring manager, I can reflect on it and realize that the process was an amazing opportunity to strengthen some of my core competencies as a designer. Here are some ways in which the interview process can make you grow if you embrace it.</p><h4>It Will Strengthen Your Storytelling</h4><p>Storytelling is hard and, personally, I wish I had more opportunities to practice this skill day-to-day. When you’re interviewing, however, you have the chance to tell stories all day long. It is an essential skill for any designer looking to mature in their career.</p><p>Use the interview process as an opportunity to learn to frame past experiences and approaches to design problems. Design hiring managers look for intentionality in design decision-making, which may be difficult to convey without showing the full picture and context to your thinking. Especially in a field where the user acts as a focal point for our work, framing the problem and solution through the users’ story is an effective communication approach.</p><p>This skill is going to serve you long past your interview process, so use the opportunity to practice it now.</p><h4>It Gives You a Chance to Practice and Improve Your Craft</h4><p>Those dreaded take-home assignments/ whiteboard exercises. Haven’t companies realized by now that they are not a good way to judge skills, because they don’t provide a realistic setting/problem for the candidate? What about prompts that solve company problems? Free work! Don’t they consider that candidates are applying to multiple jobs while working full-time, so spending time on each assignment adds up? What about candidates with obligations?</p><p>Sure, some companies haven’t realized all that, but if you want to work there, you’ll still have to do the assignment. Instead of complaining about it, look at it differently. How often do you get to work on an a design problem without PMs or devs telling you it isn’t possible? How often do you get to explore a variety of different design challenges you encounter in the recruiting process (e.g. re-design the grocery store checkout experience; create a mobile search experience; design dashboard for people moving homes; design a dog-walker app for Apple Watch, etc.)? Those are some fun problems to think about! And they really can be challenging.</p><p>At first, I grumbled about all of the work I had to do, but I quickly realized that I was actually having fun. We all know that to grow as a designer, you just have to practice design. Here, I was forced to do design exercises all day, which made me think about new problems, new user types, practice asking lots of questions, and go through the design process “my way” as I had fewer constraints. I was also able to improve my execution skills, because knowing that my Sketch files and prototypes would be thoroughly scrutnized, I approached my deliverables with more diligence.</p><h4>It is an Opportunity to Ask for and Give Feedback</h4><p>Another essential skill for a designer is ability to give, receive and learn from feedback. The interview process is one of the best venues to hone those skills. In some cases, the company will test this skill directly. In others, you can proactively develop the skill yourself by asking for feedback, and by providing it. As a hiring manager, I look for candidates with high emotional intelligence and well-developed soft skills (or potential in this area). You can showcase some of those skills by providing actionable, thoughtful feedback on the product or even the recruitment process.</p><h4>It May Prompt You to Reflect and Adopt a Growth Mindset</h4><p>During the interview process, you have the opportunity to reflect on your past experiences and take some lessons from them. It’s a chance to come to terms with failure and grow from it, and it’s an opportunity to re-frame your thinking about situations in the past. I always ask candidates about tough experiences, because I am interested in the framing of the problem more than the experience itself. How does the candidate present the situation? What terms do they use? How do they speak about others? Do they still sound upset and bitter about it or have they been able to extract key learnings and move on? As designers, we’ll continuously need to shake off failure and from our own and others’ mistakes. I’ve rejected candidates in the past because they framed situations in a black-and-white manner or have not reflected on their own contribution to the problem.</p><p>Ultimately, as a hiring manager, I am looking for someone who’s hungry and who uses every opportunity to become a better version of themselves as a designer and human being. I want my team members to be people who use experiences as stepping stones, not turn them into baggage.</p><p>I didn’t come to these conclusions overnight. I used to dread the hiring process. Having been on both sides of the table has helped me understand that the process is a unique and not-too-frequent opportunity to re-evaluate my own past actions, to sharpen my hard skills, and to understand where I still need to grow. While exhausting and stressful, I feel like I come out of the process a better version of myself than I went into it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b631e2102156" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/tips-from-a-design-hiring-manger-use-the-job-hunting-process-to-become-a-better-designer-b631e2102156">Tips from a design hiring manager: become a better designer (and human) while job-hunting</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 hack user research]]></title>
            <link>https://uxdesign.cc/how-to-hack-user-research-d30afb3c9494?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d30afb3c9494</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Wed, 18 Apr 2018 18:18:10 GMT</pubDate>
            <atom:updated>2018-09-21T00:29:35.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Ft7KY_Q2fG5qMQkIeY3nQ.png" /><figcaption>Illustration by <a href="https://medium.com/u/a10984748503">Tiphaine Gillet</a></figcaption></figure><h4>In this article, we’re sharing how we’re getting creative with conducting user research to show its value quickly and dispel notions that it’s an expensive bottleneck.</h4><p>In theory, most of us in tech know that we need to listen to the user, understand their needs and test our products early and often. In practice, it’s hard to do when we’re running by the seat of our pants trying to launch features. User research is commonly associated with prolonged timelines, additional expenses, and results that are interesting, but hard to act on (e.g., “our users don’t immediately see the value of our product”).</p><p>Your colleagues may be tempted to skip research altogether and “learn and iterate after it’s live.” That approach can create the illusion of saving time in the short term, because the product is out sooner. However, in the long term, and I’ve seen it, it can lead to wastefulness. If you release a product whose most important hypotheses are not validated even a little, you may have to spend a lot of effort redesigning and rebuilding the product (potentially incurring tech and design debt in the process).</p><p>By working with several start-ups and now at Algolia, a hyper-growth, developer-led organization, I’ve learned that I can be creative and agile in order to balance research with moving quickly. It means spending less time on recruitment and picture-perfect deliverables. It means sometimes talking to a not-perfect-fit-target-user, but still getting extremely valuable information.</p><p>Every organization is different and sets its own expectations for deliverables and project outcomes. This is what has worked at Algolia, and I am not sure it would have the same positive reception at a large multinational corporation. Still, you will pick up a few tips here that may work for you.</p><h3>Know what you’re trying to do</h3><p>Let’s go back to the basics for a moment. What you want to learn will determine whom you will recruit, how you will test and how much time you will need. If you want to test usability of your feature, you’ll run a usability test. If you want to conduct exploratory research to generate new feature ideas, you may run an observational study or in-depth interviews. Defining your goals as a first step in your project will help you to pick the right research tools and to keep the project scope focused and manageable.</p><h3>Save time on recruitment, not on research</h3><p>Recruitment, in my experience, is the most painful part of user research. You can pay recruitment companies to do it for you, but if you have a modest budget, you can be creative to economize time.</p><p>Even if you can’t recruit your ideal target user, it is still better to have someone walk through the prototype than no one. You can recruit in coffee shops: offer people free coffee for 5 minutes of their time (pro tip: avoid the morning rush). You can try posting an ad on Craigslist. You can go to a co-working space and set up a research station. Ask your friends to take a look when you see them over the weekend.</p><p>Let users come to you. If there a company event/meetup coming up that will attract your target users, set up a research station and give out swag or gift cards as compensation. People will be there because they are already interested in your company. Capitalize on this! Make them feel like they’re helping shape your company’s future. Train others within your company to help so you can test with even more people.</p><p>A company I know has Support Days, where once a week, users can come in and get their questions answered in person. Next to the support folks, there is always a researcher recruiting participants and running usability sessions</p><p>Use tools like <a href="https://calendly.com/">Calendly</a> to minimize the back-and-forth of scheduling, which can add up time.</p><h3>Test with fewer people</h3><p>I usually go for 5–7 users (within each user type category). Most of the time, you will have enough data with this number to see trends. If you don’t see trends or the patterns are weak, then you can add a few more participants. Some research is always better than no research.</p><h3>Approximate your user</h3><p>When you need results quickly, something is better than nothing. This is especially true if you are testing a prototype and are looking for general usability. Instead of spending time trying to find the ideal user profile, you can approximate your user and test with people of similar profiles. Let’s say you’re building a web app that will help sales folks in the solar industry draw up preliminary plans for a solar project. You want to test the usability of your drawing tools, which they will use to place a project on the map and generate a solar panel layout. Do you need solar sales people to test this? No! You need people of the same general comfort level with technology to see how they would use the tools. On the other hand, if you need to test the usability of the industry-specific input fields, then you definitely need to test with your target user and there isn’t a way around that.</p><p>One important note: this technique does not work for generative research, in which you need to get as close to your exact user as possible. If you don’t understand your actual potential users’ problems, you may not build the right products.</p><h3>ABC — Always Be Conducting</h3><p>Finally, it is much easier to do research if you have target users in the pipeline. It takes a bit of <a href="https://blog.airtable.com/how-to-build-a-ux-research-system-that-runs-on-autopilot/">organization up front</a> (more <a href="https://segment.com/blog/creating-a-user-research-program-that-drives-itself/">here</a>), but can help prevent scenarios where you need to test, but don’t have participants. If you are a product designer and research is not your full-time job, dedicating even 2–4 hours each week to planning user research upfront may save you time when a research need arises in the future. Constantly recruit and set up conversations, testing sessions, etc. Try to create a pipeline of research calls and activities that you can later adapt to your needs.</p><h3>Use all the tools</h3><p>Speaking of tools… When you’re short on time, you should use every opportunity and tool to get the data you need, which means stepping outside of the one-on-one interview comfort zone.</p><ul><li>I will start by mentioning the myriad of user research tools out there: <a href="https://validately.com/">Validately</a>, <a href="https://www.usertesting.com/">UserTesting.com</a>, <a href="https://www.userzoom.com/">UserZoom</a>, and so many others. You can read about pros and cons <a href="https://www.justinmind.com/blog/usability-testing-prototyping-7-best-user-testing-tools/">here</a>, and <a href="https://www.nngroup.com/articles/unmoderated-user-testing-tools/">here</a> is an oldie, but goodie on how to select these tools from Norman Nieman Group.</li><li>Join sales and implementation calls with your colleagues. These can provide a lot of information for you.</li><li>Does your company use <a href="https://www.intercom.com/">Intercom</a>? Set up mini-research questionnaires using the “Engage” feature to gather data and to recruit for research.</li><li>Do you have a support team or a call center? Listen in on the calls if you can. Go through the support tickets and conversations and follow up with users for further details. Speak to the support team members about what they’re hearing as well. (Keep in mind that they may speak to you in terms of solutions: “Our customer would be happier if we built X.” Try to get to the bottom of the problem rather than focusing on the solution first.)</li><li>Think about implementing an analytics tool like <a href="https://www.kissmetrics.com/">Kissmetrics</a>, <a href="https://www.google.com/analytics/analytics/#?modal_active=none">Google Analytics</a>, <a href="https://www.hotjar.com/">Hotjar </a>or <a href="https://www.fullstory.com/">FullStory</a> on your site to get some insights about how it’s being used. While these tools tell only a part of the story, they can give you some indication about quick wins on your site. For example, we recently learned through Hotjar heatmaps that the “Search UI” section on our docs page is too hidden. As a result, we will make it more prominent in the next redesign to ensure we share our Search UI expertise in addition to our technical know-how.</li><li>Talk to the subject matter experts. Sometimes, they will tell you more than ten users will. Recognize their biases (and tendency to suggest a lot of solutions), and use their wealth of knowledge.</li></ul><p>There are many, many tools at your disposal to get insights into your users’ needs and thoughts. Learn more about the different tools <a href="https://blog.airtable.com/43-ux-research-tools-for-optimizing-your-product/">here</a>.</p><h3>Show results quickly, often — and don’t overdo it</h3><p>As tempting as it is, don’t wait for the grand finale results presentation. Synthesize results as you go along and whet your stakeholders’ appetite. I usually do a synthesis session at the end of each day and then a larger one at the end of the week. I like to send out a research update each day or every few days to my team (that includes PMs, developers and other interested parties). This creates a sense of progress and my stakeholders are happy to see some early insights.</p><p>When hacking research, try not to fall into the deliverables trap. I usually don’t spend a lot of time on picture-perfect research reports. I compile key findings and recommendations focusing on the “so what” rather than spending time making pretty persona sheets for the sake of creating attractive deliverables. They take time and may impress people at first glance, but if they walk away not knowing what to do with these deliverables, then my time wasn’t well spent. Focus on impact of your research. What action should your stakeholders want to take right after they read your results?</p><p>As I mentioned before, it is important to consider your organization’s expectations and culture while implementing these methods. One time, I consulted with a large, traditional company, where presentation was essential to selling the idea. Our program manager hired a video crew to make a short film about our project. To me it seemed excessive, but the project would not have succeeded without it. So keep in mind what type of delivery will ensure your project’s success, but don’t be afraid to go leaner on the presentation if you can get away with it.</p><p>Most people in my company love hearing what our customers experience when they use our product. They are hungry for insights. It is our responsibility as advocates of user research to adapt our techniques to the organizations we serve so that we can keep giving our users a voice.</p><p><em>Originally published at </em><a href="https://blog.algolia.com/how-to-hack-user-research/"><em>blog.algolia.com</em></a><em> on April 18, 2018. Thanks to Marlin De May for revisions and feedback.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d30afb3c9494" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-hack-user-research-d30afb3c9494">How to hack user research</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 Change Careers While Pregnant and After]]></title>
            <link>https://medium.com/@sashaprok/how-to-change-careers-while-pregnant-and-after-4b13ca673410?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b13ca673410</guid>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[motherhood]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Wed, 18 Jan 2017 05:47:16 GMT</pubDate>
            <atom:updated>2017-01-18T17:57:58.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aBHdkjah7Y6KgDiL9JYmzg.jpeg" /></figure><p>I had been thinking about transitioning to User Experience (UX) design for almost a year. I took designers in my company out to lunch to find out more, attended design events and read about it as much as I could. Yet, I couldn’t find the courage to jump in and make the switch from my comfortable job… until I saw that positive pregnancy test.</p><p>My husband and I decided to start a family around the same time I finally decided to make the career switch. I expected to have some time to work on my new career path before pregnancy, but we got pregnant faster than either of us expected. As I stared at those two pink lines, I had two thoughts:</p><ol><li>There is never a prefect time to make a big change.</li><li>It’s all or nothing!</li></ol><p>At ten weeks pregnant, I told my boss that, given my new situation, I decided to take the leap of faith and explore a design career. Two weeks later, at the end of my first trimester, I began my 10–week full-time design program at General Assembly.</p><p>Now, just 2 years later, I am a proud Product Designer at a small tech company.</p><p>In my parent networks, I often run across moms and pregnant women who want to make a career switch, but feel stuck or do not know where to begin. Career change is not easy for anyone. It seems especially daunting if you’re expecting. I have good news, though: with the right preparation, expectations, support and mindset, expecting moms can absolutely do it. In my opinion, it’s easier than raising a kid!</p><p>Here are a few things that I learned from my experience.</p><h4>Make a Plan</h4><p>Before taking such a big step during an already emotionally charged period of your life, figure out what skills you currently have and which skills the new role will require of you. Then, figure out how you will get those skills in the time you have before you pop or after baby arrives. Make a list of your options to get those skills and get cracking. Keep your expectations and plans realistic and adjust as your pregnancy progresses. You won’t be able to get everything done before baby, and that’s OK.</p><p>If you can, try to get a little experience in your new career <em>before</em> you go on maternity leave, even if it is a free project for a friend or a project you made up.</p><p>Another important decision is when you’ll start getting back to your career after baby’s birth. Even if you are planning to leave your full-time job like I did, treat your time after birth as a proper “maternity leave.” I agreed to give myself 5 months to fully enjoy with baby, and after that picked up my career transition. Keep yourself accountable (and make your partner do it) to this timeframe and don’t push it off if you can help it.</p><h4>Get Your Support Network On-board</h4><p>This is the most important piece of advice I can give. Without your support network, this journey will be very tough and very lonely. If you have a partner, make sure they are 100% on-board with your plan, because they will be your cheerleader, crying shoulder, and (likely) provider. They will also need to make many sacrifices to support you in your journey.</p><p>I feel more than blessed for my husband, who fully supported me in the transition, comforted me, told me he is proud of me, and lovingly challenged me not to wallow in self-pity. He was the one who told me repeatedly I could get a design gig at 7 months pregnant and to continue networking. He was right.</p><h4>Announce Your Intent</h4><p>I didn’t think anyone would be interested in working with a 7-month pregnant lady, but I was wrong. A few former co-workers who just started their own company reached out to me. They knew I was new to the field and about to turn into a pumpkin, but they took a chance on me anyway (for which I am forever grateful). The only reason they knew to reach out was because I was very public about my new transition and career aspirations.</p><p>Tell people about your plan on LinkedIn. Meet for coffee with former colleagues and classmates. Tell them you’re interested in work and don’t be shy to ask for a connection or recommendations.</p><p>Also, studies show that if you make your intent public, you’re more likely to follow through on it.</p><h4>Build Your Network</h4><p>This goes hand-in-hand with the previous point. You want to start building your network <em>before </em>you need a new job. Relationships are like babies — they need 9 months to grow.</p><p>Start out by asking your friends and colleagues to connect you to others in their circles who do what you want to do. Take those people out for coffee and ask for advice about how to get into the field, their story, etc. Keep in touch and occasionally update them on your progress. Meet up occasionally. When you’re back from maternity leave, tap these people again and ask them for advice <em>again</em>. This time, ask about job search tactics, companies hiring, types of companies, interview advice, or anyone else they can connect you to. Often, those you’ve built a solid relationship with will offer to help. I would never have been successful without the generosity and help of those I met during that time.</p><h4>Create Space and Time</h4><p>As a new mom, you’ll have a lot on your plate, but personal time isn’t one of those things. When you are ready to re-start the career transition, take it easy. At around 3–4 months you can start to network online during nap times. You can even grab coffee close to home and bring baby along. I’ve done that with people I knew would be understanding and it worked well (until baby woke up and stole all the attention with his cuteness).</p><p>However, the above tactic will work for only so long. At some point, you will need dedicated time to be able to go out to events and to network. My husband and I invested in full-time daycare, which gave me the ability to focus on building new skills, finding clients and networking. If full-time isn’t an option, you can ask a family member to help watch the baby or get childcare part-time. Alternatively, network when your partner can be home and watch the baby. This is where the 100% buy-in comes in handy. Your partner <em>must </em>be willing to take over baby duty so you can focus.</p><h4>Prepare for the Roller Coaster and Keep on Keepin’ On</h4><p>They tell you to prepare for the postpartum emotional roller coaster. Joy one minute, crying the next…</p><p>Well, this is pretty similar. One day you’ll feel like you’re making great progress, and the next you’ll be wondering what the hell you’re even doing. This is, sadly and gladly, a normal part of the journey.</p><p>I heard the expression “Keep On Keepin’ On” when I started looking for work after maternity leave, and it stuck with me. In the moments when I felt down, I repeated it to myself and it helped me keep going.</p><p>I also reminded myself that every great journey begins with small steps, and all I have to do is put one foot in front of the other.</p><h4>Learn From Your Kid</h4><p>I am amazed at my son’s persistence and tenaciousness. He came into this world with a few instincts and almost no skills. Now, at 16 months, he’s running around and trying to talk. To get here, he’s taken falls and failed many times. He still does. Watching him is a lovely reminder that we all started at zero and have learned skills by practicing, trying and not giving up.</p><p>As I went through my career transition and continue to grow in my new career, my son is a wonderful and joyful source of inspiration. He not only reminds me why I decided to do this, but also that each of us can achieve many things if we’re willing to take a step, fall, stand up and try again.</p><p><em>If you have any questions, feel free to get in touch via comments or in the Contact section of my portfolio (www.aprokhorova.com/contact).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b13ca673410" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How My Geography Major Prepared Me to be a Product Designer]]></title>
            <link>https://medium.com/@sashaprok/how-my-geography-major-prepared-me-to-be-a-product-designer-70fde1f7ea91?source=rss-29c0b60055a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/70fde1f7ea91</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[geography]]></category>
            <category><![CDATA[social-science]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Alexandra Prokhorova]]></dc:creator>
            <pubDate>Sun, 08 Jan 2017 01:56:33 GMT</pubDate>
            <atom:updated>2017-01-18T05:47:58.340Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ykN3H_x4Sd2aGruyOnITeg.jpeg" /></figure><p>I am a Geographer-turned-Product Designer. In interviews and otherwise, many people ask me how this came about. I happen to think that the transition is a rather natural one. After all, Geography examines how humans shape environments and vice versa. I am sharing my story to encourage and motivate Geographers to consider a design career (or at least not to disqualify themselves from it). I also want to encourage those hiring to consider candidates with a Geography background.</p><h4>What is Geography?</h4><p>When people find out that I majored in Geography, the first question many ask is: “What’s the capital of [insert country name here]?” And while I know many world capitals, I didn’t learn them in my Geography courses at Dartmouth.</p><p>Here’s how my department describes the field:</p><blockquote>Geographers study the material and symbolic transformation of the earth in relationship to both human and natural processes. In keeping with contemporary global shifts in culture, the environment, politics and economics, the boundaries of the geographic discipline are dynamic. For example, environmental change, international development, globalization, and new spatial technologies exemplify important arenas of study in geography. Theories of space, scale, location, place, region, mobility and displacement allow geographers to critically analyze change in both human and physical environments. Geography is both a natural science and a social science as it examines people and their environment and serves as a bridge between the physical and cultural worlds.</blockquote><p>Is anyone starting to see the connection between Geography and user experience yet?</p><h4>Geo Skills as Design Skills</h4><p>I can confidently say that every single course I took for my major has benefitted my design career. To graduate, I was required to study cultural-social (e.g. geopolitics and third world development), GIS (Geographic Information Science — spatial analysis and mapping), nature-society courses (e.g. food and power) and physical geography (e.g. geomorphology). All this culminated in a two-quarter senior seminar focused on qualitative research methods.</p><p>Many of my courses focused on international development and geopolitics. I was drawn to them, because we often discussed how development institutions (e.g. World Bank, USAID) were blind to the actual needs of those they were trying to serve, and, instead, created ineffective “developmental solutions” rooted in their own biases and assumptions about the needs of the people in these communities. A different approach, of course, would be to start by understanding the problems from the point of view of those they wanted to serve. This was the academic version of Human-Centered Design and I didn’t know it.</p><p>In my GIS courses, I learned about spatial data and how to represent complex trends visually to communicate a message. I learned about databases and other technological foundations, which later on allowed me to speak to developers intelligently. I also learned about the importance of visual communication, which serves me to this day in my design work.</p><p>One of the most valuable pieces of my education was my department’s emphasis on research and storytelling. They encouraged (and sponsored) me to conduct field studies to truly understand existing problems, my own biases, and then to tell other people’s stories.</p><p>The combination of research, visual/spatial thinking, and social science theory created a meaningful foundation for my future career in product design.</p><h4>What I Would Do Differently to Prepare Myself for a Design Career</h4><p>I don’t have regrets, but if I were to go to college all over again, there are a few things I’d do differently.</p><p>First, I’d enroll in that Design Thinking course at the Engineering School. At the time, I was convinced I would go into academia, so I naturally focused on political philosophy and similar courses. However, I think this course should be fundamental to any new grad and I would encourage <em>everyone</em> to take it.</p><p>Second, I wish I gave myself permission to be creative. That’s where I have had to catch up the most as a designer. I didn’t take art classes in college, because I thought they weren’t worth the tuition costs and that I should focus on more “serious” things. In retrospect, an art class or two would have fundamentally changed my path to design. I’ve done art and visual design classes since (such as pencil drawing and basics of graphic design), and seen how valuable they have been.</p><p>Alternatively, I could have spent more time in the Jewelry Studio or signed up to do graphic design for a campus publication. There are so many options on campus to create, it’d be a pity not to take advantage.</p><p>Finally, and most importantly, I would not tie myself to a specific career track. Geography attracts many “do-gooders”, those who want to positively impact the world, give voice to the voiceless. I’ve seen many Geography majors put themselves on the academia/public sector/ international development/ NGO track without ever considering the direct positive impact they could have in the private sector. That’s how I approached it as well. I wanted to be a professor. I realize now that if I had kept an open mind, I could have diversified my internship experiences and coursework to make the transition to a private sector career easier.</p><h4>Advice to Geographers Exploring Tech</h4><p>There are many different ways to design, especially the newer fields like Product Design. If you’re a Geography major interested in exploring a design career, you should absolutely do it and not discount yourself because of your non-traditional background, or because “you didn’t do graphic design”, or you aren’t “creative”. Just like other social sciences, Geography taught you critical thinking, research and social theory, all of which are essential to design. You’ve spent time thinking about visual communication. In addition to that, Geography taught you to think about the contextual dimensions (cultural, spatial, environmental), which are incredibly important to developing products and services.</p><p>That said, visual foundation is helpful in addition to the research and critical thinking skills I outlined above. So take those extra GIS and mapping courses, where you can design beautiful maps to communicate important information. Or sign up for a graphic design course.</p><p>In Product Design, diverse perspectives are essential to building effective and useful products. Geographers can bring fresh ideas and relevant skills to create solutions that meaningfully and positively impact end users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70fde1f7ea91" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>