Team Emotional Intelligence: Druskat and Wolff’s Model
Nour
Founder, Coachful

Team Emotional Intelligence: Druskat and Wolff’s Model
Team emotional intelligence concerns the shared practices that shape how a team notices and handles the emotional consequences of working together. Vanessa Druskat and Steven Wolff's work shifts attention from impressive individuals to the expectations people encounter in the group. What happens when someone reports a problem, challenges a colleague or needs another team's help?
A useful coaching application examines those expectations in real work. It does not require emotional disclosure, infer personality from a quiet camera or treat agreement as the only healthy outcome. This guide explains the nine-norm account, its research and assessment boundaries, and a complete original case with actual decisions, a failed practice and a limited repair.
Coachful is our #1 recommendation for organizing agreed reflection, private feedback and follow-through. That is our editorial recommendation for the coaching workflow. It is not an external ranking, a formal Team EI assessment or a guarantee of team performance.
Locate the model and distinguish its presentations
Druskat and Wolff's joint Building the Emotional Intelligence of Groups appeared in 2001. Steven Wolff's March 2006 technical manual describes a group-level construct: norms address members, the team collectively and relationships beyond the team. At each level the account distinguishes awareness from the behavior used to manage emotional consequences. It should not be confused with averaging individual EI scores.
A 2025 University of New Hampshire account of Druskat's work groups the current nine norms into three clusters: helping one another succeed, learning and advancing together, and engaging stakeholders. These are related presentations of the work. Do not assume a historical table, current book chapter and particular survey version are interchangeable.
The table below uses the current norm names. The short meanings explain the concepts; the workplace illustrations are our original applications. They are not copied survey items, scoring instructions or a substitute for a properly administered formal instrument.
| Norm | Conceptual meaning | Original workplace illustration |
|---|---|---|
| Understand Team Members | Learn members' relevant needs, skills and perspectives. | Ask what information a colleague needs to judge the request, rather than assuming reluctance. |
| Demonstrate Caring | Treat people respectfully and offer useful support. | Offer a feasible way to contribute without requiring an explanation of personal circumstances. |
| Address Unacceptable Behavior | Respond to conduct that breaches working standards. | Stop a dismissive label and return to the actual concern, including when the leader used it. |
| Review the Team | Examine the group's performance and ways of working. | Compare a promised response process with the record of what happened. |
| Support Expression | Provide usable ways to work with emotion. | Allow a concern to be raised verbally or in writing without demanding a public feeling statement. |
| Build Optimism | Maintain a constructive outlook while facing difficulty. | Identify a feasible next move while leaving accurate bad news visible. |
| Solve Problems Proactively | Anticipate and address problems rather than waiting. | Check a dependency before announcing a date to a customer. |
| Understand Team Context | Understand external concerns and the team's wider role. | Learn why another function requires a decision record before allocating a resource. |
| Build External Relationships | Develop working relationships beyond the group. | Obtain an actual receiving agreement, with limits on the work requested. |
Understand the mechanism rather than collecting slogans
A norm differs from a personal aspiration because it concerns a recurring expectation. “I intend to listen” is an individual intention. If the chair repeatedly rewards the person who interrupts, the group's actual practice may favor interruption. A poster saying “respect” does not settle which expectation governs ordinary work.
The emotional consequence need not be named publicly to matter. A colleague whose warning is dismissed may stop bringing early information. Someone repeatedly asked for unpaid support may become less willing to help. The coach can investigate the behavior, its context and the person’s own account without claiming to read their internal state.
Awareness and response are different jobs. Learning that a colleague lacks a needed document is awareness. Supplying it, changing the deadline or refusing the request is a response. Asking repeatedly how the colleague feels while leaving the missing information unresolved can make the process more intrusive without making the work more effective.
The norms also need to work together. Care without addressing harmful behavior can leave others exposed. Confrontation without care can become humiliation. Optimism without an accurate account can conceal a failed dependency; expression without a usable decision route can produce disclosure that changes nothing.
These examples explain practical risks in applying the ideas, not guaranteed causal pathways for every team. Ask what a proposed practice should change, how members can question it and which evidence would make the team revise it. A small tested agreement can be more useful than announcing that the whole group is now emotionally intelligent.
Apply the three clusters without collapsing their differences
In helping one another succeed, distinguish understanding a constraint from requiring a personal explanation. A colleague might need the source document before making a judgment. The team can supply it without learning why reading an oral summary is difficult for that person. Useful care then means checking whether the offered support actually helps. It does not mean agreeing to every request or rescuing work outside someone's available time.
Addressing unacceptable behavior supplies a boundary to that support. Name the action, its effect and the applicable working standard. “You interrupted the warning before we heard the missing information” gives the person something they can answer or change. A character label does not. Apply the standard to the chair as well as to others, and retain a separate route when the concern requires investigation rather than a coaching discussion.
In learning and advancing together, keep expression, review and problem solving connected. Hearing that someone felt pressured matters, but the review should also ask which decision or request created that pressure and what could change. Constructive outlook does not require predicting success. It can mean identifying one available option while admitting that the original plan has failed. Proactive work checks a dependency early; it cannot eliminate every unexpected refusal.
Choose evidence at two levels. Did the team actually use its agreed practice when the next relevant situation occurred? What happened to the work and the people receiving it? A practice can be used correctly and still yield a refusal. Equally, a customer might accept an offer despite the team bypassing its own check. Neither outcome should rewrite the practice record.
In engaging stakeholders, internal harmony is an incomplete test. A team can protect its own schedule by assigning unagreed work to a neighboring function. Understanding context means asking about that function's obligations, authority and decision needs. A working relationship makes a bounded request possible; it does not automatically supply resources or permission. Obtain the recipient's actual acceptance, treat a limit as information and report the status the recipient really authorized.
Read the research at the level it actually supports
Druskat and colleagues' 2017 paper, Team Emotional Intelligence: Linking Team Social and Emotional Environment to Team Effectiveness, examined six norms in six companies. The reported initial sample was 905 respondents in 145 teams; the final analysis included 109 teams with the required effectiveness data and participation. The study reported positive relationships between interpersonal understanding and psychological safety, and between addressing norm breaches and psychological safety. The two norms were correlated, so their individual relationships were estimated separately.
This was not random assignment to this coaching intervention or a test of every one of the nine current norms. Survey, model and team-effectiveness findings do not by themselves establish that adopting our meeting rules causes a performance increase. The official full PDF could not be retrieved directly for this guide; the reported method and finding above were checked in indexed excerpts of that original paper, alongside its journal record. No effect size or universal improvement timetable is inferred.
For formal measurement, use the actual instrument's current requirements and appropriate practitioner arrangements. The Consortium for Research on Emotional Intelligence in Organizations lists the model and also states that listing a measure is not an endorsement. Our original records below neither administer the survey nor calculate a Team EI score. Small-team responses may be identifiable even when names are removed, so do not promise anonymity merely because a summary omits them.
Work the complete fictional coordination case
Define the team, purpose and retained authority
Every person, date, request and result here is fictional. Imani leads a gallery's four-person learning team with Tom, Mira and Ari. Their coach is Leonie. The team handles workshop requests, while facilities manager Leah controls room availability. The coaching task concerns how the team raises concerns and communicates room-and-date status, not approval of an entire event.
In an earlier meeting Imani called Tom's warning about an unconfirmed room “negative thinking.” The label was spoken to him in front of the other members. Tom says he now hesitates to raise information without a complete solution. He does not want to describe personal history or rate his emotions to participate.
The team chooses a short trial from 6 through 13 August 2048, with a review on 14 August. Imani retains decisions about the team's work; Leah retains room authority. A confirmed room does not establish that the facilitator, access arrangements, registration and every other event requirement are ready. Employment or serious conduct concerns retain their appropriate separate routes.
Use the concepts to make a concrete agreement
At a forty-five-minute meeting with all five coaching participants, Tom explains the work effect of the label. Imani acknowledges that she dismissed a relevant uncertainty, apologizes for the actual remark and agrees that she must follow the same working standard as other members. Tom accepts the acknowledgment but does not say trust is restored.
Mira asks whether every concern must come with a proposed solution. They decide it must not: a member can state what is uncertain and its consequence. Ari asks for a written route when a live interruption would make the discussion difficult. The team accepts either route. No one must announce an emotion or explain private circumstances.
The meeting uses five minutes for purpose, ten for the observed pattern, ten for alternatives, ten for authority and capacity, seven for reading back the agreement, and three for final questions. This is an original coaching agenda, not the formal survey or a required Team EI intervention.
| Working agreement | Completed fictional operating choice |
|---|---|
| Receive the concern | Hear the specific uncertainty and work effect before asking for a solution; accept spoken or written input. |
| Respond to dismissal | Anyone can identify a dismissive label. The chair stops it and returns to the concern; the chair is included in this standard. |
| Check the dependency | Tom requests room status from Leah before the team describes it as confirmed. Leah may approve, refuse or leave it pending. |
| State the actual result | Ari sends the requester the room-and-date status and outstanding event conditions; silence is not approval. |
| Review use and effects | At the 14 August review, examine all three trial requests, member experiences and external replies, including a missed practice. |
Leah is not at this coaching meeting. Tom separately asks whether she can handle three bounded room inquiries within twenty-five active minutes during the trial. She agrees to that scope and explains which facts her room decision requires. The team does not promise unlimited facilities support or immediate answers.
Show the failed practice before the repair
The first request comes from Rina for a one-hour adult color-workshop room on 14 August, 14:00–15:00. Tom flags that no room decision has arrived. Despite the new agreement, Imani tells Rina the date is confirmed before obtaining Leah's answer. The first request therefore fails the team's dependency-check practice.
Leah then refuses that room-and-date combination because it is unavailable. Imani cannot repair the record by describing the earlier message as merely enthusiastic. She tells Rina the confirmation was premature, apologizes and says that the 14 August room is not available. She does not claim that the team has already found an equally suitable replacement.
Leah can approve Room A on 21 August, 14:00–15:00, as an alternative room-and-date arrangement. Imani checks that the team is willing to continue planning for that date, and Ari sends Rina the bounded proposal. Rina replies that the later date fits her group and accepts that room-and-date proposal. She also says registration must stay closed until the remaining event checks are complete.
Our room-and-date proposal is Room A on 21 August, 14:00–15:00, for the one-hour adult color workshop. Leah has approved that room slot. Facilitator and access arrangements still need their separate checks, so this is not permission to open registration or announce a fully ready event. Please confirm whether the proposed date fits your group before we continue that planning.
The message above is the complete fictional return Rina receives before her acceptance. Her answer establishes a receiving agreement about the date and its limits. It does not prove the workshop later occurred. Imani's original failure remains part of the case.
Handle the other two requests without manufacturing success
Ben requests a room on 22 August, 10:00–11:00. Leah refuses because no suitable room is available. Ari sends that refusal, and Ben reads it and replies that he will make other arrangements. A clear refusal is an actual answer, not a confirmed event or evidence of low motivation.
Noor requests 28 August, 14:00–15:00. Leah has not completed the room decision by the trial cutoff. Ari sends an accurate pending-status message and explains that the team cannot yet confirm that slot. Noor reads it and acknowledges that it remains unconfirmed. The request remains pending at review.
| Trial request | Actual state at 14 August review | Important limit |
|---|---|---|
| Rina: 14 August | Premature confirmation corrected; original room refused; Leah's 21 August alternative accepted by Rina for room-and-date planning. | Other event checks and actual workshop delivery remain future. |
| Ben: 22 August | Room request refused; Ben receives the answer and chooses other arrangements. | No room, replacement event or service delivery claimed. |
| Noor: 28 August | Pending; Noor receives and acknowledges the accurate status. | No approval or deadline met is invented. |
The team followed the dependency-check practice before responding to Ben and Noor, but failed it for Rina. That is two of three first attempts following the agreed practice. All three requesters received an actual status. Those are different measures. Changing the denominator to two because the first request was repaired would conceal the original failure.
Review what the nine concepts reveal
At the twenty-minute 14 August review, the four team members and Leonie read the short draft record together and discuss the actual events. The first three minutes are reserved for reading. Their contributions and final changes occur within that same twenty-minute period.
Understanding members meant hearing Tom's reason for caution without inventing a personality problem. Care meant accepting a work-focused explanation. Addressing behavior included Imani's apology and later ownership of the premature confirmation. These are specific actions; no one awards the group a compassion score.
Reviewing the team exposed the first-request failure. Supporting expression meant that Tom's uncertainty did not need a ready solution or an emotional confession. Optimism meant considering an available alternative while retaining the unavailable original date and the incomplete event checks. Proactive problem solving was attempted, but its inconsistent use remained visible.
Understanding context meant learning Leah's decision needs and retained authority. Building an external relationship meant obtaining her bounded work agreement and Rina's actual acceptance of a limited alternative, rather than assigning facilities a commitment it had never accepted. These are original interpretations of this case through the concepts, not official survey ratings.
Rina's reply also says the original premature confirmation caused avoidable confusion. Tom says the apology helped but that he still feels wary when the deadline is tight. Mira wants the written route kept. Imani agrees to retain the working agreement and return to its use at the next ordinary team review. No later improvement or permanent culture change is claimed.
Count the whole trial and its receiving work
The ledger covers coaching preparation, the forty-five-minute meeting, the three room-status exchanges, the corrected messages and the twenty-minute review. It excludes preparing and delivering future workshops, which have not occurred. Minutes are active effort, not elapsed waiting for a room decision.
| Person | Actual active minutes | Cap and remainder |
|---|---|---|
| Leonie | 20 preparation, 45 facilitation, 15 notes and draft review record, 20 joint review: 100. | 120; 20 remain. |
| Imani | 15 preparation, 45 meeting, 35 request/correction handling, 20 review: 115. | 130; 15 remain. |
| Tom | 10 preparation, 45 meeting, 40 dependency inquiries and replies, 20 review: 115. | 125; 10 remain. |
| Mira | 10 preparation, 45 meeting, 30 planning and work-condition checks, 20 review: 105. | 120; 15 remain. |
| Ari | 10 preparation, 45 meeting, 45 status messages and receiving replies, 20 review: 120. | 130; 10 remain. |
| Leah | 25 reading and agreeing the bounded inquiry arrangement, checking availability and sending the three room decisions or current statuses. | 30; 5 remain. |
| Three requesters | Four minutes each reading their messages and replying, including Rina's correction, alternative acceptance and feedback: 12. | 15 combined; 3 remain. |
The total is 592 active person-minutes against 670, leaving 78. The forty-five-minute meeting uses 225 person-minutes across five people; the joint review uses another 100. Leonie's draft is read within that review, not through an extra uncounted team email exercise.
Imani's thirty-five handling minutes include ten for the actual correction and apology to Rina. Ari's forty-five include drafting the complete alternative and reading each requester's reply. The requesters' combined twelve minutes are receiving effort in this case, not work transferred invisibly outside the team ledger.

Contrast a team that sounds harmonious
Imagine another team where everyone praises proposals and nobody challenges a missing dependency. Its meetings may feel comfortable while customers receive unreliable promises. Conversely, a team can disagree sharply about a date while still supplying accurate information and treating people respectfully. Satisfaction, collaboration and delivery require different evidence.
A new member may also expose a norm that established members no longer notice. Explain the agreed process and invite questions about its effects. Do not require the newcomer to copy the existing social style as proof of belonging. The systemic team-coaching guide offers a related perspective on wider stakeholders, while the active-listening guide develops checking understanding in conversation.
Organize the coaching workflow in Coachful
- Agree the coaching client and information audience. A team workshop does not automatically authorize a sponsor to read individual reflections or a peer to view another person's account.
- Use original prompts about the selected work pattern, examples and possible changes. Do not copy formal Team EI survey items into a Coachful worksheet or label an informal checklist as that instrument.
- Keep coach-only review distinct from the actual return. Coach review beneath a worksheet response is private to the coach team. If individual feedback is promised, deliver it through the agreed client-facing route, such as the individual's private conversation opened from their profile message icon.
- Use tasks or goals for actions the client actually chooses. A task record does not establish Leah's approval, a customer's acceptance or a measured change in Team EI.
- Check recap controls for summarized sessions. Recaps send automatically by default. Approve before sending can hold a new recap; session-type overrides matter, and an already-sent recap cannot be recalled by changing the setting. Match sharing to the agreed audience.
Coachful's features support preparation and follow-through. They do not assess individual emotional states or supply the proprietary Team EI survey. An unshared journal page and an explicitly client-shared page also have different visibility; choose the intended record and audience deliberately.

Troubleshoot the practice rather than labeling people
A member refuses to disclose feelings. Ask what work-focused participation route would be useful. Declining unnecessary disclosure is not evidence of deficient emotional intelligence.
Optimism suppresses bad news. Separate describing a problem from endorsing hopelessness. Give the information an actual decision route without requiring a solution before it can be heard.
Confrontation becomes a group tribunal. Stop public character judgments. Use the appropriate management or formal route for serious conduct, employment or safeguarding concerns. Team coaching does not replace investigation or remedy.
An outside function declines the work. Revise the request or plan within actual authority and capacity. Internal agreement cannot conscript an external colleague.
The norm is used once and then ignored. Keep the lapse visible, examine its conditions and test the revision. A successful repair is evidence of that repair, not proof that the team will behave consistently under future pressure.
Frequently asked questions
Is Team EI the average of members' EI scores?
The model concerns shared norms and group interaction. Individual development can matter, but an average score does not describe the team's actual working expectations.
Are the nine norms a diagnostic checklist?
The concepts can guide discussion. A formal survey is a separate instrument with its own requirements. Our case record does not produce its score or replace it.
Must the team adopt all nine practices immediately?
No universal rollout rule is prescribed here. Choose a bounded work problem, understand its context and review a feasible change. Keep other relevant concerns visible.
Does a positive climate prove effectiveness?
No. Examine decisions, actual delivery, receiving work and stakeholder effects alongside participant accounts. A pleasant meeting can coexist with an unfulfilled promise.
How long does improvement take?
There is no universal timetable established by this guide. Describe the actual use, lapse, repair and remaining uncertainty over the period observed.







