# Example: user interview synthesis

## Filled inputs (abridged)

- `{{research_question}}`: Why do new team admins stop setting up the product in their first week?
- `{{interview_notes}}`: five sets of notes, labelled P1 to P5. Excerpt from P2:
  > "I invited two people and then realised I had to set up roles first, so I just stopped. I didn't want them to see everything." ... "I came back two weeks later when my manager asked."
- `{{participant_info}}`: P1 to P5 are team admins at companies of 10 to 80 people; P1, P2 and P4 signed up from a free trial, P3 and P5 were set up by sales.
- `{{decisions}}`: whether to redesign onboarding around roles before invites

## Sample output (trimmed)

### Key findings
1. **Admins pause setup when they are unsure what invited teammates will see.** (P1, P2, P4; strong)
   - P2: "I didn't want them to see everything."
   - P4 described hiding the projects list before inviting anyone.
   - Implication for the decision: supports offering role setup before or during invites.

2. **External prompts, not the product, bring paused admins back.** (P2, P5; moderate)
   - Both returned after a manager or colleague asked about the tool.

### Contradictions
- P3 invited 12 people on day one without setting roles and did not mention concern. P3 was set up by sales, which may have covered permissions on the call.

### What we did not learn
- Whether admins who never returned had the same concern (all five participants eventually returned).