<?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 Jenifer Bulcock on Medium]]></title>
        <description><![CDATA[Stories by Jenifer Bulcock on Medium]]></description>
        <link>https://medium.com/@JeniferBulcock?source=rss-6c487187cd9f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*phKLcn2s8Z0z7U_u4hcP6Q.png</url>
            <title>Stories by Jenifer Bulcock on Medium</title>
            <link>https://medium.com/@JeniferBulcock?source=rss-6c487187cd9f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:29:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JeniferBulcock/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[User research in the 0–1 space: researching for innovation.]]></title>
            <link>https://medium.com/@JeniferBulcock/user-research-in-the-0-1-space-researching-for-innovation-ca2dce2a87b?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca2dce2a87b</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[experience-strategy]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Wed, 22 Mar 2023 16:06:32 GMT</pubDate>
            <atom:updated>2023-03-22T16:06:32.017Z</atom:updated>
            <content:encoded><![CDATA[<p>This article was originally published on the <a href="https://www.peoplemade.co/blog/user-research-in-the-0-1-space-researching-for-innovation">Peoplemade</a> blog in March 2023.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iMAgFNAtoz8kkp0ltRbmcg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@joannakosinska?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Joanna Kosinska</a> on <a href="https://unsplash.com/photos/1_CMoFsPfso?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Peter Thiel introduced the concept of 0–1 in his <a href="https://www.amazon.com/gp/product/0804139296/ref=as_li_qf_sp_asin_il_tl?tag=zto-20&amp;ie=UTF8&amp;linkId=K5HJDPUEXGTSURYE&amp;geniuslink=true&amp;asin=0804139296&amp;revisionId=&amp;format=4&amp;depth=1">2014 book</a>. It refers to the entrepreneurial practice of building something that does not exist yet — “a solution that changes the market”. It’s about having the courage to think beyond incremental advancements, to take a leap forward from what exists today. Thiel refers to this as the essence of true innovation.</p><h3>Research led innovation</h3><p>Generally speaking, user research is defined in two categories: generative and evaluative (more about these below). Both of these are important to the product development lifecycle and are leveraged at different stages, to inform solutions and reduce risk.</p><p>The third form of user research is exploratory research. In my experience, exploratory research gets less of a spotlight in the product development lifecycle, because teams are more focused on iterating on existing product offerings… Or, using Peter Thiel’s framework: 1-n. Whereas exploratory research is best suited to innovating in the 0–1 space.</p><ol><li><strong>Exploratory research:</strong> is useful to disambiguate a problem space, learn about the people within it and identify areas where innovation could flourish.</li><li><strong>Generative research</strong> is conducted in the early stages of product development and is used to deepen the understanding of a user group or problem area and generate ideas for solutions. It facilitates strategic decision-making. ie Are we building the right things?</li><li><strong>Evaluative research</strong> is used to test and validate potential solutions. By conducting evaluative research, companies gather feedback on ideas/concepts and identify areas for improvement before launching. It facilitates executional decision-making. ie Are we building things right?</li></ol><p><strong>Exploratory research</strong></p><p>Exploratory research is particularly valuable for guiding innovation, as it identifies unique or unsolved problems. This type of research is geared toward creating knowledge. It provides a foundational understanding of people, their behaviors, beliefs, motivations, and the social, cultural, and environmental contexts they live within. Exploratory research is particularly powerful when combined with other forms of research. ie market, external factors, macro trends, and strategic foresight. Exploratory research helps us think outside the box and ensures we are solving real problems for real people.</p><p><strong>Generative research</strong></p><p>In the context of early-stage startups, generative research is particularly valuable. By conducting generative research, startups can better understand their prospects, and customers to identify opportunities related to their existing products/services. This ensures companies are developing experiences that are more likely to meet customer needs and differentiate in the market.</p><p>It’s important not to skip the exploratory and/or generative phases when the goal is innovation. By not spending enough time in these phases we miss the opportunity to gather a deep knowledge about the problem space and people. This might result in missed perspectives and opportunities.</p><p><strong>Evaluative research</strong></p><p>Evaluative research, on the other hand, is typically conducted later in the product development process and is focused on evaluating and refining specific product or service concepts or design execution. This type of research is used to test the proposed solution, by evaluating hypotheses, validating or invalidating assumptions, and identifying areas for improvement.</p><h3>User researcher as an innovation partner</h3><p>User researchers are perfectly positioned to be partners to entrepreneurs and early-stage startups defining unique product/service offerings. User researchers have a high tolerance for ambiguity and are uniquely skilled to navigate it. By involving a researcher in this process, you not only gain a partner to help you navigate the ambiguity that is inherent when innovating. They also help set you up for success and uncover unexpected outcomes by thinking about the implications of product innovation through various lenses: ie. social, cultural, and environmental.</p><p>User research may become that undesired radically honest friend. However, as much as it will help prove if hypotheses are wrong, it will also provide insights to get them right.</p><h3>Informed innovation</h3><p>All forms of user research are valuable tools for driving innovation in product or service development. To yield the best results in the 0–1 space, research should be conducted in the following sequence*:</p><ol><li>Exploratory</li><li>Generative</li><li>Evaluative</li></ol><p>*Note: <br>There might be instances where it’s necessary to loop back to the prior step, however, it’s not advised to skip a step, when designing for innovation.<br>Depending on the level of ambiguity and risk, it is possible to consider combining 2 sequential steps in one study.</p><p>Trust the process of UX research. It may not always be clear where it will lead you, but it will always lead you to valuable outcomes. Stay curious.</p><p><a href="https://peoplemade.squarespace.com/blog/anatomy-of-a-usability-test">Next</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca2dce2a87b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anatomy of a usability test]]></title>
            <link>https://medium.com/@JeniferBulcock/anatomy-of-a-usability-test-bf3e6caa1cf?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf3e6caa1cf</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Thu, 09 Mar 2023 17:22:22 GMT</pubDate>
            <atom:updated>2023-03-09T17:23:31.560Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article was originally published on the </em><a href="https://www.peoplemade.co/"><em>Peoplemade</em></a><em> blog in March 2023.</em></p><p>Usability testing (or user testing) is an evaluative user research method. It’s specifically helpful when understanding if the UX design (user experience) “works” — can a human comprehend the information and complete goal-oriented tasks within acceptable limits? Usability testing is a great way to de-risk the launch of a product. It identifies potential hurdles or drop-off points with a new product flow or feature before it becomes available to your customer base.</p><h4>Usability testing is:</h4><ul><li>Assesses whether a user can navigate a product/flow/feature for its intended function</li><li>Assesses which areas of a product/flow/feature users have difficulty with</li><li>Measures users’ attitudes towards a task (satisfaction, comfort, ease of use)</li><li>Provides direction on what areas of the product/flow/feature need attention before shipping</li></ul><h4>Usability testing is not:</h4><ul><li>Ethnographic in nature. It will not help us understand our users’ backgrounds, beliefs, needs, or behaviors.</li><li>Generative. It will not help us understand our users’ pains or gaps in an experience.</li><li>Statistically significant quantitative data (usually)</li><li>Used to assess addressable market</li></ul><h4>When to conduct usability testing</h4><ul><li>When you are looking to evaluate the usability and comprehension of a new design concept/feature</li><li>When you have low or hi-fi wires of a screen design and/or short user flow</li><li>Ideally, after you’ve completed generative, exploratory, or concept validation research studies</li><li>Before you launch the product/feature</li></ul><h3>A framework for designing great tests</h3><p>To get the most out of your user test, it’s best to be very clear on what it is you want to learn. The below framework is helpful for narrowing in on your goals and tasks and designing a valuable study.</p><p><strong>Research goal</strong>: What are you trying to learn? eg. “Understand the usability of the shopping experience.”</p><p><strong>Research question</strong>: Usually framed with a user behavior or experience goal in mind. These questions should ladder up to the research goal and help you curate your task types. eg. “Are the filter/sort features discoverable and usable?”</p><p><strong>Task</strong>: An actionable request that you ask of your participants to capture insights that will help you answer the research question. eg. “Imagine you are looking to buy a pair of sneakers. Find all sneakers that are available in size 10.”</p><p>There are two types of tasks:</p><ol><li><strong>Open-ended</strong> — Open-ended tasks and questions allow the participant to respond without any constraints. They are particularly helpful in gaining deeper insights from your participants, for example, the reasons behind a response or attitude, or general feedback.</li><li><strong>Closed</strong> — Closed tasks and questions provide a finite set of options for the participants to select from. These are generally quick and easy to analyze.</li></ol><figure><img alt="Usability testing framework" src="https://cdn-images-1.medium.com/max/500/1*TAk5tFXBTn_QbHS9g04EaA.png" /></figure><h3>Tasks</h3><p>The majority of tasks can be broken down into 3 main categories:</p><ol><li><strong>Effectiveness</strong> — Whether or not users successfully achieve the task.</li><li><strong>Efficiency</strong> — Cognitive effort and resources expended to complete a task.</li><li><strong>Satisfaction</strong> — The level of comfort or acceptability of a given task.</li></ol><h3>1. Effectiveness</h3><p>The following data types help us understand whether or not a user can accurately complete a task that allows them to achieve the desired goal.</p><ol><li><strong>Task Success:</strong> This simple metric pass/fail measure, that tells you if a user could complete the given goal-oriented task.</li><li><strong>Error Count:</strong> This is the number of errors a user committed while trying to complete a goal-oriented task. It can be calculated with miss-clicks, rage clicks, or an indirect path that may yield errors.</li><li><strong>Single Ease Question (SEQ):</strong> This question measures (on a seven-point scale) the participant’s perceived ease of completing the goal-oriented task. It’s used as a predictor of task completion rates and times. Ask the SEQ after each completed (or failed) task. A sample of at least 10 should be used to yield meaningful results.</li><li><strong>Confidence:</strong> Confidence asks users to rate (on a seven-point scale) how confident they were that they completed the task successfully.</li><li><strong>Comparative or A/B testing</strong>: This is a method of comparing two versions of a design solution to determine which one performs better. Remember to alternate between showing A vs B first to avoid bias.</li><li><strong>Behavior</strong>: Observing behavior (when running moderated studies) can provide valuable qualitative data that can help you understand “why” participants might be struggling with a given task.</li><li><strong>5 Second Test or Rapid product reaction test:</strong> This is a method where participants are shown a design for 5 seconds and then asked to respond to a task. It can be used to assess messaging (recall and comprehension) and visual communication of a given screen.</li></ol><h3>2. Efficiency</h3><p>The amount of cognitive effort and time it takes for a user to complete tasks.</p><ol><li><strong>Time on Task:</strong> This metric measures how long it takes participants to complete or fail a given task. Longer task times are generally an indicator of usability problems. There are 3 ways to report this data:</li><li><strong>Average Task Completion Time</strong>: Include only users who completed a task successfully. This is the most common way to report.</li><li><strong>Mean Time to Failure</strong>: The average time users are spending on a task before they give up or complete the task incorrectly.</li><li><strong>Average Time on Task</strong>: The total duration users are spending on your task.</li><li><strong>Subjective Mental Effort Question (SMEQ):</strong> The SMEQ allows the users to rate the perceived mental effort to complete a task. It consists of a single scale (rated from 0–150) with nine labels from “Not at all hard to do” to “Tremendously hard to do”. This is slightly more sensitive than the SEQ. A sample of at least 10 should be used to yield meaningful results. <a href="https://uxpsychology.substack.com/p/standardized-usability-questionnaires-ccb">Learn more.</a></li></ol><h3>3. Satisfaction</h3><p>Satisfaction measures how well a product or service experience meets customer expectations. Understanding your customers’ task sentiment can help you prioritize the importance or urgency of design revisions. It can also be used as a prediction of customer loyalty.</p><ol><li><strong>Attribute or Transaction Satisfaction:</strong> This task asks the participant to rate (on a 7-point scale) their satisfaction with a specific flow/feature. It can be used to diagnose issues related to features, quality, ease of use, and price. To understand what’s driving these ratings, offer a space for customers to add a comment about their attitude.</li><li><strong>Likelihood to Recommend (LTR) /</strong> <strong>Net Promoter Score (NPS)</strong>: The Net Promoter Score is an index ranging from -100 to 100 that measures the willingness of customers to recommend a company’s products or services to others. It gauges the customer’s overall satisfaction by asking them to respond to an 11-point scale (0–10) and is an indicator of a customer’s loyalty to the brand.</li></ol><h3>Calculating overall usability</h3><ol><li><strong>Single Usability Metric (SUM):</strong> This metric is a compilation of 4 key metrics: task completion rates, task time, satisfaction, and error counts, and is used to represent the usability of a given task. A SUM calculator will help you compute these metrics. <a href="https://measuringu.com/wp-content/uploads/2005/04/SUMv5.xls">Download the SUM Calculator</a> from <a href="https://measuringu.com/sum-2/">MeasuringU</a>.</li></ol><h3>Benchmarking (against other websites)</h3><p>Some of the above metrics have industry averages and can be used to benchmark your digital experience. Below are benchmarking metrics, companies should aim for, or try to exceed (source MeasuringU):</p><ul><li>Task Success/Completion rate average: 78%</li><li>SEQ average: 5.5</li><li>NPS: average in your industry or, your company over time</li></ul><p>Alternatively, there are standardized surveys that can be used to benchmark overall usability.</p><ol><li><strong>System Usability Scale (SUS</strong>): The SUS has become an industry standard and is derived from a ten-item questionnaire (graded on a 5 pt likert scale). It can be conducted with a min of 5 participants. It measures the perceived usability of an experience. <a href="https://xd.adobe.com/ideas/process/user-testing/sus-system-usability-scale-ux/#:~:text=SUS%20is%20a%20practical%20and,problem%20with%20a%20design%20solution.">Learn more</a>.<br>• SUS average: 68</li><li><strong>Standardized User Experience Percentile Rank Questionnaire (SUPR-Q)</strong>: This 8-item questionnaire is ideal for benchmarking a product’s user experience. It allows participants to rate the overall quality of a product’s user experience based on four factors: usability, trust/credibility, appearance, and loyalty. For this reason, SUPR-Q can be used to calculate sub-scores for these categories. <a href="https://measuringu.com/product/suprq/">Learn more.</a><br>• SUPR-Q average: 50%</li></ol><figure><img alt="User testing techniques." src="https://cdn-images-1.medium.com/max/1001/1*4QHyYEvDoNy4p769wVBy8g.png" /></figure><h4>Additional user testing techniques</h4><ol><li><a href="https://www.trymyui.com/%E2%80%9Dhttps://trymyui.com/alfq%E2%80%9D?__hstc=122632852.96989b55399b5b7a01095688852c1eb0.1677265335863.1677265335863.1677265335863.1&amp;__hssc=122632852.1.1677265335863&amp;__hsfp=541345839">Adoption Likelihood Factors Questionnaire</a> (ALFQ)</li><li><a href="https://www.trymyui.com/blog/2017/02/24/sus-pssuq-website-usability-surveys/?__hstc=122632852.96989b55399b5b7a01095688852c1eb0.1677265335863.1677265335863.1677265335863.1&amp;__hssc=122632852.1.1677265335863&amp;__hsfp=541345839">Post-Study System Usability Questionnaire</a> (PSSUQ)</li><li><a href="http://sumi.uxp.ie/en/index.php">Software Usability Measurement Inventory</a> (SUMI)</li><li><a href="https://garyperlman.com/quest/quest.cgi?form=QUIS">Questionnaire For User Interaction Satisfaction</a> (QUIS)</li><li><a href="https://www.notion.so/Anatomy-of-a-usability-test-69c096801de940d3b27c627925eb52d8">Post-Study System Usability Questionnaire</a> (PSSUQ)</li></ol><p><strong>References<br></strong><a href="https://measuringu.com/">https://measuringu.com/</a><br><a href="https://uxpsychology.substack.com/">https://uxpsychology.substack.com/</a><br><a href="https://www.retently.com/blog/">https://www.retently.com/blog/</a><br><a href="https://xd.adobe.com/ideas/process/user-testing/">https://xd.adobe.com/ideas/process/user-testing/</a><br><a href="https://www.qualtrics.com/experience-management/customer/">https://www.qualtrics.com/experience-management/customer/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf3e6caa1cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stakeholders: the other end-user cohort]]></title>
            <link>https://medium.com/@JeniferBulcock/stakeholders-the-other-end-user-cohort-2e3989ba4967?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e3989ba4967</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[stakeholder]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[qualitative-research]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Fri, 10 Feb 2023 00:23:38 GMT</pubDate>
            <atom:updated>2023-02-10T00:23:38.494Z</atom:updated>
            <content:encoded><![CDATA[<p>This article was originally published on the <a href="https://www.peoplemade.co/blog/stakeholders-the-other-end-user-cohort">Peoplemade</a> blog in February 2023.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nz8o5SmbPXmfbwtkDfmmoQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jasongoodman_youxventures?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jason Goodman</a> on <a href="https://unsplash.com/photos/bzqU01v-G54?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’ve written dozens of research reports. It’s not uncommon that they are peppered with bold, honest phrases that are designed to emphasize important key findings. Findings that hold a lot of weight, and are foundational to influencing key decisions.</p><p>In my experience product and design teams find these eye-opening and energizing. They are grateful for the clarity and guidance. However, in organizations that are new to user research, or unfamiliar with qualitative data it can be challenging to persuade those at the very top.</p><h4>My biggest tip</h4><p>Here’s the key to ensuring success with your next stakeholder presentation… When planning your next research study, remember to also <strong>consider your stakeholders as an end-user cohort</strong>. This is the work behind the work. Take the time to set up some short “getting to know you” sessions with as many leaders as you can.</p><p>Use the questions below to guide you. By uncovering the answers to these, you will be better equipped to make sure that the next stakeholder presentation you give is received with open ears.</p><p><strong>Key questions</strong></p><p>Here are some questions you and your team might want to answer before you begin your next UXR project.</p><ul><li>What are your stakeholders’ goals/dreams/fears?</li><li>Do they have strongly held beliefs/assumptions that you should be aware of?</li><li>What’s their familiarity/level of experience with UXR? Do you need to educate or build trust?</li><li>What’s their comfort level with qual vs quant deliverables and methods? Do you need to explain the value or tailor your storytelling to suspend disbelief?</li><li>What’s their appetite for provocation? Are they open to having the study invalidate an idea or internally held assumption?</li><li>What altitude of insight will best resonate with them? Consider packaging insights differently for different stakeholders.</li><li>How do they prefer to consume information, long form/short form/deck/verbal presentation, etc?</li></ul><h4>This will help you</h4><ul><li>Build relationships with your stakeholders that will generate trust.</li><li>Understand what storytelling techniques/formats to employ and help you craft and frame a story that resonates.</li><li>Strike the right balance of qual and quantitative data to appeal to their decision-making preferences.</li><li>Ensure that your work is valued and has more impact on the organization.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e3989ba4967" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Skills designers need today]]></title>
            <link>https://medium.com/@JeniferBulcock/skills-designers-need-today-b7ec5e1618f5?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7ec5e1618f5</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Tue, 11 Oct 2022 13:47:41 GMT</pubDate>
            <atom:updated>2022-10-11T13:47:41.143Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Team sitting at board table with laptops." src="https://cdn-images-1.medium.com/max/1024/1*UgLbInVZz_W3p_tZ8flblg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mapbox?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mapbox</a> on <a href="https://unsplash.com/s/photos/designers?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The design industry has changed a lot over the years, and the skills required to succeed have shifted. It used to be that a successful designer was an expert in technical skills: design software, craft, and visual design. These days we have software and open-source templates/design components that replace the need for a deep level of competence in these areas. As a result, the skills designers need to succeed in the workforce have evolved, and today, more weight is put on soft skills and strategic thinking.</p><h4><strong>Communication</strong></h4><p>A big part of a designer’s job today is communication. Design is a team sport and the ability to communicate effectively is vital. Your approach and point of view are vital. The areas where good communication is needed are vast: presenting work to stakeholders, rationalizing decisions, and communicating the value of design.</p><ul><li><strong>Looping in stakeholders:</strong> The more awareness, buy-in, and visibility you can give to your work (or your team’s work), the more impact it will have within the organization.</li><li><strong>Communicating the value of design:</strong> Good design has been proven to have a significant impact on business success and yet is still now well understood by business leaders. Communicating your work&#39;s value or impact has become a necessity for designers.</li><li><strong>Storytelling:</strong> Communicating your approach or rationalizing your work by highlighting the problems you are solving in a compelling way will have a big impact on the level of buy-in you will see.</li></ul><h4><strong>Collaboration</strong></h4><p>Nobody likes to work with an ego. Learning to work with others is a huge part of being a good designer. Designers will experience more success in a role if they learn to check their ego at the door and create trust with their team members and empathy for their colleagues.</p><ul><li><strong>Co-creation:</strong> Co-creation is the practice of collaborating with other disciplines or stakeholders. It’s a great way to capture diverse points of view to guide the design process. When you involve others in your design process, they feel they are part of the solution, they become champions of the work, and they’re less likely to create barriers to implementation.</li><li><strong>Connection:</strong> Designers who make a conscious effort to connect and meet with people outside of their immediate team will create opportunities to have more impact in the organization. Learning about other departments, people, and disciplines, to understand their challenges and goals. Talking to them about your skills, approach, and goals will provide a foundation for collaboration across the organization and help break down silos.</li></ul><h4><strong>Curiosity</strong></h4><p>Curiosity is such a valuable skill for problem-solving that frequently gets overlooked. It manifests in several ways: curiosity about the people you are designing for, curiosity about the business goals, and curiosity about the industry or environment that your work will be consumed within. Having this broad understanding will help shape your design solutions.</p><ul><li><strong>Empathize:</strong> Creating empathy with the people you are designing for, and learning about their needs will ensure the success of your solutions.</li></ul><h4><strong>Creative Play</strong></h4><p>Don’t be afraid to be playful, experiment, and explore — the design process is iterative and relies on exploration and learning from mistakes. Focus on making concepts tangible by creating artifacts or stimuli (physical, visual, narrative) to help articulate your ideas. Be open to feedback and iterate to refine it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7ec5e1618f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A quick guide to running research interviews]]></title>
            <link>https://medium.com/@JeniferBulcock/a-quick-guide-to-running-research-interviews-92802c95d7b4?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/92802c95d7b4</guid>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 16:57:19 GMT</pubDate>
            <atom:updated>2023-02-01T16:21:44.378Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Two women in conversation, sitting at a table." src="https://cdn-images-1.medium.com/max/1024/1*sxPiRMAMs8-UO4PfAo1mKA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@wocintechchat?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Christina @ wocintechchat.com</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Interviews are a valuable way to develop empathy; they help you learn about the situational context, mindsets, motivations, and behaviors of the people you are designing for. Interviewing was my introduction to user research, and over the years I’ve developed this list of guidelines to help others with their practice.</p><p><strong><em>Who is this guide for? </em></strong><em>Anyone looking to fine-tune their research skills: Product managers, Researchers, Designers.</em></p><ol><li>Be curious</li><li>Craft the discussion</li><li>Run the interview</li><li>Debrief</li></ol><h3>Be curious</h3><p>Firstly, take a moment to reorient your thinking, this is your time to be curious and open. You don’t have pressure to come up with ideas or solve problems, you just need to listen and observe.</p><p>This is the time to let your interview participants be the star of the show. In this conversation you are not the expert, they are. Avoid making assumptions, remember, you don’t know what you don’t know. Instead, ask open-ended questions that let the participant give you anecdotal evidence and bring you into their world. A good way to keep yourself in check is to document your assumptions and return to follow up later in the interview.</p><h3>Avoid bias</h3><p>There are many different kinds of biases to be aware of while you’re conducting interviews. Some biases are harder to spot than others, but it is important to have an understanding of them to limit bias in your interview questions as well as any tertiary questions that may come up through your users’ answers.</p><p><strong>Avoid leading questions<br></strong>Participants could presume there is a response you are looking to hear rather than being open to hearing their personal response.</p><p>Instead of this: “Was your experience with <em>Company A</em> good?” <br>Do this: “Can you tell me about your experience with Company A?”</p><p>Instead of this: “Do you eat apples because they are healthy?”<br>Do this: “Why do you choose to eat apples?”</p><p><strong>Start broad and then narrow in<br></strong>Ordering questions in the discussion guide incorrectly can also generate bias. For example, if you narrow in too early, you are at risk of missing all the context that may have influenced the situation or hearing about what is truly important to your participant.</p><p><strong>Understand interviewer bias<br></strong>Interviewer bias takes many different forms. Sometimes it’s assuming what your participant will say, and cutting them off before they’ve had the chance to provide more detail. Other times it can be simply changing your tone or reacting noticeably to something they’ve said. These subtle queues can indicate that their response was desirable or undesirable which can influence how they choose to respond to the question.</p><p><strong>Remain neutral<br></strong>Be careful not to conduct your synthesis with preconceived notions. Looking for particular patterns rather than finding patterns within the data you have is a form of <em>confirmation bias</em>.</p><h3>Craft the discussion</h3><p><strong>Identify goals<br></strong>Be clear about what you want to learn. Are you looking for a broad understanding or a deep one? Are you interested in learning about all your users or just a subset? Having clear scope and goals will help you craft a research study that will ensure you are getting the insights you need.</p><p><strong>Build the guide<br></strong>The guide is not a survey, a good guide helps you stay on topic but shouldn’t be used to dictate a rigid conversation. It’s important to give the participant breathing room to share stories about what’s important to them, remember you don’t know what you don’t know. This might mean that you cover the topics in your discussion guide out of order — and that’s ok. It’s your job to keep track of what you’ve covered and what you haven’t and redirect the conversation when necessary.</p><p><strong>Be respectful of the participant’s time<br></strong>Generally, it&#39;s good practice to run an interview for 45–60mins. This is ample time to have a valuable conversation, but not too long for the participant to lose interest. A guide that’s about 2 pages should generate a 45–60min interview.</p><p><strong>Use appropriate language<br></strong>If speaking to external customers, avoid using internal language that may not be familiar to them.</p><p><strong>Ask open-ended questions<br></strong>These promote storytelling and get to the “why” behind a situation/behavior/emotion.</p><ul><li>“In as much detail as you can, tell me about your experience with x..?”</li><li>“Was there anything that you found particularly frustrating?”</li></ul><p><strong>Probe for the underlying motivation<br></strong>Qualitative research is about understanding the person, and their underlying thoughts, beliefs, and motivations. I have a few phrases I use to help tease this out of people.</p><ul><li>“Why did you use that phrase?”</li><li>“Can you tell me more about that?”</li><li>“Can you give me an example?”</li></ul><h3>Run the interview</h3><p><strong>Don’t crowd the participant<br></strong>My rule of thumb for an in-person interview is 3 people. 1 interviewer, 1 note taker (research support), and the participant.</p><p>These days with remote work it’s a little easier to expand this group. For online, remote interviews it’s easier to bring more people into the process, which has the added bonus of building awareness and advocacy for research insights. However, there are some ground rules. Keep the invite list small. To help keep the participant focused on the interviewer, only the participant and interviewer should have their cameras on, any guests should remain on mute with their cameras off. Set expectations with guests that they will have a few minutes at the end of the interview to ask any pressing follow-up questions — this ensures that the guests feel included but don’t interrupt during the interview.</p><p><strong>If possible, delegate a separate person as a note taker<br></strong>This will free you up to focus on the interview and help bring others into the interview process, building advocacy for the findings.</p><p><strong>Set expectations<br></strong>Introduce yourself to the participant, mention anyone else who will be listening to the conversation, and indicate the broad/high-level topic(s) you’ll be covering in the conversation (but be careful not to share your hypothesis as this could skew the interview).</p><p><strong>Ask permission to record<br></strong>Explain that recordings won’t be shared publicly, and findings will be anonymized before being shared back to the organization.</p><p><strong>Build rapport<br></strong>Taking 5 minutes to ask your user some conversational questions about themselves, their day, and what they like to do in their free time makes them feel more comfortable and puts them into the mindset of answering questions about themselves. It also has the added bonus of building a little extra context for the interview.</p><p><strong>Facilitate the conversation<br></strong>Keep an eye on the original goals of the study. Are you covering the topics you need to? Be prepared to bring the participant back to the key topics if the conversation drifts into areas that aren’t related to your goals. Here are some phrases you can use to guide the conversation:</p><ul><li>“Thanks so much for this detail, I wanted to jump back to something you said earlier.”</li><li>“I’m also curious to learn about x.”</li></ul><p><strong>Silence is ok<br></strong>Don’t be afraid to take a pause. People generally feel the need to fill the pause in a conversation. Pauses are a technique used by researchers, that invites the participant to open up and provide more information.</p><p><strong>Never correct the participant<br></strong>Remember in this context they are the expert and correcting them can erode rapport. If you find that they are misinterpreting something, that’s something to take note of, it might indicate a lack of clarity in the product or experience.</p><p><strong>Wrap up<br></strong>Once I’m comfortable I’ve covered all by key topic areas. I always ask the participant if they have any final thoughts or comments, or if there is anything that we didn’t cover that they want to share. Sometimes participants will take this one final opportunity to reaffirm what’s really important to them or share something that they hadn’t been aware of earlier.</p><h3>Debrief</h3><p><strong>Key takeaways<br></strong>As soon as possible following the interview, it&#39;s good practice to gather the team and run a quick debrief. Use this time to clarify what was heard, and align on key takeaways. Jotting these down after the interview will help with synthesis later, and act as a quick summary for anyone who wasn’t able to attend the interview themselves.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92802c95d7b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From pixels to people: How I made the career transition from design to research]]></title>
            <link>https://medium.com/@JeniferBulcock/from-pixels-to-people-837502201538?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/837502201538</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[career-paths]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Sat, 29 Jan 2022 00:10:56 GMT</pubDate>
            <atom:updated>2023-01-31T22:13:16.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Two women sitting at a table talking to each other" src="https://cdn-images-1.medium.com/max/1024/1*fawp0hHQAlmyVSieSVFiGA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mapbox?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mapbox</a> on <a href="https://unsplash.com/s/photos/interview?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><em>It’s not uncommon for me to hear that people are looking for a career change. Whether it be transferring to design from a non-design-related discipline, or from one design discipline to another. I feel very fortunate to have made the move from UX designer to researcher and hope my story will help others feel inspired and empowered to do the same.</em></p><h4><strong>In the beginning</strong></h4><p>I can still remember the moment when it happened…</p><p>I was a UI designer, working on a multi-pod team, building an employee experience tool for a global tech company. The team consisted of several embedded UX, UI, Engineering, and User Testing people, all of which were headed up by a product person.</p><p>Product direction/decisions were communicated top-down, with little context or communication of long-term vision. I remember feeling like I wasn’t getting the full picture… “why was that decision made? Where did this idea come from? Why are they insisting on solving it that way?” My curiosity was getting the better of me and I found myself thinking about the “why” more than the “how”.</p><p>It wasn’t long before I realized I couldn’t in all honesty work on a team where I wasn’t involved in shaping the product definition, and I ultimately started making career decisions that exposed me to companies that had a strategic approach to design.</p><p>Fast forward a couple of years and I found myself in a strategic experience design consultancy that took a research-led approach to solve complex design problems.</p><figure><img alt="Collection of books about research" src="https://cdn-images-1.medium.com/max/1024/1*VN1_RZHzOaNjxpTf2I03Bg.jpeg" /><figcaption><a href="https://rosenfeldmedia.com/">Rosenfeld Media</a> has some wonderful books about research.</figcaption></figure><h4><strong>Getting the skills</strong></h4><p>I was excited to finally be in a position where I could expand my skill set, now I just needed the opportunity.</p><p>I communicated my intention very early on, and remember showing interest in research and workshops that my colleagues were running. It wasn’t long before the studio had a large research project — and I was included as a team member. My first research project.</p><p>It was equally energizing and exhausting, but one thing was clear — I had found a new area of design that I enjoyed and I was good at.</p><p>A few years in consulting, exposure to some great mentors, and self-education solidified my foundation as a strategic designer. I was learning research techniques, understanding how insights translated into design decisions, running workshops to facilitate C-suite alignment, and making it all come to life with prototypes. I was creating lasting business impact through large-scale, complex service design initiatives, and falling more and more in love with the human-centered design process. I had found the answer to my earlier career question: “how are product decisions made?”.</p><p>Design for me was no longer confined to making, it was about confidently defining the strategic direction and creating value for real people.</p><h4><strong>Gaining recognition</strong></h4><p>I had the skills and experience — there was just one problem. I had not yet held the title of Researcher. The tech world saw me as a designer, with research skills — my goal now was to invert that.</p><p>After taking a design role in a high-growth startup, I set about talking to people. My prior experience in consulting had taught me to learn the business — and so this is what I did. The design org was still very young and the product and engineering organizations were starved for design help. I spent time making connections across the org, speaking to tenured staff, learning about the history of the company and how they were making product decisions today. I treated my first 6 weeks in the role as a research project.</p><p>While I was learning about them, they were also learning about me. I told stories about my design process and why research and discovery were such foundational steps. They were excited.</p><p>This excitement led to opportunities and requests for research. I was proving my skills, changing my brand, and providing value.</p><h4><strong>The payoff</strong></h4><p>Over time I developed a reputation for conducting research, and when the company made the investment to stand up a research discipline, I had laid the foundation to step into a new role.</p><p>Today I’m part of a small yet mighty senior research team for a high-growth fintech startup. I’m helping to define the discipline, establish processes, and deliver insights that are helping define the future of the consumer experience.</p><h4><strong>Principles for making a career change</strong></h4><ol><li><strong>Understand your “why”</strong> — what’s the deeper motivation that guides you.</li><li><strong>Communicate your intention</strong> — ask for what you want, show interest.</li><li><strong>Build the skills </strong>— do the work, find a mentor, self educate.</li><li><strong>Persistence</strong> — It’s going to take time. Having a strong “why” will help keep you focused.</li><li><strong>Change your brand</strong> — promote your capabilities, prove your skills and keep learning.</li></ol><h4><strong>Appendix</strong></h4><p><strong>Resources for budding researchers</strong></p><p>A comprehensive list of books, podcasts, tools, and thought leaders to follow, curated by the community (and me).</p><p><a href="https://www.research.joinlearners.com/">https://www.research.joinlearners.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=837502201538" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What it's like to work with me]]></title>
            <link>https://medium.com/@JeniferBulcock/what-its-like-to-work-with-me-8024246fbfa8?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8024246fbfa8</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Wed, 08 Dec 2021 04:49:55 GMT</pubDate>
            <atom:updated>2021-12-08T04:49:55.456Z</atom:updated>
            <content:encoded><![CDATA[<p>Inspired by <a href="https://lg.substack.com/p/the-looking-glass-a-user-guide-to">Julie Zhuo</a>, I wrote this guide for recruiters, hiring managers, and current and future colleagues, as a quick-start guide to working with me.</p><h3>How I view success</h3><ul><li><strong>Impact.</strong> Being good at my job means that I’m recommending research-led, design decisions, which affect business success.</li><li><strong>Business partnership.</strong> When design has a seat at the business table and is utilized as a strategic partner for decision making and product strategy.</li><li><strong>Healthy culture.</strong> Being good at my job means that my team’s culture is happy, healthy, collaborative, supportive, and always striving for better.</li><li><strong>Constant learning.</strong> Success is constantly learning, and applying those learnings. This could take many forms… from learning a new skill, workshop technique, industry, or leadership skill.</li><li><strong>Shared.</strong> Success should be shared. Products aren’t built in silos or by individuals.</li></ul><h3>How I communicate</h3><ul><li><strong>Australianisms usually slip through.</strong> (and my accent can confuse some). If you think I’m speaking another language, I may very well be. Please jump in and ask for clarity. This also helps me rephrase for future conversations.</li><li><strong>Purposeful.</strong> I’ve been told I have a very deliberate and purposeful way of framing my thoughts. This can result in my taking pauses in my verbal communication to find the right phrases.</li><li><strong>I steer away from dictating.</strong> When giving feedback I always frame it in terms of asking if the goal is being met, as a way to guide my team towards a solution, rather than dictating the outcome.</li><li><strong>I’m rarely blunt</strong>. My general approach is to nudge, but if I see that the nudging is too subtle and you heading down the wrong path or holding onto a solution idea that has too many holes, I will tell you… and work with you to create a better solution.</li><li><strong>Articulating design decisions.</strong> I make a point of outlining the goal, recapping research findings, and/or describing the landscape of the work, before diving into presenting at a critique. I do this to make sure everyone has the best foundational knowledge to be able to accurately assess the work and provide informed feedback.</li></ul><h3>Things I do that may annoy you</h3><ul><li><strong>Systems thinker.</strong> I’m no stranger to navigating ambiguity and am very deliberate and thorough in my approach. This means that I may take some time to formulate a recommendation. I strive to make decisions based on insight — and this takes time. This also means that if I’ve constructed a speculative point of view, I will call it out as such.</li><li><strong>I jump in with questions.</strong> I have a habit of jumping in during team presentations to ask clarifying questions. If we are talking through an idea and you don’t want to be interrupted until the end — let me know so that I can make notes for questions to come follow up with.</li><li><strong>Protected focus time.</strong> Having experience as a team of one, and supporting multiple areas of a product, I’ve experienced my fair share of context switching. I learned the hard way that context switching (especially in these remote work times) is such a disruption, mentally exhausting, and doesn’t produce great work. Instead, I aim to plan and scope projects and sequence according to business priority</li><li><strong>Idealistic.</strong> I tend to think of solutions that have strong experiential ideals first. This can mean that they need to be cut down to size to meet engineering or technical capabilities. This can be frustrating for engineers that need a solution they can build in a week — but for me, this is the first step towards collaborative problem-solving.</li></ul><h3>What gains and loses my trust</h3><ul><li><strong>Be a team player.</strong> The easiest way to gain my trust is to participate in team meetings/critiques. Offer a point of view, don’t be afraid of “being wrong”, share what you’ve learned.</li><li><strong>My</strong> <strong>moral compass.</strong> Not being truthful, not treating people with respect, or with professionalism, are no-nos in my books. Courtesy and respect are great foundations for building trust.</li><li><strong>Credit where credit is due.</strong> I don’t respond well to egos. If someone has done a good job — give them credit, it will help paint you in a positive light in my books as well. Conversely, if you are happy with my performance, tell me.</li><li><strong>Ask for help when you need it.</strong> Self-awareness goes a long way. There is no shame in admitting you aren’t sure about something or don’t know how to do something. If this is something I can help you with, I will — or I will help you find someone who can.</li><li><strong>Be transparent.</strong> Oversharing is a good general rule, and it’s my goal to do this with you too. The more we communicate with each other the better. Working in a silo, only coming up for air when you have something beautiful to show isn’t the best way to solve problems or build products.</li></ul><h3>My strengths</h3><ul><li><strong>A relentless believer in the design process.</strong> I’m a huge advocate for the double diamond process. It’s my firm belief that this approach yields solutions that differentiate business offerings by meeting and exceeding customer needs. There is a common miss conception that this process takes too long. However, I’ve found ways to conduct this process based on time and resource constraints, to mitigate risk, and ensure the best possible outcome.</li><li><strong>Seeing the big picture and acting on it.</strong> I enjoy complexity, and find myself solving problems beyond just what’s in front of me. I’m a systems thinker and enjoy developing a point of view for the big picture.</li><li><strong>Building inclusive culture.</strong> I’ve been lucky to have some great mentors who truly valued inclusive culture. By this, I mean that they found ways to facilitate how the team might co-create the culture themselves. Through this approach I’ve witnessed, happier, healthier people, who produced better work. I’ve adopted this approach too. My leadership style is that of a facilitator and coach, where I let the team tell me what they need rather than telling them how it’s going to be.</li><li><strong>Mentoring and teaching.</strong> I get a lot of enjoyment from seeing others grow. I see it as a success when I’ve worked with you to develop a new skill and you’ve grown to a point where you no longer need support with that skill. Conversely, if there is something I think you could mentor me with, I’ll reach out to you for coaching.</li><li><strong>Patients and persistence.</strong> Over the past few years, I’ve been involved in some large digital transformation projects. These usually involve organizational cultural change — this takes time and persistence.</li></ul><h3>My growth areas</h3><ul><li><strong>Continuous learning.</strong> I don’t feel like my learning of design tools, methods, and practices will ever stop — this is what keeps things interesting.</li><li><strong>Quantitative research techniques.</strong> As a qualitative researcher, I’m looking to develop my quantitative research skill set.</li><li><strong>Thought leadership.</strong> I’m currently working on building my conference presentation skills. I have a couple of talk ideas I’m working on if you’d like to hear more.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8024246fbfa8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Leadership Starter Guide]]></title>
            <link>https://uxdesign.cc/design-leadership-starter-guide-2cb70fb53359?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cb70fb53359</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Sun, 30 Aug 2020 22:45:15 GMT</pubDate>
            <atom:updated>2020-10-07T23:35:05.187Z</atom:updated>
            <content:encoded><![CDATA[<h4>A lightweight resource for designers who are new or aspiring leaders.</h4><figure><img alt="Image: A group of chess pieces illustrates leaders standing apart from the crowd." src="https://cdn-images-1.medium.com/max/1024/1*dGxL8kAMIJBEaLEsPsHfzQ.jpeg" /><figcaption>Markus Spiske on Unsplash</figcaption></figure><p>Leadership skills are often overlooked when hiring or promoting designers into leadership roles. We go to college for hard skills, but so often it’s the soft skills that make us successful in our careers.</p><p>I’ve written this article to help designers who are new or aspiring leaders, understand what leadership looks like, and what things they can do now to either refine their approach or develop skills to set them up for future leadership roles.</p><p>This article has been influenced by my career experiences, and an IxDA NYC panel discussion I moderated in May 2020 with design leaders: Radhika Nayak; SVP of Product at Kinesso, Michele Tepper; Senior Design Manager at Salesforce, and Donna Lichaw; Independent Leadership and Executive Coach. The event recording can be found <a href="https://www.ixdanyc.org/journal/2020/5/27/event-reflection-lets-take-this-online">here</a>.</p><ol><li><strong>Start where you are.</strong></li><li><strong>Create a healthy culture.</strong></li><li><strong>Build relationships.</strong></li><li><strong>Focus on communication.</strong></li><li><strong>Be selfless.</strong></li></ol><h3>Start where you are</h3><p>Leading is such a nuanced and valuable skill, and yet they don’t teach you this in design school. Too often designers are promoted into leadership roles because they have outgrown the corporate structure at the individual contributor level. But being a good design practitioner doesn’t always equal a good leader.</p><p>Leadership is a different skill-set and can lead to a different career path. If you think you’d like to explore the leadership track in your career, a great way to explore the role is to start where you are. There are many things you could do in your current position to start growing these skills and bring more awareness to your leadership goals. Michele Tepper specifically calls out that designers who are looking to make this move can “take a step back and look for ways to grow the team culture.”</p><p><strong>How to get there</strong></p><ul><li>Mentor junior designers. As a leader create opportunities for your team to mentor new designers to the team. As an IC use mentoring relationships to build up skills giving constructive feedback and setting direction without being the one executing.</li><li>Volunteer for new opportunities. Gain more visibility within the business by offering your time and skills to areas that interest you.</li><li>Speak-up. Ask questions or offer your point of view in meetings. Showing interest in how your work impacts the business or fits with other initiatives will arm you with more information that will allow you to start making more strategic decisions.</li><li>Look for ways to grow the team culture. The easiest way to do this is to think about rituals or processes that you enjoyed in other companies and suggest them to your new team. For example, cross-team critiques or team self-initiated design sprints to get them out of the day-to-day and get people working together that normally wouldn’t.</li></ul><h3>Create a healthy culture</h3><p>Culture is probably the most important aspect that influences people’s experience at work. A healthy culture can help employees feel valued, respected, and supported when bringing their ideas forward. All this contributes to better work outputs and more efficient ways of working. Think back to a time when you were unhappy at work, how long did it take you to do simple tasks versus when you were in a healthier work culture — big difference right?</p><p>Donna Lichaw says, “culture is reflected by its managers” which explains why “people don’t leave bad jobs, they leave bad managers”. She also explains that culture is best built (and maintained) in person, which is why even for fully remote teams its important to “get people together for social interaction about once a quarter”, Radhika Nayak suggests. For fully remote teams where physical interaction may not be possible, consider 30 mins every week or two just for social time.</p><p>On the flip side, some companies don’t have a strong culture, which Radhika explains can sometimes create an environment where its easier to define one.</p><p><strong>How to get there</strong></p><ul><li>If you’re in a company that you suspect doesn’t have a great culture, focus on what you can affect, not what you can’t — start small.</li><li>Carve out social time for teams to get to know each other outside the work environment. Organize quarterly in-person socials or regular online social time to build, and maintain team culture.</li><li>If in-person socials aren’t possible to create rituals to help build culture by bringing people together to discuss both work and non-work related topics.</li></ul><h3>Build relationships</h3><p>Building strong relationships at work will help you create impact; increase the success of your projects and your team.</p><p>At a team level, Michele Tepper talks about how to help the team bond. She suggests that we should look for ways to “share a bit of everyone’s personalities to break the ice, and build relationships”.</p><p>Similarly, Donna suggests deepening the relationships within your team by “deliberately creating psychological safety — let people know they can share with you, model the behavior with them that you would like to see, and ask if there are ways you can help them”.</p><p>At an organizational level, Donna also advocates for the practice of building alliances to improve the level of impact you and your team can have. She advises that this is a very conscious effort and can be achieved through the following approaches: scheduled 1:1s, create casual loop-ins, maintain a constant flow of information, finding ways for people of all levels to meet, and over-communicate / overshare to create transparency and visibility. However, she caveats the over-communication suggestion by acknowledging that this intention needs to be set from above.</p><p><strong>How to get there</strong></p><ul><li>Build relationships across the business. Strong relationships with PMs, technology, business stakeholders, and your manager will help you create more opportunities for yourself and your team.</li><li>Build close-knit connections with your team. Get to know them on a more personal level.</li><li>Build trust by building psychological safety. The most effective way to do this is by modeling this behavior yourself because it starts to breakdown barriers between boss and subordinate relationships.</li><li>Breakdown hierarchies. Encourage people of all levels to meet.</li><li>Share often. Create mechanisms for you (and your team) to share insights into respective projects easily and often. This casual stream of information will help your team’s efforts gain visibility by the organization.</li></ul><h3>Focus on communication</h3><p>Communication is such a huge part of working with others, especially via various digital channels. Communication habits can vary dramatically by channel, especially in digital work environments. It can be easy to slip into the habits of poor grammar, jargon, and abbreviations.</p><p>This can lead to miss-communications and even contribute to alienating people. Michele makes a point about this explicitly and suggests when communicating via written word that we “take the time to be human”, and “be aware that the tone of communication is very important”.</p><p>Similarly, Donna talks about the pitfalls of tools like slack, calling out: death by pings, and games of telephone. She encourages everyone to consider the right communication channel for the task. “If you’re starting to write a direct message and it’s getting long, consider if it should be a quick call. The same goes for slack threads, if the topic is getting lost, “consider a call”.</p><p>Radhika had some great tips about choosing the right communication channel when giving feedback. She advises that “giving feedback should always be done face to face”. It helps ensure that your message is landing the way you intended.</p><p><strong>How to get there</strong></p><ul><li>Consider the right communication channel for the job. Giving feedback should always be done face to face, and if things are getting lost in translation via chat tools — suggest a phone call.</li><li>Be conscious of tone and language when constructing written communication. Spend the time to use human, conversational language, and avoid overly abbreviated, short-form sentences.</li></ul><h3>Be selfless</h3><p>Mentoring, creating opportunities, and elevating others is a critical part of leading that doesn’t happen often enough.</p><p>Mentoring happens in many ways. Too often I see leaders miss the opportunity to grow someone’s skills in an area of interest because they are delegating work based on what the team member ‘can do’ rather than what they ‘want to do’. Luckily I’ve had the benefit of working with leaders who see the potential in someone, sometimes beyond what their job description might say, and then actively put people in positions where they will grow and gain the experiences they are looking for.</p><p>A good leader is defined by the success of their team. Shining light on your team’s efforts within the company will lead to bigger, and better projects for the whole team. Elevating your team’s efforts will also improve their sense of job satisfaction, build respect for you as a leader, and help create healthy team morale.</p><p>Radhika has some great feedback for leaders who are mentoring a team member into a leadership role (but this is great all-round advice for facilitating a healthy mentor, mentee relationship). She says “remember that people can lead in different ways. Try asking for outcomes and let them navigate there”.</p><p><strong>How to get there</strong></p><ul><li>Empower your team by providing them with opportunities that are in line with their respective goals.</li><li>Find moments to connect people within the company and shine a light on your team.</li><li>Avoid dictating solutions and instead set clear goals, intentions, and outcomes and let the team members explore how to get there.</li></ul><p>Try bringing these practices to your day-to-day. No matter what level you are or where you sit within the organization, its possible to affect positive change — for yourself, for your team or at an organizational level. Start where you are and focus on affecting the things you can. Do this by focusing on creating a healthy culture, building relationships, focusing on communication and when appropriate, be selfless and shine a light on your team.</p><p>A special thank you again to the panelists for their valuable insights.</p><p><strong>Donna Lichaw</strong> @dlichaw<br>Independent Leadership and Executive Coach</p><p><strong>Michele Tepper</strong> @michelet<br>Senior Design Manager at Salesforce</p><p><strong>Radhika Nayak</strong> @radhikanayak<br>SVP of Product at Kinesso</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*dTQ3wCPk0r47JtKG" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cb70fb53359" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-leadership-starter-guide-2cb70fb53359">Design Leadership Starter Guide</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[My team rules]]></title>
            <link>https://medium.com/@JeniferBulcock/my-team-rules-32d01a2cddf3?source=rss-6c487187cd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/32d01a2cddf3</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Jenifer Bulcock]]></dc:creator>
            <pubDate>Wed, 13 Nov 2019 04:07:36 GMT</pubDate>
            <atom:updated>2019-11-13T04:07:36.927Z</atom:updated>
            <content:encoded><![CDATA[<p>When working with a new team, the forming, storming and norming process can hinder collaboration and team alignment. The guidelines below I developed from my experience working with varied multidisciplinary teams over the years.</p><h3>Always have each others’ back</h3><p>Facilitate a united team dynamic. Be sure to raise concerns, new ideas, successes or roadblocks to the collective team. During team, design critiques focus on providing clear, constructive, actionable feedback. Offer to lend a helping hand if you have availability.</p><h3>Respect your teammates</h3><p>There is more than one way to skin a cat — everyone has been hired for particular skill sets, background, and experience. Value that you all have different strengths, weaknesses, ways of working.</p><h3>Create a safe space</h3><p>Provide a platform for everyone to have a say. A team has many voices, don’t let the loudest drown them out.</p><p>It’s ok if you’re unsure, better to ask for help than feel like you are letting the team down. Put your hand up if you need help.</p><h3>Always assume positive intent</h3><p>Recognize that everyone is doing what they think they need to, to do a good job and help the team/project move forward.</p><h3>Set clear expectations</h3><p>As a team, align on daily activities/standups and office working hours. Ensure project dates are clearly communicated and accessible throughout the duration of the program in a format that works for the team.</p><h3>LoE (Level of Effort)</h3><p>As a team, align on appropriate effort/design assets to communicate design solutions to your client/stakeholder. Keep a running list of agreed on tasks/deliverables, and their due date to keep everyone on the same page.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32d01a2cddf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>