<?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 Maddie Thirupathy on Medium]]></title>
        <description><![CDATA[Stories by Maddie Thirupathy on Medium]]></description>
        <link>https://medium.com/@maddiethirupathy?source=rss-e6af0212f011------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZULXKQaxKBTurrib.jpg</url>
            <title>Stories by Maddie Thirupathy on Medium</title>
            <link>https://medium.com/@maddiethirupathy?source=rss-e6af0212f011------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:12:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@maddiethirupathy/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 for India’s farmers with low digital literacy]]></title>
            <link>https://medium.com/@maddiethirupathy/designing-for-indias-farmers-with-low-digital-literacy-867eddb0474?source=rss-e6af0212f011------2</link>
            <guid isPermaLink="false">https://medium.com/p/867eddb0474</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[digital-literacy]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[social-design]]></category>
            <dc:creator><![CDATA[Maddie Thirupathy]]></dc:creator>
            <pubDate>Fri, 17 Apr 2020 09:32:34 GMT</pubDate>
            <atom:updated>2020-04-17T09:43:06.021Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F8QOS11J0QKLM_XGN7jB8w.jpeg" /></figure><p>I had been at <a href="https://www.rangde.org/">RangDe</a> for three months designing a Kiosk interface to enable the rural population to apply for loans, with a team of a Business Analyst and an India stack developer</p><p>The aim of the initiative ‘Swabhimaan’ was to scale up from their current loan disbursement program to a more digital, paper-less and quick process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0OmZVAyJIVzAp9-swOX5w.jpeg" /><figcaption>Left: Challenges. Right: New initiative</figcaption></figure><p>The project consisted of two components: There were to be Kiosks placed at post offices that enable <em>borrowers</em> to apply for loans and a mobile application for <em>Mitras — </em>RangDe employees who would facilitate the loan processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qGPuoU9BX9qx2z2V8bdZKQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdgMy4M5spsJwUd2IPvmIw.jpeg" /></figure><p>Initially, given that RangDe was still figuring out the business model, it was up to the few of us to draw out the User Journey and Personas to make sense of the information we had. The one thing that had us anxious was the persona of the rural users we knew very little about; we did not know their motivations or capabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SA7WaX8VqOXzHASaxOGZKQ.jpeg" /></figure><p>The User Journeys were used in a following workshop with the stakeholders to playback our understanding and to conduct a User persona exercise. The workshop had the stakeholders get talking about their users and empathise with them, as well as see their business more clearly in the form of workflows and journeys.</p><h3>Research plan</h3><p>We went on to create a research plan to understand our users, the context of loan applications, and more importantly, to find out their technological capabilities w.r.t ability to assimilate information, interacting with touchscreens and ability to recognise the patterns and cues. Also, RangDe’s borrowers are by majority, women. While we did not have a clear idea of our users’ demographics, we expected a majority of users to have low illiteracy, technologically if not educationally. It would be a challenging task to design touch screen interfaces for Users who’ve never used smart phones or any other touch devices before. The plan was to find useful resources and ideate on ways to enable interactions. We would then be prototyping these ideas to make them testable.</p><h3>Ideas for design patterns for low-tech literacy</h3><p>To start with, there are a number of resources available by institutions like MSI on designing for the digitally illiterate.</p><p>Some learnings and suggestions that came out of secondary research were the use of:</p><ul><li>Extensive use of hand-drawn, semi-abstracted cartoons with voice annotation</li><li>Aggressive mouse-over functionality,</li><li>A consistent help feature</li><li>Looping full-context video dramatizing the purpose and mechanism of the application</li><li>Virtual companion</li><li>A press-to-read mode</li><li>Familiar shapes and metaphors</li><li>Use of contextual colours</li><li>Helpful animations and transitions</li></ul><h3>Features</h3><p>The functionalities of the Kiosk App had to be kept to a minimum in order to not intimidate the users and capture only the necessary information.</p><p>The Kiosk had to perform the following functions:</p><ol><li>Authenticate a user:</li></ol><ul><li>1. Get Aadhaar number of the user</li><li>2. Get Biometric scan of fingerprint or Iris</li></ul><p>2. Capture the Loan details</p><ul><li>Loan amount required</li><li>When the loan is needed</li></ul><p>3. A financial literacy quiz with multiple-choice questions</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qXsVoOlgT6n4SqSJD9FK2A.jpeg" /></figure><h3>Prototyping as a probe to understand tech capability of users</h3><p>We generated ideas and prototyped a few interactions as well as a complete workflow to take to field research in cuddalore, a district in Tamilnadu. We translated the screens in the local language and used a combinations of visual cues, audio and interactions to help the user understand. An initial and slightly crude version of the prototype is below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUN9dmqKxEws%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUN9dmqKxEws&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUN9dmqKxEws%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7857b127dad551c62de1c9fa20504160/href">https://medium.com/media/7857b127dad551c62de1c9fa20504160/href</a></iframe><h3>Field research</h3><p>While at the village, we spoke to 20 rural loan borrowers based on the research criteria with a mix of demographics. The first half of the session consisted of finding out basic and family details, extent of usage of ATMS, bank accounts, post offices etc to help validate the assumptions the business model was based on. The second half consisted of asking the borrowers to interact with the testing device to complete the flow of applying for a loan. The testing was conducted with and without assistance and the observations and feedback was noted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EQGps6ZUk63FfciuEMZTLA.jpeg" /><figcaption>With a user to understand demographic and tech challenges</figcaption></figure><p>Both the first and second sessions surprised us when we realised how few people accessed ATMs or had interacted with touch screens of any kind. We observed that less than 4 out of the 20 got comfortable with the touch interactions while the majority struggled with basic actions. However, almost all of them were willing to learn and understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2dXQJdAM7eU4CB8sRanKYg.jpeg" /><figcaption>Quick insights from asking users about their demographic, education and tech comfort</figcaption></figure><p>We noted down the problems the users faced for each step on the flow and some of the fundamental issues were the following:</p><h3><strong>Some fundamental problems and Insights:</strong></h3><p>Among many insights, the few basic ones were:</p><p><strong>Read/write in local language</strong></p><ol><li>Reading quiz questions wrongly</li><li>Not understanding complicated words</li></ol><p><strong>Basic comfort with Post office(where the kiosk will be placed)</strong></p><p>3. Need their husband to take them there</p><p>4. Will go to the post office if accompanied by people</p><p><strong>Comfort with touch screen</strong></p><p>5. Not being able to recognise buttons</p><p>6. Not being able to press (usually dragging or pressing hard)</p><p>Based on insights, we came up with a set of guidelines that will ensure that the users do not get intimidated and get familiar with the application quickly. This required us to move away from contemporary UX thinking that focusses on delight and information, to a more empathetic approach that keeps the flow simple and easy to understand.</p><h3><strong>Guidelines</strong>:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lkGaMhMNoUnCd--xy03oeg.jpeg" /></figure><ol><li>A consistent ‘submit’ button that is recognizable, intuitive and stands out on the screen ( Borrowers generally did not recognize the elements on a screen)</li><li>Feedback on a task completed successfully ( Needs to happen slowly because the borrower is not used to fast transitions and needs more time to process every action)</li><li>Need to use symbols and colors that the borrowers associate with (‘Submit’ or ‘enter’ are vague terms for the borrower, hence the ‘tick’ symbol)</li><li>A vertical flow of tasks ( A clear direction is less confusing and borrowers tend to get confused by elements placed in different positions in different screens)</li><li>One call to action per screen, keeping options to a minimum</li><li>Information to be displayed only if it helps the user perform the task. Any other information may distract and confuse the user</li><li>Very less text to be used in order to not intimidate illiterate users</li><li>Audio and visual cues( like a ping for right and wrong) to support all the text and input fields</li></ol><h3><strong>Focussed and simplified screens based on guidelines</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*UmO_q-AFJgWpc5Mn3JunFA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*YgXG-qt7JXjAMGG9x6jTlQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*q8HE6qNC79NA9hbmQcraoQ.png" /><figcaption>Using metaphors, animations, bold styles instead of relying on text</figcaption></figure><p><strong>Final screens, after a visual designer’s input, looked like this:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nzSF31fqfEHAI0GvIU1_Mw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XPcCdyqs8wffjviCVqxD7w.jpeg" /><figcaption>On the right is a bioscope, a video device used decades ago for entertainment in villages selected as the kiosk form for familiarity</figcaption></figure><p>This was a great experience for me to be able to interact with a set of users so different from the people I design for on a daily basis. They surprised and motivated us to come up with different ideas and the project always had us on our toes. It was also a lesson in learning to work with uncertainty, ambiguity and within constraints of time and information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=867eddb0474" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doer: a productivity and discovery app]]></title>
            <link>https://medium.com/@maddiethirupathy/doer-a-productivity-and-discovery-app-a882f69d881b?source=rss-e6af0212f011------2</link>
            <guid isPermaLink="false">https://medium.com/p/a882f69d881b</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Maddie Thirupathy]]></dc:creator>
            <pubDate>Fri, 22 Jan 2016 22:06:00 GMT</pubDate>
            <atom:updated>2020-04-20T07:53:50.477Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xMyM1rIJmsPRC6iQ6-bGxg.jpeg" /></figure><h4>A case study in Mobile application UX design</h4><p>Being a regular user of Inspirational apps like Pinterest and Instagram, I collect creative projects which I mentally make a note to try out later. A lot of people who like to learn new creative skills end up looking up tutorials on video or diy sites, but its easy to lose track of them or forget to follow through on the projects.</p><p>To actively create, a person has to be constantly motivated and some appreciation always helps. Its easier to make a habit of it when the projects are organised into daily life. My proposed concept solution is a productivity app which is also a discovery and sharing platform. The following is my experience of designing the structure, features and the user experience of the mobile application.</p><h3>Naming</h3><p><strong>Doer </strong>is easily pronouncable, can quickly slip into a catch phrase, straight-forward and indicates efficiency.</p><h3>Features of the App</h3><p>The App should help users:</p><ol><li>Discover creative projects based on user’s interests</li><li>Incorporate projects into their schedule</li><li>View their weekly/monthly schedule and projects scheduled</li><li>Like projects and save them for later</li><li>Start a project with the help of instructions and videos</li><li>Upload pictures of completed projects or wip work and document</li><li>Share work on instagram</li><li>View instagram feed of fellow users</li></ol><h3>Understanding the user</h3><h4>What does the user want to achieve?</h4><blockquote>“I want to learn to paint with water colors in the next two months”</blockquote><blockquote>“I want to make Christmas ornaments by December”</blockquote><blockquote>“I want to learn different techniques in painting”</blockquote><blockquote>“I want to plan sunday family-time with fun things to do”</blockquote><h3>Commitment issues</h3><p>Mobile applications have a personality and a tone of voice. Productivity and scheduling apps run the risk of seeming like a nagging secretary. Moreover, everyone has their own preference for the level of rigidity or flexibility that works for them. Some like to plan every minute of their day whereas some cannot commit to a strict schedule. It was necessary to find the sweet spot.</p><h4><strong>Solution</strong>:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MPbzaDfZV35VIud7WAGEpg.jpeg" /><figcaption>Sketching ideas on Display of schedule</figcaption></figure><p>Providing all the necessary information while scheduling a project, like the no. of hours already scheduled into a day, other appointments from the personal calendar so that the user can make informed decisions and feel in control.</p><h3>What should the user see in the App’s home screen?</h3><blockquote>The home feed should interest the user by enabling him to browse through projects that are related to their interests, which they might add to their schedule.</blockquote><blockquote>If the user has already added a ‘water color painting’ project with a beginner-level difficulty, the feed should contain projects with similar or higher levels of difficulty to continue the learning.</blockquote><blockquote>If the user has multiple interests, the feed should contain projects from all interests</blockquote><h4><strong>Solution:</strong></h4><p>Since there are multiple interests a user follows, and each interest/topic contains multiple projects curated under it, one option could have been that the projects be displayed in random/recommended for user/most liked order.</p><p>But since the user is not only simply browsing through projects hoping to get inspired, but is doing so with more aim , categorising the projects into the topics/interests seemed more appropriate and useful for the user.</p><p>This meant exploring <strong>mixed-scrolling</strong>: to use vertical scrolling to navigate through the topics/interests and horizontal scrolling to browse through projects under a topic. Since the navigation is derived from the nature of the information categorisation, it would not astonish users and would feel intuitive . An on-boarding procedure can help ease the users in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NN6J0VjgWMPxLAwAlmFpfg.jpeg" /><figcaption>Mixed scrolling</figcaption></figure><h3>Dual-functional Home screen</h3><p>There are two events that lead a user to successfully schedule a project.</p><ol><li>Discovering a project of interest and knowing how much time it would take to complete</li><li>Assessing own schedule and deciding when time can be allocated for the project depending on his other appointments</li></ol><p>The problem was to display both(projects and schedule) at the same time to be able to plan whether to add a project to a particular day.</p><h4><strong>Solution:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FPP9HK-CA0U8W7lOz4fPZw.jpeg" /><figcaption>Explorations of home screen links and popups</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*z206-jVY3C70faqKU-otag.jpeg" /><figcaption>Exploring the My projects/My schedule Page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JT5IkKsFI97Ff3xqGwAudw.jpeg" /><figcaption>Orienting the calendar for better visibility and ease</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*fPZA1vk45m7sY4lRTDGGsw.png" /><figcaption>Home screen</figcaption></figure><p>A day-schedule that is displayed in the home screen along with the feed, which could shrink when browsing the feed.</p><p>The dates would also act as a buttons that lets users view the projects planned for that date.</p><p>The calendar or the week’s schedule will act as reminder of the upcoming projects.</p><h3>Interaction of scheduling</h3><ul><li>Scheduling a project to a day must be a deliberate and memorable experience that feels like a commitment as well as be engaging</li><li>It should be quick and easy and not require multiple clicks or page transitions, to encourage the action to be carried out more often since it is the primary aim of the application</li></ul><h4>Solution:</h4><p>While researching different interactions that would feel intuitive for categorising and organising, I discovered <strong>Drag and drop</strong> interactions as an interesting alternative for content management. Since I had my doubts on whether a dragging action would be uncomfortable for the user, further exploration on dragability was reassuring that the interaction feels quite smooth, plus it saves UI space and adds an interesting dynamic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*FyGNMQqSe4AXLfdIo3Et1w.png" /><figcaption>Scheduling by<strong> Drag &amp; drop</strong></figcaption></figure><p>The App would highlight the day schedule on pressing/dragging a Project, and the user can drop it into a day or expand the calendar to the month-view. Browsing through the expanded monthly-view can let the user schedule into the upcoming months</p><h3>Keeping track of projects and progress</h3><p>The user might start and complete his scheduled projects in different ways. The different scenarios could include</p><ul><li>Being interrupted during a project and hence planning to do it later</li><li>Planning to do it over a period of days</li><li>Might decide to start a future project, etc</li></ul><h4><strong>Solution</strong>:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*1dKnvNcUiRo2nD_I3fW-Dg.png" /><figcaption>Accessing scheduled projects</figcaption></figure><ul><li>The App would notify on the App bar when there are projects scheduled for the day</li><li>Push notifications during the start of the day to remind the user, in case the project requires materials to be purchased, etc</li><li>The application prompts the user to record starting and completing a project</li><li>An icon displayed on the project thumbnail lets the user know that the project is in progress</li></ul><h3>Documenting and sharing</h3><p>While doing a project, the user can take photos at different stages of the project and document them in the project’s page</p><p>Photos of completed or wip project can be shared on instagram and the Instagram feed of App users can be viewed in-app as well.</p><h3>Profile and settings</h3><p>The ‘liked’ projects from the feed can be accessed in the user’s profile as well as other settings like ‘Topics/Interests’ being followed</p><h3>Prototyping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HvvsuABEDvJ1QuXfAUJkSQ.jpeg" /><figcaption>Design starts with sketches and then digital prototypes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*W8HNZyOwH0bSSMes-Pyafg.gif" /><figcaption>Scheduling Interaction</figcaption></figure><p><em>Thanks for reading. Check out the App screens at </em><a href="https://www.behance.net/gallery/33163001/Doer-A-productivity-and-discovery-app"><em>Behance</em></a></p><h4><em>Check out the App screens in </em><a href="https://www.behance.net/gallery/33163001/Doer-A-productivity-and-discovery-app"><em>Behance</em></a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a882f69d881b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>