<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Evelyn</title>
    <description>
This emotional data doesn't show up in spreadsheets, but it drives everything that does.
I worked with a manufacturing company where safety incidents spiked every quarter during budget reviews. Management couldn't understand the pattern until we discovered that financial uncertainty was making workers rush through procedures they'd normally complete carefully.
The solution wasn't more safety training – it was better communication about business performance and job security so people weren't operating from a place of anxiety about their future with the company.
The Meeting Room Meltdown
Last year I was facilitating a leadership team workshop when one of the participants had what can only be described as an emotional breakdown during a discussion about delegation.
Instead of addressing it appropriately, the CEO immediately called for a break and pulled me aside to ask if we could "skip the emotional stuff and focus on practical management techniques."
Here's what he was missing: the breakdown was directly related to practical management challenges. This person was drowning under excessive workload because they couldn't delegate effectively – not because they lacked technical knowledge about delegation, but because they were terrified of being seen as incompetent if they couldn't handle everything independently.
Their emotional response was providing crucial information about why standard delegation training hadn't worked for them. But instead of using that information to develop a more effective solution, leadership wanted to pretend it hadn't happened.
We ended up developing targeted emotional intelligence training that specifically addressed confidence issues around delegation and workload management.
Six months later, that manager was successfully leading a team of four people and had been promoted to senior leadership. But first, they had to work through the emotional barriers that were preventing them from applying practical management skills effectively.
The Australian Context
Working in Australia gives me an interesting perspective on emotional intelligence resistance. We have this cultural thing where acknowledging emotions feels un-Australian – too American, too therapy-focused, not practical enough.
But we also have strong cultural values around fairness, mateship, and looking out for each other. When you frame emotional intelligence as "understanding your people so you can support them effectively" rather than "getting in touch with feelings," it resonates much better.
The most successful Australian leaders I work with have developed emotional intelligence without calling it that. They're just naturally good at reading people, adapting their communication style to different personalities, and creating environments where people feel comfortable contributing their best work.
They don't use emotional intelligence terminology, but they absolutely use emotional intelligence skills.
What Actually Works in Practice
Effective emotional intelligence development isn't about sensitivity training or group therapy sessions. It's about practical skills like:
Recognising when someone's stress levels are affecting their judgment and adjusting your expectations accordingly
Understanding why certain communication styles trigger defensive reactions in different people
Knowing how to deliver criticism that improves performance rather than destroying confidence
Reading the emotional climate of meetings and adjusting your approach to get better outcomes
Managing your own emotional responses so you can think clearly under pressure
These are management skills, leadership skills, and communication skills that happen to involve understanding emotions rather than ignoring them.

</description>
    <link>https://speakerdeck.com/scoles</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/scoles.rss"/>
  </channel>
</rss>
