Categorizing Blockers: People, Process, Tooling, Dependencies

If you're an owner reading status updates and sensing a project is stalled without knowing exactly why—this is for you. Most founders treat 'blockers' as a single bucket, but the cure for a person-based delay is nothing like the fix for a tooling gap.

Why Categorizing Blockers Matters for Team Speed

When a team member reports "I'm stuck," it's often delivered as a side note. For a founder or CEO of a 30-500 person company, this lack of precision is a productivity killer. You end up asking three follow-up questions just to understand if you need to talk to a person, buy a software license, or fix a broken workflow.

By enforcing a taxonomy of blockers, you force the team to diagnose the obstacle before it reaches your desk. This shift moves the conversation from "Why isn't this done?" to "I see we have a process bottleneck; let's streamline the approval loop."

The 4 Primary Blocker Categories

1. People Blockers

These occur when progress depends on a specific individual's availability, skill set, or decision.

• Symptoms: Waiting for a manager's sign-off, a key stakeholder being OOO, or a team member lacking the training to complete a task.
• Founder Fix: Re-assigning authority or clarifying the blocker escalation policy.

2. Process Blockers

These are caused by the "way we do things around here." If the rules are slowing down the work, it's a process issue.

• Symptoms: Bureaucratic red tape, redundant meetings, or unclear SOPs.
• Founder Fix: Simplifying the workflow or removing a non-value-added step.

3. Tooling Blockers

Issues related to the software, hardware, or technical environment.

• Symptoms: Broken integrations, lack of access permissions, or slow software performance.
• Founder Fix: Budget approval for better tools or prioritizing IT support tickets.

4. Dependency Blockers

These are items outside the immediate team's control.

• Symptoms: Waiting for a vendor response, a legal review, or a cross-functional partner to finish their piece.
• Founder Fix: Peer-to-peer outreach to the other department head or vendor management.

Tool tip (AIAdvisoryBoard.me): The most effective way to handle these categories is through a consistent Plan → Fact → Gap methodology. By requiring teams to label the "Gap" using these four categories, you gain an instant heat map of where your company is truly stuck. If 80% of your gaps are labeled "Process," you know exactly where to spend your energy on Monday morning. See how the 7-day diagnostic works.

Blocker Labeling Template: Good vs. Bad Examples

| Status Update | Category | Why? | | :--- | :--- | :--- | | Bad: "Still waiting on marketing." | N/A | Vague; creates friction and defensiveness. | | Good: "Blocker: Dependency (Marketing). Need ad copy to finish landing page setup." | Dependency | Clear ownership and specific missing asset. | | Bad: "The software is annoying." | N/A | Subjective; doesn't indicate a path to resolution. | | Good: "Blocker: Tooling. Salesforce API limit reached; manual sync taking 2 hrs/day." | Tooling | Quantifies the pain; points to a technical solution. | | Good: "Blocker: People. Need CEO final approval on pricing before sending the contract." | People | Identifies the specific bottleneck (often the owner). |

How to Implementation a Blocker Taxonomy in 3 Steps

1. Standardize the Labels: Add these four categories to your daily or weekly status report template. Don't allow "Other."
2. Define the Escalation Trigger: Decide when a blocker moves from a team-level problem to a founder-level problem (e.g., any blocker active for >48 hours).
3. Review the Heat Map: Once a month, look at which category is the most frequent. This tells you if you have a hiring problem (People) or a micromanagement problem (Process).

Manager scan (2-minute digest example)

• Total Blockers Active: 12
• People: 2 (Hiring interview lag in Engineering)
• Process: 6 (New QA flow is adding 3 days to every ticket)
• Tooling: 1 (Figma license seat limit reached)
• Dependencies: 3 (Waiting on external legal counsel feedback)
• Observation: Process blockers have tripled this week. The new QA workflow needs a review or it will stall the end-of-month release.

Micro-case (What changes after 7–14 days)

A founder of a 45-person professional services firm was spending nearly 10 hours a week in "alignment meetings" because project delays were always described as "we're just busy." After implementing a mandatory blocker categorization for 14 days, a pattern emerged: 60% of delays were actually "Process" gaps related to the client onboarding form. It wasn't that the team was lazy; the tool they used was so complex that clients stopped halfway through. In one week, the founder simplified the form and reclaimed 6 hours of meeting time because the "why" was finally visible. The team stopped guessing, and the owner stopped micromanaging the staff's daily schedules.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

Tool tip (AIAdvisoryBoard.me): True visibility isn't about knowing what people are doing every minute; it's about seeing the Gaps between the Plan and the Fact. Categorizing blockers is the first step in building a self-healing operations layer where the data tells you where to intervene. Explore the Plan/Fact/Gap methodology here.

FAQ

What if a blocker fits into two categories? Pick the root cause. If you are waiting on a person because the process is slow, it's a Process blocker. If you are waiting on a person because they are the only ones who know how to do it, it's a People (and likely a training) blocker.

How do I encourage the team to actually report blockers? Remove the stigma. As a founder, celebrate the early reporting of blockers. A blocker reported on Tuesday is a problem; a blocker discovered on Friday is a disaster. Align this with your blocker escalation policy.

Can an AI summarize these categories for me? Yes. AI can ingest raw daily updates and automatically tag them with these four categories. However, the team must first provide enough context (who/what/where) for the AI to be accurate.

Should I include dependencies on other internal departments as 'external'? In a 30-500 person company, treat other internal departments as Dependencies. It helps you see where cross-functional friction is slowing down the whole organism.

Conclusion

Categorizing blockers is the fastest way to turn a "messy" company into an efficient one. By separating People, Process, Tooling, and Dependencies, you stop chasing shadows and start solving the real problems that keep your team from shipping. Start this Monday by asking your team to label just one active delay using this framework.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.