---
title: "Discussion on \"When your team gets called a blocker\" | Hashnode"
description: "Discussion on \"When your team gets called a blocker\". On the word every busy team eventually hears, why arguing back doesn't work, and the numbers that do."
url: "https://hashnode.com/posts/when-your-team-gets-called-a-blocker/6ae0fb2da2bf4a8e3b159b45"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [When your team gets called a blocker](https://salesforcegirl.hashnode.dev/when-your-team-gets-called-a-blocker?utm_source=hashnode&utm_medium=feed)

On the word every busy team eventually hears, why arguing back doesn't work, and the numbers that do.

Oct 27 · 9 min read · salesforcegirl.hashnode.dev  
Updated Nov 7  
Read the article

-   [#software-engineering](https://hashnode.com/tag/software-engineering)
-   [#productivity](https://hashnode.com/tag/productivity)
-   [#project-management](https://hashnode.com/tag/project-management)
-   [#management](https://hashnode.com/tag/management)
-   [#agile](https://hashnode.com/tag/agile)
-   [#leadership](https://hashnode.com/tag/leadership)
-   [#scrum](https://hashnode.com/tag/scrum)
-   [#engineering-management](https://hashnode.com/tag/engineering-management)

## Written by

[Randi W](https://hashnode.com/@salesforcegirl)

@salesforcegirl · Lakeport

  
[View profile](https://hashnode.com/@salesforcegirl)

See a need, fill a need: Untangling real-world Salesforce orgs, building healthy engineering teams, & shipping software without the burnout

Vendor demos show pristine systems, but real-world orgs are 10-year-old hoards of competing triggers, forgotten packages, and technical debt. And the teams running them are often burning out trying to keep the wheels turning. I’ve spent just under 20 years in the enterprise trenches—from making desk waffles to boost morale on support calls at LogMeIn to building team health frameworks and leading systems engineering at SurveyMonkey and Salesforce. I write about untangling messy systems, building solutions for complex systems and why genuine team care is just as critical as clean architecture.

## Responses 2

Markdown supported · ⌘↵ to post

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 28](https://hashnode.com/posts/when-your-team-gets-called-a-blocker/6ae0fb2da2bf4a8e3b159b45/comment/6ae144109975f2d0c482cdb1)

The "done but not released" example makes the hidden wait easy to see. Did you track the reason for each wait too, or was the time in that stage enough to start the conversation?

[Randi W](https://hashnode.com/@salesforcegirl)

[Oct 28](https://hashnode.com/posts/when-your-team-gets-called-a-blocker/6ae0fb2da2bf4a8e3b159b45/comment/6ae144109975f2d0c482cdb1#reply-6ae1692c8f07b9280a3c3302)

Honestly, at first we didn’t track the reason, and that was the mistake.

When work got stuck in UAT, we pushed it to the next sprint and carried a point. After a while our sprints were full of 1-pointers that were mostly “waiting in the release window.” Then we moved UAT to done. It helped morale, but it was a story we told ourselves: the tickets closed, the work wasn’t live, and getting it to production took more effort the longer it sat.

I think of it like a bakery. Finished bread sits in the window going stale, and by the time it ships, nobody wants it anymore.

So we built a separate board to see that work again, and I started looking at three clocks: how long work waited to get into a sprint, how long it actually took to build (not what we pointed it), and how long it took to get out. I had hunches about which kinds of work got stuck most, and I wanted data to prove or kill them, so we could fix the bottleneck instead of hiding it.

To answer your question: time in stage was enough to start the conversation. The reason is what lets you fix it.

It also changed the deal with the business. When we take your work into a sprint, we’ll need you to smoke test it when it’s ready. If it was worth fighting for to get in, it’s worth helping get out the door.
