<?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 Naaja King on Medium]]></title>
        <description><![CDATA[Stories by Naaja King on Medium]]></description>
        <link>https://medium.com/@naajak?source=rss-293a89626ec5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Hlb3hF9vvrt4Q0gK2y8SYQ.png</url>
            <title>Stories by Naaja King on Medium</title>
            <link>https://medium.com/@naajak?source=rss-293a89626ec5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:05:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@naajak/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[Analytics That Facilitate Executions Throughout the Trading Life Cycle]]></title>
            <link>https://medium.com/@naajak/analytics-that-facilitate-executions-throughout-the-trading-life-cycle-acfbdd91583c?source=rss-293a89626ec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/acfbdd91583c</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[components]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Naaja King]]></dc:creator>
            <pubDate>Sun, 13 Sep 2020 17:44:48 GMT</pubDate>
            <atom:updated>2020-09-14T01:46:23.043Z</atom:updated>
            <content:encoded><![CDATA[<h4>UX Enhancements through Component Refinements</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*esRYMOSEhaFPva-BtSE41Q.png" /></figure><h4>Project Overview</h4><p>The project was to produce an MVP for an analytics portal of a multinational agency brokerage and financial markets technology firm specializing in electronic trading services and products for hedge fund and asset management clients, including tools for pre-trade analysis, trade execution, order management and post-trade evaluation.</p><p>The backend behind the product was complex. Processing large data sets, then filtering on specific attributes and/or then focusing on select data sub sets made keeping process fast a challenge. Every click or un-click resulted in a query to the database. The less clicks required to perform a task and the more efficient the user experience was, the less calls on the back end were made. Reducing unnecessary calls to increase performance is particularly important for a toll that deals with big data. Ultimately increased User Experience could translate directly into increased product performance.</p><p><strong>Challenge:</strong> Provide time saving and efficiency for large volume and frequent transactions within Program Trading.</p><p><strong>Opportunity:</strong> Refine reusable component for faster future development and increased ease of use for the User. Improve task success such as editing applied filters or adding new filters. Save the User time by allowing for customization that remains consistent through separate sessions and across multiple devices.</p><p><strong>Goal:</strong> Support the workflow of editing and viewing many reports in varied progress in order to solve multiple baskets simultaneously. Allow for easy cross filtering of reports using interactive charts and filters throughout the Pre, Intra and Post Trade life cycle.</p><p><strong>My Responsibilities:</strong> Design refinements at the component level enhancements Provide annotated wireframes to aid Developers with the implementation of the designs. Then coordinate with Developers on the execution and visual representation of components within the code environment.</p><h4>Discovery</h4><p>A skeletal version of the portal was in the process of being built. Functionality was continuously being added while the user experience was continuously being enhanced.</p><p><strong>User Feedback </strong><br> Insights were gained through user feedback on wireframes and low fidelity prototypes helped to drive the design. User feedback provided clarity on things such as how User predominantly used filters. Filtering was most often used to reduce a data set. For filters like client or business unit, Users rarely wanted to see all.</p><p>When filtering on other sub sets such as region or country, the User normally filtered down the full data set to see 1 or multiple option. Given that adding single or a few filters out of the full data set were more common than looking at the full data set and excluding a single or a few filters, it made sense for the default state for filters to include all options. Then the User could alter the all state by adding 1 filter option at a time or selecting all and then excluding 1 filter option at a time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*F-rSMZWXicowW2-wZEnHlA.png" /></figure><h4>Define</h4><p>Technical Research for Design Enhancements utilizing Third Party Integrations</p><ul><li>Dockable multi screen, multi window layout management using <em>GoldenLayout</em>. Framework to hold components that allows for row and column arrangement with stacking that enables multiple windows (within the same hierarchy or within sets of hierarchy) to be nested in the same space. Enables pop out windows that allows the User to utilize desktop space with the option to use parts of the portal as standalone widget.</li><li>Utilizing <em>React Split-pane</em> allowed for resizable vertical or horizontal panes with an option to allow for persisting settings.</li><li><em>ag-Grid</em> implementation allows for custom filtering UI and logic. The framework enables lazy-loading, strategically requesting minimal records at a time to conserve critical server resources when the User scrolls, filters or sorts through large data sets. <em>ag-Grid</em> supports real time updates that allow the User to see the most recent and relevant data, as it is available.</li><li>Chromeless browser, <em>OpenFin</em>, runs locally on the desktop and can be customized to make the portal feel like a native app. The snap-and-dock windows enable the User to arrange their screen layout to fit their needs, maximizing desktop real estate. The User can manage and maintain the layout across multiple monitors and allowing the User to recreate the layout when they log in at different locations.</li></ul><h4>Deliver</h4><p>Throughout the Agile workflow, enhancements for the product were implemented through the efforts of the product, design and engineering teams. Communication and expectations management through out the various disciplines was critical. UX artifacts were key in the communication process.</p><p><strong>Iterative Enhancements</strong></p><p>The iterative loop of Agile Design and Development allows for continuous refinement and improvement of the user experience without design being a bottleneck for developers when creating a complex product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*P6jcOJuHGjO3_DnWIJ7czQ.png" /></figure><p><strong>Task Flows</strong></p><p>Task Flows were developed to document the process that a user would go through to complete a common task within the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*1QflqLXoBiaI6IWxh1i1jg.png" /></figure><p><strong>Annotated Wireframes</strong></p><p>The annotations indicated details that are not easily discerned from a static wireframe. This includes functionality, user interactions, and various possible states.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/1*nwQLkgRhRVxF1soY5cxuCQ.png" /></figure><h3>Next Steps</h3><ul><li>Expand subset of internal clients for usability testing</li><li>Expand visual theme options from the current default light theme to include a dark theme execution</li><li>Increase functionality and integration with other tools and systems</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acfbdd91583c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Holistic Assessment Inspires Product Enhancements]]></title>
            <link>https://medium.com/@naajak/https-medium-com-naajak-holistic-assessment-inspires-product-enhancements-11899a6c40?source=rss-293a89626ec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/11899a6c40</guid>
            <category><![CDATA[financial]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Naaja King]]></dc:creator>
            <pubDate>Tue, 16 Jan 2018 20:31:42 GMT</pubDate>
            <atom:updated>2018-01-16T20:31:42.805Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Centralized Workspace to Promote Oversight and Consistency</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B_rJvAOUoUU7M3fr_d2fAw.png" /></figure><h4>Project Overview</h4><p>As part of an evolving standardized ratings strategy, the application was created to allow for a consistent and simplified analytical process. The ultimate vision was an end-to-end work environment that could continue to evolve. The goal was to create a centralized workspace to enhance internal controls by providing greater transparency to allow for easier supervision by managers who are held accountable to regulators as well as the analyst community. Before embarking on next iteration for product, the team took a step back to access the products current performance.</p><p><strong>Challenge: </strong>The overarching hierarchy of the product was based on concepts that were new to the user. This made it particularly difficult to articulate interactions and expectations to the user.</p><p><strong>Opportunity: </strong>Improve user performance by automating mundane tasks allows the user can focus on analyzing the world’s markets, and embedding controls for risk management.</p><p><strong>Goal: </strong>Reduce the risk of compromised ratings by detecting and preventing potential errors earlier in the process. Prompts to the user confirmed that each requirement has been satisfied, allowing the user and their manager to feel confident that they have complied with these key requirements.</p><p><strong>My Responsibilities: </strong>As a member of the four-person User Experience Team, I documented the overarching process, connected the process to user flows and the information architecture or the product. I conducted a heuristic analysis of the product and worked with the Business Analysis’s, Product Owners and Development Team to elaborate on user stories as part of the larger SCRUM team.</p><h4>Deliverables</h4><p>As part of the new release, the team focused on solving some of the usability problems with the previous release. The UX Design deliverables that were created as part of the new solution included:</p><p><strong>Process Flows</strong></p><p>Derived from our analytical policies and procedures, the process flow organizes the key requirements of the ratings process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*VT0trQXpqbx-ejF6-MjpHA.png" /><figcaption>View the full <a href="http://www.naajaking.com/pdf/srp_Process_vs_Project.pdf">Process Flow</a> document</figcaption></figure><p><strong>Information Architecture</strong></p><p>Because the product team experienced personnel turnover through out the lifespan of it’s development, unfortunately a comprehensive road map to the product had not been maintained. As a result, it was necessary to take a comprehensive inventory of the product at its current state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EgbowGgTfkdKLl3pE6u_iA.png" /><figcaption>View the full <a href="http://www.naajaking.com/pdf/srp_Site-Map_Task-Flows.pdf">Site Map and User Flows</a> document</figcaption></figure><p><strong>Heuristic Analysis</strong></p><p>As part of the recommendations document, enhancements would be proposed based on specific feedback found during usability testing and general user interface improvements would be included based on comparing the product against the established usability principals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zetKc6S6-2lnBTRG8UIp7A.png" /><figcaption>View the full <a href="http://www.naajaking.com/pdf/srp_Heuristic_Analysis.pdf">Heuristic Analysis</a> document</figcaption></figure><p><strong>Wire Frames</strong></p><p>Some of the findings from the preliminary usability testing indicated problems such as:</p><ul><li>The functionality was difficult to use because it required back and forth “search-find-click-assign” of the parent to child</li><li>There was not a full, step by step view of the entire case and all its related tasks</li><li>There were navigation pain points of the current systems, such as displaying the supporting contextual information in key areas</li></ul><p>The wireframes served as a road maps were design to demonstrate the details for future product enhancements. They connected the enhancements and new features to the underlying structure of the existing product in order to address the most pressing usability problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TtG8zdE60jvx1acO98ATvw.png" /><figcaption>View the sample <a href="http://www.naajaking.com/pdf/srp_Enhancements.pdf">Wire Frames</a></figcaption></figure><h4>Next Steps</h4><ul><li>Additional Feature Ideation<em><br>The team ideated with the client on enhancements and potential new features.</em></li><li>Develop Additional User Stories for Enhancements<br><em>The new features and enhancements were prioritized based on implementation feasibility, budget, user needs. The recommendations for the next release would include enhancements that were proposed based on the research findings and testing outcomes.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11899a6c40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Almost 40% Increase in Completed Auto Loan Applications]]></title>
            <link>https://medium.com/@naajak/almost-40-increase-in-completed-auto-loan-applications-5fb3b7a2612b?source=rss-293a89626ec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fb3b7a2612b</guid>
            <category><![CDATA[financial]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[auto]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Naaja King]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 20:57:55 GMT</pubDate>
            <atom:updated>2018-01-08T21:33:48.560Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Seamless Application Experience for Mobile Users</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DQL3p0O7slOh_c9nfPxRzg.png" /></figure><h4>Project Overview</h4><p>Industry research has shown that automobile owners are looking to move through the steps of purchasing and financing their vehicles in one place. They are looking to research online financing options, select a vehicle, and determine the purchase price of the vehicle online, prior to visiting the dealership.</p><p><strong>Challenge: </strong>The approach called for offering customers a more seamless buying experience that allows them to shop for and purchase automobiles more efficiently.</p><p><strong>Opportunity: </strong>Based on existing Analytics, a growing number customers were accessing the site on a mobile or tablet devices. It was clear that the old Auto Loan Application that had been adapted from the desktop patterns did not provide an optimized mobile experience. The redesign of the Auto Loan Application to be more mobile friendly also served as an opportunity to enhance the Auto Loan Application process. Shopping features could also be potentially incorporated as a partnership with TrueCar was forged.</p><p><strong>Goal: </strong>Based on the analytics stats of falloff as user moved through the Auto Loan Application funnel, reducing abandoned applications was pivotal. The redesign aimed to set user expectations about the process and next steps in addition to providing faster approvals. Existing Online Banking (OLB) customers accounted for approximately 85% of the auto loan applicants. To serve existing customers and prevent loan defaults due to missed or late payments, the lender offered a discount for using automated direct payments. The new application made it simpler for existing customers to select auto deduct as a payment option.</p><p><strong>My Responsibilities: </strong>As a member of the three-person User Experience Team for the project, I conducted the competitive analysis, designed annotated wireframes and created a prototype for usability testing.</p><h4>Discover</h4><p>The first phase of the project began by gathering business requirements and getting an overview of the common offerings in the auto loan market place.</p><p><strong>Competitive Analysis</strong></p><p>Market place competitors were identified through sources on Morning Star and Forbes. The competitive analysis focused specifically on the auto financing experience, from the auto loan landing pages, including the tools offered and the application itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nC37HU3Suw1GZWvezX20LA.png" /><figcaption>View the full <a href="http://www.naajaking.com/pdf/AutoLoan_Competitive_Analysis.pdf">Competitive Analysis</a></figcaption></figure><h4>Define</h4><p>The research findings were synthesized to narrow down the scope of the project.</p><p><strong>Feature Prioritization</strong></p><p>When prioritizing the features that would be included in the project scope, each proposed feature was evaluated based on its prevalence within the market place (User Expectation), how it aligned with the clients goals for the project (Business Objectives) and whether the feature was an enhancement to existing functionality or had to be developed from scratch (Implementation Feasibility).</p><h4>Develop</h4><p>The next step was to design how the users would interact with the product in order to accomplish the various tasks that were needed to apply for an auto loan.</p><p><strong>Wire Flows</strong></p><p>Wire Flows were developed to document the process that a user would go through to complete a common task within the mobile product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52auyIebEy6kQ4nJfo2uBw.png" /><figcaption>View the full size <a href="http://www.naajaking.com/pdf/auto-loan_wire-flow.pdf">Wire Flow</a></figcaption></figure><p><strong>Usability Testing</strong></p><p>The usability test utilized the production environment coupled with an InVision prototype displayed through UserZoom to walk the users through an unmoderated usability test and present them with contextual questions. Six participants, between the ages of 21 to 65 were recruited through UserZoom. Being a current customer was not a requirement. However, users were screened out if they had not recently applied for an auto loan or were not looking to apply for an auto loan within the next year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TVMNvxspGGbUCq9C8iHIBg.png" /></figure><h4>Deliver</h4><p>Within the time constraints of the project, we were able to deliver a responsive web based application that was mobile friendly and included the priority features to meet user needs and the identified business goals.</p><p><strong>Annotated Wireframes</strong></p><p>Before passing the wireframes along to the development team, annotations were added to indicate functionality, User interactions, and content sources. The annotations followed the format of the corresponding User Stories, displaying the wireframes that corresponded to the scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sGUKOqCcEJ-uPQxmV8rM8Q.png" /><figcaption>View the full size <a href="http://www.naajaking.com/pdf/auto-loan_annotations.pdf">Annotated Wireframe</a> sample.</figcaption></figure><h4>Next Steps</h4><ul><li>Continuing to Measure KPIs<br><em>One of the Key Performance Indicators identified at the start of the project was reducing abandoned applications. The Auto Loan Application redesign was released on a Friday. When the analytics were checked on Monday, it was found that there had been an almost 40% increase in the number of app completes compared to our previous 2 months.</em></li><li>Expand Existing Features<br><em>Some features were implemented in their most basic form as part of the minimal viable product. In future Sprints, these features would be improved and enhanced for upcoming releases.</em></li><li>Increased Functionality<br><em>Some functionality could not be implemented despite the benefit to Users due to time and budget constraints. Additional features would be identified for development in future Epics.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fb3b7a2612b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guided Process for Case Processing and Compliance]]></title>
            <link>https://medium.com/@naajak/https-medium-com-naajak-guided-process-for-case-processing-and-compliance-7a316dd521de?source=rss-293a89626ec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a316dd521de</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Naaja King]]></dc:creator>
            <pubDate>Thu, 28 Sep 2017 19:42:05 GMT</pubDate>
            <atom:updated>2017-09-28T19:43:18.067Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Health Insurance Provider — Claims, Appeals &amp; Grievances</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIvXY_h8B7vdegiuETyeNg.png" /></figure><h4>Project Overview</h4><p>As part of business and technology transformation initiative, the Appeals &amp;Grievances (A&amp;G) department replaced outdated and unsupported component content management system with the more agile and capable PegaRULES Process Commander platform to enable a more efficient Appeals &amp; Grievances process. The new A&amp;G platform was implemented in multiple phases, with each phase enabling complete A&amp;G capabilities with automation aligned with specific organizational lines of business.</p><p><strong>Challenge: </strong>The department was tasked to reduce the labor cost for case processing and administrative managerial cost to oversee operations while maintaining the quality and consistency necessary to avoid of non-compliance penalties.</p><p><strong>Opportunity: </strong>Guided process to standardize and simplify tasks such as Identifying duplicate cases. The new system provided an opportunity for processes improvements such as distributing work more effectively through automation. The new system also allowed the organization to incorporate more analytics and reporting to provide visibility into case data and workload reporting.</p><p><strong>Goal: </strong>A guided process of standardized and repeatable steps for A&amp;G resolutions would begin with gathering and standardizing the most important information at the initial point of contact. The information would be documented in an audit trail would further the organizational goal of focusing on their customer needs by providing the best resolution without the need to rework the case. The guided process would also facilitate the adherence to the strict Service Level Agreement (SLA) necessary for compliance.</p><p><strong>My Responsibilities: </strong>As the UX Lead, I was responsible for guiding the design process from start to finish, As a client liaison I worked closely with the project sponsors and subject matter experts to insure that the user experience met the needs of the various user groups while aligning with the organizational business objective. This ranged from conducting user interviews to producing all design deliverables including: personas, user flows, wireframes, high-fidelity mockups, journey maps, and the style guide</p><h4>Discover</h4><p>The first phase of the project began by interviewing the business stakeholders the identifying the various user groups to interview.</p><p><strong>User Research</strong></p><p>Through our initial interviews with the department stakeholders and business sponsors, we identified 5 distinct groups within the department.</p><p>We interviewed 18 users out of the department of 67 people for a total of almost 24 hours worth of interview footage:</p><ul><li>5 Clerical Users</li><li>4 Managers</li><li>3 Resolution Specialists</li><li>5 Non-Clinical Specialists</li><li>1 Clinical Specialists</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*wumuyz-nXwXTMnII6IW1-A.png" /><figcaption><strong>Contextual Inquiries: </strong>We watched 4 different user groups performing their typical daily tasks, both in person and through screen sharing.</figcaption></figure><p>We found that the Clinical Users had a unique set of needs that were already being met by a third party medical records system. They only used the CCMS system to enter in their final appeal determination, while the other 4 groups used the CCMS system while gathering information from up to four other systems that did not talk to each other. This led us to concentrate our focus primarily on 4 out the 5 groups with the A&amp;G department.</p><p><strong>Process Flows</strong></p><p>The steps taken to complete the processing of a case within the current process were documented. This helped identify areas for improvement within the existing process. The User flows were developed to illustrate how the different user groups accomplish their tasks within the current system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFqKQVM5mE7_9TJ4jy5WMA.png" /></figure><p><strong>Research Findings</strong></p><p>Based on the qualitative data gathered we gained valuable insights into the behaviors and frustrations based on observing the users directly as they performed their daily tasks. We looked at the most common frustration to gain understanding into how the application could make the process more efficient and effective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5iPX2HB6onCB6kVTX7PZ4w.png" /></figure><h4>Define</h4><p>The research findings were synthesized to determine the tasks that were most important in order to accomplish the goal of processing A&amp;G cases quickly while meeting compliance standards.</p><p><strong>Personas</strong></p><p>Our research centered on the 4 out of 5 user types that would be using the application the most. Lean, role-based personas were developed focusing on the user’s function and responsibilities within the department. Since the goals of the user groups were aligned with different stages in the Case Processing life cycle, a case processing life cycle was developed to map the user goals against. Basic demographic information such as years of experience and work location/environment was included to provide insights into the needs of each group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*pEH2tk9Ez8Y0vte7IYSGSg.png" /></figure><p><strong>Feature Prioritization</strong></p><p>The personas helped to uncover universal used features and functionality, as well as aid the evaluation of new ideas. Those insights were important in determining which features made the most sense to recommend for implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*gZBL1z4QduY3GWsI9lF2lg.png" /></figure><h4>Develop</h4><p>We made a plan for how we could make the application user friendly while retaining the depth of information needed at various points in the process.</p><p><strong>Design Enhancements</strong></p><p>Depending on the case, a user might need to see only the most recent data or historical data sometimes going back multiple years. A strong focus on the visual hierarchy and placement of data and tools was important so that they user had access to multiple layers of data when it was required without cluttering the screen when it was not necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Onc9ZlKzVUkHMfHNPucotw.png" /></figure><h4>Deliver</h4><p>We were able to streamline the A&amp;C case process while guiding the user through their tasks with structured forms, context specific searches, and reminders within a persistent workflow structure.</p><p><strong>Annotated Wireframes</strong></p><p>The annotations indicate details that are not easily discerned from a static wireframe. This includes functionality, user interactions, and explanations of the content. The goal was to communicate to business analyst, developers and client the value of the design in the context of the bigger picture of how the application would contribute towards established KPIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pf4D7bdA8jcqMlCjgUkndA.png" /></figure><p><strong>Style Guide</strong></p><p>The style guide is a “living document” to promote reusability for the current and future applications that catalogs of all the repeating visual patterns in order to maintain visual consistency. Designers and developer were able to save time by using the style guide as a reference instead of starting from scratch each time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*hxhxAVpzeaNN3LkSio7i7Q.png" /></figure><h4>Next Steps</h4><ul><li>Conduct Usability Testing on the application once it’s released<br> <em>Gather insights on learnability, memorability, errors and satisfaction</em></li><li>Include responsive layouts for other sizes for future technologies<br><em>The initial application was developed specifically for the 1366x768 screen resolution size, based on the standard monitors for the office and company distributed laptops</em></li><li>Increased Functionality<br><em>Some features were not implemented despite the benefit to Users due to time and budget constraints. In the future, those features could be re-visited</em></li><li>Increased Integration<br><em>The first release was scoped to include integration with 2 existing portals, 4 system integrations. Additional medical records system integration would allow Clinical Users to migrate to the new application.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a316dd521de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make It Clear, Fast & Easy]]></title>
            <link>https://medium.com/@naajak/make-it-clear-fast-easy-4ccf116d1a16?source=rss-293a89626ec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ccf116d1a16</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[point-of-sale]]></category>
            <dc:creator><![CDATA[Naaja King]]></dc:creator>
            <pubDate>Sun, 23 Aug 2015 04:12:40 GMT</pubDate>
            <atom:updated>2017-09-28T19:43:48.182Z</atom:updated>
            <content:encoded><![CDATA[<h4>A New Start for a Windows-based Desktop Application</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R7eK_Jk--LRVL6KMpr1Bcw.png" /></figure><h4>Project Overview</h4><p>CellSmart POS was designed by store owners and users appreciate how “closely it matches the day-to-day activities of a cellphone stores.” The customer base has grown to +1,000 stores primarily through word of mouth.</p><p><strong>Challenge: </strong>The company needed to create a simple and user friendly product for the next version released. The point of the highest customer cancelations happened within 30 days of installing the product. The most common reason customers gave was the steep learning curve.</p><p><strong>Opportunity: </strong>CellSmart plans to convert from a desktop-based application to a browser-based application with their next release.</p><p><strong>Goal: </strong>Adapt the feature rich POS system to the browser-based environment while making the product more intuitive to shorten the learning curve for new customers.</p><p><strong>My Responsibilities: </strong>As part of a 3 person team with a UX Researcher and an Interaction Designer, my role was UI Designer. I created the visual look &amp; feel for the user interface. I also served as the primary point of contact with the client, facilitated meetings, scheduled contextual interviews &amp; on-site usability testing. We all collaborated on user interviews, crafting personas, sketching options for how to improve the task flows, usability testing, creating the final high fidelity interactive prototype and we compiled all of our work into final recommendations documentation.</p><h4>Discover</h4><p>The project began with the research.</p><p><strong>Competitive Research &amp; Analysis</strong></p><p>We looked at 8 potential competitors, then narrowed the list down to 3 companies who operated within the same Mom &amp; Pop local Cellular Store market as CellSmartPOS. CellSmartPOS was the clear leader in terms of features and functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*AbE4roQ9EjMd1WvotxZUJA.png" /></figure><p><strong>Research Findings</strong></p><p>We found that store owners and managers did not always rely exclusively on CellSmart POS to track their products &amp; inventory. The reasons that was cited was the steep learning curve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YBV1IsAB04KnQyxXKaXzHQ.png" /><figcaption><strong>Contextual Inquiries: </strong>We visited 4 different stores to learn how a typical mom-and-pop cellular store operates.</figcaption></figure><p>When we spoke with the Help Desk manager, we found that adding &amp; deleting inventory is one of the top three reasons customers contact tech support. The other top two issues were outside of our scope since they did not involve the User Interface (printer support and slow connection).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*eQth0UrvhBSpOVHQ2Q4jgw.png" /></figure><p>The owners and managers that we interviewed told us that 80% of all in-store transactions were customers paying their monthly pre-paid bills in cash. Since the vast majority of these customers paid their bill at the same location every month, the basic information for these customers was already recorded in the system.</p><p><strong>Usability Testing: The Desktop Version</strong></p><p>When we walk through the system with users, we found that the critical call-to-action buttons were difficult to find.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_hEZYRcdhP3v3NtsWiyAg.png" /><figcaption>Screenshots from the desktop version for paying a bill, the home page dashboard, new product.</figcaption></figure><p>User with <strong>Minimal POS experience:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/306/1*9pbkCiypd5362C9wgVGsMw.png" /></figure><ul><li>3.5 mins to complete bill payment process</li><li>Found it difficult to navigate back to the dashboard</li><li>Disoriented by the excessive amount of buttons and tabs</li></ul><p>User with <strong>Significant POS experience:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/308/1*kLz9YLMIxYJaywVeLaj0EQ.png" /></figure><ul><li>1:29 mins to complete bill payment process</li><li>Was overwhelmed by the amount of information on the screen</li><li>Found some buttons misleading or confusing</li></ul><h4><strong>Define</strong></h4><p>The next step was to synthesis our findings to determine what was most important to the user, and what was most relevant to the business goals, such as reducing customer calls to tech support.</p><p><strong>Personas</strong></p><p>Based on our research, we saw three distinct types of users emerge. We crafted personas to represent users who had similar behaviors and goals:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*6Q5IobP8G3lfUQZuWPGpAg.png" /></figure><p><strong>Feature Prioritization</strong></p><p>We determined which features to focus on based on the expected frequency of use and their alignment with business goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*-pjbX2TtA08RSqd9er5T6A.png" /></figure><h4><strong>Develop</strong></h4><p>We made a plan for how we could make the product more user friendly.</p><p>Our first recommendation was to condense and simplify the navigational information architecture. We proposed condensing the secondary navigation to 23 subcategories to alleviate confusion and allow the user to rely more on recognition instead of requiring them to commit 42 subcategories to memory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6BG2APlsj-D2iNhG01atrw.png" /></figure><p>We sketched out possible layout solutions for the Home Page Dashboard, the Bill Payment screens and how to combine the Inventory processes with the Product lists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*A3wzjT8-QB67cDb6UtrmHA.png" /></figure><h4><strong>Deliver</strong></h4><p>We were able to streamline the Payment Process workflow. Decreasing it by 8–10 clicks/actions <em>(depending on whether the user was already in the system or not)</em>, and by 4 pages/pop-ups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p0X8IM-9sznwm9szOq8lPw.png" /><figcaption>The light blue actions and pages indicate steps that were combined or eliminated in the process.</figcaption></figure><p>We tested our sketches with users, incorporated their feedback, then created basic wireframes. We then tested the wireframes with users, some with basic POS experience and some without any POS experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*dihon609qyT-ZkN6984GVg.png" /><figcaption>User did not see the calls to action for printing the receipt when they were placed under the receipt. They were looking for the calls to action in their activity area in the center of the page.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*5Vv9JRwq9YeamoHCKzEkGA.png" /><figcaption>Users did find the space to enter the confirmation number. More visual emphasis was placed on the call to action and the title of the field was changed to include multiple verbiage used on multiple external carrier payment portals.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*nz2tbklmzTM6qT57gvMFlQ.png" /><figcaption>An additional button to add multiple unique IMEI numbers for products that require individual numeric identifiers, while using the same product descriptions.</figcaption></figure><p><strong>Download the </strong><a href="http://www.naajaking.com/pdf/cellsmartpos_iterations.pdf"><strong>Iterations</strong></a><strong> to see the findings and the resulting features.</strong></p><p>We addressed the stumbling blocks that users encountered and moved to an interactive prototype.</p><p><strong>Download the </strong><a href="http://www.naajaking.com/pdf/cellsmartpos-annotated_wireframes.pdf"><strong>Annotated Wireframes</strong></a><strong> with Use Cases and User Stories.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*ruTb3-qqvbNHckpbWkj_1Q.png" /></figure><p><strong>You can also try the </strong><a href="http://k0rmad.axshare.com/#c=2"><strong>Interactive Prototype</strong></a><strong> for the upcoming proposed browser-based version of CellSmartPOS.</strong></p><h4>Next Steps</h4><ul><li>Further usability testing with additional users<br><em>Conduct usability tests on additional features and user flows once designed</em></li><li>Consider which types of data can be accessed by all users vs. which should be limited to specific users and/ or locations<br><em>This is an option that will be more feasible to explore once the browser based system is deployed</em></li><li>Explore different options for responsive layout<br><em>Conduct user research to identify needs specific to mobile platform</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ccf116d1a16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Combining Gaming, Social Interaction &
Physical Fitness]]></title>
            <link>https://medium.com/@naajak/wii-move-combining-gaming-social-interaction-physical-fitness-8c102bd4fc96?source=rss-293a89626ec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c102bd4fc96</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[apple-watch]]></category>
            <category><![CDATA[gamification]]></category>
            <dc:creator><![CDATA[Naaja King]]></dc:creator>
            <pubDate>Sun, 23 Aug 2015 00:20:55 GMT</pubDate>
            <atom:updated>2018-01-08T19:05:21.903Z</atom:updated>
            <content:encoded><![CDATA[<h4>An Apple Watch app that combines Nintendo’s most popular console games with the physical engagement of their Wii Fit U.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9UvjBIWKsUiZ-Y__UJT4Q.png" /></figure><h4>Project Overview</h4><p>The Nintendo brand personality is known for being fun; their tagline is “Putting Smiles of the Faces of Everyone Nintendo Touches”. As part of the User Experience Design Immersive, our 2 person team focused our project on finding areas of opportunity for this iconic brand. We proposed expanding the gaming opportunities for existing Nintendo users to promote the characters and games to those who are not already existing fans.</p><p><strong>Challenge: </strong>Most fitness apps fail to help people enjoy exercising. Users lose interest in the apps. The lack of motivation can lead to problems associated with inactivity and weight gain.</p><p><strong>Opportunity: </strong>Nintendo prides itself on producing products that impacts their consumers positively, making the brand perfectly positioned to expand their reach by developing their first app with a focus on motivating people to stay physically active. The social element would empower existing fans to easily promote the Nintendo brand to their friends. The rewards feature would also be a potential for the company to establish partnerships with non-competing retailers and service providers.</p><p><strong>Goal: </strong>Integrating game-like features for an app for iPhone and Apple Watch so users will be inspired to participate in more physical activities that allow them to interact with friends and others in the Nintendo community through interactive physical challenges. The app would be positioned to attract existing fans and new players through popular games and social media sharing in the app.</p><p><strong>My Responsibilities: </strong>We both worked on each aspect of the project. Collaboratively we drafted a proposal, conducted comparative analysis &amp; user research, ideated features, sketched User Interface options, conducted usability testing, creating low-fidelity wireframes, refining the interface and created medium &amp; high fidelity interactive prototypes <em>(I created the final high-fidelity prototype)</em>.</p><h4><strong>Research Summary</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*z450Zhv9F20f9JaZHqAgcw.png" /></figure><p>The Apple Watch is a prime opportunity for the brand to push the exercise focus by taking the user outdoors with real life experiences. The Apple Watch allows for the expansion the functionality of Nintendo Wii U remote with the heart rate sensor, and calorie-burning measurements.</p><p>This is a great opportunity to launch Nintendo’s first app utilizing the new technology of this cutting edge platform.</p><p><strong>Competitive / Comparative Analysis</strong></p><p>We compared 4 different Fitness apps, including Zombie Run! which has a gaming element incorporated into it. We listed the features that each app contained. We tracked 10 different features and then narrowed our focus to<br>5 primary features:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*wwY3UC3HmFCRjUa4k8TRSw.png" /></figure><p>In order to get an idea of how users felt about the competition, we asked a sample group to try them out. The users were asked to complete basic tasks within the apps; selecting a workout and then finding their personal stats. We found that the apps had between 9–7 pages, and 7–8 clicks. With the exception of the Nike training app, which had the most complicated interface, requiring the user to go to 14 pages and 13 clicks. The features that users found helpful or convenient were also noted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*2980KKDQTuePRhCKltFQbw.png" /></figure><p><strong>User Research</strong></p><p>We sent out an initial survey and received 55 responses. We found that:<br>The average Fitness App user who is also interested in Gaming is between 25 to 35 years old. They work out or engage in physical activities Often. Final Fantasy, Legend of Zelda and Pokemon (Nintendo games) are among the most popular. The majority of them have iPhones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*JQRZPCjNm_YMkQU7Ulwv-w.png" /></figure><p>We initially thought that our target audience would be more interested in gaming than working out. We were surprised to find that not only did the largest group work out or engage in physical activity often, but the second to largest group worked out very often.</p><p>We conducted user interviews and gained valuable feedback include:</p><p><strong>Users were incentivized by rewards…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*t8xmTn2-Xvt-AX8ioT4fmw.png" /></figure><p><em>I used to use Oscar &amp; Misfit because my insurance company sent it to me<br>and I got Amazon dollars for using them.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*wBb6SWIxqM1UU1Yaqk2_9A.png" /></figure><p><strong>Users used games to connect with family &amp; friends…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*t8xmTn2-Xvt-AX8ioT4fmw.png" /></figure><p><em>I like getting nudges from my Dad through Words with Friends.<br>But if I only got alerts from the game I would find it annoying.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*wBb6SWIxqM1UU1Yaqk2_9A.png" /></figure><p><strong>Users enjoyed incorporating their physical actives<br>with their social time…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*t8xmTn2-Xvt-AX8ioT4fmw.png" /></figure><p><em>I like to organize hiking trips with my friends.<br>These are the same people that I drink martinis with. I like the fact that we get to hang out and doing something healthy at the same time.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*wBb6SWIxqM1UU1Yaqk2_9A.png" /></figure><p><strong>Technical Research</strong></p><p>In order to conform to the standards of the Apple Watch, we researched the platforms capabilities…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*MISMqf8k5DKzXdu_ib7xuQ.png" /></figure><p><strong>Analysis &amp; Synthesis</strong></p><p>We laid out our findings into an Affinity Map and plotted the feedback into 4 categories: • Pains • Pleasures • Context • Behaviors</p><p>Based on that feedback, we thought of features that might address the needs expressed by users:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*CVZ6xGfl-1Os1gbus4cHKA.png" /></figure><p>Based on the results that we gathered, we saw three distinct types of users emerge. We crafted personas to represent users who had similar behaviors and goals:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*-xXKeMQA4Pt2bs3saSbcKw.png" /></figure><p><strong>Design</strong></p><p>We sketched out the initial screens and took the solutions that worked the best with the limited real-estate of the Apple Watch screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zUyCkYzEwvWcTwybv7467g.png" /></figure><p>We conducted 3 usability tests on a low fidelity paper prototype of the sketches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8T-wICbs_EuY1SsbMzSTjg.png" /></figure><p>Based on user feedback, we incorporated Apple Watch specific behaviors &amp; functionality, such as the progression to long glance from short glance, and synching data from the existing health app options.</p><p>We then conducted 3 usability tests on a medium fidelity paper prototype of the screens of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h8pFuPDw9Wqkyui-skchYA.png" /></figure><p>We incorporated the feedback and conducted 3 usability tests on a medium fidelity paper prototype of the screens of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BG5dKFpPflXTpa1lFDupeQ.png" /></figure><p>Based on the feedback that we received, we added more competitive elements, such as seeing where you were ranked among the other players. As we proceeded to the final interactive prototype, we added more game themed elements, like animated characters, and additional notifications with game themed message.</p><p><strong>Download the deck of </strong><a href="http://www.naajaking.com/pdf/wiimove-annotated-wireframes.pdf"><strong>Annotated Wireframes</strong></a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_saB-7Co_3rqcSFQBnpZdQ.png" /></figure><p><strong>You can also try the </strong><a href="https://dl.dropboxusercontent.com/spa/8n3q1mfyqagk1rr/Exports/42mm_watch_wii-move/42mm_watch_wii-move.html"><strong>Interactive Prototype</strong></a><strong>.</strong></p><h4><strong>Next Steps</strong></h4><ul><li>More game theme options based on other Nintendo games<br><em>(Such as Legend of Zelda, Final Fantasy, and others)</em></li><li>More types of physical elements<br><em>(Jumping, squats, shadow boxing, etc.)</em></li><li>Create the remaining screens &amp; function for the Apple Watch app<br><em>(Calendar, invite friends, solo player games)</em></li><li>Fully functional Mobile App<br><em>(Research, define and design)</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c102bd4fc96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expanding Impact for Social Good]]></title>
            <link>https://medium.com/@naajak/expanding-impact-for-social-good-6033a73bf78c?source=rss-293a89626ec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/6033a73bf78c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[donations]]></category>
            <dc:creator><![CDATA[Naaja King]]></dc:creator>
            <pubDate>Fri, 21 Aug 2015 01:05:07 GMT</pubDate>
            <atom:updated>2017-09-28T19:44:18.501Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introducing individual-to-organization transfers in a peer-to-peer payment app</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*5VxaIOYtua2Va5WWvUkEDw.png" /></figure><h4>Project Overview</h4><p>As part of the User Experience Design Immersive, the objective of this group project was to integrate a new feature into the established structure of an existing product. The group consisted of 3 User Experience Designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*t8xmTn2-Xvt-AX8ioT4fmw.png" /></figure><p><em>Venmo’s mission is to connect the world and empower people through payments. Empowerment happens when we recognize that money is a tool we can use to help others: sending money to a family member down on his luck, helping fund a friend’s new art project, or donating to a charity.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*wBb6SWIxqM1UU1Yaqk2_9A.png" /></figure><p><em>Source The </em><a href="http://blog.venmo.com/hf2t3h4x98p5e13z82pl8j66ngcmry/2014/1/2/givedirectly-on-venmo"><em>Official Venmo Blog</em></a></p><p><strong>Opportunity: </strong>Strengthen the Venmo brand by offering options for users to donate money through the app to causes they care about.</p><p><strong>Challenge: </strong>Integrating individual-to-organization transfers into an existing peer-to-peer payment app in a way that meets the needs of existing Venmo users.</p><p><strong>Solution: </strong>Create profile pages for nonprofits and separate pages for their campaigns, seamlessly integrate the new feature into the existing functionality, and encourage easy giving through the Venmo social feed.</p><p><strong>My Responsibilities: </strong>Researching online fundraising services , conducting user interviews, collaborating to prioritize features, sketching User Interface options, drafting an App Map, creating low-fidelity wireframes, refining the wireframes and putting them into an interactive prototype.</p><h4>Process</h4><p>We followed the “Double Diamond” project cycle. Starting with our original problem statement, we conducted research to explore the opportunities within the market place that Venmo operates in. Then we used the insights that we gathered to define who the current Venmo user is and the potential users that might find the option to donate through Venmo appealing. We tried out multiple options for how these new features might be incorporated into the existing app. Then we narrowed done those options to find the most optimum solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*oxj54ytejjziC7Nl9PS20A.png" /></figure><h4>Discover</h4><p><strong>Competitive Research &amp; Analysis</strong></p><p>Venmo holds a unique position, since it has no direct competition. There are other peer-to-peer payment apps, and other payment options. However, none of them incorporate the social component that makes Venmo special.</p><p>There are Donation apps that many users currently use to send funds to nonprofits and crowd rising campaigns. However, their payment process is not as fast and easy as the payment process that Venmo is famous for.</p><p>There are also Donation Service Site that facilitates fundraising for nonprofits and crowdsourcing projects. Although the service sites generally provide a content management system that allows fundraisers to add a wide variety of content, fundraisers must promote their fundraising page through other channels. They can share their fundraising pages through social media, through their existing donor base, through advertising or other marketing efforts. The service sites allow for searching, but a user must actively initiate the donation process.</p><p><strong>User Research</strong></p><p>We created an initial screener survey. We sifted through the responses to find those who fit the description of our target users. We were specifically looking to find people who fit into 3 user groups:</p><ul><li>Venmo users</li><li>Online donors</li><li>Venmo users who donate online</li></ul><p>We then we reached out to those respondents to gain further insights into their goals, behaviors, pleasure points and pain points.</p><p>We then followed up with 17 of our target users:</p><ul><li>5 = Email surveys</li><li>2 = Phone interviews</li><li>10 = In-person interviews</li></ul><h4>Define</h4><p><strong>Synthesis</strong></p><p>We laid out the findings from our User Research into an Affinity Map…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/233/1*HO1-C4HP3Z2b22ZnjAvxag.png" /></figure><p>We plotted the feedback into 3 categories:<br>• Motivation<br>• Importance<br>• Context</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*f3R6dNLv8UNovYlyw09pFA.png" /></figure><p>Two repeating themes emerged:<br>• Relationships<br>• Trust</p><p><strong>Personas</strong></p><p>We crafted personas based on our research to represent users who had similar behaviors and goals. Based on the results that we gathered, we saw three distinct types of users emerge:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*QEoORE0t4_1uJFB1L93X-w.png" /></figure><p><strong>Feature Prioritization</strong></p><p>We determined which features to focus on based on how well they aligned with the goals of our target users and how viable they might be to implement into the existing Venmo structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*vgBSkRILP8CifPO1DPfbuA.png" /></figure><p>Given the social nature of Venmo, the best way to promote the charities would be to show users the donations that other users made through their news feed. We determined the most seamless way to allow users to search for charities would be to integrate them into the existing search functionality.</p><p><strong>Journey Map</strong></p><p>We crafted a journey map to plot the context that the various users typically interact with the app. Based on out interviews, user who currently used Venmo did not have many pain points with the existing app. We focused on when each type of user might interacted with the app for social reasons or entertainment purposes in addition to performing their actual transactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*sM3ULI8QvHB77vm_Mf3yZA.png" /></figure><h4>Develop</h4><p><strong>Possible Task Flow</strong></p><p>We plotted out an App Map to get an overview of how users can transfer funds to an organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z21xPIw40Fk4AkfW0QtsHQ.png" /><figcaption>This is the final App Map with the task flow revisions incorporated.</figcaption></figure><p><strong>Design</strong></p><p>We conducted design studios to sketch out multiple options for how to incorporate the donations option into the Venmo payment process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8n26lBK0PpaP5hH3zhjmKA.jpeg" /></figure><p>Afterwards we made the most successful ideas into wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*TEfHIzP79nAPhxyKfQ2-Qg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*4PKlzoQbiBZrHRPqDaleOA.png" /></figure><h4>Deliver</h4><p>We took the solutions that appealed to us from our sketches and used them as a starting point for our wire frames.</p><p><strong>User Testing &amp; Iterating</strong></p><p>We conducted usability tests on 8 users with low fidelity paper wireframes, and on 9 users with a high fidelity interactive prototype.</p><p>The purpose of the tests were to explore:</p><ul><li>How findable and usable our donation feature is to users</li><li>How this feature integrates into the existing user flow</li></ul><p>We asked users to perform the following tasks:</p><ul><li>Discover specific causes within the news feed</li><li>Search for a nonprofit</li><li>View information about that organization</li><li>Make a donation</li></ul><p>We iterated our solution based on the feedback that we received on our low fidelity paper wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qywmrIL7HNJZHFfdx5f6PA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9TlBBDTcFbgw6szknWocw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxAfVQweHkxZWozfbNlvJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XDisKxB0ZxC_hHpN18Husw.png" /></figure><p>The refined solutions were then tested in our <a href="http://invis.io/AS3IWGSJX"><strong>medium fidelity interactive prototype</strong></a>.</p><h4>Next Steps</h4><ul><li>Additional user research:</li></ul><p><em>-- What motivates users to donate spontaneously?</em></p><p><em>-- How are users influenced by their friends’ posts?</em></p><p><em>-- What other information do users consider before selecting a cause?</em></p><ul><li>Include Charity Navigator ratings</li><li>Option to donate within Transfer to Bank process</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6033a73bf78c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>