back to overview<\/a><\/p>\n[\/et_pb_text][et_pb_image src=”https:\/\/www.flumiq.ch\/wp-content\/uploads\/2022\/12\/flumiq-sketch-control-panel.png” alt=”flumiq sketch control panel” title_text=”flumiq sketch control panel” _builder_version=”4.20.0″ _module_preset=”default” width=”80%” width_tablet=”80%” width_phone=”100%” width_last_edited=”on|phone” global_colors_info=”{}”][\/et_pb_image][et_pb_text content_tablet=”<\/p>\n
Operation of a company means execution of business\u202fprocesses.\u202fdocumentation\u202fis there to preserve and to develop the\u202fknowledge\u202fabout those processes and therefore the core of the business. Why does it happen, that this documentation is outdated or incomplete? Is the core of the business not worth to be secured? <\/p>\n
Looking at\u202fwarehousing\u202foperations it depends, whom you ask about the frequency, if outdated documentation is evaluated to happen sometimes, regularly, or even in most of the cases. But why? Almost nobody argues against the value of documentation during the implementation of a new business in order to keep everybody aligned, trained and so on, but later? Is it not important anymore? It assures that the knowledge is kept. It required by governance models, certifications or just as a good practice. It is the basis for process improvements and this gets hopefully not just recognized in case of a major change or system migration or similar. So, the question remains, how can outdated documentation happen? <\/p>\n
One of the reasons for sure is that writing of documentation is cumbersome and boring. Short-term even the value is limited and if there are time constraints \u2026 <\/p>\n
So, if it gets missed to create the documentation right from the beginning, why does it not get resolved later on? Typically, if someone feels the need for the documentation, he or she looks at it, finds it outdated and creates a workaround, meaning a separate sketch, just for the current need and this is not seen as part of the documentation and gets forgotten later on. Next time same procedure again, wasted time and energy. <\/p>\n
How can we do better? We know about the power of routine. How can we put the process documentation as part of the\u202fdaily\u202fbusiness? How can we benefit from the documentation on a daily basis? A\u202fcontrol\u202fpanel based on the process documentation as an idea? A flow diagram with real-time\u202fKPI\u202f\u2019s for the process steps. Impact analysis of any finding would be easier as the steps before and afterwards are clearly visible. This would\u202f\u202fprovide\u202fbenefit\u202fon a daily basis and as byproduct the documentation is checked implicitly and with that accuracy is promoted. <\/p>\n
As illustration the sketch above, which indicates the throughput of a certain step as speed and backlog of tasks as range like in a cockpit of an electric car (plus some triangles and color coding for acceleration etc.). KPI\u2019s and visualization can vary based on the individual case. <\/p>\n
” content_phone=”<\/p>\n
Operation of a company means execution of business\u202fprocesses.\u202fdocumentation\u202fis there to preserve and to develop the\u202fknowledge\u202fabout those processes and therefore the core of the business. Why does it happen, that this documentation is outdated or incomplete? Is the core of the business not worth to be secured? <\/p>\n
Looking at\u202fwarehousing\u202foperations it depends, whom you ask about the frequency, if outdated documentation is evaluated to happen sometimes, regularly, or even in most of the cases. But why? Almost nobody argues against the value of documentation during the implementation of a new business in order to keep everybody aligned, trained and so on, but later? Is it not important anymore? It assures that the knowledge is kept. It required by governance models, certifications or just as a good practice. It is the basis for process improvements and this gets hopefully not just recognized in case of a major change or system migration or similar. So, the question remains, how can outdated documentation happen? <\/p>\n
One of the reasons for sure is that writing of documentation is cumbersome and boring. Short-term even the value is limited and if there are time constraints \u2026 <\/p>\n
So, if it gets missed to create the documentation right from the beginning, why does it not get resolved later on? Typically, if someone feels the need for the documentation, he or she looks at it, finds it outdated and creates a workaround, meaning a separate sketch, just for the current need and this is not seen as part of the documentation and gets forgotten later on. Next time same procedure again, wasted time and energy. <\/p>\n
How can we do better? We know about the power of routine. How can we put the process documentation as part of the\u202fdaily\u202fbusiness? How can we benefit from the documentation on a daily basis? A\u202fcontrol\u202fpanel based on the process documentation as an idea? A flow diagram with real-time\u202fKPI\u202f\u2019s for the process steps. Impact analysis of any finding would be easier as the steps before and afterwards are clearly visible. This would\u202f\u202fprovide\u202fbenefit\u202fon a daily basis and as byproduct the documentation is checked implicitly and with that accuracy is promoted. <\/p>\n
As illustration the sketch above, which indicates the throughput of a certain step as speed and backlog of tasks as range like in a cockpit of an electric car (plus some triangles and color coding for acceleration etc.). KPI\u2019s and visualization can vary based on the individual case. <\/p>\n
” content_last_edited=”on|phone” _builder_version=”4.20.0″ _module_preset=”default” text_font=”|300|||||||” text_text_color=”#000000″ text_font_size=”18px” text_line_height=”25px” header_font=”||||||||” header_text_color=”#6667ac” header_font_size=”35px” header_line_height=”32px” header_2_font=”||||||||” header_2_text_color=”#6667ac” width=”80%” width_tablet=”80%” width_phone=”100%” width_last_edited=”on|phone” custom_margin_tablet=”” custom_margin_phone=”” custom_margin_last_edited=”on|desktop” custom_padding_tablet=”” custom_padding_phone=”|0px||0px|false|false” custom_padding_last_edited=”on|phone” module_alignment_tablet=”” module_alignment_phone=”” module_alignment_last_edited=”on|phone” global_colors_info=”{}”]<\/p>\n
Operation of a company means execution of business\u202fprocesses.\u202fdocumentation\u202fis there to preserve and to develop the\u202fknowledge\u202fabout those processes and therefore the core of the business. Why does it happen, that this documentation is outdated or incomplete? Is the core of the business not worth to be secured? <\/p>\n
Looking at\u202fwarehousing\u202foperations it depends, whom you ask about the frequency, if outdated documentation is evaluated to happen sometimes, regularly, or even in most of the cases. But why? Almost nobody argues against the value of documentation during the implementation of a new business in order to keep everybody aligned, trained and so on, but later? Is it not important anymore? It assures that the knowledge is kept. It required by governance models, certifications or just as a good practice. It is the basis for process improvements and this gets hopefully not just recognized in case of a major change or system migration or similar. So, the question remains, how can outdated documentation happen? <\/p>\n
One of the reasons for sure is that writing of documentation is cumbersome and boring. Short-term even the value is limited and if there are time constraints \u2026 <\/p>\n
So, if it gets missed to create the documentation right from the beginning, why does it not get resolved later on? Typically, if someone feels the need for the documentation, he or she looks at it, finds it outdated and creates a workaround, meaning a separate sketch, just for the current need and this is not seen as part of the documentation and gets forgotten later on. Next time same procedure again, wasted time and energy. <\/p>\n
How can we do better? We know about the power of routine. How can we put the process documentation as part of the\u202fdaily\u202fbusiness? How can we benefit from the documentation on a daily basis? A\u202fcontrol\u202fpanel based on the process documentation as an idea? A flow diagram with real-time\u202fKPI\u202f\u2019s for the process steps. Impact analysis of any finding would be easier as the steps before and afterwards are clearly visible. This would\u202f\u202fprovide\u202fbenefit\u202fon a daily basis and as byproduct the documentation is checked implicitly and with that accuracy is promoted. <\/p>\n
As illustration the sketch above, which indicates the throughput of a certain step as speed and backlog of tasks as range like in a cockpit of an electric car (plus some triangles and color coding for acceleration etc.). KPI\u2019s and visualization can vary based on the individual case. <\/p>\n
[\/et_pb_text][et_pb_post_nav prev_text=”previous post” next_text=”next post” _builder_version=”4.20.0″ _module_preset=”default” title_font=”|300|||||||” title_font_size=”18px” title_line_height=”2px” hover_enabled=”0″ global_colors_info=”{}” width=”90%” sticky_enabled=”0″][\/et_pb_post_nav][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"
Operation of a company means execution of business\u202fprocesses.\u202fdocumentation\u202fis there to preserve and to develop the\u202fknowledge\u202fabout those processes and therefore the core of the business. Why does it happen, that this documentation is outdated or incomplete? Is the…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[23],"tags":[24,26,25,27],"class_list":["post-1267","post","type-post","status-publish","format-standard","hentry","category-general","tag-documentation","tag-kennzahlen-en","tag-logistik-en","tag-prozess-en"],"yoast_head":"\n
Outdated documentation? - flumiq<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Outdated documentation? - flumiq\" \/>\n<meta property=\"og:description\" content=\"Operation of a company means execution of business\u202fprocesses.\u202fdocumentation\u202fis there to preserve and to develop the\u202fknowledge\u202fabout those processes and therefore the core of the business. Why does it happen, that this documentation is outdated or incomplete? Is the...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/\" \/>\n<meta property=\"og:site_name\" content=\"flumiq\" \/>\n<meta property=\"article:published_time\" content=\"2022-12-02T16:31:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-04-01T15:28:38+00:00\" \/>\n<meta name=\"author\" content=\"Christian Ordelt\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Christian Ordelt\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/\",\"url\":\"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/\",\"name\":\"Outdated documentation? - flumiq\",\"isPartOf\":{\"@id\":\"https:\/\/www.flumiq.ch\/#website\"},\"datePublished\":\"2022-12-02T16:31:11+00:00\",\"dateModified\":\"2023-04-01T15:28:38+00:00\",\"author\":{\"@id\":\"https:\/\/www.flumiq.ch\/#\/schema\/person\/81ef7659d58ac8e8124f0df64d77a5a1\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.flumiq.ch\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Outdated documentation?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.flumiq.ch\/#website\",\"url\":\"https:\/\/www.flumiq.ch\/\",\"name\":\"flumiq\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.flumiq.ch\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.flumiq.ch\/#\/schema\/person\/81ef7659d58ac8e8124f0df64d77a5a1\",\"name\":\"Christian Ordelt\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.flumiq.ch\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/7bc60a12c3df5a3a81fcd223a064de0519d13a983b7b9914e9483e3fab1cf169?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/7bc60a12c3df5a3a81fcd223a064de0519d13a983b7b9914e9483e3fab1cf169?s=96&d=mm&r=g\",\"caption\":\"Christian Ordelt\"},\"url\":\"https:\/\/www.flumiq.ch\/en\/author\/christian-ordelt\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Outdated documentation? - flumiq","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/","og_locale":"en_US","og_type":"article","og_title":"Outdated documentation? - flumiq","og_description":"Operation of a company means execution of business\u202fprocesses.\u202fdocumentation\u202fis there to preserve and to develop the\u202fknowledge\u202fabout those processes and therefore the core of the business. Why does it happen, that this documentation is outdated or incomplete? Is the...","og_url":"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/","og_site_name":"flumiq","article_published_time":"2022-12-02T16:31:11+00:00","article_modified_time":"2023-04-01T15:28:38+00:00","author":"Christian Ordelt","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Christian Ordelt","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/","url":"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/","name":"Outdated documentation? - flumiq","isPartOf":{"@id":"https:\/\/www.flumiq.ch\/#website"},"datePublished":"2022-12-02T16:31:11+00:00","dateModified":"2023-04-01T15:28:38+00:00","author":{"@id":"https:\/\/www.flumiq.ch\/#\/schema\/person\/81ef7659d58ac8e8124f0df64d77a5a1"},"breadcrumb":{"@id":"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.flumiq.ch\/en\/2022\/12\/02\/veraltete-dokumentation\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.flumiq.ch\/en\/"},{"@type":"ListItem","position":2,"name":"Outdated documentation?"}]},{"@type":"WebSite","@id":"https:\/\/www.flumiq.ch\/#website","url":"https:\/\/www.flumiq.ch\/","name":"flumiq","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.flumiq.ch\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.flumiq.ch\/#\/schema\/person\/81ef7659d58ac8e8124f0df64d77a5a1","name":"Christian Ordelt","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.flumiq.ch\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/7bc60a12c3df5a3a81fcd223a064de0519d13a983b7b9914e9483e3fab1cf169?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/7bc60a12c3df5a3a81fcd223a064de0519d13a983b7b9914e9483e3fab1cf169?s=96&d=mm&r=g","caption":"Christian Ordelt"},"url":"https:\/\/www.flumiq.ch\/en\/author\/christian-ordelt\/"}]}},"_links":{"self":[{"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/posts\/1267","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/comments?post=1267"}],"version-history":[{"count":6,"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/posts\/1267\/revisions"}],"predecessor-version":[{"id":1533,"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/posts\/1267\/revisions\/1533"}],"wp:attachment":[{"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/media?parent=1267"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/categories?post=1267"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.flumiq.ch\/en\/wp-json\/wp\/v2\/tags?post=1267"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}