North Star Product Strategy
The non-goals exercise finally stopped our roadmap from ballooning every sprint. I still reopen the worksheet before exec readouts.
Editorial opening
Judgment ships when language does
SprintHarbor Academy gathers working product leaders who care about how decisions get written down, not just what ships first. We host cohorts, clinics, and async rooms for tech professionals across Korea who want calmer roadmap forums and clearer handoffs. Nothing here promises automatic promotion; we practice the unglamorous work of specs, readouts, and retros that still matter after the slide deck is filed.
Members trade annotated artifacts, critique discovery notes, and rehearse facilitation scripts that survive real enterprise clients. If you are allergic to vague advice, you will find the community tone direct and kind.
Harborline community desk · live roster
Welcome to the Harborline community desk
Members shipping better decisions this season: 1,842 active handles across forums, clinics, and study halls. Pick a doorway, read the rituals, then take one step toward a cohort that matches your craft focus.
- Weekly studio blocks with operator facilitators
- Breakout triads for roadmap critiques
- Shared artifact wall visible to your whole cohort
- Office hours that stay in the activity log
- Peer swaps with structured prompts
Learning paths the community keeps near the top
Harborline learning paths behave like community-curated playlists. Members upvote briefs, teardowns, and facilitator scripts so the most useful material floats upward without a popularity contest devolving into noise. Each path blends live conversations with async artifacts you can reuse at work the same week. Moderators rotate weekly so no single voice dominates the feed, and every path links to a responsible operator who has shipped comparable programs in enterprise markets.
Upvotes are not vanity metrics; they unlock mentor attention for the threads that need it. When a path stalls, the community editor archives it with a short note so newcomers do not chase outdated templates. You can follow a path solo, but the designed experience assumes you will leave at least one public comment so the next cohort inherits context.
Paths are numbered intentionally—the sequence mirrors how experienced PMs revisit fundamentals after every major launch. Expect to disagree with at least one step; disagreement is surfaced, not smoothed away, because the goal is shared vocabulary rather than false consensus.
- Write a decision sentence for the next risky bet.
- Pair it with a customer signal someone outside your pod can verify.
- Publish a roadmap diff that names owners, not just themes.
- Run a forum using the Harborline timer and note-taking roles.
- Capture a retro entry in the shared activity log with follow-up owners.
- Ship a short essay back to the community digest with what changed.
Ambassadors who model the tone
Ambassadors are not mascots; they are members who consistently surface better questions. They receive no special perks beyond early access to experiments and a moderator bat phone for escalation.
- Yuri Han · Seoul — "I stay for the ruthless clarity on roadmap diffs; nobody handwaves trade-offs."
- Leo Park · Busan — "The facilitation lab changed how I close meetings without a parking lot of maybes."
- Ines Alvarez · Remote APAC — "Metrics reviews here end on time because the ritual is designed, not improvised."
- Tariq Mensah · Pangyo — "Cross-org workflow maps from cohort night saved our handoffs from quiet rework."
- Nari Cho · Jeju — "I share discovery notes because the comment threads stay technical, not performative."
Stories from cohort timelines
Chronological conversation snippets—each tied to a concrete module.
Evidence-Led Roadmapping
The activity log template is now our default after launches; incident records feel less scary.
Discovery Sprints for Busy Teams
Facilitator script kept me from improvising prompts when stakeholders went quiet—huge relief.
Metrics That Change Decisions
Retired a dashboard nobody trusted after the charter exercise; the review agenda is shorter and kinder.
AI-Assisted Product Judgment
Review ladder made async spec reviews calmer; the cohort still wants a deeper dive on evaluation harnesses next season.
Choose how you authenticate
Connect your GitHub identity so we can place you in the right critique pods and avoid duplicate accounts. We only request basic profile details; repository access stays with you. After linking, you can still choose email digests for reminders. Moderators use the same link path when they rotate shifts, which keeps onboarding consistent for everyone arriving from open-source communities.
Notebook entries worth the scroll
Browse the blogWhen your roadmap is polite but unclear
Polite roadmaps hide missing owners. Here is how we teach cohorts to surface them without drama.
Discovery notes people actually reread
Good discovery is not more transcripts. It is a note structure your future self thanks you for.
Metrics reviews that end before midnight
Shorter metric reviews are not lazier. They are a kindness to judgment.