ConfigDeck
Smashing Magazine Articles
Smashing Magazine

From Kickoff To First Concept: How To Turn Brand Strategy Into Visual Direction

Commentary on a Smashing Magazine announcement

Summary

Smashing Magazine published a detailed walkthrough of the 'pre-concept' phase of brand identity design — the work between kickoff and the first visual direction. The article focuses on workshop questions and exercises that force stakeholders to define vague brand adjectives before designers open Figma.

Smashing Magazine published a long-form article on the often-skipped phase between a brand strategy kickoff and the first visual concept. The piece, written from the perspective of a practicing brand designer, walks through specific workshop techniques for closing the gap between ambiguous adjectives like “modern” or “disruptive” and actionable design direction.

What’s actually new

This isn’t a product launch or a tool release — it’s a process article, so “new” here means new framework. The core argument is that brand projects fail not at the logo stage but earlier, when terms like “premium” or “bold” go undefined across a stakeholder group. The author introduces what they call the “pre-concept phase” and structures it into concrete steps: perception-focused workshop questions (e.g., “What should people believe about the company after seeing the brand for the first time?”), a competitor perception mapping exercise using two-axis positioning, and references to Jake Knapp’s Three-Hour Brand Sprint as a complementary method. The article also includes a FigJam-based Brand Workshop Toolkit linked from within the piece. Two real project examples — a health tech company selling to government medical institutions and a fintech team — illustrate how the same adjective can point toward opposite visual systems depending on audience context.

What it means for your config

This article lives entirely in the brand strategy and design process space. It has no bearing on developer configuration files, build tools, linting setups, or any toolchain config. There are no code artifacts, CLI commands, or integration points to consider. If your team uses design tokens or design system configs that flow from brand decisions, the upstream thinking described here might inform what values end up in those tokens — but the article doesn’t touch that layer at all.

Nothing to migrate, nothing to watch for breakage, nothing to wire up.

If you’re a developer who occasionally gets pulled into brand or product design conversations — or if you’re on a team where “the brand feels off” keeps delaying design system work — the perception questions and competitor mapping exercise in this article are worth reading directly. They’re practical enough to run in a single workshop session and could save cycles downstream when your design system’s color palette, typography scale, or component tone keep getting second-guessed by stakeholders who never aligned on what the brand was supposed to communicate in the first place. The linked FigJam toolkit is the quickest entry point.


Read the full announcement on Smashing MagazineFrom Kickoff To First Concept: How To Turn Brand Strategy Into Visual Direction