1. Dartmouth Drupal-based CMS and Repo System High Fidelity Prototype
Client: Dartmouth College
Role: Designer, Developer
This high fidelity prototype was created for formative testing of Dartmouth College’s ambitious plan to migrate their back-end administration system for dozens of affiliated websites from an OmniUpdate to a Drupal 7 framework, while at the same time providing their editors access to a shared content repository. Working as the UX and UI lead for the new system, the Axure RP prototype I created went through several on-site user tests moderated by myself (see below - the test script can be used to navigate through the prototype). It received high marks from a sample set of users for its ease of use and its intuitiveness.
2. Moderated and Remote Usability Testing
Role: Test Designer, Moderator
The Dartmouth test design was a formative/diagnostic test using a within-subjects design. Testing of 5 users fitting our profile target took place on-site at Dartmouth College within the space of one day. Following a brief introduction, the tests began with general questions about how site editors currently perform routine site admin duties and about their work environment. After that, a series of 6 tasks was set before each of the users. Tasks were usually divided into a series of smaller tasks. Each task (set down in writing) described a particular work scenario that a site editor would likely find herself in at any given time during her workday. After the user read the written task and acknowledged that they had understood what has being asked of them, recording using ScreenFlow was started and they were told to begin. We asked and encouraged participants to think aloud while performing these tasks, then asked a number of follow up questions for each task and on the experience as a whole.
Other projects required lab-based testing in a controlled environment using Morae Recorder, Observer and Manager to document the testing, with participants and moderator in the usability lab and observers and visitors monitoring from an adjacent room. Tests or surveys requiring a larger or more specialized screened population sample would call for dedicated third-party solutions for desktop and mobile testing, such as UserZoom, UserTesting.com and Optimal Workshop.
3. Low-fidelity Prototypes and Wireframes
Role: Designer, Developer
Using tools like Axure RP, Balsamiq and OmniGraffle to create dynamic interactive prototypes had helped us pre-visualize and plan out the effectiveness and usability of any proposed layout for desktop user interfaces by getting the design approach in front of the users and stakeholders before going to code. All three programs do a great job of simulating the same kind of front-end and client-side functionality found on most 'real' websites, with comparatively little effort.
4. Mobile Application and Mobile Responsive Prototypes
Role: Designer, Developer
Axure also served as a powerful tool for planning mobile applications, providing features that support swipe/pinch gestures, and mobile responsive sites supporting adaptive layouts on differently sized viewports. Shown below are some recent projects used as guides for native iOS apps and mobile responsive pages for Blue Cross Blue Shield.
5. Personas and User Scenario Documents
The creation of personas was often necessary when planning the user experience design of any given project. Typical personas would be hypothesized after market-segmented survey data was gathered and analyzed, or recorded directly through user interviews. Complete demographic data and user scenarios, describing how any given set of users would interface with an existing system, would be taken into account when designing a solution. This science was applied both to the consumer facing applications and websites our clients would have us create for their audience (such as the Veramyst Allergy Watcher BDA shown here) as well as to our MessageMaker CMS and reporting system that our clients would employ to publish content and gather metric data.
In the case of the Aegon/TransAmerica LifeStage Advisor, such formulated demographic buckets were critical in helping to develop the system logic necessary to produce the most appropriate insurance product recommendations based on both inputed demographic and lifestyle data. The document shown here is a test script used to confirm that logic was correct.
6. Other Documentation: Test Scripts, Functional Spec Documents, User Tutorials
Role: Designer, Co-developer
Many other kinds of documentation were required for projects dealing with a great deal of customized features.
Aegon Test Script: Aegon/TransAmerica's
goal was to guide casual consumers to different insurance recommendations
based on demographic data entered by the user, along
with yes or no answers to several
Part of my job
here was to test the widget logic
for several campaigns constructed in XML using this script as a guide, very time consuming
and intricate work.
City University of New York (CUNY) Functional Spec Document: On many occassions, functional specifications were gathered during the initial discovery process. For CUNY, using the annotated wireframe buildout of the page templates as a guide, a Word document was exported from Axure with notations explicitly called out for our developers to go by.
Liberty Mutual Facebook App User Tutorial: Complex projects which would call for clients to use One To One Interactive's MessageMaker CMS platform would often call for additional training and tutorial materials to be produced as a collaboration between OTOLabs and the client's internal communication teams. For Liberty Mutual, this deck was created to bring Facebook business page managers up to speed on how to assign subscription feeds to each LM rep's Facebook Wall (now known as the News Feed).
7. System and Task Flows
Complex projects usually called for a flow diagram, visualizing possible user interactions throughout the project on the client side or internal processes and calls for data between the client and the server side, or both. Most of these early diagrams were created in MS Visio, but as time went on, I found Axure to do a very good job visualizing conditional logic and allowing it to be shared easily.
8. Quality Assurance and Testing
Client: Spaulding Rehab
Role: QA Lead
Hot on the heels of the four
re-vamped Partners HealthCare
sites was this effort to upgrade
certain page templates within the
primary Spaulding Rehabilitation
Network website, including the
homepage and most section landing
and subpages for the most
In addition to extensive site-wide
cross-browser and device render
testing, a great deal of QA attention
was focused on the newly integrated
facility and service locator
functionality incorporating Google
Dozens of test cases were applied to
these very prominent finder forms
to ensure the accuracy and precision
of the logic that determined
the location results of all facilities,
services or physicians that fell
within a choice of radius from any
given ZIP code.
9. MessageMaker Platform Product Development
Client: One To One Interactive
Role: Designer, Co-developer, Usability Lead
The MessageMaker (formerly PolyThink) platform was a customized, proprietary webservice developed by One To One Interactive's Labs division. The Labs division was responsible for innovating digital marketing solutions beyond traditional web development. These solutions included installed applications, mobile apps, desktop widgets and social spaces. The MessageMaker Platform was an integrated suite of products composed of a content management and publication system, an application deployment and sharing system, a CRM and e-mail delivery system, a social media curation and reputation management system, and an analytics and metric reporting system for apps, e-mail and social.
As part of the MessageMaker product development team, and as the Interactive Project Manager of the Labs division, it fell on me to work closely with our clients, as current and potential users of our platform, to optimize the user experience and integrate new product features needed for any content endpoint served from and reporting back to the platform. I would then translate the client's needs and business goals into actionable development items for the review of the product dev team and act as an agent for the user's interests - reconciling their needs with the development team's strategic goals for the product.
In addition to these responsibilities, it was also common to find myself constructing and customizing any given project's configuration, channel and content feed structure through the CMS platform.
One To One Interactive