Skip to main content
Steady at the Top
← All articles

Is fear becoming the way your company gets work done?

Look for fear-based management in the way people conceal uncertainty, avoid escalation, and respond to those who bring difficult information. Verify specific events before assigning a label. Establish clear work standards and reporting routes while addressing harmful conduct through a fair, authorized process.

Abusive supervision is employees’ perception of sustained hostile verbal or nonverbal supervisory behaviour, excluding physical contact, following Bennett Tepper’s 2000 research definition. That construct is more specific than a demanding job, a difficult conversation, or a missed promotion. It describes perceived patterns of conduct, not a clinical diagnosis of a manager or proof of intent in an individual case.

Fear-based management is used here as an operating warning about coercive incentives, not as another validated diagnosis. Keep high expectations separate from humiliation and threats. A deadline can be firm while a person remains able to report an obstacle, question an assumption, and use an appropriate complaint process.

Recognize the quiet that follows a forceful meeting

Consider this composite. You leave a tense operating review believing that your message finally landed. That evening, while a friend describes their own week, you keep checking whether the team has sent a stronger recovery plan. No one has challenged the plan again. The next day a manager asks privately whether a warning should be left out of the board update because it will make the responsible executive look bad.

The silence after the meeting does not establish that people understand the work or agree with the plan. Ask what changed in the information reaching you. Did the discussion clarify the next action, or make it costly to describe uncertainty? Establish the event and the reporting conditions before concluding either that the team is fragile or that the culture is coercive.

This recognition scene is a composite, not a case report. It names pressure and behaviour without diagnosing the reader. If stress-related symptoms persist or affect daily life, a licensed clinician is the right person to consult. A leadership review can address work conditions; it is not diagnosis or treatment.

Use the consequence-pattern audit

This proposed diagnostic examines how a management response affects the handling of work information. It is not a screening test for psychological illness or a formal finding about conduct. Where harassment, retaliation, discrimination, threats, or other employment concerns arise, involve the appropriate people process and employment counsel. Use emergency or security procedures for an immediate safety issue.

1. Choose concrete episodes

Select recent occasions involving bad news, uncertainty, disagreement, and a missed obligation. Include an event that leaders believe was handled well. Record the people’s roles and the operating question without collecting private material that the review does not need. Work from a record where possible and invite correction of an incomplete account.

Avoid starting with a request to name the most feared leader. That can create a contest of reputation while leaving actual conduct unclear. Ask what happened, what was said or done according to the available evidence, and what response followed. Mark recollection as recollection rather than creating an exact quotation no one recorded.

2. Distinguish the standard from the delivery

Write down the legitimate work expectation. Then examine how it was communicated and enforced. A manager may have needed to stop unsafe work or reject an inadequate result. That necessity does not settle whether personal ridicule, threats, or inconsistent consequences were appropriate. Review the expectation and the conduct as separate questions.

Ask whether the person knew the requirement before the event and had an authorized way to challenge an impractical instruction. If the requirement was missing, state it now without pretending it had always been clear. If it was clear, examine how the person responded and what options were available at the time.

3. Follow the information after the response

Compare the concern raised with the next report. Was uncertainty clarified, resolved, omitted, or relabeled? Establish who authorized the change. A revised forecast may reflect new evidence, but it may also leave an unresolved dependency invisible. Do not infer either explanation without comparing the underlying records.

Morrison’s review of employee voice and silence examines the withholding of useful work input. Use that question here: did the response make the operating information more accurate and usable, or merely make it less visible? The answer should come from an event sequence, not from how confident the final presentation sounded.

4. Examine how escalation works in practice

Ask a person doing the work how they would raise an obstacle if their manager rejected it. Identify the next owner, the kind of evidence needed, and the response they could expect. Check whether the route has authority to act and whether it offers suitable independence when the concern involves the normal decision owner.

Do not test the route by asking someone to make an unnecessary live complaint. Use a hypothetical first, then inspect properly authorized records of real cases. Preserve confidentiality and any applicable reporting protections. A leadership audit should not become a second investigation that pressures people to repeat private experiences to an expanding audience.

5. Check the consistency of consequences

Compare materially similar events across status levels. Ask which difference in responsibility, evidence, or conduct explains a different response. An executive’s commercial value may matter to an assignment decision, but it does not by itself answer a concern about harmful behaviour. Use established processes rather than a private exemption created by the CEO.

Look for consequences attached to the act of raising a concern, not only formal sanctions. Exclusion from relevant work or repeated disparagement may need examination. Do not declare retaliation from a single observation. Establish the sequence and consult the responsible professionals about the scope and independence of the review.

6. Repair an observable management practice

Choose a change tied to the evidence. You may need a clearer acceptance standard, a second route for an unresolved concern, an independent conduct review, or a different response when someone reports uncertainty. Assign an owner and identify how the change will be checked. Avoid announcing that the culture is fixed after a meeting about the culture.

If your own response contributed to the problem, describe the behaviour and the correction. “I interrupted the warning and treated the uncertainty as lack of commitment. Next time I will establish the facts before deciding the response.” Use a statement supported by the actual event. Do not require employees to reassure you that your admission proves you are a good leader.

Read warning signs as questions

Repeatedly positive reports, rehearsed agreement, and late escalation can each justify inquiry. They do not independently establish fear-based management. The reports may be accurate, the meeting may have a narrow purpose, or the issue may not yet be known. State what evidence would distinguish those possibilities before you settle on a preferred story.

For a project that remains green despite unresolved dependencies, ask how status is determined and who can change it. For a leader who receives no challenge, ask what information was available before the meeting and where reservations could be recorded. For a team that escalates late, examine whether earlier escalation reached someone able to decide.

Do not reward a dramatic disclosure more than an accurate ordinary report. People should not have to describe a crisis in order to receive attention. Create a category for a plausible concern that needs checking. Give the owner a way to respond without demanding certainty from the person who first noticed the issue.

Preserve a demanding, usable standard

Edmondson’s psychological safety research concerns interpersonal risk in a team. The practical application is permission to contribute relevant information, not freedom from work expectations. You can require an adequate result while asking how the team will identify and report the conditions that prevent it.

Write the acceptance criteria and escalation condition together. For example: “The release requires the responsible specialist’s approval. If approval is not available, stop and contact this owner. Do not describe the work as complete while approval remains unresolved.” That is a proposed operating script, not an empirical claim or a guarantee that every person will respond as intended.

When an executive says the team needs to become tougher, translate the request into the work. Ask what exact obligation is not being met and what conduct would demonstrate improvement. If the answer remains a demand that people tolerate ridicule or conceal constraints, bring the concern to the appropriate governance or employment process rather than disguising it as resilience training.

Make a corrective conversation specific

A proposed opening is: “We need reliable delivery and accurate information. I want to review this event because the concern appears to have disappeared from the report without a recorded resolution. We will establish what happened, review the response, and clarify how the issue should reach a decision. We are not asking anyone to diagnose a colleague or prove loyalty.”

Let the person respond to the actual account. Keep disputed facts visible. Explain who will review any conduct concern and how the operating work will be covered meanwhile. Avoid promising a personnel outcome or sharing someone’s private account in order to demonstrate that leadership has listened.

Use the wider trust and conflict playbook for recurring relationship problems. If your own unresolved conflict keeps shaping a response, examine the grudge repair process. Where the issue is a repeated reward for harmful conduct, review culture and behavioural reinforcement rather than issuing another general message about respect.

Check what happens after the announcement

Inspect the next warning and the next missed obligation. Ask whether information reached the owner, whether the response followed the stated process, and whether the correction was completed. Do not measure progress solely by a warmer meeting or a larger number of comments. Keep the evidence tied to the work and the treatment of people who provide it.

A management practice is worth changing when the record shows that it obstructs accurate information or permits harmful conduct. Make the response proportionate and properly authorized. Preserve demanding standards while giving people a usable path to report reality. The goal is a business that can act on difficult information, not one that has learned to present a more reassuring version of it.

Sources

Steady at the Top