<?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 Mojdeh on Medium]]></title>
        <description><![CDATA[Stories by Mojdeh on Medium]]></description>
        <link>https://medium.com/@mojdehmarashi?source=rss-b8dd7cc8f65d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sfpi5k_jW9ZbXxL1fATfKA.png</url>
            <title>Stories by Mojdeh on Medium</title>
            <link>https://medium.com/@mojdehmarashi?source=rss-b8dd7cc8f65d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:29:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mojdehmarashi/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[When Design Breaks Its Promise: Why Premium Brands Can’t Resist the Optimization Trap]]></title>
            <link>https://medium.com/@mojdehmarashi/when-design-breaks-its-promise-319e56e8c530?source=rss-b8dd7cc8f65d------2</link>
            <guid isPermaLink="false">https://medium.com/p/319e56e8c530</guid>
            <category><![CDATA[design-ethics]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Mojdeh]]></dc:creator>
            <pubDate>Tue, 24 Mar 2026 21:30:55 GMT</pubDate>
            <atom:updated>2026-03-24T21:37:24.604Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why even premium brands struggle to deliver on their promises when systems override intentions</h3><figure><img alt="Abstract 3D composition showing disconnected geometric blocks in muted grays and bronze, representing fragmented systems and structures that don’t align." src="https://cdn-images-1.medium.com/max/1024/0*FfqNJo00oqePxLZA" /><figcaption>Abstract representation of disconnected systems — when design serves business constraints rather than user needs.</figcaption></figure><p>My vacuum stopped working. I called support and suggested the charger might be the issue. The technician insisted it was the motor — the expensive motor — and attempted to redirect me toward purchasing a refurbished vacuum instead. I bought the motor. During installation, another part broke. I ordered the replacement from Amazon. After reassembling everything, the vacuum exhibited the same problem.</p><p>Second call: A different agent conducted video troubleshooting and immediately confirmed it was the charger. Exactly what I’d suggested from the start. I purchased the charger she recommended. She told me delivery would take seven business days, and that I had three days to return the motor with a printed shipping label.</p><p>When the shipping notification arrived for the charger, I noticed the billing address was wrong — not slightly off, but a completely different street in a different city. I contacted chat support to correct it. The agent’s response: “I am not able to update the billing address, as it is set by default.” Not “let me escalate this” or “let me find who can help.” Simply: the system won’t allow changes. When I continued pressing on the issue, he sent me a vacuum cleaning video and a promotional discount code.</p><p>Two days later, pressed for time before the supposed three-day return deadline, I called requesting an extension. The third agent seemed surprised — returns are accepted for 30 to 60 days, and labels are scannable, no printing required. Three calls, three completely different policies.</p><p>The charger that was supposed to take seven business days? Arrived the next morning.</p><p>This is Dyson — a company built on design excellence and premium service. If they can’t deliver on their brand promise, something fundamental has shifted in how companies approach customer experience.</p><p>A healthcare portal buries patient messaging at the bottom of a scrollable menu, positioned below six revenue-generating options. Following corporate acquisition, service quality degrades. The messaging feature that once held prominence becomes progressively harder to locate with each interface iteration.</p><p>E-commerce product listings promise “100% cotton” in prominent headlines, then disclose “actually 95%” several layers deep in expandable product details — with no specification of the remaining 5% material. For users with allergies or sensitivities, this isn’t merely inconvenient. It’s potentially harmful. Yet the interface architecture prioritizes sales conversion over user safety.</p><p>These aren’t isolated failures. This has become the industry standard.</p><p>Organizations with mature design practices involve designers throughout implementation. When constraints emerge — budget reductions, technical limitations, compressed timelines — designers can adapt their work to balance business requirements with user experience. Strong organizations maintain rigorous UI review processes, ensuring nothing ships without validation against user needs.</p><p>But many companies treat design as a discrete deliverable rather than an ongoing practice. The designer creates a thoughtful, user-centered solution and transfers it to implementation teams. Then business requirements shift. Engineering introduces modifications for technical expedience. Marketing revises messaging to align with campaign strategies. Product managers reprioritize features based on metrics dashboards. Sometimes designers only discover these modifications when users begin reporting issues with experiences they never designed.</p><p>Service agents operate under similar constraints. Chatbot systems are architected to deflect volume from costlier human support channels. Agent scripts prioritize resolution efficiency over problem resolution. Database architectures prevent correction of obvious errors. Training budgets contract while support volume expands. Policy documentation contradicts itself because no single source of truth exists.</p><p>Each decision, viewed in isolation, appeared defensible to someone within the organization: reduce operational costs, increase throughput efficiency, optimize for scale, minimize system complexity. The cumulative effect, however, produces systems engineered to serve internal operations rather than the people depending on them.</p><p>Designers genuinely aspire to create experiences that serve users and address genuine problems. They navigate constraints imposed by budgets, business objectives, stakeholder requirements, and technical limitations. When they articulate vision for user-centered experiences, they aren’t being disingenuous. They’re operating within systems that frequently prevent delivering what they’ve designed.</p><p>Service agents genuinely want to resolve customer issues. They’re provisioned with scripts, metrics frameworks, and tools that optimize for everything except actually solving the problems users present.</p><p>The relevant question isn’t whether individual contributors harbor good intentions. It’s who controls the systems that override those intentions, and whether anyone maintains accountability for the gap between articulated promises and delivered reality.</p><p>The Dyson example proves particularly instructive: this represents a premium brand with established design credentials and historical reputation for service excellence. If an organization with these advantages cannot resist structural pressure to optimize for operational efficiency over customer problem resolution, what does this reveal about industry-wide priority structures?</p><p>We possess the technical capability to architect superior systems. The resources exist to develop properly trained support teams. Design expertise is available to create interfaces that serve users rather than manipulate behavior. The constraint is never capability. The constraint is priority.</p><p>Chat interfaces could present consolidated forms rather than sequential interrogation flows. Support agents could be empowered to correct data inconsistencies rather than informed that “the system won’t permit changes.” Product listings could undergo verification before publication. Healthcare portals could prioritize patient needs over revenue-generating features.</p><p>We select different architectures. More precisely: those controlling budget allocation, establishing performance metrics, and defining organizational success criteria select different architectures. Individual designers and service agents — those positioned closest to user needs — rarely possess that authority.</p><p>When promises consistently fail to align with reality, users internalize lessons about what to expect and whom to trust. They calibrate expectations downward. They assume that requesting assistance will consume time without yielding resolution. They understand their requirements will remain subordinate to operational priorities.</p><p>Organizations making these architectural choices might consider what they’re actually optimizing: short-term cost reductions that erode trust equity and accelerate customer attrition, efficiency metrics that quantify everything except problem resolution, growth trajectories that sacrifice the quality foundation upon which brand value was originally constructed.</p><p>Design that fails to deliver on implicit promises doesn’t merely generate momentary user frustration. It transmits broader instruction about whose needs command priority and what users should anticipate from organizations claiming to serve them.</p><p>This proves costly for all participants — but particularly for organizations that eventually discover broken promises ultimately fracture business models as well.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/when-design-breaks-its-promise-mojdeh-marashi-fjkwc/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=319e56e8c530" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What AI can’t see: when absence becomes permanent]]></title>
            <link>https://medium.com/@mojdehmarashi/what-ai-cant-see-when-absence-becomes-permanent-c631d364de26?source=rss-b8dd7cc8f65d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c631d364de26</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Mojdeh]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 20:02:52 GMT</pubDate>
            <atom:updated>2026-02-13T20:02:52.104Z</atom:updated>
            <content:encoded><![CDATA[<h3>What a simple illustration request revealed about training data bias</h3><figure><img alt="Three AI-generated images of a young girl with wood. First two show anatomically impossible arm positions with wood on her back instead of in her arms. Third image shows a different composition that finally worked after changing the prompt entirely" src="https://cdn-images-1.medium.com/max/1024/1*c_UhSLAQ2eHBe8K9OxoPxA.png" /></figure><p>I was working on a story that needed a simple illustration: a young girl carrying a bundle of wood in her arms, seen from behind. A straightforward image to support the narrative moment. I turned to an AI image generator, as I often do for story development, expecting this would take a few attempts to get the composition right.</p><p>After dozens of tries and increasingly specific prompts, the AI kept producing the same anatomically impossible result: a girl with wood on her back, one arm twisted behind her in ways that defied human physiology. I refined my language. I tried different phrasings. Nothing worked. The AI seemed unable to understand what I was asking for.</p><p>Perhaps you’ve experienced something similar — a moment when an AI tool consistently misunderstands a request that feels perfectly clear to you, and no amount of prompt refinement seems to bridge the gap.</p><h3>When the Problem Isn’t the AI</h3><p>That’s when I shifted approach. If the AI couldn’t generate what I needed, maybe I could find a reference image to work from. I started searching: “person carrying wood shown from behind,” “woman carrying firewood in arms seen from behind,” variations on this theme across multiple search engines and image databases.</p><p>I found many images — but not what I needed. As I kept searching, I noticed they all fell into two distinct categories.</p><p>The first: documentary-style photographs of African and rural Asian women carrying enormous loads — massive bundles strapped to their backs or balanced on their heads. The photography emphasized the scale of the burden, the hardship of the labor. These images appeared in contexts about traditional practices, rural life, development work.</p><p>The second: lifestyle aesthetic shots of young white women holding small amounts of wood styled as props. Smiling faces, carefully styled outfits, cozy backdrops of stacked firewood. The wood was a prop in a narrative about rustic charm or outdoor living.</p><p>What I didn’t find: an ordinary person doing ordinary work, photographed from a practical angle that simply showed the task being done. Not romanticized. Not exoticized. Just the mundane reality of carrying a moderate amount of wood in your arms while your back faces the camera.</p><h3>Questions About What Gets Documented</h3><p>This pattern made visible something I’d been noticing but hadn’t fully examined. The same task — carrying wood — seemed to receive completely different photographic treatment depending on who was performing it and why someone was taking the picture. Marginalized women’s labor was documented to emphasize burden and tradition. Western women’s interaction with firewood was styled as lifestyle aesthetic. But the everyday, unremarkable version of this task? That seemed to exist in a gap between these two frameworks.</p><p>I found myself wondering: whose activities get photographed, and how do those choices reflect what’s considered worth documenting? When photographers throughout history decided what merited capturing — when painters chose their subjects, when writers selected which stories to preserve — what got included and what got overlooked?</p><p>Perhaps more importantly for our current moment: if those gaps and biases in historical documentation now form the training data for AI systems, what happens to those absences? They don’t just persist — they become encoded, automated, seemingly authoritative. The AI could draw from abundant examples of both the lifestyle aesthetic and the documentary hardship — but not the everyday reality that fell between them.</p><h3>Beyond Absence: Encoded Bias</h3><p>The issue extends beyond what’s missing to what patterns are present. I noticed this while using AI for another purpose: generating simple character sketches for story development. I asked for drawings of three 10–11 year old girls, specifying modest, age-appropriate, and non-sexualized clothing. The AI produced three figures representing different ethnicities. The white and Asian characters appeared in jeans and t-shirts. The Black character consistently appeared in revealing, age-inappropriate clothing — exposed midriff, tight clothing — regardless of how many times I specified these requirements.</p><p>This raised different questions. The AI wasn’t working from absence here but from presence — from patterns in its training data where Black girls were apparently depicted differently than other children. Even explicit counter-instructions couldn’t override whatever weight that pattern carried in the system.</p><p>Both examples — the missing ordinary perspective and the embedded stereotype — point to the same underlying issue: AI systems learn from what humans chose to create, document, and archive. Those choices weren’t neutral. They reflected who had cameras and power, what narratives seemed worth telling, which subjects were considered interesting, important, or worthy of preservation.</p><p>This isn’t new. Medical research long relied on data from predominantly white male subjects, establishing what counted as ‘normal’ health baselines and treatment protocols without accounting for how these measures differ across races and ethnicities. Now we’re seeing similar patterns play out in training data for AI systems — the gaps and biases in what was historically documented become the gaps and biases in what AI can generate.</p><h3>What This Means for Design and Narrative</h3><p>As someone working at the intersection of design and storytelling, this feels particularly relevant. Writers make choices about which stories to tell, which perspectives to center. Designers make choices about what to build, what to make visible, what to prioritize. These have always been consequential decisions.</p><p>But now those choices are becoming training data. What we design, what we document, what we consider worth creating — these decisions may shape what AI systems can generate tomorrow. The gaps we leave become gaps that scale. The biases we embed become biases that automate.</p><p>This isn’t an argument against AI. It’s an observation about responsibility. If our work today helps train the systems of tomorrow, then the choices about what to include, how to frame it, whose perspectives to prioritize — these matter in ways they perhaps didn’t before. Or maybe they always mattered this much, and we’re only now seeing the consequences made visible through AI’s limitations.</p><h3>An Invitation to Notice</h3><p>I’m still thinking through the implications of this. What strikes me is how easy it would be not to notice — to assume the AI simply couldn’t understand my request, rather than recognizing that the gap was in what the AI had learned from us.</p><p>You might find yourself noticing similar patterns. Requests that should be simple but produce consistently wrong results. Gaps that reveal themselves not through what AI generates, but through what it repeatedly cannot generate despite clear instructions.</p><p>These moments might be worth paying attention to. They may tell us something about what we’ve collectively chosen to document, create, and preserve — and what we’ve chosen to overlook. And they raise questions worth asking as we continue building the reference libraries that will shape what becomes possible to generate, design, and imagine in the years ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c631d364de26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Amplifying the unheard: what good design and narrative actually do]]></title>
            <link>https://medium.com/design-bootcamp/amplifying-the-unheard-what-good-design-and-narrative-actually-do-7c4a61840d4a?source=rss-b8dd7cc8f65d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c4a61840d4a</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Mojdeh]]></dc:creator>
            <pubDate>Thu, 05 Feb 2026 23:38:35 GMT</pubDate>
            <atom:updated>2026-02-06T10:31:04.850Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>How good design and compelling stories make visible what’s been overlooked</strong></h4><figure><img alt="Abstract flowing waves transitioning from muted gray to vibrant teal and coral, representing amplification and emergence" src="https://cdn-images-1.medium.com/max/1024/1*dA5oCH6YLWTricaISMSgsQ.png" /></figure><p>Great design and compelling stories share a quality: once you encounter them, they feel inevitable. But that obviousness is hard-won — it comes from paying attention to what was being overlooked.</p><h3>The Silence That Follows</h3><p>There’s a particular silence that follows good design work. When a solution lands right, there’s little to discuss. Stakeholders nod. The work disappears into usefulness. This isn’t indifference — it’s the design working.</p><p>When friction has been smoothed away completely, people can barely reconstruct what made the previous approach fail. The solution before them feels so natural that the problem itself becomes hard to imagine. A well-designed interface doesn’t announce itself. Users simply accomplish what they came to do, then move on.</p><p>But that seamlessness required something specific: <a href="https://medium.com/design-bootcamp/why-your-users-lie-and-how-ux-research-reveals-the-truth-1ce1f5acae89">observing what users couldn’t articulate</a>.</p><h3>What Users Can’t Say</h3><p>Users build workarounds without realizing they shouldn’t need them. They accept frustrations as inevitable. <a href="https://medium.com/design-bootcamp/beyond-effortless-how-cognitive-friction-optimizes-user-experience-f3216502ef13">They adapt their thinking to match available patterns</a> — even when those patterns don’t match how they actually work. Often this happens because a design followed popular trends without questioning whether those patterns served this particular problem or this specific audience.</p><p>Good design surfaces these unspoken struggles and resolves them. It makes visible what had been normalized into invisibility.</p><p>Consider the user who opens five browser tabs to compare information the interface won’t show side-by-side, assuming that’s just how things work. Or the person who abandons a task halfway through because the next step isn’t where intuition suggests it should be — but who never reports this as a problem because they assume the issue is their own confusion, not the design.</p><p>These silent adaptations are everywhere. They’re what user research exists to uncover — not through just what people say they need, but especially through observing what they’ve learned to accept.</p><h3>The Narrative Parallel</h3><p>The same dynamic governs narrative work. When a story gives voice to what has been silenced — whether by history, culture, or power — readers experience something quieter than revelation. The narrative simply feels true. Natural.</p><p>They might wonder why they haven’t encountered this perspective before, or why it took so long to reach them, but not whether it deserves to be told. The story doesn’t announce itself as recovered or restored — it just exists, as if it had always been part of the conversation.</p><p>But that ease required someone noticing the absence. Recognizing which voices had been marginalized or erased. Building the narrative architecture that would allow those voices to surface without the weight of explanation.</p><p>The work becomes visible not through argument but through presence.</p><h3>Advocacy Through Architecture</h3><p>Both practices are acts of advocacy — but advocacy of a particular kind. They don’t announce themselves loudly. They don’t make speeches about what deserves attention.</p><p>Instead, they create the conditions where what was once invisible becomes impossible to unsee.</p><p>In design, this might mean showing next steps contextually instead of expecting users to remember multi-step processes. Or surfacing information at the moment of decision rather than three clicks away. Or removing steps that exist only because “that’s how we’ve always done it” or because that’s how popular applications do it — not because users actually need them.</p><p>In narrative, it might mean centering a perspective that’s been treated as peripheral, or building a story structure that allows complexity to emerge gradually rather than overwhelming readers with context all at once.</p><p>Neither approach requires announcing its intentions. The friction becomes smooth. The silence becomes voice. And what required intense attention to surface now feels self-evident — the kind of solution or story that makes its necessity clear simply by existing.</p><h3>What Makes This Hard</h3><p>The difficulty in both practices is the same: you have to notice what’s been normalized.</p><p>Users won’t report workarounds they’ve come to see as normal process. Readers won’t name the absences they’ve been taught not to expect. The <a href="https://uxdesign.cc/designing-for-everyone-not-just-the-average-361686c44365">dominant patterns — whether in interface design or cultural narrative — shape what feels possible</a>. What falls outside those patterns becomes difficult to see, let alone articulate.</p><p>But the challenge goes deeper than individual perception. Organizations and industries build entire frameworks around what’s already familiar. Design systems codify existing patterns. Style guides reinforce established conventions. Success stories about what “works” often mean what worked for a specific context — but those specifics get lost in translation, leaving only the visible pattern.</p><p>There’s comfort in the recognizable. Stakeholders feel safer approving designs that look like what they’ve seen succeed elsewhere. Readers feel more confident engaging with narrative structures they recognize. This isn’t unreasonable — proven patterns reduce risk. But it also means that alternative approaches, no matter how well-suited to the actual problem, face greater resistance simply because they’re unfamiliar.</p><p>And there’s a power dynamic embedded in what gets normalized. “This is just how it works” often means “this is how it’s always worked for the people who built it” — and those builders typically share certain perspectives, contexts, and assumptions. Questioning the inevitable requires asking whose needs shaped the original design, whose voices anchored the original narrative, and who benefits from keeping things as they are.</p><p>This is why both design research and narrative craft require a specific kind of attention: the willingness to question what seems inevitable, to notice the gaps between what systems offer and what people actually need, to recognize that what feels natural is often a sign not of correctness but of familiarity.</p><h3>The Work That Disappears</h3><p>When design or narrative does this work well, it disappears into usefulness. The solution feels obvious. The story feels true. Users accomplish their goals. Readers encounter perspectives that feel essential, not exotic.</p><p>That obviousness is the goal — but it’s also what makes this work easy to undervalue. When everything feels natural, it’s hard to see the architecture that made that naturalness possible. Hard to recognize the choices about what to surface and what to layer deeper. Hard to appreciate the advocacy that happened through structure rather than announcement.</p><p>Both practices solve the same fundamental problem: how to make visible what deserves attention but has been overlooked, silenced, or accepted as inevitable. Not through argument, but through building the pathways that make presence possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c4a61840d4a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/amplifying-the-unheard-what-good-design-and-narrative-actually-do-7c4a61840d4a">Amplifying the unheard: what good design and narrative actually do</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[Making complexity navigable: design and narrative as parallel practices]]></title>
            <link>https://medium.com/@mojdehmarashi/making-complexity-navigable-design-and-narrative-as-parallel-practices-865f12786555?source=rss-b8dd7cc8f65d------2</link>
            <guid isPermaLink="false">https://medium.com/p/865f12786555</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[design-leadership]]></category>
            <dc:creator><![CDATA[Mojdeh]]></dc:creator>
            <pubDate>Wed, 14 Jan 2026 18:43:36 GMT</pubDate>
            <atom:updated>2026-02-04T19:49:27.050Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nLpjGhvK3dZLB5VPl9zfpA.png" /></figure><p>For years, I’ve worked in parallel as both a UX strategist designing complex systems and a writer exploring literary narratives rooted in cultural memory. The deeper the work goes, the more apparent it becomes: these aren’t separate crafts — they’re parallel practices of making complex worlds navigable.</p><p>Both design and storytelling begin with guiding attention — but they don’t end there. They create pathways through complexity, decide what surfaces when, and recognize that the order of revelation shapes what people choose to notice, understand, and pursue. This isn’t metaphor. It’s structural.</p><h4>The Architecture of Attention</h4><p>When designing a product experience, a designer choreographs where users look, what they notice, and how they move through information. This isn’t manipulation — it’s necessity. Without intentional architecture, complexity becomes chaos. The same principle governs narrative: writers create structures that guide readers through emotional and conceptual territory, revealing information in sequences that allow understanding to build.</p><p>Both practices require understanding that attention is finite and precious. In UX, designers talk about cognitive load and progressive disclosure. In storytelling, writers talk about pacing and narrative tension. These are different vocabularies for the same fundamental challenge: how to guide someone through complexity without overwhelming them, while ensuring nothing essential disappears.</p><p>The parallel becomes even clearer when examining what both practices wrestle with: the politics of visibility. What gets foregrounded and what recedes shapes what becomes knowable. In design, this might mean deciding which product features appear in primary navigation versus three layers deep. In narrative, it might mean choosing which cultural perspectives anchor a story versus which remain peripheral. Neither choice is neutral.</p><h4>Systems Thinking as Craft</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OBhknSf2xXxKU5hatxqccA.png" /><figcaption>Parallel practices, parallel principles</figcaption></figure><p><strong>Narrative structure is a system. So is a well-designed product experience.</strong> Both require holding the entire architecture in mind while attending to each moment of encounter.</p><p>What makes both practices particularly compelling is that they’re not just about guiding attention — they’re also about understanding how elements interconnect to create meaning. This is where systems thinking becomes craft.</p><p>In UX, designers map user journeys: the paths people take through a product, the transitions between states, the moments requiring reassurance or clarity. Writers construct similar arcs: story structures with transitions, moments of recognition, and carefully timed revelations. Both are designing how meaning accumulates through sequence.</p><p>The craft in both cases is understanding that the whole is not just the sum of parts — it’s how those parts interconnect to create coherent experience.</p><h4>What This Reveals</h4><p>The notion that one practice is “strategic” while the other is “creative” misses something fundamental. Both require the same core capacity: seeing systems, understanding how information flows through them, and making choices about what that flow reveals, how it reveals it, and when.</p><p>Recognizing this parallel helps clarify what good design and good writing actually require. Strong UX strategy asks: what story does this product tell about what’s possible? Where does confusion arise because the structure doesn’t support the journey being asked of users? Strong narrative work asks parallel questions: what narrative structure would help readers hold this complexity emotionally? Where does friction exist not because readers need to sit with difficulty, but because the right pathways haven’t been built?</p><p>Both practices solve the same problem: how to build architectures where attention, revelation, and meaning unfold in ways that serve understanding. Every choice about what surfaces, and when, is also a choice about what becomes possible to know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=865f12786555" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embracing Tradition: Why Some Customs Deserve to Be Preserved]]></title>
            <link>https://medium.com/@mojdehmarashi/embracing-tradition-why-some-customs-deserve-to-be-preserved-3f1579a6b3d7?source=rss-b8dd7cc8f65d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f1579a6b3d7</guid>
            <category><![CDATA[tradition]]></category>
            <category><![CDATA[nowruz]]></category>
            <category><![CDATA[zoroastrianism]]></category>
            <category><![CDATA[persian]]></category>
            <dc:creator><![CDATA[Mojdeh]]></dc:creator>
            <pubDate>Tue, 04 Apr 2023 06:55:14 GMT</pubDate>
            <atom:updated>2025-12-25T05:26:39.070Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Embracing Tradition: Why Some Customs Deserve to Be Preserved</strong></p><p>Yesterday was <a href="https://en.wikipedia.org/wiki/Sizdah_Be-dar">Sizdah Be-dar</a>, the 13th day of the Persian New Year, marking the end of Nowruz. Most years, Sizdah Be-dar falls on a weekday, making it difficult for people to take the day off and spend it in nature, as is customary. However, this year, Sizdah Be-dar fell on a Sunday, providing an opportunity for proper celebration.</p><figure><img alt="Photo: A historic garden in Iran — Courtesy of the author" src="https://cdn-images-1.medium.com/max/1024/1*QdfEJTfksf7hoL_cnQ9u8w.jpeg" /><figcaption><a href="https://en.wikipedia.org/wiki/Ferdows_Garden">Ferdous Garden</a>, Tehran, Iran (May 2016)— Photo by the author</figcaption></figure><p>As I walked in the park, surrounded by many fellow Iranian-Americans, I experienced a flood of emotions. I was thrilled to hear conversations in my mother tongue, watch people dance to Persian music, savor traditional foods and sweets, and run into many friends. Yet moments later, I was struck by feelings of sadness, disconnection, and nostalgia for the <a href="https://en.wikipedia.org/wiki/Sizdah_Be-dar">Sizdah Be-dar</a>s of my childhood.</p><p>Being an immigrant means feeling incomplete at times like this. While it’s wonderful to hold on to old traditions — especially ones that have lasted for thousands of years and become part of our generational memory — it’s challenging to maintain them properly when you’ve been away from your birth country for so long. In my case, my entire adulthood. Even our New Year’s day can end up being just another ordinary day since it’s not a national holiday here. The hardest part is that even when we’re lucky enough to celebrate one of our traditions, it always pales in comparison to the one that lives in our memories.</p><p>I grew up in pre-revolution Iran and have lived in the U.S. for decades now. In my distant yet vivid memories, Sizdah Be-dar was always bittersweet. We spent an amazing time with family and friends outdoors — playing games, dancing, singing, and eating great food — but we also felt sad saying goodbye to the holidays.</p><p>But the holidays themselves were magical, especially for us kids. Schools were closed for a few weeks, allowing us to fully experience Nowruz and all its beautiful traditions. During the holidays, we visited family and friends with our parents, a practice known as “Did-o Baz-did” (visiting and paying back a visit). This meant you could go to someone’s house in the morning and potentially host them at your house in the afternoon on the same day! While these visits were short, they were incredibly fulfilling, especially for children. Not only did we eat great snacks — mostly delicious sweets — at each house we visited, but we also received presents (Eidi) from every grown-up we met. These presents were traditionally crisp, brand-new bills that allowed us to buy the things we wanted for ourselves.</p><p>Most people had a long list of relatives and friends they needed to visit. In fact, it was not uncommon to spend the entire 12 days of New Year on Did-o Baz-did. So to avoid missing each other — meaning going to someone’s house while they were out visiting someone else — there was a schedule in place for these visits. Each family had a specific day when they would stay home and receive guests. Furthermore, these days were assigned based on seniority. For example, my grandmother would stay home on the 2nd day of Nowruz while my great aunt, who was older, accepted visitors on the 1st day.</p><p>When I was seven years old, I was introduced to a beautiful and meaningful Nowruz tradition that left a lasting impression on me. That year, our New Year visit to my grandmother’s house turned out to be longer than usual, with several other guests in attendance, including my dad’s cousin. Just as he was about to leave, my dad, who was a mentor to him, asked him to stay a little longer. A few minutes later, when his older brother arrived, it all made sense. The two brothers had been at odds for months and hadn’t spoken since their disagreement. As soon as they saw each other, they became visibly nervous, realizing they had been tricked into visiting my grandmother’s house at the same time for a reason.</p><p>After a brief talk about the importance of family and letting go of grudges, my dad encouraged the brothers to reconcile. At first, they seemed hesitant, but eventually, they embraced each other and forgave one another, setting aside their differences. The image of the two brothers embracing is my most beautiful and unique Nowruz memory — one I have carried with me throughout the years.</p><p>That moment taught me something I didn’t fully understand until I became an adult living far from home: traditions aren’t just about the rituals themselves — the new clothes, the special foods, the festive gatherings. They’re containers for something deeper.</p><p>Many of our old traditions like this one — facilitating reconciliation among estranged loved ones by promoting forgiveness and fostering mutual understanding — are too valuable and precious to be forgotten. These traditions go back to a time when celebrations were not just about exchanging shiny objects.</p><p>Every New Year, I am reminded of this memory and that Nowruz is more than just an excuse for setting a beautiful Haft-sin, buying new clothes, eating delicious sweets, and taking long vacations. Nowruz is an ancient tradition rooted in the core beliefs of Zoroastrian culture — Good Thoughts, Good Words, and Good Deeds — that calls for us to renew ourselves and our relationships, to cleanse our bodies and souls, and to give to those who are less fortunate. Nowruz is a time to let go of grudges and negative feelings and start anew with a better and kinder version of ourselves.</p><p><strong>May your days all be Nowruz, and may your Nowruz be victorious. </strong><br><em> — A loosely translated traditional Nowruz greeting</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f1579a6b3d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>