Creative brand
concept & strategy
in New York

A brand concept usually arrives as a set of images. A logo sketch, a colour palette, a few mockups of a website and a sign. The images get the attention. The written rationale beside them gets skimmed. That is a mistake, because the rationale is the part that survives after the presentation ends.

Think about who reads it later. The designer who presented the concept will not be in every meeting. A new marketing hire, an agency that produces the campaign, a developer building the site and a board member who missed the workshop will all meet the concept through a document. If the logic lives only in the head of the person who presented it, the concept starts to drift within months.

A good rationale explains choices, not intentions. Intentions are easy and empty. Modern, bold, friendly, trustworthy. Every concept claims them. Choices are specific. The typeface is a narrow grotesque because the name is long and has to fit on a small app icon. The palette is warm because every competitor uses cold blue. The symbol is a simple mark because the product appears as a tiny favicon more often than on a billboard.

Each choice should connect back to something in the strategy. A positioning line, a customer insight, a practical constraint. When a reader can trace a visual decision to a reason, they can defend it. They can also tell when a later request breaks it. Somebody asking for a bigger logo on every page is easier to answer when the document says why the logo is small.

Keep it short. One page per concept is often enough, with a paragraph for the idea and a line or two for each major element. Long essays hide the useful parts. Plain sentences work better than design vocabulary. A founder should understand every line without asking what a word means.

Decide the format before writing. Some teams put the rationale on the slide next to each mockup, which keeps images and reasons together but makes the text too short to carry real arguments. Others write a separate memo that travels with the presentation file, which gives room for detail but risks being left behind when the deck is forwarded. A useful middle path is a short caption on every slide and a single page document attached to the same file, so whoever opens the concept later finds the reasons without having to ask for them. Name the file clearly and store it in the same folder as the source artwork, where people will look for it when they need to extend the brand to something new.

Write down what the concept deliberately does not do. Maybe it avoids photography of people. Maybe it never uses the symbol without the wordmark. Maybe it keeps a single accent colour. These refusals protect the concept more than any list of features does, because most damage comes from well meaning additions.

Include the weak spots honestly. Every concept has places where it is thin. Perhaps the typeface lacks a heavy weight, or the palette struggles on dark backgrounds. Naming them early lets the team plan the fix. Hiding them means they are discovered in production, under pressure.

The rationale also helps during the decision itself. Stakeholders who read the reasons before seeing the images tend to judge the fit with the strategy rather than personal taste. Send the text a day ahead. Then present. The conversation starts from shared ground.

After a concept is chosen, the rationale becomes the first chapter of the guidelines. It does not need rewriting from scratch. It needs updating as the concept grows into a full system, with each new rule linked to the same reasons. That continuity keeps the brand coherent long after the original team has moved on to other work.