{"id":762,"date":"2013-11-18T19:21:46","date_gmt":"2013-11-18T17:21:46","guid":{"rendered":"http:\/\/thomasdt.com\/?p=762"},"modified":"2013-11-18T19:21:46","modified_gmt":"2013-11-18T17:21:46","slug":"brainstorming-on-communication-in-rd-department","status":"publish","type":"post","link":"https:\/\/rationalk.ch\/blog\/brainstorming-on-communication-in-rd-department\/","title":{"rendered":"Brainstorming on communication in R&#038;D department"},"content":{"rendered":"<p>The following notes came from a meeting that I had with colleagues on how to communicate efficiently within the department (R&amp;D department)<\/p>\n<h1>Why do we have to communicate, why sharing knowledge ?<\/h1>\n<h2>Business<\/h2>\n<ul>\n<li>Brainstorming and idea creation are facilitated<\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Duplicate work can be avoided<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Decision can be taken faster and in a more efficient way (better alignment)<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Faster and easier involvment of new colleagues<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Living Experts knowledge is captured<\/span><\/li>\n<\/ul>\n<h2>Individual<\/h2>\n<ul>\n<li>People have access to the same level of information<\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">The team feels as a team (people cohesion)<\/span><\/li>\n<\/ul>\n<h1>Target Audiences<\/h1>\n<p>A R&amp;D department (technician, engineer, researcher and project manager). The people are not necessary \u00a0in the same office.<\/p>\n<h1>What &amp; How<\/h1>\n<ul>\n<li>Technical Communication \/ non-Technical Communication<\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Spoken Communication \/ Unspoken Communication<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Live Communication \/ On-demand Communication<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Short, middle and long terms communication<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Face-to-face meeting: Technical Day, Local Pulse<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Web conference : Technical Meeting<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Newsletter : Monthly Management Report<\/span><\/li>\n<li><span style=\"line-height: 1.714285714; font-size: 1rem;\">Reporting : Portofolio Management tool, project presentations, project planning, technical notes<\/span><\/li>\n<\/ul>\n<h1>Communication strategy<\/h1>\n<h2>Process committee meeting<\/h2>\n<p>Who : A small group of three persons<br \/>\nWhat : Innovation process update, administrative process update<br \/>\nWhen : 3 times a year<br \/>\nTime frame : long terms<br \/>\nBenefit : workflow efficiency, faster work<\/p>\n<h2>Department Day<\/h2>\n<p>Who : the whole team<br \/>\nWhat : 1 th\u00e8me (example : communication faire savoir), 1 day<br \/>\nWhen : Yearly<br \/>\nTime frame : long terms<br \/>\nBenefit : En plus de la th\u00e9matique, le team building<\/p>\n<h2>Department Meeting<\/h2>\n<p>Who : The whole Team<br \/>\nWhat : Team communication on non-technical subjects, work climate analysis, general information<br \/>\nWhen : monthly<br \/>\nTime frame : short terms<br \/>\nBenefit : Communicate every day life&rsquo;s problems<\/p>\n<h2>Technical Day<\/h2>\n<p>Who : The whole Team<br \/>\nWhat : All projects are discussed during 1 day in a neutral location. Difficulty due to high Volume of information. Interactive communication<br \/>\nWhen : Yearly<br \/>\nTime frame : Long terms<br \/>\nBenefit : Same level of knowledge on the current project progress<\/p>\n<h2>Technical Meeting<\/h2>\n<p>Who : The whole Team<br \/>\nWhat : 1 project is presented during 45 minutes and the audience can interact. To be experiemented.<br \/>\nWhen : Monthly<br \/>\nTime frame : Middle terms<br \/>\nBenefit : Interactive communication, OPTIONAL attendance, could lead to a technical handbook<\/p>\n<h2>Local Pulse Meeting<\/h2>\n<p>Who : The whole Team<br \/>\nWhat : 1 hours, 3 minutes per person, weekly log of the project (incl. Risk, decision, problems)<br \/>\nWhen : Weekly<br \/>\nTime frame : short terms<br \/>\nBenefit : Risk sharing, problem solving, resource allocation<\/p>\n<h2>Global Pulse Meeting<\/h2>\n<p>Who : 2 to 3 persons from each geographic site, we call them connectors<br \/>\nWhat : 1 hours, similar to pulse but global, format to be defined\/experimented<br \/>\nWhen : monthly or weekly<br \/>\nTime frame : middle terms or short terms<br \/>\nBenefit : interactive global communication<\/p>\n<h2>Monthly Management Report<\/h2>\n<p>Who : The whole Team<br \/>\nWhat : Report current month achievement and updates<br \/>\nWhen : monthly<br \/>\nTime frame : middle terms<br \/>\nBenefit : information on-request<\/p>\n<h1>More relative to KM than to Communication<\/h1>\n<p>TPD Knowledge Transfert Session:<\/p>\n<ul>\n<li>Experts are training new employees<\/li>\n<li>People receiving the information should report the learning (Technical Note)<\/li>\n<li>The expert review and sign the technical note<\/li>\n<\/ul>\n<h1>Actions and next steps<\/h1>\n<p>Risk : Overcommunication -> No time for \u00ab\u00a0real\u00a0\u00bb work<\/p>\n<ul>\n<li>Test the different new communication vector and give feedback<\/li>\n<li>Work on the most appropriate way for non disruptive communication<\/li>\n<li>Example : notify people when a new document is created in the knowledge base<\/li>\n<li>Understand on how people look for the information, to do so identify some \u00ab\u00a0profils\u00a0\u00bb to perform the study : Technician, researchers, managers, \u2026<\/li>\n<li>Work on how to train people to locate the information<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The following notes came from a meeting that I had with colleagues on how to communicate efficiently within the department (R&amp;D department) Why do we have to communicate, why sharing knowledge ? Business Brainstorming and idea creation are facilitated Duplicate work can be avoided Decision can be taken faster and in a more efficient way [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"enabled":false},"version":2}},"categories":[2],"tags":[],"class_list":["post-762","post","type-post","status-publish","format-standard","hentry","category-dev"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/posts\/762","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/comments?post=762"}],"version-history":[{"count":0,"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/posts\/762\/revisions"}],"wp:attachment":[{"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/media?parent=762"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/categories?post=762"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rationalk.ch\/blog\/wp-json\/wp\/v2\/tags?post=762"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}