We Were Arrogant — And a School Administrator in Sneakers Proved It
The best solutions often already exist. They are just not in your building.
We thought we were the experts.
We had the degrees. The design reviews. The roadmaps. Twenty years of platform evolution behind us.
And still, a school administrator in sneakers and jeans solved the problem we couldn't.
The problem we kept avoiding
Our platform had a rights system — the kind that controls who sees what, who edits what, who manages whom. Simple in theory. A nightmare in practice.
The original architecture was built for a different era. Small schools, clear hierarchies, predictable roles. But schools grew. Org structures got messy. Suddenly you had teachers who were also department heads who also ran after-school programs across multiple campuses.
Our roles system couldn't handle it.
For years, we heard the complaints. For years, we debated solutions in high-level design reviews. We sketched hierarchies. We argued about edge cases. We built prototypes that never shipped.
We fell into the classic trap: thinking design happens in our office.
The visit
Then I went to see her.
She ran a school group with more staff than my entire village has people. She didn't yell. She didn't complain. She just turned her screen toward me.
"It didn't work," she said calmly. "So I hacked a workaround."
She had abandoned our entire roles system.
Built her own solution in Microsoft Power BI. Pulled our data through an export, restructured it the way she actually needed, and created a dashboard that let her manage permissions her way.
She wasn't waiting for us to fix it. She just fixed it.
What her solution looked like
Her approach was brutally pragmatic.
She exported user data from our platform weekly. Fed it into Power BI. Built a permissions matrix that reflected how her schools actually operated — not how our system assumed they should.
When someone changed roles, she updated a single row in her spreadsheet. Done.
No tickets. No waiting. No six-month roadmap.
What we did next
We scrapped our roadmap that day.
We didn't build our solution. We built hers.
Our engineers sat with her. They mapped her logic. They rebuilt our permissions system around the mental model she'd already validated — not the one we'd invented in a conference room.
Six months later, it shipped. The complaints stopped.
Not because we were clever. Because we finally listened.
The lesson I keep coming back to
Real product design is not easy. But sometimes, we make it harder than it needs to be.
We think the answer is in the code. In the whiteboard. In the next sprint.
Usually, it's sitting in an office 50 miles away, wearing a sweatshirt, waiting for someone to ask.
Stop trying to be clever. Start listening.
The best solutions often already exist. They're just not in your building.