HPI at work: 10 difficult everyday situations and how to respond

Here are ten of these moments, described as they actually occur. For each: what is happening from the perspective of the person involved, the spontaneous reaction that worsens the situation, and the behavior that works — with the exact words to say and the precise gestures. No theory: scenes from the office, workshop, and hallway, and responses applicable as soon as tomorrow morning.

1. In the meeting, he interrupts and corrects everyone

Team meeting, 10 a.m. A colleague presents an idea; before he finishes, your collaborator jumps in: “no, that won’t work, there are three problems.” He is often right. The room closes off. During the break, two people confide in you that he “crushes” everyone.

What is happening: a very rapid thought, often described as branching, that has already unraveled the reasoning and its consequences while the other begins their sentence. The objection is not contempt: it is the raw output of a machine that goes faster than the roundtable. The person generally does not perceive the effect produced: for them, they are helping by signaling the obstacle. Received by the group, this interruption is perceived as arrogance and creates isolation — the opposite of what they seek.

The spontaneous reaction that worsens: correcting him in front of everyone (“let others speak”). Public humiliation triggers a disproportionate reaction in a hypersensitive person, and the message “you are too much” settles in for the long term.

1. Give him a role that channels rather than repress: “you quickly spot the flaws, I’m entrusting you with the synthesis of risks at the end of the meeting.” The flow finds a corridor.
2. Agree on a discreet sign in private: “when I lay my hand flat, it’s time to let the round finish.” A non-verbal cue avoids a public reprimand.
3. Name the fact, not the person: “you interrupted Marc twice, he hasn’t finished his idea” is audible; “you are abrupt” is not.
4. Value the relevance once the round is finished: “your objection about the deadline, we’ll keep it, it’s valid.” Recognized, the need to be right calms down.

To prevent this from happening again: establish a structured speaking turn for the entire team (everyone finishes their point, objections come later). The structure protects the group without targeting an individual, and it also relieves the one who needs restraint.

❌ To avoid: “you think you are smarter than others” — an interpretation of intent that deeply hurts and cuts off any cooperation.

2. The simple instruction that goes nowhere

You assign a defined task: fill out a table according to a template. Three days later, nothing is submitted. Digging deeper, you discover that he wanted to revise the structure of the table, question the usefulness of the process, and propose a different tool. The table, however, is still not done.

What is happening: a need for meaning and difficulty executing without understanding the “why.” The task presented as obvious triggers a cascade of questions: what is this table for, who reads it, why this format. As long as the meaning is not established, execution remains blocked, not out of bad will but because the brain refuses the empty gesture. This is often compounded by the boredom of a task deemed below their level, which amplifies the temptation to redesign it.

The spontaneous reaction that worsens: repeating the instruction more firmly (“do it, that’s all”). Authority without reason reinforces the blockage and triggers the feeling of being infantilized.

1. Give the meaning in one sentence before the instruction: “this table serves management to arbitrate the budget on Friday.” The why unlocks execution.
2. Set the non-negotiable framework and the free space: “the format is mandatory for this Friday; your improvement ideas, we’ll take them, but later, in a separate note.”
3. Set a short checkpoint at 24 hours rather than a distant deadline, to catch the blockage before it settles.
4. Welcome the redesign as a resource: “keep your tool proposal, we’ll look at it on Monday.” What is heard stops parasitizing the task of the day.

To prevent this from happening again: make it a habit to accompany each mission with a line of context (what it’s for, for whom, by when). Two sentences upfront save three days of floating.

❌ To avoid: concluding “he doesn’t know how to do simple things” — it’s rarely the difficulty, it’s the absent meaning that blocks.

3. The repetitive task and disengagement

He excels at complex files. But on recurring data entry, follow-ups, monthly reporting, he multiplies inattentive errors, forgets lines, submits late. He is reproached for a lack of seriousness, while he is brilliant elsewhere.

What is happening: a high need for stimulation. A brain accustomed to handling complex issues does not settle on the repetitive task: it shuts down. Boredom is not a whim, it’s a state that genuinely degrades attention and reliability. The paradox confuses those around: the same person can be remarkable on a difficult problem and failing on a routine, precisely because the routine does not mobilize enough resources to keep them present.

The spontaneous reaction that worsens: increasing control over simple tasks (“I will double-check everything behind you”). Surveillance over the repetitive humiliates without correcting the cause, which is the lack of stimulation.

1. Rebalance the load rather than sanction: systematically attach a part of complexity to thankless tasks, to maintain engagement.
2. Transform the routine into a measurable challenge: “your goal: zero errors on the reporting this month, we’ll review it together at the end.” The game awakens attention.
3. Sequence with a timer: propose short, timed blocks on the repetitive, with the visual timer, to hold attention for a limited duration rather than diffuse.
4. Automate or delegate what can be: part of the repetitive can often be tool-assisted. It’s not a privilege, it’s clarity about what works.

To prevent this from happening again: map out with the person what bores them and what nourishes them, and arbitrate the distribution accordingly. A three-column table (what stimulates / what wears out / what is neutral) makes the discussion concrete.

❌ To avoid: “if you are so smart, you can fill out a table” — the ironic remark crystallizes rejection and improves nothing.

4. The comment that hurts him too much

You slip in a banal feedback: “attention, the proofreading is missing on this email.” The face closes, the voice trembles, he remains defensive all afternoon, even declaring that he “never manages.” The reaction seems disproportionate to the comment.

What is happening: emotional hypersensitivity frequently described in high-potential individuals. The emotion comes on strong, fast, and overwhelms reasoning in the moment. A small critique is not experienced as a technical detail but as a global judgment on personal value. It’s neither feigned fragility nor manipulation: it’s an amplified mode of reception, which the person endures as much as those around them.

The spontaneous reaction that worsens: minimizing (“it’s nothing, don’t take it that way”). Denying the emotion reinforces it and adds the feeling of not being understood.

1. Always separate the fact from the person: “the email is very good; it just needs proofreading” rather than a global reproach. Targeted feedback defuses the value judgment.
2. Welcome the emotion without commenting on it: “I see this affects you, it’s okay, we’ll talk about it in ten minutes.” Time helps to calm the wave.
3. Address it when calm, never when heated. Once the emotion has subsided, the technical message gets through entirely; when heated, nothing is heard.
4. Lock in the positive first: announce what is going well, then the point for improvement, then again a support. The structure protects without watering down.

To prevent this from happening again: prioritize feedback in one-on-one and written form rather than on the fly in public. If emotional suffering becomes recurrent or overwhelming, refer to occupational medicine or a psychologist: identify and refer, not diagnose.

❌ To avoid: “you are too sensitive” — the label hurts, shuts down dialogue, and does nothing to regulate the emotion.

5. The perfect report that never arrives

You are waiting for a summary note for Tuesday. Tuesday, nothing. He has rewritten it four times, deemed “not developed enough,” explored additional angles, added annexes that no one requested. The document, excellent, is still in progress.

What is happening: a demanding perfectionism, often fueled by the fear of disappointing and by a thought that multiplies possibilities. Each version opens new avenues; the “sufficient” does not exist, only the “perfect” matters, and it recedes as one approaches it. The resulting procrastination is not laziness: it’s the avoidance of a submission deemed never good enough, with a real burden of anxiety.

The spontaneous reaction that worsens: demanding even more quality (“take your time, do it well”). The invitation to refine feeds the spiral instead of stopping it.

1. Set an explicit level of demand: “for this submission, I want 80%, not 100% — two pages, no annexes.” Naming the cursor allows stopping.
2. Break it down into dated milestones with imposed intermediate submissions: a plan by D+1, a draft by D+2. Fragmentation breaks the all-or-nothing.
3. Distinguish draft from final version: “send me an imperfect V1, we’ll improve it together.” Allowing the imperfect unlocks the submission.
4. Value the submission, not just the result: “you delivered on time, that’s what matters today.” This reinforces the expected behavior.

To prevent this from happening again: verbalize the expected level of finishing and the firm date for each mission. Without a reference, perfectionism sets the bar to the maximum by default.

❌ To avoid: “you are never on time” — the global reproach reinforces the performance anxiety that is at the root of the delay.

6. The conflict in the name of principle

A decision is made in a meeting to save time on a client file. He opposes it head-on : « that's not honest towards the client ». He doesn't back down, even if it means turning the whole team against him. The atmosphere becomes tense over what seemed like a detail.

What is at stake : a particularly acute sense of justice and coherence, often described in high potential individuals. A gap between the stated values and the decision made is experienced as unbearable, almost physically. This is not gratuitous rigidity : it is a loyalty to the principle that takes precedence over relational comfort. When welcomed, this ethical demand is a valuable safeguard for the organization ; when poorly received, it becomes a source of ongoing conflict.

The spontaneous reaction that worsens : imposing without discussion (« it's decided, we move forward »). Forcing an issue of values triggers a deep resistance, not just a simple disagreement.

1. Acknowledge the value before arbitration : « your point about honesty is legitimate, I hear you ». Acknowledgment diffuses the intensity.
2. Explain the real constraint : « here's why we are deciding this way this time, and here’s what we are preserving ». Shared reasoning makes the decision acceptable.
3. Offer a framed alert space : « if you see a real ethical risk, you report it directly to me ». The official channel channels the energy.
4. Clearly distinguish the negotiable from the non-negotiable: some decisions can be discussed, others cannot, and stating this avoids sterile confrontation.

To prevent this from happening again : involve the person upstream on sensitive topics rather than presenting them with a fait accompli. If consulted beforehand, they defend the decision ; if discovered afterward, they fight it.

❌ To avoid : « you always look for the little flaw » — reducing an ethical demand to a character flaw deprives the team of a useful alert signal.

7. Ten open projects, two completed

He starts everything with enthusiasm : a process overhaul, a tracking tool, competitive monitoring, a background note. Three weeks later, everything is started, nothing is finished. Each new idea chases away another, and the expected deliverables are delayed.

What is at stake : a flourishing curiosity and a mind that quickly shifts from one topic to another. The start is exhilarating — novelty, complexity, stimulation — but the finishing phase, more repetitive, falls below the interest threshold. Dispersion is not a lack of will : it is an imbalance between the appetite for openness and the weaker appetite for closure. Without a framework, energy disperses and the value produced drops.

The spontaneous reaction that worsens : multiplying demands thinking that he « can do everything ». Adding topics to someone who is already opening too many accelerates dispersion.

1. Limit the number of active projects : « we keep a maximum of three ongoing, the others wait ». The constraint protects the finishing.
2. Make closure visible : materialize progress with a board where tasks are moved to « completed ». The 3-column board (to do / in progress / done) makes the remaining tasks concrete.
3. Set « done is better than perfect » as the rule for the final stretch, and celebrate each closure.
4. Park new ideas : keep a list of « later ». The noted idea stops demanding immediate action.

To prevent this from happening again : establish a weekly project review ritual — what we close, what we freeze, what we open. A motivation board that makes progress visible maintains momentum until the end.

❌ To avoid : « you never finish anything » — generalization discourages ; it is the closure that needs to be equipped, not the motivation that needs to be punished.

8. The open space that exhausts him

4 PM, open floor. Conversations, ringing phones, comings and goings. At the end of the day, he is drained, irritable, says he can « produce nothing anymore ». Yet, on telecommuting days, his output doubles and his mood changes completely.

What is at stake : frequent hyper-sensory perception, where stimuli — noise, light, movement — are not filtered and accumulate. The brain processes everything continuously, which exhausts the attention available for actual work. This is neither a whim nor anti-social behavior : the fatigue at the end of the day is the cost of an unfiltered environment. The clear gap between the office and telecommuting is the best indicator of this mechanism.

The spontaneous reaction that worsens : minimizing (« everyone works in open space, make an effort »). Denying sensory overload adds guilt to exhaustion.

1. Adjust the immediate environment : noise-canceling headphones, a quieter place, a bubble or closed room for demanding tasks. These are simple adjustments, not favors.
2. Frame concentration periods : « two hours without interruption in the morning », signaled to the team. Protecting time is as valuable as protecting space.
3. Open telecommuting for background tasks when possible : aligning the location with the type of task significantly improves output.
4. Name the need without stigmatizing : « you need calm to give your best, we will organize that ». Acknowledgment diffuses shame.

To prevent this from happening again : integrate these adjustments into the team's functioning rather than on a case-by-case basis, and ensure they hold over time. A reasonable adjustment is part of work organization ; in case of impact on health, occupational medicine is the contact.

❌ To avoid : treating the request for calm as a negotiable privilege — it is a condition for performance, not a comfort.

9. The hierarchical instruction he contests

You ask him to apply a procedure from management. He responds : « why ? that makes no sense, who decided that ? ». The tone is not insolent, but the insistence on understanding resembles, from above, a challenge to authority.

What is at stake : a relationship to authority based on competence and coherence rather than status. The authority argument alone (« that's how it is ») does not work : the person needs a reason to comply, not a rank. This is not rebellion for the sake of rebellion : it is a demand for justification. Misunderstood, it appears as insubordination ; well handled, it produces solid and lasting adherence, because it is reasoned.

The spontaneous reaction that worsens : retreating behind status (« I decide »). Pure hierarchical argument puts up barriers and turns a sincere question into a power struggle.

1. Give the reason, even briefly : « this procedure exists because the quality department had such an incident ». A justification often suffices to gain adherence.
2. Distinguish the question from refusal : asking why is not refusing to apply. Answer the question, then confirm the expectation of execution.
3. Set the limit with respect : « I explain the why ; then, on this point, we apply, even if you are not 100 % convinced ».
4. Open a channel for substantive disagreements : « if you think the procedure is bad, write me your arguments, I will escalate them ».

To prevent this from happening again : make it a habit to accompany top-down instructions with a word of explanation. The « time lost » in justifying is regained in adherence and reliability of execution.

❌ To avoid : reading every question as a challenge to your legitimacy — it is the best way to create the conflict you fear.

10. The sudden disengagement

An usually proactive collaborator becomes silent, cynical, withdrawn. He does the minimum, no longer proposes anything, seems elsewhere. This is not his usual state. Some speak of « laziness », others of a simple temporary slump.

What is at stake : for a high potential person, a sudden disengagement first suggests exhaustion — from prolonged boredom (sometimes called bore-out) or from overload and loss of meaning (burn-out). The usual intensity of engagement has a downside : when meaning collapses or stimulation is lacking for too long, withdrawal can be quick and deep. This is not laziness : it is a signal, and a signal that does not allow for « to observe a bit longer to see ».

The spontaneous reaction that worsens : re-motivating through pressure (« get moving, we need you »). Adding load to someone who is disengaging accelerates the collapse.

1. Open a non-judgmental exchange : « I find you different these days, how do you really feel at work ? ». The open question creates space for dialogue.
2. Listen without immediately solving. The primary need is to be heard, not to be reorganized within the hour.
3. Guide towards the right resources : occupational medicine, listening cell, psychologist. Identifying and guiding is your role ; diagnosing is not.
4. Act on what depends on you : workload, meaning, autonomy, recognition. These are the organizational levers for sustainable re-engagement.

To prevent this from happening again : regularly monitor the fit between the position and the needs for stimulation and meaning, without waiting for the breaking point. A quarterly exchange point is better than a halt.

❌ To avoid : attributing withdrawal to a character flaw and letting it go. In the face of enduring suffering, the response requires professional support, not a reframing.

HPI at work, what to do : the summary table

In response to the question « HPI at work, what to do », the same logic recurs in the ten scenes : read the functioning behind the behavior, retain the reflex that worsens, apply the conduct that calms. Here is the summary.

To go further

To extend, the DYNSEO free tools catalog offers directly useful materials for these situations — task organization, time management, motivation. On the cognitive observation side, the cognitive tests provide awareness benchmarks (they do not establish any diagnosis), and the application CLINT offers cognitive training exercises for adults, supporting a well-being approach at work.

Frequently Asked Questions