Why we show clients two design directions, not one or three

The real problem: decision design, not just design

Most conversations about client deliverables focus on the design itself. The harder question, and the one that determines whether a project ships cleanly or drifts through a dozen revisions, is how you present the design for decision.

From our project work, the common failure isn't that the design is bad. It's that the client can't decide well with what they've been given. If you present one direction, they have nothing to compare it to, so feedback comes in as vague adjustments ("feels a bit flat," "want it more bold") and iterations drift without clear structure. If you present four or five directions, they get overwhelmed, default to the safest option to avoid a high-stakes choice, or simply defer the decision and the project stalls.

Two directions is a specific choice, not a compromise. Enough contrast to make the decision meaningful. Few enough to keep the conversation focused on the real trade-offs.

Design Direction vs Mockup vs Visual Identity (Quick Clarification)

These three terms get conflated constantly. Worth pinning down before going deeper:

- Design Direction is the strategic frame. Style, tone, the visual logic the brand will communicate through. It's the idea, not the execution.

- Mockup is the execution. A specific screen or layout rendered to show what the finished product would look like inside one direction.

- Visual Identity / Brand Guidelines is the broader system (logo, colors, typography, voice) that sits above a specific project. Inputs into Design Direction, not a replacement for it.

The two directions we present are at the Design Direction level. Each is expressed through a small number of representative mockups, but the decision the client is making is about direction, not about any specific mockup.

Why not one direction

Presenting one direction and iterating from there is tempting because it looks simpler. In practice, it usually produces worse work, for three reasons.

No comparison means no structure for feedback. When a client looks at a single design, they can only react to what they see. They don't know what it's compared to, so they can't say "I prefer this because X" with any specificity. Feedback comes back as "more modern," "less busy," "more energy," and the design team iterates in directions that may or may not match what the client actually wanted.

Iteration without direction drifts. Each revision nudges the design one way or another, but without a clear alternative to compare against, the cumulative drift often pulls the final result away from the original intent. Three weeks in, the design looks different from what was approved in round one, and nobody can point to exactly when it changed.

Scope expands invisibly. Revisions in a single-direction process tend to compound: one change triggers another, each seemingly small, until the total work done is far beyond the original scope. Two directions force the scope discussion to happen upfront, because the contrast makes the trade-offs visible.

Why not three or more directions

Three or more directions sound generous. In practice they produce worse decisions.

Decision fatigue is real. Research on consumer choice (from jam displays to retirement plans) consistently shows that more options produce lower decision confidence and higher deferral. When presented with too many alternatives, people don't carefully compare them all. They either pick the first one they react to, pick the safest, or postpone the decision entirely. None of these produce the client's actual best choice.

The third option is often designer-favorite territory. In agency practice, the third direction is frequently the one the designer personally finds most interesting, whether or not it actually fits the brief. This creates an unfair conversation: two brief-matching options and one "passion project" that distracts from the real decision.

More contrast between options doesn't help past a point. Two directions with clear, meaningful contrast give the client enough to think with. Adding a third option usually adds noise rather than signal, because the third is either too similar to one of the first two (redundant) or too far afield (irrelevant).

Presenting exactly two is a discipline. It forces the design team to think hard about which two directions actually represent the meaningful range for this brand, rather than hedging with a third option as a safety net.

The two directions we present

Every engagement produces these two:

Industry-Standard Direction

What it is: A well-crafted interpretation of what works in the category. Draws on conventions that users in this category recognize and expect. Safe in the best sense: users understand it immediately, it clears the baseline quality bar of the category, and it gives the client confidence that the work will perform.
What it's not: A lazy copy of competitors. A serious industry-standard direction interprets the conventions intelligently, adapts them to the specific brand's context, and executes them well. The craft is in the interpretation, not in reinvention.
When it's the right answer: For established brands with something to protect. For high-stakes launches where usability and recognition matter more than standing out. For categories where users have strong expectations and violating them creates friction (financial services, healthcare, utility apps).

Differentiation Direction

What it is: A direction that extends from the same brand fundamentals but pushes further, creating a more distinctive visual or experiential identity. Aims to be memorable in a category that often blurs together. Takes on more perceptual risk to earn more perceptual reward.
What it's not: A wild experiment disconnected from the brand. The differentiation direction is still grounded in the brand's values, audience, and business context. It's extended, not invented from scratch.
When it's the right answer: For early-stage brands that need to stand out to survive. For saturated categories where the industry-standard approach produces invisible work. For brands whose strategic position is built on being different, not better at the same thing. For launches that prioritize memorability over familiarity.

What both directions have in common

Both are serious, fully-developed proposals. Both are grounded in the same brand inputs (audience, business goals, brand guidelines). Both are technically feasible. Neither is a "safe fallback" or "designer's favorite." Each stands on its own as a valid direction, and the client's job is to decide which strategic stance fits the business better.

How we decide which direction to recommend

We present both. We also make a recommendation, backed by reasoning. Clients don't have to follow it, but refusing to recommend would be a form of evasion. The factors we weigh:

- Brand stage: Early-stage brands usually benefit more from differentiation, because invisibility kills early brands. Established brands often have more to lose from radical change, because they've built recognition capital that's worth preserving.

- Category dynamics: Crowded categories reward differentiation (every brand looks the same, the one that looks different gets noticed). Sparse categories reward standard approaches (users appreciate familiarity when there aren't many options anyway).

- Business goal: Retention-focused work tends to reward familiarity (existing users want continuity). Acquisition-focused work can reward boldness (new users need a reason to try you, and different is a reason).

- Risk tolerance: Some clients have the cultural and strategic room to take design risks. Some don't, for reasons that are completely valid (regulatory, shareholder, internal politics). Recommending differentiation to a client who structurally can't pursue it wastes everyone's time.

The recommendation is always specific: "Given [factor], we'd recommend the [direction] as the primary, and consider pulling [specific element] from the other direction to address [specific concern]." Generic "it's up to you" recommendations aren't recommendations.

The hybrid approach

In practice, the final direction is rarely a pure A or B. It's almost always a hybrid: one direction as the backbone, with specific elements from the other layered in to address specific concerns.

A common pattern: the client selects the Industry-Standard direction as the primary (because it's safer and more immediately comprehensible) but pulls the distinctive typography, color accent, or layout quirk from the Differentiation direction (to add memorability without the risk of a fully distinctive execution). The opposite hybrid also happens: Differentiation as the primary with Industry-Standard's navigation patterns retained (to keep usability familiar while the surface feels fresh).

The two-direction presentation is a conversation-starter for this hybridization, not a forced binary choice. Clients who understand this get more value from the process, because they can articulate what they want as "that, with this element from the other one" instead of "something in between."

Brand guidelines are inputs, not outputs

Some clients assume that because they have a brand bible or corporate identity guideline, the design direction is already decided. It isn't. Guidelines define the ingredients (logo usage, color palette, typography, voice). Design direction defines how those ingredients combine for a specific project, medium, and audience.

Two projects with the same brand guidelines can produce very different design directions, legitimately. A landing page for a cold audience and a support portal for existing customers have different goals, different content requirements, and different interaction patterns. Both use the same brand colors and typefaces. Neither is wrong.

So: guidelines are input to the two-direction exploration. Not a replacement for it. A complete brand bible still leaves open a range of valid design directions, and the job of the design team is to propose the two that best fit this specific project.

The payoff

Once the two-direction decision is made, the rest of the project gets faster. Both sides have a shared reference point ("the selected direction with X modification from the other one") that iteration rounds can refer back to. Feedback gets more specific because the client has vocabulary for what they want. Scope stays closer to original because the direction was decided upfront, not drifted into.

Two directions is a small discipline with an outsized compounding effect on project quality. The alternative (one option with open-ended iteration, or three-plus with decision paralysis) looks flexible but usually produces slower and less satisfying outcomes.