Project Backstory - This needs to change

"Do we have a document on this?" "Where can I find it?" "Who should I approach?" "Does CompSci deal this?" "I’m sorry it took time to figure this out." It’s so frustrating to hear these questions in almost every meeting. Instead of focusing on solutions, we spend half the time just trying to track down resources and explain what CompSci is in a Biotechnology company. This needs to change- said Computational Sciences Head.

I needed to know 3 things from Stakeholders

1. What tone do we want to set for CompSci (work and culture wise)?

2. What information is critical for the team?

3. Why are even long-time employees struggling to find data?

Answers to my questions

How did I familiarise myself with the Computational Sciences Department and delivered solution in two-week deadline?

1. Recognising the need for diverse input, I mapped the placement and availability of CS information

CS Information Platforms

2. I swiftly launched a survey targeting all CompSci employees to pinpoint the following:

1. Content that would be helpful to CS staff on a shared website

2. Understand the staff’s information ecosystem

3. Gather individuals frustrations and requirements

Realisations after Survey:

1. A new platform called has been recently created to store all technical information within the CompSci - Technical Knowledge Base

2. Effective site navigation alone isn't enough, planning a proper communication flow is also essential for impact.

3. New News: Technical Knowledge Base is the new Confluence

Connecting with the creator of Technical Knowledge Base I learnt:

1. Platform currently hold:

   • Project data - documents, meeting recordings, educational resources

2. Employees must obtain access and approval before uploading files to the platform.

3. Access is restricted and controlled to ensure privacy and confidentiality.

New platform addresses the issues found in Confluence, which the team recently has decided to retire.

4. To address diverse user needs and avoid missed requirements, I created a focused persona based on Affinity Diagram drawn after Survey.

78% of CompSci Staff Frequently Use MyJAX : Ideal for Site Mapping CS Information

5. Conducted Closed and Open Card Sorting— After gathering required resources, to uncover authentic mental models and users' key terminology driving user-centered design

Closed Card Sorting Results

Open Card Sorting

6. From observed patterns, I developed a clear site map that answers 'Who we are' and 'What we do'.

MyJAX Internal Website

Technical Knowledge Base will contain

7. Multiple solutions emerged, so to align everyone I prioritised the user's perspective and presented a high-level audit in the end.

Here’s the revamp based on the following guidelines:

1. A One-Stop-Destination for all the CS content should be designed with internal bi-directional flow.

2. The data mentioned within each category should satisfy all search parties.

3. There should be awareness of what's available, where it's available and who to go to (POC).

4. Simple, seamless navigation.

8. Further, enhancing Communication and Tailored Content was equally important

1. Include verbal updates in weekly CS meetings for improved communication.

2. Foster effective information flow across all employee levels.

3. Design content that considers both the employee's role and tenure, ensuring relevance for everyone from new hires to veterans.

Next Steps in the Project:

1. I presented the challenges and solution recommendations to the Stakeholders and the CS Team using different visual aids.

2. I documented the project and sent it to the Director of Project Management who was majorly involved in designing the current website.

3. Later, the team implemented the new Information Architecture into the internal JAX website.

User Response calculated through SUS Survey