Getting a good idea accepted is about more than the idea itself. It has to survive the distance between what we meant, what someone heard, what they assumed, and what they're actually able or willing to support.

Have you ever proposed a technical idea that seemed obviously worthwhile, a better architecture, a new tool, a process improvement, some long-overdue refactoring, only to hear "that won't work", "we tried that before" or perhaps the most dangerous response of all: "sounds interesting, we'll think about it"?

So you explain it again. With more data, more arguments, another diagram. Surely, once people understand the facts, they'll agree.

But they don't.

Being technically right isn't enough. People interpret the same proposal through different experiences, priorities, fears, incentives and assumptions. What looks like an obvious improvement to you might look like risk, extra work, loss of control, or simply the wrong problem to someone else.

In this session, we'll explore why good ideas encounter resistance, and what you can actually do about it. We'll combine communication theory and psychology with practical techniques you can use in your next architecture discussion, team meeting or conversation with management.

We'll look at how to:
- recognize what is really behind resistance instead of immediately defending your idea
- uncover hidden assumptions and move from assumption to alignment to agreement
- ask questions that invite dialogue rather than make people defend themselves
- adapt the same idea for peers, teams, managers and business stakeholders
- use logic, emotion, credibility and framing without turning persuasion into manipulation
- distinguish miscommunication from genuine disagreement, because sometimes people understand you perfectly and still disagree

Expect communication models, psychology, some Aristotle, and practical examples. No Jedi mind tricks. Just a better understanding of why people say no, and what to do next.