The key to Colorado's success? Instead of making people use a new slapdash web portal or provide payroll stubs to prove employment, they simply used their existing UI website and data collection systems.
Placing arbitrary paperwork on potential recipients consistently results in low take-up rates.
It is not surprising that hastily crafted websites with these sorts of burdens failed to deliver to people.
States should think about how they can reduce paperwork, and, like Colorado, think about creative ways they can use existing programs to minimize the burdens placed on the people they are trying to serve.
I think these conversations can often benefit from specific examples.
Here's one: an @ideas42 blog post from my former colleague Nuha Saho about how his experience as a NYCHA resident gave him a lot of knowledge that aided the design of our RCT: ideas42.org/blog/street-sm…
This is just a nice example of the tensions that are often in play here. When we were designing the posters, we initially just did a mail merge with the administrative data to get the name for each house.
But no one actually uses the "official" name for those complexes.
I know we are all all upset about the Child Allowance Website, but I want to register a Formal Complaint to Administrative Burdens twitter about Massachusett's vaxmillionsgiveaway.com
1.) Why the heck is this opt in? Use a state database that covers 90% of the population (for example, driver's licenses), then confirm vaccination upon being drawn.
2.) You need to respond to winning with TWENTY FOUR HOURS to be eligible
The reasons Democrats have "abandoned" work requirements as a guiding principle is that they do not actually perform their intended function - imposing work requirements does not increase labor force participation.'
When policies do not work, we should move on from them.
I though this was a really interesting point. A lot of the jobs (ie, servers) that are trying to hire right now are *especially* unpleasant when they are short staffed.