Tag Archives: information architecture

Goodbye IMDb, hello…

kilbo-logo…independent consulting practice & stealth startup!

I’m incredibly excited to announce that I am now a freelance consultant specializing in customer & user experience analysis, and information & content architecture for mobile applications and the web.

For the past eleven years, I’ve had the privilege of working at two of the top 25 Fortune 500 companies in the world, Amazon (IMDb) and Microsoft. Combined, the products I’ve worked on have over 100MM downloads for Android and iOS, and over 300MM website visitors a month. It’s been exhilarating and humbling to work on properties at that scale with some wicked smart people.

But for a few years now I’ve been wanting to get back to working for myself and have the flexibility to be around more for my kids. After a year working with my IMDb colleagues to set a new information architecture, apply a new Material design, and get the wheels turning on development, (launching soon-ish!) it’s now time to strike out on my own.

So, if you know anyone that needs help tuning up or launching an app or website, I’d really appreciate a referral! The best way to contact me is through my LinkedIn profile at https://www.linkedin.com/in/kilbo.

And, because I also miss my startup roots, I’m also incubating a new company. Over the winter I’ll be working on the business plan and expect to be ready to scale and launch the new idea in the first quarter of 2017.

Stay tuned!

Goodbye Microsoft, hello…

…IMDb*!

I am very pleased to announce that I was extended and have accepted an offer to work at IMDb (Internet Movie Database) as a Senior Product Manager. I’ll be doing product manager-y stuff like helping to align the mobile and website user experiences and information architecture for the quarter of a billion people who visit every month.

It is very much a dream job for me and I am both humbled and elated that I’ll be able to practice my craft on an Internet property with such a tremendous history and reach. Feel free to start sending me your suggestions now. ūüôā

To all my Microsoft colleagues: Thank you for the last nine years! I’m going to miss your passion and your brains. We did some great work together and I look forward to seeing what you do next.

(* A wholly owned subsidiary of Amazon.com, Inc.)

The Office Developer Center Redesign

My team, in conjunction with partners across Microsoft, shipped a new Office Developer Center experience at http://dev.office.com this morning.

The New Office Developer Center

The New Office Developer Center

I’m incredibly proud of the work we all did. This was a hugely complex project that saw us combine six different developer centers into one, consolidate a little over 200 pages down to 24, re-write every single page, and simultaneously reset the global experience across 11 languages.

This was arguably the most challenging project I’ve worked on here at Microsoft and presented the thorniest information architecture problem I’ve ever encountered.

The Office family of products spans multiple products with their own hierarchies of brands and tasks for developers. At the top level, there is Office, SharePoint, Exchange, and Lync. Within Office alone there is Access, Excel, InfoPath, OneNote, Outlook, PowerPoint, Project, Publisher, Visio, and Word. Microsoft is also asking developers to write apps for Office and for SharePoint, and the development details are a bit different between Office and SharePoint. Add in Office 365 service content, and you have many different pivots you could apply.

Then we had to consider that we’re always balancing between the past, present, and future when we’re talking about development. There is a huge audience of developers who have written code to older versions of Office, a smaller set that’s targeting the current version, and then Microsoft is trying to guide developers to be set up for the future evolution of the platform.

The challenge here boiled down to: what information architecture would expose the breadth and depth of the product offerings, feature current and future development options, and not alienate developers targeting previous versions?

We had many, long discussions around the right pivots here, and in the end we decided to stick with the top-level product names as the main pivots for the navigation, and placed app development messaging on pages where it was product-relevant.

How’d we do?

The Redesigned Visual Studio Developer Center

If you’re a frequent visitor to the Visual Studio Developer Center on MSDN, you’ll notice that we just switched things around a bit. Okay, quite a lot, actually!

We’ve fundamentally changed the information architecture of the site, implemented a regular page pattern for non-Library pages and significantly shrunk the number of non-Library pages on the site.

Information Architecture Changes

Over the past six months, my team and I have been looking closely at site metrics around page views, clicks on pages, survey and other site feedback, and other data available to us around how developers use the site. What emerged from that noise of data were some clear signals about how the site was being used and we’ve tried our best to respond with updated site navigation and content organization.

The most obvious change is in the site navigation:

The Old Visual Studio Developer Center Header Navigation

The New Visual Studio Developer Center Header Navigation

The Old Visual Studio Developer Center Footer Navigation

The New Visual Studio Developer Center Footer Navigation

The biggest change is moving from eight items to six and the addition of sub-navigation links.

What went away were top-level links to Support and Downloads.

The Support link was rarely clicked and the page itself did not receive that much traffic, so that was an easy choice. On the other hand, the Downloads navigation link was consistently the most-clicked link in the header navigation and surfaced as a top task on the site as a whole.

So why remove Downloads from the site navigation? It seems counter-intuitive to do so. In the old model we had a dedicated downloads page that aggregated links to most of the popular or key downloads and these links¬†spanned Visual Studio and Team Foundation Server. Finding the download you were looking for involved skimming a few dozen links and if you didn’t find it, you were pretty much stuck performing a site search or going back to your favorite Internet search engine.

In the new model, downloads are now part of the page-level information architecture as a regular link block, appear on every page, are scoped to the topic of the page they appear on, and usually provide an “all downloads” link that takes you to the Microsoft Download Center. I’m very curious what you think of this change, since it’s a big one.

Other visible changes of note are changing Library to Documentation, Learn to Languages, and the addition of sub-navigation links.

Library, as a term, has specific connotations for developers in general and Microsoft developers in particular. To avoid potential confusion for non-Microsoft developers and in the interest of clarity, changing to Documentation more accurately reflects what you can expect to find behind that link.

When we looked at the data around¬†Learn, it was clear that developers were looking for language-specific learning resources more than anything. In fact, wherever we had a language learning link, it often was the most-clicked link on the page. By elevating Languages to the top-level navigation, we’re hoping that when you come in to the site via search, which many of you do, you’re now only a click away from those language learning resources.

The reasons behind the addition of sub-navigation items were twofold: more clearly represent the lower-level structure of the reorganized site in the header and provide a sitemap like experience in the footer. Hopefully this will help with the, “Where the heck is ‘foo’?”

Under the hood and not so obviously, the navigation now reflects the underlying content information architecture that pivots around products, samples,¬†languages, extensions, documentation and community. Each one of these “buckets” now only contains content aligned with it, whereas before we had all sorts of stuff spread across the entire site.

Regular Page Pattern

I’m a strong believer that regularized page patterns assist repeat site visitors and that placing things in standard spots reduces the cognitive burden of analyzing a page for the task you are trying to complete. Prior to today, we had pages that more or less followed a handful of page patterns, and several that were freeform designs. If you had picked five pages at random from the site and examined their functional layout, chances are none of them would have matched.

As much as possible, (there are always exceptions,) we have a single page pattern across the site:

The New Page Pattern

As much as possible, we have contextualized the links in the right-hand column to provide the most-requested downloads and link you to places that make the most sense when coming from this page.

I’m hoping that if you’re a frequent visitor of the site, you’ll be able to more quickly find what you’re looking for, because now things will always be in the same place on the page.

Page Reduction

How many web pages does a website need? It depends.

In the case of Visual Studio, we had around 323, give or take a handful. The traffic graph yielded a curve like this, with the long tail being very flat when you looked out to the end:

When I see something like this across hundreds of pages, I naturally ask, “What are those pages that aren’t getting much traffic and do we need them?” As we¬†clicked through each page of the site, what we discovered was that most of them were very out of date or had been shimmed into the site to solve some short-term need and then forgotten. Others were important to internal, company¬†stakeholders but uninteresting to customers.

After careful deliberation, we’ve removed and redirected hundreds of pages. The site is now about 80 pages, which we’re going to be continually working on driving down to under 50. The core site, which you directly access via the navigation and sub-navigation elements, is 11 pages.

By doing this, we’re hoping that your search experience just become a whole lot better. Fewer pages with completely re-written, focused content limited to a single topic should provide better search engine results than many diffuse¬†pages that span multiple topics.

Please let me know what you think about this new experience in the comments, as I’d love to have more input as we consider the future evolution of the site.

My New Job

Visual Studio 2012 shipped last month, so the rhythm of the business shifted to reorganizing for the next product cycle. As a part of the reshuffling, my job scope expanded from overseeing the Visual Studio Developer Center¬†to the MSDN proper and Team Foundation Service¬†websites. My charter covers content presentation, information architecture and experience integration. That’s a fancy way of saying, “Help build a more useful and pleasant to visit website.”

MSDN, according to Alexa, receives about 11% of all web traffic directed to microsoft.com, so I’m really looking forward to helping shift the experience for the millions of customers that visit the site. If you’re one of those customers, feel free to let me know what you do and don’t like about MSDN, and I’ll incorporate that into the evolving plans.

My team has also grown and I’m very happy to be working with some of the same people that I worked with a few years back when I was Lead Site Manager for TechNet*.

I already have some ideas about some things I’d like to see change and I’ll be highlighting them here going forward; don’t be shy about telling me what does and doesn’t work. ūüėČ

(*Having helped launch Microsoft Answers¬†in 2008, I’ve now officially¬†worked across¬†the Microsoft technical website audience triad of Developer, IT Pro and Consumer. It’s amazing and humbling when I start to think of the millions of people that have interacted with my work. Very few places in the world have that scale opportunity and I feel fortunate¬†for the opportunity.)