<?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 Nicholas Peckham on Medium]]></title>
        <description><![CDATA[Stories by Nicholas Peckham on Medium]]></description>
        <link>https://medium.com/@hellonicko?source=rss-1fdb7283ab98------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*KJeUZoEkfmqmiszg.</url>
            <title>Stories by Nicholas Peckham on Medium</title>
            <link>https://medium.com/@hellonicko?source=rss-1fdb7283ab98------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:52:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hellonicko/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[Latin America’s small business warehousing problem — A UX case study]]></title>
            <link>https://medium.com/@hellonicko/latin-americas-small-business-warehousing-problem-a-ux-case-study-2f6efd696830?source=rss-1fdb7283ab98------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f6efd696830</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nicholas Peckham]]></dc:creator>
            <pubDate>Mon, 19 Nov 2018 04:30:06 GMT</pubDate>
            <atom:updated>2019-06-10T18:38:21.688Z</atom:updated>
            <content:encoded><![CDATA[<h3>Latin America’s small business warehousing problem — A UX case study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ha4gCWXYGQkpumvrREB67g.png" /></figure><h3>Project Details</h3><p><strong>My Role:</strong> Product Architect (also UI, project management and many other hats — it’s a startup)<br><strong>Company/website:</strong> <a href="http://www.cubic.mx/">www.cubic.mx</a> — <strong><em>Many screens below show “Zingo” as the name, this was the investors name but after testing different names Cubic prevailed as the winner.</em></strong><br><strong>Product:</strong> Warehouse booking and order fulfillment platform in Latin America<br><strong>Product Team:</strong> Lead Product Designer (myself), Product Manager, CEO, 2 Backend engineers, 1 Front End Developer, Sales lead<br><strong>Some tools:</strong> Sketch, Marvel, Usability Hub, Google Analytics, Hotjar, Ubertesters, User testing, Contextual Inquiries, and Jira<br><strong>Project duration: </strong>At Time Of Writing<strong> — </strong>12 Months and counting<br><strong>Location:</strong> Miami, Bogota, Mexico City</p><h3>The problem</h3><p>Many parts of Latin America are still catching up to the E-commerce craze that has been part of North American’s life for so long. There is currently no way to easily search for, discover, and utilize warehousing space in a flexible way. In Latin America, finding a warehouse to store product is quite cumbersome and outdated. The process of agents, brokers, negotiations, and networking create a barrier to a simpler straight forward process. For small and medium size businesses the process of finding a warehouse that will cater to a small product volume is one of the biggest challenges most start-ups are facing when searching for warehousing. Most warehouses require a minimum amount of product and an inflexible length of lease. Startups are left scrambling to grow their business and reach customers. This is where Cubic, an online warehouse booking platform, comes into play.</p><h3>Starting from Scratch</h3><p>When I started with Cubic there was no product, and the business was more or less just an idea. The larger company I work with, Rokk3r Inc, has a process called a ‘think phase’ where ideas are validated through a series of exercises. Below are some of the basic slides used to create a strategic plan to build the Cubic MVP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TPJsUyZa30rm5yNHOYQuww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*macZY_P8t6y8QjGz3iF7Rw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gE4fd8KN5K7FGQwAodt0YA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-JvLumy3tbGO6MEs2dud9w.png" /></figure><p>I was brought onto the product team shortly after the think phase had wrapped up. It was now up to me to see the MVP design and build all the way through.</p><p>The first steps were trying to understand the warehouse and logistics industry. This took many weeks. The team and I did tons of research. This included domain research, competitor analysis, and understanding the overall health of the logistics industry in Latin America.</p><p>After reaching out to industry experts on LinkedIn and internal networks, I was able to gather enough details to come up with a rough features list and split it into ‘nice to haves’ vs ‘must haves’. This was key to building the MVP and naturally the ‘must haves’ were implemented into the first prototype that was created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ykkHh55e4WNDbPmjpeXe9Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q8CAHNcY1LBCAg7mLlbsxg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*egGEdBK-PWB79LiZwVOpiA.jpeg" /></figure><h3>Three different products</h3><p>An interesting thing about platforms is that it often ends up being multiple products wrapped up into one. In the case of Cubic, we needed to build a product for Warehouse Renters, Warehouse owners, and an Administrator.</p><p>It was important to understand early on how each interaction from one user would affect another. Diagrams helped me visualize the process before designing the flows. The whiteboard helped too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*481qerLXGSoq4ALq4c_H0Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fDoq5xQiSVssDPmnnmz_Kw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eeX0ds-WkriqNGCmji4-_g.png" /></figure><h3>Product ideation</h3><p>I started designing for mobile first. We collected loads of data suggesting that we would need to have an entire mobile experience for the product we were building (for the MVP we decided to skip the dashboard functionality for mobile). Below are some of the first low-fidelity mobile wireframes that were used to fuel more conversations and iterations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*Pkk9FssaQe7tTZrhLJRBSg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*hSjPN86_NLaX-fe5aYNl7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*lXQQgTonmjYP_9XeC71Skg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*OdSs6Ko6qBpM42Ulj3bnjg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*VF0qCTg_UKvssGRthOn0FA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*ul2FkH0atPDezspXB_lcAg.png" /></figure><h3>Managing Multiple Types of User Dashboards</h3><p>One of the biggest challenges of this product was keeping users informed of the steps involved in the booking process. Because this is an MVP and we are not integrated to warehouse management systems yet, a lot of the processes are manual. This creates a scenario where the renter, owner, and admin all have different actions to complete at different times of the booking process.</p><p>We needed to create a UI that displayed the correct dialogue and expectation for each user. The challenge was the dialogue is dynamic and can change based on the actions of another user. For example, if a renter submits a booking request, the warehouse owner would be notified to review that request, and while the owner reviews the request, the renter would be notified that they need to wait to proceed until the owner has reviewed the request. At the same time the admin also needs to review the customer making the request to make sure they are credible and meet Cubic standards. To help the lead engineers understand the logic, I created what I like to call ‘booking stories’. They are step-by-step cards that each user would see within their dashboard and notify the user of what action to take during the booking process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1fOIuy-BJMYqISaWyZ5CAw.png" /></figure><h3>Combining Value Proposition &amp; Usability Tests :(</h3><p>This was one of the first projects I have worked on where I was not only testing usability but also testing product viability at the same time. It was difficult to strategize how to ask questions about usability and seamlessly deduce if our testers would even use a product like this.</p><p>The best solution was being on the ground in Mexico City and meeting with potential users to hear their insights and how they would use our product. It was great to eat so many tacos, but more importantly have meetings with top tier Mexican companies that were so willing to help.</p><p>We tested with many potential customers that would could be renters and owners. This allowed us to do some on-site Q&amp;A to gain deeper insights of how warehouses function. Below are some cool shots of the team testing the product in the companies cool offices and warehouses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ksod3o0yg6djNhU33xVoRA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mhEaF3Fq6pCaLTPrwxlw_Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k48sMOtODH_T9_GAszoJSA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5o_b_KlmTmijqPGIzP6Uw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*enH7TQ7ex_pnI1BlTZCJiA.jpeg" /><figcaption>I was the one taking photo during value prop testing — I would then take over the meeting and discuss usability, features, and functionality</figcaption></figure><p>The data we collected answered many questions. Most importantly, the question of “would people even use a product like the one I was designing” was answered with an <strong>overwhelmingly yes.</strong> Woo!</p><p>After we returned back to the states, we were able to move quickly with iterations and continued remote testing with the same users from Mexico.</p><p>The product started to take form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IZ1IKz2QyREjTpFXfXEPnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VF70Ttb8IBvGdJ2OFqEzA.png" /></figure><p>After testing and testing, one continued issue we had was the side navigation menu, many people were unsure of the booking dropdown. So we simplified the side menu and removed nested items and placed those items always in view.</p><p>This is also when we renamed our company to Cubic. We changed the logo, name, and styles of the UI throughout the platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ca1_pE3VkOn125IsQETQfw.png" /><figcaption>The homepage</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iN77QTTQSrRi56-j0kbdNQ.jpeg" /><figcaption>The first screen for renter sign up</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EzQX40d-HsV0jjsuXCx3Sw.png" /><figcaption>Renter dashboard — managing bookings</figcaption></figure><h3>Some personal notes about things I have learned while working with Cubic</h3><h3>User Advocacy — Plus Managing Investor Expectations</h3><p>A huge challenge in my role with Cubic is the elegant balance of fighting for the user, but also meeting expectations of the investors. It consistently feels like we are moving too fast, add features or functions that have not been validated, not testing enough, and overall just building the product for our investors. No matter the road map, there are always limited resources and a lack of focus on testing and iterating.</p><p>Because of my role as UX/UI, and PM, it became overwhelming and was hard to be constantly thinking about the people that would be using our product. There were so many times I had to remind myself who I was building this product for. I have now created a checklist that I complete at the end of every design or collaboration day to keep myself in check.</p><h3>Working remotely sucks — Kind of</h3><p>Autonomy and the freedom to work wherever definitely has its perks. But, from a productivity perspective, being in the same room as developers and the CEO defeats any perk working remotely has. The larger company I work for, Rokk3r Labs, has an office in Bogota, Colombia where all the engineers and developers are based. I have traveled to Bogota three times to get shit done with our development team. No matter the annotations, Jira Sprint, or Slack conversation, nothing compares to being able to point at something with a developer at your side and explain how it should be functioning or animating.</p><blockquote>I am huge advocate for working with the product team side-by-side.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1JfEPP0RkaaOvjolu8iZzg.jpeg" /><figcaption>That’s me working with my team in Colombia!</figcaption></figure><h3>The end — but not really</h3><p>Cubic has just shipped, and launched marketing campaigns. It is starting to gain traction. It was so rewarding to have 8 users the first week complete the registration flow and start the booking process. There is still tons of work to do, and I am excited to watch the platform evolve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SB1uIC2FKP-EXfSF11avsg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f6efd696830" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving conversions with design — a UX case study of Emerge.me]]></title>
            <link>https://medium.com/@hellonicko/ux-case-study-with-a-dash-of-ui-emerge-me-c6738e451125?source=rss-1fdb7283ab98------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6738e451125</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[conversion-optimization]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nicholas Peckham]]></dc:creator>
            <pubDate>Sun, 12 Aug 2018 18:46:27 GMT</pubDate>
            <atom:updated>2018-09-10T03:36:15.224Z</atom:updated>
            <content:encoded><![CDATA[<h3>Improving conversions with design — a UX case study of Emerge.me</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HUIRpLyDgZpO0zlxcW3x9Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*vioLX-UaaeeWJO-jUZoS-Q.png" /></figure><h3>Project Details</h3><p><strong>My Role:</strong> Lead UX/UI Designer (A bit of project management too)<br><strong>Company/website:</strong> www.emerge.me<br><strong>Product:</strong> Supplement insurance platform for mobile and desktop<br><strong>Product Team:</strong> Lead UX/UI, Product Manager, CEO, Lead Engineer<br><strong>Some tools:</strong> Sketch, Marvel, Usability Hub, Google Analytics, Hotjar, and Jira<br><strong>Project duration:</strong> 4 months<br><strong>Location:</strong> Miami, Florida</p><h3>Project results</h3><p>The results of this project are data driven. These results are a by-product of relentlessly fighting for the user and focusing on their needs <em>(while maintaining business objectives).</em></p><p>Below are some results of my time spent working with Emerge:</p><ul><li>Redesigned homepage ‘above the fold’ experience for both mobile and desktop. <strong>Increased desktop main CTA conversions from 8% to 27%, mobile CTA from 2% to 18%</strong></li><li>Redesigned copy and quote form <strong>increasing form completion from 4% to 15%</strong></li><li>Increased navigation and findability (used 5 second test)</li><li>Doubled the amount of users that were scrolling to the bottom of the homepage</li></ul><blockquote>Below I will focus on solving ‘above the fold’ content, which also helped solve navigation and findability</blockquote><h3>What is emerge.me?</h3><p>Emerge is a startup focused on fixing the supplemental insurance industry. The leadership team can be found running around the streets saying:</p><blockquote>“We’re making supplemental insurance easy to understand and accessible to everyone”</blockquote><p>The insurance world is riddled with antiquated processes and most supplemental insurance today is still sold by an actual person coming to your home and making you sign a stack of papers.</p><h3>99 Problems — and research was one</h3><p>Within my first week with Emerge, I quickly discovered the lack of user research. A startup with minimal user research? No way!</p><p>Before I jumped in and redesigned anything, I needed to understand more about the individuals actually using the product. Unfortunately, because of the way the customer database was set-up, I was only able to have minimal contact with actual customers. So, it would be guerrilla strategy interviews or nothing (at least in the beginning). This meant everyone in the office, coffee shop, or my immediate family would succumb to a usability test. In the end I interviewed 17 people from different demographics, ages and gender.</p><p>During test sessions, I relied heavily on A/B tests, switching between the live site and clickable prototypes. Observing people switch between the two versions made it easy to eliminate assumptions while also gaining insights to user preferences.</p><p>Some of the discoveries were:</p><ul><li>Users were not able to comprehend and explain the site’s purpose within 5 seconds of viewing above the fold content.</li><li>They were unable to complete a given task quickly, because of site navigation and findability issues.</li><li>They felt the quote form lacked structure.</li><li>Pages were too long and didn’t tell a good story.</li><li>Of the users I interviewed — older (ages 48+) generations preferred background images over illustrations. The younger generation (ages 20–40) strongly preferred the illustrations.</li></ul><h3>‘Above the fold’ content, and navigation redesign</h3><p>‘Above the fold’, such a lovely use of editorial language in the digital space. This often overlooked section of a website can be priority numero uno in regards to first impressions which directly impacts user behavior.</p><p>With Emerge, they understood this but did not execute well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BLMRPWNClUJLTpYEd1rauw.png" /><figcaption>Original design that I was challenged with improving</figcaption></figure><p>The original design looked nice, but did not function as well as it could. There was no obvious eye path, CTA’s did not pop, bounce rates were not meeting company goals and after testing, it was discovered that readability and comprehension were problematic as well.</p><p>Some of the answers I gathered during testing explained how users did not know if the site was a general insurance marketplace, or if Emerge was selling their own products. The main CTA(s) were consistently overlooked and almost no one watched the product video. Most visitors only scrolled down 30% of the page on both desktop and mobile.</p><p>Below are the hotjar click heatmaps after 2000 visitors, for both desktop and mobile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P2QyDcuQLjZ2_W-QBH5Osg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*gDn28AREixg86ev13RGJzw.png" /></figure><p>The most clicks for both desktop and mobile were on buttons that immediately distracted users from the site’s purpose. On desktop, for some unknown reason, 7% of all visitors were clicking on ‘login’. And just in case you think “ha, staff testing the site”, this was not the case. On mobile, 7.5% of visitors were quickly clicking on the hamburger menu. Users disappeared after these clicks.</p><p>I wanted to completely redesign the homepage so we could A/B test. This was a difficult solution to implement because of the buy-in needed from the rest of the team.</p><blockquote>This is one reason why I started with designing above the fold content first. To get the team on board, I created a presentation to sell my idea. In the presentation, I simplified the design process by simulating the lack of eye path and how the design was built around form and not function.</blockquote><p>Below are some slides from the presentation:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQ--VpS8lONU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQ--VpS8lONU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQ--VpS8lONU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/83de0c4e2ef190409e70faef997600e7/href">https://medium.com/media/83de0c4e2ef190409e70faef997600e7/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FX68n3v0OsRg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DX68n3v0OsRg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FX68n3v0OsRg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0fef4cb02d23b1c1cb8fea22606698ae/href">https://medium.com/media/0fef4cb02d23b1c1cb8fea22606698ae/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FgZLdaa5rgnI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DgZLdaa5rgnI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FgZLdaa5rgnI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0cb38f99ffffb536d1c713b3220b17a2/href">https://medium.com/media/0cb38f99ffffb536d1c713b3220b17a2/href</a></iframe><p>With a few strategically placed arrows and triangles, I was able to demonstrate how a new UI could increase usability. The team approved the new interface so we moved forward.</p><h3>Some notes about the User Interface</h3><p>As you can see from the updated UI, some of the style was dramatically changed . This was very purposeful. The reason behind the changes were:</p><ul><li>The original UI had competing colors calling for the users attention; so we selected a secondary brand color that would only be used for CTA’s.</li><li>Because of our marketing channels and the way users were directed to the site, a larger majority of the users visiting the homepage were under the age of 38. This data pushed us into experimenting with illustrations instead of images.</li></ul><h3>Launching the redesign</h3><p>After more iterations, more testing, and of course many compromises, we decided to build and launch the version below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dhmQFZCSZEShWPaThSMoFw.png" /></figure><p>Once we launched, we monitored how user behavior changed using Google Analytics and Hotjar.</p><p>Below are the results from the click heatmaps from Hotjar:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KyPTQsJjhDIQy-6kOg0HlQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*6ewB1idZITL_9CN0WVaORg.png" /></figure><p>After 2,000 visitors, the results were pretty clear that the new design worked much better at converting users.</p><ul><li><strong>Original</strong> desktop design heatmap — Main CTA(s) converted 4% of users; <strong>New</strong> desktop design heatmap — Main CTA <strong>converted 27%, up from 8%</strong></li><li><strong>Original</strong> mobile design heatmap — Main CTA(s) converted 2% of users; <strong>New</strong> mobile design heatmap — Main <strong>CTA converted 18% of users, up from 2%</strong></li><li>As a result of user immediately understanding the product offering, the amount of users scrolling to bottom of the homepage doubled.</li></ul><h3>To be continued</h3><p>Conversions were increased, and bounce rates decreased. This does not mean Emerge is in the clear, there is still a lot of work to be done. But at least the user experience is heading in the right direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xzsNKwB6DX1OEQDl_pxorg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6738e451125" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lendified —a FinTech UX Project]]></title>
            <link>https://medium.com/red-academy/lendified-a-fintech-ux-project-7579d64d3c32?source=rss-1fdb7283ab98------2</link>
            <guid isPermaLink="false">https://medium.com/p/7579d64d3c32</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Nicholas Peckham]]></dc:creator>
            <pubDate>Tue, 14 Mar 2017 00:43:02 GMT</pubDate>
            <atom:updated>2017-05-04T14:18:19.002Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D6qbo_EMVJJNXs1DsV0f_A.png" /><figcaption>Our product design delivered to the client.</figcaption></figure><h3>Intro</h3><p>When I was approached to lead a team of UX and UI designers on a project with a financial tech company, my initial reaction was skepticism because I knew nothing of the domain. Because I love a challenge, I jumped right in.</p><p>What you are about to read is a case study about my role as a product designer working with a FinTech company and what it was like overseeing every step of the design process. After our first day of research with Google Analytics, it was clear to us that we needed to design for mobile first. But to have more of a focused case study, I am going to talk about the desktop redesign.</p><h3>The Research</h3><p>Lendified is a company that offers short term business loans. In order to complete this project the team needed to do extensive research to understand the purpose of the product we would be producing. We needed to understand the people applying for loans and why they needed it. This included:</p><ul><li>Hours of youtube, google, and financial blogs</li><li>User interviews</li><li>Hanging with the team at Lendified and asking a lot of questions</li><li>Spending loads of time on their existing site</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3EJKr-4cUUR3Tre3pp4gFA.jpeg" /><figcaption>Our first brain dump session.</figcaption></figure><h3>The Diagnosis</h3><p>The next step was to see why Lendified needed a redesign. We spent two days tearing apart their current website piece by piece. There were some obvious issues that needed to be solved. Here are some of the items we discovered:</p><ul><li>Information Architecture — during our usability tests, people were not able to navigate a given task within a set threshold of 6 seconds.</li><li>Eye Path — Most people didn’t know where to look on the site to find certain CTA’s (call to actions) or content.</li><li>Competing Icons and CTA’s— It was difficult for users to tell the difference between buttons and icons. Colors, sizes, and placement choices contributed to this.</li><li>Color scatter — Users complained about too many different uses of color and being distracted.</li><li>Latency Issues — Using Google’s site speed test, the current site ranked 27/100. Just like in school, that’s an F.</li><li>Users felt concerned about the credibility as a result of the above. This is a major problem when dealing with a financial site.</li></ul><h3>Prototype First Approach</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E33imqX6FNAJLpaQqMm7TA.jpeg" /></figure><p>We started prototyping and testing as soon as possible. We had our first wireframes done the second day of the project. As the data trickled in, we made new versions and continuously iterated upon those. This became the day-to-day norm of the project.</p><p>In order to make the right design choices, we did massive amounts of research on UX/UI patterns. We focused on what works and what doesn’t work for financial companies. Early on in the design process, we established that we needed to be particular in building a product that expressed trust and credibility.</p><h3>The Information Architecture (Sitemap)</h3><p>Because of the poor usability testing results with the current sitemap and navigation, we restructured their existing ones that would eliminate duplicate content, increase SEO opportunities, and most importantly enable the user’s ability to find what they need quicker. We gave the mobile sitemap a lot of attention. Through analytics and user testing, data showed that people were using the mobile site very differently than the desktop site. The data also suggested we needed to build a specific IA for mobile. To match the mobile sitemap, we built a mobile only site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EKk3rN2pwDQ3r_xpQnMQTA.jpeg" /><figcaption>Below is a fun way of working on the nav bar and footer using the good ‘ol sticky note method.</figcaption></figure><h3>The Usability Tests</h3><p>This is easily one of the most important parts of the design process. It comes down to seeing if your designs suck or not. We decided to do one on one testing as well as remote. Testing provided us actionable insights, enabling the team to design better experiences. When presenting to the client, user testing was at the forefront of every conversation. One of the most influential tools we used to defend our design was the eye path test. We used a simulation software to develop a comparative analysis of their current site and our redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kk-ZLdnzo26Ssuuj-u31vg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5glxZzaqPPoGCBaOKRnbAA.png" /><figcaption>This is a comparison of the current site and the redesign site. The redesign demonstrates how we were able to direct the user’s gaze to the main calls to action.</figcaption></figure><h3>The UI / Colors</h3><p>Lendified has a signature green that we needed to work with to stay within brand guidelines. To address the problems of color scatter and competing icons, our lead UI designer created the following style tile. It was important to compliment the signature green and not clash with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uq72GVSlIYUGBpkItnX7PA.png" /></figure><h3>The High-Fidelity</h3><p>With all our research and pieces strategically placed, we had enough to back our design choices and have our UI team develop high fidelity mock ups. Here is what the redesigned product looks like in the wild.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TwGj2NKAZ4EIo-5YJgLsTg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kEaOSODuOzQysAZHpQUbpw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7gF9cZ4K8yfW1FQaNR7noQ.jpeg" /></figure><h3>Words About The Design Team</h3><p>I want to give a shout out to the team I was working with and how much our chemistry had an impact on our project. Working with the right people can make or break the experience of collaboration. The group I worked with was stellar. Our ability to communicate, adjust, and shift at any moment was key to our success. Ultimately, trusting each other is what makes the difference between designing a great product or a mediocre one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*-xI9edvbl_aUzW6FkkRe4g.gif" /></figure><h3>The Summary</h3><p>On a cold Friday, we presented all our data and prototypes to the client. Simply put, they loved it. Success.</p><p>Our success came from our granular approach to validating every step of the process. That’s what UX is all about. Every pixel has a purpose.</p><p>Reflecting back on the diagnosis section of this case study (IA, eye path, color scatter etc), we provided a solution for each problem. We also went above the expectations of our client by providing future insights for growth.</p><p>The end.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7579d64d3c32" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-academy/lendified-a-fintech-ux-project-7579d64d3c32">Lendified —a FinTech UX Project</a> was originally published in <a href="https://medium.com/red-academy">RED Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Power Lines and Trucks — a Design Hack]]></title>
            <link>https://medium.com/@hellonicko/power-lines-so-cool-unless-they-fall-on-you-5e440a622b6d?source=rss-1fdb7283ab98------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e440a622b6d</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nicholas Peckham]]></dc:creator>
            <pubDate>Sun, 26 Feb 2017 04:05:31 GMT</pubDate>
            <atom:updated>2017-02-26T15:07:16.516Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s get on thing straight, electricity is super cool. It’s also super dangerous. So I guess the proper statement is, ‘contained electricity is super cool’.</p><p>What you are about to read is a retrospective case study of a product I created 2.5 years ago. Now that I have a UX design brain, I am able to look back at past projects I have been a part of and recognize design processes I was using. At the time I didn’t know they were official design practices, they just made sense to apply to the building process. Below is an image of our finished product to give you an idea of what we built because while reading this, you might not have a clue of what I am talking about. We called it the o.h.a.s. (overhead hazard awareness system).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QiNOtA_CUAMmdyo_EYwYIg.jpeg" /></figure><h3>The Idea Spark</h3><p>A while back I was working as Health, Safety and Environment Data Analyst in the oil industry. I was constantly skimming through data. The data was specific to problems humans were having in the North Dakota oil field. Having access to a huge database of problems was a treasure trove for my designer mind. Everyday I was being provoked by data to think of solutions to help people not injure themselves. One day, my co-worker Alex and I were investigating a case where a truck hit some power lines. Fortunately no one was hurt. A month later, another truck pulled down some power lines. Two months past, another line strike. Here’s the loco thing, some of these line strikes were costing companies around 50,000 USD. Alex and I continued to ask the same question over and over;</p><blockquote>“Why the hell is no one creating a solution for this?”</blockquote><h3>Initial Research</h3><p>We started off by doing some domain research. To put it simply, no one had a real solution yet. Some oil companies were hanging some bullshit flagging up with wooden posts that would rip apart in the extreme North Dakota winds. Other than that, the solutions were non-existent. We both agreed to start sketching out ideas of possible solutions of products we could create to alert truck drivers of upcoming power lines.</p><p>We visited every industrial company website known to the internet. We surveyed everyone at work. We even drove miles and miles of North Dakota oil fields looking for any possible solutions people had come up with. It became pretty obvious that we were going to be the first ones to develop a specific product to address one very specific problem.</p><h3>Design Challenges</h3><p>Here’s the thing, Alex and I are not industrial designers or engineers (not yet anyways). As a video producer and digital content creator, I knew how to design for the digital space but I didn’t know much on how to create for the physical world. But this didn’t stop us. After throwing around ideas and third grade level drawings, we brainstormed a list of issues we needed to design around. Here’s a list of just some of them:</p><ol><li>Visibility; day vs night.</li><li>North Dakota Winds; because gusts can be as much as 140 m.p.h, yes it’s absurd.</li><li>Ice; During winter the oil field grounds can become a ridiculously thick layer of ice.</li><li>Portability; our product would need to be moved from one location to another by humans, frequently.</li><li>Setup; the simplicity of the design was vital to the people that would be setting it up.</li></ol><p>To give you an idea of what the environment might look like at the worst times of the year, I gift you with these lovely images. I will forgive you if you want to return the gift for a full refund (sorry North Dakota).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*DZFSyX4E_rGHEWHRyBi3qQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*lUPVvilIITLHylqv1dRiBg.jpeg" /></figure><h3>Building — The Most Fun Part</h3><p>We probably spent 30 hours a week driving to different hardware stores researching different types of materials, contraptions, nuts &amp; bolts, and tools. We were about to build a product out of fitting pieces designed for plumbing, flooring, and even parachuting. We also spent a considerable amount of time on Amazon.com looking for other solutions. After about two months of building material research, we were ready to start assembling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZURDngwg0iJJomLv90K-VQ.jpeg" /><figcaption>That’s Alex, crushing it in his everyday camo pants.</figcaption></figure><h3>The Prototypes</h3><p>Once we had our prototype standing, we took a step back and just stared at it for about five minutes. There was a lot of head tilting, walking around it, jumping on it, and pulling on it. Without saying anything to each other, we were both super excited, but also acknowledging all of it’s flaws. We made a list of what needed to be improved. This list consisted of pretty much the whole design. But that was ok, we went into the project expecting to have flaws in our creation. Version two was put together within a week. We went from taking 3 week assembly to just a week, I knew we were on the right track. The third iteration took one weekend.</p><h3>Field Testing</h3><p>Version three, almost there. Alex had a second property in a rural area without any development. It was the perfect place to truly test out our design. <strong><em>“Version three vs the environment”</em></strong>. We were confident enough to set it up and leave it stranded there for 30 days without returning. When we did return, to our amazement it was still standing. We made some changes to it and left it out for another 60 days. We returned again to a very satisfying sight. It was still standing as if we had just set it up the day before. Success. Below is a video of how the o.h.a.s looked as you pull up to it. Notice the flickering ribbons across the top of it, that was an accidental and not part of the original design, it actually made it even more visible, Huzzaw!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-coU9wGq0ZE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-coU9wGq0ZE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-coU9wGq0ZE%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f18557d2fb8dfb09d756020286affaff/href">https://medium.com/media/f18557d2fb8dfb09d756020286affaff/href</a></iframe><h3>The Components</h3><p>Without boring you too much of the individual parts we used for the finished product, I’d like to give you an idea of the creativity that went into it. We needed to use ultra durable pieces and also use as little pieces as possible. We eventually ended up on a prototype that was able to be assembled in the field with the use of just four pieces. Those four pieces all served a very specific purpose. Here are some of components and purposes below;</p><ol><li>1.5&quot; steel, threaded conduit piping in 10ft, 5ft, and 3ft sections (we wanted our design to be super durable and also modular for different heights of power lines)</li><li>Non-Rip paracord 550 (used to hang reflective ribbons, it was key it didn’t tear and wear down in the extreme weather)</li><li>Threaded flanges (we wanted as little tools needed to set up the kit, by using threading flanges and piping, you could set the kit tool-free).</li><li>Highly reflective industrial tape (nighttime and winter storms would present a serious problem for visibility, we wanted our design to stick out like a homeless person shopping in a Gucci store.)</li><li>3/4&quot; plywood and plastic sheeting (together these pieces would form the base of the structure that would hold everything together. Plywood and plastic was economical and long lasting, but also created enough weight to hold the system down in high wind conditions. It was also light enough for two people to carry and set up).</li><li>A-frame jacks (the jacks were used to setup and level the kit on all ground conditions. This included concrete roads, snow, dirt, and ice.</li></ol><h3>The Finished Product</h3><p>Our next step was setting up a demonstration of the overhead hazard awareness system to a national distribution company that had a retail store in North Dakota. We needed an image and branding. We decided on a company name of “Dakota Fox”. When I created the logo and branding of Dakota Fox, I wanted to portray the earthy and icy feeling of North Dakota. We settled on the design below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZrVEDscHkxgQuTjgGio2A.png" /></figure><p>With the product ready for show, we had a successful first meeting. After a few more meetings, we ended up selling our design to them. Boom! Below are images of the o.h.a.s. in all its glory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QiNOtA_CUAMmdyo_EYwYIg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Z7GPtYOHJZ5-CjgkI5KyA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UalW5WWO7WLPBJVW0kOMSQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eai8bFDQqYpik4_d99w9WQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e440a622b6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brew Box — Creating a Two Sided Platform]]></title>
            <link>https://medium.com/red-academy/brew-box-a-beer-distribution-company-ba2454e21688?source=rss-1fdb7283ab98------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba2454e21688</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[beer]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[redesign]]></category>
            <dc:creator><![CDATA[Nicholas Peckham]]></dc:creator>
            <pubDate>Tue, 21 Feb 2017 04:40:15 GMT</pubDate>
            <atom:updated>2017-02-26T15:08:15.640Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Intro</h3><p>Have you ever had craft beer delivered to your doorstep? That’s what the company Brew Box is doing in Ontario, Canada. They are doing a good job at it too. Right now, their core offering is a monthly subscription box of beer. Even though the company is only two years old, they are already acknowledging opportunity for growth. As a UX designer, this is when I got involved in the craft beer delivery scene.</p><h3>The Problem</h3><p>Brew Box approached our design team with a problem that had to be solved in less than three weeks. They needed help understanding how to integrate a new craft beer store front to their website without detracting from their core offering of subscription services. This wasn’t only a digital problem. Brew Box supplies an End-to-End service by being the distribution platform for many local Ontario breweries. We quickly recognized that we would be working in the realm of a two sided marketplace, customer and breweries. Brew Box gently sets themselves right between the middle of the two.</p><h3>Our Approach</h3><p>Going into this project we knew nothing about the alcohol industry in Canada. So we hit the web and dug through loads of data the Canadian government makes available to the public via <a href="http://www.statcan.gc.ca/">http://www.statcan.gc.ca/</a>. Not only did we learn how massive the industry really is, but how much room there is for growth. Brew Box came to us with the right kind of idea, and now it was time to validate the execution.</p><p>Because we had never worked in the booze industry before, we wanted to get a feel for how the company operated. Before we knew it, we were building and packing boxes of beer at Brew Box’s warehouse. It was really helpful being able to meet the core team and hear the different insights each person contributes to the company. One of the first things noticed about the product was the packaging. Essentially, it was just a box of beer, but let’s talk about that later. Here are some action shots of the Brew Box and design team working hard together at the warehouse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mjz0ZTAaWhxV78TMKgH0Cw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EagrmuJVXg07vZZnWvlInw.jpeg" /><figcaption>Yes Matt, you can take it home with you.</figcaption></figure><p>Once we had an understanding of what goes down at the warehouse, it was time to focus more on the recipients of those beer boxes we were packing.</p><h3>Listening To The Customers</h3><p>One of the benefits of working with Brew Box is they already had their customer database readily available to us. We were easily able to contact customers for surveys and interviews. We received an overwhelming response from current customers. But what about non-customers, we interviewed them too. It was really important to us to find all types of beer drinkers. We sought out craft beer enthusiasts, the hardcore boozers, and the light drinkers too. After receiving our first sets of quantitative data from survey responses, we needed more, so we set up contextual inquiries to focus more on the qualitative side of things. Here’s a picture of us casually and enthusiastically inquiring a craft beer enthusiast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQqMYxIiU4HD1UAH4Fz54g.jpeg" /><figcaption>Super exciting, I know.</figcaption></figure><h3>Don’t Forget About The Breweries</h3><p>We set up in person interviews and also sent out email surveys to different breweries to find out how they operate their business now, and how they want to be operating their business in the future. 90% of them said they are aiming for some type of distribution but lack the tools necessary to make it happen.</p><h3>The Insights</h3><p>We dug through website Analytics, industry data, and after gathering insights from Brew Box, customers, non-customers, and breweries, we needed to put it all together to form ideas to solve the problem Brew Box came to us with. But once you solve one problem, all of a sudden you have more to deal with. In this case it was user engagement. According to their site analytics, 76% of their customers visited their site once to oder their box and then never returned. As long as they were receiving their box at their door they had no reason to return to the site. We also found that only 25% of breweries are using some type of online distribution platform.</p><p>So here is what we planned on tackling:</p><ol><li>Restructure the marketing from a subscription box to a ‘membership box’. This was the key to more business as well as continued business.</li><li>Add a new feature to the website called “The Bottle Shop”. This is where people can purchase craft beer with out being a member.</li><li>Demonstrate why Brew Box are experts and how they can share that expertise with you.</li><li>Redesign the packaging and the tasting notes in that packaging.</li><li>Increase engagement for returning users on the Brew Box site.</li><li>Create a two-sided platform for both Brew Box and Breweries can use to manage their businesses.</li></ol><p>Easy right?</p><p>One of the patterns we identified between all surveys and interviews was the idea that Brew Box was just a ‘box of beer subscription service’. Here are the key findings that we worked with to validate our designs.</p><ul><li>80% of Brew Box clients are purchasing craft beer from other sources</li><li>91% of polled Brew Box users would be interested in curating their own orders</li><li>38% are interested in receiving more than one ‘traditional’ box per month</li><li>Only 25% of brewers use a subscription based delivery service</li></ul><h3>The Designs</h3><p>One of the first things we noticed was the need to update their current logo to a design that is more applicable to smaller sizes. We also cleaned up the distressed look for a more modern feel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JuT8p3NBjTG0x8rQp3raeQ.jpeg" /></figure><p>Our team completed high amounts of domain research and comparative analysis of the beer delivery industry. We made a list of all the design element we liked, and of course what we hated. I refuse to bore you with all the iterations of wireframes we made, so here are just a few of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tBAkfO79L1NtkVCwoVc4dA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zn36QVLQEsSwHG1o4aWzYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ry0HZUAD0pGI7HfjfrVJdQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UYu0pg4ENS8WbGNtU6wP9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sZFuPTgWvKgraLx5LoDP7Q.png" /></figure><p>The final product went through many iterations as well. Here are two of them. The final (for now) on the right went through the minimalist shower and dried off looking fresh and clean and felt very functional. We reached this solution by going through hours and hours of user testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rx4IhWUSXS9GGXme5QYF2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*omLxWjkcXIvFAZSpsBv5Dg.png" /></figure><h3>The User Profile</h3><p>The user profile is one of the major elements that Brew Box was currently lacking. Our surveys and interviews show that people want access to member benefits, they want to track their shipping, and most importantly they want to know more information about the beer they are drinking. We designed the profile to be easily interpreted and highlight the features of being a member. The creation of the profile was geared toward engagement. Now, after users become a member, they have a reason to return and interact more with the site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8YS_U2Y1LQNG-R9qJSSZBA.png" /></figure><h3>The Operations Design</h3><p>Brew Box was lacking in providing the breweries the tools necessary to help them become a partner for distribution. It was simple to see that by providing the breweries with tools to help their business grow, it would result in Brew Box’s business growing as well. So we designed a platform to assist in both businesses cohesively working together. We never took the wireframes past mid-fidelity at this part of the project because we still have massive amounts of research to complete with their backend systems. As you will see, the design is based entirely on function and not style. The buttons are optimized for most thumb sizes, the fonts are clear, the menu is easy to read. We put ourselves in their shoes and imagined what it would be like trying to manage a business on the go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*hab_95sB_vEUyN5ENRjYUg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*DVPlN9QiZSNs2ahFCQcMSw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*1shL0znPbdxpPFHEzj-4wg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*oibiL_WAw0QtO-hUfWuFqw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*2A5plTzH21AgMPf5rsljFw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*sGORI9WgNgwDx9a81QMALQ.png" /></figure><h3>The Box</h3><p>After we redesigned and reframed the site, and created a management platform, we still had another problem we had to tackle. This was the package design. During our contextual inquires, more than half the people commented on the packaging being “mediocre” or “unimpressive”. They wanted something that made them feel like they weren’t just buying a box of beer from the liquor store. Below are the renders of what we imagined the box should look and function like. The box is just another vital piece of the puzzle of a complete end-to-end experience. The first image you will see is what the customer sees when opening the box. After is our redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D0C7pjAR5ebKSWt7iyMmyQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1eqdFH0oRB2WC5gkq0K8Ag.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rfCx_TBfK1kltWe5yWOymg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rclYJPo-hjs_zzm7nPMkHw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UmiPT8PotV3bdWNHEFwHRA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7d4LS5wStY6eOWYZ4qKQLA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*la21QYJcivD6LWY0mvUfWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XmReW87yBse7ljpQ7TJeVQ.png" /></figure><h3>The Ending (and beginning)</h3><p>We presented our findings and designs to Brew Box. To put it simply, they were thrilled with the work completed. We not only hypothetically solved the issue of adding their new store front to the site, but we provided them with a reframing of their overall message. I say ‘hypothetically’ because there is still a lot of testing to be done once the redesign goes live. On top of that, we established the need and design for a platform to connect both brewer and Brew Box to work efficiently and improve each others business. In the last stage, we were able to fill a gap of low satisfaction during the user journey by reimagining how beer could be presented, and redesigning the packaging to complete the end-to-end product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba2454e21688" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-academy/brew-box-a-beer-distribution-company-ba2454e21688">Brew Box — Creating a Two Sided Platform</a> was originally published in <a href="https://medium.com/red-academy">RED Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[eggplant — a platform to shop local]]></title>
            <link>https://medium.com/red-academy/eggplant-a-platform-to-shop-local-6237fda42f83?source=rss-1fdb7283ab98------2</link>
            <guid isPermaLink="false">https://medium.com/p/6237fda42f83</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nicholas Peckham]]></dc:creator>
            <pubDate>Sun, 29 Jan 2017 01:46:33 GMT</pubDate>
            <atom:updated>2017-01-29T03:55:34.223Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Very Beginning</h3><p>“Once up a time there was a kick-ass UX design squad that was tasked with providing a solution to a soon-to-be-dead local market called Kensington Market. The squad had just two weeks to come up with an online platform that would effectively change the world. That’s not true, but they did need to save Kensington.</p><p>The squad would then go on a journey of research, more research, designing, more designing, and a little bit of building. They would build an online platform that evolved from a confined idea, into a liberated one for any small business to use.”</p><p>That was a short excerpt from the critically acclaimed book “How to write a case study in the 3rd person”.</p><p>The following article will describe my experience of what it was like to be tasked with building a web-based platform to help a local collection of different shops, call Kensington Market, protect itself from decreasing sales.</p><h3>The Research Stuff</h3><p>The squad and I jumped right into figuring out why the market was suffering. We started by hitting the streets. We spoke with shop owners. We spoke with customers too. Immediately we started noticing patterns in the answers people were giving us. Shop owners didn’t have time or the technical know how to get started online, and the customers shopping there did so because they lived within walking distance of the market. This insight allowed us to create a survey to send out to people on the Facebook to figure out if people outside of the area were visiting Kensington Market, and most importantly, if they even liked the place. Some key data collected is represented below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*fOVOhvPhzBvdPWDHMWfpEQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*aPzip4KUw12bfm4feNi7aQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*QbI6CbOyOcF6UvyjL5VKlg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Ip0-A7L8c3KUlyDU4Ge1Tw.png" /><figcaption>Of the people surveyed, 80% of them live too far; 91% want delivery; 54% visit the market less than once a month; 88% would try a Kensington online platform.</figcaption></figure><p>Let’s get a better understanding of this data and how it effected our decision making throughout the project. Of the people we sent surveys to:</p><ul><li>80% of people live too far from the market</li><li>80% do not like the overall atmosphere Kensington offers</li><li>If people shopped online 91% prefer deliver over in-store pickup</li><li>54% visit Kensington less than once a month.</li><li>88% said they would try an online platform for Kensington</li></ul><p>After digesting the data, we knew exactly the problems we needed to solve. We also used the data to develop two specific types of users that would be engaging with our product. The two users represented the millennial group who want access to local, inexpensive, and quality groceries that are provided by Kensington Market. Based on this information, we developed version uno(1) of our mission statement.</p><blockquote>Greater accessibility to local groceries.</blockquote><p>The squad went straight to the white board and started shitting out ideas of what was necessary for our product to deliver exactly what our users want. Below are some really exciting action shots of the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X2ikMLSTycgG6Qxawwx5dw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TUtLoDbXjEqRRqe3xz1irQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5Yve3F58168Ghh9LFKX2Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lbONQj1qJvKSBR5acbYKhA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YHkzc04nIJx-4IXGOjaH4A.jpeg" /></figure><p>After using the white board as our brain toilet, we had to take step back and define what exactly it was we were building. While gazing from afar, we all slapped our foreheads. We were missing a bigger opportunity. There was an important question we asked ourselves.</p><blockquote>“Are we building a platform to sell local groceries for a lackluster Toronto market, or a dynamic platform for any business to sell anything online?”</blockquote><p>Have you ever seen the movie Alien? Kensington Market was a host body and one day it’s spine was violently torn open and ‘eggplant’ came crawling out. Not an actual eggplant though. ‘eggplant’ is the name we decided to call our platform.</p><p>This was a major turning point. We realized we created a product that had a much further reach than just Kensington Market. We immediately samurai sworded the word groceries out of our mission statement and proudly created version dos(2) of our mission statement.</p><blockquote>Greater accessibility to local products.</blockquote><p>With clarity, we now knew the purpose of eggplant is to provide any group of small businesses to create a collective and provide a specific area the opportunity to purchase locally produced items and have them delivered directly to the users door. This will create a much larger market for local goods and provide any crafty person the tools to get started with their local business.</p><h3>Building the Design &amp; Stuff</h3><p>After building our sitemap, we emphasized building a product of simplicity. After producing some user flows and use cases, it was fairly simple for us to create some wireframes. Below are some images of mid/kind-of-low fidelity wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6_ZKE36C4IjRZj3eI9F7uA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*36CjFFH-EC7v0RVgnGpKsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fw9ZZBGKdT0y0S_dOhskVg.png" /></figure><h3>“I Fight For the Users”</h3><p>As we built more and more, I personally realized that we were on the path of creating something that was not that unique. Besides the focus on local products, we were building just another online commerce site. There was a recurring question at the forefront of my sexiest organ, my brain.</p><blockquote>How could we keep users engaged while using eggplant?</blockquote><p>I began by thinking about what helps us designers make decisions. The answer was data. We needed to provide data to the user. Once I notified the squad, we set out to create a personal user dashboard. The purpose of this dashboard is tell the users story of purchase history and habits over time. As a user shops, they will have the ability to see in real time what type of impact they are having on both their bank account, and the environment. Below is a high fidelity mockup of how the dashboard might look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zPlGguM5oTO1I3stUVZojA.png" /></figure><h3>The Very End</h3><p>“Using methodical processes, the squad created something much bigger than what they originally set out for. They didn’t save the world. But they did provide Kensington Market a way to dig themselves out of its own grave. Other markets and local businesses came flocking to eggplant to free themselves of steady decline.”</p><p>That was another brilliant book excerpt. It’s also not true. This whole project was produced for a UX design course at Red Academy. The squad are four UX students that worked super hard to develop the fictional function of eggplant. Maybe one day eggplant will not just be a vegetable, but a fully functioning web platform to assist shop owners and customers come together and promote locally made products.</p><p>Now…let’s go buy some eggplant at Walmart.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6237fda42f83" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-academy/eggplant-a-platform-to-shop-local-6237fda42f83">eggplant — a platform to shop local</a> was originally published in <a href="https://medium.com/red-academy">RED Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[re.Intro | a Case Study]]></title>
            <link>https://medium.com/red-academy/re-intro-a-case-study-4ced6172b6d2?source=rss-1fdb7283ab98------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ced6172b6d2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nicholas Peckham]]></dc:creator>
            <pubDate>Sun, 15 Jan 2017 03:57:47 GMT</pubDate>
            <atom:updated>2017-01-16T03:51:59.777Z</atom:updated>
            <content:encoded><![CDATA[<p>A product created from nothing.</p><h3><strong>The Very Beginning</strong></h3><p>What you are about to read is how an inexperienced UX designer gave birth to a mobile application prototype called ‘re.Intro’. The creation of ‘re.Intro’ was developed as a result of taking an accelerated User Experience (UX) design course. The assignment was to pair up with another classmate (the user), and interview them to explore potential mobile application opportunities.</p><p>The opportunity that emerged was a mobile application to assist the user in setting and achieving goals through positive reinforcement.</p><p>The project had a deadline of three days. On the fourth day, the prototype along with deliverables were due, which included:</p><ul><li>User Interview Script</li><li>User Persona / Affinity Diagram</li><li>User Flow</li><li>Storyboard &amp; UI Sketches</li><li>Minimum 5 Screen Clickable Prototype</li><li>5 Minute Presentation</li></ul><h3><strong>LET’S DO SOME RESEARCH!</strong></h3><h3>The User Interview</h3><p>The intention of the user interview was to discover what could be improved in the users daily life. The interview took place in a lounge area of a small school called Red Academy. It lasted fifteen minutes. I bombarded the user with broad questions to get as much information as possible about their life and habits. It was definitely more difficult than I had imagined. It started vague and ended vague. I did film the interview to be able to recall and clarify the user’s answers. Filming the interview would prove very useful later on the design process.</p><h3>The Diagrams and Personas</h3><p>The next step was to categorize the users traits and habits. I did this by producing an affinity diagram using the software Sketch. The diagram allowed me to categorize their characteristics, preferences, likes, and frustrations into a simple to understand overview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*B0beti4oeBCgDJjdBgp_xw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Er_AqbIiaFYGA8VxMcJ1fg.png" /><figcaption>1st and 2nd versions of the Affinity Diagram</figcaption></figure><p>The overview was then translated into a user persona (created with Photoshop). You can see both revisions of the affinity diagram and the user persona include category consolidation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrT2OXRF7QsMNGaTUI4tjA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TrkZq7U-dHS5u57BiWwPbg.jpeg" /><figcaption>1st and 2nd versions of the User Persona. (Pay attention to the consolidation of Interests and Pain Point)</figcaption></figure><p>After rewatching the interview three times and evaluating the user persona repeatedly, I concluded the user’s problems and goals were one in the same. This is when the decision was made to build a product that would assist him with both. Kill two birds with one app (sorry birdies). Below you will see the user’s problems and goals tied together.</p><ul><li>Spend more time with friends.</li><li>Prioritize free time.</li><li>Be more creative.</li><li>Pursue s stable career.</li><li>Monetary gains.</li></ul><h3>LET’S DO SOME PLANNING!</h3><h3>The Sketches</h3><p>Because the user spent so much time interacting with different media streams, the solution was to create an app that would curate a customized feed of media using the users pre-selected media sources. I <strong><em>“assumed”</em></strong> (don’t cringe too much) that any person wanting to achieve goals needed to feel more confident and positive. At this point of the UX process, time would not allow deep research into how a person sets and achieves a goal. This is something I will take with me and improve on while working on new projects.</p><p>To demonstrate the basic function of re.Intro, I created a storyboard to display how the user might feel using the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ss9UxJ9mQw-kEAWSO5Nj0w.jpeg" /><figcaption>If you’d like a limited edition print of my incredible artwork, please contact me directly.</figcaption></figure><p>Once the storyboard was finished, it helped me interpret the flow of how the user might move through the app. I then created some low-fidelity user interface sketches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7IZSylk-rzuR41AK6VSYw.jpeg" /></figure><p>The first version of the UI sketch seen above existed to demonstrate the core purpose re.Intro. I added one more screen to inform the user the purpose of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Y5Z-O3vi9w2pCBiQNWgRQ.jpeg" /></figure><h3>The Flow</h3><p>After seeing the app developing on paper, it was time to create a user flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0tqSDW2e7P412raUxeWtQ.png" /></figure><p>Once version 1 was complete I realized there was an opportunity to create a more focused product. Goals! The app needed to have a step to set goals. Once the user sets goals, the curated content is more specific and more purposeful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gf5cHf49u8wiRao0e_-2ng.png" /></figure><h3>LET’S BUILD A PROTOTYPE!</h3><h3>The Prototype</h3><p>Now that there was a clear purpose, it was time to create a functional prototype! I did this using Adobe Experience Design. The prototype started off as low-fidelity, but being able to utilize the included content in Experience Design, a mixture of a low and mid-fidelity prototype was developed. Four iterations of the prototype were created based solely on my own experience using the app in the process of designing it. Below you will find the some static screens of the fourth iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*3G_agZtBRvIDugRXLiSzug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*gZuW-JLTd-BcQk_tvCsVlA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*GAGwF8RYp4dGnwimdZVk1g.png" /></figure><p>If you would like to view prototype version 4, check it out below:</p><p><a href="https://xd.adobe.com/view/57b1c213-13a8-4643-833f-6989e89ea7b0/">https://xd.adobe.com/view/57b1c213-13a8-4643-833f-6989e89ea7b0/</a></p><h3>The Very Ending</h3><p>The whole process used to create a user centered design (UCD) was eye opening. I found it challenging to not include details in the product that I personally would want to use. I found it really interesting how you can find opportunity just by asking questions. The idea of UCD now makes complete sense. Honestly, I can’t wait to discover more opportunities and create designed solutions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ced6172b6d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-academy/re-intro-a-case-study-4ced6172b6d2">re.Intro | a Case Study</a> was originally published in <a href="https://medium.com/red-academy">RED Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>