Building a tool for Crewasis data scientists.
Crewasis has been delivering game-changing data insights for clients since 2017. By unlocking the power of data, the data scientists are able to consult marketing and sales leaders on revenue and growth opportunities.
Team
3x Product Designers
My Role
UX Researcher
Lead Product Designer
Stakeholders
CEO
Senior Product Manager
Data Scientists
Engineering Team
Timeframe
3 Weeks
Challenge
Using decentralized tools, the data scientists needed an internal platform to improve internal collaboration, communication, and feedback for weekly deliverables.
Using decentralized tools, the data scientists needed an internal platform to improve internal collaboration, communication, and feedback for weekly deliverables.
Solution
An internal portal for the Crewasis data scientists to improve collaboration, transparency, and communication. This would allow for efficient data analysis, leading to faster business insights to increase client revenue.
An internal portal for the Crewasis data scientists to improve collaboration, transparency, and communication. This would allow for efficient data analysis, leading to faster business insights to increase client revenue.
Research & Insights
Research & Insights
Clients want collaboration.
Clients want collaboration.
Data scientists were looking at project briefs on Quip, uploading and downloading data on Google Drive, creating unorganized presentation decks async, and sending files on slack. With so many decentralized resources, management sought to create a better experience for its employees with a platform that met their needs.
I guided my team through a competitive analysis of work-place collaboration tools and dashboards to draw feature inspiration for the following objectives:
Goal #1: Upload/download data sets and files to a centralized resource library (off-boarding Google Drive)
Goal #2: Project management dashboard
Goal #3: Real-time collaboration features
Data scientists were looking at project briefs on Quip, uploading and downloading data on Google Drive, creating unorganized presentation decks async, and sending files on slack. With so many decentralized resources, management sought to create a better experience for its employees with a platform that met their needs.
I guided my team through a competitive analysis of work-place collaboration tools and dashboards to draw feature inspiration for the following objectives:
Goal #1: Upload/download data sets and files to a centralized resource library (off-boarding Google Drive)
Goal #2: Project management dashboard
Goal #3: Real-time collaboration features
Data scientists were looking at project briefs on Quip, uploading and downloading data on Google Drive, creating unorganized presentation decks async, and sending files on slack. With so many decentralized resources, management sought to create a better experience for its employees with a platform that met their needs.
I guided my team through a competitive analysis of work-place collaboration tools and dashboards to draw feature inspiration for the following objectives:
Goal #1: Upload/download data sets and files to a centralized resource library (off-boarding Google Drive)
Goal #2: Project management dashboard
Goal #3: Real-time collaboration features
Users want transparency.
Users want transparency.
After conducting interviews with our target end users, the Crewasis data science team, we quickly discovered that their needs were different than business goals. Upon analyzing responses, we identified key pain points among the team that became integral to the design:
Transparent Collaboration Few multi-edit documents for teams to work on together, efficiently.
Centralized Feedback 70% of users reported feeling confused when receiving feedback across multiple platforms. This made it difficult to iterate on the next deliverable.
Communication with Client 40% of data scientists mentioned they could not ask clarifying questions or receive feedback for next deliverables because client communication was only through CEO.
After conducting interviews with our target end users, the Crewasis data science team, we quickly discovered that their needs were different than business goals. Upon analyzing responses, we identified key pain points among the team that became integral to the design:
Transparent Collaboration Few multi-edit documents for teams to work on together, efficiently.
Centralized Feedback 70% of users reported feeling confused when receiving feedback across multiple platforms. This made it difficult to iterate on the next deliverable.
Communication with Client 40% of data scientists mentioned they could not ask clarifying questions or receive feedback for next deliverables because client communication was only through CEO.
After conducting interviews with our target end users, the Crewasis data science team, we quickly discovered that their needs were different than business goals. Upon analyzing responses, we identified key pain points among the team that became integral to the design:
Transparent Collaboration Few multi-edit documents for teams to work on together, efficiently.
Centralized Feedback 70% of users reported feeling confused when receiving feedback across multiple platforms. This made it difficult to iterate on the next deliverable.
Communication with Client 40% of data scientists mentioned they could not ask clarifying questions or receive feedback for next deliverables because client communication was only through CEO.
3 feature ideations
3 feature ideations
Home Dashboard
To understand the user's vision, we engaged the data scientists in a card-sort activity to help us determine an intuitive dashboard layout for their future portal, as well as key features to incorporate in our designs.
To understand the user's vision, we engaged the data scientists in a card-sort activity to help us determine an intuitive dashboard layout for their future portal, as well as key features to incorporate in our designs.
Using the results of the card-sort, we created a mid-fi prototype of the Home Dashboard to test. We found that 75% of users found it the features too crowded, clicking through multiple buttons for a task as a result of option paralysis. We simplified the screen to have less features, and moved items to the side navigation for easier organization.
Using the results of the card-sort, we created a mid-fi prototype of the Home Dashboard to test. We found that 75% of users found it the features too crowded, clicking through multiple buttons for a task as a result of option paralysis. We simplified the screen to have less features, and moved items to the side navigation for easier organization.
To understand the user's vision, we engaged the data scientists in a card-sort activity to help us determine an intuitive dashboard layout for their future portal, as well as key features to incorporate in our designs.
Project Dashboard
By utilizing Google Drive, Quip, and Slack to gather various information, it became clear that our users needed a centralized hub where they could easily access all project-related data, documents, and resources. After finalizing features to include on this dashboard and conducting user testing on our mid-fi prototype, we found a majority wanted a more prominent Activity Feed and Communication module to help keep feedback top-of-mind.
By utilizing Google Drive, Quip, and Slack to gather various information, it became clear that our users needed a centralized hub where they could easily access all project-related data, documents, and resources. After finalizing features to include on this dashboard and conducting user testing on our mid-fi prototype, we found a majority wanted a more prominent Activity Feed and Communication module to help keep feedback top-of-mind.
Insights
The data scientists had 4 deliverables (or, 'insights') due every week for 4 week sprints. Keeping this in mind, we made sure that insights were easily filtered by week, and that each insight had the related files accessible. Users would be able to upload and download files as needed, and edit the final deliverable from this screen before review. We also included the feedback comments in a chat function below for ease of reference.
The data scientists had 4 deliverables (or, 'insights') due every week for 4 week sprints. Keeping this in mind, we made sure that insights were easily filtered by week, and that each insight had the related files and reports centralized in view. We also included the feedback comments in a chat function below for ease of reference.
Lessons Learned
Lessons Learned
Broader questioning It wasn't until the conclusion of the project that one of the principal data scientists brought up how the teams monitor project progress. This insight was vital since we were developing a progress tracker. In hindsight, I would have sought to question the intricacies of the work management process so we could tailor the portal feature to their specific work flow.
Project timelines and incentives Due to our limited time, we couldn't carry out a second usability test. Our project faced challenges with time management due to delays in receiving responses from the client. If we had provided more incentives for data scientists to engage in our research and user testing, it's possible that our timeline would have been shorter, allowing for more extensive testing and smoother implementation in the future.
Team guidelines It was only during this project that I came to recognize the significance of team guidelines for fostering a smoother dynamic during sprints. These guidelines helped us manage disagreements, communications, and decision making in a swift manner to help us complete our sprint.
Broader questioning It wasn't until the conclusion of the project that one of the principal data scientists brought up how the teams monitor project progress. This insight was vital since we were developing a progress tracker. In hindsight, I would have sought to question the intricacies of the work management process so we could tailor the portal feature to their specific work flow.
Project timelines and incentives Due to our limited time, we couldn't carry out a second usability test. Our project faced challenges with time management due to delays in receiving responses from the client. If we had provided more incentives for data scientists to engage in our research and user testing, it's possible that our timeline would have been shorter, allowing for more extensive testing and smoother implementation in the future.
Team guidelines It was only during this project that I came to recognize the significance of team guidelines for fostering a smoother dynamic during sprints. These guidelines helped us manage disagreements, communications, and decision making in a swift manner to help us complete our sprint.