From Gain ~ Topics: case studies, user research/usability, web design
Case Study: NPR.org
Editor’s note: On July 27, 2009, National Public Radio (NPR) relaunched the website www.npr.org through the efforts of its in-house design team and interactive agency Schematic. The following case study was written at AIGA’s request and coordinated by Sarah Zimmerman. Please contact the editor if you would also like to provide a case study.
Screenshot of the new NPR.org homepage, taken on September 14, 2009. (click to see before and after)
Client name:
National Public Radio (Washington, D.C.)
Project name:
NPR.org redesign
Duration of project:
April 2008–July 2009
Project team:
The redesign team consisted of roughly 30 people: designers, developers, project and product managers and editorial producers. For purposes of this case study, the core design team consisted of:
NPR (in-house)
- Darren Mauro director, user experience
- Jennifer Sharp design director
- Callie Neylan senior designer, user experience
- David Wright senior designer, user experience
- Brian Ingles user experience designer
- K. Libner senior analyst/information architect
- Scott Stroud senior analyst/information architect
Schematic
- Ian Cunningham creative director (New York)
- Tim Smith art director (Atlanta)
- John Ferguson senior designer (Atlanta)
Introduction and justification
NPR embarked on a major redesign of its web presence in April 2008. Its existing web platform and content management system (CMS) were outdated (it had been six years since our last redesign) and failed to provide the functionality for delivery of NPR’s signature storytelling and news reporting. An outside firm—Schematic—was hired to provide the initial visual design and information architecture, but the final product was developed in-house via a collaborative effort among NPR’s editorial, user experience, design and application development teams.
The goal
Our existing site failed to meet audience needs or deliver a news experience consistent with the NPR brand. Our goals for this launch were to provide:
- Flexibility in the presentation layer (via enhanced interactives, multimedia, audio, modularity), and a more intuitive and powerful CMS. NPR is well on its way toward the goal of training all news staff in digital media delivery via a grant from the Knight Foundation and needed a platform to better support these new capabilities. In addition, NPR has made key hires in the past 18 months to build its core multimedia, photojournalism and design teams.
- A redesigned user experience to improve the existing navigation, functionality and overall usability of the previous site.
- Enhanced visual design that strengthened the NPR brand. We were tasked with making visual something that has historically been exclusively audible. Everyone knows what NPR sounds like, but what does NPR look like?
- Improved editorial efficiency. Editorial producers were using a variety of workarounds to manipulate the system. We identified the driving goals behind these workarounds and added new features to the CMS to address editorial needs.
Methodology
Moleskine sketches from lead designers Callie Neylan (left) and David Wright explore layout options for the NPR blog and mobile site. (click for larger image)
In the early stages of the redesign, we were working with Schematic, moving linearly through the design process. Toward the end of the initial design phase, Kinsey Wilson joined NPR as senior VP of digital media, providing clear directives on how he wanted to see the team operate to build upon Schematic’s framework. The in-house product design and development was implemented via Agile development methodologies with a focus on participatory design; we had two editorial producers embedded in our group for the duration of the project. Their feedback was invaluable in helping us design a system that met the needs of our news teams. This involved a physical shuffling of a large number of staff so that the redesign team could work in close proximity. This move happened in February 2009 with a launch date set for July 2009.
Under Kinsey’s direction, we also took part in brainstorming exercises; completely rethinking and restructuring important elements of the information architecture that we felt would not work for our editorial process and/or did not reflect a certain “NPR-ness”; i.e., “wit and whimsy,” according to Dick Meyer, executive editor.
The main limitations were production time and adjusting to a new way of collaborating. We were unable to make as many improvements to the CMS for launch as we would have liked, since we were building upon our existing CMS framework.
During the earliest stages of the project, we conducted interviews and developed user personas representing our existing and potential audiences. The site architecture emerged from our understanding of user goals for finding, hearing, reading, viewing, and interacting with content. We performed several rounds of usabilty tests; these studies validated and improved our navigation model and guided our iterations of page design.
This was the first major project at NPR where Agile development methodologies were used. It took a couple of cycles for the team to adjust to this new way of working and to get into a good flow.
Challenges
Wireframes displaying the underlying grid superimposed over the story page template. In all, there are eight page templates for the site, each serving a specific editorial purpose. (click for larger image)
One of the main challenges was adapting to Agile methodologies. We had to think on our feet, be nimble, iterative and willing to fail often and fast. In some cases, we spent significant amounts of time working through a problem only to realize that our initial idea simply wasn’t going to work. We had to be okay with scrapping time-intensive, developed ideas and completely starting over when necessary.
Each one of us also had to be open-minded and empathetic. When conflicts arose over how best to solve a problem, it was imperative to remember that in the end, we were all working toward the same goal. NPR hires incredibly smart people and we were always challenging each other. This environment was highly conducive to developing a great end product.
This project was also very complex in terms of the sheer number of product users post-launch (there are more than 300 registered users of our CMS) and the information architecture of the system on both the front- and back-ends.
Because of the wide variety of editorial needs, newsrooms present interesting challenges. Post-launch, we are entrusting design tools to people who aren’t trained designers. It continues to be an exercise in the ultimate compromise between form and function.
A sample page out of the NPR.org style guide. (click for larger image)
In terms of design, NPR hasn’t historically been a design-focused organization and therefore lacked any established standard design processes or documentation. One of the main deliverables of the design group was a set of comprehensive style guides: one for the design and development teams, another for our editorial staff. We are focused post-redesign on a more visual way of thinking; the style guide will help us maintain consistency and educate the rest of the organization on the basics and importance of good design.
Results
Results so far have been very positive, although we are still in the immediate post-launch phase. We created a flexible presentation layer that allows our editorial, design and multimedia teams to quickly create new layouts with minimal dev involvement. We also developed a platform with a focus on visuals and photography, allowing for visual NPR storytelling that equals in quality to our renowned audio news delivery.
Our team has also received an incredible amount of positive press for this project, having been written about by The New York Times, Fast Company and the Poynter Institute (and now AIGA). We’re very proud of what our team has accomplished.
Beyond the results
We learned a lot through experimentation with a working prototype; we had a staging server set up that mirrored the actual site and was pulling from live databases. This enabled editors to publish actual content via the prototype, allowing us to identify bugs in the design and editorial workflows before launch.
In any large, complicated project like this, having more time would have been beneficial. However, given the time limitations, we were forced to fail fast and really focus on the most important goals of the redesign. This, I think, helped lead to a simple, elegant solution.
To other design practitioners, I would offer this advice: Design with an open mind. Our project was successful because a group of skilled, talented and passionate individuals were able to bring their skills to the table to solve a problem, while simultaneously recognizing and respecting the skills and talents of their colleagues. In the end, we were all intensely passionate about reaching the same goal.
Further reading
-
Cheers to all involved. There really is nothing quite like the feeling shared amongst colleagues and clients with the launch of a website-- especially a redesign. I'm sure I speak for all interactive designers out there when I say a special bond is formed amongst the involved parties.
Please keep the studies coming. It's great to see others' work, and personally reminds me why I belong to AIGA. The before-and-after presentations never lose their effect; they rejuvenate us designers like nothing else. -
Seems like a lot of people for a website I could most likely build on my own in less than a week...
Nice result, but perhaps a little too much spent. -
Upon further review, I'm really interested to know who endorsed the proposal to have three designers and a design director on a single project? Not to mention a creative director and an art director....wooowzers.
None of the technology offered on the site seems to warrant it... It's all been done and/or is available free online. -
Owen, I agree that they made it look easy. But good luck redesigning a site like NPR in a week, for 300 contributors, who have varying degrees of online know-how.
Just because something has been done before doesn't make it easy. I think it is hard to grasp the scope of this project despite the detailed description we're given. -
Owen, I think that's a bit short-sighted. I can see coming up with the initial concept and basic navigation strategy in a week, but actually working out all of the interactions for that amount of content would take anybody quite a bit of time.
-
Don't forget the reason many of us like what we do: collaboration.
Like the author said, "... we were always challenging each other. This environment was highly conducive to developing a great end product."
If all that's put into one product is one person, that's all you're going to see. Think how much more dynamic and colorful the solution will be if more than one person incubates the egg. The best successes are those that can be shared. -
"I think it is hard to grasp the scope of this project despite the detailed description we're given."
John, you're right. It was hard to condense over a year's worth of work into a succinct case study. And unless you've worked on a large database-driven website like this, hard to grasp the magnitude and complexity of it. I read another comment somewhere mentioning this as a "graphic design" case study. Graphic design was an important part of what we did, for sure, but overall, this was an in-depth exercise in systems design more than anything else.
To clarify, Schematic was only involved until November 2008, when they handed off the final visual design and information architecture (they did the heavy design lifting in the first phase). After that, the remaining design and implementation was done solely via NPR's core team.
Perhaps I should have added screenshots of the content management system. We redesigned that simultaneously with our front-end web presence. So in essence, there were two products being designed at the same time. The complexity lay in how these two products worked together to pull all of NPR's content – past, present, and future – via our databases and API.
What you see on any given page of the site now is the finished presentation of a single scenario. What you don't see are all the other scenarios, especially the worst-case ones, that we had to design for, too. These all had to be integrated into the CMS so the editors have access to the appropriate publishing tools/designs at their disposal. These can vary greatly depending on the news cycle.
Another significant challenge was how to appropriately and effectively implement audio as the core of what we do. Again, the sheer number of scenario variations required that we come up with many different design solutions. -
Large site design endeavors are never easy. Especially with so many stakeholders. I for one (I can hear my team cheering me on with this comment) would love to have the amount of time scoped for this project - not to mention the resources. You've done a brilliant job and I'm sure you're already thinking about design tweaks as I write this. Nice work.
-
I like the new site - looks clean - reminds me of UXmag for some reason - am also curious if having that many designers/creatives working on the same website caused conflict (i.e. too many cooks spoil the broth)?
-
@Joey - During the first phase, Schematic did the UX and design work, with input and critique from NPR's design team, which at that time included me, our design director, and one of our information architects.
During the second phase, after Schematic handed off their deliverables, we were working via the Agile process. Under this method, those at the director level or higher were well-aware of our daily progress and whether or not we met our milestones, but didn't take part in the day-to-day production of the site. They did, however, weigh in when there were design-related differences, helping to make sure we ultimately made decisions based on NPR's overall business goals.
So, surprisingly, there wasn't that much conflict among the designers. As a team, we really had great mojo and all had the same end vision. Have you ever read the book Organizing Genius, by Warren Bennis? He talks about the synergy of creativity and group dynamics. In my experience, this project was similar in spirit to the ones he writes about. -
obviously Owen is not a golfer
(big lebowski reference) -
This is by far a more in-depth review than the visitor perspective quick review/critique that I posted on my blog. Glad to see I wasn't the only one paying attention. =]
http://www.highbrowdesigns.com/blog/2009/08/28/npr-launches-new-look-online/

Comments