In the previous blocks, I have explored how storyboards can function as communication tools in group projects or in presenting complex topics to clients with simpler visuals. I have also discussed that storyboards are usually not the final product; they are simple sketches that help think faster, test ideas, or troubleshoot potential issues before investing more time and resources. I have reflected on the structure of storyboard blocks and how scenarios, personas, and annotations work together to make the sequence understandable and functional.
But reflecting on all of this raises a personal question: as designers, we naturally aim to produce the final project in the best way possible, and that is always our main goal. Yet, is it worth spending time developing a new system or refining the storyboard step when it does not appear directly in the final outcome? Could that time be better spent focusing on the finished design or another system? Storyboarding is a step that exists mostly behind the scenes, and its impact is often indirect, visible only in the quality of decisions, clarity of communication, or avoidance of mistakes.
Engaging with this question requires balancing two impulses. On one hand, investing in storyboarding can lead to better-informed choices, clearer communication with collaborators or clients, and a more deliberate design process. It allows for experimentation, supports problem-solving before resources are committed, and can reveal possibilities that are not immediately apparent. On the other hand, creating a new system or spending excessive time refining provisional sketches carries the risk of delaying the actual design work, without producing a tangible, visible outcome.
For me, the value of storyboarding lies in treating it as an investment rather than an extra task. Even if it remains invisible in the final project, it can shape the design in meaningful ways, clarify thinking, and prevent costly errors. The challenge is to recognize when developing a storyboard—or even a new form of visual language—is truly necessary, and when existing methods suffice. Not every project requires extensive experimentation, but at the same time, skipping this step entirely can mean missing insights that improve the final result.
Ultimately, this reflection raises further questions: when is the investment in storyboarding justified? How can we ensure that this behind-the-scenes work meaningfully contributes to the visible outcome? And how do we balance the desire to experiment and explore with the practical goal of producing the final project efficiently? These are questions I continue to consider in my own practice, as I weigh the unseen effort of storyboarding against the impact it can have on the design itself.
