Peer-to-Peer Skill Exchange Platform

Task Overview

As a Product Management Intern working on "SkillSwap", your role is to shape the product direction and define its initial features. "SkillSwap" is a web-based platform connecting individuals who want to learn a new skill with those who can teach it. For example, someone who knows graphic design can learn guitar from a guitarist who wants to improve their photography skills. Your tasks involve market understanding, user persona creation, product requirement definition, and initial visualization of the product experience.

Key Focus

This assignment blends strategic product planning with basic visual conceptualization. You will not only outline who the product is for and what it should do, but also provide simple wireframes that reflect the user flows and key interfaces. The goal is to ensure you can think end-to-end: from user needs all the way to how the product might look and feel at a basic level.

Deliverables

1. Market & User Research Summary:
   • Summarize the existing landscape of peer-to-peer learning platforms. Identify at least two competitors and their strengths/weaknesses.
   • Provide a brief analysis of potential user needs and pain points. These can be assumed based on logical reasoning or hypothetical user interviews. Why might people prefer a peer-to-peer skill exchange? What challenges exist in connecting learners and teachers?
2. Value Proposition & User Personas:
   • Articulate a clear value proposition: What sets "SkillSwap" apart from traditional learning platforms?
   • Develop 2-3 user personas that represent distinct target audience segments (e.g., a college student looking to learn a new language, a working professional wanting to develop a hobby). Include their motivations, goals, and the barriers they face.
3. MVP Feature Set & Prioritization:
   • Outline the core features required for the Minimum Viable Product. For example: Profile Creation (skills offered and wanted), Skill Matching System, Messaging for scheduling sessions, Basic Review/Feedback System.
   • Use a simple prioritization method (e.g., MoSCoW) to indicate which features are must-have, should-have, etc.
4. User Stories & Acceptance Criteria:
   • Write 4-6 user stories capturing critical product interactions (e.g., “As a user interested in learning guitar, I want to view potential guitar teachers nearby so that I can schedule an in-person lesson”).
   • Provide acceptance criteria for each story to ensure clarity.
5. Metrics for Success:
   • Propose 3-4 key metrics to track product success (e.g., match success rate, user retention, time-to-first-match).
   • Explain the rationale for each metric and how it would guide future product decisions.
6. Basic Wireframes (Low-Fidelity):
   • Create low-fidelity wireframes (hand-drawn sketches or digital equivalents) of at least 2-3 key screens. Consider the homepage, profile setup screen, and a sample match results screen.
   • These wireframes should illustrate the core user experience and help visualize how the features come together.

Submission Guidelines

• Upload your documentation (PDF, Google Docs, or slides) that includes your research summary, value proposition, personas, MVP feature list, user stories, acceptance criteria, and metrics.
• Upload your wireframes as image files or link to a tool like Figma/Miro.
• There is no strict deadline; you may submit whenever your work is complete. However, submitting sooner allows us to proceed with reviewing your work earlier.

Evaluation Criteria

• User-Centered Insight: How well do the personas and value proposition reflect understanding of user needs?
• Clarity & Coherence: Is the MVP scope defined clearly and logically aligned with the product goals and user stories?
• Prioritization & Feasibility: Are the outlined features appropriate for an MVP, balancing ambition with simplicity?
• Actionable Metrics: Do the success metrics make sense and would they be helpful in guiding product decisions?
• Visual Thinking: Do the wireframes adequately represent the intended user flow and feature functionality, even at a low-fidelity level?
• No LLM: We will know if you use one.

Good luck, and we look forward to seeing your approach to making "SkillSwap" a reality.