Help workshop visitors find a reason to return
Investigate a drop in repeat visits and choose one test without assuming reminders are the answer.
Product managers, founders and people shaping a new service.
Your approach: Write a problem brief, pilot plan, decision table or simple journey. A software architecture, API or app is not required.
The problem
A neighborhood arts center wants more people to return after a first free workshop. Develop a focused product proposal: decide what to learn, which change to test and what evidence would justify a next step. Explain why your proposal addresses a visitor need rather than only improving a dashboard.
- Of 80 first-time visitors last month, 12 attended again within four weeks. No reasons for leaving were recorded.
- Workshops have 20 seats; popular evening sessions fill while weekday sessions often have empty seats.
- A coordinator can support a four-week test with $600 and no added classes. Visitors may decline follow-up messages.
Work within these constraints
Declare test spending and account for each planned expense.
Required target: ≤ 600 dollars
Work within the current classes and 20-seat limit; avoid improving repeat visits by displacing everyone new.
Keep participation and any follow-up contact optional.
Separate observed behavior from a claim that the proposed change caused it; name an important uncertainty.
What to deliver
Problem hypotheses
Offer at least two plausible reasons for low return visits and choose a small discovery activity that could distinguish them.
One testable change
Describe the audience, benefit, smallest change, non-goals and why it follows from your evidence or stated assumptions.
Measures and decision
Define who counts in the comparison, how you will observe returns, a guardrail for new visitors and a continue/change/stop rule.
Delivery and tradeoff
Allocate the budget and coordinator’s work; explain one rejected alternative and what you would do if popular sessions fill sooner.