{"id":5139,"date":"2025-09-09T18:52:30","date_gmt":"2025-09-09T17:52:30","guid":{"rendered":"https:\/\/humansofcode.org\/?p=5139"},"modified":"2025-09-10T06:19:00","modified_gmt":"2025-09-10T05:19:00","slug":"calling-in-the-courageous-alternative-to-calling-out","status":"publish","type":"post","link":"https:\/\/humansofcode.org\/ja\/personal-development\/calling-in-the-courageous-alternative-to-calling-out\/","title":{"rendered":"Calling In: The Courageous Alternative to Calling Out"},"content":{"rendered":"

In the age of instant reactions and public accountability, \u201ccalling out\u201d has become a familiar tool in the workplace. Someone says something questionable, and we respond – often publicly – with a correction, a critique, or a clapback. While this can feel righteous, it can also feel like a public attack, and not consistent with the psychologically safe space we work hard at creating and maintaining.<\/p>\n\n\n\n

But what if there\u2019s a better way? One that invites growth instead of shame, dialogue instead of defensiveness?<\/p>\n\n\n\n

Welcome to the art of \u201ccalling in.\u201d<\/p>\n\n\n\n

What Is \u201cCalling In\u201d?<\/strong><\/h2>\n\n\n\n

Calling in is the practice of addressing problematic behavior or language through private, respectful conversation. It\u2019s not about avoiding hard truths – it\u2019s about delivering them in a way that encourages reflection, not retaliation.<\/p>\n\n\n\n

Instead of saying, \u201cThat was inappropriate,\u201d we might say, \u201cHey, I wanted to check in about something you said earlier – can we talk?\u201d<\/p>\n\n\n\n

Instead of a public reprimand, we offer a quiet moment of connection.<\/p>\n\n\n\n

It\u2019s grown-up. It\u2019s generous. And it\u2019s surprisingly effective.<\/p>\n\n\n\n

Why It Works – Especially for Inclusive Teams<\/strong><\/h2>\n\n\n\n

Calling in creates psychological safety. It reduces the threat response that often comes with public correction, especially for neurodivergent team members who may already be navigating sensory overload, executive function challenges, or social anxiety.<\/p>\n\n\n\n

It also models emotional maturity. Leaders who call in demonstrate that accountability doesn\u2019t have to come with humiliation. That feedback can be firm and kind. That we can be wrong – and still be worthy.<\/p>\n\n\n\n

In short: it builds trust.<\/p>\n\n\n\n

Practical Tips for Leaders<\/strong><\/h2>\n\n\n\n

Here\u2019s how to make \u201ccalling in\u201d a cultural norm:<\/p>\n\n\n\n

    \n
  • Choose the right moment.<\/strong> Don\u2019t wait too long, but don\u2019t pounce either. A calm follow-up after the meeting often works best.<\/li>\n\n\n\n
  • Use curiosity, not accusation.<\/strong> \u201cCan you walk me through what you meant?\u201d opens more doors than \u201cThat was out of line.\u201d<\/li>\n\n\n\n
  • Keep it private.<\/strong> DM, email, or a quick 1:1 chat. Public correction should be reserved for urgent harm or repeated patterns.<\/li>\n\n\n\n
  • Focus on impact, not intent.<\/strong> Help the person understand how their words or actions landed, without assuming malice.<\/li>\n\n\n\n
  • Offer a path forward.<\/strong> \u201cHere\u2019s how we might approach this differently next time\u201d is more useful than \u201cDon\u2019t do that again.\u201d<\/li>\n<\/ul>\n\n\n\n

    When \u201cCalling Out\u201d Is Still Necessary<\/strong><\/h2>\n\n\n\n

    Let\u2019s be clear: calling in isn\u2019t a free pass for harmful behaviour. Sometimes, public accountability is essential – especially when power dynamics are at play or harm is ongoing.<\/p>\n\n\n\n

    But for the everyday missteps, the awkward phrasing, the unconscious bias – calling in gives us a chance to educate, not escalate.<\/p>\n\n\n\n

    The Leadership Challenge<\/strong><\/h2>\n\n\n\n

    Inclusive leadership isn\u2019t just about policies and pronouns. It\u2019s about how we show up in moments of tension. Do we shame, or do we support? Do we react, or do we reflect?<\/p>\n\n\n\n

    Calling in is a skill. A mindset. A quiet revolution in how we hold each other accountable.<\/p>\n\n\n\n

    So next time someone slips up, ask yourself:
    Do I want to be right – or do I want to be effective?<\/p>","protected":false},"excerpt":{"rendered":"

    In the age of instant reactions and public accountability, \u201ccalling out\u201d has become a familiar tool in the workplace. Someone says something questionable, and we respond – often publicly – with a correction, a critique, or a clapback. While this can feel righteous, it can also feel like a public attack, and not consistent with the psychologically safe space we work hard at creating and maintaining. But what if there\u2019s a better way? One that invites growth instead of shame, dialogue instead of defensiveness? Welcome to the art of \u201ccalling in.\u201d What Is \u201cCalling In\u201d? Calling in is the practice of addressing problematic behavior or language through private, respectful conversation. […]<\/p>\n","protected":false},"author":2,"featured_media":5140,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"slim_seo":{"title":"Calling In: The Courageous Alternative to Calling Out - humans of code","description":"In the age of instant reactions and public accountability, \u201ccalling out\u201d has become a familiar tool in the workplace. Someone says something questionable, and w"},"_slim_seo_primary_term_category":0,"_slim_seo_primary_term_post_tag":0,"footnotes":""},"categories":[48,49,7,17],"tags":[],"class_list":["post-5139","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-inclusion","category-leadership","category-personal-development","category-team-work"],"_links":{"self":[{"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/posts\/5139","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/comments?post=5139"}],"version-history":[{"count":2,"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/posts\/5139\/revisions"}],"predecessor-version":[{"id":5142,"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/posts\/5139\/revisions\/5142"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/media\/5140"}],"wp:attachment":[{"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/media?parent=5139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/categories?post=5139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/humansofcode.org\/ja\/wp-json\/wp\/v2\/tags?post=5139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}