Sunday recap is a way for me to record items I came across the Web during the week. It acts as a permanent home for things I want to explore more or reflect upon. It was inspired by Harold Jarche’s PKM Mastery class I took in 2014.
Content Management/Knowledge Management
The best example of a CMS is the Web. There is relevant and irrelevant content. The relevant content is often found through referrals. This may be in terms of ratings, curation by a trusted party, or from a known source. Referrals can be pushed, through something like a subscription service, or pulled from knowledge networks when there is an immediate need for information. People with more diverse and deep knowledge networks get better information.
After reading the post, I clicked on Harold’s post concerning a simpler approach to knowledge management, “ESN as knowledge bridges“.
The use of an ESN highlights the need for a simple but effective knowledge management (KM) strategy that can be supported by everyone. The best way to build useful organizational knowledge is by connecting it to individual knowledge-sharing.
The challenge is to enable individual knowledge-sharing with minimal external control, to seek, make-sense of, and share knowledge. Each person must find a process that works on an individual basis and this in turn can support the organization in leveraging collective knowledge. The reverse, starting from the organizational perspective, is much more difficult.
Organizational Design – Managing Complexity
Advanced Work by Elsko Kilpi.
What if the organization really should be an ongoing process of emergent self-organizing? Instead of thinking about the organization, let’s think about continuous organizing. If we take this view we don’t think about walls but we think about what we do and how groups are formed around what is actually going on, or what should be going on. The new management task is to make possible very easy and very fast emergent formation of groups and to make it as easy as possible for the best contributions from the whole network to find the applicable tasks.
The Platform Stack is a tool for us to think through platforms and plan them. Irrespective of what you’re building, the stack helps to figure which layers you differentiate yourself in and how. It helps understand the key strengths of businesses that are already out there in the market. Without getting lost in the quagmire of features and functionalities, the stack helps us understand the key drivers of value and helps us benchmark ourselves on those parameters against competition and substitutes.
Minimum Viable Products
Putting the “VP” into MVP – great post on understanding MVPs http://t.co/i0HaT8Szwj
— Ben Yoskovitz (@byosko) January 14, 2015
The MVP, contrary to popular belief, is NOT the minimum set of features required to create a working product. Nor is it the product itself. It is, instead, a process. The MVP is the smallest experiment that either proves or disproves assumptions about a business idea. Although rapid development is of the essence, that is only true to the extent that the development helps us to quickly obtain our learning and research objectives.