Capture blockers easily with a few clicks. Blockers occur inside the technology org, as well as outside on vendors, HR (hiring), Legal (policy approvals), etc, etc. Invite them all, because you only pay for teams, add as many people as you want!
Seeing EVERY organization-wide blocker is overwhelming. Select your team and see an ordered list (by urgency and age) of your teams' blockers. Can you help? Can you escalate? Best of all, by capturing what blocks your team you can discuss them at the next retrospective!
The most common cause of blockers taking a long time to resolve is the team blocking doesn't know they are blocking something important or it gets lost in the noise. By filtering on your team, you can quickly see an ordered list (by urgency and age) of teams blocked by your team.
By capturing blockers "Blocked" generates easy-to-understand charts. You don't need a lot of data to gain insight into what team to team dependencies hurt most, or what types of blockers (based on tags you apply to them) are the most frequent or impactful. Seeing these trends over time helps see that changes you make process and organizationally have had an impact.
"Blocked" operates in real-time. As blockers are added and resolved they are immediately shown on every logged-in user's browser window. You can also add an email address or alias to a team and get email notifications, and/or a Slack channel to get slack messages in the team's channel. Meet the developers and teams where they are - and as much as it pains us, it's probably not our tool!
There is often an overwhelming number of blockers making it hard for teams to know which ones they should resolve first. We help make an organization-wide urgency scale with plain English labels when assigning urgency to a blocker. You can see immediately where your blocker sits on another team's blocker list, and help them understand when it's too low in your opinion. Negotiate!
Avoid double entry, and let people see Blockers where their attention is. Blocked will Flag and add a comment to connected Jira issues when a blocker is Opened, and unflag those issues in Jira when they are Resolved in "Blocked.".
Although you don't need to care or know the mathematics behind how we KNOW tracking blockers and dependencies manipulates lead-time (for the better). "Blocked" didn't happen overnight, and is the culmination of 10 years of understanding the science behind cycle-times in software development data.
Open blockers ordered by urgency