To directly answer your question: no, I don't think a massive matrix like this works, even if you only show 30 queues at a time. There's just far too much information on the screen for a manager to take in day-to-day, and far too much visual noise (a user who isn't assigned to a queue does not need to be shown with "0" score.)
Here is what I think you should do, instead.
Write down all of the jobs to be done for this screen. For example:
- I want to see how many queues are open and in need of an agent.
- I want to see which agents are available to take on more queues.
- For each open queue, I want to see the best available agent, based on their score.
- I want to see how many queues are open for an excessively long time (is it because the agent's score is too low? Do I need to bring in someone else?)
Then for each job to be done, you can make a design for that.
I want to see how many queues are open and in need of an agent.
You could show the number of open queues and a list of them. The number would help gauge if things are normal, or getting potentially serious. The list would show what's in need of support, and help assess urgency.
I want to see which agents are available to take on more queues.
You could show a list of agents who are available, or will soon be available, and the system could suggest 3-5 queues to assign them to next. Better yet, the system could use logic based on the agent's profile and score to automatically assign them to their next queue.
For each open queue, I want to see the best possible agent, based on their score. You'd show the empty queues with a list of 3-5 available agents and their corresponding scores, with the option to load more agents.
I want to see how many queues are open for an excessively long time. You'd show the queue, the agent, the agent's score, and the length of time it's been open, with any information as to why,
Would you still need a complete list of every queue / agent assignment? Maybe. Some people like having that view to browse, especially if they're looking for something and can't remember exact spellings. Rather than a matrix, you might just want to build a simple table that can be searched on agent name, queue issue details, etc.
My advice is to take a look at gridviews and tabs vs. matrices, based on what your user is trying to do.