Cord's Insights library provided people with a variety of resources to help them get the most out of the product, their job search, and the tech industry itself.
It allowed users to browse through a selection of articles, stories, videos, and podcasts, designed to cater to different people with different skill levels and interests. We had a designated team of copywriters and content producers that curated each resource to ensure that it was informative, easy to understand, and relevant to our user's needs. As the UI/UX Team we were always committed to providing the best possible experience on cord, and our content library was just one way to achieve that objective.
As a team, we aimed to increase organic acquisition and cord sign-ups. We conducted user research (find organic acquisition research here) that helped us understand what kind of resources people would benefit from when looking for a new job, and whether or not a blog section of a content library was something engineers and people looking for work would be interested in.
After conducting research, we noticed that the needs of people who were already using Cord were very different from those who weren't. Because our goal was to create content that benefited both our users and Cord itself, we decided that we needed to provide different experiences: one for the public i.e. non-cord users, and one for signed-in users, i.e people that had an account on cord.
- Increase the number of sign-ups
- Increase cords’ visibility and engagement
- Create a differentiation between cord and its competitors
<img src="/icons/hammer_yellow.svg" alt="/icons/hammer_yellow.svg" width="40px" /> What we established?
Our target audience was already engaged with other content libraries and newsletters and research showed that they would not only be interested in but benefit from an insights section within cord. A relationship that not only would benefit our users by providing them with content to support them in their careers and inform them about their industry but help cord achieve their goals.
- Building a content library would establish leadership in the industry and be a differentiator between cord and its direct competitors;
- Improve search engine optimization (SEO) and drive more traffic to the website;
- Educate and engage users potentially leading to higher retention rates;
- Providing a platform to showcase product features, use cases, and success stories;
- Building trust and credibility with potential users (for both engineers and companies hiring);
- Creating a community around the product, leading to valuable user feedback and insights.
Process & Research
- Discover, Define, Design, and Deliver
First, we conducted user research as part of the HCD process.
After gathering insights from surveys and interviews, we defined the problem and began ideating. Our initial version of Cord's Insights progressed from sketches to high-fidelity prototypes and throughout the process, I held multiple review sessions with all stakeholders to ensure that everyone was in agreement and that we were following what we believed to be the right direction. Before delivery, I conducted a small usability test with members of other teams within the company. Based on their feedback, I made further iterations resulting in the final product.
- Go to Organic Acquisition Research.
- Experience 1 - Was focused solely on the logged-off experience and the one to everyone who lands on the cord.co has access to.
- Experience 2 - The focus was on the experience after sign-in. Since people on Cord had already built profiles with information about themselves and their skills, it made sense to use this information to provide a great user experience. We used this information to populate the "home" area on Cord, which we renamed "Insights." This area housed all the articles available publicly, but they were now highly tailored and personalized to the user based on the information on their profiles (as we had learned during research).
Experience 1: Public / Landing Page
Experience 2: Signed-In