Prototyping process with journey maps
The Open Single-cell Pediatric Cancer Atlas (OpenScPCA) is an open, collaborative project to analyze data from the Single-cell Pediatric Cancer Atlas (ScPCA) Portal, which currently holds over 500 samples from more than 50 pediatric cancer types. OpenScPCA uses an open contribution model designed to allow experts worldwide to contribute and rapidly share the results of analyses in real time. The project was officially launched in April 2024.
Organizing and managing open analysis projects is not new to us. In 2019, we co-organized the Open Pediatric Brain Tumor Atlas (OpenPBTA) project with the Center for Data-Driven Discovery in Biomedicine (D3b) at Children’s Hospital of Philadelphia (CHOP). We learned many lessons from OpenPBTA and were eager to incorporate them into our new venture.
Going into OpenScPCA, we knew it would be important to have:
- A clear sense of how contributors will interact with the project
- Good documentation to help external researchers make contributions to the project
To achieve this, we first had to understand more about who our potential contributors might be!
Who?
After working with over 60 contributors worldwide on OpenPBTA, we already had an idea about what kinds of experts might be interested in this project and how we might characterize their expertise. We built OpenScPCA user archetypes focusing on the experience and skills we expect contributors to bring to the project. Here’s what we were able to determine!
If it sounds like we are describing you, we encourage you to learn more about joining OpenScPCA!
Scenarios
We noted the common use cases for projects involving contributors and Data Lab members. We also had to predict some less frequent scenarios that contributors and Data Lab members will likely encounter as the project progresses.
Example Scenario:
Scenario 10: Help! My setup is glitching
A researcher has forked the repo and set up the project locally. When they try to make commits, they get an error. Their pre-commit is failing, and they think something is wrong with the codebase or their setup.
What they need to do:
- Create a bug report using the bug report template.
- Move the discussion to the appropriate location as guided by the organizers.
- Participate in troubleshooting.
What the Data Lab needs to do:
- Redirect their issue to the correct forum.
- Help troubleshoot their issue.
With a greater understanding of potential contributors and possible scenarios, we could begin the journey-mapping process!
What is a Journey Map?
A journey map is a set of user activities arranged on a timeline. Depending on the goals of journey mapping, additional information is added to the map like user thoughts, emotions, and relevant information.
Journey maps are used to chart user behavior in a variety of contexts and tasks. We used journey mapping to track the steps users needed to take for a particular task and any support which would help them be successful.
In our case, we are using journey maps to achieve the latter.
Journey maps are useful tools to create a shared understanding and foster discussion of users and processes in an interdisciplinary setting. It also helps different teams to agree on how the process should work.
Templating the journey map
Journey maps can help track various aspects of a user journey. It is important to distill the information that is most helpful for how we want to use the journey map.
To start, we outlined the end goal of the journey mapping activity.
Goals:
- To lay out process and surface disagreements, missing information, and potential hitches
- To make a clear distinction between the responsibilities of the contributor and the responsibilities of Data Lab members
- To gather items that need to be documented for contributors
Creating the template
Based on our goals, we created a template to help us capture information at each step.
- Steps in the process: A brief description of the step
- Contributor action: Describes what action contributors need to take for the step to be successful
- Data Lab member action: Describes what action Data Lab members need to take for the step to be successful
- Tools: Lists what tools they are using at this step (Example: Github Issues, RStudio)
- What documentation are they referring to: What types of documentation will help contributors successfully complete this step
Journey mapping
- We grouped the actions from each scenario into tasks. Some scenarios were small enough to be considered in their entirety, while some had actions that overlapped with other scenarios, like merging a pull request. In those cases, the actions from multiple scenarios were grouped together.
- We divided the tasks among the science team members, the community manager, and the UX designer based on their expertise and which tasks they were most likely to be involved in.
Getting on the same page
Once everyone had completed their assigned journey map(s), we took time to review each other’s work, ask questions, and leave feedback. Some of the issues we identified were resolved asynchronously. Some required further discussion, so we had a meeting to answer the remaining questions and come to a resolution.
Here's how the activity helped us:
Jaclyn Taroni, Director: "As Director of the Data Lab, I found the process was most useful for surfacing disagreements or areas that needed more discussion. The team members who will be responsible for carrying out the project have varying levels of experience with collaborative open science projects and teaching reproducible research practices. Journey mapping provided an opportunity to share relevant lessons we've learned over the lifetime of the Data Lab."
Joshua Shapiro, Senior Data Scientist: "Journey mapping helped organize my thinking about the complex web of interactions in an collaborative project. We were able to identify steps and frame processes that might otherwise have been missed or given less attention during the planning phases of a project like OpenScPCA."
Ally Hawkins, Data Scientist: "As a member of the science team that did not play an active role in OpenPBTA, I did not have previous experience working on an open-collaborative project that involves external contributors, like OpenScPCA. Journey mapping really helped me understand what it would look like to interact with external contributors on a project like this before even starting the project. It gave me the opportunity to think about the overall processes that would be implemented throughout the course of the project and ask questions about what my role would be in each process. I left journey mapping with a clear understanding of expectations for what we as a team would need to focus on and what we would need to document for contributors."
Stephanie Spielman, Data Scientist: "Journey mapping was a great way to conceptualize how different components of tasks interact, including how our team interacts with one another as well as with external collaborators. In particular, it helped jog my brain to think about often-overlooked small, but crucial, aspects of how a large project with many moving parts come together. Journey mapping has made me feel more prepared to engage with both my team and with external collaborators because I've taken the time to think through the scenarios and potential outcomes we'll encounter over this project's lifetime."
Jen O’Malley, Scientific Community Manager: "My role involves building and managing a community of external collaborators. Journey mapping helped me understand who our potential collaborators might be. It also helped me visualize the steps they would take from learning about the project, deciding to participate, being onboarded, and becoming an active contributor. This was helpful for developing a recruitment strategy, planning a communications campaign, and determining how we would provide ongoing community support."
Deepa Prasad, UX Designer: "My role in the project was to structure the documentation to be easy to access and use. Journey mapping gave me a holistic view of the process and the documentation items which needed to be included. It also gave me valuable information about context and which of our user archetypes would be performing the task which helped determine the level of detail we included in the docs, and informed the navigation menu."
Journey mapping can be used as a quick and cheap way to identify potential problems and develop strategies to mitigate them. It can also be used as a tool to ensure that everyone on the team is on the same page. For OpenScPCA, this process helped us visualize the experience of potential contributors from being onboarded to making their first contribution. We felt better prepared to support contributors and tackle challenges before launching the project!
Are you a disease expert, a seasoned computational biologist, or looking to hone your data analysis skills? Consider joining a supportive community that is building a resource to benefit pediatric cancer research! Learn more about OpenScPCA and how to get started here.
The Open Single-cell Pediatric Cancer Atlas (OpenScPCA) is an open, collaborative project to analyze data from the Single-cell Pediatric Cancer Atlas (ScPCA) Portal, which currently holds over 500 samples from more than 50 pediatric cancer types. OpenScPCA uses an open contribution model designed to allow experts worldwide to contribute and rapidly share the results of analyses in real time. The project was officially launched in April 2024.
Organizing and managing open analysis projects is not new to us. In 2019, we co-organized the Open Pediatric Brain Tumor Atlas (OpenPBTA) project with the Center for Data-Driven Discovery in Biomedicine (D3b) at Children’s Hospital of Philadelphia (CHOP). We learned many lessons from OpenPBTA and were eager to incorporate them into our new venture.
Going into OpenScPCA, we knew it would be important to have:
- A clear sense of how contributors will interact with the project
- Good documentation to help external researchers make contributions to the project
To achieve this, we first had to understand more about who our potential contributors might be!
Who?
After working with over 60 contributors worldwide on OpenPBTA, we already had an idea about what kinds of experts might be interested in this project and how we might characterize their expertise. We built OpenScPCA user archetypes focusing on the experience and skills we expect contributors to bring to the project. Here’s what we were able to determine!
If it sounds like we are describing you, we encourage you to learn more about joining OpenScPCA!
Scenarios
We noted the common use cases for projects involving contributors and Data Lab members. We also had to predict some less frequent scenarios that contributors and Data Lab members will likely encounter as the project progresses.
Example Scenario:
Scenario 10: Help! My setup is glitching
A researcher has forked the repo and set up the project locally. When they try to make commits, they get an error. Their pre-commit is failing, and they think something is wrong with the codebase or their setup.
What they need to do:
- Create a bug report using the bug report template.
- Move the discussion to the appropriate location as guided by the organizers.
- Participate in troubleshooting.
What the Data Lab needs to do:
- Redirect their issue to the correct forum.
- Help troubleshoot their issue.
With a greater understanding of potential contributors and possible scenarios, we could begin the journey-mapping process!
What is a Journey Map?
A journey map is a set of user activities arranged on a timeline. Depending on the goals of journey mapping, additional information is added to the map like user thoughts, emotions, and relevant information.
Journey maps are used to chart user behavior in a variety of contexts and tasks. We used journey mapping to track the steps users needed to take for a particular task and any support which would help them be successful.
In our case, we are using journey maps to achieve the latter.
Journey maps are useful tools to create a shared understanding and foster discussion of users and processes in an interdisciplinary setting. It also helps different teams to agree on how the process should work.
Templating the journey map
Journey maps can help track various aspects of a user journey. It is important to distill the information that is most helpful for how we want to use the journey map.
To start, we outlined the end goal of the journey mapping activity.
Goals:
- To lay out process and surface disagreements, missing information, and potential hitches
- To make a clear distinction between the responsibilities of the contributor and the responsibilities of Data Lab members
- To gather items that need to be documented for contributors
Creating the template
Based on our goals, we created a template to help us capture information at each step.
- Steps in the process: A brief description of the step
- Contributor action: Describes what action contributors need to take for the step to be successful
- Data Lab member action: Describes what action Data Lab members need to take for the step to be successful
- Tools: Lists what tools they are using at this step (Example: Github Issues, RStudio)
- What documentation are they referring to: What types of documentation will help contributors successfully complete this step
Journey mapping
- We grouped the actions from each scenario into tasks. Some scenarios were small enough to be considered in their entirety, while some had actions that overlapped with other scenarios, like merging a pull request. In those cases, the actions from multiple scenarios were grouped together.
- We divided the tasks among the science team members, the community manager, and the UX designer based on their expertise and which tasks they were most likely to be involved in.
Getting on the same page
Once everyone had completed their assigned journey map(s), we took time to review each other’s work, ask questions, and leave feedback. Some of the issues we identified were resolved asynchronously. Some required further discussion, so we had a meeting to answer the remaining questions and come to a resolution.
Here's how the activity helped us:
Jaclyn Taroni, Director: "As Director of the Data Lab, I found the process was most useful for surfacing disagreements or areas that needed more discussion. The team members who will be responsible for carrying out the project have varying levels of experience with collaborative open science projects and teaching reproducible research practices. Journey mapping provided an opportunity to share relevant lessons we've learned over the lifetime of the Data Lab."
Joshua Shapiro, Senior Data Scientist: "Journey mapping helped organize my thinking about the complex web of interactions in an collaborative project. We were able to identify steps and frame processes that might otherwise have been missed or given less attention during the planning phases of a project like OpenScPCA."
Ally Hawkins, Data Scientist: "As a member of the science team that did not play an active role in OpenPBTA, I did not have previous experience working on an open-collaborative project that involves external contributors, like OpenScPCA. Journey mapping really helped me understand what it would look like to interact with external contributors on a project like this before even starting the project. It gave me the opportunity to think about the overall processes that would be implemented throughout the course of the project and ask questions about what my role would be in each process. I left journey mapping with a clear understanding of expectations for what we as a team would need to focus on and what we would need to document for contributors."
Stephanie Spielman, Data Scientist: "Journey mapping was a great way to conceptualize how different components of tasks interact, including how our team interacts with one another as well as with external collaborators. In particular, it helped jog my brain to think about often-overlooked small, but crucial, aspects of how a large project with many moving parts come together. Journey mapping has made me feel more prepared to engage with both my team and with external collaborators because I've taken the time to think through the scenarios and potential outcomes we'll encounter over this project's lifetime."
Jen O’Malley, Scientific Community Manager: "My role involves building and managing a community of external collaborators. Journey mapping helped me understand who our potential collaborators might be. It also helped me visualize the steps they would take from learning about the project, deciding to participate, being onboarded, and becoming an active contributor. This was helpful for developing a recruitment strategy, planning a communications campaign, and determining how we would provide ongoing community support."
Deepa Prasad, UX Designer: "My role in the project was to structure the documentation to be easy to access and use. Journey mapping gave me a holistic view of the process and the documentation items which needed to be included. It also gave me valuable information about context and which of our user archetypes would be performing the task which helped determine the level of detail we included in the docs, and informed the navigation menu."
Journey mapping can be used as a quick and cheap way to identify potential problems and develop strategies to mitigate them. It can also be used as a tool to ensure that everyone on the team is on the same page. For OpenScPCA, this process helped us visualize the experience of potential contributors from being onboarded to making their first contribution. We felt better prepared to support contributors and tackle challenges before launching the project!
Are you a disease expert, a seasoned computational biologist, or looking to hone your data analysis skills? Consider joining a supportive community that is building a resource to benefit pediatric cancer research! Learn more about OpenScPCA and how to get started here.