We start on the outside and work in. That means understanding the people who'll use a product before considering how it should be built, so the insight we generate is grounded in what's technically feasible and commercially realistic from the start. Our designers work alongside engineers, product leads and data specialists, not separately from them.
We identified friction in the Schools Plus booking flow early, before significant development investment was made. The changes that followed improved conversion and avoided costly rework.
On Swaya, the design challenge wasn't just building an app students would use. It was balancing the need for meaningful feedback with the risk of making it feel like another chore. Two tensions shaped the design. First, how to avoid survey burnout. Second, how to prevent bias, whether from peer pressure or timing, like students rating homework poorly on a day a big assignment lands. The solution was to randomise and distribute questions across the student population over time. Each student gets different questions, removing the influence of peer pressure, and responses build up gradually rather than reflecting a single shared moment.
In each case, the design work didn't slow delivery. It made it more focused, more efficient and more likely to produce something that actually worked.