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 responds?

How do you know whether a message is being worked on, or just sitting?

Does using the inbox require additional flagging, categorization, or workarounds that create more problems than they solve?

Shared inboxes are often an easy solution to a problem that wasn't fully diagnosed.

Missed communications, no contingency plan, lack of visibility, and an "all hands on deck" mentality all make a shared inbox feel like the obvious answer. In client-centered organizations especially, the intent is usually right, but the process is all wrong.

Because what is the shared inbox really solving?

• Does it establish clear ownership?

• Does it structure loose workflows?

• Does it support triage and prioritization?

• Does it improve visibility and accountability?

• Does it facilitate delegation?

• Does it support follow-through?

  
  

Not usually. More often, it's introducing another variable that looks like a solution but further muddies the underlying problem.

The goal is to understand what the inbox is doing for the organization—or what it was intended to do—and then determine whether it was the right solution in the first place.

Shared inboxes should support the process, not become the process.

When they become the process, changing the technology alone won't solve much.

(Em dash still mine.)