-
Notifications
You must be signed in to change notification settings - Fork 31
Implement "other spending" tab on candidate pages #700
Comments
I think that is important to separate out, since this is spending affecting a candidate and not spending the candidate is legally responsible for. |
I agree with Lindsay that, however we do this, we need to strongly separate IE spending from the candidate's funds--lots of markers to make that distinction. Thanks! |
+1 |
+1 as well |
Agree on the separation. I also want to call out that usability testing has (But that should be a separate issue) On Thursday, September 17, 2015, Jennifer Thibault notifications@github.com
|
To do: Just adding independent expenditures in a table on a new tab with all the same columns except for candidate. |
Usability testing is indicating that users aren't associating "Other Spending" with the data that will be available on that tab, and therefore aren't clicking. They also don't reliably associate "Independent Expenditures" with Super Pacs. Task:
Don't have good instincts on what to call it (that will pass legal muster); recommend we keep gathering data for now, but it's strikes me that our language isn't matching user expectations yet. |
That's really interesting feedback, I'll get with the FEC team and start coming up with some options to test in the future. Thank you. |
I think the solution is in both redesigning the places where this "other spending" data shows up (like the committee browse page and committee pages, as you reference in other issues), as well as coming up with a better label for the tab. I'm going to break the tab issue out into its own issue and copy your comment there. |
In order for users to see which other groups are making IEs for or against a candidate, we should show them on the candidate's page.
Question for @jenniferthibault and @onezerojeremy : do you think this should just be on a separate tab? We had previously tried to remove tabs from candidate pages but this might be a fine reason to bring them back.
The text was updated successfully, but these errors were encountered: