Research Process:

During the research process, it became clear that the project needed well-informed yet quick data collection for the client. The client lead, designers, and I collaborated to develop a Grounded Research evidence-based approach called ROOT to mitigate bias. It consisted of 8 segments completed during our 6-month engagement.

While following this process, certain stages had iterations or loop points. I show this by the cycling arrows for the ROOT diagram.

In the first stage, I created surveys while collecting measurements through team meetings.

With baseline data established, I continued to collect data from interviews and surveys.

During this process, I realized the importance of employee morale in this project. I encouraged them by showing smaller chunks of data visualization and progress notes.

Internal Community Thread:

The interviews and internal conversations revealed agreement on both problems and excitement sources:

💻 Collaborative interfaces to allow for real-time actions and prevent miscommunication.

👥 Shared knowledge between different teams to prevent siloing of information and problematic troubleshooting.

⚙️ Automation of routine processes that allow for bulk actions in production. 

🤝 Integration of information from other software used by the company

Custom Database:

These areas needed further division to discuss targeted areas with the client.

While identifying opportunities, I worked with the team to create tiered connections. These categories are back-linked to the database.

Below is a quote from a subcategory with an attached pain level from the earlier survey data.

Resource Management:

II focused on resource management related to the custom database and user stories. 

I saved resources by an estimated 40% through:

1) Maintaining the opportunity solution tree as we verified categories with the client

2) Using an LLM, recordings, and structured research questions to create user stories

The collected evidence was used to inform our client at this stage. I organized the data visualizations to showcase the best choices for our client.

Asset Journey Maps:

I proposed asset journey maps rather than user journey maps to capture the changing asset groups and personnel in the production pipeline to better capture the full investment selections.

1️⃣ Categories include ‘Loop Points’ to show alternative workflows not captured in linear flow, and follow-up questions for the internal teams.

2️⃣ Asset provides a short summary of that section in the process, and how it relates to other roles.

3️⃣ The asset showcases roles associated with that step and newly acquired sub-assets.

I utilized these three areas to create three distinct zones, showcasing the nuances of the asset pipeline.

Using the research and client investment section, I focused on employee roles involved in the creation and use of product assets:

Product Brief:

The investment selection chosen required improvement of both searching and filtering existing and non-finalized libraries of their assets.

Some of the frustration and wish-related comments from employees provided baselines regarding searching and filtering in the next software upgrade. I compiled their quotes in the database. From there, I created a product brief and a back-linked visual report.

Conclusion:

The compilation of a holistic database, visual map, asset journey maps, and product brief provided an informed view of all major problem spaces, providing the client with evidence and confidence to defend their second phase of development.

Reflections:

This project required tight cross-collaborative work to keep deliverables on track during a major client’s holiday calendar, especially during the early discovery phases. I am proud of what our team accomplished. I learned a lot about internal vs. external communication, customizing research for quick action, and being more comfortable with large datasets, If allowed a similar project, I would cross-verify information early on to generate client discussions in the initial engagements. This way, we can tackle any blind spots together and forge a strong client relationship.

15

Teams were heard and documented