I've spent the last 15 years creating and sustaining learning environments that trust children. I co-founded the Agile Learning Centers network, helped launch the Alliance for Self-Directed Education, and since 2014 I've led operations at a large microschool in Charlotte, North Carolina. I've watched kids build businesses, teach themselves to code, spend months obsessing over marine biology or chess or historical warfare, and develop into thoughtful, capable people without anyone handing them a curriculum or a grade.
I know this works. The people in this space know it works. We see it every day.
But for over a decade, I struggled with something that I think everyone in this space struggles with: how do you capture and communicate the depth and richness of learning in environments where it's authentic to each child, not derivative of some monolithic academic agenda?
The Documentation Problem
Every learning community I've been part of has struggled with this. We all take pictures. We all have some version of the story where educators snap hundreds of photos throughout the week, maybe post a few to a Slack channel or a shared Google Photos album, and then most of it just sits there. At the end of the year, someone spends a painful weekend pulling together a yearbook or a parent report from fragments scattered across five different apps.
We tried everything. ClassDojo, Seesaw, shared drives, blogs, wikis. None of them understood our experience. They were built for classrooms with one teacher, one age group, one curriculum. In a microschool, five kids of different ages might be deep in a project together and you want to capture that moment for all five of their portfolios in one step. A parent might document something that happened at home over the weekend. A tutor who comes in twice a week might add their observations. The tools we had couldn't do any of that without a painful workaround.
And then there was the portability problem. We'd spend years building documentation for a child, rich observations and narratives and photos, and when that family moved on, all of it stayed locked in whatever platform we were using. The learning belonged to the child, but the record of it belonged to the institution. That felt wrong.
These aren't abstract problems. They're the daily friction that makes documentation feel like a chore instead of a practice, and they're the reason most educators in this space eventually stop doing it consistently. Not because they don't care, but because the tools make it too hard.
Building the Thing
Last year, I realized I had enough technical knowledge, and that the tools available to non-engineers had advanced far enough, that I could actually build what I'd been wishing existed for a decade. So I did.
Prism started as a solution to the specific, tactical problems I just described. A place where an educator can take a photo of five kids working together, tag all of them, write a quick note about what's happening, and have it land in each child's portfolio in one step. Where parents and educators and tutors can all contribute to the same learner's record. Where the portfolio belongs to the family, not the school; so when they move on, their child's learning history goes with them.
Those were the table stakes. But as I built and started using it with our school and then with other communities, something bigger started to take shape.
Making Learning Visible
Here's the deeper problem. A kid at our school got obsessed with betta fish. Over three weeks, what started as "I want a pet" turned into comparative research on species and breeds, tank volume calculations, a full budget proposal with ongoing costs, a persuasive presentation to the community, and eventually a self-taught crash course in aquatic ecosystems. She was doing real math, real science, real economics, real persuasive writing. But the educator capturing that moment in real time is just writing, "She's deep into a fish project this week. Did a ton of research." That's the honest observation, and it's exactly right for the moment. The question is what happens next.
In Prism, when an educator or parent captures a learning moment like that, Learning Signals surface the educational dimensions that are present in the experience: the subject areas, skills, developmental domains, and interests that are woven into what happened. Not replacing the observer's description, but expanding it. Making the structure visible without forcing the experience into a predetermined box.
You know the learning is real. You see it. But when a grandparent asks what your kid is studying, when a state evaluator needs documentation, when a teenager needs a transcript for a college application, you're stuck translating rich, multidimensional experience into language that a system built for standardized outputs can understand.
That translation has been entirely manual, and it's exhausting. Prism doesn't eliminate the human work, but it makes the translation far less painful by building structured data from unstructured moments over time.
The Bigger Challenge
This isn't just a tooling problem for individual schools. It's a movement-level challenge.
We're in the middle of something significant. School choice programs are expanding across the country. Microschools, learning pods, homeschool co-ops, and hybrid programs are growing faster than at any point in recent history. Educators are leaving conventional schools to build something better. Parents are discovering that their kids learn more deeply when they're free to follow their interests. There's more energy, more creativity, and more diversity in how people are educating children than I've seen in 15 years of doing this work.
But as these models become more visible and more publicly funded, the accountability conversation is coming. It's already here, actually. And if we don't articulate what rigorous evidence of learning looks like on our own terms, someone else will define it for us. The risk is that the same reductive metrics that drove so many educators and families out of conventional schooling — standardized tests, grade-level benchmarks, curriculum checklists — get imposed on the very spaces that were created to escape them.
The opportunity
The microschool movement doesn't need to prove itself on the old terms. It needs to define better ones. That means building tools and practices that can communicate the real depth and breadth of what happens when you trust children to lead their learning — in ways that are credible and legible to the outside world without flattening the experience into a single score.
What I Didn't Expect
The thing I didn't anticipate when I started building Prism was how much the tool would shape the practice, and how much the practice would shape the person doing it.
When you commit to capturing learning moments consistently, something shifts. You start noticing things you would have walked past before. The negotiation skills in how kids organized a game. The scientific reasoning in a question you almost dismissed. The persistence in a project that looked, from the outside, like a kid just messing around. Your first portfolio entries might be surface-level, and that's fine. Over time, your eye develops. You start seeing more, and what you see changes how you respond, what you offer, what you trust your kids to figure out on their own.
This is what I've come to think of as the practice of observation. It's not just documentation for the sake of record-keeping. It's a discipline that actively develops the educator or parent who engages in it. The more you observe, the more angles you develop, and the richer your understanding of each child becomes. Prism doesn't just store the output of that practice. It supports it, reflects it back, and over time, it makes you better at it.
That wasn't in the original product spec. It emerged from using the tool in a real learning community with real kids. Which, I suppose, is exactly how it should work in a product built for emergent learning.
Prism is a learning documentation and portfolio platform for microschools, homeschooling families, and self-directed learning communities. Learn more at prism.guide.
