Inquery

Website

Role

UX Researcher, UX Designer

Duration

3 months

Responsibilities

UX research, wireframing, prototyping, usability testing

Mockup of Inquery

2

Designers

Discovery

According to the U.S. Bureau of Labor Statistics, the field of data science is expected to grow 28% by 2026. When compared to the national average of 7.7%, it makes sense that more students, educators, and businesses are tapping into the industry now more than ever as the world starts to realize the power of data. Many small businesses don’t have the time, money, or resources that larger corporations have to tap into this potential. Conversely, students have a difficult time gaining hands-on, real-world experience when many smaller businesses are not privy to what data science is since the term has been recently popularized. Data science educators are having a difficult time finding data and real-world projects for their students to work on for the same reason. Inquery aims to address these challenges through a tailored job board, facilitating connections between users and opportunities.

Challenge

Many small businesses don’t have the time, resources, or knowledge to become a data-driven organization. Conversely, data science students need opportunities to grow their skillset.

Proposed Solution

Provide small business owners and data scientists with a personalized job board to connect with each other. By working together, they can help these businesses become more efficient.

Phase 1

Understanding the User

Listening sessions, competitor analysis, pain points and personas


Listening Sessions

Takeaway: Users lack opportunities for communication with each other.

We conducted multiple listening sessions with data science students from UNC-Chapel Hill and NC State University, data science educators from UNC-Chapel Hill, and small business owners from Chapel Hill, NC to understand our user needs. While individual needs varied, the shared theme revolved around the necessity for consistent communication. Some of the questions we asked to gather these results included:

What was your last internship/job search experience like? What made the experience positive or negative?  
Have you ever worked with a data scientist before? If not, do you know what a data scientist does?
What types of projects do your students typically work on? Where do typically find the data they will use?

Competitor Analysis

Takeaway: Provide the need-to know information upfront rather than requiring users to search

The most commonly used job board by our users were Handshake, LinkedIn, Glassdoor, and Upwork. This analysis helped us identify opportunities for Inquery, such as providing more consistent job information and simplifying the process into one flow rather than third-party portals.

Pain Points

We identified a core pain point from each of our users, which were student apprehension about unresponsive employers, educators struggling to connect with small business owners, and small business owners grappling with comprehending data science's benefits.

Inquery user pain points

Personas

Compiling our research into personas helped us simplify our goals into actionable insights. Taking into account our three primary types of users, data science students data science educators, and small business owners, we were now ready to start the design.

Inquery persona Inquery persona Inquery persona
Phase 2

Starting the Design

User journey, information architecture, sketches, wireframes, high-fidelity prototype V1.


User Journey

Considering the flows for a both a data scientist and small business owner helped us determine opportunities for improvements, such as automatically syncing information from a student’s profile into their application and helping small business owners sort through their applicants with an application preview.

Data Scientists

Inquery user journey data scientists

Small Business Owners

Inquery user journey small business owners

Information Architecture

We divided our information architecture into the view for a data scientist (once they have created an account) and the view for a small business owner. The main difference was how either user would interact with the job/applicant search.

Data Scientists

Inquery information architecture

Small Business Owners

Inquery information architecture

Sketches

Initial ideations of Inquery included a profile with an extremely visible call to action button to message business/data scientists, a search bar for a user's top recommended profiles, and an about page where small business owners could learn about the value of hiring a data scientist.

Centible user pain points

Wireframes

Our wireframes highlighted primary user flows: applicants finding and applying for jobs, and business owners overseeing applications. A key addition in the wireframes was a chat screen, enabling effortless communication and Zoom meeting scheduling for employers and applicants. This addressed a mutual pain point: insufficient, effective communication.

First-Time User

Inquery wireframes

Returning User

Inquery wireframes

High-Fidelity Prototype V1

Our first high-fidelity prototype included a detailed onboarding per Apple's Human Interface Guidelines and built upon the ideas we had in our wireframe.

Phase 3

Refining the Design

Usability testing, iterations, high-fidelity prototype V2, accessibility, style guide.


Usability Study Feedback

Our unmoderated usability study was sorted into both tasks and reflections for data scientists and small business owners. Our questions asked them to navigate to portions of the prototype and give feedback on the design and their experience. Some questions we asked participants were:

Imagine you are a data scientist trying to apply to Acme Corp. How might you navigate to the portion of the site where you can apply to the company?
Were you able to find the applications to your job posting? Was this experience difficult or easy?
If you had a magic wand, what would you change about this experience?

Iterations

First Major Improvement: Active Hiring

“I think it could be helpful to add a feature that shows whether a data scientist is open to work and similarly whether a company is open to hiring.” - User A

Inquery iterations

Second Major Improvement: Rapid Apply

“It was easy to find the screen where I can apply for a job, however options include message or go to website. No clear Apply option.” - User C

Inquery iterations

High Fidelity Prototype V2

Our high-fidelity prototype synthesized our user feedback into a usable prototype we could relay to our developers. Click on the prototype below to interact with it!

Accessibility

We followed best practices to ensure that our app was accessible for all users, some of which were:

Contrast Ratios

The contrast ratios between the colors we used in the foreground and the background meet Web AIM standards.

Text Hierarchy

Copy that is meant to be a heading, subheading, or body is an appropriate size in descending order of importance.

Consistentcy

Back buttons, next buttons and search bars aree all located in expected locations so users aren't distracted by complicated functionalities.

Design System

The design system we created for Inquery used Segoe UI for typography, included components of how our navigation bar would change with the selected user, and prioritized a neutral color palette with the exception of our primary and secondary shades of purple.

Inquery's design system
Phase 4

Going Forward

Takeaways


Takeaways

Impact

Out of the 4 tasks we asked our users to complete, all 6 users were able to complete all 4 tasks and 100% of users said they would use this site.

“I thought it was easy to find where I can view people that applied to my job posting since it is located on the navigation bar.”
"The design is very good! It's very straightforward to use and I love the visuals."
“I especially liked the different categories a company or business owner can look for potential candidates.”

What I Learned

  • Your users are your greatest asset. Through usability testing, they may uncover suggestions for improvements that you hadn't even considered!
  • Your first draft is never your final one. There is always room for improvement, and it's important to learn from every iteration.