Client: (Confidential)
Project Duration: 1.5 months
Team: 1 UX Design Lead (My Role), 1 UX Designer
Project Team: 1 Software Architect, 1 Product Manager
Goal: To create an enterprise mobile app for service team and installers authorized to maintain and add new shading devices within a Commercial Building.
UX Process: Stakeholder interviews, user flow mapping, wireframe design iterations
UX consulting work for an IT agency to create a web app to be used by the internal recruiting team.
Client: Infosys
Project Duration: 1 month
Team: 3 Software Developers, 1 UX Designer
Goal: To create an enterprise web app for internal HR recruiters and incoming Software Development Associates, which will be used during the applicant interview process.
UX Process: User testing and stakeholder interviews, prototype design using Material Design-React UI components.
The ITP help page supports 200+ students of NYU Tisch-ITP. This project is where I started incorporating accessibility in my UX practice. It has sparked my curiosity for inclusive design, and helped me gain subject matter expertise on WCAG 2.0 Web Accessibility standards.
Web accessibility simply means “an inclusive practice of ensuring there are no barriers that prevent access to websites by people of all types of abilities.” You can read more about WCAG or Web Content Accessibility Guidelines here.
I broke down a quick overview on how we tackled the project in the first 12 weeks, where our team went from learning about WCAG, redesigning for accessibility and teaching content managers how to be inclusive in their content creation process.
Before we can revamp the site to meet WCAG standards, there were many requirements to consider:
During my preliminary user interviews, I have heard many origin stories, some quick glances to how certain pages came about, (ITP is turning 40 this year!) and helpful insights from both admin users and the students.
What I’ve been hearing from the administrator’s side:
“We built this page so our e-mails to students would somehow live in a landing page.”
“The pages were born out of student’s needs and then it became unwieldy, or obsolete as most communications happen in the e-mails.”
“My workflow relies heavily on recreating last year’s pages, and keeping old recent versions accessible for reuse.”
What the students say:
“Iconography would help a lot in easily identifying content.”
“I would search Office Hours by google-ing. It’s faster that way.”
The team started with a simple survey to understand usage of the site.
I have created a pre- web redesign survey to identify features that would need focus in the redesign and the student questionnaire results.
At this point, the team was able to attend an hour workshop to understand the basics of digital accessibility. Teach Access has a good basic tutorial on building accessible sites.
Some of the notes that stood out for me:
Using the current site map, the following were the steps we took:
Our team spent 2 weeks to identify and rearchitect sections and pages in order of importance based on the initial survey we have done.
One of the challenges that we have encountered is that there were plenty of deprecated sites that need to be re-validated with Content Managers. For the first redesign, we wanted to simplify and do a cleanup of content and categorize the navigation considering not just the students need, but also content managers who are using the help site as a landing page to send out critical information to students.
The site is over a decade old and was managed by 3 content managers:
Selecting WordPress as a platform helped us expedite the web development side and focused on design and reorganizing content. We focused on Office Hours page as it is one of the most frequently used feature of the site. The page was redesigned and converted into custom HTML/CSS tables. We started working on setting up a child theme and translated the wireframe design into a proper homepage complete with hierarchy 3 sidebar.
While I had started adding content under the main page “Registration”, we started noticing some issues:
The team has curated a list of guidelines that we will turnover to the content managers so new content created are being maintained following standards.
We have been improving the site and use github for updates on the guideline document. The final site is now published on https://itp.nyu.edu/help.
Frontier Health is an early stage startup that has an online global marketplace. FH connects MedTech innovators to over 200 Healthcare providers in Sub-saharan Africa.
Our goal is to develop a seamless on-boarding experience that features the business value proposition to increase user acquisition on the supply side of the business (Medtech device innovators).
Project Role: User Flow Map, Wireframe Sketches, Prototype
Duration: 1.5 months
UX Team Members: Ahad Basravi, Ariella Chivil, Riri Nagao, Krizia Fernando
Version 1: Automated Onboarding Process
The team got together within the first week to understand the service touch points of Frontier Health. How does the user first interact with the product/service and where does it begin and end?
Competitive Analysis
Initially we were looking at existing marketplace B2B products that both service supply and demand, such as Airbnb and Ebay. The automated process of onboarding is our first user flow on how FH will be interacting with customers online.
Combining both the business requirements information we have collected after interviewing stakeholders, we started with whiteboard sketches to map out main features on the site, and have generated our first wireframe.
UX Writing
In the process of refining the messaging of the site, we have researched how popular business landing pages communicate to their customer. One perfect example is Uber, which has a very straightforward and simple copywriting.
Our user interviews revealed two types of users: (1) our early stage med-tech startup CEO and (2) an operations lead for a later stage startup.
Version 2: An Authentic/High Touch Approach
From our first design review with the Product Manager and the client, we have gathered different types of feedback which were very insightful and have contributed to the final redesign of the prototype.
What we learned:
Krizia Fernando