Rationale Overload

Rationale Overload is what happens when a designer walks into a brand presentation armed with their complete design process instead of a crisp business recommendation. You lay out every false start every abandoned direction and every rationale that eventually led to the system on screen. The deck becomes a 50 slide tour of your sketchbooks moodboards and late night iterations. The client nods politely for the first 10 minutes then their eyes glaze over. By the time you reveal the actual identity they have lost the plot. They pick apart the one detail they remember which is usually the color or the secondary mark you barely believed in anyway. The article How to Present Brand Identity to Clients Without Getting Destroyed identifies this as one of the three main reasons presentations collapse along with personal taste objections and scope creep. It kills more good brand identities than bad design ever could. The root cause is simple. Designers want the client to appreciate the sweat equity. Clients want to make a fast decision that aligns with goals they already approved in the brief. These priorities clash and the designer loses every time.

This problem shows up in the dissertation format the article warns against. Fifty slides of process. A history of the brief. Three concepts for exploration. Ten slides of rationale per concept. The logo reveal at slide 38. Then the silence that stretches while the client tries to figure out what they are supposed to do next. The client does not know how to respond because you have not framed the work as a decision. You have framed it as a story with too many chapters. Business decisions do not have chapters. They have clear recommendations and next steps.

What it isnt is zero explanation or expecting the client to trust your taste blindly. You still connect dots. You still prove the system solves the problems laid out in the signed brief. The difference sits in volume and focus. Strong rationale is surgical. This color palette signals premium quality because we anchored it to the principle of trust that the entire leadership team signed in the stakeholder workshop last quarter. Rationale Overload catalogs every color you rejected and why with hex codes cultural references from the 1998 Apple iMac campaign to the 1984 IBM identity and a detour through trends on Dribbble in 2021. One builds confidence. The other invites endless debate and scope creep.

Concrete example. Consider the disastrous 2023 presentation for a B2B software company called Pulse. The brief locked in three principles after weeks of alignment sessions. Clarity. Energy. And professionalism. The design team prepared 62 slides anyway. The first 22 walked through the entire rationale chain. We looked at these three type families. We killed this one because it felt too friendly for the enterprise audience. We refined the spacing on this logomark across 14 versions here are the prints. The head of sales jumped in at slide 14 to ask why the chosen blue was not the exact blue in their current PowerPoint templates from 2019. The conversation never recovered. The team spent the next month doing seven new directions none of which matched the original brief. The project budget ballooned 40 percent and the final identity felt like a committee decision instead of a strategic asset that could scale across their sales decks and conference booths.

We have seen identical failures at larger scale. The 2021 rebrand attempt for a national restaurant chain followed the same path. The agency showed their full exploration of 19 different illustration styles for the mascot. The founder who started the chain in 2007 fixated on an early rejected version that looked more cartoonish and reminded him of the original sign above his first storefront. He insisted they bring elements back. The presentation structure gave that nostalgia a place to live and the project died in committee six weeks later.

A third concrete example comes from a freelance designer working with a direct to consumer skincare brand called Lumina in early 2022. The designer was proud of their thorough process. They created a 38 page PDF deck that included scanned notebook pages from the first week of sketches and even some inspiration from a 2015 Pentagram project. During the Zoom presentation they spent 25 minutes explaining why they moved from organic shapes to a stricter grid system citing Bauhaus principles from 1923. The CMO who had approved the principles in the brief started to question whether the final lockup would work on their Instagram feed from a specific campaign they ran in summer 2021. She pulled up old posts and the meeting became a live redesign session. The original recommendation never got approved. The designer delivered three separate options in the next round and the client picked the weakest one based on personal preference. All because the rationale came before the recommendation and in far too much detail. The voxel diagram in the article shows the difference. One side shows the designer buried in stacked pages of rationale labeled defending a dissertation. The other shows the designer pointing at a single clear board labeled selling a decision.

When to use the counter tactics against Rationale Overload. Pull this knowledge out for every paid client presentation that follows a signed brief with locked approval criteria. Structure your deck exactly like the copyable outline. Context for five minutes where you read the brief verbatim. Principles for ten minutes where you translate each principle into a visual rule before any Brainy work appears. One direction for twenty minutes. Proof for ten minutes. Make every slide headline a business decision not a feature or exploration. The typography slide reads We chose this sans because it delivers the clarity principle we locked in the brief rather than Typography options explored. Run the meeting so the client agrees to the principles before any mark appears. This kills the oxygen that Rationale Overload needs to survive. Use this approach especially when your stakeholder map shows a CEO or founder with strong personal opinions or when the marketing director fears getting blamed for a bad launch. Those people respect strategy. They eat process porn for breakfast and then ask for changes.

When not to bother with sparse rationale. You can go deeper when creating internal case studies for your studio portfolio or when mentoring a junior designer on your team. Show them the graveyard then. Explain every turn so they learn what not to do in real rooms. The same goes for award submissions or speaking at design conferences like the HOW Design Live event where process stories earn standing ovations. Skip the tight constraints when the entire decision making group sat through all the discovery workshops and already knows the brief by heart. Even then keep it tighter than feels natural because you never know when a new stakeholder joins the call. Never unleash the full rationale dump on any client ever. It does not build trust. It broadcasts insecurity and opens the door to taste based feedback.

Stop defending your diary and start selling the decision the brief already approved.