From blank page to ready-to-use lesson plans.
Staff at the Boys & Girls Club were spending up to an hour building each daily program plan from scratch. We scoped and piloted a tool that hands them a finished plan in their own template, so that time goes back to the kids.
The problem
Youth development staff at the Boys & Girls Club were responsible for daily program plans: structured lesson plans that guide activities through the school day. Each one took 30 to 60 minutes to build from scratch in a standard template. With limited staff across three locations, that prep time came straight out of the time available for the kids.
- An hour a plan, every day. Building each program plan from a blank template ate 30 to 60 minutes of staff time.
- Time taken from the kids. Across three sites with limited staff, prep time was time not spent on programs.
- The same plan, over and over. Staff rebuilt similar plans from scratch every day, with no way to reuse the work.
We didn't write the code on this one. We ran everything around it: the conversations, the buy-in, the product direction, and the pilot. It's the process that became how Asylo works.
Where the method came from
This was 2023, the first time we ran the process that became Asylo's operating model. The pilot ran across all three sites and validated something bigger than the tool itself: the method of sitting with frontline staff, understanding the daily burden, and building something that removes it. The technical stack has changed since. The method hasn't: find the person losing time, understand what's at stake, build on real requirements instead of assumptions, and deliver something that works.
