I watched a product lead refresh the same volunteer dashboard three times in one night. Not because the numbers had changed. Because one row showed a woman in Ohio who’d opened the lesson plan at 9:14, closed it at 9:21, and never clicked “I’m in” again. That one row is why she traded dashboards for volunteer discovery interviews.
That gap between finishing the plan and deciding whether to come back is where the real work happens. Everything else—agent pilots, sentiment scores, the roadmap the exec team keeps waving—sits on top of it like fresh paint over a crack.
She started running volunteer discovery interviews instead of polling the analysts. Simple questions. What made you hesitate? What were you staring at when you almost said yes? The answers didn’t fit on any slide. They just kept showing up.
The volunteer discovery interviews that replaced the roadmap review
Your weekly sync with the children’s director used to start with feature status. You swapped the first ten minutes for one standing question: “What kept a volunteer from finishing the lesson this week?”
The answers never matched the AI wishlist. One director described a volunteer who spent twelve minutes hunting the right craft supply list because the print button sat three clicks deep. Another mentioned the parent who texted at 9 p.m. asking for the memory verse because the app only showed it inside the full lesson flow. These were not nice-to-haves; they were the moments that decided whether the volunteer opened the app again.
Torres’s method insists the interview happens while the work is fresh. You started requiring the director to bring one screenshot or one printed page that showed the exact friction. The specificity forced the team to stop theorizing about volunteer experience and start seeing it. She scheduled the volunteer discovery interviews while the frustration was still fresh.
How One Captured Pain Turned Into a Narrow Shipped Tool
A single volunteer’s email thread became the artifact. She had printed the lesson at home, realized the take-home activity required glue sticks she did not own, and spent the next morning driving to three stores before the kids arrived. The director forwarded the thread with the subject line “this is why we lose people.”
You scoped a two-week build: a one-tap “what do I need to buy” list that pulled only the items marked as supplies, formatted for a phone note or a printed half-sheet. No new AI. No new dashboard. The tool shipped to 12 pilot churches. Volunteer completion rate on those lessons rose 19 percent in four weeks. The signal was narrow enough that the build stayed small and the measurement stayed honest.
The Weekly Rhythm That Keeps the Signal Fresh
You now run a 45-minute Friday call limited to three people: the children’s director, the support lead who sees the most tickets, and you. Each person arrives with one raw artifact—no slides, no summaries. You watch the artifact together for eight minutes, then spend the rest of the time writing the smallest possible test that would remove that exact friction.
Nothing goes on the roadmap until it survives two consecutive weeks of this filter. The discipline removes the political weight of executive requests and replaces it with a growing list of narrow, volunteer-validated problems. The AI pilots still exist, but they now compete for the same scarce build time as the glue-stick list. Most of them lose.
Your Turn: Apply This Today
- Pick the one children’s director or volunteer coordinator you already email weekly and ask her to forward one volunteer message or screenshot from the last seven days before Friday.
- Block 30 minutes on your calendar this week to watch that single artifact with her on a shared screen and write the smallest test that would remove the friction.
- Ship the test to no more than three churches and define success as one observable change in volunteer completion rate, not in NPS or sign-ups.
- Cancel the next roadmap review meeting and replace it with the same 45-minute artifact review, keeping the attendee list to three people max.
- Write down the exact question you will ask every week for the next four weeks and put it in the calendar invite so it cannot drift.
- Choose one AI pilot currently on the roadmap and ask the team to name the volunteer frustration it would remove; if they cannot name one from an actual artifact, move it to the bottom of the list.
The pattern in “The Tuesday the Children’s Director’s Inbox Became the Real Product Spec” and “The Fitness App a Pastor’s Kid Shipped Without Writing Code” shows the same result: the smallest shipped change that comes from watching real labor beats the largest planned feature that never leaves the slide deck.
I consult with product leaders at ministry organizations on continuous discovery rhythms, volunteer friction capture, and narrow tool scoping. Let’s talk.