<?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 Omar Raddaoui on Medium]]></title>
        <description><![CDATA[Stories by Omar Raddaoui on Medium]]></description>
        <link>https://medium.com/@oraddaoui?source=rss-4e88a7606643------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*r1yIW9VpNzLqEEs8h3EL6w.jpeg</url>
            <title>Stories by Omar Raddaoui on Medium</title>
            <link>https://medium.com/@oraddaoui?source=rss-4e88a7606643------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:19:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oraddaoui/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[Most Product Risk Is Front-Loaded]]></title>
            <link>https://medium.com/design-bootcamp/most-product-risk-is-front-loaded-d678cce57254?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/d678cce57254</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 00:14:29 GMT</pubDate>
            <atom:updated>2026-02-07T11:12:09.646Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sBHHLPjbw9ZqvLNY" /><figcaption>Product Risk Accumulates Early</figcaption></figure><p>Most product failures don’t start with bad execution. They start with a premature solution.</p><p>Smart teams.</p><p>Strong tech.</p><p>Polished design.</p><p>Still the wrong product.</p><p>Why?</p><p>Because the solution shows up before the problem is truly understood.</p><p>The pattern is easy to spot.</p><p>Early conversations often sound like this:</p><ul><li>How do we make this work for users?</li><li>How do we make it look elegant?</li><li>What features should we add?</li><li>How do we scale it?</li></ul><p>These aren’t bad questions.</p><p>They’re the right questions — asked at the wrong time.</p><p>And timing mistakes are among the most expensive ones product teams can make.</p><h3>The quiet mistake: confusing usability with utility</h3><p>This is one of the most common — and costly — errors in product work.</p><p>Teams treat usability and utility as interchangeable.</p><p>They’re not.</p><p>Usability asks:</p><ul><li>Is it easy to use?</li><li>Is it intuitive?</li><li>Is it efficient?</li></ul><p>Utility asks:</p><ul><li>Does this solve a real problem?</li><li>Does it meaningfully improve someone’s life or work?</li><li>Is this worth existing at all?</li></ul><p>(adapted from NN/G’s framing on <a href="https://www.nngroup.com/articles/usability-101-introduction-to-usability/">usability vs. utility</a>).</p><p>A product can be highly usable… …and still be useless.</p><p>That’s the trap: product appeal ≠ design appeal.</p><p>Sleek UI attracts users.</p><p>Utility keeps them.</p><p>“Useful” isn’t a feeling. It’s a sequence.</p><p><a href="https://www.nngroup.com/articles/usability-101-introduction-to-usability/">Useful</a> = Utility + Usability</p><p>Usability amplifies value.</p><p>It does not create it.</p><p>When teams optimize usability <a href="https://www.interaction-design.org/literature/topics/usability?srsltid=AfmBOoo6_LFm-RZRBTfMdi3tEFhWippTiB3Wj2Myypf7GfQ8wapNnZT0">before proving utility</a>, they’re not innovating. They’re decorating uncertainty.</p><h3>Why teams rush anyway</h3><p>Most teams don’t skip deep problem work because they’re careless.</p><p>They skip it because ambiguity is uncomfortable.</p><p>Because discovery is harder to justify than delivery.</p><p>Because shipping feels safer than thinking.</p><p>Until it isn’t.</p><p>That’s why guardrails matter.</p><p>Not bureaucracy.</p><p>Not heavyweight process.</p><p>Guardrails that prevent teams from slipping into solution mode before they’ve earned the right to.</p><h3>Where the Double Diamond actually earns its keep</h3><p>The <a href="https://www.designcouncil.org.uk/our-resources/framework-for-innovation/">Double Diamond Innovation Framework</a> isn’t about slowing teams down.</p><p>It’s about enforcing sequencing</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AJYbvjxrHdK-WX55" /><figcaption>Adapted from the Double Diamond Innovation Framework by UK Design Council</figcaption></figure><p>Two spaces — kept intentionally separate.</p><p>Problem Space (Discover → Define)</p><ul><li>Explore broadly Understand deeply.</li><li>Converge on the right problem.</li></ul><p>Solution Space (Develop → Deliver)</p><ul><li>Generate options.</li><li>Test aggressively. Converge on what actually works.</li></ul><p>The danger isn’t moving fast.</p><p>The danger is crossing the boundary too early.</p><p>This isn’t an argument for endless discovery — it’s an argument for earning the right to move on.</p><h3>The real gate between problem and solution</h3><p>This is where the <a href="https://www.productplan.com/glossary/5-ws-and-h/">5 Ws and H</a> become a gate — not a formality.</p><p>Before leaving the problem space, you should be able to answer clearly:</p><ul><li>Who is experiencing the problem?</li><li>Where does it occur in their real context?</li><li>When does it arise?</li><li>Why does it matter <em>to them</em> (not to us)?</li><li>What is the core unmet need — not the feature gap?</li><li>How are people coping today, including workarounds?</li></ul><p>Here’s an illustration drawing from a <a href="https://www.linkedin.com/posts/anisha-sethi-b020a6190_uxdesign-uiux-designthinking-activity-7370413908538556416-lDCz/">post by Anisha S.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*YwHrVE78ulrkypmh" /><figcaption>Illustration of the 5Ws and H framework</figcaption></figure><p>If these answers are fuzzy, the solution will be too.</p><p>Notice where the “How” actually belongs.</p><p>It’s not how you plan to solve the problem.</p><p>It’s how people are currently dealing with it.</p><p>Only after that do you earn the right to ask how it should be solved.</p><p>That distinction alone prevents most cart-before-the-horse failures.</p><h3>Where Atomic UX quietly strengthens the system</h3><p>Atomic UX (a framework developed <a href="https://blog.prototypr.io/what-is-atomic-research-e5d9fbc1285c">by Daniel Pidcock</a>) isn’t about working in smaller increments.</p><p>It’s about how teams create trustworthy knowledge</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/0*KtZXBR-fGf7KI1iC" /><figcaption>Atomic UX model illustration — Example draws from illustration by Daniel Pidcock on Prototypr</figcaption></figure><p>Each atomic unit is a small, observable fact:</p><ul><li>A usability breakdown</li><li>A repeated friction point</li><li>A behavioral pattern</li><li>A validated user reaction</li></ul><p>On their own, these facts don’t justify action.</p><p>Combined intentionally, they form insight.</p><p>That creates a clear chain of provenance:</p><p>Experiment → Fact → Insight → Recommendation</p><p>If a recommendation can’t be traced back to evidence, it’s no longer product thinking.</p><p>It’s guesswork.</p><h3>Why Atomic UX and Double Diamond belong together</h3><p>The Double Diamond protects when teams should solve.</p><p>Atomic UX protects how teams know what they’ve learned.</p><p>Together, they prevent familiar failure modes:</p><ul><li>Treating anecdotes as evidence</li><li>Backfilling rationale after decisions</li><li>Mistaking confidence for correctness</li></ul><p>Direction stays honest. Learning stays honest.</p><h3>A closing thought</h3><p>Most product misfires don’t fail because of poor execution.</p><p>They fail because of poor sequencing — solving before understanding.</p><p>Good design isn’t invisible because it’s minimal.</p><p>It’s invisible because nothing about it feels accidental.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/0*nP4BZO-TCE9sw9LG" /><figcaption>A quote on good design being invisible to the user by Dan Norman</figcaption></figure><p>Correct problem. Correct need. Correct timing.</p><p>That’s not aesthetics.</p><p>That’s discipline.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d678cce57254" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/most-product-risk-is-front-loaded-d678cce57254">Most Product Risk Is Front-Loaded</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>
        <item>
            <title><![CDATA[Stop Building Chatbots. Start Designing Systems: My Journey into Agentic AI]]></title>
            <link>https://medium.com/@oraddaoui/stop-building-chatbots-start-designing-systems-my-journey-into-agentic-ai-98d0560268ab?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/98d0560268ab</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 07:30:32 GMT</pubDate>
            <atom:updated>2025-12-29T07:30:32.062Z</atom:updated>
            <content:encoded><![CDATA[<p>For months, I kept hearing the same message everywhere:</p><p>AI is changing everything. LLMs are everywhere. Agents are the future.</p><p>Most people stop there.</p><p>They build chatbots. They turn prompts into endpoints. They demo something flashy.</p><p>I wanted to know something deeper:</p><p>Can someone who isn’t a software developer actually design and build a real, intelligent system?</p><p>Not a toy. Not a single prompt. A system that <em>thinks in steps</em>.</p><p>So I tried.</p><h3>The Shift That Changed Everything</h3><p>At some point, it clicked.</p><p>Building with agentic AI isn’t about prompts. It’s about systems thinking.</p><p>You stop thinking like a user of AI. You start thinking like a designer of intelligence.</p><p>Most AI products today are endpoints:</p><p>You ask → it answers. You upload → it generates.</p><p>Agentic systems are different.</p><p>They reason, plan, act, and adapt across multiple steps.</p><p>A Google <a href="https://cloud.google.com/resources/content/ai-agent-handbook">guide</a> describes AI agents as systems that can understand context, pull from multiple sources, and act on a user’s behalf. An Amazon <a href="https://aws.amazon.com/blogs/database/key-components-of-a-data-driven-agentic-ai-application/?sc_channel=sm&amp;sc_campaign=DBA_Blog&amp;sc_publisher=LINKEDIN&amp;sc_country=global&amp;sc_geo=GLOBAL&amp;sc_outcome=awareness&amp;sc_content=DB_Blog&amp;sc_category=Amazon%20Aurora&amp;linkId=866658673">blog</a> frames them as systems that decide <em>how</em> to accomplish a task, not just execute instructions.</p><p>That framing matters.</p><p>Because once you understand it, you realize something important:</p><p>A single AI model is bad at doing everything at once.</p><p>Give one model a massive, complex task and the output degrades somewhere along the way.</p><p>The solution isn’t a better prompt.</p><p>It’s specialization.</p><h3>What Agentic AI Looks Like in Practice</h3><p>Instead of one “smart” AI, you design multiple focused ones.</p><p>One agent analyzes input. Another enriches it with context. Another evaluates tradeoffs. Another decides what happens next.</p><p>Sometimes they run sequentially. Sometimes they branch. Often there’s a supervisory layer.</p><p>This isn’t magic.</p><p>It’s applied systems design.</p><p>This diagram, taken from an AWS <a href="https://aws.amazon.com/blogs/database/key-components-of-a-data-driven-agentic-ai-application/?sc_channel=sm&amp;sc_campaign=DBA_Blog&amp;sc_publisher=LINKEDIN&amp;sc_country=global&amp;sc_geo=GLOBAL&amp;sc_outcome=awareness&amp;sc_content=DB_Blog&amp;sc_category=Amazon%20Aurora&amp;linkId=866658673">blog</a>, illustrates the anatomy of an agentic AI application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/0*5PCP9rN8yOAN6tLs" /><figcaption>“Anatomy of an agentic AI application” — Amazon AWS blog by Brooker and Vlasceanu (2025).</figcaption></figure><p>The Mental Model That Unlocked My Progress</p><p>Here’s the analogy that changed how I build:</p><p>Think of an automated car wash.</p><p>A car doesn’t get clean in one step.</p><p>It moves through stages.</p><p>Wash.</p><p>Rinse.</p><p>Wax.</p><p>Dry.</p><p>Finish.</p><p>Each stage transforms the same object into something more valuable.</p><p>That’s how agentic systems work.</p><p>User data enters the system. Each step transforms it. Context accumulates. Value compounds.</p><p>You build the system once. Then let it run the journey.</p><h3>How I Approached Building (as a non-developer)</h3><p>Before touching tools, I forced myself to do one thing:</p><h3>Draw the system.</h3><p>Flowcharts. Diagrams. Clear stages with names and purpose.</p><p>This was critical.</p><p>It helped me detach from <em>what</em> I was building and focus on <em>how intelligence flows</em>.</p><p>At this stage, I wasn’t solving UI or implementation. I was designing structure.</p><p>If you skip this step, complexity will catch you later.</p><p>Hard.</p><h3>Choosing the “Brain”: Workflow Orchestration</h3><h3>This step took several weeks.</h3><p>I needed something that was:</p><ul><li>No-code or low-code</li><li>Visual-first</li><li>Capable of branching logic</li><li>Able to connect real tools and APIs</li><li>Affordable for experimentation</li></ul><p>I tested a lot:</p><p>Zapier. Make. n8n. OpenAI Agent Kit. Others you’ve probably seen trending.</p><p>Each had tradeoffs.</p><p>After long experiments and even longer conversations with ChatGPT, I chose Make to prototype.</p><p>Not because it’s perfect — but because it gave me control without forcing me to become a developer.</p><p>That balance mattered.</p><h3>The UI Problem (And Why Experience Matters)</h3><p>This part surprised me.</p><p>I could have built everything as a chat.</p><p>It would have been faster.</p><p>But it would have killed the experience.</p><p>I wanted users to feel like they were <em>moving</em> through something. Progressing. Evolving.</p><p>From a UI/UX perspective, experience is everything.</p><p>Too simple, and you flatten the idea. Too complex, and you drown in execution.</p><p>That’s when I found Lovable.</p><p>Lovable let me generate real websites and flows by describing what I wanted in natural language.</p><p>Not mockups. Real UI.</p><p>Crucially, I confirmed I could connect Lovable (frontend) to Make (backend).</p><p>That separation was another breakthrough.</p><p>The Real Build: UI, Brain, Memory</p><p>At first, building felt overwhelming.</p><p>I asked ChatGPT where to start — and got a long, intimidating roadmap.</p><p>So I did something simpler.</p><p>I broke everything down to absurdly small steps.</p><ul><li>Step 1.1</li><li>Step 1.2</li><li>Step 1.3</li></ul><p>And I realized every intelligent system boils down to three things:</p><p>The UI Where users interact.</p><p>The Brain LLMs + logic that interpret context and decide what happens next.</p><p>The Memory A place to persist state over time.</p><p>Without memory, there is no journey.</p><h3>The Hard Parts No One Talks About</h3><p>This is where most demos end — and real building begins.</p><p>Some hurdles I hit:</p><p>Understanding what a webhook actually is (It’s just a doorbell between systems.)</p><p>Connecting Lovable → Make reliably</p><p>Realizing Google Sheets wasn’t best for memory purposes</p><p>Moving to Airtable to store user state</p><p>Designing prompts with roles, guardrails, and intent</p><p>Debugging workflows step by step instead of guessing</p><p>Accepting that ChatGPT is a collaborator — not an oracle</p><p>Sometimes I disagreed with ChatGPT.</p><p>Sometimes I was right.</p><p>That was a confidence unlock.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/0*uxz-jB_WesWcrZxP" /><figcaption>From user input to intelligent outcomes: A multi-step agentic AI workflow. Generated with ChatGPT</figcaption></figure><p>What I’d Tell Anyone Starting This Today</p><p>Build the MVP first. Then simplify it again.</p><p>Think in systems, not features.</p><p>Separate UI, intelligence, and memory early.</p><p>Choose tools that are likely to survive long-term.</p><p>Experiment before committing, every platform has built-in assumptions on how you build.</p><p>Expect friction. Debugging <em>is</em> learning.</p><p>No-code doesn’t mean no architecture.</p><h3>Final Reflection</h3><p>This journey was messy.</p><p>Slow. Frustrating. At times, discouraging.</p><p>What I’ve built so far might not look impressive to experts in the space.</p><p>But that’s not the point.</p><p>The real win was learning how to design intelligent systems as a non-developer.</p><p>The barriers to building aren’t gone — but they’ve dropped low enough that curiosity and persistence matter more than credentials.</p><p>If you’re not learning how to build with agentic AI right now, you’re missing something big.</p><p>Not hype.</p><p>Opportunity.</p><p>The age of system-thinking builders is here.</p><p>And you don’t need permission to start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98d0560268ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Supercharge your UX Pursuits with the DIKW Framework]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uxplanet.org/supercharge-your-ux-pursuits-with-the-dikw-framework-9fa87b2586be?source=rss-4e88a7606643------2"><img src="https://cdn-images-1.medium.com/max/974/1*eUtD3Zv_jqRgf-u6G3EvxQ.png" width="974"></a></p><p class="medium-feed-snippet">If there is one thing and one thing only the UX practice boils down to, it would be making decisions, and informed decisions at that.</p><p class="medium-feed-link"><a href="https://uxplanet.org/supercharge-your-ux-pursuits-with-the-dikw-framework-9fa87b2586be?source=rss-4e88a7606643------2">Continue reading on UX Planet »</a></p></div>]]></description>
            <link>https://uxplanet.org/supercharge-your-ux-pursuits-with-the-dikw-framework-9fa87b2586be?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fa87b2586be</guid>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Sun, 05 Feb 2023 17:10:56 GMT</pubDate>
            <atom:updated>2023-02-06T16:58:16.507Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[If Knowledge is a Lemon, the Juice is in the Squeeze.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@oraddaoui/grow-as-a-subject-matter-expert-with-the-dikw-framework-4af066c987e8?source=rss-4e88a7606643------2"><img src="https://cdn-images-1.medium.com/max/973/1*e1a3nu-VmfEzluQMuZI5Lw.png" width="973"></a></p><p class="medium-feed-snippet">Knowledge without action is a floating mental abstraction.</p><p class="medium-feed-link"><a href="https://medium.com/@oraddaoui/grow-as-a-subject-matter-expert-with-the-dikw-framework-4af066c987e8?source=rss-4e88a7606643------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@oraddaoui/grow-as-a-subject-matter-expert-with-the-dikw-framework-4af066c987e8?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/4af066c987e8</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[knowledge]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Fri, 13 Jan 2023 03:47:56 GMT</pubDate>
            <atom:updated>2023-01-17T18:18:39.460Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Make Sure What You’re Erecting is Not a UX House of Cards]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uxplanet.org/make-sure-what-youre-erecting-is-not-a-ux-house-of-cards-69ae8e4f0441?source=rss-4e88a7606643------2"><img src="https://cdn-images-1.medium.com/max/911/1*VxICwwzGDTth5qdy8AMPZA.png" width="911"></a></p><p class="medium-feed-snippet">You are in Command of your UX Ship. Don&#x2019;t Get Lost or Adrift in a Vast Ocean.</p><p class="medium-feed-link"><a href="https://uxplanet.org/make-sure-what-youre-erecting-is-not-a-ux-house-of-cards-69ae8e4f0441?source=rss-4e88a7606643------2">Continue reading on UX Planet »</a></p></div>]]></description>
            <link>https://uxplanet.org/make-sure-what-youre-erecting-is-not-a-ux-house-of-cards-69ae8e4f0441?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/69ae8e4f0441</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Mon, 26 Dec 2022 21:39:28 GMT</pubDate>
            <atom:updated>2022-12-27T22:55:46.470Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Navigating Complex UX Projects: What you Should Know]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/design-bootcamp/navigating-complex-ux-projects-what-you-should-know-b8c7667c982a?source=rss-4e88a7606643------2"><img src="https://cdn-images-1.medium.com/max/900/1*3nqHQbztxPg-jW-t-dn3xw.png" width="900"></a></p><p class="medium-feed-snippet">Sure, the choices you make on your journey will carry benefits, but they may carry hidden costs too, and they add up. Choose wisely.</p><p class="medium-feed-link"><a href="https://medium.com/design-bootcamp/navigating-complex-ux-projects-what-you-should-know-b8c7667c982a?source=rss-4e88a7606643------2">Continue reading on Bootcamp »</a></p></div>]]></description>
            <link>https://medium.com/design-bootcamp/navigating-complex-ux-projects-what-you-should-know-b8c7667c982a?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8c7667c982a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Sun, 18 Dec 2022 05:26:48 GMT</pubDate>
            <atom:updated>2022-12-18T08:31:13.780Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Nine Reasons to Power up your UX Pursuits with Quantitative Data Skills]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/design-bootcamp/nine-reasons-to-power-up-your-ux-pursuits-with-quantitative-data-skills-a22c6ec1a790?source=rss-4e88a7606643------2"><img src="https://cdn-images-1.medium.com/max/963/0*xzAFsejvUmcQrVtz.png" width="963"></a></p><p class="medium-feed-snippet">From data to impact: this is your job as a UX Decision Maker</p><p class="medium-feed-link"><a href="https://medium.com/design-bootcamp/nine-reasons-to-power-up-your-ux-pursuits-with-quantitative-data-skills-a22c6ec1a790?source=rss-4e88a7606643------2">Continue reading on Bootcamp »</a></p></div>]]></description>
            <link>https://medium.com/design-bootcamp/nine-reasons-to-power-up-your-ux-pursuits-with-quantitative-data-skills-a22c6ec1a790?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/a22c6ec1a790</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-researcher]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Mon, 28 Nov 2022 05:28:01 GMT</pubDate>
            <atom:updated>2022-12-03T07:52:58.583Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Success in UX Research and Design is NOT Something You Stumble Upon]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/design-bootcamp/success-in-ux-research-and-design-is-not-something-you-stumble-upon-925e58ce4666?source=rss-4e88a7606643------2"><img src="https://cdn-images-1.medium.com/max/891/1*IcEkM5aRK8FVLsBcsHZOwA.png" width="891"></a></p><p class="medium-feed-snippet">Ticking the Checkmarks of the UX Research and Design Process is No Guarantee of Success</p><p class="medium-feed-link"><a href="https://medium.com/design-bootcamp/success-in-ux-research-and-design-is-not-something-you-stumble-upon-925e58ce4666?source=rss-4e88a7606643------2">Continue reading on Bootcamp »</a></p></div>]]></description>
            <link>https://medium.com/design-bootcamp/success-in-ux-research-and-design-is-not-something-you-stumble-upon-925e58ce4666?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/925e58ce4666</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Wed, 02 Nov 2022 01:33:40 GMT</pubDate>
            <atom:updated>2022-11-03T18:02:58.473Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[More than a destination, UX design is a journey!]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/design-bootcamp/more-than-a-destination-ux-design-is-a-journey-db8e26850934?source=rss-4e88a7606643------2"><img src="https://cdn-images-1.medium.com/max/1280/1*8eQB0lomVkJWRxXJ4A3g3g.jpeg" width="1280"></a></p><p class="medium-feed-snippet">Embrace Uncertainty. Lead with Empathy.</p><p class="medium-feed-link"><a href="https://medium.com/design-bootcamp/more-than-a-destination-ux-design-is-a-journey-db8e26850934?source=rss-4e88a7606643------2">Continue reading on Bootcamp »</a></p></div>]]></description>
            <link>https://medium.com/design-bootcamp/more-than-a-destination-ux-design-is-a-journey-db8e26850934?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/db8e26850934</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Sat, 01 Oct 2022 22:13:10 GMT</pubDate>
            <atom:updated>2022-10-03T07:45:03.554Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Embrace the Art of Giving Epic Presentations: Three Tips To Get You Started]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/technical-excellence/embrace-the-art-of-giving-epic-presentations-three-tips-to-get-you-started-7858d1ec2f39?source=rss-4e88a7606643------2"><img src="https://cdn-images-1.medium.com/max/2600/1*39d0W4AweConAaD4h80kSw.png" width="4477"></a></p><p class="medium-feed-snippet">How badly do you want to brush up on your presentation skills? The good news is if you really want it and you are willing to invest&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/technical-excellence/embrace-the-art-of-giving-epic-presentations-three-tips-to-get-you-started-7858d1ec2f39?source=rss-4e88a7606643------2">Continue reading on SYNERGY »</a></p></div>]]></description>
            <link>https://medium.com/technical-excellence/embrace-the-art-of-giving-epic-presentations-three-tips-to-get-you-started-7858d1ec2f39?source=rss-4e88a7606643------2</link>
            <guid isPermaLink="false">https://medium.com/p/7858d1ec2f39</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[presentations]]></category>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[presentation-skills]]></category>
            <dc:creator><![CDATA[Omar Raddaoui]]></dc:creator>
            <pubDate>Sat, 18 Jun 2022 18:18:57 GMT</pubDate>
            <atom:updated>2022-12-30T18:10:20.742Z</atom:updated>
        </item>
    </channel>
</rss>