When I was working on redesigning parts of the NASA/Astrophysics Data System (ADS), I looked for opportunities to streamline the experience for the scientists, students and other researchers who use the site.
It was very helpful talking to scientists and science librarians about the aspects of the interface they used most heavily. To supplement user interviews, I used Google Analytics custom events to explore which features in the existing interface were heavily trafficked and which were generally ignored. This information combined to inform my decision of which elements to highlight, which to de-emphasize, and which to remove altogether.
Below I provide some screen comparisons of a few of the pages I redesigned and re-implemented in JS, HTML and CSS.
For the redesign of the search results page, I emphasized scannability, situating the search result titles as the main focal point. Since Google Analytics showed that sort operations were the most common operation on a set of search results, I raised the visual profile of the sort selector. Across the board, I increased font sizes.
This one is cheating a bit, since the predecessor system I'm generally showing in the "older version" tabs was retired before I thought to get a screen shot of its abstract page. Instead, I show the original system's abstract page (the original system is still heavily in use as it is the one that astrophysics researchers are most familiar with, so thousands of people still see this page each week!) I focused on hierarchy and contrast and added a left navigation panel to bring order and scannability to the page.
ADS libraries are a place where users can store their personal collections of papers. They have many purposes and could serve as a quick reading list, a convenient way to generate metrics, or a list intended for public consumption. In the original implementation, there was lots of explanatory text and the main functions of the library—to explore your library collection or possibly add a library— were not as obvious. My redesign simplifies things considerably, with some of the least-used functionality being removed entirely, or moved elsewhere.
With this page I focused on using hierarchy and alignment to allow a user to, at a glance, understand the significant metadata attached to their library and the actions they can undertake on their library (manage permissions, export, visualize...).