WEWeekend Experiments

About

I'm a former engineer with two kids (about 1 and 3). We explore the world together — I want fun things to show them, and ways for them to notice how stuff actually works.

Weekend Experiments is the list of activities we ran at home that worked: the kids particularly enjoyed them, and each one demonstrates a physical phenomenon (or another clear bit of how the world behaves).

Most ideas never make the cut. What you see here are the keepers. Kits may come later if they help families gather materials — join the mailing list if you want that news.

Merch lives next door at Engineerdadcoffee.

FAQ

What ages is Weekend Experiments for?+

Ideas are curated for ages 1–5, with clear age bands on each card (like 1–2 or 3–5). Many activities flex younger or older with small tweaks — we note that when we know it.

How do you think about safety?+

Every tested idea includes a safety note (tasting, glass, slips, choking hazards, supervision). Adults run the session; kids explore within those boundaries. When in doubt, skip or adapt.

Will there be kits?+

Maybe later. Physical kits would be optional materials boxes for favorite experiments — handy if you want less hunting for supplies. The experiment guides stay on the site either way. Join the mailing list for news.

When are kits coming?+

Soon-ish. We are still proving weekly winners at home first. Join the kit waitlist if you want a heads-up when preorders open.

How messy are these?+

Each card lists mess level: low, medium, or high. High-mess ideas (like Density Layers) assume a tray, towel, and a willing kitchen. We flag that up front so you can pick the right day.

How do you choose what to publish?+

A dad runs sessions weekly with a ~1-year-old and a ~3-year-old. We keep winners, demote duds, and label status honestly: idea, draft, tested, or winner.

Indoor or outdoor?+

Both. Filters on the experiments page let you pick indoor, outdoor, or either. Weather and mess tolerance usually decide.

Will there be other languages?+

Later. English first while we nail the content. Multilingual support is on the roadmap once the core library feels solid.