Author: Product Team · Date: 2026-06-24 · Status: Draft for alignment
Solo note-taking is seamless; collaborative note-taking is broken. When teams need to think together — project kickoffs, research synthesis, meeting notes — they copy content into Google Docs, lose context, and fragment knowledge across tools. Users can't co-create and annotate inside the app where their individual thinking already lives, so collaboration becomes a manual export problem rather than a natural workflow.
What we are NOT solving: real-time simultaneous co-editing (Google Docs parity), replacing team wikis like Notion or Confluence, or cross-company guest access.
1. Team lead sharing context As a team lead, I want to invite two colleagues into a workspace where I've organized my project notes, so they can read, comment, and add their own notes without me having to recreate everything in another tool.
2. Researcher synthesizing contributions As a researcher, I want to add notes to a shared workspace my manager created, so I can contribute findings directly alongside existing content rather than emailing a separate doc.
3. Individual protecting personal notes As a user with both personal and team notes, I want clear visual separation between my private notes and shared workspace content, so I never accidentally expose something I didn't intend to share.
4. New team member onboarding As a new hire, I want to be invited into an existing team workspace and immediately browse the notes there, so I can get up to speed without needing to be added to five separate tools.
| Metric | Target | Timeframe |
|---|---|---|
| Workspaces created per active team account | ≥ 1 workspace / team within 30 days of launch | 30 days |
| Workspace invite acceptance rate | ≥ 60% of invites accepted | 60 days |
| Weekly active workspace notes (notes opened in a workspace by non-owner) | 25% of workspace members active weekly | 60 days |
| Reduction in "export to Google Docs" events | −20% among workspace-enabled accounts | 90 days |
Primary health check: if invite acceptance rate drops below 40%, the friction in the onboarding flow needs immediate review before expanding rollout.
| Risk | Likelihood | Mitigation |
|---|---|---|
| Privacy confusion — users unsure which notes are shared | High | Persistent visual treatment (badge, workspace label) on every shared note |
| Low invite acceptance — invites feel spammy or untrustworthy | Medium | In-app invite flow with sender context; avoid cold email delivery as v1 |
| Scope creep toward real-time editing | High | Explicit non-goal; lock the appetite to async collaboration for this cycle |
| Engineering underestimate on permissions model | Medium | Spike permissions architecture in week 1; time-box to 3-week shaping session with eng |
| Milestone | Target |
|---|---|
| Shaping complete + eng alignment | Week 2 |
| Internal dogfood (team-only) | Week 6 |
| Closed beta (50 teams) | Week 9 |
| GA rollout | Week 13 |
Timeline assumes a 3-person eng squad. Revisit if squad size changes.
Open questions for alignment session: - Do we support inviting users who don't yet have an account? (email-gated signup flow) - What happens to shared notes when a member is removed — do they retain a personal copy? - Should workspace notes count against the individual note limit on free plans?