<?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 David Arjun on Medium]]></title>
        <description><![CDATA[Stories by David Arjun on Medium]]></description>
        <link>https://medium.com/@darjun90?source=rss-60ca7fd886bb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ooOb7VdoL9LckFtLB0ZM0w.jpeg</url>
            <title>Stories by David Arjun on Medium</title>
            <link>https://medium.com/@darjun90?source=rss-60ca7fd886bb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:21:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@darjun90/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[dev.to and the User Experience]]></title>
            <link>https://medium.com/davidarjunuxdi/dev-to-and-the-user-experience-f6c2c93125e7?source=rss-60ca7fd886bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6c2c93125e7</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-interface-design]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[David Arjun]]></dc:creator>
            <pubDate>Mon, 16 Oct 2017 04:05:02 GMT</pubDate>
            <atom:updated>2017-10-18T21:18:19.661Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8fAzi716hrEPupK-3D-lCQ.png" /></figure><p>Improving User Experience by Restructuring Information Hierarchy</p><p><strong><em>Overview</em></strong><em>: 21 Days, Team Project (3 Members), User Research consisting of screeners, user interviews, usability testing (3 rounds), competitive/comparative analysis, heuristic evaluations, sketching, wireframing, personas, user/task flows, user journey, rapid prototyping, high fidelity mockups and prototype utilizing Sketch and InVision.</em></p><h3><strong>Scope</strong></h3><p>dev.to is an online community where programmers learn, share<br>ideas, and find opportunities. Born out of the popular Twitter account, <a href="https://twitter.com/ThePracticalDev">ThePracticalDev</a>, dev.to strives to create an online<br>community for sharing and discovering great ideas, having<br>constructive debates and making friends. Anyone can share<br>articles, questions, discussions, etc. as long as they have the<br>rights to the words they are sharing. Our team at General Assembly was approached by The Practical Dev to redesign their site in order to improve the current onboarding and sign-up process as well as overall usability of the site while also encouraging more users to participate in the community. After thorough research and testing, we focused on improving information architecture and hierarchy to improve the overall functionality of the site and its processes while maintaining the founders’ goals of keeping the site lightweight.</p><h3><strong>Research</strong></h3><p>My team evaluated various business goals including increasing user sign up and account creation rate, increasing active user rate, improving onboarding process and overall improvement of site features and layout. Based on our assumptions in conjunction with business goals, we kicked off our research phase with an initial problem: <strong>How might we improve the current onboarding and sign up process, while encouraging users to participate in the online community of dev.to?</strong></p><p><strong>Heuristic Evaluation</strong></p><p>Using the ABBY Method, we evaluated dev.to on various factors such as findability, learnability and accessibility.</p><p><em>Goals</em>: Our goals were simple, we wanted to figure out what the overall usability of the site was like and what some user pain points could be.</p><p><em>Insights</em>: We found that the hierarchy of information on the site needed work, feature discoverability needed improvement and that the site was not as controllable as it could be.</p><p><strong>Competitive/Comparative Research</strong></p><p>With our problem statement in mind, we decided to run competitive and comparative analyses in order to see what relevant sites were doing well and how dev.to could implement said strengths. Site examples that we looked at were Stack Overflow, Reddit and LinkedIn.</p><p><em>Insights</em>: Some sites integrated simple features that were not present on dev.to. These features ranged from the way search results were organized and categorized, the variety of content that was available and the way posts were structured and separated on an interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*0AOreKb9dly-2AWZuTp_gw.png" /><figcaption>Medium Landing page with suggestions and post breaks.</figcaption></figure><p><strong>User Interviews and Initial Testing</strong></p><p>We interviewed 24 users. The group included students and professional developers and ranged from people who were not familiar with the dev.to site to senior users of the site. Our initial questions focused on background, what resource sites individuals referenced when wanting an answer to a question to what features people were looking for on a site in general (onboarding preferences, site structure, etc.). We also asked users to run through a series of tasks on the existing dev.to site and let us know what they were thinking as they were going through the functions. User feedback included responses like:</p><p>“ I want the option to be educated to during onboarding”</p><p>“ I like a clean and simple UI that is easy to navigate”</p><p>“ I want immediate content upon signing up”</p><p>“ I don’t want to be scrolling for eternity”</p><p><strong><em>Synthesis</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ta_G81qoUUT9kcmdC7IN8g.jpeg" /><figcaption>Key points from User Interview Responses</figcaption></figure><p><strong><em>Insights</em></strong>: We found that a lot of users love the community that dev.to presents, they felt welcome and genuinely happy with the content that chose to click into. While the love for what dev.to is building was clearly felt, a lot of users were frustrated with various parts of the site. An initial problem that the site had was that the majority of their user base was clicking through to a post from Twitter or a Google search and were not entering through the homepage and thus missing out seeing a lot of the features that the sight presented. When users actually looked at the homepage, they were presented with a cluttered interface that was super confusing. We found that users were unhappy with the structure of the homepage, they felt that there was too much going on with the interface, some features were hidden (thus unknown to them) and that there was no specific structure to the information that was being immediately presented or showing up as search results. Even users who have been on the site since its initial launch were unsatisfied with the look of the site and the way things were being categorized. Visuals are important, structure is important and users noted that they would use the site more if it were friendlier to their experience!</p><h3>Personas</h3><p>From our synthesis, we created 2 primary personas and mapped out an intial user journey for our first persona:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZjSU7Vd2_rR2S1pkWvIEg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Garaty80JDjTTFwjhlPxtw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dYz1mp8qDCiBJk7EFQvYHg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VVi3UDeD8y0Hl9jF0rG7-Q.png" /><figcaption>User quotes and pain points derived from interviews, testing and synthesis</figcaption></figure><p><strong>Revised Problem Statement</strong></p><p>After we synthesized all of the research we conducted, we saw some clear issues regarding the current dev.to site and revised our problem statement:</p><p><strong>How might we strengthen dev.to community participation by improving the current site’s hierarchy of information?</strong></p><h3>Translating Research into Design</h3><p>After restructuring our problem statement, we moved into the design phase. dev.to wanted to make some changes to their site while also keeping the site as lightweight as possible. Once we settled on the idea that restructuring the information architecture of the site would be beneficial to users, we focused on changes that could be implemented immediately. The changes were based on insights found through our research process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJq15mL3HLNsGfrJcowmtg.png" /><figcaption>Insights leading to design changes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6UwOB_hdON0na1Js7DnM7g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tKkghiB18fOZ-v0NYUCEtQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ph1Fuij5-EpzGjabIkm3w.jpeg" /><figcaption>Entering our design studio</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0mfHS2rHjSAGzb8iA_IleQ.jpeg" /><figcaption>Initial Screen Ideas</figcaption></figure><h3>Prototype</h3><p>We built our prototype screens using <a href="https://www.sketchapp.com/">Sketch</a> and brought the screens to life via <a href="https://www.invisionapp.com/">InVision</a>.</p><p>You can view our prototype here:</p><p><a href="https://projects.invisionapp.com/share/SCDNIL2H5#/screens/255146346_Desktop">Click here to view the project `dev.to prototype`</a></p><p><strong>Mockups and Annotations</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*Rw52vf3dxqAAxve2Z9cRUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*vxmbYLeI4QP1RSbKqcewkQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*hlltuSv37AQ6nbAR7zBx4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*4RQhFYP-6L6wboApGDHgVw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*K4iz_YcSrgwibk2pyepGow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/549/1*x5t3NhOQKX6m0YizZFTWYQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/653/1*gtTe0l27LPLgMzfxgBQo3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*Pqt_NcjMYCTiEinGWQ-5Rg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*maNCA85yecku3hQ6dk6RDA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*Pn3MeAWaRrdC018gec_ezg.png" /><figcaption>Some key screens that we built out in our prototype</figcaption></figure><h3>Testing Round 2</h3><p>We moved into phase 2 of user testing where we asked users to test our prototype. We tested 5 users with each going through 4 different scenarios ranging from going through the onboarding process to locating content that they wanted to see.</p><p>Our testing goals:</p><ul><li><strong>Users should understand what dev.to is all about upon sign up</strong></li><li><strong>Users should understand what the tags are used for</strong></li><li><strong>Users should understand how to access their profile and dashboard</strong></li><li><strong>Users should be able to filter and easily access search results</strong></li><li><strong>Users should be able to differentiate between comments and replies</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewOT2UlXnK2ufG0xfVH-Zg.jpeg" /><figcaption>A wonderful user going through our newly redesigned onboarding process</figcaption></figure><p><strong>User Testing Results</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w_9vIyZrGmwT9V5hc2YDnQ.png" /></figure><p><strong>Revised User Journey</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jANrx1jzXCP5MNttlZvTxw.jpeg" /></figure><p><strong><em>Insight</em></strong>: Dennis is much happier with the process. He is able to complete tasks as needed and had an easier time learning about the site and its functions.</p><h3><strong>Conclusion</strong></h3><p>Overall, our research provided us with several insights including the importance of hierarchy, restructuring, and presenting content.We saw that restructuring and presentation of content offered benefits that were strong enough to prevent the need to give an immediate overhaul. Users needed clearer definitions of where things were and what they did upon experiencing the interface for the first time. Cleaning up the UI and presenting a quick onboarding process were key and users were happier with the final product. Sometimes less is more and making these minor changes will make a large impact on dev.to and represent a good launch point for further iterations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YIRGQib1Kmir0F-WsXXlAg.jpeg" /><figcaption>The UX Team!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6c2c93125e7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/davidarjunuxdi/dev-to-and-the-user-experience-f6c2c93125e7">dev.to and the User Experience</a> was originally published in <a href="https://medium.com/davidarjunuxdi">davidarjundesign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[letgo — an exploration of feature integration]]></title>
            <link>https://medium.com/davidarjunuxdi/letgo-an-exploration-of-feature-integration-cfcb1dd2a65e?source=rss-60ca7fd886bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfcb1dd2a65e</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[feature-integration]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[David Arjun]]></dc:creator>
            <pubDate>Mon, 14 Aug 2017 00:59:31 GMT</pubDate>
            <atom:updated>2017-10-16T04:19:10.724Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Integrating new features for a seamless user experience</strong></p><p>Restless reinvention. This is an idea that I’ve seen reinterpreted in many ways while exploring design thinking. With this approach, your scope is constantly moving, your eyes are consistently seeking ways to tinker and make the things we use everyday better and maybe even simpler. Restless reinvention allows for continued innovation which in turn leads to untold growth potential for us and the things we interact with. Restless reinvention means that there is no such thing as a finished product, everything is a prototype just living its days in ever shifting phases and iterations. When facing the idea with this mindset, any product is a canvas, even the things that seem perfect at their intended function!</p><p>We live in a super interconnected world (we are lucky to be here!). Not only are we interconnected, but our society has found wonderful ways to integrate technology to increase the means by which we do normal things such as communicate. A great benefit of this integrated world is our ability to interact with people that we may not have ever met in our daily lives. This interaction or the hope of this interaction has lead us to find and create ways to interact that go beyond just talking. In 1995, Craigslist and eBay were founded and would go on to “modernize” and iterate upon the centuries old process of peer to peer shopping- “good ol’ buying from each other in a non-store based format”. 22 years later, both Craigslist and eBay are way further along in terms of capacity and reach but they are no longer the only players on the field. With the age of apps and the continued growth of integrated society, there are many other services that aim to continue the peer to peer selling format.</p><p>Launched in 2015, letgo is a newer peer to peer buying and selling platform that plays the same game as Craigslist but has decided to focus on the app market (one where Craigslist isn’t as strong). Another huge difference in letgo, is their choice of an integrated chat feature aimed at making communication between users as simple as possible — this is done through removing the guesswork of how users communicate outside of the app by just providing them with in app means. While this is a simple yet powerful change in the process, it doesn’t solve many of the problems that letgo faces. These problems range from physical safety (letgo has been associated with armed robberies and murders) to simple scams (one person holds up their end of the process but the other end simply falls through). A typical process follows a buyer and seller agreeing on the sale of an item posted on the service and then agreeing to meet in person for the physical exchange of goods and currencies. This is a beautiful transaction in a perfect world (the perfect world being one that we don’t quite exist in yet). Working with a team of myself and two other UX designers, we set out to approach issues that letgo was having and conceptualize new features that will offer solutions to the problems that letgo users were facing. Our team was tasked with integrating new features into letgo’s structure that would create a safe way for users to complete an ecommerce monetary transaction(from both buyer and seller perspective’s) while having letgo make some money from said transaction. How might we build a secure commerce feature that would benefit buyers, sellers, and letgo alike?</p><p>We had a lot of assumptions going in about what a user would want from a transaction such as the one letgo facilitates. These assumptions were based on the ideas of what users of peer to peer sites deem safe mixed with the ideas of users of ecommerce transactions in general (not necessarily peer to peer) mixed in with initial research into letgo competitors in general. All assumptions were rooted in hard truths — users wanted to trust their sellers or buyers, they wanted to make sure they were getting what they paid for. They want to know that they are guaranteed as a safe of a transaction as possible. With these assumptions in mind, we moved further into our research phase and created a survey that we would use to identify our target users: individuals who have been part of a certain number of peer to peer transactions (in the past year). Our survey focused on whether or not users have used peer to peer platforms and tried to extract specifics behind those who have had negative experiences using these platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*01qx1k9w9C_hvS7GP0yScA.png" /><figcaption>A pretty strong turnout from the negative experience camp.</figcaption></figure><p>After we identified users who fit into our target group from our survey screener, we set out to interview 12 individuals. The questions we asked were: When was the last time you purchased something off of a peer to peer platform?</p><blockquote><strong><em>What makes you feel safe purchasing something online?</em></strong></blockquote><blockquote><strong><em>Can you tell me about a negative experience that you had with an online purchase?</em></strong></blockquote><blockquote><strong><em>What is your preferred e-commerce payment method?</em></strong></blockquote><blockquote><strong><em>Do you feel comfortable attaching banking information to an online platform?</em></strong></blockquote><blockquote><strong><em>Have you ever done an in person pickup for anything you have purchased online? Do you have any requirements for this sort of pickup (ex: specific setting, time of day, companion)?</em></strong></blockquote><blockquote><strong><em>What would you require from a peer seller before picking up a product in person?</em></strong></blockquote><blockquote><strong><em>You mentioned that you also have sold an item using a peer to peer platform. Can you tell me about the last time you did that?</em></strong></blockquote><blockquote><strong><em>As a seller, are you/would be willing to pay a small percentage of your profits to a host website? (Ex: Would you allow ebay to take 3% of your total profits in exchange for facilitating your transaction?)</em></strong></blockquote><p>Our interview results were strong and quickly backed up our initial assumptions. Users wanted confidence in their purchases. They wanted to purchase things securely on a trusted platform with trusted users. Some overwhelming data poinst that we synthesized from our interviews were that PayPal is the standard that users expected and felt comfortable with in their online transactions and that users were generally on the fence about meeting up in person with a stranger and had requirements for this to actually happen (things ranging from meeting in a public place to bringing a friend along). From our data, we generated 6 “I” statements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-lWnulFGqgstqt8_zRCE7A.jpeg" /><figcaption>aka “I want to feel GOOD about this transaction in every possible way”</figcaption></figure><p>The data points and these “I” statements lead to the following two primary personas being born:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m2ypaKgsJ7tB3baEo7GKQw.jpeg" /><figcaption>Maria is frequent user of peer to peer platforms making her very experienced in the game.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0rLM7XxY3ODxBaBgse1IVQ.jpeg" /><figcaption>Mike is a situational user of peer to peer platforms, one who will use it when the need arises but doesn’t frequent a site or app.</figcaption></figure><p>With Maria and Mike, we were looking at users who have very different general uses for a peer to peer platform but they both had the same types of requirements. They wanted to be sure that this transaction would work out in the way that they intend it to. Our new problem statement was also born out of synthesizing this data: <strong>How might letgo facilitate a safe and secure in-person peer to peer transaction?</strong></p><p>We researched what was industry standard, weighed this against the data we pulled from our surveys, previous research and interviews and moved into our design studio. We loved the “conversational” process championed by services such as letgo — where the bulk of a transaction process is planned out by simply talking to the other party in the transaction. We took this idea and compared it to a full transaction conversational method championed by newer peer to peer services like grailed. We wanted to incorporate our ecommerce process within this conversation so that there could be an entire transaction history right in the chat! The idea was to keep it simple, lighthearted and to make further use of letgo’s already present AI. To take it a step further and reach outside of the app into the physical implications of a transaction, we decided to integrate the option of a “GoBox” similar to Amazon Lockers or even allowing letgo’s AI to suggest safe or suggested meetup locations within a specific area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DUFg-XELn8m1HjcgjSlA9A.jpeg" /><figcaption>Hey user! We’re going to make sure that nothing goes wrong for you! Shout out to our teammate Samantha for also playing the role of UX photographer!</figcaption></figure><p>Our design studio resulted in the layouts that we thought made sense and a logical user flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WAqvu-Q1Y_7kGaHprGTEsQ.jpeg" /></figure><p>We engaged in two rounds of usability testing — the first with a super simple layout that seemed to confuse the users we sought who were familiar with letgo (or similar apps). Users were able to get through their tasks but were confused with the placement of functions in the conversation, thinking they completed messages (rather than clickable options). Our second round of testing integrated a keyboard and letgo’s ever popular suggested response feature that definitely alleviated the majority of users’ confusion and allowed every user to seamlessly make it through each of the 3 scenarios that they were presented with. The scenarios were focused on the perspective of our persona, Maria who wanted to buy a product, securely checkout with said product via the app’s new ecommerce transaction feature and successfully negotiate a dropoff for said product to a GoBox. After this she wanted to build her rapport on the app by verifying her profile from her phone number (in addition to the Facebook and email verifications that letgo currently offers). Maria could also check to see her history of sold items and view her LetGo balance — held in a Venmo style account which could be used within the app or cashed out to various secure accounts such as PayPal.</p><p><a href="https://invis.io/KPCZG8IVT#/247695510_Item_Search">Click here to view the project `letgo`</a></p><p>Throughout our process, we kept thinking of ways we would love to further develop this app. It could be by offering an “uberEATS” style delivery service for a product or having a set dropoff location such as a local UPS store or pharmacy where a user could then go to pick up the item at a later time. All in all, I believe users will gravitate toward the conversational features as our digital presence and digital interactions with people around us become stronger and more prominent. When everything is framed in this conversation view, there aren’t multiple phases that one has to check to see all points of their transaction, it’s all right there in the chat! Remember that couch that you love so much but won’t fit in your new apartment? Letting go is easier now, all it takes is a quick chat!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfcb1dd2a65e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/davidarjunuxdi/letgo-an-exploration-of-feature-integration-cfcb1dd2a65e">letgo — an exploration of feature integration</a> was originally published in <a href="https://medium.com/davidarjunuxdi">davidarjundesign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenMic- A Foray Into Design Thinking]]></title>
            <link>https://medium.com/davidarjunuxdi/openmic-a-foray-into-design-thinking-dcb63a84309d?source=rss-60ca7fd886bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcb63a84309d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[David Arjun]]></dc:creator>
            <pubDate>Thu, 03 Aug 2017 06:03:59 GMT</pubDate>
            <atom:updated>2017-10-18T20:43:25.269Z</atom:updated>
            <content:encoded><![CDATA[<p>Facing The Question: What Is Design Thinking?</p><p>When facing the question of “What Is Design Thinking?”, I can think of an unlimited amount of ways that I would have approached this question prior to starting the UXDI course at General Assembly. I found out that it’s one thing to learn the principles of good design (shout out to Dieter Rams) and another thing altogether to actually take any principle that you want and apply it to something tangible. I’ve always been more than a casual observer of “design”, always thinking about it, always trying to find different ways to approach it but never taking the steps to actually attempt to apply it. Design Thinking has a far deeper application structure than I would have ever imagined. I tried to take this structure and properly apply it to my first project.</p><p>I was a man of many hats during the process of completing this project. I found myself donning the top hat of project manager, the watch cap of user researcher (Jacques Cousteau of the UX world) and even the hard hat and beret of information architect and interaction designer, respectively. Most importantly, I found myself removing these hats altogether in order to don the role of empathizer.</p><p>OpenMic is a project that melded approximately 10 hours of inspiration scattered across three days. It was built from writing instruments, paper, the category of “music” and a bit of love. All of these materials found themselves coming to life as a lo-fi prototype through a wonderful app called Marvel.</p><p>OpenMic set out to solve a problem that I thought to find common in the real world — owning the resources necessary to produce and record music is expensive! I assumed that a lot of people love to make music, whether for fun or “professionally” and that many people would love to get their music out into the world but may not have access to the necessary tools required to get going. With this in mind, I recalled many instances where I’ve seen people indulging in great experiences that they may not have everyday access to and this was done through the magic of renting! It brings all the fun of the experience but without the hefty price commitments that come with purchases. Out of this came a solid problem: How might we provide “musicians” with the means to make, produce and record music in an affordable and noncommittal way?</p><p>I set out to confirm that this problem was indeed real and conducted 11 user interviews. The questions that I asked were:</p><ol><li>Do you consider yourself an avid music listener?<br>2. Do you attend any music shows/concerts/events? If so, do they tend to be big or small or does it vary?<br>3. Would you say that you enjoy listening to music? If so, how long do you think you’ve enjoyed it rather than just simply listening to it?<br>4. Have you done karaoke, did you enjoy it? If so, have you done it for a party or event and would you record it if given the chance?<br>5. Have you at any point, made music? Could be from playing an instrument to full on production or recording? If so, how and where have you done it?<br>6. Do you think you’d enjoy making music in any form?<br>7. When you think of making and recording music “professionally”, do you imagine the process to be difficult or expensive? What do you think some problems would be?<br>8. If you suddenly decided that you wanted to start recording music (or if you have), do you think/did you it would be expensive to gather all materials needed: instruments, mixing tools, studio, production, etc.<br>9. Would you be more inclined to start doing this (even for fun by yourself or with friends) if the necessary materials/locations were more readily available?<br>10. What is your experience with booking apps such as AirBnB or Tentrr? Did you enjoy your experience with either of these or any other booking apps? What are some things that you like/didn’t like?<br>11. How much would you be willing to spend for an hour in a specific place? <br>12. Do you like meeting new people?<br>13. Do you like networking?<br>14. Have you had a past job where you worked on different projects with the same person or same team?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Bc-hmoGJjrcqYxtaqGxjA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IPzKjFuajei6WufBtzpWxA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ODTcT-kz_EllaN8YaOUMQ.jpeg" /><figcaption>User Interviews</figcaption></figure><p>At first, I was definitely aware that I would get important information out of these questions but was not fully aware of what a “leading” question might be, especially when I already had a solution to my problem in mind. My fears were alleviated when people graciously answered all of my questions in full without any extra prodding! Music seemed to be a topic that all of my interviewees enjoyed talking about and my assumptions were confirmed with a resounding “YES”! An interviewee stated that “I am a producer but I can’t operate to the degree that I want to because I cannot afford a soundboard that would take the music I’m working on to the next level”. Another interviewee stated that “I like recording at home with the mic that connects to my computer but I know my tracks could be next level if I had access to an isolation booth”. I immediately thought to myself: I feel both of you. I feel all of you. I want to do something about this. OpenMic is needed and has very important real world implications!</p><p>My original concept was composed of what I thought could be an applicable user flow jotted down in my notebook (along with some logo ideas):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*szuFviEkZhDaeplbnj_dSQ.jpeg" /><figcaption>Original Sketches</figcaption></figure><p><strong>The following sketches formed the basis of my first prototype:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XQ_aMhRMLn8d6UA9lYkmWw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6tj_fgxBomQ7fhWIVrm6GA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvRYc57yV2fTDH09HnpW2g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GT_7ZrPbTEtlqIlAu8eyKA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U2mF-EoKOPvCzBmTDGhgZw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H3kdasbCobGjHEQMPy5Teg.jpeg" /><figcaption>From top left to bottom right, you can find the page flow of OpenMic. The concept here was to take a booking process and emulate it as close to a normal, everyday checkout as possible for something of this nature. It was meant to have an air of familiarity so that the process could be intuitive and have a very accessible level of learnability.</figcaption></figure><p>The next step was to run usability tests to see if this flow made sense and if the practical application of this idea was a feasible thing. I also wanted to discover the easiest possible way for someone to get all information needed but still be able to complete the major task of OpenMic in a minimal amount of steps. I did a quick solo dry run, thought it was great, remembered that I wasn’t my user and went out to get the app tested in the real world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vCf1AQ_8XHTUyRahGwiCEg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QupvVnrIvttdicAq-EHFzQ.jpeg" /><figcaption>I’ll buy you a drink if you test my prototype!</figcaption></figure><p>I asked all 11 of my interviewees to test what came out of their answers to my original questions and 11/11 were successfully able to complete the task at hand! A few offered interface suggestions which I used to clean up ambiguous icons and buttons and add more detail to what was otherwise blank space and thus the final lo-fi prototype of OpenMic was born!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fmarvelapp.com%2F3fedgj1%3Femb%3D1&amp;url=https%3A%2F%2Fmarvelapp.com%2F3fedgj1%2Fscreen%2F30938155&amp;image=https%3A%2F%2Fmarvelapp-live.storage.googleapis.com%2Fserve%2F2017%2F7%2F9b2093e0609c436ba15475e5a156d574.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=marvelapp" width="452" height="925" frameborder="0" scrolling="no"><a href="https://medium.com/media/2257bae2eafd00fbdb89909cb5252eb8/href">https://medium.com/media/2257bae2eafd00fbdb89909cb5252eb8/href</a></iframe><p>I set out to create an app that could help people have a voice and I wanted to apply my ideas of design principles and design thinking to this project. I learned that I have a lot to refine but if I followed the steps thoroughly: Empathize-Design-Ideate-Prototype-Test, I could truly make something that could make a difference to my user. In my journey, I was happy to find people to call my users, I was happy to find ways to empathize with them, and to get others to empathize as well. I learned that UX is a truly applicable field, one that finds itself centered in every major cornerstone of our daily lives, and by approaching design thinking in a human centered way, things could be much easier! I am excited to continue this UX journey and to provide that open mic. Everyone has something that deserves to be heard and through truly understanding what our users need, we can give them a platform to say those things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcb63a84309d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/davidarjunuxdi/openmic-a-foray-into-design-thinking-dcb63a84309d">OpenMic- A Foray Into Design Thinking</a> was originally published in <a href="https://medium.com/davidarjunuxdi">davidarjundesign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>