Read e-book Sharing expertise : beyond knowledge management

Free download. Book file PDF easily for everyone and every device. You can download and read online Sharing expertise : beyond knowledge management file PDF Book only if you are registered here. And also you can download or read online all Book PDF file that related with Sharing expertise : beyond knowledge management book. Happy reading Sharing expertise : beyond knowledge management Bookeveryone. Download file Free Book PDF Sharing expertise : beyond knowledge management at Complete PDF Library. This Book have some digital formats such us :paperbook, ebook, kindle, epub, fb2 and another formats. Here is The CompletePDF Book Library. It's free to register here to get Book file PDF Sharing expertise : beyond knowledge management Pocket Guide.


  1. Knowledge Sharing in Agile Software Teams
  2. Shop by category
  3. Help Employees Create Knowledge — Not Just Share It
  4. Knowledge Sharing

The interviews were performed with engineers from transform individual knowledge into organizational knowledge. At company B, 8 respondents Commonly, such a transformation is explained to depend on a have been interviewed. And, all interviews were semi- In industry, several different terms are used to describe the structured, i. Though, depending on the prevailing perspective, give limited explanation of the system part.

The system view of PSS what kind of knowledge it involves differs. Particularly for PSS seems to address other aspects than an integrated product view situations it is concluded that there are differences between an does, but this is not further explained. For manufacturing companies, different perspectives, PSS could be assumed to be seen from moving towards PSS, there is a challenge in integrating the service different points of view, but all definitions presented in Tukker et al aspects in the development process and so far many companies [19] seem to describe a strategic business point of view where the that offer services do not fit these with the existing Product-Service emphasis is on what is sold to customers, cf.

One example of a definition is that PSS is A comparison of competing paradigms of product development in the result of an innovation strategy, shifting business focus from academic communities have recognized marketing, organization, designing and selling physical products only, to selling a system of engineering design and operations management as main conflicting products and services which are jointly capable of fulfilling specific perspectives [11].

Particularly the view on products differs between client demands [20]. Another example is that PSS are a specific the perspectives p. Engineering design views the product, first as 1. Hence, the knowledge From this guidance, it can, firstly, be interpreted that a development management insists being performed differently. Though, in product development design problem they need to understand some basics — such as literature the view on knowledge is typically described from an what they are designing, what it should do and who should use it engineering design perspective.

Thereby, formalizing and storing of and in what circumstances. The technical knowledge base is not encompassing enough. Second, an development is closely linked to the project and group activities. In interpretation of the guidelines can also be that companies are this context, verbal communication is a common way to share challenged in a much more extensive way than just figuring out how experiences.

Respondents stressed that team members or to mix or combine product and service solutions. Email and chat A base for innovations is that some aspects of new knowledge are conversations are mentioned as a way to contact people within the added to the existing knowledge base [25], such knowledge can be organization, commonly this is done to set up a face to face about markets, processes, ideas, products, structures etcetera. These support systems make it possible to form dispersed The companies in the study are moving towards PSS, but do not teams or a dispersed project organization.

Offered services are Company servers are used to disseminate formal and typically offered as add-on to products. One of the companies has organizational documents, for instance written instructions, lessons tried PSS on contract level but not on a development level. The staff can For the companies included in this study, knowledge based tools search the servers to find relevant information, though it is play an important role to validate the included technologies, the expressed that finding information is perceived as time consuming.

These tools The engineers prefer to ask a colleague or find a former team make storing, retrieving and dissemination of technical information member to ask, this is an easier way to retrieve information. Also, the tools provide traceability of performed 5. In occurrence. One of the companies is performing in house development of some For example, those who worked as project leaders perceived that knowledge based tools, which is referred to as method they did share knowledge within the organization; such activities development.

But, also, they have to understand how to implement, how shared on daily basis was explained as reporting progress in to educate users and scalability aspects of the application. The method developer outside their projects. None of the respondents agreed that investigates the situation, analyzing the purpose of the task, the knowledge sharing occurred constantly see Figure 1.

This work is guided by a knowledge based engineering lifecycle cf. The method developer has an extended responsibility to package and activate the application in collaboration with the IT-department. The method developers emphasize that the success of the application depends on how well it fits into the established development process, its usability and if it is accepted by its users.

Knowledge Sharing in Agile Software Teams

Besides collaboration with IT-department, the method developers work closely with people that are considered as domain experts, such as process owners. These people possess deep and focused knowledge about certain activities and provide valuable input to the method development. Sometimes the method development follows a technology push approach, where the method developer locates an activity that is Figure 1: Knowledge sharing within the organization.

In such a case, the demands on the developer are other responses, see Figure 2. Usually, the method developer identifies the governing processes and the documented instructions for the activity. Since all activities are not documented and described at the company, the method developers have to solve problems as they emerge.

There is a team of method developers that can seek support among each other.

For example, reoccurring meetings, as well as documented guidelines and instructions for method development found in collaborative repositories, such as collaborative workspaces and networked disk drives, are seen as knowledge sharing activities. Figure 2: Knowledge sharing with colleagues. Figure 4: Where do you search for information or knowledge. There was a mix of expertise in the team, but that mix was asked a colleague, which is a person from the same department overall from within the engineering field.

To be able to project.

Shop by category

For industrial practices, the discerned indications can provide a basis for reflection. We have in Figure 3: Knowledge sharing within the project. In those previous studies the 5. Within the project archives, product assurance plan. And, it is the human and archive, and the product assurance plan defines the delivery criteria contextual interpretation of that displayed information that for opening gates in projects according to the product development transforms it into knowledge.

Still, this is found as a theoretical process. Thus, making the perception of shared knowledge to align with explicit knowledge and information, and making the distinction that what is not so frequently shared is experiences. Modica and Rustichini [28] have trust in finding the information needed, i.

KNOWLEDGE MANAGEMENT AND INNOVATION - Dr Kondal Reddy Kandadi - TEDxUniversityofBolton

If The analogy of PSS is that manufacturing companies generally can so, it might be possible to suspect that the information input could perceive a shift as ill-defined and wicked [22] [23], hence a stepwise be sparse also. Is so, the team approach. Yet, how can such activities be they do not in their as-is state support PSS as a whole. The supported and performed in practice? And, the support for capturing ambiguous and uncertain nature of development activities that often these reflections in action, how would that look like?

Reflections in goes hand in hand with PSS and service provision means that the teams usually do not come in written text, rather in dialogues. If this is the case, striving for providing, for example should be most frequent within the project and that knowledge leasing, would build up service knowledge, subsequently how to sharing should be less frequent on an organizational level. The develop suitable physical products for a leasing contract is one step empirical data indicates that the assumption has some relevancy, towards PSS. And, from these experiences how to change the but provides no insights to why a situation like this could occur.

One product development process can be understood. PSS, it seems, management, for example to communicate what is happening in the has become a wider concept than intended, branding all the company as a whole or to transfer information about the business variants of traditional sales of things development as usual to the environment.

If so, there is a need of an organizational strategy to view that all products remain in the ownership of the manufacturer support other forms of meeting that support knowledge sharing. It and that company sell the service of operations in the customer seems useful to; for example, figure out how to provide structured processes [9].

Help Employees Create Knowledge — Not Just Share It

Today, engineers and product developers have to and focused feedback from a larger audience and how to evaluate possess a wide range of knowledge, though still that vast the impact of an informative meeting in order to improve the larger knowledge base is about the physical product. PSS adds more meeting format for knowledge sharing. Though, it is important to relational complexity into that situation, since for development note that all larger meetings should not turn into knowledge sharing issues the engineers and developers have to expand their activities, information transfer is also needed.

Basically, there is a knowledge domains into the area of customers. These kinds of activities are hard to support their most valuable asset.

Knowledge Sharing

A key in this perspective is if the asset is in project work. Further, such knowledge sharing occurs more considered to be protected not shared or if it is considered to be verbally, in sketches, simple pictures and even by using gestures.

  1. Handbook of Poultry Feed from Waste: Processing and Use.
  2. The Gatekeepers Challenge (Gatekeepers Saga, Book 2)!
  3. Explicit Knowledge and Knowledge Sharing.
  4. Queer Globalizations: Citizenship and the Afterlife of Colonialism.
  5. Sharing Expertise: Beyond Knowledge Management - Google Books.
  6. Log in to Wiley Online Library.

A So, sharing expertise is easier said, than done. Besides interaction with company automation of knowledge work the interest is turning towards representatives in the research projects, Interviews that composed perceived and experience based knowledge. Still, in companies, of predefined questions have been performed. This data provide a there is an awareness of the challenges to transform the stored background for the purpose of this paper to discuss the established information into actions and the staff into knowledgeable workers.

The engineers experiences are seldom shared in contemporary management of knowledge for the purpose of PSS formal reports but are a necessity in the development of services, introduction in the company. For this reason, if you are really committed to scalable learning, you should find ways to build deep, trust-based relationships within a broader ecosystem of organizations so that you can mobilize the relevant expertise and talent to address unexpected performance challenges whenever they arise. If you just focus on the people within your organization, you will likely confront serious limitations to the ability to scale learning.

Many organizational leaders have a mental model that learning requires significant upfront investment to develop the course materials and take people out of their work so that they can go to the training program and learn. The hope is that there might be performance improvement down the road, but that comes after the initial investment and assumes you can retain the people in your organization. Scalable learning shifts the focus to learning in the work environment as new performance challenges arise.

In this context, addressing the performance challenge effectively can deliver performance improvement on the spot through new approaches and the learning is actually a by-product of having effectively addressed the performance challenge. So, the model flips — performance improvement leads to learning, rather than vice versa. When we see the world around us as stable, learning can be viewed as the accumulation of knowledge over time. You just keep piling new knowledge on top of the knowledge you already have.