This was one of our earliest major engagements — and in many ways the one that shaped everything that came after it.

When a nationally recognized high school brought us in to replace their legacy administrative system — the central technology that every teacher and staff member touched daily — we spent time with as many stakeholders as we could find. Not because we had the right questions, but because we wanted to establish relationships. We wanted people to know that when they had something to say after the system launched, there was someone who would listen.

The initial rollout was a success. Then came the "but wouldn't it be better if..." conversations. Because we had built relationships before the system launched, we could turn frustrations into strategic conversations rather than complaints requiring fixes.

One teacher said she never had her grades finished until the last minute and that it would be wonderful to enter them from her living room in her pajamas. This was the early 2000s — web applications were not yet the norm. But the framework had the capacity for a web portal. We built one. Teachers entered grades from anywhere. A secure on-campus validation system ensured accuracy before anything was committed to the record.

The GPA discovery was more complicated. Multiple people were using the word "GPA" to refer to calculations that were not the same calculation. What looked like a disagreement about math turned out to be a problem of identity. Each GPA was serving a different purpose for a different audience. The solution was to give each calculation its own name — to brand it — so everyone was speaking the same language.

The web grade portal wasn't in the original specification. The multi-GPA engine wasn't in the original specification. None of the most important things we built were things anyone asked for at the start. They were things that became possible because we built something designed to adapt — and stayed in the room long enough to find out what was actually needed.