Emotional intelligence is the ability to notice what is happening in oneself and in other people and to act on it well. The term was made widely known by Daniel Goleman in 1995, and the four domain version used here follows his later work. PMI includes it in the People domain because most project failures happen in a conversation. Projects fail far more often through misread stakeholders, unspoken disagreement and information nobody passed on than through anything technical, and every one of those failures happens between people.
It is treated here as a working competence, which means something that can be practised, observed and improved. The sections below describe the four domains, what each one costs when it is missing, how a room and a stakeholder are read and the two things the competence is regularly mistaken for.
The four domains of emotional intelligence
The four domains are laid out on two questions. The first is whether the attention is on oneself or on somebody else. The second is whether the person is noticing what is happening or doing something about it.
Each cell holds a thing somebody could watch a person do, which is the only form in which these domains can be practised or assessed. The left column is accurate reading and the right column is what the person does with the reading.
Self awareness is knowing what one is feeling while feeling it, and knowing what it is doing to one's judgement. The practical form is a project manager noticing that they are irritated with a supplier before writing to them, and that the irritation is really about a different meeting.
Self management is what happens next, and it consists of choosing the response. Suppression is the counterfeit, and it leaks through tone and timing where it cannot leak through words. A project manager who receives bad news without visible alarm is told the next piece of bad news earlier, and that is the whole of the practical payoff.
Social awareness is reading other people accurately, including the ones saying nothing. It covers empathy, and it also covers organisational awareness, which means knowing who actually decides, who has to be consulted before a decision sticks and which two departments have a history.
Relationship management is the output of the other three. Influencing, coaching, handling a disagreement and building the connections that will be needed before they are needed all sit here.
What each domain costs when it is missing
| Domain | The failure | Where it lands on the project |
|---|---|---|
| Self awareness | Not knowing that the irritation in this meeting arrived from the last one | A supplier receives a letter that costs a month of goodwill over a fault they did not cause |
| Self management | Reacting visibly to the first piece of bad news | The second piece arrives a fortnight later than it could have, by which point the options have gone |
| Social awareness | Reading the loudest person in the room as the room | A plan passes review with three people privately certain it will not work |
| Relationship management | Building a relationship at the moment something is needed from it | The dependency owner agrees in the meeting, deprioritises it that afternoon and tells the project manager in week nine |
Reading a room
The social awareness row is the one the examination tests most often, and reading a room is mostly noticing changes. Who has stopped contributing since the scope change was announced, which two people have started addressing their points to each other and away from the group, and whether the silence after a proposal is agreement or the sound of nobody wanting to be first are the things to notice.
The loud people are the easy signal and rarely the useful one, because somebody willing to say the thing in the meeting will usually say it afterwards as well. What is lost by missing the quiet ones is the objection that never gets another outing.
The reliable move when a reading is uncertain is to test it out loud and cheaply. Saying that the room has gone quiet and asking what is not being said either brings out the objection or establishes that there is none, and both outcomes are worth the ten seconds they cost. The alternative is guessing silently and proceeding, which is how a plan reaches sign off with three people privately certain it will not work.
Reading a stakeholder
The same reading applied to one person over time has three parts worth separating. What the stakeholder says they want is the stated requirement. What they are measured on is usually the better predictor of what they will defend when something has to give. What they are afraid of, which is often a repeat of something that went badly before, explains the requests that otherwise look irrational.
A sponsor who keeps demanding weekly detail is rarely interested in the detail. The request is usually about a previous project that surprised them late, and the way to meet it is to make surprise less likely. Larger tables do not help. This is what separates a competent reading from a courteous one. Courtesy sends the report that was asked for, on time and well formatted. Reading gets at what the report was for.
Why emotional intelligence belongs in a delivery role
The case is empirical. The failure modes on real projects are requirements two parties understood differently, a risk somebody saw and did not raise, a dependency owner who was never genuinely committed and a sponsor whose real objection arrived at the review. Scheduling technique and risk analysis leave every one of those untouched, because none of them is a calculation that went wrong.
The competence weighs more on adaptive and hybrid work than on predictive work. The coordination that a detailed plan used to carry is carried instead by frequent conversation between people who have to trust one another's information, so removing the plan means the relationships have to hold more.
The two things emotional intelligence is mistaken for
Agreeableness and emotional intelligence both produce calm meetings, and only one of them produces accurate meetings. The competence includes delivering the assessment somebody would sooner not hear, in a form they can act on, which is a harder skill than either bluntness or comfort.
Manipulation shares most of the same skills, and the distinction has to be held deliberately because it lives in intent. The difference is whose interests the reading serves. A project manager who reads a stakeholder in order to give them what they actually need is doing something quite different from one who reads them in order to get a signature.