> 
> **Summary**: [New Navigation](https://meta.stackoverflow.com/questions/308875/new-navigation-release-candidate) has been removed so we can build similar functionality (plus other improvements) for everyone. I [summarized the feedback below](https://meta.stackoverflow.com/a/360311/1438) to incorporate into the replacement design. (If I missed anything, feel free to add another answer.)
> 
> 
> 

A primary duty of a Q&A system is matching questions with people who can (and are willing) to answer. Stack Exchange sites use an eclectic mix of tagging, filters, search, sorts and [feed algorithms](https://stackoverflow.blog/2010/11/09/stack-overflow-homepage-changes/). We also lean heavily on Google (and other search engines) indexing the content. For sites of a certain size, this system works fairly well. But on Stack Overflow it’s been less than ideal [for years now](https://meta.stackexchange.com/questions/302970/how-is-question-quality-measured-in-a-b-tests). Sklivvz [rationalized those elements](https://meta.stackexchange.com/questions/251095/let-s-improve-our-site-navigation) and [honed the UI](https://meta.stackoverflow.com/questions/308875/new-navigation-release-candidate) so that people can customize their view into the site’s questions. **We’re building on that work so that more people can find questions to answer**.

As you might have gathered from the title, the *paradoxical first step* will be to **disable the beta setting December 4, 2017**. That way we’ll avoid having to maintain two separate code paths as we build better navigation tools. (For those keeping score, this is part of the “Information Architecture investigation” Joe mentioned in the [November update](https://meta.stackexchange.com/questions/301449/2017-teamdag-project-updates/302969#302969).) Flexible and customizable navigation is not only critical to Stack Overflow, but also to [Enterprise](https://www.stackoverflowbusiness.com/enterprise), [Channels](https://meta.stackoverflow.com/questions/358943/what-s-happening-with-channels). So we’re going to make something that works for all of those users. As David Fullerton recently told us, “When working in a shared feature area, rather than developing it only for one area and then ‘porting’ it to another, we must design for all cases.”

![Most common uses of New Nav](https://i.stack.imgur.com/sa3DW.png)

As you can see, many of the saved tabs are available via classic navigation. Many people used the option to “restore old tabs” to get the default tabs back. Anecdotally, I’ve heard some people turned the feature on for the UI convenience and never customized it at all. The other common usage is to create a tab for tags they are particularly interested in. It’s nice to have easy access to all the tags you want to look at right on the page. We probably won’t use the tab interface again (it gets crowded quickly), but we do want to make it easy for you to jump to the tags you care about.

For those of you who rely on saved tabs to find questions, it must be frustrating that we are taking them away even temporarily. Of registered users who have used Stack Overflow recently, 1% have opted in. Roughly 0.6% have saved a search and just over 0.1% have saved a search with a custom name, sort, or filter. The median reputation of New Nav users is 535. Given how little we did to promote the feature and that it was hidden behind a [user preference](https://stackoverflow.com/users/preferences/current), that’s amazing conversion. Clearly there’s something useful going on that we need to build into 3.0.

In order to suss out the key functionality, **what saved tabs do you regularly use that can’t be simulated with bookmarked searches?** For instance, a fairly common saved tab lists a tag’s bountied questions, which is the same as <https://stackoverflow.com/questions/tagged/python?sort=featured>. But some sorts aren’t available, such as sorting by the size of the bounty or when they end. 265 users have saved sorts specific to bounties, but it’s not clear whether they need those sorts to help find questions to answer or if it’s just something they are curious about. 

Obviously it’s better if useful views are built into the site so everyone can access them. That’s the primary reason we are asking. However, we are also asking in case there’s some way we can provide a workaround in the meantime.