Poster Brief Interpretation 225

title: "How I Read a Poster Brief Before I Touch the Software" description: "The questions I ask and the research I do before any poster concept begins." date: "2022-12-15" tags: "poster design","process","brief" draft: false

The biggest improvements in my poster work over the last several years haven't come from learning new software features or discovering new typefaces. They've come from the work I do before I open any software at all. The quality of a poster concept is almost entirely determined by the quality of thinking that precedes it.

Here's what that pre-production process actually looks like.

Interrogating the Brief

Most poster briefs I receive are underdetermined. They specify the content (event name, date, location, copy) and perhaps a general direction ("we want it to feel energetic" or "make it look premium"), but they leave the most important questions unanswered.

I ask:

What is the poster's primary job? Is it to drive ticket sales, build awareness, signal cultural positioning, or all three? The answer changes the hierarchy.

Who is the audience and where will they encounter this poster? Age, cultural context, and viewing environment shape every aesthetic decision.

What are the constraints? Budget determines print method, which determines color modes and material options. Venue constraints might determine format. Brand guidelines might constrain typographic choices.

What are the reference points? What does the client love? What do they explicitly not want? I always ask for three to five examples of work they admire and three they hate. This is more useful than any amount of written direction.

The Competitive Context

I look at every poster in the same genre, category, or community as the one I'm designing. Concert poster for a jazz venue? I look at what the venue has done before, what comparable venues are doing, and what the broader concert poster tradition looks like for this genre.

This isn't to copy — it's to understand the visual language I'm speaking and decide where I want to sit within it. Do I want to speak the genre's visual dialect fluently? Do I want to deliberately subvert it? Either is a valid answer, but I need to know what I'm doing and why.

Reference Collection

Before I concept, I spend time building a reference folder specific to this project. Not a moodboard — I find moodboards too loosely organized to be useful. A specific, annotated reference collection: these compositions, for this quality; these typefaces, for this register; this image treatment, for this feel.

The references are prompts and constraints, not templates. I'm not looking to reproduce what's in the folder — I'm using the folder to sharpen my understanding of what the poster needs to feel like.

A Constraint Inventory

I write down every constraint explicitly: format, color limitations, copy elements that are fixed, elements that are flexible, approval process, print timeline.

Constraints that feel frustrating at the start often become the most creatively productive elements of a project. Working within a single-color print budget has produced some of my strongest poster work because the constraint forced compositional and typographic decisions I wouldn't have made with more freedom.

First Ideas Without Software

Before I open InDesign or Illustrator, I sketch. Not polished drawings — quick diagrammatic sketches that capture compositional ideas. Where does the primary element sit? What's the scale relationship between elements? Is this image-dominant or type-dominant?

These sketches are fast and expendable. I'll make eight to twelve before I find one worth developing. The point is to generate options before I've invested time in any single direction.

Software is for execution. Concept development is better done with a pen and a willingness to throw ideas away.