<?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 Zaynab Aderonke Ogunnubi on Medium]]></title>
        <description><![CDATA[Stories by Zaynab Aderonke Ogunnubi on Medium]]></description>
        <link>https://medium.com/@slim_zee?source=rss-5504b6aa21b8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pI1o2U1zeOkoJGiYxZEQPA@2x.jpeg</url>
            <title>Stories by Zaynab Aderonke Ogunnubi on Medium</title>
            <link>https://medium.com/@slim_zee?source=rss-5504b6aa21b8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:32:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@slim_zee/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[Stop Benchmarking Giants: You’re Not Building the Next Airbnb (Yet)]]></title>
            <link>https://medium.com/charisol-pulse/stop-benchmarking-giants-youre-not-building-the-next-airbnb-yet-feff305ab42e?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/feff305ab42e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Wed, 10 Dec 2025 15:02:37 GMT</pubDate>
            <atom:updated>2025-12-10T15:02:37.163Z</atom:updated>
            <content:encoded><![CDATA[<p>Every startup has that one moment in a product meeting when someone says: “<em>Let’s look at how Airbnb does it.</em>” or “<em>Stripe solved this the same way.</em>” or “<em>Can we do something like Amazon?</em>”</p><p>It sounds harmless. Even smart.</p><p>But here’s the truth nobody wants to admit:</p><blockquote>Copying giants is the fastest way to build a product that doesn’t fit your stage, your users, or your reality.</blockquote><p>Big-company UX isn’t startup UX. Their problems aren’t your problems. Their constraints aren’t your constraints. Their users aren’t your users.</p><p>Yet many early teams spend more time studying billion-dollar interfaces than understanding the people they’re actually building for.</p><figure><img alt="A chart comparing early stage product with mature company" src="https://cdn-images-1.medium.com/max/1024/1*3UqyfSYUqpkbC22rQeASVg.jpeg" /><figcaption>Early-stage product vs. Giant comparison</figcaption></figure><h3>The Scale Problem</h3><p>Airbnb’s search flow looks the way it does because they operate in 220+ countries.</p><p>Amazon’s checkout flow works because they’ve spent over a decade optimizing it for millions of transactions per hour.</p><p>Stripe’s docs are a masterpiece because they support countless edge cases and enterprise-level integration paths.</p><p>You don’t need all that, at least not now.</p><p>Most early-stage products don’t even have:</p><ul><li>enough traffic to justify complex funnels</li><li>enough features to warrant heavy navigation</li><li>enough users to validate advanced personalization</li><li>enough data to automate anything meaningful</li></ul><p>So when small teams copy giants, they accidentally copy solutions to problems they <em>don’t even have yet</em>.</p><p>And the real risk is <strong>misalignment</strong>.</p><figure><img alt="An image of team members brainstorming and wireframing on a whiteboard" src="https://cdn-images-1.medium.com/max/1024/0*ehgLW2xoknJfBDnb" /><figcaption>Photo by <a href="https://unsplash.com/@kaleidico?utm_source=medium&amp;utm_medium=referral">Kaleidico</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Benchmarking giants leads to three predictable traps:</p><p><strong>1. Overbuilding features users don’t need. </strong>You introduce complexity because “<em>that’s how the big guys do it</em>” when your users were fine with simple.</p><p><strong>2. Solving for scale before you have scale. </strong>You design for edge cases you haven’t met. You optimize flows no one is using yet.</p><p><strong>3. Ignoring the thing that actually gives you an edge. </strong>Startups win by <em>speed, closeness to users, and learning,</em> not polish that mimics billion-dollar teams.</p><p>When you benchmark giants too early, you stop seeing your product for what it is: an experiment, not an empire.</p><h3>So Who Should You Benchmark?</h3><blockquote><strong>Benchmark teams at your stage, with your constraints, solving similar behaviors - not similar industries.</strong></blockquote><p>If you’re validating an MVP:</p><ul><li>look at products with crisp, simple flows</li><li>study scrappy teams that learned fast</li><li>compare approaches, not aesthetics</li></ul><p>If you’re refining a feature:</p><ul><li>benchmark teams that tested, iterated, and shipped lean</li><li>look at what they removed, not what they added</li></ul><p>If you’re early in your category:</p><ul><li>benchmark user behavior, not “UX inspiration”</li><li>observe friction, motivations, expectations</li></ul><p>The best models for early-stage teams are <em>peer companies</em>, not giants. The giants only make sense when you start solving giant-sized problems.</p><h3>What to Do Instead</h3><p>Here’s a cleaner, more grounded way to guide your product decisions:</p><figure><img alt="Team members going through the design thinking framework, starting with empathy and then ideating" src="https://cdn-images-1.medium.com/max/1024/0*r_FHJV6bk0sGHVsZ" /><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><ol><li><strong>Start with your users’ real behavior, not someone else’s UI.</strong><br> If your users aren’t dropping off, you don’t need a redesign.</li><li><strong>Borrow principles, not patterns.</strong><br>Airbnb’s trust cues? Great principle.<br>Their entire booking architecture? Not for you.</li><li><strong>Design for the next 3 months, not the next 3 years.</strong><br>Your product will change. Don’t lock yourself into complexity.</li><li><strong>Use constraints as a strategic advantage.</strong><br>Fewer features = clearer focus.<br>Smaller teams = faster loops.<br>Limited resources = intentional choices.</li><li><strong>Let maturity dictate complexity - not ambition.</strong><br>If you don’t have scale, don’t design for scale.<br>If you don’t have a marketplace, don’t design like one.<br>If you don’t have huge traffic, don’t build like you do.</li></ol><h3>The Point Isn’t to Think Small; It’s to Think Correctly</h3><p>Benchmarking giants too early is like training for a marathon by copying an Olympian’s routine on day one.</p><p>You’ll burn out long before you see progress.</p><p>Startups win by staying close to the ground: talking to users, simplifying, learning, adjusting, and shipping with intention.</p><p>There will be a time to study Airbnb.<br>There will be a time to learn from Amazon.<br>There will be a time to match Stripe’s polish.</p><p>But you have to earn that level of complexity.</p><p>For now?</p><blockquote>Build the best version of your stage, not someone else’s finish line.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=feff305ab42e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/stop-benchmarking-giants-youre-not-building-the-next-airbnb-yet-feff305ab42e">Stop Benchmarking Giants: You’re Not Building the Next Airbnb (Yet)</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[When Agile Becomes an Excuse for Chaos]]></title>
            <link>https://medium.com/charisol-pulse/when-agile-becomes-an-excuse-for-chaos-c0a727d98f79?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0a727d98f79</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 15:02:37 GMT</pubDate>
            <atom:updated>2025-11-11T16:33:40.462Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone says they’re agile.</p><p>But somewhere between the sprints, the stand-ups, and the endless pivots, <strong><em>agile </em></strong>stopped meaning adaptable and started meaning unplanned.</p><p>You can feel it when you walk into certain product teams. Every week brings a “new priority”. Meetings multiply. Research becomes optional. And what started as a method for clarity slowly turns into a cover for confusion.</p><p>Agile wasn’t supposed to be this way.</p><figure><img alt="An illustration depicting what “Agile” is all about" src="https://cdn-images-1.medium.com/max/1024/1*R2A24Ykan90sr6Dxkb-8RA.jpeg" /></figure><h3>The Spirit vs. the Practice</h3><p>When the Agile Manifesto was first introduced, it aimed to liberate teams from rigid processes. It was a call to focus on outcomes, not bureaucracy. On people, and not paperwork.</p><p>Unfortunately, somewhere along the way, the pendulum swung too far. Some teams dropped <em>all</em> structure in the name of “being flexible”. Documentation disappeared. Context was lost. Product direction shifted weekly.</p><p>Agile turned into a sprinting treadmill, with lots of motion and little progress. And eventually, we lose sight of the goal. This mirrors the dynamic explored in “<a href="https://medium.com/charisol-pulse/the-mvp-trap-when-fast-isnt-always-smart-860df5957802">The MVP Trap: Why Fast Isn’t Always Smart</a>”, and how moving <strong><em>fast </em></strong>can sometimes cost more than we think.</p><p>The truth is, <strong>agile isn’t about speed. It’s about learning. </strong>And learning only happens when there’s focus.</p><h3>The Hidden Cost of ‘Fake Agile’</h3><p>When teams confuse agility for chaos, the fallout is easy to spot:</p><ul><li><strong>No one knows what success looks like.</strong> Goals shift faster than they’re met.</li><li><strong>Research and design become afterthoughts.</strong> “We’ll figure it out later” becomes the team motto.</li><li><strong>Teams burn out.</strong> Because it’s hard to run a marathon when the route keeps changing.</li><li><strong>Users feel the confusion.</strong> The product experience mirrors the team’s lack of clarity.</li></ul><p>Chaos doesn’t come from change. It comes from <em>change without direction.</em></p><h3>How to Bring Order Back</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwREid2umrkxWA5tvUz9bw.png" /><figcaption><a href="https://www.freepik.com/free-photo/improvement-success-planning-ideas-research_2910884.htm#fromView=search&amp;page=2&amp;position=17&amp;uuid=15310b64-35f7-4014-90b9-534aa77b6f61&amp;query=agile+product+development">Image by Freepik</a></figcaption></figure><p>You don’t need to abandon agile to fix it. You need to remember what made it work in the first place.</p><p>Here are five small habits that keep agile grounded:</p><ol><li><strong>Plan small, but plan.</strong><br>Agile still needs intention. Define a clear sprint goal, not just a list of tickets.</li><li><strong>Let research guide iteration.</strong><br>Moving fast is fine, but moving fast on the wrong assumptions just multiplies rework.</li><li><strong>Balance flexibility with accountability.</strong><br>Pivots are healthy when they’re backed by insight, not panic.</li><li><strong>Document the thinking, not the ceremony.</strong><br>You don’t need long reports, just shared notes that capture context beyond the meeting.</li><li><strong>Protect focus.</strong><br>Every new idea doesn’t need to make the next sprint. Velocity without value is noise.</li></ol><h3>The Real Meaning of Agile</h3><p>Agile was never meant to be chaos. It was meant to be clarity through movement.</p><p>When done right, it helps teams adapt without losing sight of what matters. When done wrong, it becomes a shield for poor planning, weak communication, and short-term thinking.</p><p>True agility isn’t about constant motion. It’s about <em>controlled movement, </em>small, intentional steps in the right direction.</p><blockquote>Because moving fast means nothing if you don’t know where you’re headed.</blockquote><p>Agile isn’t the problem. The way we hide behind it is!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0a727d98f79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/when-agile-becomes-an-excuse-for-chaos-c0a727d98f79">When Agile Becomes an Excuse for Chaos</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[The Validation Mirage: Why Most “User Feedback” Isn’t What You Think]]></title>
            <link>https://medium.com/charisol-pulse/the-validation-mirage-why-most-user-feedback-isnt-what-you-think-9786dbf50134?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9786dbf50134</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Wed, 29 Oct 2025 15:02:24 GMT</pubDate>
            <atom:updated>2025-10-29T15:02:24.662Z</atom:updated>
            <content:encoded><![CDATA[<p>Every startup claims to listen to its users.</p><p>Yet somehow, users keep leaving.</p><p>The problem isn’t that teams aren’t collecting feedback; it’s that they’re mistaking agreement for insight. Most of what’s called <em>validation</em> today is really just <strong><em>confirmation </em></strong>in disguise.</p><figure><img alt="A couple of sticky notes pinned to a board, with the contents of the majority blurred out" src="https://cdn-images-1.medium.com/max/1024/0*rL-mIxiN1L8psmWl" /><figcaption>Photo by <a href="https://unsplash.com/@patrickperkins?utm_source=medium&amp;utm_medium=referral">Patrick Perkins</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s a comforting illusion: you run a few interviews, get nods of approval, and feel confident you’re on the right path. But validation isn’t about making you feel better; it’s about helping you see more clearly.</p><p>And this is where most teams stumble.</p><p>We say we’re validating, but often, we’re just looking for confirmation. The more effort we put into something, the more we want the world to agree it’s worthwhile. That’s why early user research, prototype testing, or survey responses can feel reassuring, even when they’re misleading.</p><h3>What’s Going Wrong</h3><p>Honestly, if you ask me, I think many teams approach validation with the best intentions. They actually want to learn. They want to listen. But somewhere between enthusiasm and execution, the goal quietly shifts.</p><ul><li>They run user interviews, hoping to <em>validate</em> their idea, but lead the questions toward the answers they want.</li><li>They test prototypes to “<em>prove usability</em>”, but never pause to ask whether the concept itself makes sense.</li><li>They celebrate every “<em>This looks great</em>”, but miss the hesitation before it.</li></ul><p><a href="https://medium.com/charisol-pulse/the-mvp-trap-when-fast-isnt-always-smart-860df5957802">In a recent piece</a>, I talked about how the <em>‘</em><strong><em>V</em></strong><em>’</em> in MVP often gets lost in the rush to launch. But the problem starts even earlier, in how teams decide what’s <strong><em>viable </em></strong>in the first place. Because before we build the wrong thing fast, we often validate the wrong thing well.</p><p>And that’s the real trap.</p><figure><img alt="A table comparing validation against truth, outlining the difference between the two." src="https://cdn-images-1.medium.com/max/1024/1*BBVC0V9-DnKle8TDKByzYQ.jpeg" /></figure><h3>Why It Matters</h3><p>This kind of false validation doesn’t just slow teams down; it warps their confidence.</p><p>When feedback becomes flattery, you start investing in ideas that don’t hold up. You pour time and energy into fixing the wrong things, all while missing what truly matters.</p><p>And the impact stacks up:</p><ul><li><strong>False confidence:</strong> Teams double down on weak ideas.</li><li><strong>Wasted sprints:</strong> You fix what didn’t need fixing.</li><li><strong>User fatigue:</strong> People stop sharing honest feedback because nothing changes.</li><li><strong>Missed insights:</strong> The real problems stay buried under polite answers.</li></ul><p>When you chase validation instead of truth, you end up building products that look right — until they meet reality.</p><p>Because real validation doesn’t come from users saying, “<em>I like it</em>.” It comes from observing what they actually do, how they struggle, what they skip, and where they pause.</p><h3>How to Break the Cycle</h3><p>If you want feedback that’s useful, not just pleasant, you have to treat validation as discovery, not confirmation. You don’t need fancy frameworks or new jargon, just <a href="https://medium.com/charisol-pulse/building-for-usability-7-small-habits-for-creating-products-people-love-b054f3d00465">better habits</a>.</p><figure><img alt="An illustration of the biased validation cycle, starting from Idea to Leading question to Positive feedback to False confidence and cycling back to Idea." src="https://cdn-images-1.medium.com/max/1024/1*iccaqnxBgtH89dN-F-XgbQ.jpeg" /><figcaption>The Biased Validation Cycle</figcaption></figure><p>Here are a few that work:</p><ol><li><strong>Ask open-ended, neutral questions.</strong><br>Not “<em>Would you use this?</em>” but “How would this fit into what you already do?” You’re not looking for approval, you’re looking for context.</li><li><strong>Watch what people do, not just what they say.</strong><br>Humans are fickle; they say one thing and do another. So instead of taking them at their word, observe their behavior.</li><li><strong>Separate desirability from usability.</strong><br>Someone liking an idea doesn’t mean they’ll use it or pay for it. Those are different kinds of validation.</li><li><strong>Look for hesitation, not enthusiasm.</strong><br>The pauses, frowns, and “<em>um…”</em> moments are where truth hides. Watch what users do, not just what they say.</li><li><strong>Document assumptions before testing.</strong><br>You can’t validate what you haven’t defined. Write down what you <strong><em>think users </em></strong>want before you test, then check if the results actually support it.</li><li><strong>Reframe validation as discovery.</strong><br>The goal isn’t to confirm what you think or prove your idea is right; it’s to learn what is missing.</li></ol><h3>Closing Thought</h3><p>Validation isn’t proof; it’s interpretation. And if that interpretation starts from bias, excitement, or the desire to confirm what we already believe, then all our “<em>user signals</em>” are just reflections of ourselves.</p><blockquote>Because feedback isn’t truth, until you learn to hear what’s not being said.</blockquote><p>Real validation doesn’t sound like applause, as much as you might want it to. It sounds like questions, friction, and sometimes, uncomfortable truth. In simple terms, real validation isn’t when users agree with you; it’s when they teach you something you didn’t expect.</p><p><em>What we build starts with </em><strong><em>why </em></strong><em>we build it.</em> See our process at <a href="https://charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=The+Validation+Mirage"><strong>Charisol.io</strong></a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9786dbf50134" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/the-validation-mirage-why-most-user-feedback-isnt-what-you-think-9786dbf50134">The Validation Mirage: Why Most “User Feedback” Isn’t What You Think</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[The MVP Trap: When Fast Isn’t Always Smart]]></title>
            <link>https://medium.com/charisol-pulse/the-mvp-trap-when-fast-isnt-always-smart-860df5957802?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/860df5957802</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Thu, 16 Oct 2025 15:02:22 GMT</pubDate>
            <atom:updated>2025-10-16T15:02:22.799Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone wants to move fast.</p><p>Founders love momentum. Teams crave progress. The phrase <em>“ship early, ship often”</em> sounds like a badge of honor.</p><p>But I’ve watched that same speed turn into rework, user confusion, and endless hotfixes. The MVP was meant to save time, yet somehow, it keeps costing teams more.</p><p>Because somewhere along the line, we forgot what the “<strong>V</strong>” stands for.</p><figure><img alt="A chart showing the difference between building for validation and building for speed" src="https://cdn-images-1.medium.com/max/1024/1*OqhGJjiwjX7D3eLNQHQSUg.jpeg" /><figcaption>The MVP Trap (Validation vs. Speed)</figcaption></figure><h3>What an MVP Is (and Isn’t)</h3><p>The MVP was never about building <em>less</em>. It was about learning <em>faster</em>. Its purpose is to test a clear assumption, not to ship a half-finished product and call it progress.</p><p>When speed becomes the goal instead of understanding, teams start skipping the thinking.</p><ul><li>They build features no one asked for.</li><li>They launch without knowing what success looks like.</li><li>They collect feedback they can’t make sense of.</li></ul><blockquote><strong>It’s not that they didn’t move fast. It’s that they moved blind.</strong></blockquote><figure><img alt="An open book showing a chapter on building a minimum desirable product" src="https://cdn-images-1.medium.com/max/1024/0*yhRb6zgRaCR5lWFp" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Real Cost of Rushing</h3><p>Startups often pay for “<em>fast</em>” with something far more expensive later: <strong>trust</strong>.</p><ul><li>Users don’t come back when their first experience feels broken.</li><li>Teams burn out fixing the same usability issues that should’ve been caught earlier.</li><li>And instead of learning from real users, everyone ends up defending decisions they made in a hurry.</li></ul><p>What was supposed to be <em>lean</em> becomes <em>looped; </em>a cycle of patching, guessing, and hoping.</p><p>Dropbox could have made that mistake, too. But rather than rushing to code a cloud storage system, they created a short demo video explaining how it <em>would </em>work. The video went viral overnight, pulling in thousands of sign-ups, all before a single line of backend logic existed.</p><p>That simple test proved there was real interest and gave them clarity before they invested heavily in development.<strong> They moved fast, but smart — </strong>a strong reminder that validation is the real speed.</p><h3>How to Build Smarter MVPs</h3><p>A smarter MVP doesn’t start with features; it begins with learning. Airbnb did this brilliantly. Before building any platform, they rented out their own apartment to test whether people would pay to stay in someone else’s home. They took photos themselves, listed the space, welcomed guests, and learned from the experience. That scrappy experiment validated demand before they scaled.</p><p>As a founder, there’s a better way to move fast, and that’s by staying intentional. Here are a few ways to avoid the MVP trap:</p><figure><img alt="A circular chart that shows the flow of a smart MVP cycle: Define → Learn → Adjust → Ship" src="https://cdn-images-1.medium.com/max/1024/0*aQ78N6Z1PxPHITsW" /><figcaption>The Smart MVP Cycle (Define → Learn → Adjust → Ship)</figcaption></figure><h4><strong>1. Start with one clear question</strong></h4><p>What problem are we validating? Not what do we want to <em>build</em>, but what do we want to <em>understand </em>and <em>why</em>.</p><h4><strong>2. Map the smallest experience, not the smallest product</strong></h4><p>An MVP isn’t a skeleton. It should still make sense to a real person using it for the first time.</p><h4><strong>3. Validate early, not after launch</strong></h4><p>Talk to five people. Watch them interact with your prototype. It’s faster than rebuilding later.</p><h4>4. Avoid perfection paralysis</h4><p>Get enough clarity to move to the next step — not more, not less.</p><h4><strong>5. Define what learning looks like</strong></h4><p>If you can’t tell what success or failure means for your <strong>MVP</strong>, you’re just shipping and waiting.</p><h3>Closing Thought</h3><p>Speed only matters when you’re moving in the right direction.</p><blockquote>The goal of an MVP isn’t to launch fast; it’s to learn fast.</blockquote><p>Think of it as a discipline, and not a shortcut. Because if you’re sprinting without clarity, you’re not innovating. You’re just running in circles.</p><p>And in the end, the smartest teams aren’t the fastest; they are the ones who learn the quickest!</p><p><em>We help teams uncover the right problems before rushing to solutions.</em> Explore our process at<strong> </strong><a href="https://charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=The+MVP+Trap"><strong>Charisol.io</strong></a><strong>!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=860df5957802" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/the-mvp-trap-when-fast-isnt-always-smart-860df5957802">The MVP Trap: When Fast Isn’t Always Smart</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[Building for Usability: 7 Small Habits for Creating Products People Love]]></title>
            <link>https://medium.com/charisol-pulse/building-for-usability-7-small-habits-for-creating-products-people-love-b054f3d00465?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b054f3d00465</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 15:02:49 GMT</pubDate>
            <atom:updated>2025-09-30T15:02:49.730Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building for Usability — 7 Small Habits for Creating Products People Love</h3><p>When people talk about building products, the focus usually falls on the big things: shipping features, meeting deadlines, and scaling growth. Those matters, but from experience, what makes a product <strong><em>usable</em> </strong>rarely comes down to one big move. It’s the small habits teams keep (or ignore) every day.</p><figure><img alt="An open page of a book differentiating between an MVP (Minimum Viable Product) and an MDP (Minimum Desirable Product). And why an MDP should be the go-to." src="https://cdn-images-1.medium.com/max/1024/0*alqRaNVE5-zL6W0J" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’ve sat in rooms where a product looked perfect on paper. Innovative features, solid flows, all the boxes ticked. But once it reached real people, things fell apart. A button wasn’t where users expected it. The language felt stiff and robotic. A simple step required unnecessary explanation. These weren’t massive failures; they were tiny gaps that piled up until users gave up.</p><p>That’s when it became clear to me: usability isn’t one big decision. It’s a series of small habits, repeated over and over. Here are a few that stand out.</p><h3>1. Asking “Who is this for?” early and often</h3><p>It’s easy to get caught up in features, roadmaps, and deadlines. However, every useful product begins with a clear understanding of the person who will use it. Teams that pause, even briefly, to ask, <em>“Who is this really for?”</em> tend to build with more clarity and fewer assumptions.</p><p>In one project, a team I worked with had been going back and forth on adding new onboarding steps. The conversation shifted the moment someone asked, “<em>But who exactly is struggling with onboarding right now?</em>” That one question cut through the noise and redirected the effort to solving a real issue, rather than piling on extra steps.</p><h3>2. Writing things down, even if it’s rough</h3><p>Notes from a call. A quick research summary. A list of pain points. Documentation doesn’t have to be polished to be useful.</p><p>Teams that capture their thinking as they go avoid the trap of relying on memory or assumptions. It also makes collaboration smoother, because context doesn’t live in one person’s head.</p><h3>3. Testing before you’re ready</h3><p>Usability isn’t something you tack on at the end. It’s something you surface early. The teams that get this right don’t wait for pixel-perfect designs. They put scrappy prototypes in front of people and let feedback guide their direction.</p><p>I’ve once tested a half-finished flow with just clickable wireframes. The feedback we received wasn’t about colors or visuals; no surprises there, because that wasn’t our focus. We were more concerned about ease of use, and what surfaced during that test was confusion in the steps. Catching those early saved weeks of work later.</p><figure><img alt="Rough pencil sketches of screens" src="https://cdn-images-1.medium.com/max/1024/0*SQ3GoB7n8hSfuQqz" /><figcaption>Photo by <a href="https://unsplash.com/@halacious?utm_source=medium&amp;utm_medium=referral">Hal Gatewood</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>4. Listening more than you speak</h3><p>In user interviews or product reviews, the temptation is to talk, justify, or defend. But the teams that build usable products are the ones who practice listening. They resist the urge to fill silences. They ask follow-ups. They let users show them, not just tell them.</p><h3><strong>5. Choose plain words over technical terms.</strong></h3><p>In one project, the login error message originally read, <em>“Authentication credentials invalid</em>.”</p><p>Accurate? Yes.</p><p>Helpful? Not at all.</p><p>So we changed it to <em>“Your email or password is incorrect”.</em> Same functionality, but completely different experiences after the user interacts with them. This demonstrated to us the habit of writing for people, not for systems. Using everyday language in buttons, instructions, and alerts prevents unnecessary friction.</p><h3>6. <strong>Ask, “Can someone understand this without help?”</strong></h3><p>A quick gut check before shipping anything is to step back and see if the interface or flow makes sense without explanation. If the design needs a guide, it’s probably too complex. Teams that do this regularly identify confusing points earlier, rather than waiting until users complain.</p><h3><strong>7. Value consistency more than novelty.</strong></h3><p>There’s always a temptation to “<em>wow</em>” users with something new. I’ve seen teams introduce quirky design twists that looked brilliant in isolation but clashed with the rest of the product. Users ended up confused rather than impressed.</p><figure><img alt="A monitor showing a myriads of applications" src="https://cdn-images-1.medium.com/max/1024/0*xMGd94PUAQYvGFEH" /><figcaption>Photo by <a href="https://unsplash.com/@writecodenow?utm_source=medium&amp;utm_medium=referral">Boitumelo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Over time, we learned that people rarely thank you for novelty, but they always appreciate consistency. They like knowing where things are, how they’ll work, and that yesterday’s pattern still holds today. The habit of choosing consistency — boring as it sounds — keeps products usable in ways flashy features can’t.</p><p>These aren’t groundbreaking practices, and that’s the point. Usability doesn’t come from grand strategies; it grows from the quiet, consistent habits of how teams design, write, test, and communicate.</p><p>When teams treat these small things as part of their everyday work, people feel it. Products feel easier. And that ease, that quiet sense that “<strong><em>this just works</em></strong>”, is what makes people stick around.</p><p><em>What we build starts with </em><strong><em>why </em></strong><em>we build it.</em> See our process at <a href="https://charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Building+with+People"><strong>Charisol.io</strong></a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b054f3d00465" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/building-for-usability-7-small-habits-for-creating-products-people-love-b054f3d00465">Building for Usability: 7 Small Habits for Creating Products People Love</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[User Research for Startups: Essential Methods to Start With]]></title>
            <link>https://medium.com/charisol-pulse/user-research-for-startups-essential-methods-to-start-with-9062091b5430?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9062091b5430</guid>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Thu, 11 Sep 2025 15:01:54 GMT</pubDate>
            <atom:updated>2025-09-11T15:01:54.242Z</atom:updated>
            <content:encoded><![CDATA[<p>Startups don’t always have the time, budget, or people to run full-scale research programs. But that doesn’t mean research has to wait until the team “<em>grows up</em>”. Some of the most valuable methods are simple, low-cost, and can fit right into the early chaos of building a product.</p><figure><img alt="Sticky notes on a wall with common research methods" src="https://cdn-images-1.medium.com/max/1024/0*yY8TuTWSFHDpgQXj" /><figcaption>Photo by <a href="https://unsplash.com/@dtravisphd?utm_source=medium&amp;utm_medium=referral">David Travis</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Over the past few years, I’ve seen that the challenge isn’t access to tools. It’s knowing <em>which methods to start with</em> and <em>how to use them without slowing things down</em>. Here are a few I recommend to any early-stage team.</p><h3>1. User Interviews</h3><p>Talking to people sounds obvious, but it’s often skipped in the rush to build. A handful of well-structured conversations can save weeks of assumptions.</p><figure><img alt="A picture of two people having a conversation depicting user interview" src="https://cdn-images-1.medium.com/max/1024/0*5-kx2OnjFXCK3QF2" /><figcaption>Photo by <a href="https://unsplash.com/@wocintechchat?utm_source=medium&amp;utm_medium=referral">Christina @ wocintechchat.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ul><li><strong>When to use it:</strong> At the idea stage, or when you’re trying to validate a problem.</li><li><strong>What it gives you:</strong> Context, motivations, and the “<strong><em>why</em></strong>” behind behavior.</li></ul><p><strong>Pro tip:</strong> Keep it short. Even five interviews can highlight patterns worth paying attention to.</p><h3>2. Usability Testing</h3><p>If you already have a prototype, or even just wireframes, watching someone use it is eye-opening. The gap between what we <em>think</em> is intuitive and what people actually do can be wide.</p><figure><img alt="A man trying to navigate an application on his mobile phone, depicting usability testing" src="https://cdn-images-1.medium.com/max/1024/0*HiM8BE-8PcZMiP3g" /><figcaption>Photo by <a href="https://unsplash.com/@disruptxn?utm_source=medium&amp;utm_medium=referral">Desola Lanre-Ologun</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ul><li><strong>When to use it:</strong> Before launch, during iteration, or when usage drops after release.</li><li><strong>What it gives you:</strong> Evidence of friction, confusion, and design opportunities.</li></ul><p>This doesn’t need labs or fancy software. A Zoom call and screen share often do the job.</p><h3>3. Industry Research</h3><p>Every product operates in a larger context. Industry research keeps you grounded in the bigger picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z1STSUZC5Xuk339P" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ul><li><strong>When to use it:</strong> When you’re entering a new market or planning your positioning.</li><li><strong>What it gives you:</strong> Trends, market forces, growth potential, and consumer preferences.</li></ul><p>Scan industry reports, publications, and market intelligence platforms. Note where the market is heading and identify gaps that bigger players overlook.</p><h3>4. Surveys (Done Right)</h3><p>Surveys are tempting because they feel scalable, but they can backfire if they’re vague or too long. Keep them targeted; straight-to-the-point, clear questions, no jargon.</p><figure><img alt="A screen showing online survey participation" src="https://cdn-images-1.medium.com/max/1024/0*BGMW9zpeVUvGDQig" /><figcaption>Photo by <a href="https://unsplash.com/@moneywise?utm_source=medium&amp;utm_medium=referral">Moneywise</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ul><li><strong>When to use it:</strong> To measure satisfaction, prioritize features, or spot trends across a group.</li><li><strong>What it gives you:</strong> A breadth of perspective to complement the depth you gain from interviews.</li></ul><p>A simple survey of your beta users can reveal what matters most, rather than what’s loudest in the room.</p><h3>5. Competitor Analysis</h3><p>You’re not the first to try solving your problem. Looking at how others approach similar challenges can save you from reinventing the wheel.</p><figure><img alt="A visual representation of competitor’s analysis" src="https://cdn-images-1.medium.com/max/1024/0*1_lS-IvcAWjLH1ef" /><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><ul><li><strong>When to use it:</strong> Before building, when exploring a new feature, or when you want inspiration.</li><li><strong>What it gives you:</strong> A sense of patterns, best practices, and opportunities to differentiate.</li></ul><p>Sometimes, a quick teardown of three competitor flows tells you more than a deck of “best practices”.</p><h3>6. Social Media Listening</h3><p>People are honest online in ways they won’t be in an interview. Social platforms are a goldmine of unfiltered thoughts.</p><figure><img alt="Icons of popular social media application" src="https://cdn-images-1.medium.com/max/1024/0*5cZ-H5xiawJ-8tct" /><figcaption>Photo by <a href="https://unsplash.com/@shutter_speed_?utm_source=medium&amp;utm_medium=referral">Shutter Speed</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ul><li><strong>When to use it:</strong> To spot emerging pain points, monitor competitors, or understand how people talk about your space.</li><li><strong>What it gives you:</strong> Real user language, complaints, celebrations, and comparisons.</li></ul><p>Follow conversations on platforms your audience uses. Monitor hashtags, communities, or competitor mentions. Note recurring frustrations and language patterns, you’ll learn both what matters and how people describe it.</p><h3>7. Analytics</h3><p>You don’t need a whole data team to learn from product usage. A few key numbers, such as where users drop off during signup or how many return after the first session, can guide next steps.</p><figure><img alt="A screen with data and charts depicting analytics" src="https://cdn-images-1.medium.com/max/1024/0*3hXWk9wNSbEQBneL" /><figcaption>Photo by <a href="https://unsplash.com/@hostreviews?utm_source=medium&amp;utm_medium=referral">Stephen Phillips — Hostreviews.co.uk</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ul><li><strong>When to use it:</strong> Post-launch, or any time you want to measure impact.</li><li><strong>What it gives you: </strong>Guidance on what to investigate next.</li></ul><p>Numbers on their own don’t tell the whole story, but they highlight where to look closely with qualitative methods.</p><h3>Final Note</h3><p>Early-stage research doesn’t have to be overwhelming. Start with a couple of these methods and keep them lightweight. The goal isn’t perfect data; it’s learning enough to make better decisions and move forward with confidence.</p><blockquote>Because when you strip it down, research is just structured curiosity. And curiosity is something every startup can afford.</blockquote><p><em>Curious how we turn insights into real products?</em> Explore what we do at <a href="https://charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=Researcher%27s+Toolbox"><strong>Charisol.io</strong></a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9062091b5430" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/user-research-for-startups-essential-methods-to-start-with-9062091b5430">User Research for Startups: Essential Methods to Start With</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[Notes from a UX Researcher: What They Don’t Tell You About Scaling]]></title>
            <link>https://medium.com/charisol-pulse/notes-from-a-ux-researcher-what-they-dont-tell-you-about-scaling-da27687adfbd?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/da27687adfbd</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Wed, 20 Aug 2025 14:02:06 GMT</pubDate>
            <atom:updated>2025-08-20T14:02:06.711Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Nobody tells you what it feels like to scale a research team.</blockquote><p>Sure, there are plenty of articles about hiring, building ops, or setting up frameworks. But the actual day-to-day? The in-between? It’s a bit messier than the case studies make it seem.</p><p>Some days, I’m setting up a discovery process from scratch for a product that’s still taking shape. Other days, I’m helping a teammate troubleshoot a usability test, reviewing research plans, or rewriting documentation so it actually gets read. And in the middle of all that, trying to carve out space to think strategically while still being deeply in the weeds.</p><figure><img alt="A collage-like illustration where different small panels depict moments in research: conducting interviews, analyzing data, brainstorming, sharing insights." src="https://cdn-images-1.medium.com/max/1024/1*SdSrkCHPXSfGSsmsXoy6zg.png" /><figcaption>UX Research Moments (Generated with ChatGPT)</figcaption></figure><p>It’s a mix of progress, process, and a lot of learning on the go.</p><p>By the way, this isn’t a step-by-step guide to scaling UX research. It’s a window into the things they don’t tell you — the parts I’ve had to figure out along the way. If you’re navigating similar waters, maybe this will feel familiar.</p><h3>The Myth of Scaling</h3><p>When people talk about “<strong><em>scaling</em></strong>”, it sounds big — like adding more researchers, rolling out sophisticated systems, or automating half your workflow with Notion and Airtable.</p><p>And while those things <em>can</em> be part of it, they’re not the whole story. In real life, scaling often looks like:</p><ul><li>Choosing <strong>depth over breadth</strong>, even when others want “just a quick survey”.</li><li>Saying <strong>no</strong> to one more project request to prevent your team from burning out.</li><li>Repeating the same explanation about research timelines to different stakeholders, with patience 🙄.</li><li>Fighting the subtle pressure to always be <strong><em>doing more</em></strong> instead of doing what matters.</li></ul><p>It’s easy to feel like you’re not scaling “right” when your process isn’t sleek or your team isn’t growing fast. But the truth is: scaling is just as much about <strong>increasing capacity </strong>and <strong>clarity</strong> as it is about adding headcount.</p><p>Some of our most significant shifts didn’t come from hiring or tooling up. They came from conversations, priorities, and rethinking how we spent our time.</p><h3>The Reality of Leading a Small (but Mighty) Team</h3><p>Right now, I lead a team of four: two junior researchers and two interns.</p><p>It’s a compact team, but a committed one. And honestly, leading a small research team comes with its own rhythm — one that’s more personal, more hands-on, and sometimes, more demanding.</p><p>I’ve learned that:</p><ul><li><strong>Coaching is daily</strong>, not just during feedback sessions. It happens in Google Chat/WhatsApp messages, in shared docs, in post-call debriefs.</li><li><strong>Context matters</strong> — a lot. What feels obvious to me as the lead isn’t always clear to someone new to research or the company.</li><li><strong>Trust is built through small wins</strong>, not just big moments. Helping someone successfully run their first moderated session is just as important as delivering a cross-functional report.</li></ul><p>There’s also the balance — being a lead while still being an individual contributor. Knowing when to <em>step in</em>, when to <em>step back</em>, and when to just listen.</p><p><strong>What makes it worth it?</strong></p><p>Seeing the team grow. Watching someone who was nervous about stakeholder interviews go on to confidently present insights in a product meeting — that’s the kind of progress that doesn’t show up in dashboards, but it’s the kind that matters.</p><figure><img alt="A digital illustration of a small team gathered around a desk, brainstorming with sticky notes, laptops open, and one person guiding the discussion." src="https://cdn-images-1.medium.com/max/1024/1*_P7E-_kQKR1YkFUC3knc8w.png" /><figcaption>A small team brainstorming (Generated with ChatGPT)</figcaption></figure><h3>What’s Working (So Far)</h3><p>We’re still learning as we go, but a few things have helped us stay grounded and effective as a team:</p><ul><li><strong>Biweekly research syncs</strong>: Just an hour to share what we’re working on, what we’re stuck on, and what we’re learning. It keeps us aligned without overwhelming anyone.</li><li><strong>Lightweight templates</strong>: From research plans to synthesis boards, we created simple templates that save us from reinventing the wheel every time. It helps the juniors move faster and makes quality easier to maintain.</li><li><strong>A shared resource hub</strong>: Articles, decks, checklists — even past mistakes. It’s our little library of context, and it’s been surprisingly helpful, especially for onboarding interns or catching someone up quickly.</li><li><strong>Clear project leads</strong>: Every project has a lead researcher, even if it’s not me. This builds ownership and gives each team member a chance to practice leading without being overwhelmed.</li><li><strong>Encouraging “show and tell”</strong>: We make space to present unfinished work. It reduces pressure, sparks discussion, and helps everyone learn — especially from the messy middle of research.</li></ul><p>None of these is groundbreaking. But they’ve made our team feel more connected, more confident, and more capable of handling real research work.</p><p><strong>And that’s a win 🏆.</strong></p><h3>The Parts I’m Still Figuring Out</h3><p>As much as I’d love to say we’ve got it all figured out, we absolutely don’t. Leading a team comes with its own share of “<em>I-hope-this-works</em>” moments, and I’m learning to be okay with that.</p><p>Here’s what I’m still navigating:</p><ul><li><strong>Balancing hands-on work with leadership</strong><br>Sometimes I’m deep in research myself, other times I’m reviewing someone else’s. Switching hats constantly — from contributor to coach — is hard. I’m learning to trust the team more and not jump in too quickly.</li><li><strong>Giving feedback that helps, not hinders</strong><br>It’s easy to correct. It’s harder to guide. I don’t want to edit people’s work into my voice; I want to help them grow into theirs. That’s still a muscle I’m building.</li><li><strong>Protecting focus</strong><br>We’re a small team with big demands, and the “<em>just one quick question</em>” moments add up fast. I’m learning that being available doesn’t mean being interrupted all day.</li><li><strong>Being okay with doing things differently</strong><br>Not everything I’ve read in “how to lead” books applies to our context. Sometimes we need to create our own ways of working, and that’s both freeing and uncomfortable.</li></ul><blockquote><strong>Truth is, leading a research team isn’t a tidy checklist.</strong></blockquote><p>It’s a bit messy.</p><p>It’s deeply human.</p><p>And it’s filled with small decisions that add up, even if no one else sees them.</p><figure><img alt="A cartoon-style illustration showing a person (a research team lead) juggling multiple roles." src="https://cdn-images-1.medium.com/max/1024/1*oq6-Td1S7LODRVKrUkEmVQ.png" /><figcaption>Different roles of a research team lead (Generated with ChatGPT)</figcaption></figure><p>I didn’t write this because I have all the answers (sorry to disappoint you if you hoped otherwise). I wrote it because sometimes, what we need most as team leads is a reminder that we’re not alone in the figuring-it-out.</p><p>Leading a UX research team — especially in a growing company — isn’t about perfection. It’s about clarity, care, and constant learning. It’s about asking better questions, offering support without smothering, and remembering that the work <em>we</em> do helps everyone else do <em>their</em> work better.</p><p>So if you’re also in this seat; leading, learning, and navigating the unknown, I see you.</p><p><strong>You’re doing better than you think.</strong></p><p>Let’s keep building what doesn’t exist yet. And keep showing up, even when it’s messy.</p><p><a href="https://charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=leadingaresearchteam">Home - Charisol | End to End Product Development</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da27687adfbd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/notes-from-a-ux-researcher-what-they-dont-tell-you-about-scaling-da27687adfbd">Notes from a UX Researcher: What They Don’t Tell You About Scaling</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[The Afterlife of UX Research: How to Ensure Insights Lead to Action]]></title>
            <link>https://medium.com/charisol-pulse/the-afterlife-of-ux-research-how-to-ensure-insights-lead-to-action-10e76fcf1744?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/10e76fcf1744</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Tue, 22 Jul 2025 11:01:54 GMT</pubDate>
            <atom:updated>2025-07-22T11:15:44.437Z</atom:updated>
            <content:encoded><![CDATA[<h4>What you do after the research matters as much as the study itself</h4><p>You finished the research. The insights are clear. The deck is polished. You even held a readout.</p><p>And then… silence.</p><p>No follow-up questions. No visible shift in direction.</p><p>The team moved on, and your research quietly disappeared.</p><p><strong><em>Sound familiar?</em></strong></p><figure><img alt="Illustration of a female researcher handing a document to a male colleague in an office. She is smiling and saying “Done,” while the colleague accepts the paper, symbolizing a project handoff." src="https://cdn-images-1.medium.com/max/1024/1*UYbFwm5KVjvnxrRZtaTYMQ.png" /><figcaption>“Done!” But is it really? (Generated with ChatGPT)</figcaption></figure><p>Many teams treat research like a transaction:</p><p>Ask question → run study → deliver report → done.</p><p>But research isn’t a package. It’s a process, and the real work often begins after the “delivery”.</p><blockquote>If insights don’t connect to action, we haven’t finished the job.</blockquote><h3>So, What Should Happen After the Research?</h3><p>Post-research is where things can break down — or break through. Here’s what happens when we don’t plan for what comes next:</p><ul><li>Insights go unread or misunderstood</li><li>Decisions get made without the full context</li><li>Learnings fade, even if they were valuable</li></ul><p>Without <strong>follow-through</strong>, even great research becomes shelfware.</p><h4>How I’m Rethinking the “After”</h4><p>After carrying out a research study, I started asking myself:</p><ul><li>What does success look like <em>after</em> the readout?</li><li>Who’s responsible for making insights stick?</li><li>How do we (the research team) support action, not just understanding?</li></ul><p>Asking these questions led us to a few intentional shifts</p><figure><img alt="A cartoon-style illustration of a researcher presenting a report to two team members. The presenter is animated and holding a clipboard, while one of the team members casually responds with “Cool,” showing minimal engagement." src="https://cdn-images-1.medium.com/max/1024/1*Enfbe4s2ignsvd9GllFa_Q.png" /><figcaption>The report was clear. The response? Not so much. (Generated with ChatGPT)</figcaption></figure><h3>What We Now Do Differently</h3><p><strong>1. Follow-Up Sessions (Not Just Readouts): </strong>Instead of a one-time presentation, we now schedule follow-ups to explore the application of the findings, asking:</p><blockquote>How does this insight affect our roadmap, copy, or design direction?</blockquote><p><strong>2. Co-Creation Over Broadcast: </strong>We don’t just “present” findings anymore. Now, we involve teams in applying them — building frameworks, personas, and decision guides <em>together</em>.</p><p><strong>3. Insight Tracking:</strong> We track how and where key findings show up in future work. <em>Was it used in a feature brief, user story, or onboarding flow?</em> It helps us learn what sticks — and what gets lost.</p><p><strong>4. Create “Insight Anchors”: </strong>We distill findings into short, sticky formats (e.g., 1-pagers, quotes, top 3 takeaways) that teams can revisit quickly, especially during planning cycles.</p><h3>Why It Matters</h3><p>Research isn’t done when the study ends. It’s done when the insight shapes something real — a product decision, a strategy shift, a clearer “no”.</p><p>And that means designing for what happens <em>after</em>.</p><blockquote>Because lasting impact doesn’t come from what we <em>present</em> — it comes from what people <em>remember</em> and use.</blockquote><p>If you want your research to matter, don’t stop at the report. Design the afterlife of your insight.</p><p>That’s where real influence begins.</p><p>From insight to product-market fit — we’re with you all the way. <a href="https://www.charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=aftertheresearch"><strong><em>Explore our process</em></strong></a><strong><em>!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10e76fcf1744" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/the-afterlife-of-ux-research-how-to-ensure-insights-lead-to-action-10e76fcf1744">The Afterlife of UX Research: How to Ensure Insights Lead to Action</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[How Ready Are Teams for AI?]]></title>
            <link>https://medium.com/charisol-pulse/how-ready-are-teams-for-ai-fda3560eeaf6?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fda3560eeaf6</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[organizational-change]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 10:02:07 GMT</pubDate>
            <atom:updated>2025-07-09T10:02:07.788Z</atom:updated>
            <content:encoded><![CDATA[<h4>Assessing AI readiness by asking better questions</h4><p>Before rolling out AI tools across teams, we needed to ask a more fundamental question:</p><blockquote>Are our teams even ready for AI, and where would it help?</blockquote><p>The hype around AI is loud. But real transformation doesn’t start with tools. It starts with understanding how people work, where they struggle, and what support would truly make a difference.</p><figure><img alt="The word “AI” followed by a question mark" src="https://cdn-images-1.medium.com/max/1024/0*9ykGu967xh4ua512" /><figcaption>Photo by <a href="https://unsplash.com/@nahrizuladib?utm_source=medium&amp;utm_medium=referral">Nahrizul Kadri</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Why We Didn’t Start by Introducing AI Tools</h4><p>We weren’t chasing trends or piloting the latest AI platforms. We started by asking: <strong>Where are our teams wasting time and energy?</strong></p><p>Our belief: If we don’t understand the real <em>friction </em>in workflows, we can’t apply the right solutions — AI or otherwise.</p><h3>Our Approach</h3><p>We launched a company-wide survey to uncover:</p><ul><li>Which tasks feel repetitive or tedious?</li><li>Where do processes slow people down?</li><li>What gets in the way of focus or progress?</li></ul><p>We grouped the responses by team and prioritized based on:</p><ul><li>Frequency of the issue</li><li>Time cost, and</li><li>Perceived frustration.</li></ul><blockquote>“We didn’t ask about AI tools at first. We asked about pain. Then we looked at patterns.”</blockquote><h4>What We Found</h4><p>Our teams are working hard, but wasting energy on the wrong things. We realized that almost every team had a clear pattern of repeated, high-friction tasks:</p><ul><li>UX researchers were buried in transcription and synthesis</li><li>Product managers were overwhelmed by documentation and updates</li><li>Operations teams were swamped with meeting and tracking tasks</li><li>Sales was spending hours on manual outreach</li><li>And the list went on…</li></ul><p>These weren’t glamorous problems. But they were real. And they were holding teams back.</p><figure><img alt="Sticky notes being pinned to a board" src="https://cdn-images-1.medium.com/max/1024/0*uibYT8qUYHHphGbl" /><figcaption>Photo by <a href="https://unsplash.com/@patrickperkins?utm_source=medium&amp;utm_medium=referral">Patrick Perkins</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What That Tells Us About AI Readiness</h3><p>Here’s what we learned about readiness:</p><ul><li>Teams are <strong>open to help</strong>, but they are not all sure where AI fits</li><li>Most people want <strong>support</strong>, not <strong>replacement</strong></li><li>Readiness depends not on hype, but on <strong>fit — </strong>how well a solution targets a real problem.</li></ul><h4>So… How Ready Are We?</h4><p>We’re more AI-ready than we thought, there’s strong potential — but only if solutions are:</p><ul><li>Specific</li><li>Practical</li><li>Aligned with real pain points</li></ul><blockquote>In short: AI can’t lead the process. It has to follow the pain.</blockquote><h4>What Happens Next</h4><p>We’ve started matching the top pain points with targeted process improvements, automation options, and yes, AI tools where they make sense.</p><p>But the lesson we’re taking with us?</p><blockquote><strong>Start with people, not platforms.</strong></blockquote><p>If you’re wondering how ready your team is for AI, don’t start with a tool.</p><p>Start with a question: <em>Where are we wasting time?</em></p><p>When you find the friction, you’ll find the opportunity. Only then does AI become a solution, not just a shiny experiment.</p><p>At <a href="https://www.charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=aireadiness">Charisol</a>, we believe how we work is just as important as what we build. <a href="https://www.charisol.io/?utm_source=medium&amp;utm_medium=blogpost&amp;utm_campaign=aireadiness"><strong>Get to know us</strong></a><strong>!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fda3560eeaf6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/charisol-pulse/how-ready-are-teams-for-ai-fda3560eeaf6">How Ready Are Teams for AI?</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 Research — Even When No One Asks for It]]></title>
            <link>https://medium.com/design-bootcamp/why-we-document-research-even-when-no-one-asks-for-it-4c2e28d4f347?source=rss-5504b6aa21b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c2e28d4f347</guid>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[repositories]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Zaynab Aderonke Ogunnubi]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 12:33:07 GMT</pubDate>
            <atom:updated>2025-07-02T10:34:41.181Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why We Document Research — Even When No One Asks for It</h3><h4>The unglamorous but essential habit that makes research truly valuable over time</h4><p>I’ve lost count of how many times I’ve wrapped up a round of research, carefully organized the findings, and… no one asked for the documentation.</p><p>And yet — I document it anyway. Every time.</p><p>Because research documentation isn’t just for <em>now</em>. It’s for later. For others. For decisions yet to be made. It’s an invisible backbone of product teams that want to learn and grow, even when no one’s watching.</p><figure><img alt="A library of books (as a metaphor for stored knowledge)" src="https://cdn-images-1.medium.com/max/1024/0*laCEsyk6QEH8DGy9" /><figcaption>Photo by <a href="https://unsplash.com/@bamin?utm_source=medium&amp;utm_medium=referral">Pierre Bamin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We often think of documentation as a formality — something you do to close out a project or tick a box. But in practice, it does something far more valuable: it protects what we’ve learned.</p><p>Teams change. Memory fades. Priorities shift.</p><p>But written, structured research holds steady. It remembers for us when we forget.</p><p>It reminds us:</p><ul><li>What our users said six months ago</li><li>Why we made a particular product decision</li><li>Which ideas we already tested — and why they didn’t work</li></ul><p>When we don’t document, we risk repeating the same mistakes, asking the same questions, and overlooking hard-earned insights.</p><blockquote>Research documentation is not a waste of time, it’s a quiet investment</blockquote><p>Think about what happens when research isn’t documented:</p><ul><li>A researcher redoes a usability test that’s already been done.</li><li>A PM pitches a feature that users explicitly said they don’t want.</li><li>A new team joins a project with no access to past user feedback.</li></ul><p>It’s not just inefficient. It’s frustrating — and costly.</p><p>On the flip side, when research is documented (even lightly), it becomes:</p><ul><li>A reference point for future decisions</li><li>A source of inspiration for new ideas</li><li>A living archive of how user needs evolve over time</li></ul><p>Even if no one asks for it right now, someone will be grateful for it later.</p><figure><img alt="A team looking at shared notes" src="https://cdn-images-1.medium.com/max/1024/0*108g_vAphKQ79kG3" /><figcaption>Photo by <a href="https://unsplash.com/@byfortytwo?utm_source=medium&amp;utm_medium=referral">FORTYTWO</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Not every research effort needs a 30-slide deck or formal report. Sometimes all you need is:</p><ul><li>A short write-up of key insights</li><li>Bullet-point takeaways with links to recordings</li><li>A Notion page or tagged folder in your research repo</li></ul><p>The goal is clarity and accessibility — not perfection.</p><p>You’re not documenting for the spotlight. You’re documenting so the knowledge doesn’t disappear when you move on, take a break, or hand off the project.</p><blockquote>When we don’t document, we don’t just lose data — we lose decisions.</blockquote><p>In a fast-moving team, documentation is how we slow down enough to remember.</p><ul><li>It’s how we honor the effort we put into understanding our users.</li><li>It’s how we give others a starting point instead of a blank page.</li><li>It’s how we make our research more than a one-time conversation.</li></ul><p>So no — no one may be asking for it right now.<br>But we document anyway.</p><p>Because someone will need it.<br>And when they do, it’ll be there — quietly waiting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c2e28d4f347" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/why-we-document-research-even-when-no-one-asks-for-it-4c2e28d4f347">Why We Document Research — Even When No One Asks for It</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>