It was uneasy drafting the project brief. I spent a lot of time articulating the problem space, and it made me slightly uncomfortable. It got me thinking the reason it took me so long to finish the brief.
At this moment, my primary struggle is: how can I communicate the conceptual problem to others? How do I demonstrate the value in solving the problems in a clear and comprehensible manner (without writing a fifty-page essay)? Earlier this summer, I had the thought of creating and distributing things that demonstrate the value of addressing such problem. After bouncing off ideas with friends, mentors, and professors this week, I’m more convinced that the approach will be promising.
But how much should I push to demonstrate the proof of concepts? After asking around and learning about the technical constraints and coding knowledge required to build possible MVPs, I (spent some time to get over with the fact that I can’t magically build something without learning to code, duh, and) learned that instead of pushing beyond prototypes, it’s more realistic to focus my time for the rest of the year on learning skills that will allow me to build and ship concepts.
Right now, my mind is extremely close to the problem. I felt the voice at the back of my head shouting to take a step back and bring my thoughts to the ground. By creating prototypes (interactive? writing? videos?), I could highlight the leverage points of particular moments in the complex problem space.
Starting next week, I will start working on the definition of problem space as I make sense of how and when I should make concepts into prototypes. I hope I can use the learning to update the brief. This relatively unconventional approach is different than any project that I have ever taken on at school or at work, but it is exactly what I was craving for. I can’t help feeling anxious, but also extremely excited.