Blog on the Food Insecurity Team ​

Unfortunately, it seems I forgot the team name! 😦((

As a member of the other team working on food pantry & insecurity, I wanted to dive a little deeper into how your queue works, and address some concerns.
In class, one of my teammates asked about the electronic devices question, and you answered that not only were device access pretty easy, but design should not be restricted due to such concerns.
However, in some of our interviews, we noted that a significant portion of patrons did actually have trouble with e-devices, and an active queue management app isn't too useful (at least in my opinion) if the patrons can't check it whenever they want. I do absolutely agree though that design shouldn't be restricted, we chose to only address the volunteers & staff of the pantry due to having a too big scope.

Moving on, I was wondering if you could apply the theories of computer networking here: I've just been learning a lot about queue management lately (including ECN, RED, Droptail(the simple one), DECBit, etc). If you consider patrons to be like packets, the analogy is pretty awesome! Though, you'd definitely not want to drop any packets like the active queue management protocols do...
This led me to wonder, food pantry resources are limited. How will you handle the cases where there's simply not enough resources, and some people will not receive what they want? Does the queue management app only show staff what demand there is, or do you plan to help address some of the other problem domains of food pantries?