Open Linda-Vu opened 3 days ago
@sydney-devine heads up - we're looking to add these fields in Django admin due to user feedback that we received.
@sydney-devine heads up - we're looking to add these fields in Django admin due to user feedback that we received.
Hi Linda,
Understand it came from user feedback, but going to play devil's advocate at least for the first bullet that we shouldn't always follow it. People don't read, and we know this. We made a very conscious call to not have any blockers, especially on mobile, to take people away from the big call to action, which is to go apply for the benefit. I don't think we should put any description for the benefit at the top. If someone actually wants to actively read about the benefit, they will scroll for it, but because people aren't going to read anyways, we shouldn't push the apply button further down on the page because that's the biggest call to action and thing we want to steer a user towards doing first. Happy to get on a call tomorrow before I'm gone and discuss this more, but this doesn't seem like a good use of dev time.
Also, what description is needed/suggested under Key documents?? It feels self explanatory?
@sydney-devine Some programs need a sentence to let people know what it is. We'll keep it short. Y'all can always leave it blank.
Not all key documents are actually going to be needed from the applicant. The agency is also required to do due diligence in looking up information that's already in government records. By putting a long list of "required key documents" some applicants may be intimidated from applying because they are "missing" a document. A short sentence will let applicant know it's fine if they don't have everything.
@sydney-devine Some programs need a sentence to let people know what it is. We'll keep it short. Y'all can always leave it blank.
Not all key documents are actually going to be needed from the applicant. The agency is also required to do due diligence in looking up information that's already in government records. By putting a long list of "required key documents" some applicants may be intimidated from applying because they are "missing" a document. A short sentence will let applicant know it's fine if they don't have everything.
Why not just list the actual required list then vs. the items they don't necessarily need? We also have the warning message box if it's something that impacts the application process. I think it's worth talking about the UI here before making the changes. Whoever codes this also needs to work around where the warning messages would come up.
@sydney-devine we can't "just list the actual required list then vs. the items they don't necessarily need" because we won't know what information the state agency can verify electronically for each household vs. things they will need to provide documentary proof of - each household will be different. Our goal here is to make it clear to people that the list is information and documents the household may need to provide and remind people that they should apply even if they don't have all this information because the state agency has a responsibility to help them verify their eligibility. Hope that makes sense!
@sydney-devine we can't "just list the actual required list then vs. the items they don't necessarily need" because we won't know what information the state agency can verify electronically for each household vs. things they will need to provide documentary proof of - each household will be different. Our goal here is to make it clear to people that the list is information and documents the household may need to provide and remind people that they should apply even if they don't have all this information because the state agency has a responsibility to help them verify their eligibility. Hope that makes sense!
Isn't it easier to just make that heading configurable to say Key Documents You May Need or something to that effect then? User behavior tells us people aren't going to read the sentences underneath before the list. Might be cleaner to just update the heading to drive that result.
The thing we should avoid is overstating things in copy that we know isn't going to get read. This goes along with the call to action on the page and not wanting to push it further down in the UI.
@sydney-devine we'll hold off and chat about this with you at our next sync once you're back!
Fields we'd like to add:
Technical notes: we'll likely need backend and frontend work to accomplish this. Link your PRs for both in this issue.