{"id":2034,"date":"2010-06-08T20:03:46","date_gmt":"2010-06-08T20:03:46","guid":{"rendered":"http:\/\/biz4ge.net\/?p=2034"},"modified":"2021-03-15T14:57:25","modified_gmt":"2021-03-15T14:57:25","slug":"data-the-poor-relation-with-a-big-say","status":"publish","type":"post","link":"https:\/\/kz-a.net\/biz4ge\/index.php\/business-transformation\/information-and-data\/data-the-poor-relation-with-a-big-say\/","title":{"rendered":"Data &#8211; The Poor Relation with a Big Say"},"content":{"rendered":"<p>To some use of the word \u2018data\u2019 signals the beginning of one of the most boring, technically esoteric and generally useless topics of discussion they can imagine.\u00a0 Data model, data dictionary, data schema, data cleansing, data coding &amp; classification\u2026\u2026or just plain old data.<\/p>\n<p>HELP!\u00a0 How much boredom and technophobia can one person be expected to cope with!\u00a0 Can\u2019t those sad techie\u2019s keep all that gobbledy-gook stuff to themselves and just talk to the rest of us about normal business things?<\/p>\n<p>Oh dear, a response common to many technophobes we know.\u00a0 At Biz4ge we even have some sympathy for this perspective.\u00a0 However, we also know from hard experience that the technophobes are dead wrong to place this conversation on the lower rung of technical hell.<\/p>\n<p><strong>Unfortunately, although we\u2019d never claim the topic was scintillating to most listeners, we know how fundamentally important good data is to modern organisations.\u00a0 It is not too much of an exaggeration to say that without it they are lost with little hope of rescue!<\/strong><\/p>\n<p><strong><!--more--><\/strong>You see, business processes, functions, workflows, metrics, org charts, etc, etc change quite regularly\u2026\u2026sometimes at the whim of a passing management fad.\u00a0 Where-as base data on the other hand generally changes relatively little on the whole\u2026\u2026while underpinning all the rest of the faster changing artefacts that rest on top of it.<\/p>\n<p>To understand this, while trying to avoid the more technical aspects, it is useful to think of (business) data as being split into three camps: meta data, static data and dynamic data.<span style=\"text-decoration: underline;\"><strong><\/strong><\/span><\/p>\n<p><span style=\"text-decoration: underline;\"><strong>Meta data<\/strong><\/span> is simply data about data.\u00a0 This camp covers such things as should data be ten digits long or fifteen digits long.\u00a0 Should it be numeric or alpha-numeric.\u00a0 Should it use an existing classification system (e.g. NATO schema) to group and relate items or will you choose to use one you have invented for yourself.<\/p>\n<p>These basic decisions underpin every data structure (e.g. database) ever devised and are essential to being able to speak a common data \u2018language\u2019 that uses consistent definitions,\u00a0 formats and encoding structures.<\/p>\n<p>A very common business example of meta data is the structuring of an organisation\u2019s financial chart of accounts\u2026..i.e. what locations and functions, what departmental \/ budget codes, what time periods, what currency, what consolidation roll-up, what accounting standards, etc.<\/p>\n<p>Look more widely and you will also see that the concept of an invoice, an order, a requisition, a product, a part and many, many other familiar business artefacts are also meta data entities.\u00a0 That is, an object or item with an understood set of data attributes and rules that define and specify it and its relationship to other data entities.\u00a0 In fact, a map of such things is known as an entity relationship diagram or data schema!<\/p>\n<p>Once the basic data entity building blocks are defined, for both operational and maintenance purposes, they are often then divided into two further camps\u2026\u2026.static data and dynamic data.<span style=\"text-decoration: underline;\"><strong><\/strong><\/span><\/p>\n<p><span style=\"text-decoration: underline;\"><strong>Static data<\/strong><\/span>, as the name implies is data that either does not change, or more typically, changes relatively infrequently.\u00a0 Into this camp we can place data items such as products, customers, suppliers, BOMs, routings, etc.\u00a0 It is not that these data items never change, but that once created they commonly change little and infrequently\u2026\u2026for some organisations, sometimes verging on never\u2026..which can be a problem in and of itself!<\/p>\n<p>Finally, we have the camp of <span style=\"text-decoration: underline;\"><strong>dynamic data<\/strong><\/span>.\u00a0 As this name implies this is data that changes fairly frequently.\u00a0 Into this camp we can place data items such as quotes, orders, requisitions, GRNs, invoices, etc.\u00a0 These items by definition change regularly as part of the normal cycle and rhythm of conducting business.<\/p>\n<p>However, lets now circle back to our original point\u2026\u2026that base data changes relatively little on the whole.\u00a0 How does this reconcile with the idea of dynamic data which changes regularly for instance?\u00a0 Well, as for most things, the distinction is in the definition and the use of the qualifier \u2018base\u2019 in base data.<strong><\/strong><\/p>\n<p><strong>The point is that while dynamic data changes regularly (e.g. new invoice number, new requisition number, etc) and static data from time-to-time (e.g. new supplier, existing supplier address with a new address, etc) the meta data that defines those entities (e.g. the fact that there is an invoice number or address field) almost NEVER changes!<\/strong><\/p>\n<p>When is the last time for instance that you can remember a basic data concept like that of an invoice being introduced for the first time?<\/p>\n<p>Hence our use of the phrase \u2018on the whole\u2019 when describing the low change rate of base data.\u00a0 It also explains our desire to illuminate the distinction between the data camps as we did to explain things a bit more clearly and accurately.<\/p>\n<p>With your new understanding of these three data camps\u2026..keeping in mind that these definitions have a wide general applicability, but if you went outside the realms of business (e.g. scientific research), you would find far more data camps in use than just these\u2026\u2026you should be beginning to see how fundamental data is to everything built on top of it.<\/p>\n<p>And for common business concepts like P&amp;L, ROI, management reporting, project status, etc\u2026..that is almost EVERYTHING!!<strong><\/strong><\/p>\n<p><strong>Now perhaps it is becoming fully clear why an apparently boring and technically esoteric topic like data is actually of PARAMOUNT importance to any business!<\/strong><\/p>\n<p>After money, it is arguably the lifeblood of any organisation in terms of understanding and deciding where it is, where it needs to go and how well it is progressing on that journey.\u00a0 Without good quality data a business is quite literally lost\u2026\u2026even more dangerously so if it actually believes it knows where it is (i.e. based on access to \u2018bad\u2019 data) but in fact does not\u2026\u2026.<\/p>\n<p>This observation leads the conversation nicely to a few additional important facts about data.\u00a0 Namely, once you have some data, you also need to ensure that it is as:<\/p>\n<ul>\n<li>Accurate \u2013 plus or minus how much?<\/li>\n<li>Precise \u2013 to how many decimal places?<\/li>\n<li>Timely \u2013 when am I going to be able to get this?<\/li>\n<li> Available \u2013 How will I be able to access it?<\/li>\n<\/ul>\n<p>as it needs to be (i.e. as opposed to as much as it \u2018theoretically\u2019 could be) to fill your legitimate business needs.\u00a0 There are many approaches to accomplishing this list of requirements, e.g.:<\/p>\n<ul>\n<li>use of mobile technologies (e.g. handheld devices, laptops, etc)<\/li>\n<li>use of automated technologies (e.g. bar coding, RFID, etc)<\/li>\n<li>use of rigorous routines (e.g. perpetual inventory \/ cycle counting, stock counts, trial balances, month-end closes, etc)<\/li>\n<\/ul>\n<p>and many others too numerous to quantify here, but the message is the same.<strong><\/strong><\/p>\n<p><strong>If something is important to the organisation then the relevant data relating to it also needs to be defined, instantiated, collected, collated, accurate, precise, timely and available to a level of quality matched to the importance placed on it by the organisation!<\/strong><\/p>\n<p>The number of times we at Biz4ge have seen managers puzzling over \u2018mysterious\u2019 business project failures\u2026\u2026especially in the context of large, multi-site, multi-function transformational change programmes\u2026.is nothing short of astounding.\u00a0\u00a0 Failures in which they resolutely believe they broadly got (and perhaps did get) the strategy, processes, metrics, people, systems and other dimensions of change right, but still fell short somehow.<\/p>\n<p>Although not on every occasion of course, but with frightening regularity all the same, one of the most obviously missing considerations in our experience has been a good understanding of the quality of the underlying legacy data landscape.<\/p>\n<p>Had they (i.e. management, not the \u2018techies\u2019 who often do understand but whose views are often not sought or are \u2018unwelcome\u2019) deigned to look, it being a low-level techie subject and all, they might have actually seen (shock horror) that the data landscape was not fit for purpose.<\/p>\n<p>They might have even found that it never had been and was thus never going to be capable of supporting the level of integration of processes, metrics, systems, reporting, etc that everyone had been working towards!<strong><\/strong><\/p>\n<p><strong>Unfortunately, given its lowly \u2018techie\u2019 status, looking at the data landscape is not a high priority on many a corporate transformational change programme agenda.<\/strong><\/p>\n<p><strong>And although data is often not the only issue needing attention\u2026\u2026.it is one of the most commonly overlooked, and thus one of the most inscrutably responsible culprits for the failure to achieve the expected results!<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>To some use of the word \u2018data\u2019 signals the beginning of one of the most boring, technically esoteric and generally useless topics of discussion they can imagine.\u00a0 Data model, data dictionary, data schema, data cleansing, data coding &amp; classification\u2026\u2026or just plain old data. HELP!\u00a0 How much boredom and technophobia can one person be expected to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[27],"tags":[],"_links":{"self":[{"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/posts\/2034"}],"collection":[{"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/comments?post=2034"}],"version-history":[{"count":10,"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/posts\/2034\/revisions"}],"predecessor-version":[{"id":2036,"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/posts\/2034\/revisions\/2036"}],"wp:attachment":[{"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/media?parent=2034"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/categories?post=2034"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kz-a.net\/biz4ge\/index.php\/wp-json\/wp\/v2\/tags?post=2034"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}