Designing Programmes
Karl Gerstner
Pre-Reading Context
Creating consistent design across multiple assets requires systematic methodology. Gerstner's concept of "designing programmes" (systems) rather than individual pieces provides the framework for scalable design thinking.Key Comprehension Questions
- Programme vs. Product: What does Gerstner mean by designing "programmes" instead of individual designs? How does this change the designer's approach to problem-solving?
- Systematic Thinking: How does Gerstner's methodology ensure consistency while allowing for variation? What are the key components of his systematic approach?
- Rules and Flexibility: How does creating systematic rules actually increase creative freedom rather than limiting it? Provide examples from the text.
Connection to Current Work
- Collection Development: You're creating 25+ assets for your digital collection. How would you apply Gerstner's "programme" thinking to ensure visual consistency while maintaining individual asset interest?
- Component Systems: How do Gerstner's principles relate to modern design system thinking (like atomic design or component libraries in Figma)?