How The Curveball Lab Works
Five stages that work just like real challenges do. Each stage builds on the one before it, growing skills you can use outside the classroom or training room.
Immerse
Teams get a detailed problem with people to help, limits to work within, a budget, and goals. They learn the facts, figure out who is involved, check what they have to work with, and build a first plan. The point is to really understand the problem before trying to fix it.
The team gets the Clean Water Access Initiative brief: a small town needs lasting access to clean water in 12 weeks on a tight budget. They find where the water comes from, talk to people in the town, and look into ways to clean the water.
DisruptThe Curveball
A guide throws a curveball — a planned change like a supplier dropping out, a rule changing, new people getting involved, or the budget getting tighter. The curveball is realistic, not random, and works just like the surprises real projects run into.
The main water-filter supplier leaves the contract. The team has 48 hours to find another option while still finishing on time and staying on budget.
Adapt
Teams fix their plan, weigh their choices, write down the trade-offs, and make new decisions backed by facts. The platform keeps track of how their thinking changes — what changed, why, and what facts backed up each choice.
The team switches to town-run wells, changes their budget, updates how they work with the town, and writes down why this plan will last longer than the first one.
Reflect
On their own and as a team, people look back at what they got wrong, what they learned, and how their thinking changed. Teachers give feedback with scorecards you can set up for skills like adapting, teamwork, fair choices, and more.
Alex says: "I thought water problems were mostly about technology. Seeing how much trust and local politics mattered completely changed how I think about these projects."
Transfer
People plan to use what they learned in real life — at a job, in their community, or in school research. Check-ins at 30 and 60 days show whether the learning turned into action.
Alex plans to think about the whole system in future engineering work, and will figure out who is involved before looking at the tech side on the next project.