You don’t need to know how to draw to use a comic to solve your documentation problems.
As projects become more and more complex, it becomes crucial to provide stakeholders with approachable and easy to digest design concepts.
Many teams try to use requirements documents, personas, user scenarios, and storyboards to define products. However, I’ve often found stakeholders misinterpret these documents or in some cases, don’t read them at all.
As it turns out, many companies include Yahoo!, Sun Microsystems, and Sprint have experimented with using comics as a technique for communicating the core concepts behind a design's intended experience.
In this full-day seminar which has been refined over the past few years and featured in Jared Spool’s User Interface 12 conference last fall, I will share how this technique has worked well to get teams informed and on the same page. I'll demonstrate an in-depth walkthrough of my process and the advantages I’ve found using comics over other methods.
In this workshop, I will cover a number of topics in depth, including:
At the end of the workshop, you should be able to utilize this methodology for future products or features within any team structure or environment.
Discussions about this years conference are still ongoing on our CrowdVine community site.