How Do I Get People to Listen to My Ideas at Work?

SHOW NOTES:

WorkLife Stories from School of WorkLife Episode: How Do I Get People to Listen to My Ideas at Work?

How do I get people to listen to my ideas at work is the question every capable person asks after watching a good idea get a polite nod and change nothing — and the answer isn't better ideas. People ignore ideas that arrive as information. An idea that shows them how you think is much harder to ignore.

Sam's research was a direct line to the truth, and it changed almost nothing. This is the story of the colleague who made a room lean in, and the three stories Sam found in years of research — the study that was right and ignored, the one woman looking for one button, and the reason he left teaching for this.

RESOURCES MENTIONED

Get the Seat at the Table — Professional Self-Coaching for Strategic Influence Tell the Three Stories That Turn Your Expertise Into a Voice People Listen To

Work With Me: Commissioned learning resources, speaking engagements, and organisational partnerships.

Transcript

Copy

Speaker 0:08

Sam knew the glaze well. He'd be presenting a finding — a real one, an important one — and somewhere around the second slide, he'd watch it happen. The polite nods. The eyes going slightly unfocused. Someone checking a phone. And then: "Thanks, Sam, really useful." And the room moving on to the thing it had been going to decide anyway. He'd started to wonder if he was just bad at presenting. He was to come to learn, the problem was never his slides. Welcome to WorkLife Stories from School of WorkLife. I'm Carmel O' Reilly. And today's episode is How Do I Get People to Listen to My Ideas at Work? — the question every capable person asks after watching a good idea get a polite nod and change nothing. This story is about Sam. And about the colleague he watched make a room lean in — doing the one thing he never did. The Glaze Sam was thirty-eight, a UX researcher, and very good at finding out what was actually true. He watched real people use the product. He saw where they hesitated, where they gave up, what they said they wanted versus what they actually did. His research was a direct line to the truth of how the thing worked — which, in theory, was exactly what the strategy meetings needed. In practice, he watched the glaze. He knew it well. He'd be presenting a finding — a real one, an important one — and somewhere around the second slide he'd see it happen. The polite attention. The nods. The eyes going slightly unfocused. Someone checking a phone. And then: "Thanks, Sam, really useful," and the conversation moving on to the thing it had been going to decide anyway. His research changed almost nothing. It was cited sometimes, in the way people cite a source to support a decision they'd already made. But it rarely shaped a decision. And the ideas he was most sure of — the ones that could have genuinely changed the product — landed the softest of all. He'd started to wonder if he was just bad at presenting. He'd taken a course on it. It hadn't helped, because the problem was never his slides. What He Was Actually Doing The thing that changed it was watching someone else — a colleague from the data team — present in a meeting Sam was also in. She had a finding much like the kind Sam brought all the time. But she didn't present it as a finding. She said: "Everyone was convinced the drop-off was a pricing problem — people saw the price and left. So the whole plan was about discounts. But when I actually followed what people did, they weren't leaving at the price. They were leaving at the delivery estimate. It was never about cost. It was about waiting. We'd been about to discount our way out of a problem that discounts couldn't touch." The room didn't glaze. The room leaned in. Someone said, "wait — where else are we assuming it's price?" And suddenly her finding wasn't a finding. It was a lens the whole room started looking through. Sam replayed it on the way home and saw exactly what she'd done, because it was exactly what he never did. She hadn't presented data. She'd told them how she thought — the wrong assumption, the surprise, the thing it revealed. Sam presented conclusions. She presented the journey to the conclusion, which is the part that carries the thinking — and the thinking is the part people actually lean in for. Why Ideas Get Ignored Here is the mechanism, and it has nothing to do with the quality of the idea. A finding asks to be believed. A piece of thinking asks to be followed. When you present a conclusion — users want X, the data shows Y, my research indicates Z — you're handing the room a claim, and a claim can be nodded at, filed, and left. There's nothing for anyone to do with it except agree or not. But when you show the room how you got there — what you assumed, what surprised you, what it turned out to mean — you take them on the thinking with you. And a room that has followed your thinking arrives at your conclusion as though it were partly theirs. They don't have to be persuaded of it. They watched it happen. That is the difference between an idea that gets a polite "thanks" and an idea that makes someone say "where else are we doing that?" It is not a difference of substance. Sam's ideas were right all along. It is a difference of delivery — and specifically, whether the delivery makes your thinking visible or keeps it hidden behind the result. You do not get listened to by having better ideas. Sam's ideas could not have been better. You get listened to when people can see the thinking that produced them — because the thinking is the thing they can actually use. What Sam Found He sat down and looked for the stories in his own experience, instead of the findings. He found three. A failure. Two years earlier, he'd run a beautiful study proving a feature the whole company was excited about would confuse the people it was meant for. He presented it as findings — clean, thorough, unarguable. They shipped the feature anyway. It failed exactly as he'd predicted, and by then nobody connected the failure to his study. He'd been completely right and completely ignored, and it taught him something he'd been slow to learn: a truth that stays in the report isn't a truth the business gets to use. A success. A redesign everyone wanted to pack with features. Sam had watched users drown in the existing complexity, and instead of presenting the usual report, he'd told the team a story about one specific person he'd observed — a woman who'd wanted to do one simple thing and couldn't find it under everything else. The room went quiet. They cut the feature list in half. Engagement climbed. What it showed him about himself: he doesn't study features. He studies people, and the person is what makes a room care. A passion. He'd come to UX from an unexpected place — he'd trained as a teacher first, and left because of one thing he could never make peace with: watching a learner decide they were the problem, when the truth was that something had been explained badly. That is still the whole of it. He cannot stand a person being made to feel at fault for a thing that was built without them in mind. That's why he does this work — so the person on the other side of the screen is never the one left carrying the failure. Three stories, none of them a study. All of them the truth about how he works. The Room That Leaned In The next big study, Sam didn't present as a study. The team was about to add a whole tier of features to a product Sam's research showed was already overwhelming people. He could have brought the data. Instead, when the moment came, he said: "Can I tell you about someone I watched last week? She spent four minutes looking for a button that was on the screen the whole time — she just couldn't see it under everything else. And I've made this exact mistake before: two years ago I proved a feature would confuse people, we shipped it anyway, and it failed exactly the way the research said it would. I don't want to be right and ignored again. So before we add twelve things — can I show you what happens to the one person who just wants to do one thing?" The room leaned in. He wasn't more talented that day. He was the same researcher, with the same studies behind him. He'd simply stopped handing them findings, and started showing them how he saw. Within a few months, Sam wasn't the person who reported research after decisions. He was in the room while they were being made — because the team had learned that the way he saw a problem was the thing they most needed before they chose. How to Get People to Listen: What Sam's Story Shows Don't deliver the finding. Deliver the thinking. A conclusion gets a nod. The journey to the conclusion — what you assumed, what surprised you, what it meant — is the part people lean in for, because it's the part they can use. Tell it through one person, not the whole dataset. Sam's room went quiet for one woman looking for one button. It never went quiet for a completion rate. The specific human detail is what makes a room care. Take them with you, don't hand them the answer. A room that watches your thinking happen arrives at your conclusion as though it were partly theirs — and nobody argues with a conclusion they feel they reached. The story you lead with is the one the moment needs. Uncertain room? The failure you can name. A misreading about to happen? The success only you can see. A question of what it's all for? Your passion. You bring all three; the moment tells you which. Being right was never the problem. Sam's ideas were right for years. Getting listened to isn't about better ideas. It's about letting people see the thinking that makes them worth acting on. You Already Have Ideas Worth Hearing Years of research held every story Sam needed. He'd never lacked good ideas — he'd lacked a way of sharing them that let people see the mind behind them. The failure that taught him what silence costs. The success that showed him people are what make a room care. The reason he does this at all. Yours are there in the same way — in every idea of yours that was right, and got a polite nod, and changed nothing. CLOSING That's today's story — How Do I Get People to Listen to My Ideas at Work? And if you want to go deeper, my third Professional Self-Coaching resource — Get the Seat at the Table, for strategic influence — is there when you're ready. All the details and links are in the show notes, or you can find everything at www.schoolofworklife.com. Remember: A conclusion gets a nod. The thinking that produced it is the part people lean in for — because it's the part they can use. Thank you for listening.