User Research Plan
OneSummer
A structured program to validate five core assumptions before building further. Covers parent discovery interviews, camp director supply-side interviews, prototype walkthroughs, and usability testing — using Austin, TX as the proving ground.
Research Objectives
Every session targets one or more of the five core assumptions listed in Section 2. Objectives are prioritized by risk — the ones most likely to invalidate the current product direction are addressed first.
- O1 — Time savings reality check. Quantify how long parents currently spend finding, comparing, and applying to camps. Determine if "30 minutes to 30 seconds" is credible or directionally right.
- O2 — Calendar feature value split. Understand whether the visual calendar planner is a killer feature for Derek (phone-only, time-constrained) or only for Lisa (power planner). Would Derek use it or ignore it?
- O3 — Trust threshold for a profile vault. Identify what information parents will and will not pre-fill, what triggers trust, and what triggers abandonment — specifically around medical and insurance data.
- O4 — Director appetite for standardized forms. Learn what camps currently collect, which fields they consider non-negotiable, and whether a platform-managed form replaces or supplements their own.
- O5 — Willingness to pay. Establish whether parents frame the fee as a "service charge" (bad) or a "time-save" (good), and identify the acceptable price ceiling by segment.
- O6 — Prototype navigation clarity. Identify points of confusion in the 7-screen flow (discovery → calendar → profile → search → detail → apply → dashboard).
- O7 — Trust signals that matter. Learn which UI elements (reviews, badges, refund policy, SSL indicator, etc.) move the needle on perceived safety.
- O8 — Language and mental models. Capture the exact vocabulary parents use to describe the problem — words to use in copy, and words to avoid.
- O9 — Channel and timing context. Understand when and where (device, context) parents research camps — critical for Derek's mobile-first scenario.
Key Assumptions to Test
These five assumptions are the riskiest bets in the current product thesis. Each session is designed to either confirm, disconfirm, or refine one or more of them.
| # | Assumption | Risk if Wrong | Test Method |
|---|---|---|---|
| A1 | Parents will create a profile vault and trust it with medical information, insurance details, and emergency contacts. | High — Core value prop collapses if parents won't pre-fill sensitive data | Interview Q-set PI-4; prototype task observing profile screen (Screen 3) |
| A2 | The calendar planner is the killer feature — not just for Lisa but also for Derek, who is time-constrained. | Medium — Feature stays useful for one segment; marketing message must change if Derek doesn't care | Split interview paths; Usability Task 2; direct probe PI-2-D |
| A3 | Camp directors will accept a standardized application form instead of their own intake forms. | High — Supply-side refusal breaks the one-click apply promise entirely | Director interview DI-3; present mock standardized form for reaction |
| A4 | One-click apply saves meaningful time (30-minute process collapses to ~30 seconds). | Medium — Time savings may be real but smaller; still valuable but repositioning required | Interview Q-set PI-1 (baseline timing); Usability Task 3 (timed); post-task perception question |
| A5 | Parents will pay a $2.99–4.99 booking fee per application. | High — Without a monetization mechanism, the business model does not work; must find alternative | Interview Q-set PI-5; post-session survey SQ-7/8; Van Westendorp price sensitivity framing |
Research Personas
These three personas anchor every research question. The goal is not to confirm the personas exist — it is to stress-test each assumption against all three.
Target Participants
Parent Participant Criteria
- Parent or primary caregiver of at least one child aged 5–14
- Located in Austin, TX metro area (Travis, Williamson, or Hays County)
- Has researched or enrolled a child in at least one summer camp in the past 24 months
- Derek segment: Household income under $80k; primary device for personal tasks is a smartphone
- Lisa segment: Has 2+ children; has used a spreadsheet, notes app, or calendar to track camp options
- Available for a 30-minute video or in-person session between May and June 2026
- Works for a summer camp operator or camp-adjacent organization
- Has previously participated in OneSummer research
- Unable to share a screen or navigate a prototype URL during the session
Camp Director Participant Criteria
- Operates a day camp or overnight camp serving kids aged 5–14 in the Austin area
- Camp has been operating for at least 2 years
- Decision-maker or strong influencer on enrollment software and application processes
- Camp serves a minimum of 30 kids per session
- Available for a 20-minute phone or video call
Recruitment Channels
- Parent sessions (30 min): $25 Venmo or Amazon gift card
- Director sessions (20 min): No incentive needed — frame as a peer research call; offer to share findings
- Survey-only (5 min): Entry into $100 gift card drawing (1 in 20 chance)
Parent Interview Script (~30 min)
Part 1 — Warm-up & Context (5 min)
Part 2 — Camp Discovery & Research (8 min)
Part 3 — Planning & Calendar (7 min)
Part 4 — Application Experience (5 min)
Part 5 — Trust & Profile Vault (5 min)
Part 6 — Willingness to Pay (5 min)
Camp Director Interview Script (~20 min)
Intro & Context (2 min)
Current Operations (8 min)
Platform Fit (5 min)
Standardized Application Form (5 min)
Prototype Walkthrough
After the interview, share the prototype link: camps.coreyschuman.com. Ask the participant to think aloud throughout. Use a light "tourist" framing before usability tasks — let them explore before you assign tasks.
"I'm going to send you a link — it'll open in your browser. This is a clickable mockup, not a real app. Some buttons work and some don't yet. As you look around, please say out loud what you're thinking — what you notice, what you expect a button to do, anything that's confusing. There's no right way to explore this."
Screen-by-Screen Observation Guide
For each screen, capture the following: (1) what the participant says unprompted, (2) where their cursor/finger hovers before clicking, (3) any expressions of confusion or delight.
| Screen | URL | What to Watch For | Target Assumption |
|---|---|---|---|
| 1 — Discover | /01-discover | Do they understand the value prop within 10 seconds? Do they click the search or scroll to browse? | O6, O8 |
| 2 — Calendar | /02-calendar | Do they immediately understand the visual planner? Do they want to interact or just look? Derek-specific: "Is this useful to you or too much detail?" | A2, O2 |
| 3 — Profile | /03-profile | Where do they pause? What fields cause visible hesitation? Do they scroll past medical info or read it? | A1, O3 |
| 4 — Search Results | /04-search-results | What card information do they read first? What's missing from the card? Do filters make sense? | O6, O7 |
| 5 — Camp Detail | /05-camp-detail | Do they look for reviews? Do they look for price? What makes them click Apply vs. close the tab? | O7, O8 |
| 6 — Apply | /06-apply | Do they notice the profile pre-fill? Is the booking fee framing clear? Any payment hesitation? | A4, A5 |
| 7 — Dashboard | /07-dashboard | Does the confirmation state feel complete? Do they look for a receipt or next steps? | O6, O9 |
Usability Test — 3 Core Tasks
After the free walkthrough, assign these three tasks in order. Time each task from prompt delivery to task completion or abandonment. Capture verbal confusion points and dead-end clicks.
What to capture: Does the participant start from discovery or search? How many screens do they visit before declaring success? Do they use filters? What information makes them "pick" a camp?
What to capture: Can they find the calendar add action? Do they understand the visual result? Derek-specific follow-up after task: "Was that useful? Would you come back to that calendar view, or was it just a step you had to take?"
What to capture: Do they notice profile pre-fill and react positively? How long does the form feel vs. how long it actually takes? Do they hesitate on the booking fee? Is the confirmation state satisfying?
Post-Task Debrief (3 min)
Post-Session Survey
Send via Google Form within 1 hour of session completion. Takes approximately 5 minutes. The survey captures quantitative signals that are hard to get in a conversational interview — especially willingness to pay and NPS-style signals.
Demographics & Context
Time & Friction Baseline
Prototype Reaction
Willingness to Pay
Feature Prioritization
Open-Ended
Analysis Framework
Analyze after every 3 sessions — do not wait until all 15 are done. Early patterns may change interview direction for subsequent sessions. Use the following framework per assumption.
Assumption-Level Verdict System
- Confirmed (Green): 7+ of 10 parent participants validate without prompting. Signals are unprompted, specific, and consistent across segments.
- Partially Confirmed (Yellow): Signal is real for one segment (Lisa) but absent or weak for another (Derek). Assumption holds but scope narrows.
- Disconfirmed (Red): 6+ of 10 participants show avoidance, hesitation, or direct rejection. A disconfirmed assumption requires immediate product response.
- Inconclusive: Mixed signals. Run 3 more sessions with targeted probe before issuing verdict.
Per-Session Capture Template
- Capture exact words for A1 (trust language)
- Capture exact words for SQ-10 (problem framing)
- Note any spontaneous "I hate when..." moments
- Task completion times (T1, T2, T3)
- Scroll depth on Profile screen
- Hesitation points during Apply flow
- Mark A1–A5 as: Confirmed / Partial / Disconfirmed
- Note which segment gave the signal
- Flag contradictory evidence
- What did this session not answer?
- What new question surfaced?
- Adjust next interview script?
Affinity Mapping (Post All Sessions)
After all 15 sessions, run a full affinity mapping exercise on sticky notes (physical or FigJam). Cluster by: (1) Pain points, (2) Trust triggers, (3) Willingness to pay signals, (4) Calendar feature sentiment by segment, (5) Director concerns about standardization. Each cluster maps to one or more of the five core assumptions.
Priority Decisions the Research Should Unlock
- If A1 (profile vault) is disconfirmed: Redesign the apply flow to allow per-application form fill — one-click apply becomes a saved-info shortcut, not a mandatory vault.
- If A2 (calendar) is Partial (Lisa-only): Position calendar as a power feature, not the hero. Rewrite homepage copy for Derek around "apply in 30 seconds" not "plan your whole summer."
- If A3 (standardized form) is disconfirmed by directors: Pivot to a "smart import" model — pull from camp's existing form and pre-fill from parent profile. Directors keep their form; families save the re-entering.
- If A5 (booking fee) is disconfirmed: Test freemium model (free for families, charge camps for leads) before any other pivot. Do not assume "they'd pay more" without evidence.
First 10 Families Plan
Recruitment Target Mix
- 6 Derek-type parents (phone-primary, 1–2 kids, hourly or shift work, HHI under $80k) — recruited via Nextdoor and Austin Moms Facebook
- 4 Lisa-type parents (multi-child, planning-oriented, have used a spreadsheet or notes app for camps) — recruited via PTAs and Austin Moms Facebook
- Target 50% in-person (coffee shop / library), 50% remote (Zoom with screen share)
- Minimum: 4 completed sessions before any analysis; do not wait for all 10
Session Logistics
- Screener: 5-question Google Form linked in recruitment posts. Auto-disqualify non-Austin, non-camp-researching respondents. Reply to qualifiers within 24 hours.
- Scheduling: Use Calendly with 30-minute slots, 15-minute buffers. Offer morning, evening, and Saturday slots for Derek segment compatibility.
- Remote setup: Zoom. Ask participant to share their screen and open the prototype URL before the session starts. Have a backup link ready.
- Recording: Always ask permission. Record locally, not to cloud. Transcribe key moments only — full transcription is not necessary.
- Payment: Send $25 Venmo or Amazon gift card within 2 hours of session completion.
- Debrief: Write a 5-bullet session summary within 1 hour while memory is fresh. Update the assumption tracker after each session.
Deliverable After 10 Sessions
- Assumption verdicts (Confirmed / Partial / Disconfirmed) for A1, A2, A4, A5
- Top 10 verbatim quotes (the best direct-speech descriptions of the problem and reaction)
- Feature priority ranking from SQ-9 data
- Willingness-to-pay histogram from SQ-7/SQ-8 data
- Recommended copy framing for Derek vs. Lisa homepage variant
First 5 Camps Plan
Target Camp Profile
- Day camps preferred for round 1 (lower operational complexity than overnight camps)
- 50–250 kids per session — large enough to have an enrollment process, small enough to be nimble
- Austin metro: Travis County preferred; Williamson and Hays County acceptable
- Mix of: arts, STEM, sports, and general interest camps — avoid one-category concentration
- At least 2 camps that currently use a third-party enrollment platform (CampBrain, Active Network, Jackrabbit, etc.) — to test integration feasibility
Outreach Sequence
- Identify 20 camps from Austin Camp Guide, the Austin Chamber list, and Googling "summer camp Austin [activity type]." Build a simple spreadsheet: camp name, director name, email, size estimate, current enrollment tool (if findable).
- Send cold email (Week 1). Subject: "5-min call about how Austin families find camps — sharing findings with participants." Keep to 3 sentences. No product pitch. Position as peer research.
- Follow up once (Day 5). One-sentence nudge. If no response after follow-up, move to the next camp on the list.
- First call framing: "I'm doing research on camp enrollment processes — specifically how families find camps and how directors manage applications. I want to understand your world first. I'll share what we're building at the end and get your honest reaction."
- After call: Send a one-page summary of what you heard (anonymized). This builds goodwill and positions OneSummer as a thoughtful operator, not a cold vendor.
Key Questions the 5 Sessions Must Answer
- What are the 5–8 fields that every Austin area camp considers mandatory for enrollment?
- How many camps use a third-party enrollment system, and how integrated is it with their operations?
- What is the real blocker to accepting a third-party application — data format, liability, control, or distrust?
- Would directors accept a "shared application" model if they can add 3–5 custom fields?
- What would make a camp actively promote OneSummer to families instead of just tolerating it?
Deliverable After 5 Sessions
- Assumption verdict for A3 (standardized form)
- Candidate standard field list — the fields every camp needs, likely candidates to include in the OneSummer application data model
- Inventory of "non-negotiable custom fields" — what camps insist on adding (informs custom fields feature design)
- Director acquisition channel hypothesis — which value prop gets a director to say yes (net-new families? admin time savings? visibility?)
- 2–3 camps willing to participate in a pilot as early partners
Research Timeline
All 15 sessions should complete within 5 weeks. Interim analysis after session 5 (week 2) and session 10 (week 4) ensures findings can influence subsequent interviews.
This research program is successful if, at the end of Week 6, we can make a confident go/no-go decision on each of the five core assumptions — and we have enough verbatim evidence to write a compelling one-page problem statement that a first-time reader understands without context. If any assumption is disconfirmed, success means having a clear recommended pivot, not a crisis.