Why I built this
The newsletter and the podcast are one directional. I talk, you read or listen. That has always bothered me, because the best part of this work is the conversation after: the "wait, how did you do that" and the "here is what broke when I tried it."
So this is the room for that conversation. I will be in here answering questions in Ask Chris, and the thing I most want to see is your posts in Wins: one workflow, the time it saved, how you built it.
Start with an intro below. Your role, and the one task that eats your week. That answer is usually where your first AI win is hiding.
How this place works
Three rules, all short.
1. No student data, ever. Not in posts, not in screenshots, not in DMs. Describe the workflow, strip the names.
2. Be specific. "AI is great" helps nobody. "This prompt cut my progress reports from 40 minutes to 10" helps everybody.
3. No vendor pitches. If you sell something, the value you add here is your knowledge, not your link.
That is it. Disagree with ideas all you want, stay decent to people, and post the real numbers when you have them.
Join The Evalve Community
Where educators who build get together. Ask implementation questions, share what you are building with AI, and compare notes with people doing this work in real schools, districts, and education organizations.





