<?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 Raschin Fatemi on Medium]]></title>
        <description><![CDATA[Stories by Raschin Fatemi on Medium]]></description>
        <link>https://medium.com/@purplebulldozer?source=rss-b624be66b49d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1ohHKT2SrTNwJVeNTuRFJg.png</url>
            <title>Stories by Raschin Fatemi on Medium</title>
            <link>https://medium.com/@purplebulldozer?source=rss-b624be66b49d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:39:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@purplebulldozer/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[How to use mixed method research to drive product decisions]]></title>
            <link>https://purplebulldozer.medium.com/how-to-use-mixed-method-research-to-drive-product-decisions-7ff023e5b107?source=rss-b624be66b49d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ff023e5b107</guid>
            <category><![CDATA[mixed-methods-research]]></category>
            <category><![CDATA[ux-research-method]]></category>
            <category><![CDATA[data-driven-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Raschin Fatemi]]></dc:creator>
            <pubDate>Thu, 09 Jun 2022 13:34:54 GMT</pubDate>
            <atom:updated>2022-06-09T13:34:54.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Illustration of a pie chart. There are 5 pieces to the pie. One of the pieces is cursor. The illustration uses a pink and purple color palette." src="https://cdn-images-1.medium.com/max/1024/1*mC2mL7vavRi9wZtWvQZlTg.png" /><figcaption>Illustration by Alisha Giroux.</figcaption></figure><h4>A research framework for using data and cross-validation to reduce bias and drive action</h4><p>As designers and researchers, understanding our users is core to building the right things, and guiding the design direction we take. Knowing which research direction to take is a challenge in itself. Starting with user feedback is an obvious first step. But how do you gather enough feedback to provide an accurate picture? How can you avoid high-cost interviews, reduce feedback bias, and select the most appropriate research method?</p><p>This is where a mixed-method research approach can be impactful.</p><p>A few months ago, Shopify’s Customer team shipped <a href="https://www.shopify.com/segmentation">customer segments</a> to help merchants engage with their customers more effectively. This new product replaced the existing <a href="https://help.shopify.com/en/manual/customers">Customers page</a> with more advanced, robust, and flexible capabilities. As a new design lead on the team, I was eager to understand how users feel about the product and what should be our design direction as we advance.</p><p>Our team used mixed methods to design a research framework under these principles:</p><ul><li>gather more data ≠ adding cost</li><li>reduce feedback bias</li><li>drive clear action</li></ul><h4>What is the mixed method?</h4><p>Mix method is about building a community around user research and cross-functional collaboration between UX, data science, support, and product to create a shared understanding of user behavior. This research method offers complementary insights by combining qualitative and quantitative feedback data. The foundation of the <a href="https://www.nngroup.com/articles/triangulation-better-research-results-using-multiple-ux-methods/">Mix method</a> has been around for decades now — with two main components: data richness and cross-validation.</p><ol><li><strong>Data richness:</strong> A rich understanding of user experiences comes from looking at user feedback from multiple data sources. Rather than running different research methods in silos, mixing methods creates a more accurate picture of the experience and mitigates blind spots.</li><li><strong>Cross-validation: </strong>Mix-methods show attitudes and behaviors sometimes diverge, and we can’t measure the product’s success by looking at qualitative or behavioral data alone.</li></ol><p>Comparing results from different methods give us unique complementary signals to understand the behavioral patterns and perceived experience.</p><figure><img alt="An illustration of the feedback pipeline outlined in this article" src="https://cdn-images-1.medium.com/max/1024/1*qCJBGUIGkLALglK637XEwA.png" /><figcaption>Gather diverse data from multiple data sources to find actionable insights.</figcaption></figure><h4>You have more data than you think:</h4><p>Our research framework offers diverse data gathering by employing existing feedback sources:</p><ol><li><strong>Support calls: </strong>A natural place to gather direct feedback is from the support team. For example, the Shopify support team documents all merchant frustration and makes it accessible for everyone. We looked at support calls during the first month of the release as a source to find top merchant frustration on the Customers page.</li><li><strong>Behavioral logs</strong>: Partnering with our data science team, we look at quantitative data and experimentation results to understand the overarching impact of customer segment release on merchant behavior.</li><li><strong>Internal Feedback: </strong>Centralized internal stakeholder feedback with the rest of the feedback data for cross-validation.</li></ol><p>At the same time, we conducted three new research initiatives with the same group of merchants.</p><ol><li><strong>Impression Survey:</strong> we gathered indirect, attitudinal data through a survey with two simple questions. 1) rate your experience, and 2) explain your rating in plain text format. We gathered more than 100 respondents to be reliable based on our survey population size.</li><li><strong>Session recording:</strong> We observed 55 session recordings to find actual navigational patterns through FullStory and what UX pain points stray merchants away from optimal paths.</li><li><strong>1:1 interviews: </strong>we conducted 5 remote interviews to get direct feedback and understand the merchant mental model.</li></ol><figure><img alt="Illustration of a four-quadrant chart. The x axis has why on the left side and what on the right side. The y axis has behavioral at the top and attitudinal at the bottom. The types of data are plotted on the graph." src="https://cdn-images-1.medium.com/max/1024/1*y78DLC2CBK-9M8ZSNJdxVA.png" /><figcaption>Each method provides a different perspective in terms of the questions they answer.</figcaption></figure><h4>Start Guide: run your mix methods research</h4><ol><li><strong>Preparation:</strong></li></ol><ul><li>Determine your research focus: what is prompting you to consider doing user research? Clearly define the research goal and scope.</li><li>Define your research questions and choose research methods: which method elicits information that will allow you to answer your research question best?</li><li>Map research questions to research methods: which method draws out different perspectives? Which will make effective use of time and available resources?</li></ul><p><strong>2. Implementation:</strong></p><ul><li>Build the team: there is a great value in being part of a diverse team and distributing responsibilities among team members. Having different skill sets and perspectives within the team reduces the bias.</li><li>Conduct research: gather data through each research method.</li><li>Document structurally: create data tables or templates to simplify sorting and analyzing data.</li><li>Centralize feedback: organize all data in one place and make it easily accessible for everyone.</li></ul><p><strong>3. Processing and validation:</strong></p><ul><li>Analyze data: Compare, contrast, and combine data findings from various channels.</li><li>Define actions: Form hypotheses, gather stakeholders’ feedback and define improvements.</li><li>Work with product &amp; engineering to prioritize improvements.</li><li>Measure the success of new improvements</li></ul><h4>What did we learn?</h4><p>Before the customer segment launch, we foresaw there would be a learning curve with the new advanced segment creation experience. However, the complementary results showed us that the redesign changed the page’s structure and removed some small, less appreciated elements a lot of loyal users wanted, which upset people about the overall change.</p><ul><li>Our survey used open text to let users tell us their problems and dislikes. The text analysis yielded a breakdown of categories of user problems where small UX changes cause considerable frustrations, which we validate with support calls.</li><li>In session recordings, we observed how often merchants spent scrolling and paginating without finding what they were looking for. We also discovered frustrating interactions with specific filters and how merchants validate the result.</li><li>This finding also correlates with the behavioral data, where we saw a considerable drop between people who started interacting with customer segments and didn’t end the session successfully.</li></ul><p>Looking at all the data makes us confident about what should be our focus and immediate improvement after the release. We took this finding directly to product and engineering to focus on specific things and quickly launch impactful changes. A further study after the improvement release showed people were more satisfied.</p><p>Few examples of improvements we shipped:</p><ol><li><strong>Small details matter:</strong> We learned that the lack of small components like a search bar caused the most frustration for merchants. We made this a top priority and added customer search to the Customers page.</li><li><strong>Increase affordance: </strong>We simplified the segment creation workflow based on the laws of proximity. For example, we moved the save CTA closer to where the merchant creates the segment to increase affordance. The A/B test results show the number of merchants saving segments increased by 180% compared to the previous experience.</li><li><strong>Self-serve filter creation:</strong> We learned merchants who adapted segmentation tools need more filters, so we leveraged customer <a href="https://help.shopify.com/en/manual/metafields">metafields</a> as segmentation filters, enabling merchants to create filters on their own and customize segments further.</li></ol><h4>Conclusion</h4><p>This mixed-method helped us find an actionable and specific case, focusing on particular user reactions and being more prescriptive, rather than investing in behavioral data alone. This method could diagnose the user’s pain points, inform potential prioritization, and assess whether the redesign is more effective.</p><p>It also helps stakeholders understand the big picture of user research. These are not just methods we are using in isolation. Mix method user research is iterative and drives awareness of people’s needs and forces readjusting to improve their experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ff023e5b107" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What we mean by information]]></title>
            <link>https://purplebulldozer.medium.com/what-we-mean-by-information-e19c65b7efe3?source=rss-b624be66b49d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e19c65b7efe3</guid>
            <category><![CDATA[information-gain]]></category>
            <category><![CDATA[user-interface]]></category>
            <dc:creator><![CDATA[Raschin Fatemi]]></dc:creator>
            <pubDate>Tue, 15 Jun 2021 17:25:21 GMT</pubDate>
            <atom:updated>2021-08-25T16:20:28.578Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Big Data High Horse (or Why Most Big Data Projects Fail)</h3><p><em>This post was written in 2015.</em></p><blockquote>— the elementary unit of information — is a difference which makes a difference”. (Gregory Bateson, 1972)</blockquote><p>During the past few years, the emergence of some new technologies in data infrastructure enabled all types of businesses to access, explore, transform and display their web analytics and customer data. It seems that data is the core of any successful business and everyone urges to become data-driven. From healthcare services to e-commerce, businesses start to collect their customer data and measure the impact of every change on customer behavior. These new technologies pouring in a wide stream of data from all intentional and unintentional customer behavior have constantly broadened the possibilities of describing an event. However, the challenge for business users is to <em>select </em>the most useful information piece among a gazillion descriptions that show the root cause of an event with sufficient confidence.</p><p>Data, if used effectively, provide an objective mechanism to evaluate hypotheses about the decision that needs to be made. In Information theory, the <em>effectiveness of knowledge </em>is measured by ‘Information Gain’. In simple words, Information Gain measures how much knowing a piece of information helps us in making the desired decision, or a measure to understand what makes a difference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/232/0*VPGBDDWHJFrNz_qM." /></figure><p>The above formula states that information gain(IG) is defined by the difference in ‘information entropy’ when not knowing(a) versus knowing(a). In other words, information gain shows us the <em>benefit of knowing(a).</em></p><p>To make this more clear let&#39;s look at a business case. Imagine that we are a hospitality firm and our business problem is: <em>The turnaround for preparing a room after checkout is too long.</em></p><p>One of our hypotheses for the root cause of the above problem is: <em>we have too few cleaning staff.</em></p><p>To test our hypothesis we have access to rows and rows of data showing us the size and the number of rooms, the staffing size, the average time of cleaning room, etc. The challenge is to find which data variable is the best predictor for the truthfulness of our hypothesis. For example, Graph 1A shows the comparison of the average time to clean a room with the #of cleaning staff. This report doesn’t contain any information to test our hypothesis, therefore the information gain of Graph 1A is little or zero.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/0*lfiXaFlPOSUH0VYC." /></figure><p>In another graph (1B) we show the same comparison but this time we break down the average time by an hour in a day. This time the report shows us a clue and increases our confidence in our hypothesis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/0*rtknbiEdC7macuDt." /></figure><p>From a product design perspective, we should make sure that our interface allows our business users to measure the information gain of each variable which goes beyond slicing and dicing the data and representing it in different graphical formats.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e19c65b7efe3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for Enterprise workflow: how to find the balance between flexibility & generalization…]]></title>
            <link>https://medium.com/actioniq-tech/designing-for-enterprise-workflow-how-to-find-the-balance-between-flexibility-generalization-ddd7b5bf919a?source=rss-b624be66b49d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddd7b5bf919a</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[enterprise-design]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Raschin Fatemi]]></dc:creator>
            <pubDate>Mon, 16 Dec 2019 19:45:08 GMT</pubDate>
            <atom:updated>2019-12-17T16:59:49.295Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*snXv-gSEpryMmdqOoP1C2g.jpeg" /><figcaption>Parallel universe: tracing New York’s unbuilt history: Paul Rudolph’s 1967 City Corridor proposed a megastructure of connecting buildings that would contain a highway running from the Hudson to the East river</figcaption></figure><h3>Designing for Enterprise workflow: how to find the balance between flexibility &amp; generalization with design patterns</h3><p>Imagine you need a new home — you can either hire an architect and build it yourself or you can find the best match on the market. Let’s compare the two options: if you hire an architect, you can pick any point in the continuous space of possibilities, but it has overhead costs and takes effort to make it from scratch. If you choose the best match in the market, you have a discreet and limited number of options, but it has a lower cost and is ready to live in.</p><h4>Assumption</h4><p>Let’s simplify this situation a little bit and remove the cost and time issue. Assume we are in an ideal world where building a house is not more costly and we can magically build what we want overnight. Would it still make any sense to buy an already built house instead of designing a perfect house for yourself?</p><h4>Challenge</h4><p>To reach perfect results, you need to consider every small detail and unless you’ve had extensive previous experience in building houses before, it will be difficult to know all the requirements and necessary details upfront. Your context is limited based on your own personal experience and you won’t be able to see other possible scenarios that have never happened to you before. You need to make a compromise when there are conflicting details to sort out. So, even without a cost issue, just figuring out what you really need might end up being a big obstacle to designing a building from scratch.</p><h4>Design patterns</h4><p>It is interesting to note that <a href="https://en.wikipedia.org/wiki/Design_pattern">“Design patterns”</a> or “Pattern language”, a widely adopted term in software engineering, was first introduced by the architect Christopher Alexandar.</p><blockquote><em>“Each pattern describes a problem that occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice.” </em>A Pattern Language: Towns, Buildings, Construction 1977 Christopher Alexander</blockquote><p>Alexandar says that an Architect, knowing such problems so well by studying the requirements of many previous clients, is able to define and apply these patterns, creating a house that satisfies the demands of most homebuyers. Assuming there are enough houses in the market designed based on these principles, not only is it more cost-effective to find a house that has been already built, but also there is a good chance that it would be a better match for the homebuyer. Finding a match is a much easier problem to solve as the available options and corresponding details are all available to compare, whereas in the other case building the house requires mapping a vague and idealized image to a concrete and plausible implementation.</p><p>And remember so far we have been talking about an idealized world where we bracketed out all the trouble of building the design.</p><h4>Software Product Design</h4><p>The process of designing software and designing a house are very different: building software is an iterative process whereas building a house is a waterfall process. The software is a living system that needs to be updated very frequently, the house is a fixed installation. When an enterprise company has a need for a new software they are put in the seat of the home buyer: they have an option of either building the software (in-house or have it custom built), or buy one of the solutions that are available in the market. Similarly, the cost and the overhead of developing a complex product in-house is an issue here, but the hardest challenge is the design and product decisions that need to be grounded in knowing the end user’s needs.</p><h4>Enterprise Challenge</h4><p>Enterprise software is by nature a complex product. If you are working as a designer at an enterprise software company, you may find it extremely hard to find recurring problems among your clients. Enterprise workflows are complicated and each are custom to their company-specific culture. These workflows can often be older than the employees’ entire career experiences. Therefore, it’s extremely challenging to make a change when most of the people are adapted to legacy workflows. As a result, enterprise software designers may fall into the trap of designing a solution that is customized to address their client’s unique needs and workflow. As enterprise software companies add additional clients, they will find that their solution cannot adapt to a completely different workflow environment.</p><h4>ActionIQ</h4><p><a href="https://www.actioniq.com/">ActionIQ</a> started 5 years ago, as a b2b enterprise startup to solve the emerging needs of modern marketing. Rather than starting with the typical co-founder duo of an engineer and a salesperson, ActionIQ started with a trio of engineering, product management, and design. Our team was incubated within GILT, a discount luxury e-commerce business, to optimize their client acquisition and retention strategy. This gave us incredible access to observe the day-to-day workflow of its Marketing team and deeply understand their core needs. Rather than building a custom solution for GILT’s unique needs, the makeup of our team allowed us to dissect the client’s problems into abstract components, and identify design patterns that can address each one leading to solutions that can address each component.</p><p>This approach has provided us 2 benefits: First, it provides greater flexibility, allowing users within an enterprise to interact with our software according to their unique workflow and use-cases, thereby maximizing the opportunity for within-company collaboration. Second, it provides us the foundation for addressing a diversity of enterprise needs; and thus the opportunity to scale rapidly without adding complexity.</p><p>To give an example of problem patterns we identified in early days, as a user of our platform (a marketer) wants to identify a unique customer segment based on a series of attributes to launch a targeted marketing campaign (e.g., females between 24–36 that purchased a bag and shoes in the past 2 months but have not purchased anything since then). Identifying this customer segment requires a combination of a complex set of variables (e.g., gender, age, purchase category, purchase period). Using the concept of design patterns, we realized that the targeting process can be governed by a generic set of rules (e.g., suppression, intersection, etc.), which can interact with each other to build the complex logic required for this identification process. Making these composite rules allows the user to seamlessly generate various target segments by cycling through permutations of these rules and the values assigned to each rule. This capability increases the agility of the marketer to launch infinite varieties of targeted marketing campaigns and not have to rely on the vendor to custom-code each of them.</p><p>Designing software has many things in common with designing a house, and in the case of enterprise software more like designing a skyscraper. Similar to the way the architectural design of a house doesn’t only determine the aesthetics, but most importantly defines the spatial possibilities within the physical space for the habitants, design of a software defines the navigational possibilities within the informational space of the software. Using design patterns help users find themselves in a familiar and empowering space.</p><p>This is one example of many complex marketing problems. In today’s fast-paced market environment, while the needs of our clients are constantly evolving, ActionIQ’s commitment to leverage design patterns enables us to rapidly scale and fulfill marketers’ complex needs. As designers, we have a unique opportunity to identify patterns between different problems and design products that empower clients to achieve their goals effectively and efficiently, while constantly iterating our product design to reach better results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/212/1*BHu_XEIpQf6r_KWEUOCSAw.png" /></figure><p>Raschin is the head of design at ActionIQ. She enjoys the abstrusity of turning abstract into palpable and back through design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddd7b5bf919a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/actioniq-tech/designing-for-enterprise-workflow-how-to-find-the-balance-between-flexibility-generalization-ddd7b5bf919a">Designing for Enterprise workflow: how to find the balance between flexibility &amp; generalization…</a> was originally published in <a href="https://medium.com/actioniq-tech">ActionIQ Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>