In the design of an information or knowledge-based system, values are built in to the fundamental assumptions about what information and knowledge actually is. Such values can be understood in an overarching and philosophical sense, as well as in a situated sense within certain communities, organizations, and particular types of users. In fact, such fundamental reflections are an essential first step to ensure that the knowledge-based initiative has a clear trajectory to follow. The design of knowledge organization — not the adaptation and implementation of standard or popular classification systems — is a phase that most people ignore out of convenience for a quick launch of a beta version, or a tight budget that needs to be spent for a clear ROI. The benefits of designing a knowledge organization strategy (which may involve conducting domain analysis, user studies, genre and document mapping) are not concrete, but it is fundamental to the long-term success of any information and knowledge-based undertaking. In fact, the whole process might not be that different from engaging in a philosophical discourse on epistemology, or a reflection about the nature of knowledge, but situated in a real-life context with design implications (whether that’s system design, website design, or library design). In effect, you are developing a model of knowledge (in my case, a model of music knowledge) that is conceptualized to serve a particular community (in my case, online self-taught musicians). I also articulated this in about 7500 words, this post is a coles notes-to-myself!