Student Initiantions Gallery

How is the knowledge of the company

What value does a company if the knowledge infected the core competence only in the minds of employees?

What does taking responsibility? We read in the media: Succession planning is a central management task. What happens to a company if the heads are gone? Can only lead but who knows what it takes? Is not it so that when the leadership leads and competent to understand the succession planning will solve a lot easier. Why succession planning is even an issue? What would because when the head is suddenly (accident), then you can not even begin until the succession planning. I think is important: the knowledge can not remain in the mind, it is part of the company. So how knowledge comes into the company.

give the information more, a key requirement in our society to move forward. In research and development, it helps us the goals erreichen.Nicht over again from scratch start is here. Documentation before implementation. But honestly, who uses because that in everyday life? I have! Does it help me to structure and implement a targeted vision, and that already in the planning! Writing down helps detect errors before implementation. Knowledge is now available. Competent Untersützung integrated quickly. Documents are available. The acquired is not in the head but in the company available. More work? No! Knowledge must be made available without if and but just as a team. After documentation is a lot more work, and is of poor quality. Who does not know the situation, you are asked for the umpteenth time in the same. Well, then you should think again, who does what is wrong here? The questioner or the answerer? As I hear from colleagues that they can no longer perform their work. You will be covered nonstop with requests and orders from your co-workers. Helpfulness overall. One would indeed like to get their own expertise confirmed. Say no, rejecting the other will not do that. The best way to do everything for yourself. It can anyway, yes, for whatever reason ..... Document and organize? No, just not there for missing time. Because I'll do it but even better, yourself. Yes and they are then, the irreplaceable. Do not realize that they are the problem, work more and more, are not as competent do it but to prove to everyone what always take everything very personally, always justified, and it never changes ....... . Yes and then? Some conclude your career with a heart failure, the other .......... with a burnout that necessary? No! One of the most important central executive functions is precisely the acquired knowledge is accessible. And that's only through regulated processes. As knowledge without much effort the heads of the company goes.

know how assurance through documented structured work. Knowledge must be accessible, and that this is so, that is top priority! Not knowing in my head makes me unique, but my skills knowledge quickly and efficiently in their daily life and easy to use.

I hope that I can with the lines of the one or the other encourage structured and documented to work, his knowledge make it accessible to others. Because the ability of knowledge to others to make available to their true competence. Knowledge in the head is practical, is good but the team nothing, and is not visible!

The knowledge in the company remains, and that knowledge of the staff is really accessible, this is definitely one of the central and most important management tasks! I like the same user? Later in this Blogg.

As head of a scientific technical development department, I see this as central task that acquired knowledge is available documents. knowledge must be in accordance with the expertise be documented in different ways. It's great, the leaves with the V-model from the GAMP5 implement instructions. http://www.ispe.org/index.php/ci_id/11614/la_id/1.htm
The V-Model can be integrate into any workflow. It takes time and practice with a vinous to the well to be able to apply across processes. The picture above shows the process how a product or idea can be realized. It starts from the initial idea and ends with the release. It is documented on several levels: from the specification, where typically a deep expertise exists for a high user expertise. The specification is neutral in the middle, and the design specification is the language of the developer. The entire implementation of the specification is maintained always bilateral, and when used correctly are two very efficiency and benefits. With both, I believe that knowledge should be documented are always passed (principle) in a small team, the team leader. The direct management understands the work of professionals, there is no "political signatures. If there are ambiguities, must be documented by , otherwise the project is not good. Take responsibility, someone who understands! Those who understand can decide competently. Only after completion and shared specification will start the implementation. By the way, am also of the opinion, has visions only he who is competent.

agrees that the quality of the specification , which is a top priority, but the implementation remains primarily in the art, may here be counted on the expertise of the employee. If the processes are well organized, can cooperated completely decide freely and competently implement his project.

seems important to me to mention that this process can be applied not only in the realization of products that work quite well in all areas of work. There is also a great "management tool"! Clear guidelines
= specification. Confidence in the employee = realization and on the expertise and competence of the employee count. = Control and qualification verification, shown here if the chats and was running correctly.

case of fixed work processes such as development, Support, medicine, etc. "Yes, it goes almost everywhere ..." Optimally, one uses so-called templates. The templates are pre-defined where such information is to be written down. This can all be clear what is expected, as I would like to stand outside there, and how knowledge down attachments should be.

In the V-model, for example (pictured above), the following means:
specifications: It is the "language" (language = competence) of the principal. Here is the order (the specification) by the formulation as general as possible and as restrictive as necessary be formulated. Here, by the contractor (developer) to develop the optimal solution, without restrictions due to specific requirements in its solution competence sein.Jedoch to the completeness of all claims of the specification will be sought by the client!

specifications: It represents the approach of the contractor, in the "language" of the client.

is the specification describes how the contractor (developer) solution to the requirements of the specifications. Does the job (product) is defined as being definitive and clear. For the qualification of the product apply only the information which are specified in this specification.

Design Specification: It is in the language of the contractor's written, and is used only within the department. It is the document for the implementation, it contains detailed technical information on the product declared by the developer. Are written by subject. The document is intended only for the department. It serves as the know-how protection. It should aim to write down the content so much that there is sufficient information within the trade scene. Importantly, this is done, and understood by the leading right place!

realization: here can be expected by the department, that what was developed in the specification, trade will be implemented competently. must be defined in the implementation (process) the realization documentation in each case (always) have to be miterstellt.

done after the realization of the verification, and that is so simple with the same documents that you created in the realization added. verification is also equal qualification, here it is shown that the product is a requirement of the idea. Optimally, this is not done by the same experts who have made the realization. If the qualification passed are good at using the V-model, all necessary documents available.

Rating: The release completes a job with the release of the job is finished.. To share that takes place whenever all process-related agreements met were. This is a very important point, otherwise use is the whole V-model anything. In addition to the completed project is also documented transfer pass geregelt.Wissen documented in the correct "language." The product is the physical result, the documents of proof spirit, it bears the manuscript of the "spiritual" fathers, the spiritual evidence.



suggestions like the Blogg. Questions or tips via email. Otherwise
have fun converting the next project .....
Regards Fredi Hagenbucher

My Blogs
This & That: http://dd-fredi.blogspot.com/

Development News: http://hagitechnology.blogspot.com/

Triathlon: http://trihagi.blogspot.com/

DEA in the future. Cloud Computing: http://fredihagenbucher.blogspot.com /
sites: https: / / sites.google.com / site / fredi Hagenbucher /