top of page

Tool: System Failure Diagnostic

  • Writer: Britt Turner
    Britt Turner
  • 3 days ago
  • 1 min read

Many organizational problems aren't people problems. They're systems problems. The challenge is that "systems problem" isn't a diagnosis.


So where do you start?


When I'm trying to understand why a process isn't working, I don't start with solutions.


I start with questions.

  • Who owns the process?

  • Can anyone see where work is sitting?

  • Where does work change hands?  

  • Is the process documented?

  • How do people report problems, and what happens after they do?


None of those questions tells you the answer. But together, they tell you where to look.


I've put those questions into a one-page System Failure Diagnostic you can use before deciding whether you need more staff, different technology, or a new process.


Sometimes the problem really is capacity. Sometimes it isn't.


The point is to diagnose before you prescribe.

Recent Posts

See All
Are Shared Inboxes a Solution?

Shared inboxes are a great place to start asking questions. Who decides what's urgent? How is work assigned? What happens when two people assume the other is handling it? What happens when no one resp

 
 
 
We Need More People!

We've all run into situations where an organization decides on a solution before fully diagnosing the problem. Not surprisingly, it doesn't work. One of the biggest conclusions I see organizations jum

 
 
 
Organizations Are Full Of Elevens

Eleven is a design failure. We count: Ten. Eleven. Twelve. Thirteen... Then suddenly: Twenty-one. Twenty-two. Twenty-three. If we were inventing English today, would anyone create "eleven" and "twelve

 
 
 

Comments


CONNECT

  • LinkedIn
bottom of page