Trigger: OAuth nearing completion - time to think about what happens after someone connects.

Framing

Onboarding isn't just "getting connected" — it's "becoming productive." The path to productivity differs by persona, but shares a common entry point.

Personas

Persona	Example	Entry point	Workspace state	Key challenge
Collaborator	Collaborator A	Invited	Already exists	"How do I navigate this?"
Solo dev	Claude Code user	Self-discovery	Empty	"How do I structure this?"
Team lead	Richard	Already using solo	Creating for others	"How do I set this up for my team?"

Journey Structure

Connect (shared)
    |
    +-> First session
            |
            +- No workspace -> Bootstrap flow (solo dev)
            |
            +- Has workspace
                    |
                    +- Owner -> Architecture flow (team lead)
                    +- Member -> Orientation flow (collaborator)

Coverage Analysis

Area	Status
Connection flow	Well covered (OAuth investigation)
Collaborator orientation	Partially covered (onboarding instructions task)
Solo dev bootstrapping	Gap - primary target user not covered
Team lead architecture	Partially covered (Partner Workspace case)

Open Questions

Section 1: Connection (shared)

• Largely solved via OAuth work
• Remaining: final deployment, testing with real users

Section 2: First Session by Persona

Solo dev (the gap):

• What do they see when they first connect with no workspace?
• Empty workspace vs. template vs. guided setup?
• What's the minimum viable structure to start?
• How do we teach "what to capture"?

Collaborator:

• How do they orient to existing structure?
• Do they need a "tour" or just dive in?
• What if conventions aren't documented?

Team lead:

• How do they structure for others vs. themselves?
• When to create new workspace vs. invite to existing?
• How to establish conventions that stick?

Section 3: Path to Productivity

• What's the "aha moment" for each persona?
• What habits differentiate effective users?
• How do we measure success? (sessions without re-explaining context?)

Related Work

• "Understand what it means to add another user" exploration (Collaborator A case)
• "Product Direction & Positioning" analysis (target: single-player devs first)
• OAuth investigation (connection flow solved)