Test 152

Priya’s usability notes are here: Onboarding flow usability notes — invite accepted / pre-repo-connect Author: Priya Date: 2023-10-09 Screen tested Current empty state after invite acceptance and before first repo connect: Headline: "Connect a repo when you’re ready" Support line: "You can finish setup now or come back later from workspace settings." CTA in prototype: "Connect repo" Call 1 — 2023-10-04 Participant profile: engineering manager at a 14-person team; invited by a founder, not the person who set up the workspace. Observed behavior: - Read the screen without hesitation and said the tone felt "less pushy than most setup flows." - Hovered on the CTA, then stopped to ask whether picking the wrong repo would be hard to undo. - Did not interpret the step as skippable forever; interpreted it as the next real task, just not necessarily for this exact moment. Quoted reactions: - "Okay, good — this isn’t yelling at me." - "I probably do need to connect something, just not before I ask who owns the repo list here." Takeaway: the low-pressure headline reduced anxiety for someone who had accepted an invite but did not yet have enough context to act. Call 2 — 2023-10-05 Participant profile: platform lead joining an existing team workspace. Observed behavior: - Understood what a repo connect means, but paused on the phrase "when you’re ready." - Asked what happens if they skip and go explore the app first. - Wanted a slightly more direct statement of the task. Quoted reactions: - "‘When you’re ready’ makes me think this is optional, but I know you probably want me to do it next." - "If this is the setup step, I’d rather it just say that more plainly." Takeaway: the current copy is friendly, but maybe a little too soft on what the next action actually is. Call 3 — 2023-10-06 Participant profile: product engineer invited into a workspace but not ready to install anything during the call. Observed behavior: - Liked the support line about coming back later from workspace settings. - Asked what connecting a repo unlocks and whether there is any timing pressure. - Verbally connected the screen to trial/billing timing even though nothing on the page mentions trial. Quoted reactions: - "Come back later from workspace settings is helpful; that tells me I’m not burning my one chance." - "If the clock is already running on something, I’d want the page to say that." - "I’m fine doing this later, but then tell me exactly what I’m postponing." Takeaway: flexibility message works, but some users still want a crisper statement of the next step and what changes after they do it. Patterns across all three calls - Nobody reacted badly to the softer direction; the tone is doing useful work. - Two of three users wanted the next action stated more concretely. - One of three explicitly asked about trial/timing pressure; that question came from uncertainty, not from the current page creating urgency. - The support line tested better than the headline. People liked knowing they could return from workspace settings. Two copy changes I’d test next 1. Simpler repo-connection prompt within the same overall direction Proposed headline: "Connect your first repo" Proposed support line: "Finish setup now or come back later from workspace settings." Why: keeps the lower-pressure feel, but makes the task more concrete and removes some of the marketing-softness from "when you’re ready." 2. Add explicit trial/timing context Proposed headline: "Connect your first repo" Proposed support line: "Your team trial is active. Connect a repo now or come back later from workspace settings." Why: addresses the "is some clock already running?" question directly, but it definitely pushes the screen into a more sales/billing-coded tone. My read from the calls: the problem is mostly clarity of the repo step, not resistance to the relaxed tone. Please synthesize this into a short decision reply to Priya in our internal team chat. Decision: simplify the repo-connection prompt within the already selected empty-state direction. Do not bring back trial-activation language.

Priya and Jake’s latest January read is steady: repo connection and same-session completion are stable, teammate-invite confusion hasn’t grown, support volume is normal, and nobody is asking for trial language or setup checklists. Please send Priya a private note in the internal chat: she can close the remaining Figma monitoring comments and move this back to normal support/product metrics. The shipped headline stays “Connect your first repo,” the teammate-invite clarification stays support-only, and new product-copy work needs a real metric or support-volume regression.