Skip to main content

Product Manager Challenge 2

Part 1 – Product Scenario (Creative + Organizational + Product Cycle Knowledge)

Your team has been tasked with creating a platform that helps students better collaborate on coursework and projects.

  1. Problem Exploration

    • Define two key pain points students face with collaboration today.

    • Describe your approach to validating whether these are real and worth solving.

  2. Vision & Features

    • Propose a vision statement for the platform.

    • List 3 major features you would prioritize, and explain why (reference feasibility, impact, and effort).

  3. MVP Definition

    • If you had only 6 weeks and a small 4-person engineering team, what would your minimum viable product look like?

    • Provide a clear prioritization rationale (e.g., using MoSCoW, RICE, or another framework).

Part 2 – Execution (Organization + Proactivity + Technical Prowess)

  1. Roadmap & Planning

    • Create a high-level 8-week roadmap breaking down 3 phases (e.g., discovery, MVP build, iteration).

    • Assign approximate ownership (e.g., engineers, designers, PM responsibilities).

  2. Communication & Proactivity

    • Draft a short status update email to your team at the midpoint of the project when you realize one of the features may be delayed. Show how you would:

      • Keep morale positive

      • Communicate clearly

      • Suggest next steps

  3. Technical Awareness

    • Suppose engineers propose two implementation options for a core feature:

      • Option A: Quick to build but minimal scalability.

      • Option B: More complex but allows growth and integrations.

    • Which would you choose for an MVP? Justify your decision based on product management principles.

  4. Ticket Cutting
    • Please create a ticket/task for one part of one of your potential features 
    • The Ticket should include: 
      • User Story
      • Acceptance Criteria 
      • Technical Details
      • Out of Scope

EvaluationSubmission CriteriaGuidelines

    Submission Requirements 

    1. Product

      OrganizationScenario: Clear structure

        and
      1. PDF prioritizationwith: in
          answers.

        1. 2 Key Pain Points
        2. Vision Statement
        3. 3 Prioritized Features
        4. MVP with included features 
        5. Prioritization

          Proactivity:Rationale

          6. Evidence
        of
        2. anticipating risks, communicating clearly, and proposing solutions.

    2. Execution

      Creativity:

        Original
      1. 8 featureWeek ideas and thoughtful approaches to collaboration.

        roadmap 
      2. Status

        Productupdate Developmentemail

        3. Cycle
      3. Option Knowledge:A Demonstratedor useOption of frameworks, MVP thinking,B and roadmap planning.

        justification 
      4. Public Github Repository with Project Kanban 

    Submission Conventions

    PDF should be formatted "Your Name - PM Challenge F25" (e.g. "Lucas Ha - PM Challenge F25")

    TechnicalYou Prowessmust submit your PDF and Github Repository link via this Google Form.: Balanced tradeoff reasoning, showing awareness of product-engineering compromises.

     

 

Back to top