<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Carl Fransman on Medium]]></title>
        <description><![CDATA[Stories by Carl Fransman on Medium]]></description>
        <link>https://medium.com/@carl.fransman?source=rss-ee3371851cba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8rYK_GOe8Z1xRqSzI9s26w.jpeg</url>
            <title>Stories by Carl Fransman on Medium</title>
            <link>https://medium.com/@carl.fransman?source=rss-ee3371851cba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 19:17:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@carl.fransman/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[IT shouldn’t limit corporate agility]]></title>
            <link>https://medium.com/dscribe-data/it-shouldnt-limit-corporate-agility-164689861801?source=rss-ee3371851cba------2</link>
            <guid isPermaLink="false">https://medium.com/p/164689861801</guid>
            <category><![CDATA[digitalization]]></category>
            <category><![CDATA[erp]]></category>
            <category><![CDATA[agility]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[docs]]></category>
            <dc:creator><![CDATA[Carl Fransman]]></dc:creator>
            <pubDate>Wed, 22 Sep 2021 11:59:46 GMT</pubDate>
            <atom:updated>2021-09-22T11:59:46.422Z</atom:updated>
            <content:encoded><![CDATA[<p>This summer’s Harvard Business Review focused on companies’ ability to adapt. Agility is high on every successful company’s agenda. Key to this success is the ability to execute. An unlikely bottleneck is appearing in the one department that should be bringing agility and speed. And it’s not even their fault! The IT department is victim of its own success. Indeed, in three decades, businesses have evolved to relying on IT for supporting most of their activities. Three decades may seem long but think of it: early nineties IT was limited to replacing typewriters and ledgers. A short period of point solutions was followed by a major effort to implement centralise IT around a single technology and, often, vendor. This was the golden age of ERP. We’re not saying ERP is dead but it seems the monolithic approach to IT is being questioned. Reasons often quoted are “ERP is expensive”, “one doesn’t fit all”, “we’re too dependant on one vendor”, etc. They’re all valid arguments. And we’re seeing more and more hybrid IT landscapes indeed where the core ERP is completed by functionality through adding best-of-breed solutions for instance. Also, M&amp;A activity has given rise to companies running on multiple ERP’s. At best it’s the same vendor but often it’s not. As everybody knows, (IT) integration efforts are long and expensive. And the impact of having to change puts extra weight on people, especially in the case of an already stressful takeover. Instead of starting harmonisation efforts right away, businesses take a more strategic, long term approach.</p><p>The whole thing, whichever approach one takes is confrontational though. In a previous life, we sold a best-of-breed solution to a multinational that had ERP from a single vendor. But they ran two separate instances; one for each half of the globe. We focused on implementing our tool on the instance of the headquarters. This was a very complex integration and we were up and running in six months. After going live, our client would then do the same with the second ERP instance. This took them about a whole year. First question is why that second integration took so long. Shouldn’t it actually be shorter than the first one? The whole functional analysis was done and we knew after the first integration where to find and how to connect to the data. Unfortunately that’s not how things went. First, it seemed that the ‘other half of the world’ needed to be convinced of the initial functional analysis. Luckily, the ended subscribing to the original thesis but it took some convincing. Second, and that’s the big one, the second ERP instance was configured totally differently than the first one. Remember: same technology! Because they were separate implementations, not all data was the same in both systems and, even more difficult to resolve: not all data meant the same thing. So you’d find a data point “size” and it’d be different to the one in the other ERP. Reconciling metrics (i.e. centimeters and inches) takes work but it isn’t complex. Knowing that one SIZE measure refers to size of the pallet whereas the other refers to the size of the actual item is harder to discover. So the whole integration process meant they had to go through each data point and consult people from the business in order to get the correct interpretation.</p><p>The example above is real and it’s not a lone example. I’ve seen this happen many times. The cost to these enterprises is very high: longer implementations often involves paying external consultants, it takes internal teams off of their day job and it delays putting the solution into production. Lost savings or lost income from that delay is often forgotten from cost calculations! We’ve also noticed in several cases that people when questioned about the meaning of their data answer “they’ve asked me the same question for that other IT project”. This means that knowledge exists but is not managed efficiently. What’s worse than investing in something that goes unused?</p><p>The key message for IT departments is twofold:</p><p>- it can be avoided</p><p>- it can be solved beforehand</p><p>Set up a central, easily accessible repository for all your data. And don’t just record what you have, but include the where, how it’s defined (across systems if it exists in multiple locations) and what it means. Make this repository accessible to not just the IT department but ideally include the whole organisation. Besides being easily accessible, it should also be easily searchable. This avoids people wasting time having to ask others and waiting for answers. Such a repository avoids having to ‘find out’ on the job and avoids a lot of the time wasted on the integration project. At the same time, it also allows the hybrid landscape to be efficient.</p><p>The time dimension is the most undervalued one in business strategy. If anything, when decisions and actions are taken is more important that what is done. Some products are released only to flop only to become hits when another vendor brings it to market a few years later. Is the success due to that vendor’s genius or did timing play a bigger role? In our case, implementing that central repository should not be done when the need arises. Instead, it should be core to any company’s IT strategy. Setting up and maintaining a central catalog, dictionary and glossary for all your data allows for a smoother roll-out and maintaining of systems integration. And, done well, it can relieve IT of most support calls pertaining to data as business users find their own way through the maze of IT systems, whether they be single- or multi-vendor.</p><p>Maintaining such a central repository is like basic hygiene for IT and data departments. The more agility is demanded from companies in order to maintain relevance and competitiveness, the more attention should be put paid towards basic hygiene. It allows your workforce to act and react more swiftly and to the point whereby instead of resisting, they may embrace change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=164689861801" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/it-shouldnt-limit-corporate-agility-164689861801">IT shouldn’t limit corporate agility</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data doesn’t work for you the way it could?]]></title>
            <link>https://medium.com/dscribe-data/data-doesnt-work-for-you-the-way-it-could-6ebfcf8e214f?source=rss-ee3371851cba------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ebfcf8e214f</guid>
            <dc:creator><![CDATA[Carl Fransman]]></dc:creator>
            <pubDate>Mon, 06 Sep 2021 13:39:36 GMT</pubDate>
            <atom:updated>2021-09-14T07:09:46.383Z</atom:updated>
            <content:encoded><![CDATA[<p>When discussing data-driven projects, many symptoms are referred to as ‘due to poor data quality’. That one description can hide many different causes and is a classical case of not being able to see the forest for the trees. Here are some of these symptoms:</p><p>· it takes more than 10 minutes to find data</p><p>· you rely on personal interpretation to know what the data means</p><p>· you don’t know which report tracks which KPI’s</p><p>· the company’s data team is bogged down with support requests rather than focusing on their core tasks</p><p>· data scientists complain they can’t deliver because of ‘poor data quality’</p><p>· updating existing or integrating new IT solutions takes way too long</p><p>· the same KPI doesn’t show the same result in different reports</p><p>· there are many data duplicates and users wonder which one is the trustworthy source</p><p>· too much time is lost in meetings to discuss the meaning and correct interpretation of dashboards</p><p>· business users admit they have poor trust in company data</p><p>· data resides in multiple systems; compiling reports is hard and requires IT support</p><p>· your company rolled out self-service reporting but adoption is low</p><p>· when data needs updating, nobody really knows who to turn to</p><p>I’m sure you can come up with more of these from your own experience — feel free to comment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ChCPx4z40zTdHiVNmSqFgg.jpeg" /></figure><p>Whereas until recently the solution to all these issues was to push for system consolidation, corporations are increasingly finding such projects expensive and, contrary to the original intent, they tend to limit flexibility, adaptability and slow down reactiveness of the business.</p><p>More and more companies rely on hybrid IT landscapes and therefore, as a “measure of good hygiene” introduce data catalogs as the go-to place for finding and organising data and the data catalog becomes the de facto go-to place from which to access data and reports.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ebfcf8e214f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/data-doesnt-work-for-you-the-way-it-could-6ebfcf8e214f">Data doesn’t work for you the way it could?</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 3P’s of data management]]></title>
            <link>https://medium.com/dscribe-data/the-3ps-of-data-management-84a373a759f1?source=rss-ee3371851cba------2</link>
            <guid isPermaLink="false">https://medium.com/p/84a373a759f1</guid>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[docs]]></category>
            <category><![CDATA[user-adoption]]></category>
            <category><![CDATA[metadata]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Carl Fransman]]></dc:creator>
            <pubDate>Mon, 23 Aug 2021 09:42:23 GMT</pubDate>
            <atom:updated>2021-08-23T12:59:36.849Z</atom:updated>
            <content:encoded><![CDATA[<p>Referrals to “the 3 P’s” are common in management literature. A quick search on the internet gives quite a number of explanations for the abbreviation “3P”:</p><ul><li>Product, Price, Place</li><li>Third Party (procurement, architecture, integration)</li><li>Triple Play (television, telephone, internet access)</li><li>Third Player</li><li>Three Pointer (basketball)</li><li>Proven, Probable, Possible (oil industry classification)</li><li>People, Process, Product</li></ul><p>Of these, “product, price, place” is the most commonly taught one in business school. Today, we introduce a slight twist on that one with regards to effective data management: policy, process, people. Let’s take a look at these 3P’s in more detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsaTxH-Q0ooSUiBdNYEIVA.jpeg" /><figcaption>Data is everywhere; people get lost</figcaption></figure><p><strong>Policy</strong></p><p>Your data management policy really refers to the fact that, as a business, you have a plan about data. What this means is that you’ve decided on a — hopefully company-wide — approach to dealing with data. This starts with recognising that there is data and this data, more often than not is siloed and dispersed across many systems. The plan either involves tossing out all those systems and replacing them by one single entity. We’ve seen many attempts at doing so. It typically requires many years of implementation, process changes and, more often than not, frustration amongst users. A more modern approach would let systems in place in recognition than one-fits-all doesn’t really work. Heterogeneous IT landscapes consisting of ERP, CRM, SCM,… and other best-of-breed systems are becoming common because reporting tools allow users to gather data from multiple sources and combine them into actionable output. The new policy then requires a common understanding of what data you have, where it can be found and what it means.</p><p><strong>Process</strong></p><p>In order to then effectively leverage dispersed data, a process needs to be put in place to ensure the above mentioned mapping of the data. Quite like a GPS helps us find our way, the process should help us find data, find the right data, and make sure we understand what this data represents. Indeed, if we allow data to be managed by the direct users — who should be best placed to use it correctly — we must ensure that other people know exactly what that data represents. Take, for example a multinational with a European HQ and US entity. The US users may use as “purchase price” the price at which their entity buys goods, but if those goods were acquired through the HQ, that price is more likely the HQ purchase price plus inter-company pricing. For the US entity their definition of purchase price makes perfect sense, but for corporate reporting, a clear difference must be made between both definitions.</p><p>Managing the “data GPS” is complex and involves many people. To implement the process one can’t rely on paperwork alone. Just like GPS replaced maps and atlases, the process must be materialised through implementation of a tool. That tool would be a data catalog; a digitised process allowing stewards to manage and trace data and offering end users an easy and straightforward access to data stored across multiple systems. The data catalog, by its explanatory nature helps turn data into information.</p><p><strong>People</strong></p><p>A good friend of mine likes to say “a fool with a tool is still a fool”. He does this to emphasise that, however good a tool may be, the person handling the tool determines the result. Therefore, tools should comply with a number of requirements:</p><ul><li>the tool must fit the purpose: depending on the planned use, certain features will be required, others “nice-to-have” and even others will be unneeded (and therefore may render implementation and adoption only more complex). When selecting a tool, seeking advice from specialised consultants is usually a good idea.</li><li>steep learning curves can kill a project before it leaves the starting blocks. Data stewards and end users will use the tool in very different ways; make sure that the training is adapted towards their needs.</li><li>the tool should be efficient and effective. It should be easy to use, accessible, able to search swiftly to all and hardly require any explanation for data consumers (efficient). Your web search engine doesn’t come with a manual either! It should also be able to find the correct data (effective). Some searches may yield a multitude of possible answers. Similar to a search engine, answers should be classified according to likely importance for the person searching. This can be through ratings (by other users), division of the person searching, etc.</li></ul><p>Adoption of the tool and continued usage are key for the success of your data management project. People are emotional beings and we must overcome the initial resistance to change when introducing a data catalog. This is achieved by the efficiency and effectiveness mentioned before. But research has shown that participative systems in which users remain engaged and are encouraged to provide feedback or participate in building out the content not only achieve faster adoption but maintain higher usage rates. User engagement is different for all. While many users are quite happy to just use the GPS, others are enticed to rate and leave comments (as per Google reviews or YELP for restaurants). Being able to contribute increases people’s sense of purpose and before you know it, you have a real data community.</p><p>As you may have guessed by now, while we build the tool, effectively helping to materialise the process, our true focus is on the people. People are the critical success factor of your data management project. Policy and process can be bought (consulting, tools) but the support of your users must be won. Therefore, whatever you do, make sure that your people will want to use the tool. While this can be as simple as “like that tool better”, emotional hurdles are harder to overcome than anything else. And it doesn’t depend on features alone, those in charge of the project will have the important task of picking the tool that will eventually incite the highest usage. As history has shown, you’d rather have picked the iPod than the Zune…</p><p>Therefore, in a spin on the classical “3P” expression, the 3P’s of data management really are People, People and People.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84a373a759f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/the-3ps-of-data-management-84a373a759f1">The 3P’s of data management</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data is the new oil — start digging!]]></title>
            <link>https://medium.com/dscribe-data/data-is-the-new-oil-start-digging-8d5e38c1eef3?source=rss-ee3371851cba------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d5e38c1eef3</guid>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[data-catalog]]></category>
            <category><![CDATA[metadata]]></category>
            <dc:creator><![CDATA[Carl Fransman]]></dc:creator>
            <pubDate>Wed, 11 Aug 2021 07:10:16 GMT</pubDate>
            <atom:updated>2021-08-19T12:08:13.046Z</atom:updated>
            <content:encoded><![CDATA[<h3>Data is the new oil — start digging!</h3><p>Imagine your backyard were located right above an oil field. And you knew about it. Somehow though, you never got to installing a drilling rig. Can’t complain about missing the pot at the end of the rainbow then, can you?</p><p>Well, this is exactly the kind of situation we encounter all the time; companies are awash with data, the C-suite keeps repeating the mantra “data is the new oil”, yet, somehow, they never started drilling. Sure, shovels and pick axes, yes. But really drilling? With the right equipment? Nah.</p><p>So far for similarities though. Contrary to discovering petroleum, drilling for and exposing data is not very capital intensive. Nor does it require physical labor. And that may be part of the problem. Companies are using their data on a daily basis. Some of them actually do quite a decent job given the tools they employ. Very few though actually know if and how well they’re using their data resources or what state those resources are in.</p><p>One of the challenges facing corporates is the disparity of data sources. Data may originate in different systems, be maintained by different people or even started life in different companies altogether (as in the case of post-M&amp;A). Also, whereas the 90’s saw a push towards centralization and unification around massive ERP deployments, the 20’s see an uptake of backbone plus best-of-breed and the corporate IT landscape becomes more heterogenous. It’s as if a company would have different warehouses, some storing similar parts, some storing different parts. In the end, in order to manage and deploy the inventory efficiently, one needs a good inventory management system. We’ve gotten so far that this is a given. Why then, are data not yet viewed as inventory?</p><p>Data have long been part of the technical domain. But as business users have increasing demand for using data, i.e. for self-service BI, companies have discovered that users don’t always access the right data, understand the data correctly or plainly don’t find the data altogether. In which case they need to ask IT again. And IT often discovers there may not be a single source for the requested data. Thus, we must put in place a data inventory management (for both technical — IT — and business data). Enter the Data Catalog.</p><p>This Data Catalog is nothing else than a layer above all your data systems to tell you the “what, where, how to access” of all data. For end users, this means that through a single access point they can find any data, get a clear understanding of what this data point represents and how to access that data point from a technical point of view so it can easily be incorporated in a report for instance. Similarly, the Data Catalog will allow the user to find reports that incorporate the searched data point.</p><p>The Data Catalog allows people, whether they’re technical or business users, to track down data. The current process often involves asking data specialists. This creates avoidable non-value-add overhead for a team that would rather (and better) use their time analysing the data instead of merely helping end-users access it.</p><p>A good Data Catalog though has to do more than just be the altas of data. Instead, it should allow enriching of data so that it becomes searchable like we search the web. And the found data should be actionable. All this leads to finding data according to relevance, not just by exactly matching search terms.</p><p>Success of a Data Catalog implementation can be measured through adoption: do your users connect to and employ the catalog? Population of the catalog is automated as the tool crawls corporate systems in search of data and reports. The Data Catalog is inherently dynamic, brings down data silos and reduces data inconsistencies. Appointing data stewards lets the best placed people validate and enrich the catalog and more often than not, several people must contribute. This means that the Data Catalog must be a true collaboration tool. A good tool thus leads to more people (effectively) using data, increases data literacy and data quality.</p><p>Most companies report “rapid ROI” just by reducing time spent for searching and finding data. Most companies avoid reporting how much they saved by avoiding data inconsistencies, wrong interpretation and usage of data, etc. but a general consensus is that Data Catalogs lead to:</p><p>- improved efficiency</p><p>- better decision-making through improved data comprehension</p><p>- better data consistency / quality</p><p>- better compliance</p><p>In this day and age of digitization, employees’ effectiveness is enhanced by smart data usage. So let’s empower our employees by equipping them with the right tools. Now more than ever, speed of action is important and we want to make sure our employees can access data rapidly but also avoid they use the wrong data or use data wrongly. The Data Catalog is the tool for the trade.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d5e38c1eef3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dscribe-data/data-is-the-new-oil-start-digging-8d5e38c1eef3">Data is the new oil — start digging!</a> was originally published in <a href="https://medium.com/dscribe-data">dScribe data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>