The Problem I Solved

When I started work on the Teradata Developer Portal, there was very little continuity between the sites. The main landing page was tied to the marketing site, which made users feel that it was not the go to place to look for developer resources. Other sites, such as the Downloads site, had not been updated in years, even though it is one of the most visited sites for Teradata Developers. The new site of developers.teradata.com became the landing page for Teradata Developers to learn what resources they have access to, get the latest updates, and became the benchmark for the other Developer sites to be based off of.

How I Solved It

Understanding that landscape, I participated in user research and interviews to better understand who uses each of the touch points of the Developer Portal, what they liked about the current solution, and what they hoped to see from a redesign.

Slowly but surely, I helped move the sites that fell under the “Developer Portal” umbrella to feel more like one cohesive experience. I added unified navigation, so a user felt like the sites were all a part of the same ecosystem, even if their back-end technology was not the same. Eventually, the team was able to do a major overhaul of all the sites, including a much-improved Downloads site.

The final phase involved bringing the look and feel of the site up to date with the new branding so the user would have a similar experience whether they came from the main site, teradata.com, or from one of the sites tied to developers.teradata.com. In this redesign, I emphasized easier navigation, orienting the user within the site’s overall hierarchy, and ensuring that the site is fully responsive on all screen sizes.

Why It Mattered

Use of the homepage increased as it became the default location for Teradata Developers to understand the resources available to them.