It is almost a truism that system stakeholders do not fully understand and communicate what they want, often until a system is produced and they see it isn't right. Such an outcome is wasteful, expensive, and unsatisfactory. Working with requirements in comic book style provides affordances, absent or weaker in other requirements forms, that may as- sist stakeholders in surfacing and expressing desires sooner and developers in understanding them and each other. Appropriate incorporation of comic book style artifacts into requirements work, in addition to making it more playful and enjoyable, can contribute to greater stakeholder satisfaction and more effective software development.