Summary: This article explains how senior designers and Heads of Design move work from vision to approval inside real organizations. It shows that design influence depends not only on creating strong solutions, but on understanding approval chains, stakeholder incentives, risk, accountability, and limited executive attention. The article explains two essential communication modes: storytelling for alignment and business framing for decisions. It also explores common organizational scenarios, including direct decision makers, approval chains, accountable stakeholders, delivery-focused cultures, and executive-level communication. The core message is that design leadership means intentionally shaping how decisions travel through the organization so that good design outcomes survive real-world constraints.
There’s no shortage of content about designer visibility, communication gaps, and how to create influence without formal ownership. Some of it is genuinely advanced and worth reading, like Marina Krutchinsky’s work because it shows what “high-level practice” looks like in real organizations.
But if you’re still building your communication skillset inside complex product environments, it’s worth starting with the basics first:
- Visibility is not about being loud — it’s about being legible inside the organization b)
- Influence is not a personality trait — it’s something you design intentionally c)
- Communication is not a soft skill — it’s a leadership capability
This article focuses on those foundations.
Social Media Posts Don’t Build Capability — They Trigger It
Short-form content is useful, but it’s not an educational asset alone. Most Social Media posts act as prompts: they raise awareness, name a problem, or point at a pattern. That’s valuable, but it’s not the same as building the capability to act differently inside a real organization.
- Awareness doesn’t change behavior by itself
- Capability grows through repetition, feedback, and uncomfortable practice
- No mentor, framework, or template replaces doing the work in context
Mentorship helps when you’ve already accumulated fragmented knowledge and need help structuring it, or when you feel stuck and can’t see your next learning edge. What it won’t do is integrate knowledge for you.
Trying to learn organizational communication without practicing it in real settings is a bit like learning to drive by playing a racing game. You’ll understand the mechanics, but not the consequences.
“Speak Business” vs. “Tell Stories” Is a False Choice
Design communication is often presented as a binary choice: either you speak “the business language,” or you become better at storytelling. In reality, these are two different modes of communication that serve different purposes.
- They are not competing approaches
- They solve different organizational problems
- Senior designers switch between them deliberately
The real question is not how you speak, but who you’re speaking to, what pressure they are under, and what kind of decision environment they operate in.
Two (or more) Communication Modes
Storytelling is a divergent mode of communication. You use it when you’re shaping direction, introducing a vision, or trying to build shared understanding around a problem or solution. It helps people see the bigger picture, align emotionally, and engage with uncertainty. Storytelling is what creates space for feedback and support, especially early in the lifecycle of an idea.
Business language, on the other hand, is convergent. It compresses complexity into decision-relevant input. You use it when time is limited, accountability is high, and the person you’re speaking to is primarily responsible for risk, cost, or outcomes. This is the language of trade-offs, ROI, dependencies, and impact. It’s the language approvals are made in.
Good design leadership is knowing when to move from one mode to the other — and doing it intentionally.
Real Organizational Scenarios (And How Senior Designers Handle Them)
The decision maker
When the person approving your work is also the final decision-maker, the dynamic is deceptively simple. There’s no approval chain to navigate, but there’s also no buffer. In these situations, senior designers tend to lead with business framing to establish relevance and credibility, and then use just enough storytelling to create alignment. The goal isn’t to co-design the solution together, but to make the decision environment clear and focused. Too much context can be as harmful as too little.
The approval chain
A more complicated situation appears when someone in the approval chain behaves like a decision-maker, even though they aren’t. Sometimes they already have a strong opinion about the solution, especially in organizations where design has historically been treated as visual execution. In other cases, they ask for multiple design options because the problem framing is still fuzzy and they feel uncomfortable committing. The leadership move here isn’t to argue about authority, but to protect outcome quality while keeping momentum. Inviting input, acknowledging their perspective, and allowing small areas of influence often creates enough perceived ownership to move past the bottleneck. This isn’t about politics for its own sake; it’s about creating psychological safety so that good decisions can survive the organization.
The accountable person
Another common pattern is when approval is influenced less by professional criteria and more by personal accountability. People make decisions under pressure from KPIs, bonus structures, promotion risk, or compliance exposure. In these cases, deep UX artifacts usually don’t help. What helps is reframing design value in terms of personal and organizational risk reduction.
In a flow redesign, for real example, approval stalled when we presented UX rationale and usability evidence. The moment we reframed the change as a projected reduction in false-positive handling time — with direct implications for operational cost and compliance throughput — the conversation shifted, and the decision moved forward without further debate about UX.
The delivery focus
There are also organizations where output is rewarded more than outcome. Delivery speed, visible progress, and shipping often carry more weight than measurable impact. Senior designers don’t fight this culture head-on. Instead, they translate outcomes into the language of delivery: less rework, fewer escalations, lower operational risk, faster iteration cycles. The goal is not to change how leadership thinks overnight, but to make outcome-driven design legible inside an output-driven system.
Surviving the layers
A quieter but equally important challenge appears when requests come from people who are not decision-makers themselves. In these cases, you’re not just designing a solution — you’re designing the story that will travel upwards. Senior designers take time to understand the incentives of the messenger, then equip them with a clear recommendation, explicit trade-offs, and business framing that will survive the next layer of scrutiny. You’re effectively designing the communication chain, not just the artifact.
Executive Level
At executive level, everything compresses. Attention is scarce, context is minimal, and stakes are high. Storytelling and business framing merge into a single narrative: why this matters now, what it enables, what it risks, and what it returns. Executives don’t need to understand your design. They need to understand what decision they are making and what the organization gains or risks by making it.
The Real Measure of Design Leadership
Designer visibility isn’t about being louder or more visible for its own sake; it’s about intentionally designing how your work travels through the organization, how it survives approval chains, competing incentives, and shifting priorities. At senior levels, the quality of your design is only part of the equation — the real measure of impact is whether good decisions make it through real-world constraints without being diluted, delayed, or derailed.
This isn’t presentation polish or communication theatre. It’s organizational design — and it’s one of the core responsibilities of design leadership.
More articles on Medium
More articles on Linkedin
