Case Study - InVision's Blog becomes Inside Design

In the beginning, there was the InVision blog. It had become a source of inspiration, entertainment, news, and guidance for designers around the world. Pretty great, right? But like any startup, the team at InVision wondered, “How can we do more? How can we make it better?”

I was part of the team that transformed the InVision blog into Inside Design, a website that aims to be more than just a list of blog posts. We started with a lofty goal: create a destination that focuses on finding and surfacing engaging and helpful content in a more personalized and captivating way. Not an easy task, but one that we were excited to undertake. Here’s how we did it.

Our challenges

Every day, thousands of designers, design leaders, writers, and strategists visit the InVision blog in search of something. Some come looking for inspiration; others are seeking advice and guidance on topics ranging from the next step in their careers to the next new tool to add to their design stack. Our mission has always been to be a blog written by designers for designers.

But one day, we realized that our efforts and goals had outgrown our current setup. We had become a one-stop destination for designers, but that one stop more often than not was literally one stop: readers would visit the site, read one post, and then bounce on to other, more engaging destinations.

We were also getting feedback that our page style and functionality were dated, especially for a blog focused on design. We should have been setting trends, not catching up to them. Features like a persistent navigation bar and a search function weren’t just “nice-to-haves”; they’d become industry standards.

In addition, our ways of displaying and featuring new content had gotten stale and, frankly, a bit lazy. The five newest posts were featured in a rotating hero banner at the top of the page while the remaining posts were listed with a title and a hero image in chronological order. That was it. No additional information (like a category, author, or even a publish date) was provided.

So we formed an interdisciplinary UX team to make some necessary changes. Instead of stumbling blindly into a brand redesign, we took a design thinking approach to our redesign:

  • we developed empathy with our readers by conducting user testing and user interviews;
  • we took the time to define the specific problems we were facing (engagement, discoverability, personalization);
  • we generated many variations and approaches to see what would be the best fit;
  • and we tested, tested, and tested more until we settled on a version 1.0 of a publication that made us proud and made strides towards addressing the feedback we’d gathered.

Our research

We did a ton of user research upfront, and we used all of the data we collected to inform our early variations. We didn’t just speculate that there was an opportunity for us to improve the reading experience; we knew there was an appetite from the community for deeper, better improvements to the entire blog.

For instance, one of the A/B tests we ran on the front page was a restructuring of the hero carousel and featured posts into a more mosaic-like format in an effort to get more content “above the fold”. The results?

  • The mosaic variation resulted in a 330% increase in clicks on the featured articles with no significant impact on clicks of non-featured articles
  • The variation resulted in a 46% increase in total article clicks on the homepage
  • Around 30% of the total clicks on featured articles was on the bigger featured article on the left side of the page
  • There was no significant impact on bounce rate or digest subscriptions

Our next hypothesis was that we could increase clicks in the hero section even more if we swapped out the content once the reader clicked on it. There’s more information on this change in the Personalization section below.

Another hypothesis we had centered around adding a navigation element to the front page. By adding links to category pages, we believed we could increase readers’ pages per session and time on site on the blog.

The addition of blog navigation increased pages per session by 6% and lowered the bounce rate by 3%. This confirmed our hypothesis that adding a navigation would encourage more exploration within the blog. The addition of the navigation had a negative impact on clicks on featured articles and non-featured articles on the homepage, but that makes sense because readers were clicking on the navigation elements instead of the featured posts.


Our process

After reviewing our research and prioritizing our needs based on resource availability and reader feedback, we made some changes. Here’s what they were:

Engagement

Front Page

After reviewing the user research, we tested and redesigned the front page to give readers the content they actually want to see: relevant content that’s timely and that fulfills a need, whether that’s inspiration, advice, or staying up-to-date with design trends. We made the content easy to find, and we organized it by relevance instead of publication date.

One of our biggest UX problems was designing the grid. In the previous blog, the featured content was in a hero carousel above the fold; the rest of the content lived below the fold with no established hierarchy. Our testing showed that a mosaic layout was more consumable than a list view, but we needed to figure out how many articles would be featured at once, and how featured articles would get categorized (top stories, most recent, editor’s picks, etc.).

pz66pNz.jpg
After

In the end, we decided to scale back the amount of content presented. This was mainly because only one to two new articles would be published a day at launch, so initially, keeping the grid updated and relevant would be challenging.

My role as a content strategist was to help the team analyze the flow of new content. I managed both the editorial calendar and the staging of posts in the CMS including the categorization and organization of content types to ensure we had a steady stream of content to publish and a variety of topics and types of content to feature.

Article Pages

During user testing, we found that inline modules that interrupted the reading experience received very negative feedback. That being said, we wanted to find a way to add helpful, contextual content without being invasive and annoying.

To achieve that, we added a featured post module with a call-to-action to the bottom of articles and a context sidebar to the article page. This sidebar scrolls alongside the article and contextually populates link previews, pull quotes, ads, and related InVision products. It acts as a companion piece to each article and keeps the reader engaged while scrolling.

My role as a content strategist was to find a way to make the best use of these new sidebar modules to increase social sharing, page views of related content, and clickthroughs to other InVision products. I was responsible for handpicking every item that appeared inline and in the sidebar, and I had to find a balance between providing additional helpful content and staying out of the readers’ way.

Discoverability

Front page

The InVision Blog had tons of great content, but it was difficult to find what you were looking for. There wasn’t a hierarchy to any of the category pages, and it lacked a main navigation. The reader could easily become frustrated trying to find the content they wanted, making increased bounce rates an issue across the blog. So we created a top-level navigation and added several content categories as well as a search bar to help readers find exactly what they were looking for.

As a content strategist, I was tasked with creating and editing the taxonomic structure of our content within the CMS. While a full-scale qualitative content audit is on the calendar for the beginning of net year, some of the short-term changes I made included:

  • making use of both categories and tags for improved search functionality
  • recategorizing a large number of posts from the catch-all “design” category to new categories that were more specific (like accessible design, UX Design, UI design, design resources, etc.).
  • adding categories and tags for specific types of content (like video) that improved the experience for readers and allowed for a Featured Videos module on the front page

Other pages

In addition, we wanted each type of page (new design resources, videos, category pages, author pages, etc.) to be templated but also flexible enough that modules could drop in and out based on different needs. The category and author pages in particular were designed to essentially be their own home pages that placed focus on the content.

I was brought in to offer insight into the types of content in our database and on our editorial calendar to ensure that every possible content type was accounted for.

Personalization

Personalization is an ongoing project on the blog redesign team. The major changes we made in this area revolve around the use of cookies to aid in personalizing what content is featured for each reader. As the blog’s content strategist, I added the Top Stories modules to each article page which showcases three popular posts that are specific to each reader’s viewing history. I also optimized all new content to be featured both on the front page and in the sidebar by editing images and meta copy to be helpful and informative without being distracting.

Conclusions and the path ahead

The first version of the Inside Design restyle went live for 10% of visitors in early September 2018 and was expanded to include 100% of visitors two weeks later. Qualitative feedback from both the on-page survey and our social media channels was predominantly positive. Readers were happy to see us catching up with features they liked from other blogs. Feedback on the new design features was positive as well.

Metrics-wise, there was a dip in organic search traffic immediately after launch that the engineering team chalked up to Google’s search algorithm re-crawling the new site with a different URL (we changed from http://invisionapp.com/blog to http://invisionapp.com/inside-design/). After the dip smoothed out, the site saw a 10-15% increase in both page views and time-on-site along with a 20% drop in bounce rate. Likewise, signups for both the email digest and the SaaS product increased.

Moving forward, the team wants to do much more with personalization to make visiting the blog a more individualized experience. In addition, there are the requisite bugs and broken things that come along with a 1.0 release. From a content standpoint, the plan is to split time publishing new content of all kinds (text, video, social) while nursing and polishing excellent content that’s already part of the InVision blog database.

What it Takes to Make a Podcast

There's been plenty of talk lately about podcasting: what constitutes "quality", what kinds of equipment to use, how heavily to edit. Podcast network chief Dan Benjamin recently started a podcast about podcasting. Thanks to the AMAZING Serial, there's even talk of a "podcast Renaissance ". While the main focus here on the Uprising is to focus on high-quality work and the awesome people that produce it, I thought it would be a great time to take a look at what creating a podcast, from scratch without help from NPR or Planet Money, looks like from conception to pressing publish.

Step 1: It's Gotta Start Somewhere

Before I started writing here, my thoughts were limited to a few scattered tweets and my ill-fated career in journalism. When it finally got to the point that I felt like I had something worthwhile to say, I realized I hadn't written anything of considerable length on the internet since Xanga was still a thing. I investigated a few different options and decided Tumblr was the best fit for my haphazard writing (and thinking) style.

Along with being a great place to easily post whatever's on my mind, Tumblr has also made it easy to upload and share audio. I've been wanting to do a podcast for years, and I've always thought about a career in broadcast radio. I knew when I started this blog that I also wanted to do a podcast. I wanted to speak at length to someone about something; I just didn't have the focus or direction to make it happen. I mentioned the blog and the podcast to Rob, he asked it he could be a part of it, and we were set.

On a recent episode of Upgrade, Myke Hurley (the host and co-creator of podcast network Relay.fm) gave some advice to beginning podcasters. His first point was to find a friend. I'm glad I've got that part figured out.

Step 2: Prep Work

I started with a list of topics we wanted to discuss and some (in my mind) very ambitious goals for guests. We're working our way down that list now. I'll typically pick two or three topics that sound interesting to me on any given week, and Rob and I will talk about who we should ask to be our guest.

As of now, we haven't booked our first guest. Let us know if you're interested in talking to us about something awesome!

After that, I'll research both our topic and our guest so that I'm familiar with the essential information. I'll make an outline or a list of questions I want to make sure we ask, and I'll share that document with Rob via Google Drive so that he can add questions or talking points (and so that he's not walking in blind. Don't surprise the engineer).

Step 3: Just Press Record

Recording is actually the easy part. Rob and I record what's commonly (and comically) referred to as a "double ender". Once we're connected via Skype, we each record our own side of the conversation in order to sync them up later. As far as equipment goes, Rob uses a Blue Yeti Pro fed in a Behringer Q1202USB 12-Channel Mixer. I've used a USB headset to record up until recently when I purchased what I lovingly refer to as "the Vader edition" of the Blue Yeti on an Amazon Lightning Deal. I record my audio via Audacity, and Rob records and edits in Adobe Audition. I prefer Audacity because it's free, easy, and does everything I need it to do. Rob uses Audition namely because it's included in his Adobe Creative Cloud subscription.

Step 4: Clean Up on Aisle 4

After we finish recording, I export my side of the audio as an mp3 and upload it to a shared Dropbox folder. I share a link to the via with Rob via Slack.

Slack is an ENTIRELY different post. Suffice to say, if you work on any type of collaborative effort and you're not using Slack for communication and file sharing, you're probably doing it wrong.

Rob downloads the file and adds my portion (along with his original recording) into Audition. Using some kind of magic that involves time markers, a trackpad, and tons of patience (mind you, he has to listen to me say everything again), he puts us together, cuts out the garbage (both sound and content), mixes it down to one file, puts it back in Dropbox, and pings me in Slack to let me know it's there. I listen back to the "final copy" and let him know if I notice anything off. I usually don't.

During his whole "fun and games with Audition" session (which can take anywhere from a couple of days to a week, depending on our J-O-B schedules), I'm working on the show notes. I'm so easily distracted that I have to listen back to the show at least twice with a notebook and pencil to make sure I don't miss anything. As narcissistic as this may sound, it's typically only my side of the audio because he's still working on making us sound better and more coherent than we typically are. After listening to myself ramble off-topic for large chunks of time, hoping I don't miss a reference to a link, I respect the hard and often annoying work he has to do. On my end, I'm both lackadaisical and very particular about show notes. As a listener, I know how much I enjoy having a visual resource I can refer back to later. As a show host, I frankly find all of the work-- looking for, locating, cutting, pasting, and formatting links into a format that's easy to publish and also easy to read-- to be a pain in the ass. Fortunately for our reader/listeners, I tend to write show notes more akin to ATP than Nerds on Draft (both awesome podcasts in their own rights).

I'm still working on the best way to post the podcast and the show notes in a way that makes sense. We're planning the switchover to Squarespace, and it looks like that'll make things a bit more seamless when we're trying to work with things like feeds and syndication in iTunes.

I think it's an interesting aside that iTunes and Skype are both regarded as "lacking" in their respective spaces, but they both continue to be tools on which podcasters must rely. Allen Pike has a great article on why, at least as far as Skype is concerned, we haven't been able to do any better.

Step 5: You Got a Promotion!

I don't want to say we promote the podcast so much as we let people know it's available and it exists. Neither Rob nor myself started down this road because we thought it would lead to fame and riches. We do it because we love podcasts and because we feel like we have something of value to add to the community. I love to learn; it's one of the reasons I continue to go to school every day (it's certainly not for the paycheck). It sounds corny, but I hope I can teach our listeners something whenever they decide to spend their commute or free time listening to us prattle on about something for an hour at a time.

So that's pretty much it: alpha to omega with plenty in between. We're not by any means experts (or even very good at it yet). The important thing to us and to our audience is that we love it. We're committed to making a high-quality product that we would want to download and hear. It's not fancy. We don't have separate recording machines or an IRC channel for live chat, or even our first real guest. But, as Marco Arment puts it, we care, and it's only the beginning.