Loading
Because the shared lists are per project. Somebody on four projects has four lists and no combined view, so they maintain a fifth in a notebook — and that one is the real one.
My tasks is one person's work across every project, filtered to what they own and ordered by what can actually be started.
The queue spans projects, excludes blocked work, and surfaces what is unblocked and due. Blocked items are visible separately, showing what they wait on and who owns it.
Monday morning: the queue shows six actionable tasks across three projects, two things waiting on other people, and one recurring report generating on Wednesday.
It will not order the day for you. It removes what cannot be started and shows what is due; the choice between two urgent things stays a person's.
It reads assignments, dependencies and dates from every project the person is on, plus their leave in Nest so a queue does not build up over a booked holiday.
Yes, where the person owns them.
They can see load through capacity; the personal queue is the person's own.
It shows committed hours against available, which usually answers it.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.