<?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 Lex Reed on Medium]]></title>
        <description><![CDATA[Stories by Lex Reed on Medium]]></description>
        <link>https://medium.com/@lexreed?source=rss-1c89ccee70ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*K61Eujm0Y0Fz_GqC.</url>
            <title>Stories by Lex Reed on Medium</title>
            <link>https://medium.com/@lexreed?source=rss-1c89ccee70ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:55:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lexreed/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[Venmo for Charity]]></title>
            <link>https://medium.com/@lexreed/venmo-for-charity-ca60a02758c5?source=rss-1c89ccee70ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca60a02758c5</guid>
            <category><![CDATA[venmo]]></category>
            <category><![CDATA[donations]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[nonprofit]]></category>
            <dc:creator><![CDATA[Lex Reed]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 02:33:24 GMT</pubDate>
            <atom:updated>2017-04-04T02:33:24.585Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ki4fpC90mtdeMw2iTVV_wQ.png" /></figure><p><em>This is General Assembly UX Immersive course project.</em></p><p>I lead a team of 3 classmates through the UX design process in order to explore what Venmo would look like with charitable donations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*dsGuhhaK70rFYduZ0hSXTA.png" /></figure><h3>10 Day Design Sprint Timeline</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RUdH_KwGNQSvhKGt." /></figure><p>We chose an aggressive timeline so that we would have an entire day to devote to finalization of the presentation deck and an additional day for rehearsal.</p><p>The first day I recorded what individual goals we all had for improvement as well as a group goal for the project itself; which was a final project portfolio ready.</p><p>Arguably the most insightful thing we did, in addition to interviewing venmo users, donors and charities, was comparing the processes between the two groups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*AfB1z_rxU4gy4YdiZGIYUA.png" /></figure><p>We learned exactly where and with what affordances we needed to design additional functionality in the venmo experience.</p><p>User interviews revealed that the core design principle that needed to guide all other design principles was maintaining the simplicity and efficiency of social money transactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*IxC-j5CqQQiE8SFA30Pygw.png" /></figure><p>Our user testing revealed things like, no one wanted “to be contacted by” the charity or nonprofit; but they did want to “receive the newsletter via e-mail”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*uRT4Iqn47UVDsBEjPqhmxg.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F5HsW01Npbh0%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D5HsW01Npbh0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F5HsW01Npbh0%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/23e2d87731b7c8a4f76b49ffb17de1f2/href">https://medium.com/media/23e2d87731b7c8a4f76b49ffb17de1f2/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FRfMSOjy6vMw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DRfMSOjy6vMw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FRfMSOjy6vMw%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/44f4e20e9d889c33c41b1936c5ccba87/href">https://medium.com/media/44f4e20e9d889c33c41b1936c5ccba87/href</a></iframe><p>All in all I am very proud of what my team accomplished. We worked very hard and were able to produce a research validated, user tested prototype for enabling donation functionality into Venmo’s existing app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca60a02758c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Fail an E-Commerce Prototype in 10 Easy Steps]]></title>
            <link>https://medium.com/@lexreed/how-to-fail-an-e-commerce-prototype-in-10-easy-steps-19a40172c103?source=rss-1c89ccee70ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/19a40172c103</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[fail]]></category>
            <category><![CDATA[toys]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ecommerce]]></category>
            <dc:creator><![CDATA[Lex Reed]]></dc:creator>
            <pubDate>Sun, 19 Mar 2017 23:00:43 GMT</pubDate>
            <atom:updated>2017-03-19T23:04:21.965Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*n8C0-OefE8hsfOvmbLv9jQ.jpeg" /><figcaption>Landing Page Prototype in Axure for Toys Et Cetera</figcaption></figure><ol><li>Even though this is a class assignment and you don’t actually have the permission from the owners to make them a new website, go to the store anyway with two of your classmates and convince strangers that they should share information with you about their lives and business because you smiled nicely.</li></ol><h3><strong>LEARN:</strong> Despite how much you hate hitting up total strangers for information, realize it is quite possibly the most cost effective and efficient way to get really valuable insight.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*DjtwP5i2aiB2NCYPQccqtQ.jpeg" /><figcaption>These really wonderful strangers who were kind enough to share their feelings and dreams with me.</figcaption></figure><p>2. Take pictures and then debrief together at a coffee shop. (PS you did not take enough pictures.)</p><p>3. Feel really good about yourself until you remember this is an “E”-Commerce experience and you haven’t even looked at the internet today.</p><p>4. Immediately hit up friends from college who decided to have kids and ask if you can interview them. Then have the phone interview with a new app that breaks so you can’t actually record the interview but take notes manually anyway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*UrhJfmxfFhONA1y92dbARQ.jpeg" /><figcaption>My good friend from college willing to be interviewed about her kiddos and internet toy shopping experiences!</figcaption></figure><h3><strong>LEARN: A profound respect for parents and their desire to know and encourage their children.</strong></h3><p>5. Share all the ethnographic data you collected with your peers and start writing everything on to sticky notes and white boards. Use those sticky notes to synthesize insights that will frame the scope of your project with design principles.</p><h3>LEARN: You probably should have let the 2 week timeline dictate the scope of your project instead of your excitement for the amazing insights that you synthesized and now want to make features for.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3NrTDuRjUqNfks_xAkenrg.jpeg" /><figcaption>Me, before I got separated from the group and murdered by a masked chainsaw wielding e-commerce website.</figcaption></figure><p>6. Then just like in a horror film, separate from the group and start your own wire-framing.</p><p>7. Do one paper prototype of one page from your now 10 page website (not including all the separate toy pages) and only have one usability test. Because you know, yolo.</p><p>8. Get really excited about Axure’s high fidelity options and spend 1/3 of your project time learning new techniques that won’t actually make it into the prototype.</p><h3>LEARN: Its better to make ‘<em>bad’</em> iterations quickly instead of ‘okay’ iterations slowly. You might as well learn things you didn’t expect faster than slower.</h3><p>9. Realize that you may want to include 20 toys in your prototype instead of 100 because since its only a prototype you’d have to manually make 100 unique toy pages. #facepalm</p><p>10. Start finishing your presentation at the same time as your prototype because they’re both due tomorrow. Stay up really late getting it finished and don’t do a practice run through because you’re tired and pretty sure you can wing that 8 minute mark anyway.</p><h3>LEARN: Okay, maybe practice the speech at least once before presenting.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19a40172c103" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HOW TO PROTOTYPE A SOLUTION IN 3 DAYS]]></title>
            <link>https://medium.com/@lexreed/how-to-prototype-a-solution-in-3-days-950a32f5293a?source=rss-1c89ccee70ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/950a32f5293a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[bikes]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Lex Reed]]></dc:creator>
            <pubDate>Sun, 05 Mar 2017 20:49:01 GMT</pubDate>
            <atom:updated>2017-03-05T20:54:31.354Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Project: </strong>ALL-STAR RIDERS;<strong> </strong>a<strong> </strong>journey app for urban bikers, new and expert.</p><p><strong>Prompt:</strong> Interview a peer for a problem of theirs that a mobile app might solve and create that app in 3 days time.</p><p><strong>Elisa’s Problem: “</strong>I’m worried my bike will get damaged or a flat tire from bad roads around the city and pot-holes. Things like the bike feature on google maps don’t help out because they’re really meant for cars.”</p><h4>Presentation:</h4><p><a href="https://docs.google.com/presentation/d/1aToCRExmklS8Cw_NUDUGv0Ue8J7ZIVa4e5uwQjZ-L24/edit?usp=sharing">https://docs.google.com/presentation/d/1aToCRExmklS8Cw_NUDUGv0Ue8J7ZIVa4e5uwQjZ-L24/edit?usp=sharing</a></p><h4>Prototype:</h4><p><a href="https://marvelapp.com/24bgia6/screen/25482072">https://marvelapp.com/24bgia6/screen/25482072</a></p><h3><strong>Research Process:</strong></h3><p><strong>First, I took a step back from the suggested problem and interviewed two more riders with slightly different urban bike experiences. </strong>I wanted to expand my perspective on the urban biking experience and the needs/habits of existing users.</p><p>In addition to re-interviewing Elisa a second time with questions tailored to the biking context, I also interviewed Maggie and Caesar. Maggie is a professed casual/infrequent biker, while Caesar commutes year round even through winter. I learned that there are three commonly referred to bike types and users do not like taking their phones out while on a rides.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/0*iSmZo8PwJH_uY2Ak." /></figure><p>Utilizing an affinity map I sought to refine my thoughts into the following insights:</p><ul><li>The three commonly referred to bike types roughly correlate to the different road condition needs and risk aversion of the user.</li><li>All three users reported consulting an expert resource like Google Maps for Bikes only for the first few times they road somewhere. Once a user became an Expert of their local paths they stopped engaging online resources.</li><li>Expert users consult a resource or other Expert when they find themselves New to the path about to be taken.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*6H0xg38lp2JG6BEwC-tF8w.jpeg" /><figcaption>WHY THE FUCK IS MEDIUM ROTATING THIS??? PLEASE SEND HALP.</figcaption></figure><p>I synthesized these insights into one guiding sentence to frame my prototyping: Inexperienced urban riders want to know what expert riders are doing. This meant that even though Elisa could be considered an expert of her local paths, she still wanted to consult other experts for updates to road conditions.</p><h3><strong>Prototype Process:</strong></h3><p>With the project given a framework statement from my user research I started brainstorming possible features.</p><ul><li>The app will need to offer users a routing ability.</li><li>Users will need to self-identify what bike they use so the data collected can be qualified.</li><li>If we gamify riding your bike with the app open, perhaps expert users will continue to offer their daily routes on the app. Your daily commute could collect something, in the same way Pac-Man collects fruit on a path to win points.</li></ul><p>I made a list of pages that were going to be necessary for the app and then did a 5 minute sketch sprint per page on the list. Each page would get 5 one minute, quick sketches to help me get ideas on the page and not be slowed down by finickiness. I would then use those sketches as a palate in which to make a final wire frame.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/227/0*ZcPOO-YtW5lGIX4b." /><figcaption>5, one minute sketches</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/148/0*d7B_K6X4dyh0vxRM." /><figcaption>Sketch final</figcaption></figure><p>I showed the wire-frames to users without too much information and asked for feedback with functionality and first impressions. I then made final tweaks to the wire-frames and set them up in a playable prototype format. And I quickly realized how many important things were missing; like “back” buttons. But the presentation was in 6.75 hours and I needed sleep. Lol. Oh, well.</p><h3><strong>Feedback:</strong></h3><p><strong><em>:</em> </strong><em>“When designing for the Expert [augmented reality game] you really ‘lost your way’.”</em></p><p>When I heard this I was surprised. I am actually very proud of my design solution and still feel that it was well substantiated by the expressed desires and habits of the users. After some further thought, however, I realized that I did not share a key insight in my presentation. I made the jump inside my head and did not document it so that the choice to have an augmented reality game appeared ad-hoc. The key insight not included:</p><ul><li>The up to date information, specific to bike type that is needed on a particular bike path is already in the existing riding habits of expert users. Another rider is already changing and updating their route based on existing road conditions.</li></ul><p>Knowing that I needed to get expert users to volunteer their daily route habits while also figuring out how to incentivize them to stay engaged in-between actually needing to consult the data collected, was the primary reason for choosing an augmented reality biking app game.</p><h3><strong><em>Key take-away</em></strong>: Even if my choices are brilliant, if I neglect to defend or explain them adequately then they might as well be bad choices.</h3><p><strong><em>:</em></strong><em> “I want a separate map to consult of all the commonly used bike roads instead of a router.”</em></p><p>This is a great suggestion that I think could easily be added. It makes me wonder if I didn’t need a bike router option at all and instead just a ‘heat-map’ of use by bike type and the game itself to collect that data. Perhaps I jumped to a more complicated solution than necessary. But then again that might not solve the project’s intended problem; Elisa would still want to know if her specific bike path was going to be good or if she should alter it and to what.</p><p><strong><em>:</em> </strong><em>“Don’t use the phrase ‘I wanted’ when describing features.”</em></p><p>This was important language choice feedback. In order to more accurately reflect that my features are responses to user needs I should use the phrases “user research suggest” or “users want” instead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=950a32f5293a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>