top of page

InfoDev Team Site

This Google Site functions as the primary resource for the Information Development team, including process, procedures, and other learning tools.

The Process

After conducting a content audit of the site, the my team and I discovered key pain points in the existing architecture through surveys and interviews. Comments included issues like too many options in navigation, inconsistent styling throughout the site, and unclear taxonomy.

We conducted a card sort once after using the survey and interview responses to being development into our information architecture. Surprisingly, our users' responses to the card sort varied drastically. We decided to base the information architecture off of technical writers key deliverables in their roles.

Additionally, we removed third-level navigation from the global navigation, reducing the number of options a user initially has to encounter. To increase user engagement, we added a feedback form that they could use for updates, concerns, or any positive feedback. This feedback form also helped streamline the maintenance process.

The Work

The initial design was tested with a group of 20 users, with results leading to minor changes to increase findability. We added acronyms to page titles to improve the search results.

By updating the site's style, we gave the site a professional look that adhered to Workday's branding guidelines. Right after launch, Workday updating their branding, so we updated our site as well to maintain trustworthiness with our users. Several users commented that knowing that we were striving to maintain site consistency helped them feel like the source of information was accurate and relevant.

An issue we faced in developing a maintenance plan was managing site content ownership. There were too many cooks in the kitchen for the original website. We received some kickback when we revealed our plan to only let the maintenance team have access to the site, but once we explained Google Sites publishing process, it became less of an issue.

Before

Old Site Homepage

After

Redesigned Homepage

The Result

Post launch of the new site, the team was inundated with positive feedback from the new feedback from, emails, and Slack messages. We held a Brown Bag to demonstrate the new site for our users, receiving comments from tenured writers that they would actually use the site now. I solicited feedback from recently hired technical writer with positive results. Over all, the new site exponentially improved the daily lives of users in their roles at work.

However, a drawback with the site is the hosting platform. Google Sites doesn't have the same filterable searches and other SEO features. It's sufficent enough as a website builder, but in the future, I think the site could provide better functionality if it were hosted as a dedicated knowledge base.

ilx-new-ag.png
bottom of page