← Back

Indeed Company profile editor

Product for helping employers create and manage their branding content
OVERVIEW

After a weekly sync with my Product Manager, I saw an opportunity to improve the way employers create and edit content on their Indeed profile. I took inspirations from other products and created a proof-of-concept design prototype to improve the experience.

The design was evaluated by the team, and brought forward for further iterations and validation with user testings. As a result, it made to the product roadmap in Q2 2019.

TEAM

- Product manager
- UX Researcher
- Design Technologist

TIMELINE

Sept 2018 - Feb 2019

Context

Currently when employers want to create or update content on their Indeed’s company profile, they use the following tool to manage their branding and edit their content.

Users face two main problems with this tool:

  1. When they make a change to their branding or content, they have no way to preview how it looks like on their profile and fix potential mistakes.
  2. Every changes are published to their live site immediately in front of the job seekers. They have no way to make multiple changes and publish them at once.


This results in employers lacking confidence in using the product to keep company profile content up to date. If they have made any error on the content, their visitors will able to see it immediately without having a chance for employers to correct them.


Long term direction

Before I joined Indeed, there was a design exploration to imagine the ideal editor experience: A WYSIWYG editor to manage the content.

However, I learned that the PM and the engineer team evaluated the effort and estimated that it’d require at least 6 months to build - mainly due to the complexity around the interaction of having the editor inline with the content that doesn’t have a fixed layout.


With this constrain in mind, I thought about how might we provide a better editor experience that offer content preview, but not necessary require an inline editor?

Desk research

I spent an afternoon to look around other common products and evaluated their editor experience. On the higher end of the spectrum we have products like Squarespace, Wix, Webflow etc where the editor is the core product and offer the WIYISWYG experience.


In the middle of the spectrum where the editor is a supplementary part of their core product, they use an editor pane side-by-side with a content preview to provide real-time feedback on how their content is going to look like.(Forexample: Shopify, Wordpress - for theming controls)

Considering we are designing the tool for users who are in the recruiter or marketing role with less page-creation technical experience, the WYSIWYG editor direction could be intimidating for them. Where as the other direction may have the benefit of providing a more guided approach to help users complete their profiles.


With this hypothesis, I believed this was a promising direction that struck a good balance between providing a better experience for our targeted users whilst requiring minimal product development changes.

Concept prototype

I spent the next day and a half to create quick mockups, and prototyped the core interaction with Framer to demonstrate key concept.

I’ve then presented this prototype to the PM and engineers - everyone was excited about this direction and got a consent that it’d require less effort to develop as compared to the WYSIWYG editor.

Interaction design and prototype

As an agreed next step, we planned the next couple of weeks to further iterate the design, and cover the use cases and states that match the current tool.


Partnering with a Design Technologist - we aimed to create a front-end prototype that can be used for user testing by the end of 2018 (Approximately~4 weeks time).


Within this available time, I worked on design details such as:

  • How does the navigation work between the employer product and the editor? Do we need to maintain the product navigation?
  • How might we communicate that the changes are saved as draft? And users need to click to publish once they’re ready?
  • Where best should we place the Publish button and preview options?
  • How should the interaction work for rearranging content blocks?
  • How would each of the content and theme editing option work?
  • Do we need to provide an onboarding experience to help users orientate the tool?

Throughout the design process, I explored multiple options, evaluated the pros and cons based on my own judgement, reviewed with other designers for external opinions, and conducted a few guerrilla user testings in the office for fresh perspectives.


I used Zeplin to deliver the design spec and states with our Design Technologist, and also sitting side-by-side for refinements as we get down to further design details such as states and transitions. With our close collaboration, we delivered the prototype on time as planned.

User testing results and refinements

Weeks before the prototype was ready, I collaborated with our PM and a UX Researcher to plan research and recruit participants ahead of time.

A round of user testing was conducted in the beginning of 2019, with the main goals to evaluate:

  • Do users have any comprehensive issues using the tool to create or update their company profile?
  • How do users feel about using the tool to update content?
  • Do users expect the content being saved automatically or need to be explicitly saved as draft?

Overall, we found that users had no major issues using the tool to create their company profile. It took a little bit of time for them to orientate themselves, but once they find their way around they described the experience as“prettystraight forward”. A couple of minor usability issues were noted around the interaction of the“premiumtoggle”, default placeholder content, and label misconceptions.


Based on this round of findings, I’ve proposed a small round of design iterations to address the reported usability issues. I also took this opportunity to further refine the visual design - by removing as much borders and containers as possible to reduce visual noise.

Conclusions

After the validation with user testing and constant discussions with PM about the priority, we’ve finally committed to begin with the development in Q2 2019. I look forward to see how this product improvement may increase the number of company profiles with employer content, and if it results in better formatted content as well.


With this case study, I want to demonstrate my ability to lead design-driven initiatives that wasn’t originally on the product roadmap. I also want to demonstrate my collaboration skills with different stakeholders in the product team to understand constrains and come up with solutions that satisfy both user and business needs.