<?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 Ritika Kathal on Medium]]></title>
        <description><![CDATA[Stories by Ritika Kathal on Medium]]></description>
        <link>https://medium.com/@ritika.kathal?source=rss-c9cf4846cb3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y5A49VpV8QHbQHJte9kQyg.png</url>
            <title>Stories by Ritika Kathal on Medium</title>
            <link>https://medium.com/@ritika.kathal?source=rss-c9cf4846cb3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:50:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ritika.kathal/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[Designing an Alert Framework for a Semi-autonomous Robot]]></title>
            <link>https://medium.com/@ritika.kathal/designing-an-alert-framework-for-a-semi-autonomous-robot-f2d19c25d92d?source=rss-c9cf4846cb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2d19c25d92d</guid>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[robotics]]></category>
            <category><![CDATA[human-machine-interaction]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ritika Kathal]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 12:30:00 GMT</pubDate>
            <atom:updated>2026-09-03T12:30:00.762Z</atom:updated>
            <content:encoded><![CDATA[<p>We usually think of alerts as simple UI elements.</p><p>A warning icon.<br>A red banner.<br>A notification.<br>A popup asking us to “Try Again.”</p><p>But when the product is a robot operating around people, an alert is more than a message.</p><p>It can determine <strong>who is responsible for what happens next.</strong></p><p>While working on the HMI for NAVBOT, a semi-autonomous robot designed to operate in commercial environments, I explored a simple but important question:</p><blockquote><strong><em>When should the robot handle a problem itself, and when should it ask a human to intervene?</em></strong></blockquote><p>The challenge wasn’t designing what the alerts should look like.</p><p>It was deciding <strong>when an alert should exist in the first place.</strong></p><h3>The problem with treating everything as an alert</h3><p>Imagine a staff member working in a busy environment.</p><p>They’re helping customers, handling other tasks and moving around.</p><p>Meanwhile, the robot is operating in the background.</p><p>If the robot interrupts them every time something unusual happens, the user will eventually stop paying attention.</p><p>This is <strong>alert fatigue</strong>.</p><p>And when everything looks urgent, nothing feels urgent.</p><p>So the goal wasn’t to create more noticeable alerts.</p><p>It was to create <strong>fewer, more meaningful interruptions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B4jAwC6ajnC-lGuaTIMMcg.png" /></figure><h3>First: understand what the robot can handle</h3><p>Before designing the UI, I mapped the situations the robot could encounter.</p><p>For example:</p><ul><li>Low battery</li><li>Navigation problems</li><li>Obstacles</li><li>Sensor issues</li><li>Emergency Stop</li><li>Loss of autonomy</li><li>Situations requiring human decisions</li></ul><p>The important question for each situation was:</p><blockquote><strong><em>Can the robot safely recover on its own?</em></strong></blockquote><p>If the answer was yes, the user probably didn’t need to be interrupted.</p><p>If the robot could partially recover, perhaps the user only needed to be informed.</p><p>And if the robot couldn’t safely decide what to do next, that was when human intervention became necessary.</p><p>This shifted my thinking from <strong>“What message should we show?”</strong> to <strong>“Does the user need to know this at all?”</strong></p><h3>Designing for the person, not the machine</h3><p>The operators weren’t robotics engineers.</p><p>They didn’t need to understand technical system states or diagnose internal failures.</p><p>They needed to know:</p><p><strong>What happened?</strong><br><strong>Does it matter to me?</strong><br><strong>Do I need to do something?</strong></p><p>For example, a technical message might say:</p><blockquote><strong><em>“Navigation confidence reduced. SLAM recovery unsuccessful.”</em></strong></blockquote><p>That may be useful to an engineer.</p><p>But for an operator, the useful message might simply be:</p><blockquote><strong><em>“I can’t continue. Please check my path.”</em></strong></blockquote><p>The first explains the <strong>system problem</strong>.</p><p>The second explains the <strong>human action.</strong></p><p>That became an important principle:</p><blockquote><strong><em>Don’t make the human understand the system. Make the system communicate the decision the human needs to make.</em></strong></blockquote><h3>Four types of alerts</h3><p>Instead of treating every system event as an error, I grouped alerts based on <strong>what the human actually needs to do.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dYx1cldJA5ffRUal7KMMOw.png" /></figure><h3>01 — Notification</h3><p>The robot handles the situation.</p><p>The user only needs awareness.</p><p><strong>Example:</strong><br>“Battery is getting low.”</p><p>No immediate action is required.</p><h3>02 — Restrictive Alert</h3><p>The robot can continue, but with reduced capability.</p><p><strong>Example:</strong><br>The robot detects a condition that requires it to reduce speed.</p><p>The system adapts instead of unnecessarily stopping the user.</p><h3>03 — Decision Alert</h3><p>The robot cannot determine the best next step.</p><p>The human needs to decide.</p><p><strong>Example:</strong></p><blockquote><strong><em>“Unable to reach destination.”</em></strong></blockquote><blockquote><strong><em>Try another route / Return to base</em></strong></blockquote><p>Now the user has a meaningful choice.</p><h3>04 — Blocking Alert</h3><p>The situation requires immediate attention.</p><p>The robot stops and waits for the human.</p><p><strong>Example:</strong><br>Emergency Stop or a safety-critical failure.</p><p>Here, interruption is justified.</p><h3>The decision framework</h3><p>This led to a simple framework built around three questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nOD40Dzx103lkPM_F9i0Fg.png" /></figure><h3>1. Does the human need to intervene?</h3><p>If the robot can safely solve the problem itself, don’t interrupt the user.</p><h3>2. What happens if the robot continues?</h3><p>Is it simply inconvenient?</p><p>Does the robot lose some functionality?</p><p>Or could continuing create a safety risk?</p><h3>3. How confident is the robot?</h3><p>A robot doesn’t need human help every time something unexpected happens.</p><p>But when it can no longer confidently recover, it should escalate.</p><h3>The logic behind each response</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cV3WgBWuF5r5ak1nuUPPbQ.png" /></figure><p>The framework gave new alerts a consistent logic instead of treating every new situation as a completely separate UI problem.</p><h3>An example: Emergency Stop</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pKsbkM3XClQ_qDDLA0ObZg.png" /></figure><p>This flow makes the responsibility transfer explicit:</p><ul><li>The human interrupts the robot.</li><li>The robot confirms its current state.</li><li>The human chooses what should happen next.</li><li>The robot resumes only after that decision.</li></ul><p>For example:</p><p><strong>Continue</strong></p><p>or</p><p><strong>Return to Base</strong></p><p>Only after that confirmation does the robot resume.</p><p>The important UX decision here isn’t the colour of the warning.</p><p>It’s the <strong>handoff of control between the human and the machine.</strong></p><p>The human interrupted the robot’s autonomy.</p><p>The system now needs to establish how autonomy is resumed clearly</p><h3>What I took away from the project</h3><p>This project changed how I think about alerts.</p><p>I used to think of an alert as:</p><blockquote><strong><em>“Something happened. Tell the user.”</em></strong></blockquote><p>Now I think of it as:</p><blockquote><strong><em>“Something happened. Who should be responsible for what happens next?”</em></strong></blockquote><p>That distinction becomes increasingly important as products become more autonomous.</p><p>A good intelligent system shouldn’t constantly ask humans to supervise it.</p><p>It should handle what it can.</p><p>It should ask for help when it genuinely needs human judgment.</p><p>And when safety is involved, it should remove ambiguity.</p><p>So perhaps the most important question in alert UX isn’t:</p><p><strong>“How do we design a better alert?”</strong></p><p>It’s:</p><blockquote><strong><em>“When should the machine ask the human to care?”</em></strong></blockquote><p>That is where I believe UX for autonomous systems gets interesting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2d19c25d92d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When UX Leaves the Screen: Designing for Physical Controls]]></title>
            <link>https://medium.com/@ritika.kathal/when-ux-leaves-the-screen-designing-for-physical-controls-01ae32866234?source=rss-c9cf4846cb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/01ae32866234</guid>
            <category><![CDATA[industrial-design]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[human-machine-interaction]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ritika Kathal]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 14:59:41 GMT</pubDate>
            <atom:updated>2026-08-31T14:59:41.195Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zaxje-9TlnKK1XUGJvun0Q.png" /></figure><p>Think about the last time you picked up a TV remote.</p><p>You probably didn’t look at it.</p><p>Your hand already knew where <strong>volume</strong>, <strong>mute</strong>, <strong>channel</strong>, or <strong>back</strong> were. You pressed a button, looked at the TV, and moved on.</p><p><em>Now imagine someone suddenly moved all those buttons around.</em></p><p>Nothing about the TV has changed.<br>The buttons still do exactly the same thing.</p><p>And yet, the remote would immediately feel unfamiliar.</p><p>That’s because a physical controller isn’t just an interface you <strong>look at</strong>.</p><p>It’s an interface you <strong>touch, remember, and eventually operate without thinking.</strong></p><p>And that makes designing one surprisingly different from designing a normal screen UI.</p><h3>The problem with putting everything on a button</h3><p>A TV today can do hundreds of things.</p><p>You can change the picture mode, adjust brightness, connect Bluetooth headphones, switch subtitles, search for a movie, change audio settings, open an app, browse channels…</p><p>But look at the remote.</p><p>There isn’t a button for all of them.</p><p>And that’s not a limitation of the hardware.</p><p><strong>That’s a UX decision.</strong></p><p>Because every time we add a physical button, we’re asking the user to deal with one more thing.</p><p>One more label to read.</p><p>One more location to remember.</p><p>One more object competing for their attention.</p><p>A physical controller has something a screen doesn’t:</p><h3>A limited button budget.</h3><p>On a screen, I can add another option and hide it inside a menu.</p><p>On hardware, that button is going to sit there <strong>forever</strong>.</p><p>So the interesting question isn’t:</p><blockquote>“What can we make a button for?”</blockquote><p>It’s:</p><blockquote><strong><em>“What is important enough to deserve a physical button?”</em></strong></blockquote><h3>Not all actions deserve the same treatment</h3><p>This is where designing a physical HMI starts becoming interesting.</p><p>Imagine we take all the things a TV can do and put them into three buckets.</p><h3>1. Things you do constantly</h3><p>Volume.<br>Mute.<br>Power.<br>Play/Pause.</p><p>These deserve dedicated controls.</p><p>Why?</p><p>Because you don’t want to navigate through a menu every time you want to turn the volume down.</p><p>These controls should become almost automatic.</p><p><strong>Your finger should find them before your brain has to.</strong></p><h3>2. Things you do often, but in different situations</h3><p>This is where things like a <strong>directional pad</strong> become incredibly useful.</p><p>The same four buttons can help you:</p><ul><li>Navigate the home screen</li><li>Browse movies</li><li>Move through settings</li><li>Select channels</li><li>Navigate an on-screen keyboard</li></ul><p>The physical buttons stay the same.</p><p><strong>The screen changes what they mean.</strong></p><p>This gives us a lot of functionality without needing a lot of hardware.</p><p>And this is one of the biggest differences between physical and digital interaction:</p><blockquote><strong><em>A physical button can stay fixed while its digital meaning changes.</em></strong></blockquote><h3>3. Things you rarely use</h3><p>Brightness.</p><p>Advanced picture settings.</p><p>Subtitle preferences.</p><p>Bluetooth configuration.</p><p>Sleep timers.</p><p>These don’t necessarily need a physical button.</p><p>They can live on the screen, where we have much more freedom to organise, hide and change them.</p><p>So the physical controller becomes a <strong>shortcut system for the most important interactions</strong>, rather than a physical representation of the entire software.</p><h3>The trick is deciding what stays fixed</h3><p>This is probably one of the most important decisions when designing a physical controller:</p><blockquote>What should never change?</blockquote><p>&amp;</p><blockquote>What can change depending on context?</blockquote><p>Fixed controls are the ones users should be able to find almost instinctively.</p><p>Think about <strong>volume + and −</strong>.</p><p>If you moved them around every time the user opened a different app, it would be awful.</p><p>Physical interfaces benefit enormously from <strong>consistency</strong>.</p><p>Because consistency creates muscle memory.</p><p>But then we have controls like the directional pad, whose meaning can change without confusing us.</p><p>So there is a useful balance:</p><p><strong>Keep the physical interaction stable.<br>Let the digital context change around it.</strong></p><h3>But how many buttons are enough?</h3><p>There is no magic number.</p><p>But I wouldn’t start with:</p><blockquote><em>“We have 25 functions, so we need 25 buttons.”</em></blockquote><p>I’d start by looking at the functions themselves.</p><p>For every action, ask:</p><p><strong>How often is it used?</strong></p><p>If the answer is <em>all the time</em>, give it a button.</p><p><strong>How important is it?</strong></p><p>If it needs to be accessed immediately, don’t bury it in a menu.</p><p><strong>Does its meaning change?</strong></p><p>If yes, consider making it a contextual control.</p><p><strong>Does the user need to remember it?</strong></p><p>If yes, a consistent physical position becomes valuable.</p><p><strong>Can it easily be handled on the screen?</strong></p><p>If yes, maybe it doesn’t need hardware at all.</p><p>You eventually get something like:</p><blockquote><strong><em>Frequent + important → Physical button</em></strong></blockquote><blockquote><strong><em>Frequent + contextual → Shared physical control</em></strong></blockquote><blockquote><strong><em>Rare + complex → Digital UI</em></strong></blockquote><p>It’s not a strict formula, but it’s a useful way to make the decision.</p><h3>Then comes the part screens can’t do</h3><p>Physical interfaces have another advantage:</p><p><strong>You can use them without looking.</strong></p><p>Think about driving.</p><p>You don’t look down every time you turn the indicator on.</p><p>You know where the control is.</p><p>The same thing happens with a familiar remote.</p><p>Your hand develops a mental map:</p><p><em>“Volume is here.”</em><br><em>“Mute is just below it.”</em><br><em>“The navigation controls are in the middle.”</em></p><p>That means physical UX isn’t only about <strong>visual hierarchy</strong>.</p><p>It’s also about:</p><p><strong>Reachability.<br>Spacing.<br>Shape.<br>Texture.<br>Resistance.<br>Tactile feedback.</strong></p><p>A button can communicate through your fingertips.</p><p>That’s something a screen simply can’t do.</p><h3>And the button isn’t even where the feedback happens</h3><p>Here’s the part that makes physical HMI particularly interesting.</p><p>You press a button on the remote.</p><p>But the remote isn’t necessarily what responds.</p><p>You press:</p><p><strong>Volume +</strong></p><p>Your finger gets a physical click.</p><p>And then the <strong>TV screen</strong> tells you:</p><p><strong>38 → 39</strong></p><p>The interaction is happening across two interfaces.</p><p><strong>Physical input → Digital response</strong></p><p>Which means we aren’t really designing a remote and a UI separately.</p><p>We’re designing <strong>one interaction system with two surfaces.</strong></p><p>The controller tells the system:</p><blockquote><strong>“The user wants to do this.”</strong></blockquote><p>The screen tells the user:</p><blockquote><strong>“Here’s what just happened.”</strong></blockquote><p>If either side is confusing, the whole experience breaks.</p><h3>The real skill is knowing what not to make a button</h3><p>This is where physical HMI differs most from traditional UI design.</p><p>With a screen, we have the luxury of infinite-ish flexibility.</p><p>We can add a button today and remove it tomorrow.</p><p>Hardware doesn’t work that way.</p><p>Once a button exists, it takes up space, demands attention and becomes part of the user’s mental map.</p><p>So good physical HMI isn’t about squeezing the maximum number of functions into the controller.</p><p>It’s about being selective.</p><p><strong>Some interactions deserve permanence.<br>Some deserve flexibility.<br>And some don’t deserve a button at all.</strong></p><p>That’s ultimately what we’re designing when we design a remote, controller, cockpit panel or industrial HMI.</p><p>Not buttons.</p><p><strong>We’re deciding which actions are important enough to become physical.</strong></p><p>And once you put something under a user’s fingertip, <strong>that’s a much bigger UX decision than putting it on a screen.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01ae32866234" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Beyond the Screen: When UI Meets Physical Hardware]]></title>
            <link>https://medium.com/@ritika.kathal/designing-beyond-the-screen-when-ui-meets-physical-hardware-dbb458ab1199?source=rss-c9cf4846cb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbb458ab1199</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[human-machine-interaction]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Ritika Kathal]]></dc:creator>
            <pubDate>Tue, 25 Aug 2026 14:44:48 GMT</pubDate>
            <atom:updated>2026-08-25T14:44:48.156Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XROHgwXB16VsyLwh6wpN-g.png" /><figcaption>GCS MOCKUP</figcaption></figure><p>Designing a UI in Figma is predictable.</p><p>Designing one that must align with <strong>physical buttons, a screen bezel, and a human operator is not.</strong></p><p>On a rugged unmanned ground vehicle (UGV), the Ground Control Station (GCS) used physical buttons alongside on-screen labels. Operators relied on both: <strong><em>the UI showed what each control did, while the physical button provided the interaction</em></strong>.</p><p>The problem was that the labels and buttons did not line up. Fixing it meant aligning the digital labels with the real button positions — not just adjusting pixels, but connecting the UI to the physical product.</p><h3>The Problem</h3><p>The initial HMI was designed using the available 3D/CAD dimensions.</p><p>The screen resolution was fixed, and the UI button positions were designed around the expected physical button locations.</p><p>However, during hardware integration, a few things changed.</p><p>The result was subtle but important:</p><ul><li>UI buttons were no longer aligned with the physical buttons.</li><li>Some controls appeared slightly too high or too low.</li><li>The visual spacing between UI controls and hardware controls felt inconsistent.</li><li>Repeating the problem across multiple screens would create an inconsistent HMI.</li></ul><p>The hardware was already manufactured.</p><p><strong>So the UI had to adapt to the physical reality.</strong></p><h3>Why This Was More Than a Visual Problem</h3><p>The first instinct was to simply scale the UI until the buttons looked aligned.</p><p>But that raised a bigger question:</p><blockquote><strong><em>What exactly should we align to?</em></strong></blockquote><p>The bezel?</p><p>The visible screen?</p><p>The LCD’s active area?</p><p>The edge of the physical button?</p><p>Or the centre of the physical button?</p><p>For a conventional desktop interface, a few pixels of difference might be insignificant.</p><p>For a physical HMI, it can affect the operator’s interaction.</p><p>The user sees a button on the screen and instinctively reaches toward the corresponding physical control.</p><p>That means the relationship between:</p><p><strong>visual target → physical control → hand movement</strong></p><p>has to feel intentional.</p><h3>Exploring the Options</h3><p>I considered three possible approaches.</p><h3>Option 1 — Scale the entire UI</h3><p>The quickest solution was to scale the UI based on a photograph of the final hardware.</p><p><strong>Pros</strong></p><ul><li>Quick to test</li><li>Easy to visualize</li><li>Minimal redesign</li></ul><p><strong>Cons</strong></p><ul><li>Changes the overall UI proportions</li><li>Can distort layouts and typography</li><li>Doesn’t solve unequal physical button spacing</li><li>Photograph-based measurements aren’t reliable enough for final calibration</li></ul><p>This was useful as an initial exploration, but not as the final approach.</p><h3>Option 2 — Manually reposition every screen</h3><p>Another option was to move the UI buttons independently on every screen until they matched the hardware.</p><p>This would work technically.</p><p>But it creates a new UX problem:</p><p><strong>Inconsistency.</strong></p><p>One screen might have the first button at one position while another screen has it a few pixels away.</p><p>Over time, these small differences become noticeable.</p><p>It would also make future UI changes much harder.</p><h3>Option 3 — Make the hardware the source of truth</h3><p>This became the preferred approach.</p><p>Instead of asking:</p><blockquote><strong><em>“Where did we originally design the button?”</em></strong></blockquote><p>I changed the question to:</p><blockquote><strong><em>“Where does the physical button actually exist?”</em></strong></blockquote><p>That meant measuring the final hardware and rebuilding the UI alignment around those measurements.</p><h3>The Approach</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ol4GGaHrWdHg6WT0-vcNsg.png" /><figcaption>Steps followed to align physical and UI labels in GCS</figcaption></figure><h3>1. Measure the physical hardware</h3><p>Rather than relying on the photograph, I used the actual hardware as the reference.</p><p>For each physical button, I captured its <strong>centre position relative to the active display</strong>.</p><p>Importantly, I measured the <strong>centre</strong>, not the top or bottom edge.</p><p>Why?</p><p>Because the centre represents the actual interaction point.</p><p>The measurements were then converted from physical units into screen coordinates.</p><h3>2. Create a Hardware Alignment Grid</h3><p>I created a reference layer in Figma representing the actual hardware.</p><p>Something conceptually like:</p><pre>1920 × 1200 display</pre><pre>        ↓</pre><pre>   ● Button 1</pre><pre>   ● Button 2</pre><pre>   ● Button 3</pre><pre>   ● Button 4</pre><pre>   ● Button 5</pre><p>Each dot represented the centre of a real physical button.</p><p>These positions became <strong>fixed hardware constraints</strong>.</p><p>The UI was then designed around those constraints.</p><h3>3. Stop Assuming Equal Spacing</h3><p>This was an important design decision.</p><p>The physical buttons weren’t perfectly evenly spaced.</p><p>Instead of forcing the UI into an artificial equal-spacing system, I allowed the digital controls to follow the physical hardware.</p><p>In other words:</p><p><strong>The design system had to respect the hardware geometry.</strong></p><p>This is different from designing a purely digital interface where equal spacing is often desirable.</p><h3>4. Create Reusable Button Rails</h3><p>Rather than fixing every screen individually, I created reusable left and right navigation structures.</p><p>The physical button coordinates became the foundation of these components.</p><p>This meant:</p><p><strong>Hardware position → Button component → Multiple screens</strong></p><p>instead of:</p><p><strong>Hardware position → manually adjust every screen</strong></p><p>That made the solution much more scalable.</p><h3>A Small but Important UX Decision</h3><p>One of the most important changes was deciding to align based on the <strong>centre of the physical button</strong> rather than its edges.</p><p>For example:</p><pre>Physical button<br>        ┌───────────┐<br>        │           │<br>        │     ●     │  ← interaction centre<br>        │           │<br>        └───────────┘<br>              │<br>              │<br>        UI button centre</pre><p>This creates a much more natural physical-to-digital relationship.</p><p>The operator doesn’t think in terms of bounding boxes.</p><p>They think:</p><p><strong>“That button is there.”</strong></p><p>The UI needs to reinforce that mental model.</p><h3>Validation on the Actual Device</h3><p>After implementing the new alignment, the next step wasn’t another Figma review.</p><p>It was the device.</p><p>The HMI was tested directly on the hardware and the alignment was refined through physical validation.</p><p>This helped catch issues that are difficult to identify from a design file alone:</p><ul><li>perceived misalignment</li><li>inconsistent visual gaps</li><li>relationship between button and label</li><li>readability around the bezel</li><li>whether the physical interaction felt natural</li></ul><p>The final alignment was then treated as a hardware constraint rather than a screen-specific adjustment.</p><h3>The Design Principle</h3><blockquote><strong><em>When digital and physical interfaces meet, the physical world becomes a design constraint — not an afterthought.</em></strong></blockquote><p>This experience changed how I think about HMI design.</p><p>For future projects, I would bring physical measurements into the design process much earlier, establish a hardware coordinate system before building the complete UI, and validate interaction on the actual device before treating the interface as final.</p><p>Because ultimately, an HMI isn’t successful when it looks aligned in Figma.</p><p><strong>It’s successful when the operator doesn’t have to think about the alignment at all.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbb458ab1199" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Used to Inherit Wisdom. Now We Remix It.]]></title>
            <link>https://medium.com/@ritika.kathal/we-used-to-inherit-wisdom-now-we-remix-it-bcc8e2b72b53?source=rss-c9cf4846cb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcc8e2b72b53</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[gen-z]]></category>
            <dc:creator><![CDATA[Ritika Kathal]]></dc:creator>
            <pubDate>Thu, 13 Aug 2026 21:52:37 GMT</pubDate>
            <atom:updated>2026-08-13T21:52:37.634Z</atom:updated>
            <content:encoded><![CDATA[<p>Lately, I’ve been noticing how many of our everyday phrases are quietly becoming life philosophies.</p><blockquote><strong>“I am enough.”</strong></blockquote><blockquote><strong>“The grass is greener where you water it.”</strong></blockquote><blockquote><strong>“Protect your peace.”</strong></blockquote><blockquote><strong>“Choose yourself.”</strong></blockquote><p>We see them everywhere. On Instagram, in songs, in conversations, on coffee mugs, in memes.</p><p>And I started wondering:</p><p><strong>Have we always talked to ourselves like this? Or is this something new?</strong></p><p>I think we’ve always done it.</p><p>We have just changed the packaging.</p><h3>From bhajans to memes</h3><p>Our grandparents had bhajans, chants, prayers and folk stories.</p><p>Our parents had film dialogues, songs and cult classics.</p><p>We have podcasts, playlists, Instagram reels, memes and therapy language.</p><blockquote><strong>Different generations. Different mediums.</strong></blockquote><p>But underneath all of it is the same human need:</p><blockquote><strong>Give me a few words that help me make sense of what I’m going through.</strong></blockquote><p>A bhajan might have given someone peace.</p><p>A film dialogue might have given someone courage.</p><p>A song might have helped someone survive a breakup.</p><p>Today, an Instagram post saying <em>“You don’t have to earn your worth”</em> might do the same thing.</p><p>The source changed.</p><p><strong>The need didn’t.</strong></p><h3>But something else has changed</h3><p>Earlier, most of these ideas were inherited.</p><p>They came from parents, religion, culture, books, teachers or society.</p><p>You were told what something meant.</p><p>Today, we have an almost ridiculous number of meanings available to us.</p><blockquote><strong>A therapist from another country.</strong></blockquote><blockquote><strong>A stranger on Reddit.</strong></blockquote><blockquote><strong>A lyric from a 20-year-old song.</strong></blockquote><blockquote><strong>A meme account.</strong></blockquote><blockquote><strong>A creator you’ve never met.</strong></blockquote><p>Someone sends you a reel at 1 a.m., and suddenly a stranger’s sentence becomes something you needed to hear.</p><p>We don’t just inherit wisdom anymore.</p><h3>We browse it.</h3><p>And more importantly, we edit it.</p><h3>Take the grass example</h3><p>We’ve all heard:</p><blockquote><strong><em>“The grass is always greener on the other side.”</em></strong></blockquote><p>The traditional message is simple: don’t compare your life with someone else’s.</p><p>Then came:</p><blockquote><strong><em>“The grass is greener where you water it.”</em></strong></blockquote><p>Now the message is about investing in what you already have.</p><p>But you could just as easily say:</p><blockquote><strong><em>“If the grass is greener somewhere else, go there.”</em></strong></blockquote><p>Now it’s about leaving.</p><p>A bad relationship.</p><p>A bad job.</p><p>A city that doesn’t feel like home.</p><p><strong>Three sentences.</strong></p><p><strong>Three completely different philosophies.</strong></p><p>And maybe that’s one of the biggest cultural shifts happening now.</p><p>We don’t always ask:</p><p><strong>“Which saying is true?”</strong></p><p>We ask:</p><blockquote><strong><em>“Which version is true for me?”</em></strong></blockquote><h3>Then came “I am enough”</h3><p>“I am enough” might be the most recognisable affirmation of our generation.</p><p>And I like it.</p><p>But I also think it gets misunderstood.</p><p>Does being “enough” mean you don’t need to grow?</p><p>Probably not.</p><p>Maybe it means:</p><blockquote><strong><em>I don’t have to hate myself into becoming better.</em></strong></blockquote><p>You can want a better career and still believe you’re enough.</p><p>You can want to change your body, move cities, leave a relationship, learn something new or completely reinvent yourself — without believing that the current version of you is worthless.</p><p>That’s a subtle shift.</p><p>Earlier messages often sounded like:</p><p><strong>Become better.</strong></p><p>The newer message is closer to:</p><p><strong>You are worthy while becoming better.</strong></p><p>And I think that’s genuinely interesting.</p><h3>But are we sometimes just putting pretty words on difficult feelings?</h3><p>This is where I’m conflicted.</p><p>The internet has made it incredibly easy to turn every uncomfortable experience into a neat little sentence.</p><p><strong>Breakup?</strong></p><p><em>Everything happens for a reason.</em></p><p><strong>Bad day?</strong></p><p><em>Protect your peace.</em></p><p><strong>Failure?</strong></p><p><em>It’s just redirection.</em></p><p><strong>Burnout?</strong></p><p><em>Rest is productive.</em></p><p>Sometimes these words help.</p><p>But sometimes they are just prettier ways of avoiding the actual problem.</p><blockquote><strong><em>Not every heartbreak is a lesson.</em></strong></blockquote><blockquote><strong><em>Not every failure is secretly a blessing.</em></strong></blockquote><blockquote><strong><em>Sometimes you made a bad decision.</em></strong></blockquote><blockquote><strong><em>Sometimes someone hurt you.</em></strong></blockquote><blockquote><strong><em>Sometimes you need to apologise.</em></strong></blockquote><blockquote><strong><em>Sometimes you need to leave.</em></strong></blockquote><p>And sometimes something simply hurts, without needing to become a motivational quote.</p><p>Maybe an affirmation shouldn’t make reality disappear.</p><p>Maybe its job is to help you <strong>face reality without losing yourself in it.</strong></p><h3>So, are younger generations actually different?</h3><p>Maybe.</p><p>But I don’t think Gen Z or Gen Alpha invented self-affirmation.</p><p>They’ve made it <strong>participatory.</strong></p><p>Older generations inherited many of their phrases.</p><p>We remix ours.</p><p>We take an old proverb, change five words, put it over a song, turn it into a reel and suddenly thousands of people are discussing an idea that might be hundreds of years old.</p><p><strong>Culture has become editable.</strong></p><p>And perhaps that’s the real shift.</p><p>We are becoming less comfortable accepting an idea simply because it has always been said.</p><p>We ask:</p><h3>Why?</h3><blockquote><strong>Why should success look like this?</strong></blockquote><blockquote><strong>Why should I stay?</strong></blockquote><blockquote><strong>Why should I compare?</strong></blockquote><blockquote><strong>Why should this old rule apply to my life?</strong></blockquote><p>And sometimes, after questioning it, we keep the old idea.</p><p>Sometimes we throw it away.</p><p>And sometimes we rewrite it.</p><h3>Maybe that’s how meaning survives</h3><p>Perhaps this is how humans have always evolved.</p><blockquote><strong>We inherit words.</strong></blockquote><blockquote><strong>We give them meaning.</strong></blockquote><blockquote><strong>We outgrow them.</strong></blockquote><blockquote><strong>We rewrite them.</strong></blockquote><p>Then someone younger comes along and does it again.</p><p>The bhajan, the movie dialogue, the song, the quote, the meme — they may look completely different.</p><p>But perhaps they’re all doing the same quiet job.</p><p><strong>Giving us language for something we don’t quite know how to say ourselves.</strong></p><p>So the next time you see <strong>“I am enough”</strong>, maybe don’t ask whether it’s objectively true.</p><p>Ask:</p><blockquote><strong><em>What does “enough” mean to me right now?</em></strong></blockquote><p>Because maybe the sentence isn’t the affirmation.</p><h3>Maybe finding your own meaning is.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcc8e2b72b53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transforming Creativity into Compassion: The “Art for People” Campaign Amid COVID-19]]></title>
            <link>https://medium.com/@ritika.kathal/transforming-creativity-into-compassion-the-art-for-people-campaign-amid-covid-19-efa48716d692?source=rss-c9cf4846cb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/efa48716d692</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[art]]></category>
            <category><![CDATA[empath]]></category>
            <category><![CDATA[helping-others]]></category>
            <dc:creator><![CDATA[Ritika Kathal]]></dc:creator>
            <pubDate>Thu, 12 Oct 2023 20:25:53 GMT</pubDate>
            <atom:updated>2023-10-14T08:49:37.591Z</atom:updated>
            <content:encoded><![CDATA[<p>In the midst of the challenging COVID-19 pandemic in 2021, many of us found ourselves confined to our homes, facing the uncertainty of the times. During these moments of reflection, the idea of making a difference and offering a helping hand to those in need struck a chord with me.</p><h3>The Spark of Inspiration:</h3><p>As an artist, I spent my days creating art and during those times I wondered how I could channel my creativity and social media presence to provide some relief in the trying times. The answer lay in <strong>“Art for People”</strong> — a campaign born from a desire to connect art and altruism.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kwcOA02c3_rReXOvjR2xgA.png" /></figure><p>The concept was simple yet powerful — I would encourage people to donate, and in return, I would provide them with a piece of artwork as a token of appreciation. Not only would they get a tangible piece of art, but they would also be reminded of their good deed each time they looked at it.</p><p><strong>Unleashing the Power of Community:</strong></p><p>The journey began with a passionate belief that art could serve a higher purpose. I reached out to my artist friends within the creative community, sharing my vision and the potential for collective impact.</p><p>Our collective force lies in our shared love for art and the urge to make a difference. We made a pact to offer our art to those who donated to our campaign. We leveraged our social media platforms to create awareness about the “Art for People” initiative.</p><p>We were a group of artists, and our mission was clear: to promote our fellow artists and their creative works. By highlighting the artwork of our community members, <strong><em>we aimed to draw people’s attention and encourage their participation.</em></strong></p><p><strong>It wasn’t just about receiving art; it was about the shared vision of helping others.</strong></p><p>When people made their donations, we collected screenshots to ensure transparency. Our dedicated artist friends and volunteers came together to create bespoke artworks, inspired by the recipients’ preferences. It was an artistic exchange filled with gratitude, and every piece was imbued with our desire to give back.</p><h3>In just one week, our “Art for People” campaign had raised approximately 15,000 Rupees. The donations were destined for a noble cause.</h3><p><strong>A Helping Hand to the Needy:</strong></p><p>With the support of a local NGO, we donated the proceeds to a nearby Gurdwara. They were at the forefront of providing meals to the needy, ensuring that nobody went to bed hungry. It was heartening to witness our collective creativity transform into a lifeline for those in need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*l4PyuhzG9SRlINfAScxSig.png" /><figcaption>Donation at Gurdwara</figcaption></figure><h3><strong>My learning</strong></h3><blockquote>I discovered that art isn’t just about painting on canvas or mixing colors; it can actually do some pretty amazing things. It’s like a spark that can ignite positive change, a ray of hope in the darkest of times. The “Art for People” campaign showed us just how incredible it is when a bunch of creative folks come together. It taught us a powerful lesson: when we unite for a shared purpose, we don’t just create something beautiful; we also become a reminder of the goodness we all have inside us.</blockquote><p><strong>Our Rewards: </strong>Some artworks done by Art for People</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/268/1*WN9dmK1rvtUQvY_xrMJJJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*DmsgHZEiomsWUEDYQ1mctA.png" /></figure><blockquote><em>Follow on Instagram for more artwork:</em> <a href="https://www.instagram.com/passionate_pencil/">https://www.instagram.com/passionate_pencil/</a></blockquote><blockquote><em>Do share your views and follow on medium for discussion on art, design, life, or anything:)</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efa48716d692" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flow theory- My Interpretation of Happiness]]></title>
            <link>https://medium.com/@ritika.kathal/flow-theory-my-interpretation-of-happiness-c7cbd9b361a2?source=rss-c9cf4846cb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7cbd9b361a2</guid>
            <category><![CDATA[mihaly-csikszentmihalyi]]></category>
            <category><![CDATA[happiness]]></category>
            <category><![CDATA[flow-theory]]></category>
            <category><![CDATA[art]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Ritika Kathal]]></dc:creator>
            <pubDate>Sat, 19 Mar 2022 07:52:06 GMT</pubDate>
            <atom:updated>2025-02-01T21:28:58.915Z</atom:updated>
            <content:encoded><![CDATA[<p>From the ages the basis of human existence is about living a happy life, finding happiness in life with what you do, where you live, with whom you are connected, and similar cases. This is a broad field and much research has been done and is still going on to find the “ how to…” aspect of this story.</p><p>Although the core of happiness comes from the inside as found in various researches, As discovered by happiness researcher Mihaly Csikszentmihalyi</p><p>“Happiness is <a href="https://blogs.baruch.cuny.edu/authenticityandastonishment2/files/2013/04/Mihaly-Csikszentmihalyi-Flow1.pdf">a condition that must be prepared for, cultivated, and defended privately by each person. <strong>People who learn to control inner experience will be able to determine the quality of their lives, which is as close as any of us can come to being happy.</strong>”</a></p><p>Our life is a combination of various outside factors- natural, physical, social, economic, or others. We can not always control the perspective of our life, which is an outcome of these external factors, whether good or bad.</p><p>But, in our lifetime we do experience moments when instead of being pounded over by external forces we do feel in control of our emotions. On the rare occasion when this happens we feel a sense of exhilaration, a sense of enjoyment, and such a moment becomes a core memory for what life should feel like. This is what is known as <strong><em>optimal experience</em></strong>.</p><p>The term “ flow state” coined by Mihaly Csikszentmihalyi interprets as “a state in which people are so involved in an activity that nothing else seems to matter; the experience is so enjoyable that people will continue to do it even at great cost, for the sheer sake of doing it”.</p><blockquote>Let me explain this to you with an example from my personal life,</blockquote><p>During the time I was preparing for JEE entrance,</p><p>I had no means to de-stress<em>-</em> no Television, limited mobile phone, and internet access ( those were the days with 100MB/day recharge and the luxury of Jio pack did not exist). So, my only escape and mood fresher from all the studying was <strong>sketching</strong> on the back of my worksheets :p.</p><p>The main task here was to hide these sheets from my parents, as I should be spending this time more productively on academics. The experience of engaging in an activity was difficult since I was <em>sketching after so many years</em> and involved risks like <em>keeping it a secret from my family.</em> Ultimately stretched my mind’s capacity and provided a challenge to my skills.</p><blockquote>“The best moments in our lives are not the passive, receptive, relaxing times . . . The best moments usually occur if a person’s body or mind is stretched to its limits in a voluntary effort to accomplish something difficult and worthwhile”<br>(Csikszentmihalyi, 1990)</blockquote><p>Now with clear goals like completing the sketch and the positive feedback from my friends. With compliments from strangers over the internet it started feeling intrinsically rewarding. So with more practice, my skills were improving and I started aiming for more and more challenging portraits. I have gone days skipping my lunch or dinner or sleep to complete a full detailed portrait, sometimes even spent the whole day working on various artwork.</p><p><em>You can see the progress over the years……..</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*arofqZoiYDDGZhu9NiA7_w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cxuBvhLcckyBxLkh3mKASw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*uaGEwiHpwo5bXfOqA7T6TA.jpeg" /><figcaption>For more artwork visit: <a href="https://www.instagram.com/passionate_pencil/">https://www.instagram.com/passionate_pencil/</a></figcaption></figure><p>As depicted in the graph proposed by Csikszentmihalyi,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/663/1*k2M7EZv2dB-_S9o09E10vw.png" /><figcaption><a href="https://www.researchgate.net/figure/Csikszentmihalyi-Flow-Csikszentmihalyi-1996_fig2_321469435">https://www.researchgate.net/figure/Csikszentmihalyi-Flow-Csikszentmihalyi-1996_fig2_321469435</a></figcaption></figure><p>i) <strong>if the challenge is higher than skill </strong>- the person will experience anxiety because of not being able to complete the task,</p><p>ii) whereas<strong> if the skill is higher than the challenge </strong>- then the person will experience boredom while completing the task.</p><p>iii) <strong>The balance between both the challenge and skill leads to the flow state.</strong></p><p>Csikszentmihalyi reported that flow occurs more often during work than in free time. For me, <strong>creating art is a flow state because it is effortless and I have a feeling of control over the task.</strong></p><blockquote>Follow on Instagram for more artwork:<em> </em><a href="https://www.instagram.com/passionate_pencil/"><em>https://www.instagram.com/passionate_pencil/</em></a></blockquote><blockquote>Do share your views and follow on medium for discussion on art, design, life, or anything:)</blockquote><p>Reference:</p><p><a href="https://www.sciencedirect.com/topics/psychology/flow-theory">https://www.sciencedirect.com/topics/psychology/flow-theory</a></p><p><a href="https://blogs.baruch.cuny.edu/authenticityandastonishment2/files/2013/04/Mihaly-Csikszentmihalyi-Flow1.pdf">https://blogs.baruch.cuny.edu/authenticityandastonishment2/files/2013/04/Mihaly-Csikszentmihalyi-Flow1.pdf</a></p><p><a href="https://positivepsychology.com/mihaly-csikszentmihalyi-father-of-flow/">https://positivepsychology.com/mihaly-csikszentmihalyi-father-of-flow/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7cbd9b361a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analysis of semiotics in Klaus]]></title>
            <link>https://medium.com/@ritika.kathal/analysis-of-semiotics-in-klaus-e7d8763045f4?source=rss-c9cf4846cb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7d8763045f4</guid>
            <category><![CDATA[movies]]></category>
            <category><![CDATA[klaus]]></category>
            <category><![CDATA[fictional-characters]]></category>
            <category><![CDATA[semiotics]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[Ritika Kathal]]></dc:creator>
            <pubDate>Mon, 21 Feb 2022 12:21:37 GMT</pubDate>
            <atom:updated>2022-02-21T14:09:19.438Z</atom:updated>
            <content:encoded><![CDATA[<p>Klaus is an animated movie, released in 2019, Academy award-nominated SPA studio’s creation. Klaus is inspired by the story of the joyous Christmas tale of Santa Claus. Ever wonder how the whole Christmas gift tradition started- well it starts with a letter. This movie talks about how a failed postman turns a violent town into a peaceful and beautiful place, after being posted in Smeerensburg’s with the help of wood craftsmen, in the process of collecting 6000 letters in a year. The town was a hub of centuries-long family disputes between two families, men, women, and children fighting with each other. Until one night, when a postman interacted with a woodsman and came up with the idea of distributing toys in exchange for letters to kids. (planning his escape from town). This starts a chain of series of events, making children believe in Santa Claus Christmas tales.</p><p>This act of kindness which started with a selfish motive soon changed the heart of the town and changed the shabby town into a beautiful town.</p><p>This movie catches my attention for its use of semiotics by beautifully conveying emotions. The animation house uses the technique of 2D animation to make the movie looks 3D</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BTgjNFepIdpFA6GSIMnbUg.png" /><figcaption>A simple act of kindness always sparks another, even in a frozen, faraway place. When Smeerensburg’s new postman, Jesper, befriends toymaker Klaus, their gifts melt an age-old feud and deliver a sleigh full of holiday traditions. — Netflix</figcaption></figure><blockquote><strong>Let’s meet the characters….</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/387/0*v75bZqu0ao4qA0eO" /><figcaption>Jesper- the postman</figcaption></figure><p>Jesper. The main character of the movie is a tall physique, has quirky facial expressions. The character wears a half-length coat, with a hat, badges and carries a bag for collecting letters. The look tries to depict his commitment to the duty( although at the start he intended to just finish the job as soon as possible)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/0*Rk1wJaaSyCW72R34" /><figcaption>Mr. Klaus- the woodsman</figcaption></figure><p>Mr. Klaus. The other main character of the movie is of humongous build, a long beard. The character wears thick clothes with a long coat to keep him warm, also hand gloves, and carries an ax to work in wood. The build-up personality of the character gives a cold and intimidating feeling but as the movie moves on his character develops into a sweet and loving woodsman. ( your friendly neighborhood Santa Claus)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/387/0*X5tX7ayF8L3FBbw7" /><figcaption>Miss Alva- school teacher</figcaption></figure><p>Miss Alva. The other main character of the movie has a Strong personality, surviving in the mad town of Smeerenburg. The character wears a long skirt with a poncho on top, knife in hand to cut down fish gives her character an intimidating feel. Alva is a school teacher, who wanted to teach and make a difference but got trapped in a mad town, character design is depicting that frustration and anger.</p><p><strong>Semiotics/Symbolism Analysis</strong></p><p>Each sign consist of two-part</p><p>● Signifer: the form it takes</p><p>● Signified: the concept it represents,</p><p>Semiotic analysis has three steps:</p><p>i) Analyse verbal signs (what you see and hear),</p><p>ii) Analyse visual signs (what you see),</p><p>iii)Analyse the symbolic message (interpretation of what you see).</p><blockquote>Following are the analysis based on my individual interpretation and could vary for others</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IubtpRkRdmVYNIK1Z6JOeQ.png" /><figcaption>Post office view</figcaption></figure><p><strong>Signifer:</strong> The image shows a block with <em>hen</em> and <em>letters</em>.</p><p><strong>Signified: </strong>The image shows how hen is shifting to one side of the block because of the number of the increasing letters- increasing business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GaSU8S-ywnrUMQPSRYQY7Q.png" /><figcaption>Jesper holding a child’s drawing</figcaption></figure><p><strong>Signifer:</strong> The image shows a <em>drawing</em> made by a child.</p><p><strong>Signified: </strong>The drawing tries to convey the emotion of being <em>trapped</em> in the house, by a small child as guessed from scribed drawing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UpUggg-6qcEcXwvsvpWwew.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WqlKNtj911QC5PU0mhVehQ.png" /><figcaption>Map showing the areas of Smeerensburg within few months interval</figcaption></figure><p><strong>Signifer:</strong> Both images show maps and marking points, along with marking pins.</p><p><strong>Signified:</strong> The color in both images shows different emotions i.e, sadness(1) and happiness(2). Several marking pins in the first image represent loneliness and in the second sense of teamwork.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XgX-NBNnV1aOMnTY0buWuA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PyYTfSEp3BHTJZ9ElmZPfA.png" /><figcaption>Jesper’s interaction with Mr. Klaus</figcaption></figure><p><strong>Signifer:</strong> Both images give cold vibes, it has a <em>rope</em>, a person looking through it.</p><p><strong>Signified:</strong> The images show different emotions of fear(1) and relief(2). The first image manipulated the audience to believe as if the person is going to be hanged by the rope but in reality, the ropes tie a birdhouse on the tree.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hUHeo6e7IGovBbwCA9OVyw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NMUwW1IP3gKc5orWMODfcg.png" /><figcaption>Globe in a school</figcaption></figure><p><strong>Signifer:</strong> Both images have a <em>globe</em> from the local school of Smeerensburg, with a knife and map inserted on it respectively.</p><p><strong>Signified: </strong>The first image shows a knife inserted in a globe, trying to represent how knowledge is being murdered in this place In the second image, the globe has a map inserted in it showing the transformation from the first image to the second.</p><p><strong><em>Analysing the 5W and H,</em></strong></p><blockquote>The audience <em>who</em> love watching holiday feel-good movies with friends or family.</blockquote><blockquote>Christmas story is the most talked about topic all over the world, the audience gets <em>what</em> they are looking for in the movie a new perspective of a holiday feel.</blockquote><blockquote>The audience will watch this movie <em>when</em> the Christmas season is approaching.</blockquote><blockquote>The audience will watch this movie on the online platform, <em>where</em> the reach is maximum.</blockquote><blockquote>Beautiful semiotic elements motivate the audience to watch the movie, again and again, answering <em>why</em> the movie is so special.</blockquote><blockquote>The audience nowadays likes to watch <em>how</em> much movie resembles the origin stories.</blockquote><p>References</p><p><a href="https://torschrank.com/klaus-film/">https://torschrank.com/klaus-film/</a> retrieved on March 2021 for character images</p><p><a href="https://www.netflix.com/in/title/80183187">https://www.netflix.com/in/title/80183187</a> Klaus on Netflix</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7d8763045f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>