HackerPen

From Competitive Analysis to Kano Analysis. How user needs will impact design.

TL;DR

A competitive audit was performed to determine what sets a website apart from its competitors and what it might want to include in order to attract new users. A key stakeholder was interviewed to gain insights into their future goals for the site. Current state and future state journey maps were created to show how happy a user can be, if only the stakeholder would take a UXer’s advice. Rapid prototyping was then followed by a technical consultation to shoot down any extremely complicated ideas. (Thankfully, I only have good ideas!) A kano analysis was performed on possible prototypes which determined what prototypes should be designed and which was should be forgotten. The successful prototypes were converted into high fidelity prototypes and then explained in an annotated report.

Overview

My Role: Researcher and Designer

Methods: Competitive Audit, Stakeholder Interview, User Journey Mapping, Rapid Prototyping, Technical Consultation, Kano Analysis

Tools: Google Suite, Zoom, Miro, Figma

Deliverables: Competitive Audit, User Journey Map, Feature Concepts, Kano Analysis, Annotated Wireframes

Team Members: Haley Nguyen, Nicole Neumann, and Saba Andualem

The Client

HackerPen is a start up dedicated to preparing tech job seekers for technical interviews through the use of mock interviews with professionals already established in the field of software engineering. The platform allows interviewees to work through technical questions while on a video call with an interviewer.

The Goal

At this time HackerPen is looking to make adjustments to their current method of matching interviewees with interviewers. The platform currently matches individuals based solely on available time slots. They are looking to make expansions that would include the ability to connect individuals in more meaningful ways. This would support HackerPen’s values of being a community-driven platform that connects candidates and companies together.

Competitive Audit and Stakeholder Interview

After an introduction to HackerPen, similar platforms were audited to help illustrate the mental model of the industry and further explain the problem space. Later a meeting with a major stakeholder from HackerPen took place to get a better understanding of the scope of the project and to know what would be meaningful to HackerPen’s users. 

Journey Maps

A current state journey map was created to display pain points in the platform and to make recommendations for opportunities in the future. Major pain points included the inability to match with interviewers based on professional skills and the inability to direct message interview participants after an interview.

Once wireframes were completed, a future state journey map was developed to illustrate changes.

Rapid Prototyping

Sketches of possible features were created based on the information gathered from the journey mapping. 

Proposed features included:

  • An option to send follow up questions after an interview

  • A marketplace page to select interviewers based on price

  • A profile page for interviewers

  • A post interview feedback form for interviewee to review interviewers

  • A thank you note messaging option

Technical Consultation and Kano Analysis

Prototype sketches were presented to a technical consultant who gave estimates of how long each feature would take to complete in HackerPen’s software development process. At that time, HackerPen’s goal was to add new features that could be completed in a six week timeframe. Based on that meeting, specific feature concepts were selected to move forward. They were then presented to current HackerPen users in the form of a survey. The results of this survey determined which features were required, desired, and unnecessary.

Annotated Wireframes

Based on journey mapping and kano analysis, features were chosen to move forward with wireframing. The features created were meant to be achievable within Hackerpen’s development timeframe of six weeks. Annotations were created to explain design concepts to the client.

Next Steps

Testing the wireframes with potential users would be the next phase of this project. It would be important to get feedback directly from users before moving forward to the proposed designs. It would also be best to consult again with the client stakeholder to ensure that the designs created would be feasible for their next design sprint. 

Conclusion

Many UX research and design methods were utilized for this case study. It’s amazing how all the pieces came together to create concept designs which are achievable for a small tech start-up. I hope these concepts are helpful for HackerPen and help them achieve their goals connecting great candidates with great jobs.

Speaking of jobs…..I would love one! Please reach out if you would like me to take a look at your site and help you create something great!