<?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 Hannah Makabi Daniel on Medium]]></title>
        <description><![CDATA[Stories by Hannah Makabi Daniel on Medium]]></description>
        <link>https://medium.com/@anamakabi?source=rss-889a1ebb55c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*76gm6zuT2ELERcHbZILRMw.jpeg</url>
            <title>Stories by Hannah Makabi Daniel on Medium</title>
            <link>https://medium.com/@anamakabi?source=rss-889a1ebb55c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:42:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anamakabi/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[Watching Someone Use Your Product Is Humbling. Do It Anyway.]]></title>
            <link>https://medium.com/charisol-pulse/watching-someone-use-your-product-is-humbling-do-it-anyway-af675d885d9d?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/af675d885d9d</guid>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Thu, 02 Jul 2026 15:01:02 GMT</pubDate>
            <atom:updated>2026-07-02T15:01:02.722Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><a href="https://maildrip.io/">MailDrip</a> | On Usability Testing, Real Users, and What You Miss When You Skip This Step</blockquote><p>There is a particular feeling you get when you watch someone use a product you’ve been close to for months, and they go somewhere completely unexpected.</p><p>Not wrong. Just unexpected. That moment of <em>“oh, they didn’t see that”</em> or <em>“wait, why did they click there?” </em>that’s usability testing working exactly as it should. And lately, it’s been one of the most grounding parts of my work at <a href="http://maildrip.io/">MailDrip.</a></p><figure><img alt="Magnifying glass zooming in on the words “Usability Test” on a clean, modern background." src="https://cdn-images-1.medium.com/max/1024/1*1fLXS9m5pv8kJX_G8rJkNg.png" /><figcaption><a href="https://chatgpt.com/">Picture From Chatgpt</a></figcaption></figure><h3>We’re Testing Everything, Not Just the New Features</h3><p>When most people think about usability testing, they think about it as something you do before a feature launches. Test it, fix it, ship it. Done.</p><p>But at <a href="http://maildrip.io/">MailDrip</a>, we’ve been running usability tests on both new flows we’re actively building <em>and</em> existing ones already in production. Because the truth is, something being live doesn’t mean it’s working. It just means nobody has sat down and properly watched someone use it yet.</p><p>And when you do? You start finding things. Small friction points, moments of hesitation, and flows that made perfect sense to the team but quietly confuse the person on the other side.</p><h3>Why We’re Tying It Back to Jobs-to-be-Done</h3><p>If you’ve been following this research series, you know we’ve been deep in a Jobs-to-be-Done study, interviewing personas across different user types to understand what they’re actually trying to accomplish on<a href="http://maildrip.io/"> MailDrip</a>.</p><p>Now we’re taking that a step further.</p><p>We’re recruiting participants across those different personas, email marketers, business owners, and community managers, and bringing them in to actually use the platform.</p><blockquote>The goal isn’t just “can they complete this task?” The goal is: <em>can they find their job to be done reflected in this product?</em></blockquote><p>Do they feel like this was built for them? Or does it feel like something they have to figure out? That’s a very different question. And it’s changing what we look for in every session.</p><h3>What We’re Discovering</h3><p>We’re catching things we never would have spotted otherwise.</p><p>Flows that felt intuitive from the inside turn out to have quiet dead ends. Language that made sense to the team reads as confusing to a first-time user. A feature that solves a real job exists on the platform, but users walk right past it because nothing signals that it’s there for them.</p><p>These aren’t failures, they’re findings. And finding them now, before they quietly frustrate hundreds of users, is exactly the point.</p><figure><img alt="Presenting usability insights to the team" src="https://cdn-images-1.medium.com/max/768/1*emp03ZrlGHV0bYrwCuVLTA@2x.jpeg" /><figcaption><a href="https://chatgpt.com/">Picture From Chatgpt</a></figcaption></figure><h3>Tips for Researchers Running Usability Tests</h3><p>If you’re setting up usability testing on your team, here’s what I’d tell you:</p><ol><li><strong>Don’t lead. Not even a little.</strong><br> It is so tempting to help. Someone is hovering over the wrong button, and every instinct in you wants to say, <strong><em>“It’s just over there.”</em></strong> Resist it completely. The moment you guide them, you’ve lost the data. What you’re watching is no longer their experience; it’s yours.</li><li><strong>Give them scenarios, not instructions.</strong><br> Don’t say “click on the campaigns tab and create a new email.” Instead, paint a scenario rooted in their job: <strong><em>“Imagine you just restocked your store and you want to let your customers know. Show me how you’d do that.” </em></strong>Now you’re watching how they actually think, not how well they can follow directions.</li><li><strong>Make them think aloud.</strong><br> Ask participants to narrate as they go — what they’re looking at, what they’re expecting, what’s confusing them. Silence in a usability test is hard to interpret. A running commentary is gold. You start to hear the gap between what the product says and what the user hears.</li><li><strong>Recruit across your personas intentionally.</strong><br> The same flow will land differently depending on who is using it. A community manager and a solo e-commerce founder might navigate the same screen in completely different ways. If you only test with one type of user, you’re only seeing part of the picture.</li></ol><h3>Why This Matters Beyond Research</h3><p>Usability testing isn’t just a research activity. It’s a team alignment tool.</p><p>When product managers, designers, and developers watch real users interact with what they’ve built — something shifts. It stops being abstract feedback in a report and becomes something they’ve seen with their own eyes. The urgency changes. The empathy deepens.</p><p>At <a href="https://maildrip.io/">MailDrip, </a>these sessions are becoming something the whole team cares about, not just research. Because when you see a user struggle with something you built, you don’t need a recommendation document to know it needs to change.</p><h3>The Bottom Line</h3><p>If you want to build something that actually works for the people using it, not just something that technically functions, you have to watch people use it. Regularly. With different types of users. With real scenarios. And with the discipline to stay quiet and let them show you what they see.</p><p>It’s humbling every single time. And every single time, it’s worth it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af675d885d9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/watching-someone-use-your-product-is-humbling-do-it-anyway-af675d885d9d">Watching Someone Use Your Product Is Humbling. Do It Anyway.</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[They Never Asked for a Feature. They Told Us a Job.]]></title>
            <link>https://medium.com/charisol-pulse/they-never-asked-for-a-feature-they-told-us-a-job-98fa909edc8d?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/98fa909edc8d</guid>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Tue, 05 May 2026 14:55:48 GMT</pubDate>
            <atom:updated>2026-05-05T14:55:48.222Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>MailDrip UX Research Series | Part 2: What the Research Is Revealing</blockquote><p>At <a href="https://maildrip.io/">MailDrip</a>, we don’t just build features; we build for people. That means before any decision gets made, we ask who is on the other side of the screen, what they’re trying to get done, and whether we’re actually helping them do it. Research isn’t a step in our process. It’s the foundation of it.</p><p>In Part 1, I walked you through how I set up the Persona Validation and Revenue Potential Study, the secondary research review, the Jobs-to-be-Done framework, and the three-phase research plan I designed. If you haven’t read it yet, start there.</p><blockquote>This is Part 2. And this is where things get interesting.</blockquote><h3>What’s Happening in the Interviews</h3><p>We are currently mid-study, deep in the in-depth interview phase, speaking with 5+ participants across different persona types: email marketers, business owners, community managers, and more. Each session runs 30–45 minutes, conversational rather than checklist-driven.</p><p>The goal is to hear three layers in every story: the functional job (what they need to accomplish), the emotional job (how they want to feel), and the social job (how they want to be perceived by others).</p><figure><img alt="Interview insights from figjam board, personas we validated by speaking to real users" src="https://cdn-images-1.medium.com/max/817/1*8hfzii1r3CRC7jIt8YhURQ.png" /><figcaption>Interview insights</figcaption></figure><h3>The Big Unlock: They’re Not Asking for Features</h3><p>Here’s what strikes me every single time I sit in one of these sessions.</p><p>Users are not saying <em>“I want this feature”</em> or <em>“can you build this?”</em> They are telling us their jobs. They are describing their days, their frustrations, their goals, and buried inside those stories are the exact things we need to build, message, and prioritise.</p><p>One person isn’t thinking about email marketing. They’re thinking: <em>“I need to make sure my community doesn’t go cold between events.”</em> Another isn’t thinking about automation. They’re thinking: <em>“I’m the only one running this business, and I cannot be sending emails manually every week.”</em></p><p>That’s the power of JTBD done properly. You stop hearing feature requests and start hearing real human needs. And then it becomes your job, as a researcher, as a product team, as a growth team, to go back to the drawing board and ask: <em>how does our product meet them at that job?</em></p><h3>It’s Not Just a Product Insight: It’s a Business One</h3><p>What has surprised me most about this research is how far the insights travel beyond the product team.</p><p><strong>For the growth team</strong>, JTBD language is reshaping how we think about messaging. When you know the job a persona is trying to get done, you stop writing generic copy and start speaking directly to their situation. You’re no longer talking at users, you’re talking to them, in the exact language they use to describe their own problems.</p><p><strong>For SEO and content writers</strong>, these interviews are a goldmine. What phrases do users reach for when they describe their jobs? Those are the exact search terms, headlines, and hooks that will resonate. You can’t get that from a keyword tool. You get it from listening.</p><p><strong>For product and strategic decisions</strong>, this research is laying the groundwork for something sustainable. When you build around jobs to be done, you’re not chasing trends or reacting to one-off feedback. You’re building something that can stand the test of time, because the jobs people need to get done don’t change as fast as features do.</p><figure><img alt="team collaboartion" src="https://cdn-images-1.medium.com/max/1024/0*_TQqe0pHHNVhtWwy" /><figcaption>Photo by <a href="https://unsplash.com/@silverkblack?utm_source=medium&amp;utm_medium=referral">Vitaly Gariev</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>One of the Biggest Eye-Openers: Onboarding Is Not One-Size-Fits-All</h3><p>This is something the research is making impossible to ignore.</p><p>Each persona comes to MailDrip carrying a completely different job. And if they arrive at the same generic onboarding experience, we’ve already lost them, not because the product can’t serve them, but because we haven’t shown them <em>how</em> it serves them specifically.</p><p>A community manager and an e-commerce founder might end up using the same features. But the way they need to be introduced to those features, the language that needs to be used, the outcome they need to see first, all of it is different.</p><p><strong>JTBD</strong> is showing us that onboarding isn’t just a product experience. It’s a personalisation problem. And we’re currently working on how to incorporate this jobs-to-be-done language into the platform, so that every persona feels seen from the moment they arrive.</p><h3>What This Means for Researchers</h3><p>If you take nothing else from this series, take this.</p><p><strong>Talk to your users.</strong> Not once. Not at the start of a project and never again. Regularly, intentionally, with real curiosity. There is no shortcut that replaces a genuine conversation with the person you are building for.</p><p><strong>Don’t make the mistake of assuming a product is for everybody.</strong> The moment you say “everyone can use this,” you’ve started building for no one in particular. When you talk to users and understand their jobs, you find your people, the ones who need what you’re building badly enough to stay, to pay attention, to come back.</p><p><strong>And when you use frameworks like JTBD, use them properly.</strong> Don’t skim the surface. Sit in the discomfort of not knowing, ask the questions that feel too simple, and listen for what’s underneath the answer. That’s where the insight lives.</p><h3>A Closing Thought</h3><blockquote>“If you want to build something sustainable , something that last, understand your users’ jobs to be done. Speak to them in a language they recognise. So that when they see their job reflected in a feature, they know without a doubt: this was built for me.”</blockquote><p>I’ll be closing this series here. From this research, we understand that <a href="https://maildrip.io/">MailDrip</a> is a powerful tool. We have a feature for each persona. We just need to refine our flows to reflect the real jobs to be done, then onboard each persona using those features. Stay with us and follow along. If you’re an email marketer, business owner, community manager, ecommerce seller, or digital creator, you name it.</p><p><a href="https://maildrip.io/">MailDrip</a> is the junction for you. Whether you want landing pages, opt-in pages, templates, or AI to speed things up, it’s there. Why not check us out today?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98fa909edc8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/they-never-asked-for-a-feature-they-told-us-a-job-98fa909edc8d">They Never Asked for a Feature. They Told Us a Job.</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[     .]]></title>
            <link>https://medium.com/@anamakabi/-dfc3c3b6bbf5?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfc3c3b6bbf5</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Sun, 03 May 2026 17:10:15 GMT</pubDate>
            <atom:updated>2026-05-03T17:10:15.046Z</atom:updated>
            <content:encoded><![CDATA[<h2>𝗔𝗜 𝗶𝘀 𝗻𝗼𝘁 𝗿𝗲𝗽𝗹𝗮𝗰𝗶𝗻𝗴 𝗨𝗫 𝗥𝗲𝘀𝗲𝗮𝗿𝗰𝗵𝗲𝗿𝘀. 𝗕𝘂𝘁 𝗿𝗲𝘀𝗲𝗮𝗿𝗰𝗵𝗲𝗿𝘀 𝘄𝗵𝗼 𝘂𝘀𝗲 𝗔𝗜 𝘄𝗶𝗹𝗹 𝗿𝗲𝗽𝗹𝗮𝗰𝗲 𝘁𝗵𝗼𝘀𝗲 𝘄𝗵𝗼 𝗱𝗼𝗻’𝘁. 𝗛𝗲𝗿𝗲 𝗶𝘀 𝘄𝗵𝗮𝘁 𝗜 𝗺𝗲𝗮𝗻…</h2><p>For the longest time, research meant opening ten tabs, jumping between articles, cross-referencing everything, and spending days just trying to gather enough to move forward.</p><blockquote>Then I started using AI.</blockquote><p>Not because I was told to. Not because it was trending. But because I was curious, and honestly a little skeptical, like most people.</p><p>And that skepticism? I get it. Every time something new shows up in tech, the first reaction is fear. Fear that it will replace you, complicate things, or just be another tool you have to learn.</p><p>But here is what nobody tells you.</p><p>We have been here before. People were skeptical about the internet. About smartphones. About Google. And now we cannot imagine working without them.</p><blockquote>AI is that moment , right now for our generation.</blockquote><figure><img alt="3D illustration of a young woman with a ponytail lying on a rocky cliff at sunset, reaching out towards glowing blue “AI” letters floating between her and another cliff edge. Pink and orange clouds fill the sky" src="https://cdn-images-1.medium.com/max/768/1*QJHr6PXhdHZe1X1fqjYy3A@2x.jpeg" /><figcaption><a href="https://chatgpt.com/">Image From Chatgpt</a></figcaption></figure><p>Since I started using it in my research process, what used to take me weeks now takes me a day or two. I am not spending hours hunting for information anymore. I am spending that time thinking bigger, about the problems worth solving, the products worth building, the users worth fighting for.</p><p>It has not replaced my thinking. It has made room for more of it.</p><p>I am still learning. I recently joined a course to go deeper into AI and understand it properly, not just use it on the surface, because I want to understand it well enough to bring it into UX research in a way that is actually meaningful.</p><p>This is me thinking out loud as I figure it out.</p><p>If you are on the same journey or just AI-curious, I think you will enjoy what is coming next.</p><p>Drop a comment, are you embracing AI in your work or still on the fence? I genuinely want to know. 👇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfc3c3b6bbf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the Tool, Into the Life: How We Started Seeing MailDrip Users Differently]]></title>
            <link>https://medium.com/charisol-pulse/beyond-the-tool-into-the-life-how-we-started-seeing-maildrip-users-differently-28ed11c4322e?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/28ed11c4322e</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[email-marketing]]></category>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 15:01:02 GMT</pubDate>
            <atom:updated>2026-03-30T15:01:02.667Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>The Brief That Changed How I Think About Personas</blockquote><p>There’s a trap product teams fall into without realising it: they define their users by the tool, not by the life the tool fits into.</p><p>At<a href="https://maildrip.io/"> MailDrip</a>, we had fallen into exactly that trap.</p><p>MailDrip is an email marketing platform built for simplicity, beginner-friendly, easy to navigate, and reliable delivery, competing in a market dominated by Mailchimp, Sendinblue, and ConvertKit. We have users across Nigeria and international markets on five plans: Free, Advanced, Premium, Enterprise, and Pay-as-you-go. And we had plenty of positive feedback.</p><p>But when I was tasked with leading a <strong>Persona Validation and Revenue Potential Study</strong>, I quickly realised our understanding of those users was thinner than it should have been. We knew what they did on the platform. We didn’t really know what they were trying to do in their lives.</p><blockquote>That gap was what the research was built to close.</blockquote><h3>Step One: Don’t Start With Interviews</h3><p>This is a mistake I see researchers make, often jumping straight into fieldwork before understanding what the existing data is already saying.</p><p>Before a single interview was scheduled, I ran a <strong>secondary research review and drafted a research plan.</strong> I went back through our early 2024–2025 competitor analysis and user surveys, combed through behavioral data plan distribution, feature engagement, how long it took users to move from free to paid, and sat with our sales and customer success teams to hear what users were actually telling them day to day.</p><blockquote>The output wasn’t answers. It was <strong>5–7 draft persona hypotheses,</strong> informed starting points that would shape every question we asked in the field. Sharp research starts here, not in the first interview.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVuw5Cbp71fy0lasZXLD0A.png" /><figcaption><a href="https://chatgpt.com/">Picture from ChatGPT</a></figcaption></figure><h3>The Reframe That Made Everything Sharper</h3><p>Here’s what the secondary review confirmed: <a href="https://maildrip.io/">MailDrip</a> had been seeing its users through a narrow lens of <em>email marketing.</em></p><p>But Sola, who runs a Lagos fashion store, isn’t primarily an email marketer. She’s an entrepreneur trying to keep customers coming back. Email is just one of the tools she reaches for.</p><blockquote>“I’m not a marketer. I’m a business owner wearing too many hats. I just need something that works without me having to think too hard about it.”</blockquote><p>Her real jobs? Announce new product drops weekly. Win back customers who’ve gone quiet. Build the kind of trust that turns a one-time buyer into a loyal one. Email is the channel, retention is the job.</p><p>When you see the job instead of the channel, everything about how you build, position, and talk to that user changes.</p><h3>Why Jobs-to-be-Done Was the Right Framework</h3><p>To surface those jobs across different persona types, we used the <strong>Jobs-to-be-Done (JTBD) framework.</strong></p><p>The core idea: people don’t use products, they <em>hire</em> them. Nobody signs up for <a href="https://maildrip.io/">MailDrip</a> thinking <em>“I want email marketing software.”</em> They’re thinking:</p><ul><li><em>“I need my customers to remember I exist.”</em></li><li><em>“I need to drive repeat purchases without paying for ads every time.”</em></li><li><em>“I need to communicate professionally, not look like a one-person operation.”</em></li></ul><p>JTBD opened the research beyond the product. It permitted asking about workflows, other tools, frustrations that had nothing to do with <a href="https://maildrip.io/">MailDrip</a>, and that wider context is exactly where the most useful insights live.</p><blockquote>For any researcher, if your framework limits the questions you can ask, change the framework.</blockquote><figure><img alt="A hand-drawn Jobs-to-be-Done framework sketch in a notebook, showing the three layers of user motivation." src="https://cdn-images-1.medium.com/max/768/1*bk7Lmmlbac87XGc0lAuf3w@2x.jpeg" /><figcaption><a href="https://chatgpt.com/">Picture from Chatgpt</a></figcaption></figure><h3>The Three-Phase Plan</h3><p><strong>Phase 1 — Secondary Research Review</strong>: Existing research, behavioral analytics, and internal team knowledge. The output was to draft persona hypotheses to test in the field.</p><p><strong>Phase 2 — In-Depth Interviews: </strong>We are currently speaking with 5+ participants across different persona types, email marketers, business owners, community managers, and more. Each session runs 30–45 minutes, conversational rather than checklist-driven.</p><p>The goal is to hear three layers in every story: the functional job (what they need to accomplish), the emotional job (how they want to feel), and the social job (how they want to be perceived by others).</p><p><strong>Phase 3 — Survey Validation: </strong>Patterns from interviews validated at scale 15–20 responses across persona types, through insights from the interview and targeted outreach.</p><h3>What This Means for MailDrip and for Your Research</h3><p>For <a href="https://maildrip.io/">MailDrip</a>, this study was about expanding the picture. Understanding not just who uses the product, but who they are beyond it — and whether we were truly building for their world or just for a version of it we’d invented.</p><p>For researchers reading this: The most important move you can make before any study is to challenge the frame you’ve been handed. The question isn’t always wrong, but it’s rarely the whole question.</p><p>At <a href="https://charisol.io/">Charisol,</a> we don’t just build features, we build for people. That means before any decision gets made, we ask who is on the other side of the screen, what they’re trying to get done, and whether we’re actually helping them do it. Research isn’t a step in our process. It’s the foundation of it.</p><h3>Coming Up: Part 2</h3><p>Next, I’ll take you into the interviews, the personas that came to life, the patterns nobody predicted, and what it looks like when a user’s own words completely reframe how you see the product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28ed11c4322e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/beyond-the-tool-into-the-life-how-we-started-seeing-maildrip-users-differently-28ed11c4322e">Beyond the Tool, Into the Life: How We Started Seeing MailDrip Users Differently</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hundreds of People Signed Up and Never Came Back. Turns Out, We Were the Problem.]]></title>
            <link>https://medium.com/charisol-pulse/hundreds-of-people-signed-up-and-never-came-back-turns-out-we-were-the-problem-4207ff5c9c30?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4207ff5c9c30</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Thu, 26 Feb 2026 15:01:02 GMT</pubDate>
            <atom:updated>2026-02-26T15:01:02.779Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>We had a problem that looked simple on paper but felt confusing in real life.</blockquote><p>People were signing up for our platform. We even gave them free email credits to get started. But then nothing. They weren’t using the credits. They weren’t coming back. And when they did return, it was brief. A quick look, then gone.</p><p>On the surface, the numbers looked okay. Signups were happening. But underneath? Something was broken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VYDQ7VxftNdfP6nl_DPryg.png" /><figcaption><a href="https://chatgpt.com/">Picture from Chatgpt</a></figcaption></figure><h3>My Job Was to Find Out Why</h3><p>As a UX Researcher, I was tasked with reaching out to new users, specifically people who had signed up but never really engaged with the platform. I wanted to understand what happened between the moment they created an account and the moment they walked away.</p><p>So I started talking to them.</p><p>What I found was surprising. Some of them didn’t even remember signing up. They had stumbled across the platform, created an account out of curiosity, and then moved on. Others had signed up but quickly realized they didn’t actually need an email marketing tool; it wasn’t the right fit for their business at that stage.</p><p>That was a huge insight. We weren’t just losing users because of a bad experience. We were attracting the wrong users in the first place and then doing nothing to help the right ones understand why they should stay.</p><h3>The Onboarding Problem Nobody Talked About</h3><p>Armed with this information, I went deeper. I looked at what our competitors were doing, and I noticed something consistent across the best platforms: their onboarding flows asked questions.</p><p>Not random questions. Smart, intentional ones. <em>Who are you? What kind of business do you run? What are you trying to achieve?</em></p><p>These platforms weren’t just signing people up; they were getting to know them. And with that knowledge, they could show users exactly why the product was right for them.</p><p>We weren’t doing any of that. A user could sign up, get free credits, and have no real understanding of what those credits were for, why they were valuable, or what to do next. We were giving away something useful without explaining its value.</p><h3>What We Did About It</h3><p>After pulling together my research, the user interviews, the competitive analysis, and the patterns I kept seeing, I handed my findings over to the product team. That’s where things got exciting.</p><p>We didn’t just hand off a report and move on. The Product Team, designers, project manager, and researchers all sat down together and started ideating. What would a better onboarding experience actually look like? How do we translate these research findings into something real and useful? Everyone brought their perspective to the table, and through that collaboration, we started shaping a solution that none of us could have arrived at alone.</p><h3><strong>The new approach focuses on three things:</strong></h3><ul><li><strong>Understanding the user. </strong>Right from signup, we ask who they are and what they’re trying to accomplish. Are they a small business owner? A marketer? Someone just exploring? This shapes everything that follows.</li><li><strong>Making the free credits meaningful.</strong> Instead of just giving credits with no context, we now guide users to actually use them. We explain what they’re for, show them how to send a test email, and help them experience the platform’s value firsthand before they ever commit to anything.</li><li><strong>Building trust early.</strong> A test email feature lets users see our deliverability and authenticity in action. Not just a promise — proof.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tgkb74q8sWo1MvXG1JBLKA.png" /><figcaption><a href="https://app.maildrip.io/">MailDrip</a></figcaption></figure><h3>What This Taught Me About UX Research</h3><blockquote>Here’s the lesson I want to leave you with: <strong>talk to your users.</strong></blockquote><p>I know that sounds obvious. But there’s a difference between knowing you should do it and actually doing it. When I sat down and had real conversations with people who had walked away from our platform, I learned more in a few hours than weeks of data analysis had told me.</p><p>Numbers can show you <em>that</em> something is wrong. People can tell you <em>why</em>.</p><p>And once you understand the why, you can actually fix it. You stop guessing. You stop making changes based on assumptions. You start building something that genuinely works for the people you’re trying to serve.</p><p>If your users aren’t taking the actions you expect, don’t just tweak a button or change a color. Go talk to them. Their answers might surprise you.</p><p>This is the work we are doing at <a href="http://maildrip.io/"><strong>MailDrip,</strong></a> building an experience that doesn’t just collect signups, but actually helps every user understand the value they signed up for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4207ff5c9c30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/hundreds-of-people-signed-up-and-never-came-back-turns-out-we-were-the-problem-4207ff5c9c30">Hundreds of People Signed Up and Never Came Back. Turns Out, We Were the Problem.</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why We Document Everything (And How It Saved Our New Year)]]></title>
            <link>https://medium.com/charisol-pulse/why-we-document-everything-and-how-it-saved-our-new-year-870a301d056f?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/870a301d056f</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[startup-culture]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[team-productivity]]></category>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 15:02:01 GMT</pubDate>
            <atom:updated>2026-01-22T15:02:01.271Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Coming back from the holidays shouldn’t feel like starting from scratch. Here’s how documentation made our new year transition seamless.</blockquote><p>January 5th. First day back after the holiday break.</p><p>I opened my laptop expecting the usual post-vacation fog — trying to remember what I was working on, where I left things, what needed to happen next.</p><p>Instead, I opened our documentation, and everything was right there. The research projects I’d been running. The status of each one. The next steps are clearly outlined.</p><p>Within 30 minutes, I was back at full speed. No scrambling. No “wait, what was I doing?” moments. And it wasn’t just me. The entire team picked up right where we left off.</p><figure><img alt="Organized workspace with laptop displaying project documentation and notes, representing seamless work transition after holidays" src="https://cdn-images-1.medium.com/max/1024/1*u8M1PDT0zgRWnHgtNohaAQ.png" /><figcaption><a href="http://chatgpt.com/">Image from Chatgpt</a></figcaption></figure><h3><strong>The Power of Documenting as You Go</strong></h3><p>At <a href="https://charisol.io/">Charisol,</a> we have a simple practice: we document everything as we work, not after we finish.</p><p>Every research project gets documented:</p><p>∙	What we’re researching and why</p><p>∙	What we’re finding</p><p>∙	Where things currently stand</p><p>∙ What are the next steps are</p><p>This isn’t bureaucracy. It’s survival.</p><h3><strong>Why Documentation Actually Matters for Teams</strong></h3><p>Documentation isn’t just about remembering things. It’s about making teamwork actually work.</p><ul><li><strong>Everyone knows what’s happening: </strong>When research is properly documented, designers know what insights are coming. Engineers know what problems we’re trying to solve. Product managers know which evidence supports different decisions.</li><li><strong>No duplication of work:</strong> Documentation prevents wasted time researching something that someone else already looked into three months ago.</li><li><strong>Seamless handoffs:</strong> Research doesn’t stop when one person goes on vacation. If everything is documented, anyone can pick it up and continue without losing momentum.</li><li><strong>Better decisions over time: </strong>When you document not just what you found but why you looked into it, future teammates can learn from past thinking instead of repeating the same debates.</li></ul><p><strong>What Good Documentation Actually Looks Like</strong></p><blockquote>Good documentation is: Structured and consistent. Every project follows the same template so you know exactly where to find information.</blockquote><ul><li><strong>Updated continuously:</strong> We don’t wait until a project is done to document it. Status changes? Update it. New finding? Add it. Next step becomes clear? Write it down.</li><li><strong>Accessible to everyone:</strong> Documentation lives where the team can actually find it, not buried in someone’s personal folders.</li><li><strong>Action-oriented:</strong> We don’t just document what we learned. We document what we’re doing about it, who’s responsible, and what happens next.</li></ul><p><strong>The Real Test: Holiday Break</strong></p><p>Before leaving for the holidays, each of us spent about 30 minutes updating our project documentation. Coming back, those 30 minutes we each spent saved the entire team hours of context-switching and confusion.</p><p>Let me provide a real-world example. Before the break, I was working on a research project aimed at generating revenue. I documented that I’d sent out surveys, which users had responded to, and my plan to conduct follow-up interviews with respondents.</p><p>When I came back in January, I opened the doc and saw exactly where I left off. I could jump straight into scheduling interviews with the survey respondents without having to dig through emails or try to remember who had replied. No wasted time piecing together what I was doing.</p><blockquote><strong>How Other Teams Can Make This Work</strong></blockquote><p>You don’t need fancy tools or complex systems. You need consistency and discipline.</p><ul><li><strong>Start with a simple template:</strong> Create one standard format for documenting projects: project goal, current status, key findings, next steps, and owner.</li><li><strong>Make it a habit:</strong> End each work session with 5 minutes of documentation. What did you do? What did you learn? What’s next?</li><li><strong>Use tools your team actually uses:</strong> Don’t introduce a new tool just for documentation. Use whatever your team is already in — Google Docs, ClickUp, Notion, Confluence, whatever.</li><li><strong>Document decisions, not just findings:</strong> When you make a choice, write down why. “We decided to focus on email credits because…” is way more valuable than just “focusing on email credits.”</li><li><strong>Make it accessible:</strong> Everyone on the team should know where to find project documentation. If people have to ask where something is, your system isn’t working.</li></ul><h3>The Documentation Culture at Charisol</h3><p>This practice is part of how we work at <a href="https://charisol.io/">Charisol</a>. When research is documented well, it doesn’t just help the researcher. It helps designers who need to understand user problems, engineers who need to know what they’re solving for, and product managers who need to make informed decisions.</p><p>Documentation turns individual work into team knowledge. It turns scattered insights into shared understanding.</p><p>Coming back from the holidays reminded me why this matters. We didn’t lose momentum because we’d documented where we left off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BhwbdwK4lTkCz9yqXpHbyA.jpeg" /><figcaption><a href="http://www.freepik.com/">Image From Freepik</a></figcaption></figure><p><strong>The Bottom Line</strong></p><p>Documentation isn’t glamorous. Nobody celebrates great documentation the way they celebrate successful launches.</p><p>But documentation is what makes everything else possible. It’s the foundation that lets teams move fast, work together, and build on each other’s work instead of constantly starting over.</p><p>If your team struggles with handoffs, loses context when people are out, or duplicates work, you don’t have a people problem. You have a documentation problem.</p><p>And the good news? That’s one of the easiest problems to fix.</p><p>What does documentation look like on your team? We’d love to hear what’s working (or not working) for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=870a301d056f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/why-we-document-everything-and-how-it-saved-our-new-year-870a301d056f">Why We Document Everything (And How It Saved Our New Year)</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Compliance to Confidence: How UX Research Shapes Ethical Email Design]]></title>
            <link>https://medium.com/charisol-pulse/from-compliance-to-confidence-how-ux-research-shapes-ethical-email-design-e4c2bdc79d85?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4c2bdc79d85</guid>
            <category><![CDATA[ai-in-ux-design]]></category>
            <category><![CDATA[ethical-design]]></category>
            <category><![CDATA[email-marketing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Wed, 19 Nov 2025 15:02:28 GMT</pubDate>
            <atom:updated>2025-11-19T15:02:28.987Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Sometimes, the real work of UX research isn’t about colors, buttons, or layout, it’s about <strong>trust</strong>.</blockquote><figure><img alt="A computer monitor on a modern desk displays an email inbox filled with unread messages, while multiple blue email notification icons float around the screen. A person’s hands holding a smartphone and pen are visible beside the monitor, suggesting multitasking in a work setting." src="https://cdn-images-1.medium.com/max/1024/1*yd21_WwmyI4G_OK-lYjmSQ.png" /><figcaption><a href="https://chatgpt.com/">Picture From ChatGPT</a></figcaption></figure><p>Recently, we noticed something that made us pause: when one user sends spammy or fraudulent emails, it doesn’t just affect them. It can damage the reputation of the entire sending domain, meaning that good users could suffer<strong> </strong>because of one person’s mistake.</p><p>That moment sparked a meaningful conversation for us as researchers, designers, and Engineers. How do we make compliance and ethical email practices not just a checkbox, but a built-in experience that protects everyone?</p><h3>Understanding the Real Problem</h3><p>We already have systems that ensure users follow <a href="https://maildrip.io/privacy-policy/">Data and Privacy</a> regulations. But compliance alone isn’t enough; it needs to feel clear, human, and built-in.</p><p>Through research, we discovered that users often don’t realize how small things, like spammy subject lines, suspicious links, or even specific images, can trigger spam flags or affect deliverability. It’s not always intentional; sometimes, users don’t know where the risk lies.</p><p>That insight helped us realize that education, through design<strong> </strong>rather than restriction, is where our real impact lies.</p><h3>Strengthening with AI and Smart Systems</h3><p>How might we make our existing systems, like the spam filter, smarter?</p><p>We started exploring how AI could proactively scan outgoing emails for suspicious URLs, phishing-like images, or flagged language before they’re ever sent.<br> The goal is simple: to protect users’ reputations and ensure every email sent through <a href="https://maildrip.io/">MailDrip</a> maintains quality and trust.</p><p>By combining compliance awareness with AI-powered security, we’re reinforcing a safer, more reliable experience, without disrupting user flow.</p><figure><img alt="A technician in a data center watches a large transparent screen showing glowing neural-network lines and nodes, symbolizing an AI system that scans emails and images to detect phishing links and suspicious content on our platform." src="https://cdn-images-1.medium.com/max/1024/1*9vBlR5LrcjBdWOPaFEMIRg.jpeg" /><figcaption><a href="https://www.freepik.com/free-photo/tech-support-oversees-ai-neural-network_134855678.htm#fromView=search&amp;page=1&amp;position=16&amp;uuid=fe501d66-4a04-4cf2-866f-d28b19df536e&amp;query=smart+Ai">Picture From Freepik</a></figcaption></figure><h3>Benchmarking and Collaboration</h3><p>As part of this research, we also looked outward.<br> We studied how other email marketing platforms approach deliverability, compliance, and trust. It wasn’t about copying; it was about understanding what’s working in the ecosystem and identifying where we could stand ahead.</p><p>After analyzing patterns and best practices, we presented our findings and collaborated closely with the engineering team. Some of our recommendations required deep technical considerations, so working together helped us evaluate what was feasible now and what could evolve in later phases.</p><p>That collaboration became a bridge, turning UX insights into real, technical improvements.</p><h3>Turning Research Into Action</h3><p>Our next steps are about strengthening the <a href="https://maildrip.io/">MailDrip</a> experience, reinforcing sender protection, improving AI-driven checks, and weaving ethical design principles into every layer of the platform.</p><p>Because compliance isn’t just about meeting regulations; it’s about building confidence.<br> Confidence that every email you send comes from a place of integrity, clarity, and trust.</p><p>And that’s what we’re working toward: one improvement, one insight, one iteration at a time.</p><h3>A Researcher’s Reflection</h3><p>As a UX researcher, I’ve learned that progress often lives in the quiet intersections, where design, data, and human behavior meet. Projects like this remind me why I love what I do; it’s not just about solving problems, but building systems that help people use technology responsibly and confidently.</p><p>Because at the end of the day, research doesn’t just improve products, it enhances trust.</p><p><strong>Build products your users can trust.</strong><br><a href="https://charisol.io/?utm_source=Medium&amp;utm_medium=Blogpost&amp;utm_campaign=From+Compliance+to+Confidence">At <strong>Charisol</strong></a>, we turn deep UX research into ethical, intuitive, and intelligent product experiences, so your platform doesn’t just work, it protects.<br><strong>Let’s help you design trust-driven digital products.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4c2bdc79d85" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/from-compliance-to-confidence-how-ux-research-shapes-ethical-email-design-e4c2bdc79d85">From Compliance to Confidence: How UX Research Shapes Ethical Email Design</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the Spam Folder: How Research Shaped Our AI-Powered Content Checker]]></title>
            <link>https://medium.com/charisol-pulse/beyond-the-spam-folder-how-research-shaped-our-ai-powered-content-checker-300baa4bf2b9?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/300baa4bf2b9</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[email-marketing]]></category>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Thu, 13 Nov 2025 15:02:06 GMT</pubDate>
            <atom:updated>2025-11-13T15:02:06.302Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Each time we’d get on a walkthrough call with users and they’d complain, “My emails keep landing in spam,” we’d apologize and promise to check from our end.</blockquote><figure><img alt="The MailDrip dashboard interface displays email campaign performance, instant email lists, and a navigation menu with sections such as Drip Campaigns, Contacts, and Billing, all set against a blue background featuring the MailDrip logo." src="https://cdn-images-1.medium.com/max/1024/1*X1SULpQ6BElubwBMVWCQ9g.png" /><figcaption><a href="https://maildrip.io/">MailDrip</a></figcaption></figure><p>If you’ve ever sent an email campaign and watched it disappear into spam, you know that sinking feeling.<br> For the longest time, we thought the issue was on our backend, possibly due to a server glitch or a problem with our sending domain.</p><p>Each time we conducted a walkthrough call with users and they complained, “My emails keep landing in spam,” we’d apologize and promise to investigate from our end.</p><p>However, as I continued leading these calls, observing users, asking questions, and listening to their frustrations, something clicked. What if it’s not always us? What if the content itself is the problem?</p><h3>The Discovery</h3><p>So, we dug deeper.<br>We started analyzing what users were actually sending out, subject lines, body text, images, links, and what we found was interesting. Some emails contained what we call <em>spammy words, </em>such as “Buy now,” “Limited offer,” and “Claim your prize.”<br>Others had phishing-like links, hidden redirects that could easily raise red flags for spam filters.</p><p>“We conducted a full internal study to understand how content affects deliverability, reviewing user behavior, email patterns, and spam triggers. This kind of research-led thinking is at the core of how we approach everything at Charisol. In fact, our article, <em>“</em><a href="https://medium.com/charisol-pulse/the-unseen-link-how-ux-research-fuels-powerful-brand-messaging-8c5dd588beb1"><em>The Unseen Link: How UX Research Fuels Powerful Brand Messaging</em></a><em>,”</em> examines how user research forms the underlying foundation of brand messaging and product experience.</p><p>At that point, it became clear that sometimes it wasn’t the system, it was the content.<br> If out of every ten emails, six were going to spam, we needed to find out why, not just where they landed.</p><h3>The Research That Sparked a Shift</h3><p>This was where research came in again. We conducted a comprehensive internal study to understand the impact of content on deliverability. We reviewed user behavior, analyzed email patterns, and examined existing spam-check tools.<br> How can we utilize AI to help users solve this problem?</p><h3>Designing the Solution</h3><blockquote><em>Our idea was simple: integrate AI that could detect spammy content before the user hits send.</em></blockquote><p>So, we built two pathways:</p><ol><li><strong>AI-Generated Content</strong>: Users can let AI write their emails, which are automatically optimized to avoid spam triggers.</li><li><strong>AI Content Scanner: </strong>For users who prefer writing their own emails, AI scans the content, highlights possible spammy elements, and provides a “spam score.”</li></ol><p>If your score is low, great, your content is safe. If it’s high, AI helps you fix it before it damages your sender reputation. This way, users no longer have to guess what’s wrong; they can see it in real time.</p><figure><img alt="ALT text: Screenshot of MailDrip’s “Create new instant emails” page showing the email subject setup step with options to “Write with AI” or “Check for spam,” alongside a mobile preview of the email subject line." src="https://cdn-images-1.medium.com/max/1024/1*Mfk1GOhDxh8ydJ6EbZpRLA.png" /><figcaption><a href="https://maildrip.io/">MailDrip</a></figcaption></figure><h3>Competitor and Collaboration Phase</h3><p>Before development started, I led a comparative study to examine how other email marketing platforms were utilizing AI, not just the big names, but also smaller competitors that were innovating quietly.</p><p>That research provided us with direction on what works, what feels intuitive to users, and what gaps we could fill.</p><p>After gathering insights, collaboration was the next step.<br> We worked closely with our engineering team<strong> </strong>to understand what was technically feasible and with the design team to ensure the experience looked and felt natural within MailDrip’s environment.</p><p>It was one of those moments where you see research, design, and development truly intersect, and that was exciting.</p><h3>Then Came the Real Test</h3><p>After the feature was launched, I joined another walkthrough call with a long-time user.<br> He didn’t use the AI.<br> When I asked why, he said, “It feels a bit generic.”</p><p>That was another lightbulb moment.<br> We realized users didn’t fully understand <em>why</em> AI was there or <em>how</em> it could help. To them, it was just “another AI button.”</p><p>So, we went back to the drawing board. We refined the onboarding message to clarify that the AI wasn’t just a writing tool, but a <em>deliverability assistant.</em></p><p>We also introduced short goal prompts, allowing users to personalize the tone and purpose of their emails. That way, it wouldn’t sound robotic or “AI-generated.”</p><figure><img alt="Screenshot of the MailDrip interface showing the “Write with AI” feature for creating new instant emails. The screen includes form fields for inputting context and audience, campaign goal, recipient information, email topic, and brand tone. A purple button labeled “Write Email” is displayed at the bottom right, with a note encouraging users to input prompt information for more efficient email generation." src="https://cdn-images-1.medium.com/max/1024/1*9bW-B2Z3EWbCKZok77xE6A.png" /><figcaption><a href="http://maildrip.io/">MailDrip</a></figcaption></figure><h3>The Lesson That Stuck With Me</h3><p>If there’s one thing this whole process taught me, it’s that launching a feature is only half the work.<br> The other half is watching how users actually interact with it.</p><p>As a UX researcher, it’s easy to get excited about your findings, your solution, your “big idea.” But the real success is when users adopt it, when it actually solves a problem for them.</p><p>“As we refine onboarding and watch user adoption, we’re reminded that research and speed must go hand in hand, something we explore in &#39;<a href="https://medium.com/charisol-pulse/when-agile-becomes-an-excuse-for-chaos-c0a727d98f79"><em>When Agile Becomes an Excuse for Chaos</em></a><em>.”</em></p><p>So now, every time we launch something new, we don’t just check performance metrics. We check <em>usage behavior:</em> are users adopting it? Are they ignoring it? Why?</p><h3>The Next Chapter</h3><p>Right now, we’re expanding this work further.<br>The next phase of our AI research focuses on security, utilizing AI to detect phishing links, fraudulent content, and domain-damaging behavior before it impacts others on the platform.</p><p>Because in email marketing, one user’s mistake shouldn’t ruin another’s reputation.</p><h3>Final Thoughts</h3><p>Looking back, this journey started with one simple question<br> “Why are our emails going to spam?”</p><p>However, it evolved into something much bigger—a blend of AI, research, and human understanding working together to protect users and strengthen trust.<br> And that’s the part of UX research I love the most, seeing an insight grow into a real, impactful solution.</p><p>“Stop guessing why your emails land in spam. Let AI and research-driven insights optimize your content and protect your sender reputation. Book a session with <a href="https://charisol.io/?utm_source=Medium&amp;utm_medium=Blogpost&amp;utm_campaign=Beyond+the+Spam%C2%A0Folder">Charisol</a> today and see the difference.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=300baa4bf2b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/beyond-the-spam-folder-how-research-shaped-our-ai-powered-content-checker-300baa4bf2b9">Beyond the Spam Folder: How Research Shaped Our AI-Powered Content Checker</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inside the Audit: How We’re Simplifying MailDrip’s Instant Email Flow for Every User]]></title>
            <link>https://medium.com/charisol-pulse/inside-the-audit-how-were-simplifying-maildrip-s-instant-email-flow-for-every-user-bae95b2a27a6?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bae95b2a27a6</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[email-marketing]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Thu, 23 Oct 2025 15:02:31 GMT</pubDate>
            <atom:updated>2025-10-23T15:02:31.902Z</atom:updated>
            <content:encoded><![CDATA[<p>During one of our user walkthrough sessions for <a href="https://maildrip.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Inside+the+Audit">MailDrip’s</a> <em>Instant Email</em> feature, a participant paused mid-way and said something that stuck with me:</p><blockquote><em>“</em>I like how straightforward this is, but what does <strong>unset </strong>mean?<em>”</em></blockquote><p>That single moment revealed so much. Users actually <em>loved</em> how easy the form was to fill out. We heard things like <em>“It’s so simple and clear!” </em>but small, unclear words like <strong><em>unset</em> </strong>created just enough confusion to interrupt the flow.</p><figure><img alt="Present instant email flow screen for MailDrip (app.maildrip.io)" src="https://cdn-images-1.medium.com/max/1024/1*GKdlGkZTimCnN54rpdSKRg.png" /><figcaption>MailDrip’s current instant email flow (<a href="https://maildrip.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Inside+the+Audit">app.maildrip.io</a>)</figcaption></figure><p>So, it was time to dive into research, not to redesign what worked, but to understand what could be clearer.</p><h3>The Audit: Understanding What’s Working (and What’s Not)</h3><p>We started with an <strong>internal heuristic evaluation.</strong> That’s a fancy UX way of saying we gave our form a deep, honest review, the kind where you zoom out and ask, “<strong><em>Would I actually enjoy filling this out?</em></strong>”</p><p>We looked at the usual suspects, focusing on:</p><ul><li>Clarity of labels and toggles</li><li>Button placement and hierarchy</li><li>Consistency across sections</li><li>And whether everything flows the way it should.</li></ul><p>Basically, a heuristic evaluation is like being your own product’s critic, catching confusing labels, messy layouts, or extra clicks before your users do.</p><p>The goal wasn’t just to find flaws; it was to understand usability patterns. And our audit revealed that while the form flow was strong, some labels and visual cues lacked meaning for first-time users.</p><p>So we documented each finding with screenshots and notes, identifying where confusion occurred and where users hesitated.</p><h3>Competitor Analysis: Learning from Industry Leaders</h3><figure><img alt="An image illustrating a researching conducting competitive analysis" src="https://cdn-images-1.medium.com/max/1024/0*XbwqptuRb1KHeiT6" /><figcaption>Photo by <a href="https://unsplash.com/@firmbee?utm_source=medium&amp;utm_medium=referral">Firmbee.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Next, we looked outward.</p><p>We identified <strong>three (3) platforms</strong> that used toggle-based forms similar to ours, especially those that enabled instant actions (such as instant email scheduling).</p><p>And we studied how they:</p><ul><li>Structured their form sections</li><li>Labeled toggles and actions</li><li>Guided users from start to finish</li></ul><p>One of the things we discovered was that successful forms used toggle-based <em>actions</em> (“Send instantly” instead of “Unset”), progressive disclosure to reveal sections step-by-step, and avoided multiple CTAs in a single view.</p><p>These findings helped us benchmark what clarity truly looks like.</p><h3>UX Guidelines: Aligning Research with Best Practices</h3><p>To validate our observations, we turned to trusted UX research sources like:</p><ul><li><a href="https://www.nngroup.com/"><strong>Nielsen Norman Group</strong></a>: One of the most respected authorities in the UX field. They publish research artifacts, such as articles and research findings, to support experience designers, researchers, product managers, and developers.</li><li><a href="https://baymard.com/"><strong>Baymard Institute</strong></a><strong>: </strong>Known for deep UX research into e-commerce and B2C usability. They conduct large-scale benchmark studies and publish detailed UX guidelines that are super valuable for product teams in retail or conversion optimization.</li><li><a href="https://uxcollective.com/"><strong>UX Collective</strong></a><strong>: </strong>A Medium-based online publication that curates and publishes articles from designers and researchers worldwide. It’s more community-driven, with thought pieces, reflections, and practical tips from practitioners.</li></ul><figure><img alt="A hand-drawn diagram showing the “UX Research Cycle”. The center circle is labeled “UX Research”, surrounded by connected outer circles labeled “Design”, “Development”, “Testing”, “Strategy”, “Content”, and “Marketing”." src="https://cdn-images-1.medium.com/max/768/1*sWg0uHfOXmU6YOfJBFP4Og@2x.jpeg" /><figcaption>Picture from ChatGPT</figcaption></figure><p>From these, we pulled principles that guided our next steps:</p><ul><li><strong>Progressive Disclosure:</strong> Don’t overload users; let them focus on one section at a time.</li><li><strong>Action-Based Labeling:</strong> Use clear, outcome-driven words that describe what happens next.</li><li><strong>Single Primary CTA:</strong> Limit distractions by keeping one clear action per section.</li></ul><p>These principles aligned perfectly with what we found during our audit and competitor review, giving us the confidence to move into redesign.</p><h3>The Redesign: Bringing Clarity to Life</h3><p>With clarity as our goal, we started refining.</p><p>We replaced <strong><em>unset</em> </strong>and other ambiguous terms with direct, action-oriented copy. We adjusted spacing, improved section hierarchy, and created a better sense of flow.</p><p>Now, the <em>Instant Email</em> form feels even more natural, easy to follow, visually clear, and more intuitive for users to complete.</p><figure><img alt="New instant flow screen for MailDrip (app.maildrip.io)" src="https://cdn-images-1.medium.com/max/1024/1*bdJ7rOSy4AOTvY7TJeOEiQ.png" /><figcaption>MailDrip’s proposed instant email flow (<a href="https://maildrip.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Inside+the+Audit">app.maildrip.io</a>)</figcaption></figure><p>The design phase is almost done and ready for the engineers to pick up.<br> We’ve been intentional about incorporating every UX principle discovered through research, and as always, we’ll keep refining based on new feedback.</p><h3>What’s Next</h3><p>I honestly can’t wait to show the <em>before and after</em> of this entire journey, how one small word (<strong><em>unset</em></strong>) led to a major clarity upgrade across the product.</p><p>But for now, we’re celebrating progress: a design that feels lighter, clearer, and built with users in mind.</p><p>At <a href="https://maildrip.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Inside+the+Audit">MailDrip</a>, this process reminded us that:</p><blockquote><em>Research isn’t just a phase; it’s how we stay connected to real user understanding.</em></blockquote><p><em>We designed </em><a href="https://maildrip.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Inside+the+Audit"><em>MailDrip</em></a><em> to make email automation simple, personal, and scalable.</em> Try it for yourself at <a href="https://maildrip.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Inside+the+Audit"><strong>Maildrip.io</strong></a><strong>!</strong></p><p><a href="https://maildrip.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Inside+the+Audit">MailDrip | Email Marketing For Small Businesses</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bae95b2a27a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/inside-the-audit-how-were-simplifying-maildrip-s-instant-email-flow-for-every-user-bae95b2a27a6">Inside the Audit: How We’re Simplifying MailDrip’s Instant Email Flow for Every User</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What It’s Really Like Being a UX Researcher]]></title>
            <link>https://medium.com/charisol-pulse/what-its-really-like-being-a-ux-researcher-01d0e77048e5?source=rss-889a1ebb55c------2</link>
            <guid isPermaLink="false">https://medium.com/p/01d0e77048e5</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Hannah Makabi Daniel]]></dc:creator>
            <pubDate>Tue, 07 Oct 2025 15:01:56 GMT</pubDate>
            <atom:updated>2025-10-07T15:01:56.441Z</atom:updated>
            <content:encoded><![CDATA[<p>People often assume a UX researcher just sits in front of a laptop, staring at numbers and charts all day. However, the truth is that my work is far more dynamic than that.</p><blockquote>Being a UX researcher at <a href="https://charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Being+a+UX+Researcher"><strong>Charisol</strong></a><strong> </strong>is like being a detective, a storyteller, and a translator all at once.</blockquote><p>Every day, I move between uncovering user problems, translating those problems into insights, and helping teams understand what those insights mean for the product.</p><h3>What My Work Really Looks Like</h3><p>On a typical project, my role begins with asking questions:</p><ul><li>Who are we designing for?</li><li>What problems are they facing?</li><li>Why does this matter to them?</li></ul><p>To answer these, I use a mix of methods. Sometimes I conduct usability tests, watching in real-time as users struggle or succeed with a particular flow. At other times, I conduct audits to assess how well a product aligns with usability principles. I also send out surveys to capture quick, broad feedback, and I lean on interviews and observations to understand the “<em>why</em>” behind user behavior.</p><blockquote>The goal is never just to collect data; it’s to bring the human side of the product into every design decision.</blockquote><figure><img alt="The image depicts a UX Researcher in a colorful striped sweater standing confidently before a whiteboard filled with notes and charts, highlighting a dynamic and collaborative work environment." src="https://cdn-images-1.medium.com/max/1024/1*6Vn7kviTuu1_lNH6fDLx8Q.jpeg" /><figcaption><a href="https://www.meta.ai/">Picture From Meta AI</a></figcaption></figure><h3>The Challenges Nobody Talks About</h3><p>Of course, research isn’t always straightforward. One challenge I face is communicating insights in a way that sticks. It’s one thing to tell a designer, “users struggled here”, it’s another thing entirely to make that insight meaningful enough to spark change.</p><p>Another challenge is when research gets pushed aside. Sometimes, valuable studies sit in the backlog, untouched, not because the insights aren’t useful, but because the team is focused on speed or other priorities. In those moments, it can feel as though the user’s voice is fighting to be heard.</p><p>These challenges are real, but they’ve also taught me the importance of persistence: how to advocate for users even when it’s inconvenient, and how to remind teams that every overlooked insight is a missed opportunity for better design.</p><h3>How I Overcame These Challenges</h3><p>Over time, I’ve learned that communicating insights goes beyond just reporting findings; it’s about making people feel what users experience. I now use storytelling and visualization to bring research to life.</p><figure><img alt="Image of a researcher working another colleague through some data and infographics." src="https://cdn-images-1.medium.com/max/1024/0*rquNfUs_frasOT9Q" /><figcaption>Photo by <a href="https://unsplash.com/@uxindo?utm_source=medium&amp;utm_medium=referral">UX Indonesia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For instance, when reporting usability walkthrough calls, I guide the team through key moments where users struggle. And I turn those moments into short, relatable stories that highlight not just what happened, but also why it matters for the user and the product.</p><p>Even when we can’t all be in the same session, I ensure that those insights remain visible by linking key observations directly in shared documents. That way, anyone can revisit the exact moment where an issue occurred and see the context for themselves.</p><p>As for research getting pushed aside, I’ve learned to integrate myself earlier in the process rather than waiting until the end to share findings. I now conduct live observation sessions, where team members can observe users interacting with the product in real-time. It helps everyone connect with the user experience firsthand.</p><p>And because I don’t want any research to end up buried, I actively track insights and follow up with respective teammates, ensuring these insights aren’t relegated to the back of a document, but are actually driving design and product decisions.</p><h3>What Success Looks Like</h3><p>The best part of my job is seeing research make a difference. I’ve seen usability tests lead to a 70% reduction in user errors, simply because we identified where people were struggling and adjusted the flow accordingly.</p><p>I’ve watched as findings I shared improved collaboration across design and product because suddenly, everyone was looking at the same evidence, not just opinions.</p><p>I’ve even had moments where leadership recognized the impact of research on the product, and those are the moments that remind me just how powerful this role is.</p><figure><img alt="A group of UX Researchers, product team, designers engaged in a collaborative meeting around a table, with a large screen displaying various data visualizations and charts, mockups in the background." src="https://cdn-images-1.medium.com/max/1024/1*5qW1AqsxhJt_Ux8oFsdhLQ.jpeg" /><figcaption><a href="https://www.meta.ai/">Picture From Meta AI</a></figcaption></figure><h4><strong>And here’s a real example</strong></h4><p>During a recent audit, I identified areas where users struggled to navigate key features in <a href="https://maildrip.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Being+a+UX+Researcher">MailDrip’s</a> instant email flow. As a result of that research, the team is now redesigning those problem spots.</p><p>This time, every decision is supported by evidence rather than assumptions. It may seem minor, but it’s a significant shift, turning ambiguous labels and confusing wording into something clear, intuitive, and user-friendly.</p><blockquote>That’s the power of research: it elevates a product from “working fine” to “working seamlessly”.</blockquote><p>Success, for me, is when users navigate a product smoothly without even thinking about it, and the team behind it knows that’s because research shaped the design.</p><h3>My Key Takeaway</h3><p>If there’s one thing I’ve learned, it’s this: research isn’t about slowing things down, it’s about making things better.</p><p>Every usability test, every survey, and every observation is an opportunity to gain a deeper understanding of people. And when you understand people, you create products that don’t just function; they feel natural, intuitive, and human-centered.</p><p>So if you’re a designer, product manager, developer, or aspiring UX researcher, remember this: insights don’t just sit in reports. They have the power to shape products, guide teams, and create experiences that truly matter.</p><p>And that is why I’m proud to be a UX researcher.</p><p><em>We believe how we work is just as important as what we build.</em> Get to know us at <a href="https://charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Being+a+UX+Researcher"><strong>Charisol.io</strong></a><strong>!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01d0e77048e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/what-its-really-like-being-a-ux-researcher-01d0e77048e5">What It’s Really Like Being a UX Researcher</a> was originally published in <a href="https://medium.com/charisol-pulse">Charisol Pulse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>