Second set of navigation arrows

[cmc333333]

Add “Previous” and “Next” navigation buttons at the top of the pages (i.e. arrows underneath “effective date”), instead of only at the bottom.

Should be simple, though we'll want to confirm this doesn't junk the interface up too much.

[tadhg-ohiggins]

So we're talking about something like this?

[cmc333333]

That's my understanding. I'd appreciate a gut check from @micahtaylor and/or @carodew that it's not complicating the interface too much, and whether or not it makes sense to add to all clients or just ATF.

[carodew]

Oh wow I didn't think we had committed to doing this. I don't recommend proceeding because I think it makes it much more difficult to tell what is important in terms of visual hierarchy, this hasn't gone through any design or usability testing, and it's not based on user research.

[cmc333333]

Makes sense; I think this was the riskiest of the quick wins. Moving to the Abyss for later evaluation.

[carodew]

Ok, makes sense.

Sorry if my previous response was curt, I was a little surprised. My main concern is that adding so much extra visual information in the UI can be really disruptive of the information hierarchy and can potentially confuse users who then don't have a clear visual path for what to look at, and we already have a lot of visual information on the screen. I've also not seen any user struggle with navigating the app, so it seems like a rather large risk to take without usability testing or a strong indication of a deficit in navigation options.