Scaling creative production in small cultural organizations is a structural challenge, not just a creative one. The problem usually isn’t a lack of tools—Canva is excellent for what it is—but the manual overhead required to maintain brand governance when resources are stretched thin. At Østfoldmuseene, the goal was to find a way to maintain our visual identity without it becoming a burden on an already pressured staff.
The Systemic Tension
Manual asset production is a high-entropy process. When a workforce begins to contract while task lists grow, the “manual design grind”—copying strings, adjusting margins, and double-checking templates—becomes more than just a task; it becomes a point of failure. It is a process that demands a level of meticulous attention that is hard to sustain in a high-pressure environment.
The challenge was to build a bridge that could carry that weight, allowing the humans in the system to focus on the cultural mission they were actually hired to serve.
The Architectural Decision
I chose to build a lightweight automation layer—a minimalist bridge between our data and our design. By codifying brand rules into a simple PHP and CSS engine, we moved the repetitive parts of visual judgment into the infrastructure itself. Using a “Vibe-Coding” approach, we were able to iterate through layouts with speed, focusing on system logic rather than manual syntax.
However, the most important architectural choice was the fail-safe. In a small, vulnerable institution, you cannot build fragile dependencies. I call it the “brick test.” If I were to get hit by a brick tomorrow, the system must continue to run silently for as long as the CMS API remains unchanged. And if the software eventually fails, the organization is not stranded; they simply revert to the manual way. The automation is an accelerator, never a trap.
Reflection: The Root Problem
By shifting the design process into code, we aren’t just trying to work faster; we are trying to build systemic reliability. A 98% reduction in production time is a secondary benefit. The real success is in protecting the institution’s capacity.
We solved a problem of scale by removing the constant tax of repetitive labor. This allows the organization to breathe, ensuring that even when resources are lean, the quality of our cultural output remains intact. We aren’t automating the creativity; we are automating the bottleneck to protect the space where creativity happens.
The Unresolved Thought
It leaves me thinking about the true mark of good architecture. Is it a system so advanced that it draws attention to itself, or is it something so quiet and reliable that the organization eventually forgets it is even there?
Comments (0)