@jefito: Of course software companies need to make difficult choices. Users are the WORST people to define features. they are great at helping product teams develop insights about users needs. Understanding users is critical to effective software development. Ignoring users is (perhaps there is a better word, but it resonates to me as ...) arrogance. Products need to be built for markets which have segments of users. I'm making the observation that there is a LARGE segment of users who are used to working with content structured in outline form. This is very different than tags which are meta information, an abstraction that is not easy for many people to get. I have no idea what the answer is (subnotebooks, new views, etc.) but I'm certain there is a problem for a sizable market. I've reviewed several threads on this topic and my conclusion (hypotheses really) are: 1. There are a large number (perhaps 5% ???) of the existing evernote community that would prefer a different abstraction. 2. I think it is reasonable to presume there is a large number of people who have tried to use evernote but stopped becuase of this issue (perhaps 10% of the existing user base - note its the dominant abstraction in outlook, onenote, etc.) 3. The discussions I have seen are all incredibly polarized about the ANSWER - changing the architecture or philosophical. I've seen a LOT of real hostility around this issue, as if it is an either/ or A/B right or wrong solution. 4. Since none of the proposed solutions seem to work the issue is dismissed (no published roadmap so all speculation) and there has been NOTHING presented to address or even acknowledge the underlying problem. my conclusion is that there is an arrogance on the part of Evernote or perhaps it's just a forum filled with uninformed voices, because they are assuming that potentially 15% of their users should change their behavior. 5. I like to think of myself as a pragmatist. I really really want to be able to use this tool. I think there are others like me. Changing a users behavior is possible, but hard. I think there should be an open and inclusive discussion to see if this large group of users needs can be accommodated with modest effort and without disrupting the architecture or workflow of current users. Who knows, this might lead to a much larger market share.....