4.1.1: SEW Model (Sensation–Emotion–Want)

Mapping the Inner Signals of Risk

Why Human Risk Awareness Starts Below the Surface

Before any risk appears on a register, in a planning meeting, or in an incident report—it first appears somewhere less visible:

• A pause.

• A wince.

• A mental hesitation.

• A sudden need to justify something that didn’t feel quite right.

These signals rarely show up in technical documentation. But they are the first and most honest indicators of emerging risk. Yet because they are emotional, sensory, and subjective, they are also the easiest to dismiss.

To build a risk-aware team culture, we must treat these signals not as noise—but as primary data.

That’s where the SEW Model comes in.

---

The SEW Model – Sensation, Emotion, Want

SEW stands for Sensation → Emotion → Want, a three-step internal processing chain that everyone goes through—whether or not they speak or act on it.

Component	What It Captures	Example
Sensation	The immediate, often physical or intuitive response to a situation	“My stomach tightens when we skip patient feedback”
Emotion	The internal emotional response to that sensation	“I feel nervous that we’re rushing”
Want	The impulse or desire that arises from the emotion	“I want to push back, but I also want to avoid conflict”

This chain takes seconds—but its consequences can last months.

Teams that ignore SEW signals end up with:

• Repeated issues that were “felt” but never voiced

• Frustrated team members who feel unheard

• Escalated risk that could’ve been reduced early

• A culture where people learn to suppress risk instincts

---

Why SEW Belongs in a Risk Leadership Toolkit

Most risk tools help teams analyze, track, or respond. SEW helps teams feel, name, and surface risk early—often before it’s measurable.

SEW is especially useful when:

• A team is moving too fast to reflect

• Emotional stakes are high (e.g., public demos, clinical launches)

• Power dynamics make speaking up difficult

• Teams are experiencing change, burnout, or role conflict

• A risk keeps reoccurring despite process fixes

In short, SEW helps make visible the emotional landscape of risk.

---

How SEW Shows Up in Project Life

Let’s look at how SEW might play out across different stakeholder groups at SMDC.

---

🔹 Engineer’s SEW Loop

Sensation: Developer sees a regression bug in the alert logic—again.
Emotion: Feels irritated and self-critical. Wonders why QA isn’t catching this.
Want: Wants to fix it silently and move on to avoid embarrassment.

Risk Amplified: No systemic conversation happens. Same bug recurs next sprint.

---

🔹 Patient’s SEW Loop

Sensation: Patient sees a new dashboard summary that suggests they’re “out of control.”
Emotion: Feels ashamed, confused, and frustrated.
Want: Wants to stop using the app entirely. Or worse—ignores future alerts.

Risk Amplified: Patient disengages, reducing both clinical outcomes and trust.

---

🔹 Product Manager’s SEW Loop

Sensation: Notices a repeated request from clinicians to change alert categories.
Emotion: Feels defensive. Wonders if the team is questioning their roadmap.
Want: Wants to delay the conversation—says “Let’s wait until after pilot.”

Risk Amplified: Misalignment grows, clinicians feel unheard, and late-stage redesign becomes more expensive.

---

Where to Look for SEW Clues

SEW reactions are rarely verbalized. But they leave fingerprints across team life:

• Body language: Avoided eye contact, deep sighs, rushed responses

• Language shifts: "It’s fine," "Let’s not get into it," "That’s above my pay grade"

• Meeting behaviors: People go quiet when certain topics arise

• Emails/slack: Defensive tone, over-justification, or delays in replying

• Task avoidance: Repeatedly deprioritizing something that’s “technically done” but feels risky

Your job as a risk-aware team member is to notice these patterns—not judge them—and make space for others to voice their internal reactions safely.

---

Using SEW in Risk Leadership

1. Self-Awareness: Use SEW as a Personal Diagnostic

Ask yourself in real time:

• What just triggered me?

• What emotion followed?

• What do I find myself wanting to do—or avoid?

Example:

"I felt tension when the stakeholder dismissed my comment. I felt embarrassed. I now want to stay quiet—even though I still think I’m right."

Naming this SEW chain can shift you from reaction to reflection—and allow a more thoughtful next move.

---

2. Team Retrospectives: Make SEW Explicit

Instead of asking only “What went wrong?” ask:

• What moment triggered unease? (Sensation)

• How did we feel in that moment? (Emotion)

• What did we want to do—or hold back from doing? (Want)

This turns reflection into empathy. You surface not just risk facts—but the emotional climate that enabled or disabled action.

---

3. Risk Control Design: Bake SEW into Systems

When defining thresholds, alerts, or response rules, ask:

• What might this trigger emotionally for a user or team member?

• What wants might that emotion produce—e.g., hide, delete, blame, disengage?

Then build in:

• Supportive messaging

• Reset options

• Clear escalation steps

• Room for pause and processing

---

4. Use SEW to De-Escalate Conflict

If someone is resisting a task or pushing too hard, try to decode their SEW:

• What are they sensing that we might not be seeing?

• What emotion are they protecting or managing?

• What do they want—clarity, recognition, protection, control?

This turns tension into inquiry—and inquiry into risk prevention.

---

SEW Across the Milestones

The SEW model applies throughout the entire CIS 95C risk process:

Milestone	SEW Application
1 – RBS	What unspoken risks did people hesitate to name?
3 – Stakeholder Feedback	Did anyone’s emotional response shift their scoring of a risk?
5 – Root Cause	Were there SEW patterns that created silence or avoidance loops?
7 – Patient Risk Mapping	What sensory or emotional triggers might cause disengagement?
9 – Control Prioritization	Were any controls deprioritized because someone wanted to avoid conflict or cost?
11 – Contingency Planning	What emotional responses might occur during risk activation—and how can we manage them?

---

Closing Reflection: Risk Begins with a Feeling

We often think of risk as a calculation. A probability. A score.

But in real projects, the first sign of risk is almost always human.

A flicker of doubt.
A delayed conversation.
A colleague walking away from something they used to care about.

The SEW Model gives you a tool to catch those signals. To name them. To listen with curiosity, not judgment. To design with emotion in mind—not as a weakness, but as a first line of risk intelligence.

In the next section—Collaboration and Communication in Risk—you’ll learn how to build teams that make it safe to speak early and often… because risk isn’t just what we measure.

It’s what we feel.