Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We received some revisions to the proposed look and feel. On July 27th the ZEST:attached PDF was provided as feedback along with the following comments in email: 
Okay, I have collected the feedback for you.  I'm presenting it in raw form, because I don't want to put a barrier between you and ideas unless it is actually helpful.   One thing I can say - you don't need to worry overmuch about the fiddly details of text.  We need help figuring out where we need a heading, a sentence, or a paragraph, but given a general idea of what should be where, we feel comfortable hashing it out with the various internal folks who need to be satisfied.  So long as I understand what you're referring to in a particular place, I can talk to them and figure out what the final words should be.
 
One of the replies is in the form of a pdf file (attached), and the rest are in text, below:

-----------------------
One piece of feedback on the "success" pages for tickets and certificates -- having just a checkbox for the "Always use ..." options is problematic, since the "continue" button takes you back to the calling web site.  That's why we're using a button for this currently in the test environment. (We could have a checkbox with, say, a "Save" button for it, but it seems better to minimize the number of clicks a user has to make).

Wiki Markup
\[ZEST:The other idea we have discussed is to have a checkbox like this on the login page, and perhaps have a separate (new) page allowing you to set the preference.  But that would require fairly significant effort, which I fear we don't have time for at this point.\]

...

It seems that we are asking users to self-identify according to categories which are set by us and meaningful to us. All the users want to do is get to a page via a link that they clicked on. This page is a barrier, both visually and functionally, as it stops the user's progress through the MIT experience dead in its tracks. It needs to be an interchange, like on a highway, with clear road signs. Rather than asking users to provide information according to our needs, why don't we try to see the matter from the users' perspective and anticipate what would be meaningful to them? Then we can use labels and text in a way that leads them in the direction of doing the correct thing without forcing them to stop and ponder.

Sample images of the evolution of the UI