Intake Queue
One visible queue for work that arrives from five different directions.
What we do
We capture from the channels people already use, so nobody has to be told to ask differently, then size and classify each request against past ones.
The problem
Requests come by chat, by email, in a meeting, in the corridor, and once as an urgent message to somebody's personal line on a Saturday. There is no list, so priority goes to whoever asked most recently or most loudly, and the team's real capacity is invisible to everyone, including the team.
The fix
One intake, whatever channel it arrived through. Each request captured with what is being asked, by when, and what it is for. Priority becomes a decision the manager makes on a visible list, instead of a reflex to whoever is standing in the room.
How it was built
Capture from the channels people already use, so nobody has to be told to ask differently. Classify and size each request against past ones.
What it left behind
A record of what this team actually spends its year on, which is rarely what the job description says.