Design a better cloud file collaboration experience for student project teams that improves collaboration activation

Problem Statement Description

Students working on group projects often use Drive to create, collect, organize, and submit files across documents, slides, spreadsheets, PDFs, images, datasets, and instructor-provided materials. While Drive is a natural place for shared work, many student teams still struggle to activate true collaboration: teammates may not join the folder, may request access too late, may duplicate files, may miss updates, or may default to messaging apps instead of collaborating inside the workspace.

Design a better Drive cloud file collaboration experience for student project teams with the goal of improving collaboration activation. Focus on the early lifecycle of a project team: forming a shared workspace, inviting classmates, setting the right permissions, adding relevant files, assigning ownership, and getting teammates to meaningfully participate. The experience should fit real student workflows such as class projects, capstones, lab teams, hackathons, and remote or hybrid coursework.

Assume Drive already supports file storage, sharing, comments, real-time editing in connected productivity apps, notifications, search, and permission controls. Your design should improve the user journey without compromising privacy, security, accessibility, or trust, especially given that students may use personal, school-managed, or mixed accounts.

The experience should consider:

- How a student project team starts or discovers the right shared workspace for a class assignment

- How teammates are invited, onboarded, and encouraged to take a first collaborative action

- How permissions, ownership, link sharing, and school-domain restrictions are made understandable

- How files, tasks, comments, versions, and deadlines are organized around a project workflow

- How the product handles inactive teammates, duplicate files, late access requests, and fragmented communication

- How notifications and collaboration questions avoid becoming noisy or overwhelming

- How the experience works across mobile, web, and low-friction sharing contexts

- How accessibility, student privacy, responsible AI use, and operational cost constraints shape the design

Your goal is to define a focused product experience that increases the number of student project teams who move from simply storing files to actively collaborating in Drive. Describe the target users, key pain points, core user journey, major product surfaces, and how you would judge whether collaboration activation has improved.