GSK - Portfolio View Application DViz Design Challenge

Welcome to the "GSK - Portfolio View Application  DViz Design Challenge"! 

GSK is a global leader in pharmaceutical development. This is the first part of a project to design the Portfolio View Application, which is based on data analytics. In this challenge we would like you to conceptualize and design several data visualizations that will be used in an application providing a strategic view into research & development projects. GSK leadership needs clear access to this information in order to make faster and more accurate decisions about ongoing and future research and development. 

Your focus should be on creating data visualizations to help surface this data in a meaningful and dynamic way.

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

Round 1

Submit the 4 type of data visualizations for checkpoint feedback:
1) Time in Phase
2) DPP Progress 
3) DPP Progress Detail (table view)
4) Rate of Change

• As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
• Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit the 4 type of data visualizations along with all feedback applied for final review: 
1) Time in Phase
2) DPP Progress 
3) DPP Progress Detail (table view)
4) Rate of Change

• As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
• Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
• If you're not submitting in the Checkpoint/Round 1, you are not eligible to submit in the Final/Round 2

CHALLENGE OBJECTIVES

• Create 4 to 8 data visualizations (depending on your approach) to describe the required metrics
• Revealing visualizations: Surface key analytics insight and dynamics that are easy to understand, even in a simplified view
• Flexible visualizations: Data visualizations could be represented with various degrees of detail (think: view of dashboard list vs. project phase detail)

BACKGROUND OVERVIEW

• GSK is a large global healthcare company focused on pharmaceutical Research and Development (R&D). Scientific innovation accelerates the pace at which GSK is able to develop and deliver transformational medicines. The company R&D supports hundreds of active R&D efforts at any given time.
• Members of GSK’s leadership team each manage a portfolio of R&D projects. An individual Research Unit Head portfolio may have 20 - 50 active projects. Leaders must understand their portfolio’s progression and health in order to make effective decisions regarding ongoing project activity. They also must make recommendations during Governance Board meetings as to which projects should move forward. Leaders are looking to prioritize projects which have a higher probability of success over those which are less promising. The data that defines “project success” is complex and constantly changing.
• Currently, the leadership team must engage in a cumbersome process to understand their projects at multiple stages during development. A great amount of data is captured around the details of each project. However, it is not standardized nor easily accessed in a meaningful way. Many discussions, meetings, and presentations are required to give a clear picture of project health to the leader responsible. Prioritizing projects within the context of their portfolio is even more difficult, as side-by-side comparison of data is not available on demand. This linear process is repeated continuously during a project’s lifespan - to help make regular operational adjustments, and to provide recommendations before Governance Board review meetings. 

EXPECTED SOLUTION

• Consolidate data & analytics metrics so they will be meaningful within an application for the leadership team
• Provide a standardized and accurate view of the data, with direct paths to supporting detail information
• Allow flexibility to way the visualizations express data at various levels of granularity

EXPLORATION SCORE

• Creativity: Impactful (the solution is different or unique from what has already been used)
• Exploration: Flexible (use the provided requirements as a starting point, and propose improvements that positively impact the users' goals)
• Aesthetics: Hi-fidelity design (provide a top-notch finished-looking visual design)
• Branding: Flexible (follow the provided guidelines and suggest improvements that seem appropriate and inline with the goals)

GLOSSARY

• R&D = Research and Development. GSK is focused on R&D in the pharmaceutical industry.
• Portfolio = A collection of active R&D projects. One user may have 20-50 projects within their portfolio.
• Project = An active Research & Development effort aimed at developing a viable pharmaceutical product.
• Governance Board = A group of GSK Leaders who determine if a project should continue in development or be terminated. Governance Board meetings occur regularly and address projects at multiple phases during their lifespan.
• Phase = A defined portion of a project.
• Cycle Time = The time from start to finish of one phase of a project.
• RU (Research Unit) = An area of scientific research. For example: oncology, immunology, genetics.
• eQBA (Question Based Approach) = A set of 23 standardized questions that gather data during the lifespan of a project to help provide a view into the potential for success.
• DPP (Discover Project Profile) = A subset of eQBA. Nine (9) standardized questions that gather data during the lifespan of a project to help provide a view into the potential for success.
• RAG = Colors: Red, Amber, Green. These color values are assigned to indicate the strength of the data collected for each DPP question. Red = weak, Amber = mediocre, Green = strong.

TARGET AUDIENCE/USERS

• We are focusing on GSK employees who have the responsibility to manage a portfolio of projects in development.

USER PERSONA 

• Tracy Jones, VP,  Oncology Research Unit Head
  • A senior level employee with a leadership role
  • Large amount of responsibilities, very little time
  • Comfortable with technology and online applications
• Goals - When the data is surfaced in an Application, Tracy has these goals:
  • Understand project performance in the context of her portfolio, so that she can prioritize the portfolio to make investment/resource decisions.
  • Easily drill into details of reliable project data, so that she can be confident she is making smart decisions.

USER WORKFLOW

This workflow should be used ONLY as reference to help you to understand why the user will want to see the data. We will address the User Workflow interactions in a future UI Design challenge (in the 2nd challenge).

• Tracy’s workflow in the Portfolio View Application will primarily follow a path as she answers key business questions regarding her portfolio. By finding the answers to these questions, Tracy will be able to meet her objectives. The data visualizations should support this workflow and present the analytics in a clear and insightful way.
• Question #1) How is my project doing vs. expected cycle time?
  • Tracy will look for a measure of the time a project has been in a specific phase. (Time in Phase) If she sees projects that have time greater than the Industry Target, she will know they need to be addressed at the next operational meeting.
  • Within an application, Tracy will want to view multiple projects in the same phase, to compare their cycle times to one another.
• Question #2) What is the Technical Readiness of my project vs. what is expected?
  • Tracy will look into the DPP (Discovery Project Profile) Progress for this specific project. One metric for DPP Progress is the DPP Completion. Tracy will want to see a measure of this project’s DPP Completion related to the expected completion target point. (DPP Progress / DPP Completion)  Tracy hopes to see that this project’s DPP Completion is at or above the target.
  • If Tracy sees that this DPP Completion is low compared to the target, she will drill deeper into other metrics that indicate DPP Progress.
• Question #3) How does one project compare against other projects in my portfolio?
  • Tracy will look at DPP Progress for a specific project and compare it with other projects in the same phase. She will want to look at all three metrics that make up the DPP Progress: eQBA Completion, DPP Completion, and Strength of the data collected. (DPP Progress) 
  • Tracy hopes to see a good level of eQBA Completion, DPP Completion and strong (green value) data collected compared to those measurements in the same phase of other projects.
• Question #4) Is the project’s cycle time faster/slower than expected in current and previous phases? Is this because of gains/losses in a previous phase?
  • Within an application, Tracy sees that one of her projects has a very fast cycle time for its current phase. She drills deeper into the details of that project for additional context to explain this exception. She will need a view to see and compare how the Actual Time of each phase in this project relates to the Industry Target.
• Question #5) How does my project compare with itself at a previous point in time? And, how does it compare with other projects in the portfolio?
  • DPP Progress visualizations used within an application could help Tracy prepare for a meeting to discuss next steps for one of her projects. She needs to have a thorough understanding of how it has been progressing since it began.
• Question #6) How quickly has my project changed from a previous point in time? And, how does this compare with other projects in the portfolio?
  • To further understand the potential of a project, Tracy will be looking to see if it is making steady progress throughout its duration. The change could be measured as a Rate of Change based on three different metrics: DPP Completion, Strength of data, or Time in Phase. (Rate of Change)
  • Tracy knows that this Rate of Change for these metrics should improve at an expected rate as time passes. By setting some parameters, she is able to compare her project’s DPP Completion Rate of Change from the project start through its second phase, to the DPP Completion Rate of Change from the project start through its fourth phase.
• Question #7) How will I add filters to see more granular and/or summary views of the data reported for a project?
  • Within an application Tracy may need a view of her Portfolio and all of the projects she has responsibility for. By using intuitive filters to combine properties, Tracy is able to access a more dynamic view into a project or group of projects.

REQUIRED DATA VISUALIZATIONS

• Based on the User Workflow, the following data visualizations will be needed. Additional visualizations may enhance your unique design solution.
• For each visualization, consider a version that could be simplified and displayed within a list or card view in a UI. Also consider how the visualization may have a more detailed version or allow drilling into more detail.
• Sample Content for Reference

1) Time in Phase

• Time is measured in months. 
• Each visualization should include three data points to compare:
  • Actual time to date for the phase (number of months)
  • Target time (marker for the expected cycle time for the phase)
  • Proposed time for phase (time proposed specifically for this project)
• Positive: Actual and Proposed Time should be less than or equal to the Industry Standard time.

2) DPP Progress 

• This concept is indicated by three distinct metrics: eQBA Completion; DPP Completion: Strength of data. These may be combined or kept as separate visualizations depending on your solution.
  • 2a) eQBA Completion
    • Amount (i.e. percentage) of the eQBA questions that have been answered out of the full number expected per the project
  • 2b) DPP Completion
    • Amount (i.e. percentage) of the DPP questions that have been answered out of the full number expected per the project
    • Target amount (marker showing the expected completion amount for that phase)
  • 2c) Strength of data 
    • RAG value assigned to each of the completed DPP questions
    • Visual indication of the amount of each value per a phase or the entire project
• Positive: eQBA completion should be high, DPP completion should be at or above to target, and majority of the data collected should be strong (Green).
• Controls must be available to surface a more detailed view of data: DPP Detail will display each question with an indication of completion and value. (See 2b)
• View should be controlled via filters to allow comparison between multiple phases in the project or to other projects for the same phase.

3) DPP Progress Detail (table view)

• This screen layout will represent data with more detail for the same three metrics as in: 2) DPP Progress
• The view would include:
  • eQBA questions
  • DPP question (if the question is part of the DPP set)
  • Project Names/IDs
  • Visual indication of complete/incomplete and a value representing strength of data (RAG) - for each question, for each project.
• Filters should allow control by project(s) and by phase(s)

4) Rate of Change

• This concept of Rate of Change could be applied to three different metrics: DPP Completion; Strength of data; Cycle time. These would NOT be combined into a single visual.
• Each should show a visual indication for measurement of Rate of Change (the difference in a metric’s value between two (2) points in time during the project’s lifespan). The Rate of Change could be calculated for:
  • 4a) DPP Completion - Numerical value calculated by comparing DPP Completion from point to point.
  • 4b) Strength of data - Visual representation showing the change in the Strength of data (RAG values) from point to point.
  • 4c) Cycle time - Visual representation showing cycle times for selected phases, displayed side-by-side to understand the cumulative effect.
• Positive: Looking to see an improving Rate of Change as time passes. Higher rate or more obvious change may suggest better performance.
• User should have control to specify points of time within the project to calculate Rate of Change visualizations. Additional filter options should allow comparison of the Rate of Change between multiple projects with the same parameters set.

CHALLENGE FORUM

• If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum: https://apps.topcoder.com/forums/?module=ThreadList&forumID=834869

TARGET DEVICES

• Web/Desktop: minimum 1366px width and height as required

SUBMISSION AND SOURCE FILES

Submission File

• Submit JPG/PNG image files based on Challenge submission requirements stated above
• MarvelApp link for review and to provide feedback
• Declaration files document contains the following information:
  • Stock Photos Name and Links from allowed sources
  • Stock Art/Icons Name and Links from allowed sources
  • Fonts Name and Links source from allowed sources
  • Full Details of the Topcoder Policy can be found in this LINK

Source Files

• All source files of all graphics created in Adobe XD, Figma, or Sketch and saved as an editable layer

FINAL FIXES

• As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors