<?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 Stacy Wang on Medium]]></title>
        <description><![CDATA[Stories by Stacy Wang on Medium]]></description>
        <link>https://medium.com/@stacystwang?source=rss-b6b021ffdddb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qlttAp-NqRnaqbX5Q0WD8w@2x.jpeg</url>
            <title>Stories by Stacy Wang on Medium</title>
            <link>https://medium.com/@stacystwang?source=rss-b6b021ffdddb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:21:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stacystwang/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[IntroDPD Exercise: {Stacy Wang}]]></title>
            <link>https://medium.com/@stacystwang/introdpd-exercise-stacy-wang-30ffc1c43f42?source=rss-b6b021ffdddb------2</link>
            <guid isPermaLink="false">https://medium.com/p/30ffc1c43f42</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[design-challenge]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Stacy Wang]]></dc:creator>
            <pubDate>Tue, 17 Sep 2019 19:22:49 GMT</pubDate>
            <atom:updated>2019-09-19T18:20:51.089Z</atom:updated>
            <content:encoded><![CDATA[<p>Goal: Your goal is to improve one aspect of the Venmo app using some semblance of the design process.</p><h3>1 — User interview &amp; market research</h3><p>I am a Venmo user myself for more than two years now, but as a designer, you are not the user. So to avoid bias opinions as much as I can, I reached out to 2 Venmo regular users to talk about their experience in interacting with the app. I also found that the rating &amp; reviews (about 6 millions of rating) on the Apple store are valuable feedbacks for quantitative research.</p><p>After the interviews and reading all the reviews, I was able to narrow down the two most common user pain points in my research.</p><h4>Pain point 1: Slow and unresponsive customer services.</h4><p>To my analysis, people are more cautious and anxious when dealing with everything finance/ money-related products. Therefore, have a much higher expectation of customer support on financial products like Venmo. To many people, even though technology continues growing and perfecting people still find the human connections/ communications are more direct and trustworthy than talking to machines.</p><h4>Pain point 2: What if I paid the wrong person ?!</h4><p>Venmo makes sending money fast and easy. At the same time, it is easy to make mistakes but very hard to fix. In short, they failed to provide a way for users to proceed with ease. <br>To my research, the one way to cancel or revert payments on Venmo at this moment is only through sending that user a charge request for the same amount of the payment so they can pay you back. It sounds like a simple reversed flow as to how you would go about to send the money, but think a little deeper then you will find the impractical part about the situation. Imagine you are the person who received an amount of cash from a stranger you don’t know and perhaps never will. What is the chance that you would care enough to reach out and to pay him/her back the money you accidentally received? To reality, the possibilities might be pretty low.</p><h3>2 — Defining the problem</h3><h4>Venmo on their flexibility to fix a payment mistake.</h4><p><strong><em>When I</em></strong> pay and manage money within friends through Venmo,<br><strong>I want to</strong> save time on making trips to withdraw cash from the bank or the ATM. <br><strong>I also want to</strong> avoid the hassle of carrying around the cash with me. <br><strong>So I can</strong> get the chore out of my way fast and quick with ease. <br><strong>But I can’t do that well because:</strong> <br>(1) Venmo failed to offer an easy way to stop or cancel or revert a transaction if I make a mistake. <br>(2) Venmo doesn’t provide specific information on each transaction like transaction ID, which will help the customer support to address my problem in a timely manner.</p><h3>3 — Ideation</h3><p>To brainstorm the solutions, I first looked into Venmo’s current user flow which made the problems more tangible and addressable. I then compared it with the competitors’ app. This process helped me analyzed what our competitors have done right, and I was able to pick up the inspirations and grew my approaches. <br>I decided on reorganizing the information architecture and adding some feature on the activity profiles to make it more informational as well as functional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*yOKwdNNg6oow9dqTP05mqw.png" /></figure><h4>Some new features to the solution:</h4><p>(1) Reorganize all activities in 3 main categories All/ Money In/ Money Out by using the navigation tab. → To shorten the time on searching a specific transaction.</p><p>2) Provide a receipt with assigning a transaction ID, and all purchase details information. → To ease user’s anxiety with having all the transaction details handy and help to speed up the customer support with locating the specific transaction/problem quickly.</p><p>(3) Provide a cancel payment option when it is still available. (When the recipient has not claimed the money) → To ease user’s anxiety with having an accessible way to revert a payment.</p><h3>4 — Wireframes and Prototypes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UMFvV7V-UsQKXFd8iTMT8w.jpeg" /><figcaption>A shorthand for Venmo UI flow on fixing a payment mistake.</figcaption></figure><p>This is an example of a user flow for canceling or reverting a wrong payment. A shorthand description for this flow is:</p><p>“Andrew paid Jenny $250 by mistake → He clicks activity page, searches for that specific transaction → Clicks the transaction, receipt shows</p><p><strong>Scenario 1</strong>: (When the payment status is Unclaimed)<br>→ Clicks cancel → Canceled the payment.</p><p><strong>Scenario 2</strong>: (When the payment status is Claimed) <br>Clicks request payment → Clicks request.</p><p><strong>Scenario 3</strong>: (When the payment status is Claimed) <br>Clicks contact customer service→ Fill out the form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AW8-09aVwaL-Y24XHSE8NA.png" /></figure><h3>5- Conclusion</h3><ol><li>How good is your solution based on the research findings you uncovered?</li></ol><p>In my solution, I provided an alternative way when users are trying to fix a mistake, and this eases their anxieties about when the thing goes wrong. I also offered a more accessible way for users to arrive at the solution faster, and this enhances the efficiency of getting one chore out off their shoulder quickly and at ease.</p><p>2. How long did you work on this?</p><p>I spent about 4 hrs on research and defining the problems, and put People Problem format into practice. Then spent another 2.5 hrs on ideating, Figma tutorials and prototyping. This is also my very first writing on Medium. 🙌🏻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30ffc1c43f42" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>