<?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 Alifnoushad on Medium]]></title>
        <description><![CDATA[Stories by Alifnoushad on Medium]]></description>
        <link>https://medium.com/@alifnoushad-96?source=rss-3471c28025f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Alifnoushad on Medium</title>
            <link>https://medium.com/@alifnoushad-96?source=rss-3471c28025f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:17:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alifnoushad-96/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 Dashboards for Decisions: How to Create Clear, Useful Dashboards]]></title>
            <link>https://alifnoushad-96.medium.com/designing-dashboards-for-decisions-how-to-create-clear-useful-dashboards-8d70ca9ae291?source=rss-3471c28025f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d70ca9ae291</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Alifnoushad]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 12:16:22 GMT</pubDate>
            <atom:updated>2026-07-13T13:12:58.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*6aIIgQ2L6CYbKdS4gXKwqg.png" /></figure><p>Most dashboard projects start with a familiar request:</p><p>“Here is the data. Can you make it look nice?”</p><p>The data team has cleaned the tables. Business analysts have collected use cases. Stakeholders have shared a list of KPIs. By the time the designer enters the project, the expectation is often visual polish: choose better colors, arrange the charts, make the dashboard presentable.</p><p>That is where many dashboards start going wrong.</p><p>Not because visual design does not matter. It does.</p><p>But because a dashboard is not a poster. It is not a slide. It is not a place to show everything the organization knows.</p><p>A dashboard is a decision-making tool.</p><p>Someone opens it under pressure because they need to understand what is happening, what needs attention, and what to do next. If the design does not help them reach that point faster, the dashboard becomes another report people ignore.</p><p>I have seen this pattern often: a dashboard looks impressive in a meeting, but feels exhausting in daily use. Users scroll, search, filter, second-guess, and eventually go back to Excel or ask someone else for the answer.</p><p>The problem is rarely one bad chart.</p><p>The deeper problem is that the team designed around data availability instead of user decisions.</p><h3><strong>Start with the question, not the dataset</strong></h3><p>A common dashboard mistake is starting with:</p><p>“What data do we have?”</p><p>That question is useful, but it should not be the first one.</p><p>A better starting point is:</p><p>“What decision does this dashboard need to support?”</p><p>This changes the entire design process. Instead of trying to fit every available metric onto the screen, the team starts asking what the user is actually trying to understand.</p><p>Before opening Figma, Power BI, Tableau, or any other tool, I like to clarify a few things:</p><ul><li>Who will use this dashboard?</li><li>Where will they use it?</li><li>How often will they use it?</li><li>What are their daily tasks?</li><li>What frustrates them today?</li><li>What decision does the data support?</li><li>What does success look like?</li></ul><p>These questions sound simple, but they prevent a lot of unnecessary design work. An executive checking performance in a meeting does not need the same view as an analyst investigating a trend. A control room operator looking at real-time activity does not need the same interaction model as a manager reviewing a weekly summary.</p><p>When we skip this step, dashboards become generic.</p><p>And generic dashboards usually serve everyone slightly, but nobody well</p><h3><strong>Observe the real environment</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ly0NY92Mld7G2CuOGmX0kQ.jpeg" /></figure><p>Requirements documents rarely show the full picture.</p><p>One of the most useful methods for dashboard design is observing people in the environment where they actually work. Not just asking them what they need, but watching how they use information, what they ignore, what shortcuts they take, and what interrupts them.</p><p>In one government dashboard project, the initial requirement sounded straightforward: create a dashboard to monitor city growth and anticipate future needs.</p><p>On paper, it could have become a standard analytics interface.</p><p>But the real context changed the design direction.</p><p>The team worked in a dimly lit room surrounded by large wall displays showing real-time data throughout the day. A bright white dashboard may have looked clean in a presentation, but it would have been uncomfortable in that environment. Dark mode was not a visual preference. It was a usability requirement.</p><p>That kind of insight is difficult to find in a spreadsheet.</p><p>You discover it by watching people work.</p><p>The lighting of the room, the size of the screen, the distance from the display, the level of interruption, the urgency of the task — all of these affect dashboard design. A dashboard is not only used on a screen. It is used in a context.</p><h3><strong>Understand the data before designing the interface</strong></h3><p>Designers do not need to become data analysts.</p><p>But for dashboard design, we need to understand the data well enough to know what each metric means, how it behaves, and what decision it supports.</p><p>A useful exercise is to create a simple data inventory before designing the interface.</p><p>For each important field, capture:</p><ul><li>What does this metric tell the user?</li><li>What decision does it support?</li><li>What type of data is it: number, date, category, text, location, yes/no?</li><li>What unit or format should it use?</li><li>What is a typical value?</li><li>What counts as good, warning, or bad?</li><li>Should it trigger an alert?</li></ul><p>The most useful line in this exercise is:</p><p>“This shows ___ so the user can decide ___.”</p><p>For example: <em>“This shows daily sales so the user can decide whether to run a promotion.”</em></p><p>If you cannot complete that sentence, the metric may not belong on the first screen.</p><p>A number without a decision is often just noise.</p><p>This inventory also helps reveal relationships. Total sales may depend on orders and average order value. Delivery delay may relate to region, shipment size, or clearance time. When related fields are understood together, the design can show cause and context instead of isolated numbers.</p><p>It also helps identify caveats. Maybe returns are posted the next day. Maybe data refreshes hourly, not live. Maybe a metric is only available for certain regions.</p><p>Those details matter because trust is fragile in dashboards. If users do not understand why a number looks wrong, they may stop trusting the whole system.</p><h3><strong>Design within the tool’s reality</strong></h3><p>There is another reason dashboard designs fail: the design cannot be built as imagined.</p><p>A chart that looks beautiful in Figma may not exist in Power BI, Tableau, or Cognos. A layout may break when real data appears. A custom visual may slow down the dashboard. A color treatment may not translate well in the final tool.</p><p>This is not just a development issue. It is a design issue. Before going too far into high-fidelity design, understand the tool:</p><ul><li>What chart types are supported?</li><li>What interactions are possible?</li><li>Can users drill down, filter, hover, sort, compare, or export?</li><li>How much data can the dashboard handle before performance suffers?</li><li>How often does the data refresh?</li><li>Can the interface show a “last updated” timestamp?</li><li>Which fields are restricted by role or privacy rules?</li></ul><p>This does not reduce creativity. It makes creativity useful.</p><p>A dashboard design is successful only when it survives contact with the real data, real users, and the real platform.</p><h3><strong>Every chart should answer exactly one question</strong></h3><p>One mistake appears in almost every dashboard. Teams choose charts because they’re available. Not because they’re appropriate.</p><p>Instead, start with the question.</p><p><strong>Which category performs best? </strong><br> Bar chart</p><p><strong>How has performance changed over time? </strong><br> Line chart</p><p><strong>Is there a relationship between two variables?</strong><br> Scatter plot</p><p><strong>What’s the most important number today?</strong><br> KPI card</p><p><strong>What exact values do I need?</strong><br> Table</p><p>Notice something? The chart comes <strong>after</strong> the question. Never before.</p><h3><strong>Context turns numbers into meaning</strong></h3><p>A number alone often creates more questions than answers.</p><p>Revenue<br><strong>$2.8M</strong></p><p>Good? Bad? Average? Nobody knows.</p><p>Now imagine seeing this.</p><p>Revenue<br><strong>$2.8M<br></strong>↑ 18% vs last month | Above target by 6%</p><p>Immediately useful. The number didn’t change. The context did. Context is often more valuable than the metric itself.</p><h3>Design for the brain, not the screen</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fZ7lvrb_Ws7gqvUJ-8-P6A.jpeg" /></figure><p>Dashboards are often designed for “business users,” “executives,” or “operations teams.”</p><p>But underneath those roles, we are designing for the human brain.</p><p>The brain looks for patterns. It groups nearby things. It notices differences before details. It gets tired when too much information competes for attention.</p><p>Cognitive load is the mental effort required to make sense of what is on the screen. When a dashboard has too many charts, inconsistent colors, unnecessary labels, heavy borders, unclear hierarchy, and competing signals, it forces users to work harder than they should.</p><p>A few ways to reduce that effort:</p><ul><li>Remove anything that does not help the user decide.</li><li>Show the big picture first, then allow drill-down.</li><li>Use lighter visual treatment for secondary information.</li><li>Keep related information close together.</li><li>Use consistent colors, labels, and formatting.</li><li>Reserve strong color for what truly needs attention.</li></ul><p>This is where visual design becomes more than aesthetics.</p><p>Whitespace separates ideas. Alignment creates order. Consistency builds familiarity. Hierarchy guides attention.</p><p>Minimalism in dashboard design does not mean making everything empty or plain. It means every element has a job.</p><p>If removing something does not change the meaning, it probably does not belong.</p><h3><strong>Want to go deeper?</strong></h3><p>This article only scratches the surface.</p><p>I recently put together a free playbook called <strong>Designing Dashboards for Decisions</strong>, where I cover:</p><ul><li>Choosing the right chart for different situations</li><li>Research techniques before designing dashboards</li><li>Designing for cognitive load</li><li>Accessibility best practices</li><li>AI-enhanced dashboard patterns</li><li>A practical checklist you can use on every project</li></ul><p>You can download the complete playbook from here:</p><p>👉<strong> </strong><a href="https://alifnoushad.gumroad.com/l/yfpbc">https://alifnoushad.gumroad.com/l/yfpbc</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d70ca9ae291" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to do that one project to kick off your career as UX Designer?]]></title>
            <link>https://alifnoushad-96.medium.com/how-to-do-that-one-project-to-kick-off-your-career-as-ux-designer-992e7622b371?source=rss-3471c28025f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/992e7622b371</guid>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[ux-project]]></category>
            <dc:creator><![CDATA[Alifnoushad]]></dc:creator>
            <pubDate>Wed, 10 Mar 2021 10:54:20 GMT</pubDate>
            <atom:updated>2021-03-10T10:54:20.013Z</atom:updated>
            <content:encoded><![CDATA[<h4>If you have zero experience as a designer and have worked on zero projects and you are wondering how to create a design project for your portfolio, then read on.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m82z88qUTIP-YuZRe-VHcw.jpeg" /><figcaption>Photo bykelly-lacy from <a href="https://www.pexels.com/photo/person-writing-on-white-paper-3471423/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><h3><strong>First, Gather Ideas</strong></h3><p>Create an idea board where you have the freedom to flex your brain, categorize your ideas, spread your wings!</p><p><a href="https://www.mural.co/"><strong>Mural</strong></a> is a free tool which is the best place for your ideas to gather. Play around with mural and you will find it the most flexible way to put an idea together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bVO1Ddi7C-DUHUxoUftNYQ.png" /></figure><p>There are several places you can get inspiration. Some of them are listed below.</p><ol><li><a href="https://www.behance.net/"><strong>Behance</strong></a> — Explore the variety of UX UI projects. You like the idea? put a screenshot to mural. You like the way it is presented? Do the same!</li><li><a href="http://www.dribbble.com/"><strong>Dribbble</strong></a> — Join the community and you will find perfectionists and clean, amazing UI Designs.</li><li><a href="http://pinterest.com/"><strong>Pinterest</strong></a> — go wild exploring.</li><li><strong>Medium — </strong>You know the place!</li></ol><p>Collect screenshots and links of ideas you got inspired. I hope by now you have a mural with a tones of inspirations. Now go through them and <strong>find a problem that needs a solution.</strong></p><p>For example,<strong><em> you found designs of app selling food. People are lazy to cook these days. Cooking is hard. Why not make it simpler?Or you found designs of pickup and drop apps like Uber. Is there a better and cheeper way to commute? Why not create a booking app for public transports?</em></strong></p><h3><strong>Research</strong></h3><p>Now you have the problem. Let’s find solutions.</p><p>Search for already existing solutions for your idea. Find multiple apps and documents that you think will help you develop your idea. By the end of this research you will have a clear idea what to create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NdxIFtI2AeW3WkTaFePRjA.jpeg" /></figure><ol><li>Create a <strong>competitive analysis.</strong> In simpler words, compare with different solutions you found. The different features and add-ons you found in each project.( Checkout this post for more information : <a href="https://xd.adobe.com/ideas/process/user-research/guide-to-competitive-analysis-ux-design/">guide-to-competitive-analysis-ux-design</a>)</li><li>Now <strong>talk with your friends, family and anyone around about your idea</strong>. Intake whatever valuable points they have. A different persons perspective will always help you.</li><li>If you have doubts about your idea, create the list of questions you have and spread it across globe via social media in <a href="https://www.google.com/forms/about/">google forms</a>. The questions should be very specific. Like</li></ol><ul><li>how often do you take cab?</li><li>How much do you pay for it?</li><li>Do you use any apps to book your trip? Which and why? Why not?</li></ul><p>Once you get answers, <strong>curate your</strong> <strong>solutions</strong>. I said it plural. Don’t stick up with the first obvious solution. Bring in multiple solutions. Choose the one you believe best.</p><h3><strong>Take a pencil and start drawing</strong></h3><p>Create a wireframe for the idea you have. If you think you need the laptop that’s fine too. open your preferred design tool and draw the basic wireframe and screens you want to create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ohGl6dEfPePDpa6BwbTGg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@fabianwiktor?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Fabian Wiktor</a> from <a href="https://www.pexels.com/photo/person-writing-on-white-paper-3471423/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><h3><strong>Moodboard</strong></h3><p>By now you might have a comfortable place to gather your ideas. Go back to design communities and find a design pattern you want to follow for your app. Find more similar designs styles and by the end you should have decided the following:</p><ol><li><strong>Color palette : </strong>with a Primary color. Choose your primary color wisely considering UX principles. Checkout <a href="https://color.adobe.com/explore">Adobe color</a> to explore more color palettes for your design.</li><li><strong>Design style : </strong>Choose a style staying closely with your idea</li><li><strong>Font :</strong> Choose a standard font. Readable. don’t go crazy.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwBWM9x2308Y-7MYeUCkyA.png" /></figure><h3><strong>Start Designing!</strong></h3><p>Keep your reference design close to your app screen layouts and start designing the wireframe you have ready. Tweak until you feel finished and polished.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NTe5yRn5E1VEUCa5rXnBBw.png" /></figure><p>Put the basic page connects and animations. Go wild. This way you will learn your design tool even more deeper. Work on it until you are satisfied.</p><h3><strong>Test with your friends</strong></h3><p>Share your design with your friends online. Ask them to use the prototype and give feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OvY0iXNFC02CmwjFEOx5gQ.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@plann-2999237?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Plann</a> from <a href="https://www.pexels.com/photo/person-using-smartphone-application-4549408/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>Give them tasks to complete and see if your design is taking your user where they need to go. Take the feedback constructively and make changes if you feel needs improvement.</p><p>Continue this process until you are confident with your design. If you fail in your first test , don’t worry that happens all the time. See what went wrong and find a solution for that design problem you faced. These points will help you positively in your interview.</p><h3><strong>Publish your project.</strong></h3><p>Use one of the design communities to publish your project like Behance or medium. Explain each step you went through while deriving the final solution. Point out the problem and the solution you adopted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QVVlnQbuFbcAd3JDJ3e7Ww.jpeg" /></figure><p>If you want guidance on how to publish your project, go back to the same platforms and search for ideas. Choose a design that is apt for your idea. Some example will be</p><p><a href="https://www.behance.net/gallery/86231111/Online-Banking-Dashboard">https://www.behance.net/gallery/86231111/Online-Banking-Dashboard</a></p><p><a href="https://www.behance.net/gallery/101891889/Eatin-Recipe-app-UX-Case-Study-and-Design">https://www.behance.net/gallery/101891889/Eatin-Recipe-app-UX-Case-Study-and-Design</a></p><p><a href="https://www.behance.net/gallery/66823539/UIUX-for-Web-and-Mobile-Health-analytics-apps">https://www.behance.net/gallery/66823539/UIUX-for-Web-and-Mobile-Health-analytics-apps</a></p><p>And ta da… you are done with your first proud project for your portfolio. Now go crazy and share your portfolio to your dream companies. And congrats on your first design project!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=992e7622b371" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>