Leadership is fundamentally about influence, and understanding how influence actually works is critical. Not the flowery, sanitised version from leadership books. Not the inspirational stories about charismatic visionaries. The real mechanisms by which people come to trust your judgement, adopt your ideas, and follow your lead.

This chapter dismantles common myths about influence and reveals the actual dynamics at play in organisations.

The Myth of the Better Argument

Many designers operate under what’s called the ‘better argument’ fallacy. The belief that if you just present strong enough evidence, clear enough logic, and compelling enough rationale, people will naturally agree with you. Build a solid case. Show your work. Let the data speak. Truth will prevail.

This is seductive because it aligns with how designers think. We’re trained to be evidence-based, to let data drive decisions, to build cases for our recommendations. We create research reports full of insights. We quantify impact with metrics. We show our reasoning. And in an ideal rational world, the better argument would win. Logic would triumph. Evidence would convince.

But organisations aren’t perfectly rational systems. Evidence, logic and objective merit matter. They’re necessary. But they’re insufficient. If you want to actually influence outcomes, you need to understand how it really works.

Example: The Data-Driven Pitch That Failed

At a healthcare technology company, a UX researcher named Max had spent three months conducting the most rigorous study of his career. The company’s flagship product was a patient portal that hospitals used to help patients access their medical records, schedule appointments, and communicate with doctors. However, usage was stagnant. Hospitals were adopting it, but patients weren’t using it.

Max conducted 40 in-depth interviews with patients. He ran surveys with 500 users. He analysed usage data from 50,000 patient accounts. He observed 15 patients trying to complete common tasks. The findings were clear and consistent across every research method.

The problem was identity verification. To access the portal, patients had to verify their identity by answering questions about their medical history (when was your last visit, what medication are you taking, who is your primary care doctor). This made sense from a security perspective. But patients couldn’t remember these details. They’d try to log in, fail the verification questions, get locked out, call their hospital’s IT helpdesk, and then give up in frustration.

Max’s data showed that 67% of patients who attempted to register failed identity verification on their first try. 43% never tried again. The company was losing nearly half of potential users at the registration step. The solution was obvious: use a simpler verification method like email confirmation plus a code sent to their mobile phone. Every other consumer application did this. Patients expected it. It was more secure than quiz questions anyway.

He built a comprehensive case. A 40-slide presentation with user quotes, usage statistics, competitive analysis, security research, and detailed recommendations. He quantified the business impact: moving to email and SMS verification could increase patient adoption by 40%, representing £2.3 million in additional annual revenue from hospitals paying per active patient.

Finally he presented to the product leadership team. The Head of Product, the Head of Engineering, the Chief Medical Officer, and the Head of Security. He was confident. The data was irrefutable. The business case was compelling. The solution was proven by every major tech company. How could they say no?

They said no.

The Head of Security explained that medical identity verification had specific regulatory requirements. Email and SMS weren’t sufficient for HIPAA compliance. The legal team would never approve it. Priya countered with research showing that other healthcare apps used exactly this method and were compliant. The Head of Security said, ‘Maybe they’re taking risks we’re not willing to take.’

The Chief Medical Officer worried about liability. What if someone gained unauthorised access to medical records? What if there was a data breach? What if the company got sued? Max showed statistics demonstrating that the current system was less secure because patients wrote down their verification answers. The CMO said, ‘But at least we followed established medical IT protocols.’

The Head of Engineering said the change would take six months because it required rebuilding the entire authentication system. Ma had worked with engineering beforehand and knew it would take three weeks. She pointed this out. The Head of Engineering bristled. ‘That’s an aggressive timeline that doesn’t account for proper security testing and integration with hospital systems.’

His presentation failed. Not because his argument was weak. Not because his data was wrong. But because he’d focused entirely on building a logical case whilst ignoring the political landscape. He hadn’t understood what actually drove the decision.

The Head of Security’s resistance wasn’t about HIPAA compliance. It was about risk. His entire job was to prevent security incidents. A breach on his watch could end his career. The current system might be clunky, but it was defensible. He could point to medical IT best practices and say he’d followed them. A new system, even if better, introduced uncertainty.

The Chief Medical Officer’s resistance wasn’t about liability. It was about the relationship between the company and hospitals. Hospitals were conservative. They valued stability over innovation. If the CMO pushed for changes that hospitals perceived as risky, it could damage his credibility with hospital administrators. His power came from being the bridge between product and healthcare institutions.

The Head of Engineering’s resistance wasn’t about technical complexity. It was about resource allocation. His team was already stretched. Taking on a major authentication rebuild meant delaying other projects he’d committed to. He’d look bad if those projects slipped. Better to make this seem hard so it wouldn’t be prioritised.

Max’s mistake was treating this as a rational decision when it was a political one. He needed to address the underlying concerns, not just present better evidence.

The Three Foundations of Influence

Influence rests on three foundations: credibility, relationships, and timing. Most people focus exclusively on the first whilst neglecting the second and third. All three must be present for influence to work.

1. Credibility: Earning the Right to Be Heard

Credibility is your track record of being right, being useful, and being reliable. It’s what makes people think, ‘If they’re saying this, it’s worth considering.’ It’s not the same as being liked. Plenty of likeable people have no credibility. It’s not the same as being senior. Plenty of senior people have lost credibility through bad judgement.

You build credibility through demonstrated competence. Consistently delivering high-quality work that solves real problems. Making predictions and recommendations that prove correct over time. Developing deep knowledge in areas that matter to the organisation. Following through on commitments, meeting deadlines, being someone people can count on.

Credibility is cumulative but fragile. Every project you ship, every insight you surface, every recommendation that proves valuable adds to your credibility account. Every missed deadline, wrong prediction, or failed initiative draws it down. Build it slowly, lose it quickly.

For designers, credibility often starts with craft. When your work is visibly excellent (when interfaces you design are intuitive, when research you conduct surfaces valuable insights, when systems you build scale elegantly), people start trusting your judgement beyond just the visual layer. Craft competence creates an opening for strategic credibility.

Max had research credibility. His studies were rigorous. His findings were reliable. But he lacked strategic credibility with this particular leadership team. He’d never successfully changed their minds on a major decision before. He was unknown to them beyond his research reports. His credibility account was empty when he tried to make a large withdrawal.

2. Relationships: Building Social Capital

Credibility gets you heard. But relationships determine whether people actively support your ideas or passively resist them. People are more likely to say yes to people they know, trust, and have positive history with.

Strong relationships create several advantages. Trust makes people more open to your ideas. Context from relationships gives you insight into what people actually care about, what they’re worried about, what constraints they face. Reciprocity means when you’ve helped people in the past, they’re more likely to support you now. Coalition-building becomes possible when you have relationships across functions.

Many designers underinvest in relationships, treating them as separate from ‘real work.’ But in organisations, relationships are the substrate through which work happens. Your ability to get things done is directly proportional to the quality of your organisational network.

Max had no relationships with the decision-makers. He’d never had a one-on-one conversation with the Head of Security before her presentation. He’d never grabbed coffee with the Chief Medical Officer. He’d never paired with engineering to understand their constraints. He was asking strangers to make a risky decision based solely on data. Strangers say no. Trusted colleagues consider.

3. Timing: Knowing When to Move

The same idea proposed at different moments can have completely different reception. Timing determines whether your influence attempt succeeds or fails. Great idea, wrong moment equals failure.

Good timing means understanding organisational readiness. Is the company in a mode where they can absorb change, or are they overwhelmed? Decision windows. When are decisions actually being made versus when are people just discussing? Political climate. What’s the current power dynamic, and is this the right moment to push? Stakeholder state. Are key people in a receptive mindset, or are they distracted, defensive, or exhausted?

Sometimes the most influential thing you can do is wait. Other times, it’s acting immediately before the window closes. Developing a sense for this requires paying attention to organisational rhythms and dynamics.

Max’s timing was terrible. He presented his research right after a security incident at a partner hospital had made headlines. The Head of Security was in full risk-aversion mode. The CMO was fielding angry calls from hospital administrators. Engineering was firefighting production issues. Everyone was stressed and defensive. They weren’t in a state to consider major changes. He basically walked into a minefield and wondered why he got blown up.

Example: Same Idea, Different Timing

Six months later, Max tried again. This time, he did things differently.

First, he built relationships. he started having monthly coffee chats with the Head of Security, not to pitch anything, just to understand his world. He learnt about the regulatory pressures he faced, the incidents that kept him up at night, the metrics his boss judged him on. He started pairing with engineering on small research projects, building credibility and trust with the Head of Engineering. He attended medical conference panels where the CMO was speaking, asked thoughtful questions, and followed up afterwards.

Second, he reframed the problem. Instead of ‘we should change authentication because patients struggle with it,’ he framed it as ‘we could reduce security risk and improve compliance by moving to two-factor authentication that patients can actually complete.’ Same solution, different framing. One emphasised user experience (which security and medical teams saw as secondary). The other emphasised security and compliance (which they saw as primary).

Third, he waited for the right moment. When the company landed a major hospital contract that required demonstrating security improvements, he had his opening. The Head of Security was looking for wins to show the new client. The CMO needed to prove the product was evolving. Engineering had just finished their big project and had capacity.

Fourth, he co-created the solution. Instead of presenting a finished recommendation, he asked the Head of Security, ‘What would a more secure authentication system look like to you?’ When the Head of Security suggested two-factor authentication, Max showed him his research supporting exactly that approach. the Head of Security felt smart for having thought of it because his ideas being incorporated made him feel ownership.

The decision took fifteen minutes. Same idea. Different approach. Different timing. Different outcome.

Within three months, the new authentication system was live. Patient registration success rates went from 33% to 87%. The Head of Security presented it at a healthcare IT conference as a case study in security improvement. The CMO used it in sales calls with hospitals. Engineering was proud of shipping it ahead of schedule. Everyone took credit. Max didn’t care. The work was done. The impact was real. That’s what mattered.

The Influence Equation

Here’s a simple model for thinking about influence:

Influence = (Credibility × Relationships × Timing) + Quality of Idea

Notice that the quality of your idea is additive, not multiplicative. A great idea with zero credibility, poor relationships, or terrible timing has limited influence. A ten out of ten idea with zeros in the other variables equals minimal impact. Conversely, a decent idea (say, six out of ten) proposed by someone with high credibility, strong relationships, and good timing can have enormous impact.

This is why you sometimes see mediocre ideas get adopted whilst brilliant ideas die. The equation explains outcomes that seem irrational when you focus only on idea quality. Politics isn’t the absence of merit. It’s the multiplication of merit by context.

The good news: you can improve all these variables. Credibility is built through consistent high-quality work. Relationships are built through genuine investment in people. Timing is learnt through observation and experience. And ideas can always be refined. You’re not stuck with whatever influence you have today.

Understanding Resistance

When your influence attempts fail, the instinct is often to assume your idea was wrong or your argument was weak. But resistance usually has deeper roots. Understanding why people resist is more valuable than strengthening your argument.

People resist for many reasons:

• Loss aversion: Your proposal threatens something they value (status, resources, control, certainty, autonomy)
• Competing priorities: They agree with you but have other fires to fight
• Different incentives: What you’re optimising for isn’t what they’re measured on
• Historical context: Similar ideas failed in the past, creating organisational scar tissue
• Identity threat: Accepting your idea requires admitting they were wrong about something
• Risk aversion: Change feels dangerous, and the status quo feels safe
• Cognitive load: They’re overwhelmed and can’t process another change

Understanding the real source of resistance allows you to address it directly. If someone is resisting because of loss aversion, more evidence won’t help. You need to address what they’re afraid of losing. If they’re resisting because of different incentives, you need to reframe your proposal in terms of what they care about. If they’re resisting because of risk aversion, you need to make the change feel safer.

This is where empathy becomes a strategic tool. When you truly understand someone’s position (not just their stated objection but their underlying motivations and fears), you can craft influence strategies that actually work.

Example: Turning a Resistant Stakeholder Into an Advocate

At a media company, a product designer named James wanted to improve the site’s accessibility. The business case was clear. Twenty per cent of the UK population has some form of disability. The current site was unusable for screen reader users, keyboard-only users, and people with colour vision deficiency. This wasn’t just about compliance. It was about reaching more readers and avoiding potential lawsuits.

But accessibility improvements rarely got prioritised. The Head of Product, Sophie, always said the same thing: ‘We’ll get to it after we ship these revenue features.’ Accessibility ended up in the backlog graveyard, perpetually deprioritised.

James tried the better argument approach for months. He shared statistics about disability prevalence. He demonstrated competitors’ accessible sites. He showed WCAG guidelines. He quantified the potential audience. Sophie listened politely and kept saying later.

Then James changed tactics. Instead of trying to convince Sophie, he tried to understand her. He asked her to coffee. Not to pitch accessibility. Just to understand what pressures she faced. What did success look like for her? What was her boss measuring her on? What kept her up at night?

He learnt that Sophie was under enormous pressure to grow subscription revenue. Her bonus was tied to it. Her promotion depended on it. The CEO asked about it in every weekly meeting. She wasn’t saying no to accessibility because she didn’t care. She was saying no because she had to say no to anything that didn’t directly drive subscriptions. Her incentives made accessibility invisible.

James reframed entirely. He stopped talking about accessibility as a compliance issue or a moral imperative. He started talking about it as a subscription growth opportunity.

He found data showing that accessible sites have 50% higher task completion rates for all users, not just disabled users. Clear headings, good colour contrast, and keyboard navigation help everyone. He found research showing that older users (who have money and subscribe at higher rates) disproportionately benefit from accessibility improvements. He found evidence that accessible sites rank higher in search engines because accessibility and SEO share the same foundations.

He built a prototype showing how accessibility improvements would make the subscription flow easier for everyone. He ran a small test showing that better colour contrast in the paywall increased conversion by 8%. He framed accessibility as a revenue feature, not a cost centre.

Sophie’s response was immediate. ‘Why didn’t you lead with this? Let’s prioritise it.’ Within two months, the site had proper heading structure, keyboard navigation, and WCAG AA compliance. Sophie presented it to the board as a growth initiative. Subscription conversion improved by 12%. Sophie got her bonus. James got his accessibility improvements. Everyone won because James understood that influence isn’t about better arguments. It’s about alignment.

The Power of Small Wins

Many designers make the mistake of going for big, transformative change all at once. Complete redesign. Comprehensive design system. Total process overhaul. This rarely works. Organisations are designed to resist large disruptions.

The more effective approach is accumulating small wins. Incremental changes that prove value and build momentum. Small wins work because they reduce risk perception, generate evidence that builds credibility, create advocates through positive experience, and establish precedent that makes bigger changes possible.

Instead of proposing a complete design system overhaul, start with one component. Instead of trying to change the entire product development process, run one pilot project with better practices. Instead of demanding a seat at the strategy table, contribute strategic thinking in smaller venues until your value is undeniable.

Small wins compound. Each success makes the next one easier. Over time, you can drive significant change through patient, persistent accumulation of progress. This is how informal leaders transform organisations. Not through grand gestures, but through relentless incremental improvement.

Influence Through Questions

One of the most underutilised influence techniques is asking great questions. Questions are powerful because they invite people to think rather than triggering defensiveness. They surface assumptions that might be wrong. They redirect conversations without direct confrontation. They create space for people to discover insights themselves.

Compare these approaches. Statement: ‘We should prioritise mobile first.’ This triggers debate. People defend their existing positions. You’ve created a fight. Question: ‘What percentage of our users are on mobile, and how does that compare to our development resources?’ This invites investigation. If the data shows heavy mobile usage with minimal mobile investment, the group reaches the same conclusion. But it feels like their discovery, not your mandate.

Powerful questions to develop:

• ‘What problem are we actually trying to solve?’ (Problem framing)
• ‘How would we know if this was working?’ (Success criteria)
• ‘What would have to be true for this to make sense?’ (Assumption testing)
• ‘What are we not seeing?’ (Blind spot identification)
• ‘Who else should be in this conversation?’ (Stakeholder mapping)
• ‘What happens if we do nothing?’ (Status quo examination)

The best questions don’t have obvious answers. They create productive discomfort that unlocks new thinking. They shift the conversation from positions to interests. They help groups move from debate to dialogue.

Conclusion: Influence as Practice

Influence isn’t a personality trait or a gift. It’s a skill developed through practice and attention. You can get better at it by studying how influence works in your specific organisation.

Start paying attention to influence dynamics around you. Who has influence beyond their title? How did they build it? When do your influence attempts succeed versus fail? What’s different in those situations? What resistance are you encountering, and what’s the real source? Where are your credibility gaps, and how can you address them?

The more consciously you practice influence, the more effective you’ll become. You’ll start to see the patterns. You’ll understand which levers to pull. You’ll know when to push and when to wait. You’ll build the relationships that create options. You’ll develop the credibility that earns trust.

And as your influence grows, so does your capacity to lead. Because influence is how leadership happens when you lack formal authority. It’s how designers move organisations towards better outcomes. It’s how you translate vision into reality. It’s how you lead.