<?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 NAVARA on Medium]]></title>
        <description><![CDATA[Stories by NAVARA on Medium]]></description>
        <link>https://medium.com/@navara?source=rss-2468670c458d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MizjkZ2UmscmU_dVAkxUfA.jpeg</url>
            <title>Stories by NAVARA on Medium</title>
            <link>https://medium.com/@navara?source=rss-2468670c458d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:28:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@navara/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[How to improve quality and a fast time to market of]]></title>
            <link>https://medium.com/@navara/how-to-improve-quality-and-a-fast-time-to-market-of-5758615ccb3d?source=rss-2468670c458d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5758615ccb3d</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[navara]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[NAVARA]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 12:25:10 GMT</pubDate>
            <atom:updated>2020-07-15T15:30:24.533Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to improve quality and a fast time to market of mobile apps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F50Lcc_i3HrT0_6U7a3Sjw.jpeg" /></figure><p>Do you recognize the following: waiting for hours or perhaps days for a new version of your app, before you can release it? Fast feedback on the impact of changes is required to keep the team focussed and see business value increase every increment. We will show how to improve quality of app development and speed up time to market by using the right test environment and test strategy.</p><p>As part of regular software development, manual testing is often in place, though it’s time consuming and doesn’t provide the required quick feedback. Especially in case of mobile app development, manual testing gets even more tedious due to the large number of different mobile device, on which you have to test your app. <br>To be able to scale development and testing of a mobile app, different types of automated tests need to be created. These tests need to run fast in the QA environments and reduce the time needed to release a quality assured new version of the app. We elaborate on the the test strategy for your mobile app, to reduce the manual test effort and obtain a quick and efficient feedback loop.</p><h3>Improve QA Environment</h3><p>In most cases there are one or more software development teams, working together to create new features. These teams use a version control system for the code-base (e.g. Git) and use separate branches of this code base to develop features next to each other.</p><p>To get quick feedback on introduced regression defects, which might be caused by the code change for these features, it must be possible to build all those versions and run the automated test. Although there are multiple tools available to setup an automated testing pipeline (e.g. Teamcity, Jenkins or Azure DevOps), they all require a plan for the setup of your QA environment in which the required feedback speed is incorporated</p><p>A plan for an ideal world situation would show that a commit (and push) to the version control system triggers the build of the mobile app. After a successful build, a docker container is spinned up, which contains the backend system, while the app is deployed on a device or simulator. All regression tests are executed automatically. When all tests are successful, a new version of your app is ready for production.</p><p>To get to this ideal situation your strategy will need the following:</p><ul><li>The test environment needs to be available for every commit for every team. This test environment needs to be as similar as possible to your production environment.</li><li>All tests must be automated with enough coverage to assure the quality of the product.</li><li>A dashboard displaying the results of the latest test is available and/or notifications which can be integrated in collaboration tools like Slack are used. This will help the development team to get the fast feedback they need.</li></ul><p>When you combine the different Android- and iOS versions with the number of different mobile devices, there are thousands of unique combinations on which your app is expected to work flawlessly. As you might already know you won’t be able to test every combination.</p><p>As a best practice we test our app in combination with the mobile devices the end-users are using. To get to this data we record the device information on which our app is used and test our app with the most used devices. Keep in mind that devices can be different for each country and for each application.</p><p>When automating mobile tests, you can execute them on your own devices, though maintaining an on-premise device lab, is a very complex task. A SaaS environment, in which you can run automated tests on mobile devices, provides a significant improvement in scalability, improves time to market (especially for supporting new devices modules and versions) and improves device availability SLA. Examples of these are; <a href="https://saucelabs.com/">Saucelabs</a>, <a href="https://experitest.com/">Experitest</a>, <a href="https://www.browserstack.com/">Browserstack</a>, and <a href="https://www.perfecto.io/">Perfecto</a>.</p><h3>Speed of test execution</h3><p>Nobody wants an app which is quickly developed, but lousy to use. Speed of test execution is an important factor to successfully develop your app. Yet, speed should go hand in hand with quality. High quality is not a synonym for slow development. Finding the right strategy where these two are not mutually exclusive, is the key.</p><p><strong>The principles of the testing pyramid are a good foundation for efficient testing optimizing both speed and quality.</strong></p><p>This strategy has the purpose to ensure:</p><ol><li>Development teams are in control of the quality of the product. They can indicate at any point in time what the status of the quality of the product is.</li><li>Testing is done in the most efficient manner. This means you get the most insights in the quality of the product without putting in a disproportionate amount of effort and/or time.</li><li>The way of working is scalable. This means we can sustain the way we work with a growing application or we can easily scale up our testing capacity without much more effort for the existing teams.</li></ol><p>Since quality of the product can be arbitrary and it’s not possible to get 100% test coverage, a risk based testing policy is needed.</p><p>Risk is composed out of 2 components:</p><p><em>Impact of failure * likelihood of failure</em></p><p>The development team and stakeholders define which tests are required mitigating the risks of a failing app. <br>To reach each of the above-mentioned goals, a common test approach is required for all teams working on the same product, to get a certain amount of (insight in the) quality of the product within a certain phase in the release cycle. The testing pyramid is a central piece within the strategy to reach the goals. Especially in achieving the goal related to executing tests in the most efficient manner. The testing pyramid was initially called “the test automation pyramid” by Mike Cohn with its origin in the book <em>Succeeding with Agile</em>. At this point in time it knows many different graphical representations based on the context of its usage. We can differentiate the following layers in the testing pyramid for mobile:</p><figure><img alt="Pyramide for mobile testing" src="https://cdn-images-1.medium.com/max/1024/1*Bfx5KGHl6QzKJQm-Gp04EQ.png" /></figure><ol><li><em>Unit testing</em></li><li><em>Visual (UI) testing</em></li><li><em>End2End testing</em></li><li><em>Manual testing</em></li></ol><p><em>Unit testing; It’s the foundation of the pyramid and should cover the vast majority of the front-end logic, since they are very fast. You’re testing isolated pieces of code (units) that contain (business) logical rules. We can differentiate between unit tests that require nothing else but its own code and unit integration tests, where we have a dependency on another unit or a dependency on another framework or plugin. Dependencies are mocked.</em></p><p><em>Visual (UI) testing; Also called visual regression tests, are focusing on the layout of the elements within a screen where they are in a composition which represents the composition of a screen used by the customers. The goal here is checking if the layout meets the UX/design requirements taking into account different screen sizes, resolutions, operating systems; all factors that can influence the layout of a screen significantly. Due to the great number of different mobile devices a good strategy is required for mobile. Specifically not in scope at this stage in the testing pyramid, is functional testing (sometimes it will be done implicitly due to necessary navigation throughout the application, but this should be minimised). The test data used is mocked to prevent involvement of other systems that are not in scope of the test which can only cause flakiness of the test.</em></p><p><em>End2End testing; In the previous two phases we have concluded that our UI is looking good and the business rules in our mobile app are working. We now want to establish that the logic and information we need from the backend is correctly working with the UI. At this stage we test the integration of the frontend with a live backend. The test data is created before the start of the test, for example by using data builders that insert the test data in a database required for the test case. Flows are tested from beginning to end focusing on a single test case. Avoid setting up your test data using UI Automation, this will unnecessary cause dependencies on functionality that this is out of scope for that specific test.</em></p><p><em>Manual testing; Manual testing is the tip of the pyramid and is the last resort to test whatever has not been tested in the previous layers of the pyramid or could not be tested in an automated way. This can be either due to a lack of the needed technology stack or knowledge to automate the test or the disproportionate effort needed to automate a low risk, low impact feature which is quickly tested manually. The manual testing effort should be as low as possible as this layer is difficult to scale without putting in more man power. A person can only do so much. These test are also known to be error prone since a human is not good in executing a test the same way over and over again. This does not mean that a test minded person should not go at least once through a new feature to validate it manually for “its look and feel” or exploratory testing, but we’re talking about regression testing here.</em></p><p>The testing pyramid relies on the broad basis of unit testing which are fast, reliable and scalable, up to the manual testing which is slow, costly, error prone, not scalable and last but not least mind killing and therefore should have the least number of tests. Another principle of the pyramid is that we avoid test coverage duplication as much as possible. Each layer has its own purpose and the trust in the application quality depends on the results of each layer. A failure in any layer could potentially mean a blocking issue for the release of the application. <br>When writing your automated tests, for every assertion you need to ask yourself: ‘is this not already tested in a lower layer of the pyramid?’. If the answer is ‘No’, ask yourself: ‘can it be tested on a lower layer?’ If the answer is ‘Yes’, do so. <br>This does require a solid understanding of what is and what is not already tested and what the technological possibilities are, within the architecture you are working on to be able to run the tests as fast as possible. Therefore quality and the way to get fast feedback should be an integral part of the team effort, as a single team member’s expertise might cover only part of the testing pyramid or test environment. A close collaboration between the team members is key to success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0VOqZLwOo12g8G3i0pRZow.jpeg" /></figure><p>Important note: What isn’t mentioned yet, but should surely not be forgotten are the API tests for your back-end system. These are the foundation for the E2E tests and should cover not only happy flows but also focus on alternative flows and error flows. The testing pyramid as mentioned above is envisioned from the mobile app’s perspective and used as code for a single application. The backend code can be reused for other applications as well e.g. another app or a web application variant for the same product.</p><h3>Conclusion</h3><p>Development teams must be in control of the quality of the product, testing is done in the most efficient manner and the way we work is scalable. These goals will enable quick and successful app releases. Therefore, you need to invest in a QA environment which is able to execute the automated build and test of your app on many devices on demand.</p><p>Reduction of manual tests in favor of faster and less error prone unit test and UI tests will speed up the feedback loop and improve the quality of your app. Instead of executing mind numbing manual tests to assure the quality of your app, you can use your brain to develop awesome new features.</p><p>Using continuous improvement and a risk based approach, can help you to start applying the test pyramid. You can start today by changing your manual tests into an automated test strategy.</p><p>Do you want to get to know how you can get faster feedback, do you need help to implement the testing pyramid or picking the right tools for your technology stack? We are ready to help you! Please contact us at <a href="http://www.navara.nl/">NAVARA.nl</a></p><p>Article by: <a href="https://www.linkedin.com/in/jvanheerwaarden/">Jeroen van Heerwaarden</a> and <a href="https://www.linkedin.com/in/guido-vermeulen-46b22170/">Guido Vermeulen</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5758615ccb3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ook bij corona noodwet is publiek debat nodig]]></title>
            <link>https://medium.com/@navara/ook-bij-corona-noodwet-is-publiek-debat-nodig-fa09adfff8a?source=rss-2468670c458d------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa09adfff8a</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[coronavirus]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[NAVARA]]></dc:creator>
            <pubDate>Mon, 15 Jun 2020 11:38:05 GMT</pubDate>
            <atom:updated>2020-06-15T11:44:13.981Z</atom:updated>
            <content:encoded><![CDATA[<p>Het kabinet heeft 25 mei een voorstel ingediend voor een noodwet. Deze noodwet stelt telecomdata op gemeenteniveau beschikbaar aan het RIVM om te gebruiken in de strijd tegen corona. Op wat korte berichten na, is uitgebreide media aandacht of publiek debat tot nu toe uitgebleven. Dat is opvallend aangezien het wetsvoorstel, net als de veelbesproken corona-app, zich richt op telecomdata. Deze corona-app werd wegens zorgen over privacy door experts, politici en burgers bedolven onder een laag van kritiek. Dit terwijl deelname aan de corona-app op vrijwillige basis was en je bij de noodwet niet kunt weigeren deel te nemen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p4T61vErEIptNgio6YzThQ.jpeg" /></figure><p>Bij gebrek aan publiek debat, delen wij onze mening; De privacy is bij de noodwet beter geborgd dan bij de corona-apps, maar de toegevoegde waarde van deze data is in de praktijk niet overtuigend. Bovendien wil beter geborgd niet zeggen dat het voorstel helemaal privacy veilig is. Het huidige voorstel moet daarom, net als bij de corona-apps, door onafhankelijke expert-panels openbaar worden beoordeeld zodat privacy risico’s en maatschappelijke baten tegen elkaar kunnen worden gewogen.</p><p><strong>Noodwet gebruikt telecomdata tegen corona</strong></p><p>De noodwet, die al 1 juli zou moeten ingaan, stelt een jaar lang geanonimiseerde telecomdata beschikbaar aan het RIVM. Deze telecomdata wordt door telefoonproviders verzameld en bevat informatie over telefoonverbindingen die klanten maken met zendmasten. Door die gegevens van meerdere zendmasten te combineren — zoals ook gebeurt met satellietdata bij GPS — kan redelijk accuraat de locatie van de klant worden bepaald.</p><p>In het voorstel voor de noodwet wordt de locatiedata opgeteld tot gemeenteniveau. Het RIVM krijgt deze gegevens niet rechtstreeks van de telecomproviders. Telecomproviders leveren de data op persoonsniveau, waarbij het is ontdaan van persoonlijke informatie. De data kan hierdoor in theorie niet terug worden herleid tot personen. Deze data wordt geleverd aan het CBS, die op haar beurt de data optelt tot gemeenteniveau en doorgeeft aan het RIVM. De data die het RIVM krijgt bevat een telling, per uur, per gemeente, van het totaal aantal mobiele telefoons dat daar aanwezig is vanuit andere gemeente. Daarmee kan je bijvoorbeeld voor gemeente Arnhem zien dat er tussen 13:00 en 14:00 op 5 juni 100 telefoons uit gemeente Utrecht aanwezig waren. Voor buitenlandse telefoons worden meer geaggregeerde categorieën gebruikt, zoals ‘België’, ‘Duitsland’ en ‘Noord-Amerika’.</p><p><strong>De afweging tussen privacy en toegevoegde waarde</strong></p><p>Zoals bijna elke wet is de noodwet het resultaat van een compromis. Het gebruik van telecomdata met locatiebepaling kan helpen bij het indammen van corona, maar de prijs hiervoor wordt betaald met inleveren van privacy. In Korea is bijvoorbeeld gekozen veel privacy in te leveren in de strijd tegen corona: data wordt op persoonsniveau verzameld en opgeslagen en deelname is verplicht. Hoewel daar momenteel een tweede opleving van het virus is, heeft Zuid Korea tijdens de eerste golf de curve sterk weten af te vlakken. De data wordt bijvoorbeeld gebruikt om te controleren of patiënten in quarantaine blijven, en te onderzoeken waar besmette mensen vlak voor besmetting zijn geweest en met wie ze in aanraking zijn geweest.</p><p>Dergelijk gebruik van telecomdata is in Nederland niet mogelijk door de Algemene Verordening Gegevensbescherming (AVG). De privacy van het individu is in het huidige voorstel van de noodwet dan ook gewaarborgd door de locatiedata te sommeren tot gemeenteniveau en nergens aantallen onder de 15 te rapporteren. Dat wil niet zeggen dat het voorstel zonder risico is. Het recente datalek in de Infectieradar van het RIVM laat zien dat de beveiliging van data vaak te wensen over laat. Een relevante vraag is dan ook of de beveiliging voor het delen van de data tussen de telecomproviders en het CBS wel op orde is. Een datalek van de gegevens voordat ze gesommeerd zijn zou betekenen dat de persoonlijke locatiegegevens per uur van alle Nederlanders op straat liggen.</p><p>Daarnaast beperkt sommeren van de data de toepassingsmogelijkheden. De rijksoverheid beschrijft het volgende voorbeeld<em>: “Stel dat uit de zendmastgegevens blijkt dat op een zaterdagmiddag bijzonder veel mensen uit bijvoorbeeld Rijswijk in Delft zijn geweest. Als er in één van de twee gemeenten (nieuwe) besmettingen worden gevonden, kan het RIVM de lokale GGD informeren dat dat ook zo zou kunnen zijn in de andere. Dit maakt het mogelijk om regionaal maatwerk te leveren.” </em>Bij ons rijst de vraag hoe dat maatwerk er in de praktijk uitziet. Zelfs als er bijzonder veel mensen uit Rijswijk in Delft zijn geweest is het niet mogelijk met zekerheid conclusies te trekken over de bewegingen van het virus. De gesommeerde locatiedata geeft de illusie van inzicht, maar zegt weinig over het virus en besmettingsrisico’s. Wat de toegevoegde waarde in de praktijk is van zulke onzekere inzichten is ons niet duidelijk.</p><p><strong>Publiek debat en expert-panels zijn weer nodig</strong></p><p>Er zijn dus nog onbeantwoorde vragen over de noodwet, de bijkomende risico’s qua privacy en de toegevoegde waarde in de praktijk. Dat het kabinet heeft besloten, in contrast met de corona-apps, hier voorbij te gaan aan publiek debat en onafhankelijke expert-opinie vinden wij dan ook een vergissing. Zeker gezien het bewezen nut van expert-panels bij de corona-apps: de haastig ingediende app-ontwerpen bleken van alle kanten te rammelen.</p><p>Ook de noodwet loopt het risico steken te laten vallen door de haast waarmee deze ingevoerd moet worden. Gelukkig kijkt de Autoriteit Persoonsgegevens (AP) mee, maar hun beoordelingsrapport over de noodwet is niet openbaar gemaakt en dus is het onmogelijk te beoordelen welke risico’s er in kaart zijn gebracht en hoe die worden afgedekt. Daarnaast kan de AP enkel bepalen of het voorstel wettelijk is. Niet of het voorstel wenselijk is. Daarvoor is andere expertise nodig. Het kabinet zegt constant te varen op de inzichten van onafhankelijke experts. Vraag dan ook nu naar hun kritische blik zodat zij de input kunnen leveren voor een publiek debat waarin de privacy risico’s tegen de maatschappelijke baten beter worden afgewogen.</p><p>Met dank aan: <a href="https://www.linkedin.com/in/tim-weelinck-25621448/">Tim Weelinck</a>, <a href="https://www.linkedin.com/in/rensnaeff/">Rens Naeff</a> en <a href="https://www.linkedin.com/in/roelstijl/">Roel Stijl</a>. Voor informatie: info@navara.nl</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa09adfff8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the importance of mastering data]]></title>
            <link>https://medium.com/@navara/understanding-the-importance-of-mastering-data-cdf567c80633?source=rss-2468670c458d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdf567c80633</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[NAVARA]]></dc:creator>
            <pubDate>Mon, 04 May 2020 10:39:28 GMT</pubDate>
            <atom:updated>2020-05-08T09:54:05.108Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Do you think you are a digital dinosaur?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f1HF06UjCWNP2RNkkayj8Q.jpeg" /></figure><p>Organisations have to move to a digital agenda, to keep their relevance. As data is one of the cornerstones of digitization, it is time to consider: Do I have sufficient knowledge and understanding on the subject of Data and Artificial Intelligence? Can I make the right choices when it comes to data-driven architecture? How can I monetize my data securely? Or am I a digital dinosaur? If you think you are a digital dinosaur, look no further.</p><p><em>— “Yet, digital dinosaurs making decisions without the aid of data is like a T-rex trying to do push-ups, it’s unlikely to lead to the desired outcome.” —</em></p><p>Executives often find knowledge and understanding of data, and how to use it, too technical and/or too detailed. Having a data knowledge gap will slow down critical data-related decision making. This is an impediment to becoming data-driven. So, what does a digital dinosaur need to know to make informed decisions in data-related matters?</p><p>This series elaborates on three topics of which we think digital dinosaurs know too little;</p><ol><li>The why of data;</li><li>The how of data;</li><li>The what of data.</li></ol><p>For a deep-dive on the main reasons to work data-driven in the digital age see our previous article: <a href="https://medium.com/@navara/are-you-a-digital-dinosaur-d8fa5f3cb508">Are you a digital dinosaur? — NAVARA</a></p><h3><strong>Unused data potential within the organisation</strong></h3><p>In this article we focus on the question; what is data? Many organisations have more data than they think. As a digital dinosaur, understanding more on the structure of data enables you to identify critical internal and external data, and subsequently open a new world of data-driven business opportunities.</p><p>Most well known is the data that is a digital representation of a fact, e.g. a product number, a purchase date, a telephone number or a customer name. This structured data is captured, processed and stored within an organisation. This data is stored in many forms i.e.; databases, spreadsheets, data warehouses and data lakes. However, the fact is that data can also be stored in the form of emails, text documents, pictures and non-digital documents. This second type of data is called unstructured data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*BGdSsChl9ylx5lnM" /><figcaption>Structured versus unstructured data</figcaption></figure><p>Structured data is the type of data that people tend to have in mind when thinking about data. An example of the format of structured data is a spreadsheet containing financial transactions, inventory lists and payrolls. The structured format of the data has many advantages one of which is the ease of usability in processes and applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6u_XOFRXSfYS-8kXXGrcgQ.jpeg" /></figure><h3><strong>Using structured data</strong></h3><p>As a SaaS provider, Wolters Kluwer knows the value of data like no other. To improve the customer experience, and improve internal processes, the organisation wants to make more use of their data. NAVARA supported Wolters Kluwer by obtaining actionable insights based on structured customer data. The customer data is used to analyse their sales funnel, including marketing. This analysis helped to get a better understanding of the process, and resulted in actionable insights for further improvement.</p><p>Click here <a href="https://www.navara.ai/work/work-wolters-kluwer"><em>https://www.navara.ai/work/work-wolters-kluwer</em></a> for more information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RFiPyHDvRGOWWgWpnZMd8A.png" /></figure><p>Unstructured data is not formatted in a defined structure. This type of data can be found almost everywhere, i.e. emails, photos, audio files, and text documents. With the explosive growth of emails, unstructured data accounts for approximately 80% of all organisations’ data. This number is expected to rise fast with the growth of mobile applications and chatbots. So extensive unused value is hidden in unstructured data. Organisations have an opportunity to capitalize this value by utilising this data. Understanding unstructured data is a key element to prevent becoming a digital dinosaur. Extracting and utilizing the data in its unstructured form is difficult. Next to this, the unorganised nature of unstructured data makes it more difficult to control the availability and trustworthiness of the data.</p><h3>unstructured data</h3><p>The NS transports thousands of people every day. Unsurprisingly, they receive a lot of feedback from their customers. This feedback contains valuable information for the NS to improve their services. With the help of NAVARA, feedback in the form of unstructured text data is standardized, made available and analysed. This approach enables the NS to extend their customer insights, efficiently process and respond to customer feedback and pinpoint and act upon the most important areas of improvement.</p><blockquote>-” Understanding that there are different categories of data is the first step to understand both complexity and opportunities of data. Knowing how to use all types of data will enable you to become more data-driven” .</blockquote><h3>Challenge yourself!</h3><p>As an organisation, are you already sufficiently data-driven? Or are you (becoming) a digital dinosaur? Challenge yourself! Identify three sources of unstructured data within your organisation not yet utilized within a process, applications or report. Keep in mind how these sources would differentiate your business from your competitors.</p><p>Want to learn more and close the knowledge gap? Join NAVARA’s executive leadership workshops. Or one of NAVARA’s operational analytics impact workshops.</p><p>This blog was made possible by:</p><p>Rens Naeff [<a href="https://www.linkedin.com/in/rensnaeff/">Linkedin</a>] and Chris Lemmens [<a href="https://www.linkedin.com/in/chris-lemmens/">Linkedin</a>]</p><p>Please visit: <a href="http://navara.ai/">navara.ai</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdf567c80633" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are you a digital dinosaur?]]></title>
            <link>https://medium.com/@navara/are-you-a-digital-dinosaur-d8fa5f3cb508?source=rss-2468670c458d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8fa5f3cb508</guid>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[data-driven]]></category>
            <dc:creator><![CDATA[NAVARA]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 11:36:21 GMT</pubDate>
            <atom:updated>2020-03-31T11:36:21.794Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Do you think you are a digital dinosaur? Reasons to work data-driven in the digital age.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KDpykiY6XR2Y0EH9hYvZsg.png" /></figure><p>Data is changing the business landscape in every way. Most companies have a digital agenda. And are adapting to these changes to keep their relevance in the (near) future. So it is not surprising that data is increasingly becoming the cornerstone of companies’ — digital — strategy.</p><blockquote>“… making decisions without the aid of data is like a T-rex trying to do push-ups, it’s unlikely to lead to the desired outcome”.</blockquote><p>Now is the time to consider: am I a digital dinosaur? Or do I have sufficient knowledge on the subject of Data and Artificial Intelligence? Yet, digital dinosaurs making decisions without the aid of data is like a T-rex trying to do push-ups, it’s unlikely to lead to the desired outcome. If you think you are a digital dinosaur, look no further.</p><p>This series elaborates on three topics of which we think digital dinosaurs know too little;</p><ol><li>The why of data;</li><li>The how of data;</li><li>The what of data.</li></ol><p>Changes, initiated by data &amp; analytics, are gaining more and more pace. Making it apparent that executing a data-driven strategy and gaining value from it, is not easily done. One key reason for this is a general lack of data specific knowledge within companies, especially on a strategic level. Executive often find knowledge about data and how to use it too technical and/or too detailed. This knowledge gap slows down necessary data related decision taking, actions and investments by executives. If this is an impediment to become data-driven, what does a so-called digital dinosaur need to know to make informed decisions in data-related matters in order to take advantage of data?</p><h3>Why work data-driven in the digital age</h3><p>In this article, we focus on the question why companies across sectors gain competitive advantage by making use of data. This competitive advantage can be based on three main pillars, i.e. growth, cost reduction or compliance. In this article we focus on the first two.</p><h3>Growth:</h3><p>Leveraging your data to increase revenue. In a mature market outperforming your competition is one of the few ways for a company to grow. Whereas digital dinosaurs will be struggling to outperform the market, data driven companies can contribute to this by increasing customer satisfaction (e.g. through customer 360 approach), reducing customer churn and product innovations.</p><p>Improving the relationship with your customers will result in higher customer satisfaction and lower churn. Having data driven product innovation also increases growth of market shares. Data can contribute to customer relationship by fact-based exposing your customers needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JbYLDYXkxoYAMpsgHhstXg.jpeg" /></figure><h3><em>How Robert Walters increased their revenue by working data-driven</em></h3><p><em>The recruitment business is highly competitive and rapidly changing. To stay ahead of competition and to maintain their market position in the future, Robert Walters is always keen to adopt new technologies. NAVARA helped them to understand their data, and how to economise the potential value of it. Candidate and placement data is a key differentiating factor of recruiters. We used this dataset to develop AI models that predict placements with an accuracy of 90%. Furthermore, data analysis resulted in a dozen actionable insights into the placement process that led to a significant increase in revenue. Click here [</em><a href="https://www.navara.ai/work/work-robert-walters"><em>https://www.navara.ai/work/work-robert-walters</em></a><em>] for more information on this case.</em></p><h3>Efficiency</h3><p>Another reason to work data driven is to increase efficiency. We use efficiency in the broadest sense. Leveraging data can improve the way we work by targeting bottlenecks in business processes, reduce the amount of rework and streamline handovers, increasing buying frequency and/or decreasing spend. In doing so an organisation can increase performance with their current workforce or meet their current performance with a reduced workforce. In addition, efficiency can be gained by reducing the amount of working capital, e.g. improving stock and invoice management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2fwIzU8jiL8-IlTwb3NajQ.jpeg" /></figure><h3>How Eneco increased their efficiency by working data-driven</h3><p><em>Eneco is a major player in the energy transition towards more sustainable energy and heat solutions. To meet the growing demand for sustainable solutions the current process of identification, qualification and (technical) design needs to be streamlined. We helped them to automate where possible, reduce the number of handovers and the amount of rework. The digitised process within the adapted NAVARA.ai platform increased the efficiency by a factor 5. Helping Eneco to be ready to handle the growing demand for sustainable energy and heat solutions.</em></p><p><em>Click here [</em><a href="https://www.navara.ai/work/work-eneco"><em>https://www.navara.ai/work/work-eneco</em></a><em>] for more information on this case.</em></p><h3>Challenge yourself</h3><p>As an organisation, are you already sufficiently data driven? Or are you (becoming) a digital dinosaur? Challenge yourself! Come up with 3 data-driven cases that will increase your revenue and optimize your operations. If any of these three cases are not yet started or in place, you need to take action now.</p><p>Want to learn more and close the knowledge gap? Join NAVARA’s executive leadership workshops. Or one of NAVARA’s operational analytics impact workshops.</p><p>Keep tuned to our channel as we will be regularly posting blogs on achieving digital excellence. Don’t become a digital dinosaur!</p><p>This blog was made possible by:</p><p>Rens Naeff [<a href="https://www.linkedin.com/in/rensnaeff/">Linkedin</a>] and Chris Lemmens [<a href="https://www.linkedin.com/in/chris-lemmens/">Linkedin</a>]</p><p>Please visit: <a href="http://navara.ai/">navara.ai</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8fa5f3cb508" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>