Are you tired of feeling like your organisation’s incident response is adrift in a sea of chaos? Do you find yourself overwhelmed and uncertain when faced with unexpected challenges? It’s time to introduce a concept that can transform your approach to incident management: grounding.

Imagine this scenario: Your organisation relies on a critical third-party service for its daily operations. Suddenly, without warning, the service goes down, causing a ripple effect of disruptions throughout your systems. Panic ensues as team members scramble to assess the situation, but amidst the chaos, there’s a glaring absence of grounding.

In the thick of it, confusion reigns supreme. Team members are asking questions that have already been answered, and different groups have conflicting understandings of what’s going on. The lack of a unified front only exacerbates the situation, leading to further delays and frustrations.

What is grounding, you ask? Grounding is the anchor that keeps your team steady amidst the storm of an incident. It’s about maintaining a shared understanding within the team of the current working theories, beliefs, and assumptions that we know so far during the incident. This concept was eloquently articulated in David Wood’s 2004 paper “Common Ground and Coordination in Joint Activity,” which highlights the importance of establishing common ground to facilitate effective collaboration and coordination during complex tasks.

So, how can you implement grounding in your incident response practices? Let’s break it down with some practical tips:

  1. Establish clear roles and responsibilities: Ensure that every team member knows their role in the incident response plan, from first responders to communication coordinators. When everyone knows what they’re responsible for, confusion is minimised, and efficiency is maximised.
    Example: In our scenario, grounding would involve designating specific team members to assess the impact of the third-party service failure, communicate updates to stakeholders, and work on finding alternative solutions.

  2. Clarification questions: Encourage team members to ask clarification questions if something is unclear or ambiguous. This helps prevent misunderstandings and ensures that everyone is on the same page. The more specific we are about the problem, the better it helps the collective team resolve the incident.
    Example: During the incident, team members can ask clarification questions to confirm their understanding of the situation and clarify any uncertainties.

  3. Using facts and data: Ground your responses in facts and data to maintain objectivity and accuracy. Utilise metrics, logs, and historical incident data to inform decision-making and validate assumptions.
    Example: Instead of relying solely on intuition or speculation, leverage data from monitoring tools and past incidents to identify trends, patterns, and potential solutions.


By embracing grounding, you equip your team to navigate incidents with clarity and cohesion, minimising disruptions and maximising resilience.

Intrigued to learn more about how grounding can revolutionise your incident response practices? Join us for the Uptime Labs webinar on May 8th, 2024, where we’ll delve deeper into practical examples and strategies for implementing grounding in your organisation.

Top Performers’ Secrets: 3 Ways to Excel in Incident Response

Top Performers’ Secrets: 3 Ways to Excel in Incident Response

  • what we notice when we notice a good incident response.

    Insights for Effective Incident Response



    May 2, 2024

  • The Swiss Cheese Model - root cause analysis tool for incident management

    Discover the ONE Thing You Can Do to Avoid Future Incidents



    April 16, 2024

  • network incident management for swift response

    A Key Incident Response Skill That Can Reduce Resolution Time



    March 25, 2024