Week 12 was presentation day and everything the project had been building toward for the past twelve weeks came down to ten minutes in front of a panel of industry professionals. How that day went is documented in full in the Panel Pitch and Client Presentation sections of the project notes, but in short it went better than I had expected and better than I had any right to feel confident about going in given the nerves I was carrying.
What struck me most in the room was how naturally everything came out. The months of research, the governor's pushback, the rehearsal, the late nights going over the concept until I knew every corner of it, all of that paid off in a way that felt genuinely earned rather than lucky. The concept landed. The panel responded. And the governor who had given us the most resistance came up afterwards to congratulate us. That felt like the best possible ending to a project that had tested us in ways I had not anticipated.
The biggest takeaway from this project and this module is the importance of truly understanding the space you are designing for before you start designing anything. It is rare that you will walk into a problem that exists in isolation. Almost every real world design challenge sits within an existing ecosystem with existing infrastructure, existing stakeholders, existing constraints and existing failures. Understanding that system deeply is not just useful preparation, it is the work. It shapes what you design, how you design it and sometimes whether the thing you thought needed designing is actually the right intervention at all.
For Flare that understanding came from the competitor analysis, the mentor interview, the B2B communication research and the cost modelling. Each of those built a more complete picture of the ecosystem the solution needed to live within. And the solution that emerged was not a new app or a new organisation or a new policy. It was a quiet intervention that attached itself to something already happening and made it do more. That only became possible because we understood the system well enough to know where the gap was.
I really enjoyed thinking through this project with a systems hat on, approaching the problem by asking how a solution could be as frictionless and invisible as possible rather than how it could be the most visible or the most ambitious. That way of thinking felt natural to me in a way I had not expected and I want to carry it into future work.
Whether I am working on a product or a service, in a studio or a professional environment, I think systems thinking is one of the most valuable perspectives you can bring to a problem. It stops you designing in isolation, it keeps the solution grounded in reality and it produces outcomes that are more likely to survive contact with the world they are being released into. In the future I want to apply that thinking earlier and more deliberately, not just as a lens for one particular type of project but as a default way of approaching any design challenge from the start.
<aside> 💡
Sitting here at the end of week 12 this module feels like the one that has changed how I think about myself as a designer more than any other. I came in expecting it to be about interfaces and journeys and I left having spent twelve weeks inside the mechanics of a broken system, arguing for a solution in front of a prison governor and genuinely caring about whether Dean gets his pause button.
That shift, from designing surfaces to designing systems, from thinking about how things look to thinking about how things work and who they work for, feels significant. I do not think I will approach a design brief the same way again. And I think that is exactly what a module like this is supposed to do.
</aside>