Overcoming adversity in the workplace is not about pretending a difficult situation is positive. It is about helping people face reality, find the part they can influence, and build a better way to move forward. For leaders and teams, adversity may show up as a missed commitment, a reorganization, a conflict, a resource gap, or a high-pressure goal that exposes weaknesses in the way work gets done.
Aaron Golub teaches a practical way to make that response repeatable. His approach connects perspective, ownership, accountability, resilience, and action. The goal is not a one-time burst of motivation. The goal is a team that can identify what is happening, communicate about it, ask for help, make decisions, and keep commitments when conditions change.
What is overcoming adversity in the workplace?
Overcoming adversity in the workplace means responding to a difficult event or condition in a way that protects people, improves clarity, and restores purposeful action. It involves naming the real problem, taking responsibility for the response, using support, and turning the lesson into a stronger team practice.
That definition matters because workplace adversity is broader than a personal setback. It can affect one employee, a manager, a project team, or the whole organization. The visible problem may be a missed deadline. The underlying issue may be unclear ownership, poor communication, a decision that was never made, or a culture where people wait too long to raise concerns.
Common examples include:
- A team loses a key resource while an important project is already under pressure.
- A new leader inherits conflict, low trust, or unclear expectations.
- An organization changes direction and employees are unsure how their work fits.
- A customer problem reveals a weak handoff between departments.
- A high performer is afraid to admit that a commitment is at risk.
- A team keeps discussing the same obstacle without assigning a next action.
These situations require more than telling people to stay positive. Leaders have to create enough clarity for people to act. They also have to make it safe to tell the truth early, before a manageable issue becomes a crisis.
Overcoming adversity does not mean denying unfairness, loss, fatigue, or structural problems. A perspective shift is useful only when it leads to a more accurate diagnosis and a more constructive response. If a process is broken, the team should improve the process. If expectations are vague, the leader should clarify them. If someone needs support, asking for it should be treated as responsible behavior.
How can leaders turn adversity into performance?
Leaders turn adversity into performance by treating a challenge as information about the team, the system, and the next decision. They help people move from reaction to diagnosis, from blame to ownership, and from isolated effort to coordinated action. Performance improves when the team can repeat that response under pressure.
Aaron's work begins with a simple distinction: adversity is inevitable, while resilience is a choice. That does not make resilience easy, and it does not make every challenge fair. It means leaders can choose how they frame the situation, what they communicate, who they involve, and which behavior they reinforce.
A useful leadership response has six parts:
- Name reality: Describe what happened without exaggeration, denial, or personal attack.
- Find the cause: Separate the visible symptom from the conditions that produced it.
- Choose perspective: Ask what the situation is revealing and what capability the team needs next.
- Assign ownership: Make the next decision and the next action clear to a real person.
- Use support: Bring in the information, coaching, expertise, or capacity that the team lacks.
- Close the loop: Review what changed, what was learned, and what the team will do differently.
This sequence turns an abstract value such as resilience into observable leadership behavior. It also keeps resilience from becoming an excuse to tolerate preventable confusion. A resilient team is not a team that absorbs every problem silently. It is a team that can surface problems early and respond with discipline.
For a deeper look at leading through pressure, readers can explore Aaron's guidance on mastering leadership resilience and his resilience speaker programs.
Framework 1: Things Happen FOR Us, Not TO Us
Things Happen FOR Us, Not TO Us is a perspective framework. It asks a leader or team to look at adversity as a source of information, growth, and capability rather than as proof that progress is impossible. The framework does not erase the difficulty. It changes the question from "Why is this happening to us?" to "What can this teach us, and what will we do with what we learn?"
The word "for" should not be misunderstood. It does not mean every painful event was necessary or deserved. It does not mean leaders should rush past grief, anger, or legitimate criticism. It means the team can decide whether the event will remain only a setback or become input for a wiser response.
Apply the framework at the individual level
An individual can use the framework to identify a capability that the situation is demanding. A missed opportunity may reveal a need for better preparation. A difficult conversation may show that the person has been avoiding a necessary boundary. A change in responsibilities may expose a skill that needs development.
Useful prompts include:
- What is this situation revealing about my assumptions?
- What part of the response is within my control?
- What conversation have I delayed?
- What support or information would help me make a better decision?
- What will I practice before the next similar situation?
Apply the framework as a manager
A manager can use the perspective shift to keep a team from turning a setback into a story about incompetence. Instead of asking who failed, the manager can ask which expectation, handoff, resource, or feedback pattern allowed the problem to grow. That question does not remove accountability. It makes accountability more useful because it points toward a change in behavior or system.
For example, if a project arrives late because two teams made different assumptions about approval, the manager should not stop at "be more careful." The manager can define the approval owner, establish a visible checkpoint, and ask what signal would have exposed the risk earlier.
Apply the framework at the team level
At the team level, Things Happen FOR Us, Not TO Us becomes a shared language for learning. After a hard week, the team can identify what the challenge revealed about capacity, communication, decision rights, and trust. This creates a bridge from emotion to action without asking people to suppress their experience.
The framework is strongest when leaders pair it with candor. A team cannot learn from adversity that it is not allowed to describe accurately. Leaders should acknowledge what was lost, name the impact, and then ask what the team can build from the experience.
For more work on this perspective shift, link to shifting mindset through adversity and Aaron's writing on acceptance, perspective, and gratitude.
Framework 2: Extreme Ownership and the Accountability Loop
Extreme ownership is the practice of taking responsibility for the response, even when a leader did not cause every condition. The Accountability Loop turns that mindset into a team operating rhythm: clarify the result, name the owner, check progress, address obstacles, and close the commitment. Together, the two ideas replace passive blame with visible responsibility and follow-through.
Extreme ownership should not mean accepting blame for events outside a person's control. It means asking, "Given the facts in front of us, what is my responsibility now?" A leader may not control a market change, a staffing decision, or a customer's action. The leader can control whether the team communicates early, makes the next decision, and asks for the support required to respond well.
Make ownership specific
Teams often use the word "we" when no one has a clear next action. Shared responsibility is valuable, but a shared goal still needs individual commitments. A useful commitment names the outcome, the owner, the next step, and the point at which the team will review progress.
Instead of saying, "We need to fix the handoff," say, "Jordan will map the current handoff by Wednesday, Priya will confirm the approval point, and the team will review both in Thursday's meeting." The second statement makes action visible without turning the team into a collection of isolated performers.
Run the Accountability Loop
Use this five-part practice when adversity threatens a project or team goal:
- Clarify the result: State what must be true, who is affected, and why the result matters.
- Confirm ownership: Name the person responsible for moving the next step, along with the people who need to contribute.
- Check the signal: Choose the evidence that will show whether progress is real, such as a decision, draft, customer response, or completed handoff.
- Surface the obstacle: Ask what could prevent follow-through and what support is needed before the next check-in.
- Close or reset: Confirm completion, learn from the result, or revise the commitment openly when conditions change.
The loop protects accountability from becoming a one-time speech. It gives leaders a way to notice when a commitment is drifting and gives team members a clear opening to ask for help.
| Blame cycle | Ownership loop |
|---|---|
| Focuses on who caused the problem | Focuses on the next responsible response |
| Waits for someone else to act | Names the next action and owner |
| Hides risk until a deadline exposes it | Uses regular check-ins to surface risk early |
| Treats a mistake as a verdict | Treats the result as information for improvement |
For related reading, see accountability and leadership growth. Leaders who want help applying ownership and team accountability can also review Aaron's leadership and business coaching services.
Framework 3: The Audit, The Shift, The System, The Result
The Audit, The Shift, The System, The Result is Aaron's four-stage team consulting framework. It moves a team from honest diagnosis to a new way of working. The Audit identifies roadblocks, communication gaps, and blind spots. The Shift changes the team's interpretation and priorities. The System installs repeatable practices, including the Accountability Loop. The Result is the performance and cohesion the team can sustain.
The Audit: See what is actually happening
The Audit is not a search for someone to blame. It is an examination of how the team makes decisions, communicates, hands work from one person to another, and responds when a commitment is at risk. Leaders can ask:
- Where does work slow down or return for rework?
- Which decisions remain unclear after meetings?
- Where do people discover bad news too late?
- Which responsibilities are assumed rather than assigned?
- What do team members avoid saying because they expect a negative response?
The output of the Audit is a shared picture of the current operating problem. Without that picture, teams often try to fix symptoms with more meetings, more urgency, or more individual effort.
The Shift: Change the response
The Shift is the point where the team chooses a more useful interpretation. A missed handoff might shift from "that department does not care" to "our approval path is unclear." A failed launch might shift from "we cannot trust anyone" to "we need earlier testing and clearer decision rights." The new interpretation should be honest, specific, and connected to action.
Leaders should be careful here. A mindset shift is not a demand for forced optimism. The goal is not to make a difficult situation sound pleasant. The goal is to help people see choices that blame, fear, or confusion had hidden.
The System: Make the new behavior repeatable
A team cannot depend on a good conversation alone. The System converts insight into a working practice. That may include a clearer meeting agenda, a visible owner for each decision, an escalation rule, a check-in rhythm, or a post-project review. The system should be light enough to use under pressure and specific enough to change behavior.
For example, a team with recurring missed handoffs might use three rules: every handoff has one named owner, the receiving person confirms the acceptance criteria, and any risk is raised at the next scheduled check-in rather than held until the deadline. Those rules do not solve every problem, but they give the team a repeatable way to expose and address the next one.
The Result: Review performance and learning
The Result is more than whether the immediate project ended well. Leaders should review whether communication became clearer, whether ownership was visible, whether people raised risks earlier, and whether the team learned enough to improve the next cycle. The result is evidence that the new system is helping the team perform with greater clarity.
This four-stage sequence helps leaders avoid two common errors. The first is moving to solutions before understanding the problem. The second is holding a productive conversation without installing the habits that would make the lesson durable.
Asking for help and facing fear of failure
Asking for help is a leadership strength because it brings information and capacity into the situation before a risk becomes a crisis. Fear of failure becomes dangerous when it makes people hide uncertainty, delay escalation, overcontrol the work, or protect an image of competence at the expense of the team.
Leaders shape whether help-seeking is treated as responsible. If a manager reacts to bad news with humiliation, people learn to delay bad news. If the manager asks what support is needed and what signal should have appeared earlier, people learn that early escalation is part of good execution.
Replace the performance of certainty
High-performing professionals can be especially vulnerable to the performance of certainty. They may keep working alone because they believe a leader should already know the answer. They may avoid a question because they fear that asking will reduce confidence in them. The result is often slower decisions and a larger problem.
A leader can model a better standard with language such as:
- "Here is what I know, and here is what I do not know yet."
- "I see two possible risks. Who has information that could help us test them?"
- "What support would make this commitment realistic?"
- "What should we escalate now rather than explain later?"
Build help-seeking into the system
Help-seeking should not depend only on courage in a stressful moment. Add it to the Accountability Loop. When an owner confirms a commitment, ask what could block it and which resource would be useful. At the check-in, ask what changed and whether the current plan still fits. In the review, ask whether the team waited too long to involve someone.
This approach protects both accountability and compassion. The person remains responsible for communicating the risk. The team remains responsible for creating a practical path to resolution. Asking for help is not the opposite of ownership. It is one of the ways ownership becomes visible.
Aaron's executive and leadership coaching can give leaders a structured setting to work through decision-making, resilience, accountability, and performance under pressure.
How do teams apply the frameworks in sequence?
Teams apply these frameworks in sequence by first naming the reality, then choosing a useful perspective, assigning ownership, asking for support, installing a check-in loop, and reviewing what the experience taught them. The sequence is simple enough to remember, but it must be practiced in real work rather than discussed only in a workshop.
Step 1: Name reality without creating a verdict
Start with observable facts. What happened? What was the impact? Which commitments, customers, employees, or decisions are affected? Avoid turning the first conversation into a character judgment. "The approval was not confirmed before the work started" is more useful than "the team was careless."
Step 2: Separate facts from stories
Teams often add a story to an event before they have enough information. The story may be that another department does not care, that leadership is changing direction without reason, or that one mistake proves the project will fail. Ask what is known, what is assumed, and what must be learned next.
Step 3: Use the FOR perspective
Ask what the challenge is revealing. Does the team need clearer decision rights? Better preparation? A more honest capacity discussion? More direct feedback? The answer should not minimize the impact. It should identify a capability that can improve the response.
Step 4: Choose a controllable response
List what the team can influence now. It may not control the external change, but it can control the next communication, decision, customer update, escalation, or experiment. Choosing a controllable response restores agency without pretending the team controls everything.
Step 5: Assign ownership and support
Name one owner for the next action. Then name the contributors, information, tools, or decisions that owner needs. If the commitment is unrealistic, revise it in the open. A team does not become stronger by making promises that no one can keep.
Step 6: Run the Accountability Loop
Set the check-in point and define the signal that will show progress. A check-in should not be a vague request for an update. It should answer whether the agreed action happened, what changed, what obstacle remains, and whether the plan should continue or change.
Step 7: Review the learning
Close the loop with a short review. What worked? What made the problem harder? What did the team notice late? What should become a standard practice? This is where adversity becomes organizational learning instead of a story people repeat without changing how they work.
The first 24 hours
In the first 24 hours, focus on stabilization and truth. Confirm the immediate impact, communicate with the people who need to know, stop avoidable damage, and appoint an owner for the next decision. Do not attempt to solve every long-term issue before the team has a shared view of the immediate facts.
The first week
During the first week, use the Audit and the Shift. Identify the conditions that created the problem, then choose one or two changes that can improve the next cycle. Keep the list focused. A team that leaves a difficult meeting with twenty improvements and no owner has created more noise, not more resilience.
The ongoing rhythm
Over time, embed the System in normal work. Use clear owners, regular check-ins, early escalation, and after-action learning. Revisit the Result with evidence from team behavior. Are people raising risks earlier? Are commitments easier to understand? Are leaders responding consistently when a plan changes?
Consider an illustrative example. A product team misses a launch milestone because product, sales, and operations each believed another group owned the final approval. The leader begins with the Audit by mapping the handoff and asking where the assumption entered. The Shift changes the conversation from "someone dropped the ball" to "our decision path is not visible." The System establishes one approval owner, a written acceptance point, and a check-in before the launch window. The Result review asks whether the team surfaced the next risk sooner and whether the process is clearer for the next launch.
This example is not a claim about a specific customer result. It shows how the frameworks create a practical path from adversity to better execution. The same pattern can apply to a reorganization, a difficult client relationship, a team conflict, or a goal that has become unrealistic.
How should leaders measure progress?
Leaders should measure whether the team is building better response habits, not whether a single inspirational moment made everyone feel confident. Useful signals include clearer ownership, earlier escalation, faster decisions, more reliable handoffs, stronger follow-through, and better conversations after a setback.
Choose a small set of questions that can be repeated:
- Can every active priority be matched to one clear owner?
- Do people know when and how to raise a risk?
- Are decisions recorded with an expected next step?
- How often does a team discover a problem only after a deadline?
- Do leaders respond to bad news with curiosity and action?
- Can team members name what they learned from the last setback?
These are diagnostic questions, not universal benchmarks. The right baseline depends on the team's work, size, pressure, and current operating conditions. The goal is to notice movement in the behaviors that make resilience possible.
Research can add useful context without replacing practical judgment. A recent workplace resilience meta-analysis indexed by the American Psychological Association examined resilience in relation to performance, job attitudes, well-being, and physical health, while also noting that resilience is conceptualized in different ways. Review the published research record for the workplace resilience meta-analysis. The leadership lesson is to define resilience in observable terms for the team, rather than using it as a vague label.
Leaders can review these signals at the end of a project, after a major change, or during a recurring team meeting. The review should end with one practice to retain and one practice to improve. Small, repeated changes are more useful than a large list that no one owns.
Frequently asked questions
What are examples of adversity in the workplace?
Examples include organizational change, resource constraints, conflict, unclear expectations, missed commitments, difficult customer situations, staffing changes, and goals that no longer fit current conditions. The event itself is only part of the challenge. Leaders also need to address how the team communicates, assigns ownership, requests support, and learns from the response.
How do you stay calm during workplace adversity?
Start by separating observable facts from assumptions, then identify the next controllable action. A calm response does not require suppressing emotion or pretending the issue is small. It requires enough structure to prevent reaction from becoming the only decision-maker. Naming the impact, asking for relevant information, and setting a check-in can create that structure.
How can a manager support a team through adversity?
A manager can support a team by communicating what is known, clarifying priorities, assigning ownership, making it safe to raise risks, and providing access to the information or help people need. The manager should also model accountability by acknowledging mistakes and following through on commitments. Support works best when it strengthens action rather than removing all responsibility from the team.
Is asking for help a leadership weakness?
No. Asking for help is a leadership strength when it is specific, timely, and connected to the work. It shows that the leader is protecting the result instead of protecting an image of certainty. Effective help-seeking names the risk, explains what is needed, and keeps the owner engaged in the response.
What is the difference between resilience and ignoring problems?
Resilience means facing a problem, adapting the response, and continuing with greater clarity. Ignoring a problem delays action and often increases the eventual cost. A resilient leader can acknowledge disappointment, challenge an unfair condition, or ask for more resources while still deciding what can be done next.
Turn the next challenge into a better operating system
Overcoming adversity in the workplace becomes practical when leaders connect perspective to action. Things Happen FOR Us, Not TO Us helps a team find useful information in a hard situation. Extreme Ownership and the Accountability Loop make responsibility visible. The Audit, The Shift, The System, The Result turns insight into repeatable team practice. Asking for help keeps fear from hiding risk.
Aaron Golub brings these ideas to organizations through keynotes, interactive workshops, leadership coaching, and team consulting. His perspective is grounded in lived adversity, leadership, and performance, including his experience as the first legally blind Division I athlete to play in a game and as a Tulane football team captain. The work is designed for the context in front of the audience, whether that is a company event, leadership program, team challenge, school, university, athletic department, or association.
.avif)
