<?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 Lokesh merala on Medium]]></title>
        <description><![CDATA[Stories by Lokesh merala on Medium]]></description>
        <link>https://medium.com/@lokeshbunnyluke?source=rss-1954a0339945------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*x3uQVAbmTZGbwtmoFmNQQQ.png</url>
            <title>Stories by Lokesh merala on Medium</title>
            <link>https://medium.com/@lokeshbunnyluke?source=rss-1954a0339945------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:29:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lokeshbunnyluke/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[Introduction to Design Psychology]]></title>
            <link>https://medium.com/@lokeshbunnyluke/introduction-to-design-psychology-14e10615216a?source=rss-1954a0339945------2</link>
            <guid isPermaLink="false">https://medium.com/p/14e10615216a</guid>
            <dc:creator><![CDATA[Lokesh merala]]></dc:creator>
            <pubDate>Sat, 26 Oct 2024 15:08:45 GMT</pubDate>
            <atom:updated>2024-10-26T17:02:17.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D9bvCca9X4Y2JstFUUPTIg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yISRN7ahE_YvWGTxlVn84w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CnKvkJCY-CFIIXeB4gJecA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14e10615216a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Thinking]]></title>
            <link>https://medium.com/@lokeshbunnyluke/design-thinking-8e660478155b?source=rss-1954a0339945------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e660478155b</guid>
            <dc:creator><![CDATA[Lokesh merala]]></dc:creator>
            <pubDate>Sun, 15 Nov 2020 05:04:55 GMT</pubDate>
            <atom:updated>2020-11-15T05:04:55.286Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rKG0lKTZBdXajO7SFq8uwQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ey4_pogwjenCsxJSxOyHfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gySPRCKK2GSCAungOrsf3g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*79-iZ1P0tbydkSLQ409R_w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oq2xKbYE9KgaIGVb8APTUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VLu-9hib-oDaC8fLY1ZoqQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xU8mWH2i_M8-Mac1tb8EAg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OBs4HGOzsiuYL2LroCxpVg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R0yFzoQoWcfmV3VJu6I3Ow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPdAdzV2gfynR6medLW8SA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xgEhsw5ltK5xxTUmDikxyw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e660478155b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Information Architecture- Part 1]]></title>
            <link>https://medium.com/@lokeshbunnyluke/information-architecture-part-1-c28ba6209abd?source=rss-1954a0339945------2</link>
            <guid isPermaLink="false">https://medium.com/p/c28ba6209abd</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[information-architecture]]></category>
            <dc:creator><![CDATA[Lokesh merala]]></dc:creator>
            <pubDate>Fri, 08 Feb 2019 04:34:21 GMT</pubDate>
            <atom:updated>2019-02-08T04:34:21.773Z</atom:updated>
            <content:encoded><![CDATA[<p>Information Architecture means consciously organising the content and flow of a website, app or system. That organisation should be meaningful, which means it’s based on what you know about the people using the site. In particular, what their perceptions and expectations are.</p><blockquote>IA must be user centered. Its purpose, strategy, form &amp; function should all revolve around user expectation.</blockquote><p>IA then is based on</p><p>1. Organisation schemes and structures: How information is categorised and structured</p><p>2. Labelling systems: How information is represented</p><p>3. Navigation systems: How users browse or move through the information</p><p>4. Search systems: How users look for information</p><p>IA is just not only related to websites and apps only. Super market, you might look for signage or labelling. If you don’t know where the product are. You are looking for the department or category, your item might be in, That’s IA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*zpZelQaHToImpzQ3zA9cVQ.jpeg" /></figure><p>And how easily the IA helps you find what you seek is a measure of how well it works.</p><p>The difference b/w IA and Sitemap:</p><p>The IA is a strategy of categorising, organising, prioritising &amp; linking content, based on user’s expectation/needs &amp; business goals.</p><p>The site map is a visual representation that illustrates this strategy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28ba6209abd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A website/ Application features set is determined by requirements.]]></title>
            <link>https://medium.com/@lokeshbunnyluke/a-website-application-features-set-is-determined-by-requirements-c7a44d59653e?source=rss-1954a0339945------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7a44d59653e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[client-interaction]]></category>
            <category><![CDATA[requirements-generating]]></category>
            <dc:creator><![CDATA[Lokesh merala]]></dc:creator>
            <pubDate>Wed, 06 Feb 2019 08:51:40 GMT</pubDate>
            <atom:updated>2019-02-06T08:54:19.586Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*YkHqEKeW2mO2slQync6sdw.png" /></figure><blockquote>Generating Requirements</blockquote><blockquote><em>“Requirements cannot be gathered it can only be generated. Asking proper questions generates proper requirements.”</em></blockquote><p>A website/ Application features set is determined by requirements. Asking the right question will only make you a better designer and will help you to have a proper business conversation. The more features we decide to implement the more detail we need for</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*GhJpBrXO-cs-sTH8NocqCQ.png" /></figure><p>· What those features are?</p><p>· How they should be designed?</p><p>· What level of coding, scripting, plugin or CMS platform is necessary to implement them.</p><h4>Generating requirements is a balance act. Generally, Requirements come from users and stakeholders.</h4><p><strong>1.</strong> <strong>Users requirements:</strong></p><p>For existing sites, current users.</p><p>For a new site, a specific target audience who may use it.</p><p><strong>2.</strong> <strong>Business requirements:</strong></p><p>What they believe will satisfy customers.</p><p>What they believe will deliver ROI back to the organisation.</p><p>There are three kinds of requirements, they are:</p><p>A. People say they need.</p><p>B. People actually need</p><p>C. People don’t know they need.</p><p><strong>A.</strong> <strong>Things people say they need</strong></p><p>We make very confident- but equally false predictions about future behaviour.<br> there is a huge difference b/w imagining how you’d use something &amp; actually using it.<br> Our preference at any given time are influence by our emotions, our health and our environment.</p><p><strong>B.</strong> <strong>Things people actually need</strong></p><p>When we have problem, it can be effortless to imagine a solution that will solve. However, that solution will often address a symptom instead of the underlying problem. The symptom is a right place to start but it needs to be qualified and validated. Play it forward to uncover the other actions, problems and motivations attached to the problem.</p><p>· Do we fully understand every step in every task flow, from the stand point of both the user &amp; every other user role?</p><p>· Do we have any evidence that tell us this feature or function would solve a frequent or recurring problem?</p><p>· Are there any specific scenarios or tasks where user observation would help to fill in the blanks?</p><p><strong>C.</strong> <strong>Things people don’t know they need</strong></p><blockquote><em>“People don’t want quarter inch drills they want quarter inch holes”</em></blockquote><p>i.e. The desired output is more important than the chosen tool.</p><p>Conversations about expected outcomes instead of features functions and content produce more relevant requirements for features functions and content.</p><p>When problem arise, we look for convenience first, which will almost always trump best practice.</p><p>So instead of talking about the website or its features or functions, focus on the problem people are facing</p><p>What desired outcome is required.</p><p>What they are most likely to do to solve it- with or without website.</p><p><strong>Documenting requirements</strong></p><p>· Whatever requirements you have created document them. Documentation promotes understanding.</p><p>· Documentation reference gives the entire team yours &amp; clients two things A sense of scope of what you are building. A reference point for progress during the website project lifecycle.</p><p>· Shared documentation also gives you a common way to label and describe things in a manner ever body understands.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7a44d59653e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How average users really use the web]]></title>
            <link>https://medium.com/@lokeshbunnyluke/how-average-users-really-use-the-web-80b9df80753f?source=rss-1954a0339945------2</link>
            <guid isPermaLink="false">https://medium.com/p/80b9df80753f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Lokesh merala]]></dc:creator>
            <pubDate>Tue, 14 Aug 2018 14:02:50 GMT</pubDate>
            <atom:updated>2018-08-14T14:02:50.855Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Steve Krug</em></p><p>Scanning, Satisfying, and muddling through this is how average users use the web.</p><p><strong>Scanning:</strong> One of the fact about web use is that people tend to spend very little time reading most web pages. Instead, we scan (or skim) them, looking for the words or phrases that catch our eyes.</p><p><strong>Why do people scan?</strong></p><ul><li>People don’t have the time to read any more than necessary. We’re usually on a mission.</li><li>On most pages, people came for only particular information. Scanning is how we find the interesting information.</li><li>People are used to scanning from scanning the information in magazines, books, and the online apps Facebook, twitter etc..</li></ul><p><strong>Satisfying: </strong>We don’t make optimal choices. We satisfice. In most of the cases, web users don’t go for the best choice we choose the first reasonable option, a strategy known as satisfying.</p><p><strong>Why don’t web users look for the best choice?</strong></p><ul><li>We’re usually in a hurry.</li><li>There’s not much penalty for guessing work, even if anything goes wrong all it causes is one or two clicks of the back button.</li><li>Weighing options may not improve our chances.</li><li>Guessing is more fun.</li></ul><p><strong>muddling through:</strong></p><p>We don’t figure out how things work. We muddle through.</p><p>People use things all the time without understanding how they work, or with completely wrong-headed ideas about how they work.</p><p>For example. generally, very less number of people tend to read the manuals before using a product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80b9df80753f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things that make users think — Steve Krug]]></title>
            <link>https://medium.com/@lokeshbunnyluke/things-that-make-users-think-steve-krug-1f3aad9a9bc5?source=rss-1954a0339945------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f3aad9a9bc5</guid>
            <category><![CDATA[design-sins]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[dont-make-me-think]]></category>
            <category><![CDATA[steve-krug]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Lokesh merala]]></dc:creator>
            <pubDate>Tue, 14 Aug 2018 10:38:09 GMT</pubDate>
            <atom:updated>2018-08-14T10:38:09.996Z</atom:updated>
            <content:encoded><![CDATA[<p>The most important thing that makes design easy to use. That is “Do make me think”. This is the first law of usability. When you&#39;re creating a site or app, your job is to get rid of confusion and question marks.</p><p>All kinds of things on a web page can make us stop and think unnecessarily. Every question mark adds to our cognitive workload, distracting our attention from the task at hand. As a user, I should never have to devote a millisecond of thought unnecessarily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ax6GHozHFdi7-vHEubXvHQ.jpeg" /></figure><p><strong>Few examples:</strong></p><p>Where am I?</p><p>Where should I begin?</p><p>Where did they put __?</p><p>What are the most important things on this page?</p><p>Why did they call it that?</p><p>Is that an ad or part of the site?</p><p>Clever or cute names, marketing induced names, company-specific names, and unfamiliar technical names.</p><p>So, to avoid confusions and question marks to the average users. your goal should be for each page or screen has to be self-evident. If you can’t make something self-evident, you at least need to make it self-explanatory.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f3aad9a9bc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Progressive disclosure - maximise user experience]]></title>
            <link>https://medium.com/@lokeshbunnyluke/progressive-disclosure-c89f671e65d4?source=rss-1954a0339945------2</link>
            <guid isPermaLink="false">https://medium.com/p/c89f671e65d4</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[progressive-disclosure]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[effective-design]]></category>
            <category><![CDATA[principles]]></category>
            <dc:creator><![CDATA[Lokesh merala]]></dc:creator>
            <pubDate>Sun, 12 Aug 2018 07:22:27 GMT</pubDate>
            <atom:updated>2018-08-12T12:51:05.982Z</atom:updated>
            <content:encoded><![CDATA[<p>Everything in UI should progress naturally from simple to complex. This mimics the natural way the brain processes information, successively.</p><blockquote><strong>Definition:</strong> Progressive disclosure is a strategy for managing information complexity in which only necessary or requested information is displayed at any given time.</blockquote><p>Information presented to someone who is not interested in it or isn’t ready to process it — is noise.</p><p>Progressive disclosure creates useful, aesthetic, understandable, honest and, most importantly, focused design. It’s not new either, it’s been around for more than 30 years! Only the necessary or requested information is displayed at any given time.</p><p><strong>Example:</strong> Progressive disclosure is the simple yet powerful principle that is used in everything from web pages &amp; installation wizards to amusement ride lines.</p><p>In amusement parks, it all starts from lines and then get inside and hopefully the line bit complex. overwhelmed with the line for the ride the staff is hiding just how long the line is using progressive disclosure.</p><p>They only reveal a section of the line to you at one time. Using those partitions block other patrons and the ride itself from your view as you get closer and closer to the line they reveal more to you so you can see you&#39;re getting close.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*LW1rF7nXgAXTpbDPxvxL6A.gif" /><figcaption>progressive disclosure in the amusement park.</figcaption></figure><p><strong>Conclusion:</strong> Progressive disclosure might add extra steps to your design but provides the best user experience. Use it correctly and you have a powerful technique to keeps your designs focused and honest.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c89f671e65d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>