<?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 Prakriti Verma on Medium]]></title>
        <description><![CDATA[Stories by Prakriti Verma on Medium]]></description>
        <link>https://medium.com/@Prakriti-UIUXDesigner?source=rss-676df6dbf3b0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7lU9vkvi8kmka1p2HrKzew.png</url>
            <title>Stories by Prakriti Verma on Medium</title>
            <link>https://medium.com/@Prakriti-UIUXDesigner?source=rss-676df6dbf3b0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:57:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Prakriti-UIUXDesigner/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[Moneymind — AI powered personal finance tracker]]></title>
            <link>https://medium.com/design-bootcamp/moneymind-ai-powered-personal-finance-tracker-34ec774d36ac?source=rss-676df6dbf3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/34ec774d36ac</guid>
            <category><![CDATA[ui-ux-case-study]]></category>
            <category><![CDATA[finance-tracker]]></category>
            <category><![CDATA[ai-tools]]></category>
            <category><![CDATA[ai-patterns]]></category>
            <category><![CDATA[ai-powered-app]]></category>
            <dc:creator><![CDATA[Prakriti Verma]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 06:58:33 GMT</pubDate>
            <atom:updated>2026-04-07T22:28:54.231Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An hero image on MoneyMind app showing it’s features." src="https://cdn-images-1.medium.com/max/1024/1*OYlrKADxwpL41Cxdvy8_Yw.png" /></figure><blockquote><strong>Brief: </strong>Indian youngsters make 8–12 digital transactions daily across UPI, credit cards, and cash. Yet most have no clear picture of where their money goes. They download expense trackers, manually enter data for 3–4 days, then abandon the app. The apps that do offer auto-tracking show only backward-looking data — pie charts of last month’s spending. None predict what will happen next. None connect spending to goals. None support the 15 million freelancers whose income varies month to month.</blockquote><blockquote>MoneyMind is an AI-powered personal finance tracker that predicts spending, protects goals, and speaks the user’s language — designed specifically for Indian youngsters who want financial clarity without manual effort.</blockquote><p><strong>Problem Statement:<br></strong>Users struggle to understand and control their spending because existing expense trackers either demand manual data entry (which users abandon within days) or provide only historical data without predictions, goal connections, or support for variable income patterns.</p><p><strong>Solution:</strong><br>An AI-native finance app built on three pillars that no competitor offers:</p><ol><li>Predictive, not reactive: The app tells you “You’re on pace to exceed your dining budget by ₹4,200” on day 16, not day 31. It connects daily spending to goal timelines.</li><li>Conversational, not navigational: Users ask “How much on Swiggy vs Zomato?” in plain language and get instant answers with charts.</li><li>Adaptive, not one-size-fits-all: One onboarding decision (salaried vs freelancer) branches the entire app experience.</li></ol><p><strong>My Role:<br></strong>I led the project as sole designer and worked on all aspects — user research, information architecture, interaction design, and visual design using an AI-assisted workflow throughout.</p><p><strong>Tools Used:</strong> Figma, Claude, Figma Make, Stitch<br><strong>Duration:</strong> ~2 weeks (research to high-fidelity screens)<br><strong>Target Audience:</strong> Indian youngsters aged 23–35 (salaried and freelance)</p><p><strong>The Design Process:<br></strong>I followed a three-phased process — Define, Design, and Refine.</p><figure><img alt="Design Process — Define, Design, and Refine" src="https://cdn-images-1.medium.com/max/1024/1*s4GA78J5jhjUEXVUhOnSgw.png" /></figure><h4><strong>Phase 1: DEFINE</strong></h4><p>AI tool used: Claude — research synthesis, persona creation, IA structuring</p><p><strong>Secondary Research — Understanding Users First:<br></strong>I started the Define phase not by studying apps, but by studying people. I collected 100+ user reviews from app stores across 6 popular expense tracking apps in India (Axio, Wallet by BudgetBakers, Monefy, Money Manager, Spendee, and Money Lover). These reviews are where real users describe their frustrations in their own words — unfiltered, emotional, and honest.</p><p><strong><em>Why secondary research first: </em></strong><em><br>These are real user voices, not assumptions. Starting here meant that every design decision — from the SMS trust screen to the cash flow forecast — traces back to an actual user pain, not a hypothetical one.</em></p><p>I used Claude to synthesise these 100+ reviews and extract common pain point patterns. Claude clustered the reviews into 5 recurring themes:</p><ol><li>“I quit after 3 days” — Manual entry fatigue. Users start enthusiastic but can’t sustain daily logging.</li><li>“It just shows me what I already know” — Backward-looking data with no actionable insight. Pie charts don’t change behaviour.</li><li>“I don’t trust giving bank access” — Privacy anxiety around linking bank accounts. SMS parsing feels less invasive but users need transparency.</li><li>“My income isn’t fixed, budgets don’t work” — Freelancers and gig workers can’t use monthly budget models built for salaried users.</li><li>“I want to know if I’m okay, not just what I spent” — Users want forward-looking reassurance, not just historical records.</li></ol><figure><img alt="Review and ratings from app store." src="https://cdn-images-1.medium.com/max/1024/1*QPnyGNNfIHpxeyok32TGxw.png" /><figcaption>Real user reviews from app store</figcaption></figure><p><strong>Competitive Analysis:<br></strong>With the user pain points in hand, I then analysed the 6 apps themselves to see which pains they actually address. I mapped 8 AI capabilities against all 6 competitors — not just features, but intelligent capabilities that could solve the problems users described in their reviews.</p><blockquote><strong><em>The finding that shaped everything: </em></strong><em>Only 2 of 8 AI capabilities were addressed by any competitor. Predictive intelligence, conversational finance, goal-aware analysis, and anomaly detection were completely absent from the market. The user pain points from the reviews had no solutions in any existing app.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W_8xW2GJ-Hcks542UXT1dA.png" /><figcaption>Competitive Analysis</figcaption></figure><p>5 critical gaps no competitor addresses:</p><ol><li>No predictive intelligence Every app shows what happened. None predict what will happen. (Addresses pain #2 and #5)</li><li>No natural language queries Users navigate menus. None let you ask “How much on Swiggy?” (Addresses pain #2)</li><li>No spending-to-goal connection Goals and spending exist in separate worlds. (Addresses pain #5)</li><li>Fixed salary assumption Every budget model breaks for variable-income freelancers. (Addresses pain #4)</li><li>Manual entry dependence 4 of 6 apps require manual entry. Users quit within 4 days. (Addresses pain #1)</li></ol><p><strong>User Personas:<br></strong>The personas emerged directly from the review synthesis — not invented from assumptions. Two distinct financial mindsets appeared in the data: users who earn a fixed salary and struggle with spending awareness, and users with variable income who struggle with financial security. <br>Claude helped draft the data-driven profiles; I rewrote them to feel like real people — adding the emotional context (financial guilt, anxiety, embarrassment) that AI consistently misses.</p><figure><img alt="Persona 1 — The Anxious Planner" src="https://cdn-images-1.medium.com/max/1024/1*rKi1KjdTsH2YnXUjuXG3pg.png" /><figcaption>Persona 1 — The Anxious Planner</figcaption></figure><figure><img alt="Persona 2 — The Goal-Oriented Saver" src="https://cdn-images-1.medium.com/max/1024/1*L6FvzUv_rlcEJZAq5wFSJA.png" /><figcaption>Persona 2 — The Goal-Oriented Saver</figcaption></figure><blockquote><strong>Key insight:</strong> Meera needs spending AWARENESS. Rohit needs financial SECURITY. One app, two fundamentally different dashboard hierarchies — driven by a single onboarding decision.</blockquote><p><strong>User Journey Mapping:<br></strong>I mapped both personas across 4 stages: Discovery, Onboarding, First Week, and First Month. Critical finding: two drop-off points — SMS permission anxiety during onboarding, and manual entry fatigue in week 1. Both informed the AI features I designed.</p><figure><img alt="User Journey Map for Persona 1" src="https://cdn-images-1.medium.com/max/1024/1*1QCikdlwwnWUXfaIaTwI0Q.png" /><figcaption>User Journey Map for Persona 1</figcaption></figure><figure><img alt="User Journey Map for Persona 2" src="https://cdn-images-1.medium.com/max/1024/1*S3RyXoMqqRCpepM1SMKgaA.png" /><figcaption>User Journey Map for Persona 2</figcaption></figure><p><strong>How Might We (HMW):</strong></p><ol><li>How might we track spending automatically without requiring bank account access, so privacy-conscious users feel safe from Day 1?</li><li>How might we make manual expense entry so fast that it feels effortless, even for someone logging 4–6 transactions every evening?</li><li>How might we use AI to auto-suggest the right category, account, and tags so the user only confirms rather than decides?</li><li>How might we build trust in SMS permission during onboarding so users grant access without hesitation?</li><li>How might we predict spending overshoots BEFORE they happen and give users a specific, achievable action to stay on track?</li><li>How might we intelligently suggest how to allocate income when it arrives so users don’t have to do the mental maths of goals vs. spending vs. buffer?</li><li>How might we frame financial insights as empowering actions rather than judgmental observations so users feel like they’re winning, not failing?</li><li>How might we enable couples and families to manage money together without losing individual financial privacy?</li><li>How might we create a single “financial health score” that tells users how they’re doing without requiring them to interpret charts and numbers?</li><li>How might we let users ask their finances questions in plain language and get instant, personalised, context-aware answers?</li></ol><h4>Phase 2 — DESIGN</h4><p><strong>AI tool used:</strong> Claude (IA, UX writing) · Figma Make (screen generation) · Stitch (component variations)</p><p><strong>Information Architecture:<br></strong>The IA includes adaptive logic — different content hierarchy for salaried vs freelancer, driven by one onboarding decision.</p><figure><img alt="Sitemap" src="https://cdn-images-1.medium.com/max/1024/1*gDSRBvRBIfeXNK7Mvc2qAA.png" /><figcaption>Sitemap</figcaption></figure><figure><img alt="Onboarding User flow" src="https://cdn-images-1.medium.com/max/1024/1*R5JxZUb2-SxKlOtf8lWnhg.png" /><figcaption>Onboarding User flow</figcaption></figure><p><strong>Visual Direction:<br></strong>I established the design language before touching screens. <br>The direction: calm fintech meets AI intelligence.</p><figure><img alt="Moodboard" src="https://cdn-images-1.medium.com/max/1024/1*IMp_bI901OQQovGvcxx1Yw.png" /><figcaption>Moodboard</figcaption></figure><p><strong>Visual Screens:</strong></p><figure><img alt="Onboarding, Dashboard, Transaction screens" src="https://cdn-images-1.medium.com/max/1024/1*8GKVjAZIMrcaOWjzURRQ8Q.png" /><figcaption>Onboarding, Dashboard, Transaction screens</figcaption></figure><h4>Phase 3 — REFINE</h4><p><strong>AI tool used: </strong>Claude — design critique, edge case discovery, interaction refinement</p><p><strong>Heuristic Evaluation:<br></strong>I evaluated my designs with Jacob’s ten usability heuristics and implemented changes wherever needed.</p><figure><img alt="Heuristic Evaluation" src="https://cdn-images-1.medium.com/max/1024/1*KxmVPgJU0KVNeT84CAKUbw.png" /><figcaption>Heuristic Evaluation</figcaption></figure><p><strong>My AI Design Principles:</strong></p><ol><li>Automate the tedious, augment the decisions, never replace the control. Auto-categorise (tedious). Suggest allocation (decision). Never auto-transfer money (control).</li><li>Show, don&#39;t tell. Suggestion chips teach scope by example - no limitations page needed.</li><li>Prevent, don&#39;t reject. Autocomplete steers users toward valid queries before submission.</li><li>Redirect, don&#39;t block. Out-of-scope queries get acknowledge, explain, offer alternative. Never dead-end.</li><li>Facts vs projections. &quot;You spent ₹12K&quot; = no note. &quot;You&#39;ll spend ₹14.2K&quot; = &quot;Based on 16 days.&quot;</li><li>Earn trust progressively. <br>Week 1: categorise. Week 2: insights. Month 1: predictions. Month 2+: scenarios.</li></ol><p><strong>Conclusion:<br></strong>This project demonstrated that AI can transform both the product and the design process itself. MoneyMind uses 10 AI interaction patterns across 3 core screens — not as decorative features, but as the fundamental way users interact with their financial data.<br>The AI-assisted design process compressed a month-long project into 2 weeks. But the real value wasn’t speed — it was depth. AI handled synthesis and generation so I could focus on the decisions that require human judgment: emotional tone, visual hierarchy, adaptive logic, and the nuanced trust-building that makes users feel empowered rather than surveilled.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34ec774d36ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/moneymind-ai-powered-personal-finance-tracker-34ec774d36ac">Moneymind — AI powered personal finance tracker</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[“The AI Says So” Is Not a UX Strategy]]></title>
            <link>https://medium.com/design-bootcamp/the-ai-says-so-is-not-a-ux-strategy-94adf85f5f6c?source=rss-676df6dbf3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/94adf85f5f6c</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[explainable-ai]]></category>
            <dc:creator><![CDATA[Prakriti Verma]]></dc:creator>
            <pubDate>Sun, 22 Mar 2026 10:20:14 GMT</pubDate>
            <atom:updated>2026-03-22T12:13:40.757Z</atom:updated>
            <content:encoded><![CDATA[<h4>What I learned designing AI products for users who have zero interest in how the algorithm works</h4><figure><img alt="Black box v/s Explainable UX" src="https://cdn-images-1.medium.com/max/1024/1*K9bhk2EQ4Wax0CZ9F4s-_w.png" /><figcaption>Black box v/s Explainable</figcaption></figure><p>There’s a moment in every AI product’s life when someone asks the obvious question:</p><p><em>“Why did it flag this?”</em></p><p>And if the only answer your interface can give is a confidence score (“87% likely” or “high risk”), you’ve already lost them.</p><p>I’ve spent the past year leading UX design on an enterprise AI platform. The product uses machine learning to detect anomalies across massive datasets. Patterns that humans would never catch manually. The algorithms are genuinely sophisticated. Multiple detection conditions running in parallel. Weather correlation. Peer-group comparison. Behavioral trend analysis. Statistical validation.</p><p>The AI worked. The users didn’t use it.</p><p>That gap between what the algorithm knows and what the user trusts enough to act on is where I’ve been living as a designer. And what I learned there changed how I think about every AI product.</p><h3>The trust problem nobody talks about</h3><p>Here’s the uncomfortable truth about enterprise AI: the people who need the output most are usually the least equipped to evaluate it.</p><p>In my case, the end users were operations teams and field investigators. Not data scientists. Not engineers. People who manage thousands of assets in real-time, make decisions under time pressure, and have exactly zero patience for “the model thinks.”</p><p>When we first launched, the interface showed a single risk score per flagged item. A number. No breakdown. No explanation. No way for the user to verify whether the flag was legitimate or garbage.</p><p>What happened was predictable.</p><p>The veteran operators, the ones with 15 years of domain expertise, glanced at the flags, didn’t trust them, and went back to their old process. The newer team members tried using the system but couldn’t defend the flags to their managers when asked “why did you prioritize this one?”</p><p>Months of data science work. Sitting unused. Not because the model was wrong, but because the interface couldn’t explain why the model was right.</p><p>That’s when I realized: explainability isn’t a data science problem. It’s a design problem. And it became my primary design workstream.</p><h3>Pattern 1: Show the “why,” not just the “what”</h3><p>The first thing we killed was the single aggregate score.</p><p>Instead, we designed an additive risk model where the total score is the sum of individually visible conditions. A flagged item scoring 580 isn’t just “580.” It’s:</p><ul><li>200 points from a weather-correlated anomaly</li><li>180 points from a peer-comparison outlier</li><li>200 points from an unusual event pattern</li></ul><p>Three reasons. Each one visible. Each one understandable in plain language.</p><p>This was a deliberate design choice, not just a visual one. We could have used any scoring model: weighted averages, neural network confidence, ensemble methods. We chose addition because it’s the one mathematical operation that every human being understands intuitively.</p><p>When a field investigator reads three specific reasons instead of one opaque number, something shifts. They stop asking “should I trust this?” and start asking “do these three things together make sense?” That’s a fundamentally different cognitive mode. They’re evaluating evidence, not evaluating the AI.</p><p><strong>The UX principle:</strong> Decompose every AI output into human-readable contributing factors. If the user can’t trace the score back to its inputs, the score is decoration.</p><h3>Pattern 2: Let users own the decision boundaries</h3><p>Here’s a mistake I see in almost every AI product: the algorithm has parameters (thresholds, weights, observation windows) and the designers hide them.</p><p>The assumption is that users don’t want to see the complexity. And that’s true. They don’t want to <em>see</em> it. But they desperately want to <em>control</em> it.</p><p>In our platform, every detection parameter is exposed and configurable. The threshold for what counts as “below average consumption”? The user sets it. The distance limit for peer-group comparison? User-defined. The observation period for behavioral trends? Adjustable.</p><p>This sounds like it would create chaos. It didn’t. It created ownership.</p><p>When a team in a hot climate sets their cooling threshold differently than a team in a cold climate, they’re encoding their domain expertise into the algorithm. They’re not fighting the AI. They’re collaborating with it. And when the system flags something, they trust it more because <em>they</em> defined what “suspicious” means.</p><figure><img alt="Configurable thresholds" src="https://cdn-images-1.medium.com/max/1024/1*VI2qeJJM9j4sdoeraXBHqw.png" /></figure><p><strong>The UX principle:</strong> Expose the algorithm’s decision boundaries as configurable parameters. The people closest to the domain should control the sensitivity, not the designers or the data scientists.</p><p>There’s a deeper insight here about power dynamics. When the AI sets the rules and the user just receives outputs, the relationship is authoritarian. The user is subordinate to the model. When the user sets the rules and the AI executes them at scale, the relationship flips. The AI becomes a powerful tool in the user’s hands, not an oracle they have to worship or ignore.</p><h3>Pattern 3: Make the AI learn from their work, invisibly</h3><p>This is the design I’m most proud of, and it’s almost invisible.</p><p>We built a feedback loop where real-world outcomes automatically recalibrate the model. Here’s how it works in practice:</p><p>The AI flags something. An investigator looks at it, does their work, and records the outcome using a simple dropdown. Essentially “confirmed” or “not confirmed.” That’s it. That’s all they do. Normal workflow. No extra steps.</p><p>But behind the scenes, every confirmed case bumps the triggering condition’s weight up by a small increment. Every false positive bumps it down. Over weeks and months, the conditions that consistently find real problems get stronger. The ones that cry wolf gradually fade.</p><p>The users are training the AI. They have no idea. And that’s the point.</p><p>If we had designed this as an explicit process (“Please rate the quality of this AI prediction on a scale of 1–5”), nobody would do it. They’re busy. They have work to get done. Asking knowledge workers to do extra work to improve an algorithm they don’t understand is a recipe for 0% participation.</p><p>Instead, we captured the signal from work they were already doing. The status update they’d record regardless became the training data. The design made the feedback loop invisible and therefore inevitable.</p><p><strong>The UX principle:</strong> The best human-in-the-loop system is one where the human doesn’t know they’re in the loop. Design for signal capture through existing workflows, not additional tasks.</p><h3>Pattern 4: Show different depths to different people</h3><p>One interface. Three fundamentally different users. This was the structural UX challenge that took the longest to solve.</p><p>The first user is an executive. They need three numbers: how many items were flagged, how many were investigated, what’s the recovery rate. They look at KPI tiles and move on. If the interface forces them through a map, a chart, and a data table to find those three numbers, they’ll stop logging in.</p><p>The second user is a field operations lead. They need geographic context (where are the problems clustered?) and a prioritized list they can hand to their crew. They live in the map layer and the drill-down table.</p><p>The third user is an analyst who configures the detection rules and reviews performance over time. They need condition-by-condition breakdowns, parameter tuning screens, and historical trend data.</p><p>Same platform. Same data. Three different depths of engagement.</p><p>The solution was progressive disclosure across four visual layers:</p><p><strong>Layer 1: Geography.</strong> A map with color-coded clusters. This answers “where?” in under two seconds. The executive scans it, the field lead studies it, the analyst uses it as an entry point.</p><p><strong>Layer 2: Scale.</strong> Large-format KPI tiles showing total counts and aggregate scores. This answers “how big?” The executive gets their three numbers here.</p><p><strong>Layer 3: Composition.</strong> A bar chart showing which anomaly categories dominate the portfolio. This answers “what kind?” The analyst reads this to understand the detection landscape.</p><p><strong>Layer 4: Specifics.</strong> Hierarchical tables that drill from territory to zone to segment to individual asset. This answers “which ones exactly?” The field lead uses this to build their dispatch list.</p><p>Each layer is a complete answer for someone. Nobody is forced through layers they don’t need. And the information architecture mirrors how the organization actually thinks about its operations: top-down from territory to individual asset.</p><p><strong>The UX principle:</strong> Design AI interfaces as layered systems where each layer answers a different stakeholder’s question. Progressive disclosure isn’t about hiding complexity. It’s about sequencing it so everyone finds their answer at their depth.</p><h3>The meta-principle: Explainability is an architecture, not a feature</h3><p>If I had to distill everything I learned into one sentence, it would be this:</p><blockquote><em>Explainable AI is not a tooltip you add to a confidence score. It’s the structural architecture of how the entire product communicates its reasoning.</em></blockquote><p>The four patterns I’ve described aren’t independent features. They’re interlocking:</p><ul><li>Additive scoring creates the raw material for explanation</li><li>Configurable thresholds give users authorship over the logic</li><li>The feedback loop makes the system responsive to reality</li><li>Progressive disclosure delivers all of this at the right depth for the right person</li></ul><figure><img alt="The Trust Architecture" src="https://cdn-images-1.medium.com/max/1024/1*t1F4dsxmuq4IHdbG5PVFTQ.png" /></figure><p>Together, they form what I call a trust architecture. A designed system that earns user confidence not through authority (“the AI is 87% sure”) but through transparency (“here are three reasons, you set the thresholds, and your feedback made this better than last month”).</p><h3>Why this matters right now</h3><p>The explainable AI market is projected to reach $33 billion by 2032. Every major industry (healthcare, finance, energy, logistics, legal) is deploying AI systems where the end users are domain experts, not technicians.</p><p>And in almost every case, the bottleneck isn’t the model. It’s the interface.</p><p>NNGroup’s 2026 State of UX report identifies AI trust as a defining design challenge for this era. In UX Collective, Arin Bhowmick notes that the difference between AI products people adopt and those they abandon often comes down to one question: does the user understand what the system just did?</p><p>We’re at a turning point. The designers who can build the trust layer between algorithmic intelligence and human decision-making will be the most valuable people in any AI product team.</p><p>Not because they understand the models. Because they understand the people.</p><h3>Three things you can do Monday morning</h3><p>If you’re a designer working on any AI-powered product, here’s where to start:</p><p><strong>Audit your AI outputs.</strong> For every score, flag, recommendation, or prediction your product shows, ask: can the user trace this back to its inputs? If the answer is no, that’s your first design project.</p><p><strong>Find the hidden feedback loop.</strong> Your users are already recording outcomes somewhere. Closing tickets, marking cases, updating statuses. Can that existing workflow feed signal back into the model? Design for invisible training.</p><p><strong>Map your stakeholders by depth.</strong> Who needs the three-number summary? Who needs the drill-down table? Who needs the configuration screen? If they’re all seeing the same flat interface, progressive disclosure will be your biggest impact.</p><p>The AI is only as good as the trust it earns. And trust is designed, not computed.</p><p><em>I’m a Lead UI/UX Designer working on AI-powered enterprise products. Every day I’m learning something new about how people interact with algorithms, and I try to turn those lessons into interfaces that feel trustworthy and human.</em></p><p><em>If you’re figuring out AI and UX too, I’d love to hear what’s working for you. Connect with me or drop a comment.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94adf85f5f6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-ai-says-so-is-not-a-ux-strategy-94adf85f5f6c">“The AI Says So” Is Not a UX Strategy</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[Things I learned working in the EV domain]]></title>
            <link>https://medium.com/design-bootcamp/things-i-learned-working-in-the-ev-domain-dc17305700cd?source=rss-676df6dbf3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc17305700cd</guid>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[electric-vehicles]]></category>
            <category><![CDATA[electric-car]]></category>
            <category><![CDATA[electric-vehicle-industry]]></category>
            <category><![CDATA[ev-charging]]></category>
            <dc:creator><![CDATA[Prakriti Verma]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 13:42:02 GMT</pubDate>
            <atom:updated>2025-03-20T22:01:58.335Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Image showing EV charging at home, public charging stations, and charging details on the mobile app." src="https://cdn-images-1.medium.com/max/1024/1*em6PwkIwfoMVVefMKOE7sg.png" /><figcaption>Home and public charging</figcaption></figure><p>The electric vehicle (EV) industry is growing at an unprecedented pace, revolutionizing the way we think about mobility, sustainability, and user experience. Working in this domain has provided me with invaluable insights into user behavior, technology, and the challenges that come with designing for an evolving ecosystem.</p><p>Here are my <strong>key takeaways</strong> from working in the EV space:</p><h3><strong>1. User experience is everything</strong></h3><p>EV users have a fundamentally different mindset compared to traditional vehicle owners. Their expectations are shaped by technology, sustainability concerns, and cost optimization.</p><p>The UX challenges in EV applications often revolve around:<br><strong>a) Range anxiety:</strong> Users need real-time, accurate data on charging stations, battery consumption, and estimated travel distance.</p><p><strong>b) Seamless charging experience:</strong> Finding an available and working charging station is a major pain point. Transparency in station availability and pricing significantly improves user confidence.</p><p><strong>c) Home charging optimization:</strong> Many EV users charge at home and seek features that optimize energy consumption and costs based on peak hours and renewable energy availability. Most of Europe follows dynamic pricing, which makes energy and cost optimization possible.</p><h3>2. Data accuracy and real-time updates matter</h3><p>One of the biggest challenges in the EV domain is data reliability. Users expect real-time information about charging stations, traffic conditions, and energy pricing. <strong>Delayed </strong>or <strong>incorrect data </strong>can lead to frustrating experiences, such as reaching a charging station only to find it occupied or out of order. Users often end up searching for the latest information about public charging stations on multiple apps and websites.</p><h3>3. Transparency to charging details</h3><p>EV users make decisions based on trust. This could be trust in the availability of charging infrastructure, trust in pricing models, and trust in the sustainability impact of their choices. <br>Apps and platforms need to be transparent about: <br><strong>a) Charging costs: </strong>Clear, upfront pricing without hidden fees.</p><p><strong>b) Energy sources:</strong> Showing whether the charging station is powered by renewable energy or fossil fuels. In the current environmental situation, this is a crucial component.</p><p><strong>c) User reviews &amp; ratings: </strong>Validated feedback from other users to ensure reliability. Consumers continue to read reviews on websites and applications to learn about other people’s experiences.</p><h3>4. Gamification and engagement features enhance retention</h3><p>EV apps that incorporate gamification elements tend to have higher engagement rates. <br>Features like:<br><strong>a) Eco-impact tracking:</strong> Showing users their CO2 savings compared to gasoline vehicles. <br><strong>b) Rewards for sustainable charging:</strong> Offering incentives for using green energy-powered chargers. <br><strong>c) Community engagement:</strong> Enabling users to share tips, reviews, and charging station feedback fosters a sense of belonging.</p><p>Example:<br><a href="https://www.plugshare.com/"><strong>PlugShare</strong></a><strong> </strong>incorporates a point-based reward system where users earn credits for sharing charger availability, submitting reviews, and participating in community discussions.</p><p><a href="https://www.chargepoint.com/"><strong>ChargePoint</strong></a><strong> </strong>leverages a tiered membership program that rewards users with badges and perks for using chargers strategically and participating in sustainability initiatives.</p><h3>5. Interoperability and standardization are key challenges</h3><p><strong>a)</strong> Unlike traditional fueling stations, EV charging networks are fragmented. Different providers have their own stations, apps, and payment methods, creating a confusing experience for users.</p><p><strong>b)</strong> One major challenge lies in communication protocols. Different charging networks and EVs use varying communication protocols to initiate and manage charging sessions. Establishing a universal standard for these protocols is essential for seamless communication between vehicles and charging stations.</p><p><strong>c)</strong> Another challenge is payment systems. Currently, drivers often need multiple accounts with different charging network operators, leading to a fragmented and confusing user experience. Developing a unified payment system that works across all networks would significantly enhance user convenience.</p><h3>6. Personalization increases usability</h3><p>Not all EV users have the same needs. Personalization enhances the user experience by: <br><strong>a) Smart route planning:</strong> Suggesting routes based on driving behavior, battery status, and preferred charging networks.</p><p><strong>b) Customized notifications: </strong>Allowing users to choose alerts for charger availability, price drops, or charging completion.</p><p><strong>c) Adaptive UI for different user segments:</strong> New EV owners may need more educational content, while experienced users prefer quick access to advanced features.</p><p>The key lessons I’ve learned revolve around solving real user pain points, ensuring data accuracy, building trust, and making the experience seamless and engaging.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc17305700cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/things-i-learned-working-in-the-ev-domain-dc17305700cd">Things I learned working in the EV domain</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[Influence of culture on design]]></title>
            <link>https://medium.com/@Prakriti-UIUXDesigner/influence-of-culture-on-design-c304fbff9dcf?source=rss-676df6dbf3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c304fbff9dcf</guid>
            <category><![CDATA[hofstede]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[cultural-differences]]></category>
            <dc:creator><![CDATA[Prakriti Verma]]></dc:creator>
            <pubDate>Fri, 26 Jan 2024 15:00:05 GMT</pubDate>
            <atom:updated>2024-01-26T15:01:55.996Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2fEKDuqUlrEt7RbYt5rVWw.png" /></figure><p>A few days ago, I was having chat with my colleague from U.S team. The conversation was all about our choices of coffee, the taste we prefer during which I playfully opened the website of Starbucks for both India and USA. That’s when my attention shifted from the talk of coffee to the website design of these two countries.</p><p>My curiosity took me to the websites of some of the known brands for different countries.</p><p>I noticed how every company presents itself differently on their websites in the respective countries. Not just in terms of text and translation, but from the kind of visual content used, typography selected, color palettes designed, and layouts chosen.</p><figure><img alt="Starbucks India, Starbucks Japan, Starbucks US, Starbucks Denmark (L-R)" src="https://cdn-images-1.medium.com/max/1024/1*Ek-7s7pSH2Pnl3RZl3K2zg.png" /><figcaption>Starbucks India, Starbucks Japan, Starbucks US, Starbucks Denmark (L-R)</figcaption></figure><p>Cultural differences influence design characteristics in various ways, shaping user preferences, expectations, and responses to digital products and interfaces. Understanding these cultural nuances is essential for creating designs that resonate with diverse audiences.</p><p>Here are some design characteristics that can vary based on cultural differences:</p><ul><li><strong>Color Preferences: <br></strong>Colors and symbols have different meanings in various cultures. For example Western culture often associate red with passion or danger, green with nature or envy, and blue with calm or trust whereas in asian cultures red can signify luck or prosperity, and white is associated with mourning.</li><li><strong>Symbols and icons:<br></strong>Meanings may vary across cultures. For example, the thumbs-up gesture is positive in Western cultures but can be offensive in some Asian countries.</li><li><strong>Navigation and Layout:</strong> <br>Cultural differences can influence how users navigate and process information. Consider variations in reading direction, page layout, and content organization. Some cultures prefer more hierarchical structures, while others may prefer a more egalitarian approach.</li><li><strong>User Behavior and Interaction Patterns:<br></strong>Understand cultural differences in user behavior and interaction patterns. For instance, some cultures may be more reserved or prefer indirect communication, while others may be more expressive. Adapt your design to accommodate these variations in user behavior.</li><li><strong>Language and Communication:<br></strong>Be mindful of cultural nuances in communication, as certain symbols, gestures, or phrases may have different meanings in various cultures.</li></ul><p>Apart from the above characteristics, we can also use the analysis approach based on Hofstede’s cultural-dimensions theory.</p><h3><strong>Hofstede’s 6-dimensions theory :</strong></h3><ul><li><strong>Power distance</strong>: The extent to which the less powerful members of institutions and organizations within a country expect and accept that power is distributed unequally.</li><li><strong>Individualism vs. collectivism</strong>: Whether people put more weight on the interests of the individual (individualists) or on the the interests of the group (collectivists).</li><li><strong>Masculinity vs. femininity</strong>: Whether strong, very different emotion stereotypes are associated with traditional genders (masculine societies) or emotions are allowed to overlap across genders (feminine societies).</li><li><strong>Uncertainty avoidance</strong>: The extent to which the members of a culture feel threatened by ambiguous or unknown situations.</li><li><strong>Long-term vs. short-term orientation:</strong> Whether the society fosters virtues such as perseverance or thrift, oriented towards future rewards (long-term orientation) or virtues related to the past and the present.</li><li><strong>Indulgence vs. restraint</strong>: Attitude towards enjoying life and having fun, ranging from free gratification of human desires (indulgence) versus adhering to strict social norms (restraint).</li></ul><p>We can use the <a href="https://www.hofstede-insights.com/product/compare-countries/">comparison tool</a> to understand how two countries differ. For example, the below shows the comparison between India, Japan and United States.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K7tRuJ6fDDFW_RFVgxf8eg.png" /><figcaption>Hofstede’s 6-dimensions analysis for Japan and the United States</figcaption></figure><figure><img alt="Hofstede’s 6-dimensions analysis for Denmark and the United States" src="https://cdn-images-1.medium.com/max/1024/1*QP4baALhdpZiMqiG5tgKlA.png" /><figcaption>Hofstede’s 6-dimensions analysis for Denmark and the United States</figcaption></figure><p>For instance, we can learn that Japan and the United States are relatively similar in terms of score for <em>power distance</em> and i<em>ndividualism</em>, while the Denmark and the U.S have different scores for <em>power distance, motivation towards achievement &amp; success</em> and <em>uncertainty avoidance.</em></p><h3>Conclusion:</h3><p>Cultural differences significantly impact the success of digital products and services. By embracing cultural diversity in UX design, designers can create more inclusive, effective, and engaging experiences that resonate with users across the globe. Regular user research, usability testing across diverse user groups, and ongoing cultural awareness are essential practices for successful global UX design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c304fbff9dcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design System in my day-to-day work]]></title>
            <link>https://medium.com/@Prakriti-UIUXDesigner/design-system-in-my-day-to-day-work-aebcad44f072?source=rss-676df6dbf3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/aebcad44f072</guid>
            <category><![CDATA[component-libraries]]></category>
            <category><![CDATA[ui-ux-designer]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ux-life]]></category>
            <dc:creator><![CDATA[Prakriti Verma]]></dc:creator>
            <pubDate>Sun, 29 Jan 2023 15:51:51 GMT</pubDate>
            <atom:updated>2025-03-22T15:24:03.060Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5mL-mAP0vEINf7ECR_K-8A.png" /><figcaption>Design System</figcaption></figure><h3>Brief Introduction</h3><p>Being a UI/UX designer, we have a lot to do in our day-to-day work. Few of them could be figuring out the pain points of the users, understanding the problem, brainstorming ideas with team members, providing design walkthroughs to the stakeholders, and much more.</p><p>What if we could get a little help on the visual part? Help with already created UI components and patterns. Sounds good?</p><p>….</p><p>For the last 2 years, I have been working on web and mobile applications for home and pool control systems. The aim is to make the experience better for our users not only through new features but also by making the visuals more intuitive and pleasant.</p><p>This article is more about the role of a design system in my work life.</p><p>….</p><blockquote><strong>What is a Design System?</strong></blockquote><blockquote><em>By definition, A design system is a set of standards to manage design at scale by reducing redundancy while creating a shared language and visual consistency across different pages and channels.</em></blockquote><blockquote><em>There are two important parts to a design system:<br>&gt; the design</em><strong><em> repository<br></em></strong><em>&gt; the </em><strong><em>people</em></strong><em> who manage it</em></blockquote><h3>Why did we even need a design system?</h3><p>My organization contains around 8 products, including web and mobile for home and pool control systems. Some of them were designed long back and were not up to the latest trends. These products needed to have a similar design pattern as new products for visual consistency.</p><h3>Steps we followed while creating the design system</h3><p><strong>Step 1: Setting up the process</strong></p><p>Building a design system is not just about adding UI components but also setting up the guidelines and documentation and having the whole ecosystem. Before starting the work, we had a discussion with our stakeholders across all products to make sure everyone’s on the same page.</p><p>Things figured out in this step:</p><ol><li>Tools to be used in creating the design system need to be defined in the initial phase itself. We would need tools to document and to create a design library.</li><li>Documenting the requirement from each product’s stakeholders, their current challenges, and the guidelines prepared for the end-to-end process.</li><li>Naming the files and layers seems to be a small task, but it plays a vital role in keeping everything neat and clean. It also ensures consistency by every collaborator in the team.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSF6Eq-nY3DMBUQ1xtH4DA.png" /><figcaption>Tools used in the process</figcaption></figure><p><strong>Step 2: Listing the UI components</strong></p><p>Getting the requirement about what needs to be created and up to what extent has to be found out. The UI component and its elements should be flexible enough since the design system will iterate over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NSVL6r1KV8IgijKhEodioA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q0A23nPQdXCkxWSFmoS29w.png" /><figcaption>Design System</figcaption></figure><p>It is important to keep labels and names in the library that are easy to understand.</p><p><strong>Step 3. Design the components and patterns</strong></p><p>The visual system is made up of foundational elements like defined text styles for headers and content, a color palette, inputs, forms, overlays, cards, what we call <strong>components,</strong> and <strong>patterns.</strong><br>The design system should be organized properly and as per the guidelines decided between the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VOTD19FrubpNocdJCaG7w.png" /><figcaption>Image shows how design system should be organised</figcaption></figure><p><strong>Step 4. Communication with collaborators</strong></p><p>We should always communicate with cross-functional team members to see if anyone else is having the same restrictions. Learn everything about platform requirements and how a proposed pattern would work across the entire product family.</p><p>….</p><h3>How a design system helped me:</h3><ul><li>It alleviated strain on us to focus on larger, more complex problems.</li><li>Design work is now being created and replicated quickly and at scale. Just re-use the already-created component in design pages.</li><li>It created a unified language within and between cross-functional teams.</li><li>It created visual consistency across products, and other departments. Even if a new app is added to our company, that will be consistent because of the use of a design system.</li><li>It served as an educational tool and reference for junior-level designers and content contributors.</li></ul><h3>Cons I could think of while using the design system:</h3><ul><li>Using a design system limits us to having a different design solution.</li><li>It takes time to teach a new member about our design system.</li><li>Change in one single UI component leads to the need for validation from each stakeholder across products and hence takes a lot of time.</li><li>The addition of new UI components or patterns creates delay in design handoff since these could be sometimes not thought of at the time of deciding design timelines.</li></ul><p>….</p><p><strong>Conclusion</strong>: The design system surely has its pros and cons. We just need to ensure the best practices during the process of its creation. It’s important that we as designers adopt the big-picture mindset that is required for decision-making while creating a design system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aebcad44f072" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Melody mobile app — UI UX Case Study]]></title>
            <link>https://medium.com/@Prakriti-UIUXDesigner/melody-mobile-app-ui-ux-case-study-59b01b868d0c?source=rss-676df6dbf3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/59b01b868d0c</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Prakriti Verma]]></dc:creator>
            <pubDate>Fri, 29 Apr 2022 13:05:07 GMT</pubDate>
            <atom:updated>2023-07-02T15:37:26.891Z</atom:updated>
            <content:encoded><![CDATA[<h3>Melody mobile app : a UI UX case study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0QqEz5K8Q018KFGqXXVnzQ.png" /><figcaption>Melody — Musician mobile app</figcaption></figure><blockquote><strong>Brief: </strong>When talking about celebrations, the first thing that comes to our mind is Music — Music that will cheer-up all the people in the event and make it memorable.</blockquote><blockquote>Music for your event is not only used as a form of entertainment, but it also sets a scene, creates a mood or atmosphere, brings people together and encourages participation.<strong><br> <br> </strong>Arranging a musician or band for the event, be it your D-day or house party or for your loved ones, celebration can be a tiring process. The problem increases for people searching for the musicians in a city different from where they live.</blockquote><p><strong>The problem</strong>:<br>Users don’t have time to search and book musicians for their events at their preferred location.<br> <br> <strong>The goal:<br></strong>Our musician booking app will let users search and book verified musicians which will affect users who want to view different musicians or bands at their choice of location. <br> <br><strong>My role: </strong>UI UX Designer <br><strong>Tools: </strong>Figma, Miro, Zoom<br><strong>Target Audience: </strong>users from age 20–65<br><strong>Project Duration: </strong>3 weeks</p><p><strong>Key Challenges:<br>- </strong>Going through every usability test results and design iterations in such small time was a major challenge.<br>- Finding relevant participants online for usability testing in covid situation was challenging.</p><h3><strong>The Design Process</strong></h3><p><strong>User Interview:<br></strong>Participants included independent people who were about to get married, young students looking for musician for their college fest, older people who usually handles wedding arrangements for their children.<strong><br> <br></strong>Key quotes from the target audience:</p><p>“I don’t the time to travel my hometown to arrange a music band for the event.”<br>“I don’t know any musician or music group who performs in my city. It’s important for me to book a verified performer whom I can trust for the D-day.”<br>“My life will become easier if I could select few musicians and compare them according to my requirement.”</p><p><strong>Persona:<br></strong>After interviewing users, I created two personas for my design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6Xs-0SL9UGDpKK5TtXZxg.png" /><figcaption>Persona 1</figcaption></figure><p><strong>User journey map: </strong>I created user journey map to uncover the frustration and delight that user goes through.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*b9KTmKuTN2lua62LPI363w.gif" /><figcaption>User Journey Map</figcaption></figure><p><strong>DEFINE</strong></p><p><strong>Problem statement:<br></strong>Vandana Singh is a busy working adult who needs an easy way to book musician of her choice from her current city because she have so many other arrangements to do and doesn’t have time to visit her hometown for this.</p><p><strong>IDEATION</strong></p><p><strong>Competitive audits: <br></strong>I examined my competitors’ features, pricing, differentiators, strengths, weakness and competitive reviews, etc. This helped in understanding what is already there and what needs to be added to solve the problem user is facing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4Em9GD_CIrT9_FpwfAu_3Q.gif" /><figcaption>Competitive audit</figcaption></figure><p><strong>Storyboard:<br></strong>With all the insights from research in previous phases, I created storyboard to illustrate user experience in their context to get a better understanding of what can be improved and how I can make user’s life better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJFlP9dsQlLatEGVooOEsg.png" /><figcaption>Storyboard for Persona 1</figcaption></figure><p><strong>Wireframes: </strong>With all the information gathered, I started sketching wireframes on paper. Once I felt good enough, I created digital wireframes on figma. This gave me a rough idea of how my design would look like and what more can be improved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*an75KzzrZ-o8So2VZOHZqQ.png" /><figcaption>Wireframes</figcaption></figure><p>To make sure that the I was going on the right track, I went for an <strong>unmoderated usability testing </strong>with the participants selected earlier. This resulted in iterations in my design screens since there were many gaps in the flow that didn&#39;t came to my mind until then.</p><p>I created a cheat sheet for my prototypes which made my design work faster and easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T332YdQidjZu-mW_rQqiAA.png" /><figcaption>Cheat Sheet</figcaption></figure><p><strong>Prototypes:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZmJxmkOBX2Nbv-cLG-1Q1A.png" /><figcaption>Prototype</figcaption></figure><p><strong>Conclusion: </strong>This project once again made me realise the importance of design process to find out the problem and solution for users. I am thankful to all participants without whom this would not have been the same and my developer friends who helped me with the technical feasibility.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59b01b868d0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Protextt Mobile App: a UI UX Case Study]]></title>
            <link>https://medium.com/@Prakriti-UIUXDesigner/protextt-mobile-app-a-ui-ux-case-study-3aa30d0948a3?source=rss-676df6dbf3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3aa30d0948a3</guid>
            <category><![CDATA[ui-ux-case-study]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[parental-control-app]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[product-design-process]]></category>
            <dc:creator><![CDATA[Prakriti Verma]]></dc:creator>
            <pubDate>Fri, 29 Apr 2022 07:50:43 GMT</pubDate>
            <atom:updated>2023-07-03T06:36:24.013Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qf3TYBceOzSlfarWzF9XhA.png" /><figcaption>Protextt: Parental Control App</figcaption></figure><blockquote><strong><em>Brief</em></strong><em>: Cyberbullying on social networking sites (SNS bullying) is an emerging societal challenge related to the deviant use of technologies.</em></blockquote><blockquote><em>One-quarter of teens say they have been sent explicit images they didn’t ask for, while 7% say someone has shared explicit images of them without their consent. These experiences are particularly concerning to parents.</em></blockquote><blockquote><em>Kids that are bullied are likely to experience anxiety, depression, loneliness, unhappiness, and poor sleep. The risk of suicide increases by 35% to 45% when victims do not have any support from anyone in their life, and cyberbullying amplifies the situation.</em></blockquote><h3>Problem Statement:</h3><p>Parents worry about their teens getting bullied online and need to know if that ever happens so that they can teach their teens about acceptable online behavior and support them to avoid any consequences.</p><p>This problem is particularly challenging since children can take it as an invasion of their privacy.</p><h3>Solution:</h3><p>I started with the design thinking methodologies, which include 5 stages — empathize, define, ideate, prototype, and test.</p><p>A platform on which parents can rely to get notified about any cyberbully happening to their child so that they can prepare and take any action against it.</p><h3>My Role:</h3><p>I led the project and worked on all aspects of the design system, including its visuals and UX design while my developer colleagues helped implement my designs.</p><p><strong>Alternate Apps in the market and their shortcomings</strong></p><ol><li>Complex setup of the app in the system</li><li>The need for installing two apps in parent’s and child’s mobile</li><li>A feature like Location Detection makes over-controlling</li><li>A feature like controlling maximum time for using the device doesn’t really work when a child is using multiple devices which usually a house has.</li><li>Many of the solutions are dashboard which is not useful in every context.</li></ol><h3>User Interviews:</h3><p>I chose to interview people who are parents to teenagers.</p><p>Key quotes directly from the target audience:</p><p>“It’s really important to me if any bad thing is happening in my child’s life.”</p><p>“My girl spends around 2–3 hrs on social media and takes everything on it very seriously.”</p><p>“I trust my children but I am worried about the things that may happen to him that he won’t tell us because of embarrassment or shyness. I want to be with him in every situation to handle it better.”</p><h3>Define:</h3><p>I used How Might We (HMW) to define the problem.</p><ul><li>How Might We make a list of words that are bad to be used for a child so that we have a clear understanding of what things affect the child?</li><li>How Might We have teach children to understand what to do when they face bully?</li><li>How Might We have something that would alert the guardian of the cyberbully going on with their children?</li><li>How Might We have a conversation with other parents of your child’s classmates?</li><li>How Might We reduce child’s time on social platforms which reduces the chance of cyberbullying?</li><li>How Might We make the child tell the reason behind his angry and irritating behavior?</li><li>How Might We install a control app on a child’s phone to manage his activity and phone usage?</li></ul><h3>Ideation:</h3><p>After brainstorming, I had a few ideas which could resolve our problem. I sketched the best one.</p><h3>Challenge Assumptions:</h3><ol><li>The child will easily tell why he is feeling anxious.</li><li>Parents can install a control app on their child’s phone and believe he/she is not going to use any other device at home like an iPad, laptop, etc.</li><li>Checking and managing all child’s activity on social platforms won’t raise any question on trust issues.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WZt7f-8Su-TxlmQP05Um2A.png" /><figcaption>Pen &amp; Paper Wireframing</figcaption></figure><h3>Prototype:</h3><p>I created a storyboard to visualize the problem and solution from the user’s perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ToHT37R-XjnJv9-7Qqrxw.png" /><figcaption>Storyboard</figcaption></figure><p>After finalizing sketches, I started working on prototypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V0Y2ilYxLDmAHTzoh4c71Q.png" /><figcaption>Prototype</figcaption></figure><h3>Conclusion:</h3><p>This project received good feedback from the users. We got a promising response from our users.</p><p>This was my first project to complete the whole UI UX design single-handedly. While I was nervous initially, I learned to believe in myself. I am thankful to the developers in the team who really helped me in technical feasibility discussions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3aa30d0948a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>