Handling incidents with an undisturbable person: stay calm, make urgency visible

At 10:18, monitoring reports that payments are failing more often. Three explanations, two screenshots, and a question about whether everyone should drop everything immediately appear in the team channel. Your undisturbable colleague opens the numbers and says, “First establish who is affected. Then we decide what to stop.”

That calm helps. Within ten minutes, it is clear that the error affects only new orders and that a rollback is possible. While others are still discussing different disaster scenarios, your colleague has already bounded the first recovery action.

An hour later, it turns out nobody informed customer service. The technical error is almost fixed, but dozens of customers received no explanation. The calm tone was unintentionally taken as evidence that the impact was probably limited.

That is the strength and risk of being undisturbable during an incident. An undisturbable person remains relatively calm, quickly thinks in solutions, and is not easily discouraged. Without explicit agreements, that same calm can cause urgency, social impact, or an early warning sign to receive too little weight.

Good incident handling does not ask this colleague to appear more worried. It makes clear, independently of anyone’s emotional response, what is happening, who is affected, what uncertainty remains, and when the response must escalate.

Undisturbable does not mean insensitive

In a personal user guide, an undisturbable person sits on the side of calm, stability, and quick recovery under pressure. This colleague can notice tension without allowing that tension to take over their thinking or actions immediately.

That can add considerable value during incidents. An undisturbable person holds on to facts while interpretations become mixed, helps the team set priorities, and can carry out a recovery action without treating every new report as a change of course. That stability creates room to think when time is scarce.

The downside belongs to the same mechanism. What feels manageable to this colleague may already have serious consequences for a customer or teammate. A flat response can be read as disinterest. And because recovery starts quickly, a small signal may receive attention only when it becomes visible enough in the numbers to be impossible to ignore.

That is why “you are not taking this seriously enough” is not a useful conclusion. It judges severity through someone’s expression instead of the situation. The better question is: which facts, consequences, and escalation thresholds show how serious this incident is?

UndisturbableRelaxedSensitive

Separate calm from the severity of the situation

An undisturbable person usually does not need extra alarm. The team needs an incident picture that does not depend on who sounds most tense.

Start with the observable signal. Record what has changed since when, which source shows it, and what is still working normally. “Payments are failing” is too broad. “Since 10:18, 8% of new card payments have failed; existing subscriptions are working” gives a factual boundary.

Then make the impact visible separately. State which customers, colleagues, data, or promises are affected. Explicitly ask who sees a greater risk than the current plan assumes. This turns emotional alertness into useful information without making unease itself count as evidence.

Finally, record the action, rhythm, and escalation. Who contains the damage, when is the next update, and which result makes a larger response mandatory? One person’s calm no longer has to set the pace of the entire incident.

1. 1
   FactBound what is happening

   Record the first time, the measurable signal, the affected group, and what demonstrably still works normally.

2. 2
   ImpactMake consequences and uncertainty visible

   State who is affected, which information is missing, and who sees a greater risk than the plan currently covers.

3. 3
   ActionChoose an owner, update, and escalation threshold

   Record who contains the damage, when the team reviews again, and which signal requires a heavier response.

Get to the point more directly with the same message

Under pressure, an undisturbable colleague often gains little from a long introduction mainly intended to show that the sender is worried. When fact, request, and decision point sit between cautious phrases, it takes longer to determine what is needed now.

The message does not need to become harsher. Put the signal, impact, requested action, and next moment in a clear order. Emotional or relational consequences may remain, as long as the recipient does not have to guess what to do with them.

That is why we offer transformations inside personal guides. Open the guide of the person you want to write to. When your preferences differ, the guide suggests a fitting transformation. Paste in your message and the tool returns a version that lands better with the recipient. Its content and intent remain the same. Only tone, wording, structure, and framing change.

For an undisturbable colleague, “Get to the point for Noor” is one fitting option. The error percentage, customer impact, recovery action, and 11:00 update remain the same. The new order simply makes it clearer sooner what needs to happen now.

Original

We are concerned because customers report that checkout is not working. Since 10:18, it appears to affect about 8% of new card payments. Can you pause the release and check the payment provider? At 11:00, say whether a rollback is needed.

Transformed

Since 10:18, about 8% of new card payments have failed. Pause the release and check the payment provider. At 11:00, state whether we need to roll back. Customers are now reporting that they cannot check out.

Three perspectives on the same incident

What you need to watch when working with an undisturbable colleague also depends on your own preference. Two undisturbable people can remain exceptionally clear together and assume for too long that silence means limited impact. A relaxed person can connect calm and alertness but unconsciously decide that the team is responding at exactly the right level. A sensitive person can notice risks and social consequences early and struggle to be heard when others mainly show composure.

If you are undisturbableMake urgency measurable

Do not let your shared calm determine severity. Use impact, uncertainty, and pre-agreed escalation thresholds.

If you are relaxedStay a bridge, not a referee

Translate between calm and alertness, but let facts and consequences determine whether the response is large enough.

If you are sensitiveTranslate your alarm into information

State the concrete signal, possible consequence, and what the team should check now, without claiming certainty.

If you are undisturbable too

Two undisturbable people can be a powerful combination during an incident. You tolerate uncertainty, lose little time to panic, and can break down a problem while pressure rises. Others often experience your stability as an anchor.

The blind spot is shared underestimation. When nobody appears worried, the incident feels smaller. You confirm each other’s calm assessment, move quickly to the technical work, and notice only later that customers, colleagues, or reputation were already affected.

Make someone explicitly responsible for impact, not only recovery. That person checks customer reports, internal dependencies, and possible damage outside the system. At every update, ask: “What are we not seeing in this graph?”

Use a fixed escalation table too. Agree in advance which error rate, duration, or type of impact triggers an extra owner, customer message, or stop decision. Neither of you then needs to become worried before acting at the right scale.

If you are relaxed

As a relaxed colleague, you generally notice tension without allowing it to steer for long. You can therefore understand why a sensitive colleague raises the alarm early and why an undisturbable colleague first wants to determine the scope. That makes you valuable as a translator.

The pitfall is that your middle position can automatically feel like the right measure. You may soften the alarm to preserve calm or add extra urgency because the undisturbable colleague does not show enough of it in your view. You are then still assessing reactions instead of the incident.

Translate into testable questions. “Sam is worried” becomes: “Sam sees three reports from the same customer group; are we checking for a pattern?” And “Noor remains calm” becomes: “Noor sees no reason to escalate yet; which threshold is she using?”

You do not have to give both sides equal weight. You help the team by making the information inside both responses visible and then applying the same criteria.

If you are sensitive

As a sensitive colleague, you often notice early when something changes. An unexpected silence from a customer, a tense reply, or a small technical signal can catch your attention before the scope is clear. During an incident, that may be exactly the warning system the team needs.

Tension arises when the undisturbable colleague reads your urgency as evidence that emotion has inflated your assessment. If you then warn even more firmly to be heard, the difference in tone grows and the original information disappears.

Make your signal small enough to check. State what you saw, which consequence is possible, and which short check will clarify it. For example: “Three customers used the word trust within five minutes. Can we check the last twenty reports for that before deciding communication can wait?”

At the same time, ask for a concrete return point. You do not have to be proved right immediately. You do need to know when the signal will be reviewed again and which evidence will lead to action.

Five agreements you can copy directly

Handling incidents with an undisturbable person does not require artificial alarm. It requires reciprocal agreements that give calm, alertness, and severity distinct places.

1. Our response does not determine severity. We assess an incident by reach, impact, duration, and uncertainty, not by how worried or calm someone sounds.
2. Every update separates fact, consequence, and unknown. We show what has been measured, who is affected, and which important information is still missing.
3. The greatest concern gets a short check. The colleague who sees more risk states the signal and the smallest check that can confirm or bound it.
4. Escalation thresholds are set in advance. A measurable signal triggers extra help, customer communication, or a stop decision without anyone first having to persuade through emotion.
5. Recovery and impact both have an owner. Someone repairs the system, and someone monitors customers, colleagues, communication, and damage outside the technical work.

These agreements also help when nobody calls themselves undisturbable. In our analysis of 2,705 personality profiles, 47% were undisturbable, 37% relaxed, and 16% sensitive. A team that treats only visible unease as urgency will miss signals from calm colleagues. A team that follows only the calmest assessment will lose the early warnings from a smaller but recognizable group.

What usually backfires

Trying to make an undisturbable person worried first wastes time. Show the facts and consequences, then ask for a concrete action. Severity does not have to be proved through emotional intensity.

Treating calm as agreement does not work either. A calm colleague may take the problem seriously, prefer another plan, or still be gathering information. Ask explicitly for the assessment and the escalation threshold being used.

Following the loudest disaster scenario is not a safe counterreaction. Alertness produces hypotheses, not automatic truth. Give every serious concern a short test, then let the same criteria determine the choice.

And do not wait for complete certainty before communicating. “We have been investigating failed payments since 10:18 and will update at 11:00” is more honest than silence until the technical cause is established. Impact can already grow while the solution appears close.

The smallest useful start

You do not need to write an extensive incident protocol. At the next anomaly, immediately put these four lines in the team channel:

What we have seen since when: …

Who or what is affected: …

What we do not yet know: …

Next update and escalation threshold: …

This short block gives an undisturbable person facts and room to act, a relaxed person a foothold for connecting perspectives, and a sensitive person a visible place for early signals.

An anchor point only becomes useful when it leads to an agreement like this. Read how to give feedback to a sensitive person and what the Big Five at work does and does not describe. On Personal User Guide for work, you can then create your own guide and place your preferences next to a colleague’s. That way, you solve an incident with the people who must bring calm, signals, and action together, not for a label.