North-Star and Guardrail Metrics for a Musician-Matching Collaboration App

You are the product manager at a startup that matches people who want to make music together. How would you measure whether it is succeeding? ```hint Define a good match Before listing metrics, decide what has to happen after two musicians are matched for the match to count as a success, and whether the product can actually observe it. ``` ### Clarifying Questions - Does the collaboration itself happen in the product, for example a live remote session or a shared project, or does the product only make the introduction? - Who is being matched: hobbyists looking for people to jam with, bands missing a member, or working musicians looking for paid collaborators? - What stage is the startup at, and is there a business model yet, such as subscriptions? - Are matches local and in person, remote, or both? ### What a Strong Answer Covers - The user journey from sign-up to a finished collaboration, and the moment value is delivered - A north-star metric tied to that moment rather than to sign-ups or raw match counts, with the reason for choosing it - Supporting metrics along the funnel: profile quality, match quality, conversion from match to collaboration, and retention - Guardrails covering safety, match supply across instruments, genres and locations, and users who rarely get matched - How the metric set shifts with the startup's stage and how each metric would be measured ### Follow-up Questions - If most collaborations happen outside the product, how would you know a match led to people playing together? - Matches per user are up but repeat collaborations are down. What would you investigate first? - Musicians who find a permanent band may stop using the product. Is that churn or success, and how would your metrics treat it?