PERSONA

---
persona_id: PERSONA-pm-alex-v1
status: ready
archetype: PM
seniority: Senior IC
company_stage: series-b
company_size_employees: 180
company_arr_usd: 32000000
primary_tool_stack:
  - Linear (issue tracking, owns ~400 active issues across squads)
  - Notion (PRDs, meeting notes, OKR pages)
  - Amplitude (product analytics, funnels, cohort retention)
  - Figma (for reviewing design explorations, not drawing)
  - Slack (asynchronous comms with 12 channels pinned)
  - Looker (dashboards for activation/retention metrics)
  - Gong (listens to 2-3 sales calls per week)
  - GitHub (reviews PRs that touch product-facing config)
---

# Persona: Alex Chen

> Alex Chen is a Senior Product Manager at a Series-B PLG-motion collaboration-software company who owns activation and early retention for their core "workspaces" product.

## 1. Named Identity

| Field | Value |
|---|---|
| Full name | Alexandra "Alex" Chen |
| Age | 31 |
| Title | Senior Product Manager, Growth |
| Tenure in role (months) | 14 |
| Reports to | Director of Product (Sarah Okafor) |
| Team size | 4 engineers, 1 designer, 1 data analyst (dotted line); 3 peer PMs |
| Location / timezone | Austin, TX (CT); team spans SF + NYC + Berlin |
| Education / background | BS Computer Science, UT Austin. Started as an engineer at a bootcamp-era Rails shop, moved to PM after 4 years when she shipped an internal tool that got picked up as a product line. |

**A real person this is modeled on:** Composite of two PMs from my customer interviews (anonymized).

## 2. Company Context

| Field | Value |
|---|---|
| Company (fictional) | Flowroom |
| Industry | B2B SaaS, Productivity |
| Product | Real-time collaborative workspaces — like Notion + Figjam for async-first distributed teams |
| Company stage | Series-B ($45M raised, 2024) |
| Employee count | 180 (60 in product + engineering) |
| ARR | $32M |
| Customer count | ~4,200 paying workspaces (mix of 5-100 seat SMBs, 35 enterprise design partners) |
| GTM motion | PLG with enterprise overlay |
| Tech stack (daily) | Linear, Notion, Amplitude, Figma, Slack, Looker, Gong, GitHub, Loom (occasional) |
| What your product replaces | Notion roadmap pages + Linear project views stitched via Zapier; monthly stakeholder deck built manually in Google Slides; customer-health work done in spreadsheets from CS exports |

## 3. Jobs to Be Done

### JTBD-1 — Stay on top of a moving roadmap without drowning in status pings
- **When:** I'm juggling 40+ open features across 3 squads and my director asks for a status update in 5 minutes
- **I want to:** see the current state of the 5-10 features I care most about (mine + high-visibility ones)
- **So I can:** answer questions confidently without hunting across Linear + Notion + Slack threads
- **Success metric:** reduce time-to-status-answer from 12 minutes (current, stopwatch-timed) to ≤ 30 seconds
- **Frequency:** daily (multiple times — every standup prep, every 1:1 with director, every Slack ping)

### JTBD-2 — Keep a curated list of "things to watch" that survives context switches
- **When:** I spot an interesting customer signal in Amplitude or a bug in Linear that maps to a feature I own
- **I want to:** pin that feature somewhere I'll see it again tomorrow, without building an external tracking system
- **So I can:** not drop threads I care about when my attention fragments across 6 concurrent initiatives
- **Success metric:** drop rate of "flagged" items from ~40% (current — lose track because Slack buries it) to < 10% (persistent surface)
- **Frequency:** 3-5 times/day

### JTBD-3 — Share a short curated list with my director during 1:1s without a screen-share
- **When:** Sarah pings me 10 minutes before our weekly 1:1 asking "what's top of mind?"
- **I want to:** send a link to a live list of 5 features I'm tracking, with current status visible
- **So I can:** spend 1:1 time on decisions, not status recitation
- **Success metric:** fraction of 1:1 time spent on status down from ~40% to ≤ 15%
- **Frequency:** weekly