Arity Content Review Process

Additionally, I used the results from the post-interview survey to quantify the emotional journey of the team members. Using a likert scale, I measured agreement by having participants rank how strongly they agree with a provided statement from a scale of 1-5. My analysis identified the main pain point of concern: that team members are unable to easily access materials from other departments across different softwares.

Development

Using the results from the interviews as a guide, I moved into diagramming the workflows of two processes: the current content review process as is, and the "ideal" revised content review process.

Visualizing these workflows made it possible for me to write down a step-by-step workflow of the revised content review process, which would later help generate a tree diagram of the proposed final solution.

However, I first had to consider what platform the solution would exist on. I envisioned a centralized location where the content review process could take place, thus whatever platform I ultimately chose must support cross-team collaboration and have features to track the progress of content items for a project.

I took inventory of the currently used tools at Arity: Confluence and Jira were the main ones, followed by GitHub/Git Towers, and the MS Office Suite (containing OneDrive, Copilot, and SharePoint). Additionally, I researched other tools that were either previously used OR had not been implemented, which were Trello, Notion, and Linear.

Considering the collaborative nature of this content review process, platforms that were more technical to use were struck out. This included GitHub/Git Towers and Jira. Following the same thought process, I opted not to suggest a completely new tool like Trello, Notion or Linear because the process of learning to use these tools and incorporate them into preexisting workflows would be too burdensome for team members, who are often working on fast-paced projects that would be bottlenecked by implementing a new software.

This left me with only one option: Confluence. Confluence already supported cross-team collaboration and all Arity team members were familiar with its platform. Thus, I created a tree outline that functioned as the "skeleton" for my final solution: a template that tracks the content review process of a project, all housed within Confluence.

Finally, the only task remaining was to export my tree outline to an actual functioning Confluence template.

Impact

Our final solution was a Confluence template that team members could easily duplicate and edit for their specific project needs. Its main feature was a content item table where members could upload content items and assign a tag to designate its status in the workflow. Additionally, team members could be assigned to these content items for review as needed, ensuring clear visibility of ownership in the content review process. The tabular format also provided significant information such as version history, the name of the uploader, and so forth, allowing for more clarity and conciseness.

Overall, I created a solution that formalized the (formerly nonexistent) content review process at Arity. This solution will streamline future projects, reducing time and money wasted on alleviating confusion regarding project items and ownership in the review process.

The main accomplishments for this project were:

• Presenting our findings alongside my fellow intern to the Experience Design & Research department at Arity, showcasing how the new Confluence template can be incorporated into future project workflows.
• Producing a final recommendation document for the content review process to be disseminated company-wide, with more detailed instructions on how to utilize our delivered solution.
• My coworker and fellow intern, Alex, created a one-pager summarizing our findings, proposed solutions, and thoughts for a more brief overview.

While I did make an impact on the organization through my work on this project, this project also made a significant impact on me. I learned how to use mixed research methods, interview users, and design solutions, which all will be instrumental assets in my toolbox as I continue my journey as a UX designer.