<?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 Stefan van Oirschot on Medium]]></title>
        <description><![CDATA[Stories by Stefan van Oirschot on Medium]]></description>
        <link>https://medium.com/@stefanvanoirschot?source=rss-cd36008b9e7b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*N_qWNldIBhEQv55q4BIeSQ@2x.jpeg</url>
            <title>Stories by Stefan van Oirschot on Medium</title>
            <link>https://medium.com/@stefanvanoirschot?source=rss-cd36008b9e7b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:34:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stefanvanoirschot/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[The evolution of (IT) managed services]]></title>
            <link>https://stefanvanoirschot.medium.com/the-evolution-of-it-managed-services-8df76d627f3d?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8df76d627f3d</guid>
            <category><![CDATA[managed-service-provider]]></category>
            <category><![CDATA[managed-it-services]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[sre]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Fri, 02 Jul 2021 06:35:12 GMT</pubDate>
            <atom:updated>2021-07-02T06:35:12.277Z</atom:updated>
            <content:encoded><![CDATA[<p>A managed service should focus on value being created by increasing the adoption of shareable resources that are not consumed in use, but instead gain value when they are used.</p><p>It’s all about making the entire ecosystem work. In the classic setup it is difficult to get anything done because of friction by processes slowing the system down and poor quality resulting in unhappy users and way too high support costs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HcpWuFHl3hf5-mUc" /></figure><p>In many organizations services that would benefit from being managed collaboratively in a scope[1,2] economy are actually being managed through a services provider, using processes primarily suited to prevent overconsumption.</p><p>Resources that require collaboration and continuous improvement, are hidden behind multiple approval and ticketing processes.</p><p>We believe that by identifying and shifting these resources out of these scale based governance, organizations can unleash the value, reduce the toil involved in accessing them and create a shared responsibility for continuous improvement.</p><h3>Introduction</h3><blockquote><em>“Managed services is the practice of outsourcing the responsibility for maintaining, and anticipating need for, a range of processes and functions in order to improve operations and cut expenses.”[3]</em></blockquote><blockquote>- Wikipedia</blockquote><p>The above definition leaves plenty of room for interpretation. Both the classic model of managed services as well as the modern model can fit the description. At the core, the success of the managed service should be measured by the success of the teams using the service. Looking at existing managed services from a user experience point of view immediately draws attention to some issues with the classical model.</p><p>Revisiting the definition, we look at the element of outsourcing the responsibility. We can look at outsourcing from a team point of view or from an organizational point of view. In this document we will focus on the organizational point of view first and flow into the team point of view, the internal platform, later. Successful organizations will adopt both. They will also adopt both in a modern setup.</p><h3>Classic managed services</h3><p>Classic managed services utilize cumbersome ticketing processes to support charging and they suffocate innovation through over-standardization. Outsourcing the responsibility for delivering a managed service to another organization often (still) results in this classic approach, where the main focus is the cost savings perspective while in the meantime providing its users with an inadequate as well as unsatisfactory experience. In the field, this is also referred to as a “take my mess for less”-deal.</p><p>Most outsourcing is done for cost reasons, optimization of budgets, reduction of headcount (as system integrators have many people shared across customers). The one thing where most outsourcing deals fail is evolution. Classic managed services are all about preserving what you take over from the customer with the normal improvements, but little to no evolution.</p><p>Most agreements do have what is called “innovation budget” and some text around platform evolution, but the reality is that it’s all about (only) improvements. Adding a big new service, development of such service in a complicated subsystem approach, would be a separate deal, which really doesn’t incentivize evolution. So outsourcing becomes more about preserving the status quo.</p><p>From the managed services party operational excellence is expected and parties agree on the desired service level through a strict SLA. Clauses for not meeting the SLA are embedded to prevent the delivering party from deviating from the agreement. As mentioned earlier, because of the setup of the agreement the incentive for the managed service provider is doing the same with less. “How can we deliver the bare minimum service, securing the service level, with minimum costs and effort?” So in fact, because of this model, the party delivering the service is incentivized to actually do less with less, including 0 (zero) innovation.</p><p>Because of this race-to-the-bottom setup, and strict SLAs with no responsibility for value delivery to the users of the service, two different economies emerge; the economy of scale and the economy of differentiation. These immediately start colliding. Classic managed services are set up as economies of scale, driving operational excellence, and protecting scarce resources from overconsumption instead of enabling a scope economy, and therefore value is wasted. Scope economies create efficiency by offering variety, meaning the support of the teams in the differentiation economy by providing them with relevant, valuable, reusable capabilities. Enablement of a scope economy accelerates the value creation of the economy of differentiation meaning the teams using the service who are working to accelerate the delivery of value for their customers.</p><p>Within the (traditional) economy of scale approach the mentioned protection is secured through a ticketing system and complex flows. While automation of workflows would actually support service providers to do less with less, often very little automation is implemented. This leads to many levels of manual intervention and approval steps, resulting in wait times and a degraded experience. This form of managed service does not operate with the user of the platform in mind. As we learned earlier, the success at the core of the platform should be measured as the success of the teams using the service.</p><p>Even worse; The platform slows down the speed of the teams operating on the platform. The production process slows down and innovation slows down.</p><p>Losing the connection between the users and the delivery of the service is dangerous and the service is at risk of becoming irrelevant very fast. Procedures like a request for change exist but often these are complex and time consuming, adding to the dissatisfaction of the users. All of the above occurs because of an over-focus on operational excellence and a lack of understanding of, and willingness to invest in the users of the service.</p><h3>Modern managed services</h3><p>Modern managed services are value-driven and operate using a relational agreement with the consuming party based on trust and transparency. They are designed with frictionless user experience in mind supporting the flow of the teams, allowing them to increase cadence and speed. A modern service enables teams to deliver work autonomously with self-service capabilities, in order to reduce extraneous cognitive load on the teams. These services are positioned to support the innovation excellence happening within the customer organization, meaning supporting the aforementioned economy of differentiation. Modern services, like their internal (to the organization) relatives, are to be operated as digital platforms.</p><blockquote>“<em>A digital platform is a foundation of self-service API’s, services, knowledge and support which are arranged as a compelling product.”[4]</em></blockquote><blockquote>- Evan Bottcher, 2018</blockquote><p>It’s critical that these digital platforms are led, architected, managed, developed and operated as products. New platform features flow through the same pipeline models as any other code or software release would. Managed service providers are expected to develop a balanced set of capabilities in the areas of leadership, architecture, product management, development and operations to effectively deliver an appealing product and adopt a way of working that supports continuous improvement. Through short and closed feedback loops the managed service team can execute continuous discovery as well as continuous delivery to maximize the experience of the teams using their service.</p><p>The amount of self-service functionality available on the platform is a key measure of platform maturity. The platform (the managed service) must provide services that do not require the teams using the managed service to raise support tickets. This will improve user experience by removing friction, allowing speed as well as the cadence to increase, and support flow.</p><blockquote><em>“Platforms must be designed with the user in mind [..] focus on UX and DevEx.”[5]</em></blockquote><blockquote>- Matthew Skelton, 2021</blockquote><p>Supporting the teams’ -using the platform- success is a core responsibility for the managed service provider. The managed service platform must support its users to achieve their goals by understanding needs and simplifying tasks.</p><blockquote><em>“The platform should not increase the cognitive load on teams using the platform.”[5]</em></blockquote><blockquote>- Matthew Skelton, 2021</blockquote><p>Combining the above we see a heavy focus on user experience. Frictionless, speed and flow are key. This means for users of the service to be able to focus on what is important: The creation of business value for the organisation by creating value for the end-customer. A managed service should be incredibly simple to use, any barrier for using the service should be removed, this will create the much needed “pull effect” of the platform service, making it appealing for teams to use.</p><h3>Modern platform management</h3><p>Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems. Balancing market agility meaning allowing the teams to go fast, and reliability meaning securing the stability and availability of the services is fundamental. Key with SRE when talking about how a service is led, architected, managed, developed and operated are the service level indicators, service level objectives and the resulting service level agreement accompanied by the error budget and relevant metrics for measuring business performance.</p><p>Modern platforms measure business performance using the following metrics:</p><ul><li>Product — These are the Accelerate[6] metrics related to balancing market agility and reliability.</li><li>Team/user satisfaction — Net Promoter Score, understanding what works</li><li>Adoption and engagement — % teams onboarded, platform services used</li><li>Reliability — Service level objectives, latency, # of incidents, etc.</li></ul><p>Service level indicators (SLI) are a defined measurement of an aspect of a service. For example availability, latency and throughput when thinking about user-facing systems.</p><p>The service level objectives (SLO) are a target or a range of values as measured by the SLI. The design of the SLOs are a team effort and thus a collaboration of the managed service provider, the teams using the service as well as the business for whom they develop their products.</p><p>The service level agreement (SLA) is a known construct. Being an explicit or implicit contract between the managed service provider and the organization or specifically the teams, with consequences of meeting or missing agreed objectives.</p><p>Finally there is the construct of the error budget. With the error budget one can determine the acceptable level of unreliability. Simply said; when there is budget left one can focus on increasing the number of features in the platform. When budget is exhausted or overspend features releases are frozen, post mortem items are prioritized and focus should be on improving monitoring and observability to enable a more proactive response and restore reliability.</p><h3>Your in-house supported platforms</h3><p>The aforementioned components are not only relevant for working with managed service providers. They are equally important for your internal organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*knIfDLOzB-DmZ0Jq" /><figcaption>Team Topologies visualisation of an internal platform utilising a managed services platform</figcaption></figure><p>In the figure above the mentioned internal platform builds on top of the services provided by the managed service provider. This (internal) platform is the smallest set of API’s, documentation, and tools needed to accelerate teams. It extends the value delivered by the managed service by adding organization specific value added services for example a policy-driven automation pipeline providing trust through the enforced sequence of required activities/steps involved in the development and deployment process. And for example transitioning services supporting teams to get onboarded to the platform with as little friction as possible.</p><p>The platform enablement team in the example operates in a facilitating mode for the stream-aligned/product teams enabling them to effectively use all the capabilities of the platform. Enabling teams proactively seek to understand the needs of the product teams using the service. They stay ahead of the curve regarding approaches, tools and practices in their area of expertise. Besides this they have a key learning function, promoting learning across teams. Enabling teams support flow of product teams, removing friction as much as possible and allowing for the increase of speed as well as cadence by supporting them to continuously improve their way of working.</p><p>Ownership of these internal platforms is, as the name already states, internally. They can of course be staffed through combinations of associates and partner-staff. These internal platforms adhere to all the concepts of the modern managed service as mentioned before.</p><h3>Conclusion</h3><p>“<em>Managed services is the practice of outsourcing the responsibility for maintaining, and anticipating need for, a range of processes and functions in order to improve operations and cut expenses.</em>” Revisiting the definition we see that, while still important, a shift has happened from only focussing on cutting expenses to an emphasis on anticipating need and improving operations.</p><p>Traditional outsourcing deal economics are not made for the new world. Reconsidering the paradigm is mandatory and a shift is happening. Main focus of any party delivering a service should be the success of the teams using the service. When working with other organizations this means finding ways to create a win-win situation. A setup where both parties gain from adding more relevance.</p><p>A great way to set up such an agreement is a formal relational contract[7]. This type of contract is used to govern highly complex relationships that demand collaboration and flexibility. Building on top of a foundation of trust, joint vision and goals, and shared understanding of the guiding principles the terms &amp; conditions are defined and governance mechanisms established.</p><p>Adopting modern platforms means taking a holistic approach when looking at the organization and your value streams. What do you develop yourself and what do you outsource? How do you optimize variation to maximize differentiation? And when applying outsourcing, how do you make sure you and your service provider(s) collaborate on your journey for joint-success?</p><h3>Notes</h3><p>[1] The 3 economies — <a href="http://blog.jabebloom.com/2020/03/04/the-three-economies-an-introduction/">http://blog.jabebloom.com/2020/03/04/the-three-economies-an-introduction/</a></p><p>[2] <a href="https://en.wikipedia.org/wiki/Economies_of_scope">https://en.wikipedia.org/wiki/Economies_of_scope</a></p><p>[3] <a href="https://en.wikipedia.org/wiki/Managed_services">https://en.wikipedia.org/wiki/Managed_services</a></p><p>[4] <a href="https://martinfowler.com/articles/talk-about-platforms.html">https://martinfowler.com/articles/talk-about-platforms.html</a></p><p>[5] <a href="https://www.slideshare.net/matthewskelton/what-is-platform-as-a-product-clues-from-team-topologies-wtfinar-with-container-solutions-2nd-edition">https://www.slideshare.net/matthewskelton/what-is-platform-as-a-product-clues-from-team-topologies-wtfinar-with-container-solutions-2nd-edition</a></p><p>[6] Accelerate, Nicole Forsgren, PhD</p><p>[7] A new approach to contracts, Oliver Hart — <a href="https://hbr.org/2019/09/a-new-approach-to-contracts">https://hbr.org/2019/09/a-new-approach-to-contracts</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8df76d627f3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Distributed trust with blockchain]]></title>
            <link>https://stefanvanoirschot.medium.com/distributed-trust-with-blockchain-14bc64710132?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/14bc64710132</guid>
            <category><![CDATA[ledger]]></category>
            <category><![CDATA[digital-leadership]]></category>
            <category><![CDATA[lto-network]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Mon, 19 Apr 2021 16:53:46 GMT</pubDate>
            <atom:updated>2021-04-19T16:53:46.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Blbucp0EplQ3JpxR6dUnig.jpeg" /></figure><p>A blockchain is a distributed, replicated peer-to-peer network of databases that allows multiple, untrusted parties to make transactions without the intervention of a trusted third party and ensures an unalterable storage of the data over time.</p><p>Blockchain is one of the most hyped innovations in recent years. The rise and popularity of cryptocurrencies have contributed significantly to this. Blockchain with its core properties of distributed trust and immutability has the potential to revolutionise current litigation. However, as with many new innovations, it takes several moments of hype and reflection before a technology comes to fruition.</p><p>In order to enable broad adoption of the technology, it is necessary to abstract away the complexity for the users / software developers and at the same time make the functionality easily available. In this way, we lower the barrier to adoption of this technology.</p><p>Knowledge of how a blockchain works is not necessary for the use of this technology. However, being familiar with the properties of a blockchain and why they are relevant to business operations is essential.</p><p>This chapter about blockchain starts with an explanation of the properties of blockchain and then goes in-depth into how the technology works. After this in-depth study, we look at concrete usage examples and the application within the software development world.</p><h3>Properties</h3><p>A blockchain has the following properties.</p><h3>Distributed Trust</h3><p>Organisations that want to work together, but do not trust each other completely, can set up a private blockchain and invite business partners to record their transactions in a shared distributed ledger. Private blockchains can track assets through transactions they represent on the blockchain. They also share other features with public blockchains, such as a distributed, resilient, and redundant data storage system. A private blockchain implies a degree of trust between the members of a consortium, but no entity controls the storage and validation of transactions.</p><p>Combinations of private blockchain technology with public blockchains are also possible. Such a hybrid solution can leverage the strengths of both types of blockchains. Consider, for example, recording complete documents on a closed blockchain section, which are only accessible to the parties involved. However, the security features of these documents are stored in the public part, so that the information is stored more distributed and the risk of unwanted adjustments is much smaller.</p><h3>Immutable</h3><p>Once a transaction has been added to a blockchain, it can no longer be deleted or changed without the change being made transparent. It’s easy to see why tamper-resistant records are useful in many applications, but this feature also means that there is no direct way to delete or change previous records, even for legitimate or regulatory purposes.</p><h3>Consensus</h3><p>Consensus Mechanisms allow all affiliates to agree on the state of the system. That is, to prevent fraud or double expenditure without the need for a central authority.</p><blockquote><em>“[Blockchain] provides a historical record that everyone in the network agrees to, it provides provenance — complete data integrity.” — Stewart Bond, IDC</em></blockquote><p>Different consensus mechanisms have different trade-offs in terms of speed, scalability, energy consumption (might lead to environmental impact) and time to final capture.</p><h3>How the technology works</h3><p>A blockchain is literally a chain of blocks. The blocks in the blockchain contain the data from the blockchain. This encrypted data on the blockchain is stored on all systems, the so-called nodes, that are part of this blockchain network. This ensures <strong>decentralisation</strong> and <strong>distribution of data</strong> and together they also ensure <strong>consensus</strong> about what is correct and what is not.</p><p>Blocks in the blockchain are linked to each other via <strong>hashes</strong>. Such a hash is a letter and number representation of the content of a block.</p><p>The hash of the content of, for example, block 1 is included as part of the data in block 2. In addition, block 2 has its own data. For block 3, a hash is made of the entire content of block 2, including the hash of block 1 and stored in block 3 etc.</p><p>Here we immediately grasp an important property of the blockchain: its immutability. Short explanation: a change in the content of, say, block 1 of our example would mean that the hash over the content of the block changes. After all, the content is different. This means that, because we used this hash again in block 2, the hash that block 3 was started with is also invalid. Tampering with a blockchain is therefore immediately noticed and the system that makes the error is excluded until it has corrected the error.</p><p>The fact that we have distributed the data across many systems, and stored it securely and unalterably, means that we no longer need an intermediary to validate the transactions. The blockchain fulfils the role of intermediary here.</p><h3>Prevent fraud</h3><p>The world is built on trust. Unfortunately, confidence is often lacking. An example of a Dutch organisation that uses technology to gain more control is NEN.</p><p>NEN is a standards organisation. Until recently, a central storage facility was used for certifications. NEN is switching from this central storage to a blockchain to be able to guarantee the authenticity of a certificate. After all, if something is stored on the blockchain, it cannot be changed.</p><p>This is, of course, just a start. Because we have the option of storing data reliably and unchangeably, many opportunities arise for the rest of the chain. All measuring points in the chain could be registered, deviations are quickly identified and fully traceable to the source.</p><blockquote><em>“The FBI claims there are 3,300 unrecognised universities worldwide, many of which at all levels sell degrees to anyone willing to pay the price, and that more than 50,000 PhDs are bought annually from diploma factories — slightly more than are legitimately earned. The fact that fake medical degrees appear to be extremely readily available clearly indicates that there are security concerns.” — A Rising Tide of Bogus Degrees, New York Times</em></blockquote><p>Blockchain Technology can prevent this fraud because you no longer have to prove whether something is true or not due to the solid storage of data in the blockchain. Better to prevent than to cure!</p><h3>In practice</h3><p>But how are we actually going to use this blockchain technology? Blockchain is an interesting tool in the software developer’s toolbox. It is important to understand that it is only one instrument in a set of many. The central database, just to name an example, is also part of this toolbox. It is essential to always choose the right ingredients so that the most effective solution is developed in the context of realising IT and business objectives.</p><p>More and more we will see that suppliers of blockchain technology will offer their platform — directly or indirectly through a partner channel — as a service. An easily accessible entry-level where substantive knowledge of the technology is not required to reap its benefits. The use of open source software and technology within this service ensures essential transparency and thus confidence for the recipient of the service and users of the technology.</p><p>The system integrator parties (SIs) of the world will work with their customers to see what role blockchain can play in realising the customer’s objectives. Again, blockchain is just one tool in the great toolbox used to support the customer’s journey to digital leadership.</p><p>Independent Software Vendors (ISVs), companies that develop software, will rethink whether their service or their software will become smarter, more effective, more customer-friendly by applying blockchain technology. Easy access to a blockchain platform is essential for these companies. These parties want to focus on their unfair advantage and their added value. This means adding value to the solution that can be directly experienced by the user of the solution.</p><p>To get these integrators and software development companies enthusiastic about the blockchain platform, it is essential to reach the developer. Winning the developer’s heart and mind means investing in communities:</p><ul><li>Why this blockchain platform?</li><li>How can I easily use the platform?</li><li>Does the platform have the functionality I need?</li><li>How can I use my current knowledge and skills?</li><li>As a developer, how can I influence the development of the platform?</li><li>And of course many more questions.</li></ul><p>It is essential for success to bind software developers to your platform.</p><h3>LTO Network</h3><p>A concrete example of a company that offers blockchain technology as a platform and has developed a huge community around it is LTO Network. This Dutch organisation has developed a hybrid blockchain solution for companies. With this solution, you don’t have to throw everything you do and work with overboard. It is a security layer for existing processes, systems, currencies, automations and relationships.</p><p>Two examples of the utilisation of the properties of blockchain technology by LTO Network:</p><ol><li>Proof-of-Existence: Integration into existing systems and applications to secure any type of data. Think of the software developers as described above.</li><li>Decentralised Workflows: Use blockchain technology to connect silos within and between companies for process optimisation between parties.</li></ol><p>By abstracting the underlying blockchain technology away from the users / software developers and at the same time making the functionality easily available, they lower the adoption threshold of the technology.</p><p>The aforementioned (fraud) examples would have benefited enormously from the implementation of such a solution.</p><h3>Conclusion</h3><p>A blockchain is certainly not a silver bullet, but a technology, an instrument if you like, that can be used to provide technical details for the realisation of IT objectives and thus contribute to the growth of the company.</p><p>In the coming years we will be able to gain more and more accessible access to blockchain platforms to enrich our software solutions, where necessary, in order to be more successful as an organisation with more satisfied users.</p><p>What role can blockchain play in your services to make them more efficient, more effective, smarter and more customer-friendly?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14bc64710132" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Balancing forces: Translating efficiency between differentiation and scale]]></title>
            <link>https://stefanvanoirschot.medium.com/balancing-forces-translating-efficiency-between-differentiation-and-scale-be99a177de22?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/be99a177de22</guid>
            <category><![CDATA[wall-of-confusion]]></category>
            <category><![CDATA[gto]]></category>
            <category><![CDATA[open-transformation]]></category>
            <category><![CDATA[5elements]]></category>
            <category><![CDATA[3-economies]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Thu, 19 Nov 2020 12:02:03 GMT</pubDate>
            <atom:updated>2020-12-02T10:41:52.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Balancing forces: Translating efficiency between differentiation and scale" src="https://cdn-images-1.medium.com/max/960/1*PwQDpjGhVn3BZRBnupWXig.png" /></figure><p><em>This is the written version (with some additions) of my presentation I delivered at the IDC Multi Cloud event on November 19, 2020. A recording of the session is available </em><a href="https://youtu.be/I1V0HtgD3Os"><em>here </em></a><em>on YouTube (Apologize for fiddling with the mic during the session):</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FI1V0HtgD3Os%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DI1V0HtgD3Os&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FI1V0HtgD3Os%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0086811822d9070ea05dce4328c09010/href">https://medium.com/media/0086811822d9070ea05dce4328c09010/href</a></iframe><p><em>Please let me know your thoughts, questions, feedback, remarks, etc. in the comments. This is very much appreciated!</em></p><figure><img alt="Focus is often too much in the area of just technology. A change in behaviors throughout the organization should be aspired." src="https://cdn-images-1.medium.com/max/960/1*XByR8gwAEL06A0m4-kyjJA.png" /></figure><p>Focus is often way too much in the area of just technology. A change in behaviours throughout the organisation should be aspired meaning a change in the area of people, process as well as technology.</p><figure><img alt="To measure is to know!" src="https://cdn-images-1.medium.com/max/960/1*mnxA3p0H-L-_005lgT_f8A.png" /></figure><p>To measure is to know and it all starts with having the right metrics…</p><figure><img alt="Metrics should inform work practices, practices create culture, and a generative culture unlocks transformation." src="https://cdn-images-1.medium.com/max/960/1*nV0YjFS3PZxTKSrHD1sVeA.png" /></figure><p>Metrics should inform work practices. Otherwise, how do you know you’re working on the right thing?</p><p>Executives can’t mandate cultural change. Practices create culture.</p><p>As organisations, we are what we do!</p><p>Culture is the missing piece for countless failed transformation efforts.</p><p>A generative culture unlocks transformation, keeps you on top of market disruption, and leads to higher levels of business performance.</p><p><strong>My name is Stefan van Oirschot and as Chief Digital Advisor at Red Hat I’m a strategic advisor and sparring partner for CIO’s and CTO’s.</strong></p><figure><img alt="Meaningful change can never be accomplished unilaterally — Jabe Bloom, Red Hat" src="https://cdn-images-1.medium.com/max/960/1*9cTyYiMFXPGraX0zrzoi8Q.png" /></figure><p>One of the most difficult parts of transformation is resistance to change but where is that resistance coming from?</p><p>Meaningful change is difficult because it can never be one-sided. Transformation is not a solo operation performed by a single person on their own.</p><p>Instead change causes friction between people and teams as they realise there are new technologies and new ways of working.</p><figure><img alt="Introducing the economies of differentiation and scale at play in your organization." src="https://cdn-images-1.medium.com/max/960/1*XqK0VBIobiQkaZLAdK8MPg.png" /></figure><p>I want to start by introducing the economies at play in your organisation.</p><p>On the one hand we have the economy of differentiation focussing on the accelerated differentiation and the creation of value.</p><p>On the other hand we have the economy of scale focussing on operational excellence and efficiency.</p><p>Both economies have different ways of creating value.</p><figure><img alt="The two governing theories; speed without safety versus safety without speed." src="https://cdn-images-1.medium.com/max/960/1*MhgqQdHpFOSAANS4cuhbCQ.png" /></figure><p>In the differentiation economy we focus on innovation excellence.</p><p>Flexibility is paramount, new markets are prioritised and one offs are considered most important.</p><p>In the scale economy we consider standardisation above all, focus on established markets, and consider repeatable processes as critically important.</p><p>Speed without safety versus safety without speed, two governing theories.</p><figure><img alt="Squeezing the tube; removing variations and focussing on your unfair advantage." src="https://cdn-images-1.medium.com/max/960/1*wAtmnNN_SnowdcSyynBXGg.png" /></figure><p>Are you consider removing variation?</p><p>Your competition is definitely considering working smarter by lowering complexity.</p><p>Working smarter gives you more time to focus on your unfair advantage and increase the number of strategies you can execute.</p><p>What is your unfair advantage?</p><figure><img alt="A revisit of the wall of confusion, a result of the core conflict between the differentiation and scale economy." src="https://cdn-images-1.medium.com/max/960/1*u_8HNAhUq3Nd-v9n5TFWqw.png" /></figure><p>Your unfair advantage is not only in the economy of differentiation. It’s actually to make the entire ecosystem work!</p><p>As already pointed out by my colleague Andrew Clay Shafer back in 2008 a frequent result of this core conflict is the creation of a wall of confusion.</p><p>Communication between developers and operators is limited to a ticketing system. The system is slow and there are many silos that are leading to multiple dependencies.</p><p>It’s difficult to get anything done because of friction by processes slowing the system down. Poor quality resulting in unhappy customers and too high support costs.</p><p>Low engagement by employees eventually resulting in higher levels of absenteeism and even people burning out because of the inability of seeing value being created by their work.</p><p>The empathy and understanding that arises from working with each other on shared problems is lost and results in a confusion of balance.</p><p>Problems are simply thrown over the wall.</p><figure><img alt="The confusion is not understanding the other game. …and not understanding the connection — Jabe Bloom, Red Hat" src="https://cdn-images-1.medium.com/max/960/1*Wv2dEDA5N-tWEBtDx6ZgRA.png" /></figure><p>This isn’t the only source of confusion. Each side of the wall of confusion fails to understand how the other side creates value.</p><p>They do not understand the other side’s way to “win”.</p><p>It is important to understand how these 2 sides are connected to understand how both sides can win.</p><p>Shared understanding is critical, without it both sides resort to attempts to optimise for their own concerns.</p><p>These local optimisations don’t result in efficient or effective systems. Instead they create friction, misunderstanding, confusion, hand offs and knowledge gaps.</p><p>The trick is to look at the system through a third economic logic.</p><figure><img alt="The 3rd economic logic, introduction of the scope economy and introduction of the value of reusability of shared resources." src="https://cdn-images-1.medium.com/max/960/1*EZvXQNgLzsVFlkoENKOyOA.png" /></figure><p>This 3rd economy is the scope economy.</p><p>Value is created by increasing the adoption of shareable resources that are not consumed in use.</p><p>A shared resource which is not consumed in use but instead gains value when it is used.</p><p>Examples of these types of resources include shared data, functions, and cloud native patterns.</p><figure><img alt="Recommoning, the practice of increasing value of resources by making them widely available and easily accessible." src="https://cdn-images-1.medium.com/max/960/1*Hk5Wup1ZdRm9V_OVCA11FQ.png" /></figure><p>The implication is that some resources currently being managed in differentiation would be more valuable being managed in the scope economy.</p><p>As an example think of product teams distracted from their customer focus attempting to manage shared resources used by other teams in the organisation.</p><p>Instead we want to observe when resources initially developed by product teams mature, and cross team demand emerges and then shift these resources into a scope economy.</p><p>On the other hand in many organisations services that would benefit from being managed collaboratively in a scope economy are actually being managed by processes primarily suited to prevent overconsumption.</p><p>By identifying and shifting these resources out of scale based governance, organisations can unleash the value, reduce the toil and create a shared responsibility for continuous improvement.</p><figure><img alt="An example of data where recommoning offers reusability and value increases through shared use." src="https://cdn-images-1.medium.com/max/960/1*7vi1elTU7qsx1dGumSGXaw.png" /></figure><p>Organisations often sub optimally manage these shared resources.</p><p>In the scope economy attempts to limit consumption do not preserve value. Instead they increase friction, reduce adoption and destroy value!</p><p>Think about your data. When more teams have access to the same data does that data get used up?</p><p>No, the data instead becomes more and more valuable to both your teams and for customers.</p><p>In scope adaptability is paramount. Repeatable change is most important and an innovative culture provides our advantage.</p><figure><img alt="Giving people insights into how their work delivers value for the business, results in lower levels of absenteeism." src="https://cdn-images-1.medium.com/max/960/1*HABI0RAJXBCCx485BbcgpQ.png" /></figure><p>We want to move away from pushing tickets and confusing policy walls to recommoning of resources into a shared platform. This results in a platform that acts as an interface between differentiation and scale economies.</p><p>The platform decouples the market driven cycle times from each other, enabling developers and operators to act in ways that are timely and allow for maximum impact.</p><p>When these 3 economies begin working together in harmony the mentioned core conflict dissipates and friction in the organisation is reduced.</p><p>Furthermore; giving people insights into how their work delivers value for the business, results in lower absenteeism and a smaller chance of people burning out.</p><figure><img alt="Introduction of the 5 elements; failures as well as opportunities." src="https://cdn-images-1.medium.com/max/960/1*_aTgWEQqLc15IddOiVGaOQ.png" /></figure><p>Essential to transformation is the understanding of the 5 elements.</p><p>Let’s start by introducing them and identify the 5 failures as well as the 5 opportunities!</p><p>Leadership prevents change instead of enabling peer level conversations and setting direction with ambition.</p><p>Product management building things that customers do not value. Time which would be better spent working with teams to create strategies for creating differentiated value.</p><p>Development building the wrong things, doing unnecessary rework and having long feedback loops instead of high quality execution.</p><p>Architecture artificially constraining the organisation by focussing on old processes, old ways of thinking, and an inability to leverage new technologies. Instead architecture has an opportunity to focus on accelerating product development and ensuring long term quality by creating enterprise wide patterns and frameworks.</p><p>And finally operations, moving away from just putting out fires, and focussing on incidents and outages, to establishing a foundation of resilience.</p><figure><img alt="Balancing the elements across the 2 dimensions; change&lt;-&gt;stability and tactical&lt;-&gt;strategic." src="https://cdn-images-1.medium.com/max/960/1*kGc_Yrcf7wbLuAbUTPg-sw.png" /></figure><p>The 5 elements can be balanced across 2 dimensions.</p><p>The first dimension we discussed earlier as well as the effect of investing in variety where it creates the most value and creates an efficient and effective system.</p><p>The second dimension is the timespan from tactical to strategic where tactical concerns need to be balanced against the strategic efforts.</p><p>Over focus on individual capabilities will create an organisational mis-balance between these dimensions.</p><p>Locally optimising the system for development and the organisation ends up tipping towards the upper left being too much focused on rapid, short term change and therefore sacrificing long term stability and options.</p><figure><img alt="Elements are not roles, they are capabilities." src="https://cdn-images-1.medium.com/max/960/1*6X00MR12SOx25BZlXFB8qQ.png" /></figure><p>Elements are not roles, they are capabilities.</p><p>Within an organisation, an organisational unit, for example a department, a team, all these elements should be in place.</p><p>The elements should be in balance &amp; interacting to reinforce each other!</p><figure><img alt="Create the conditions that make transformation inevitable. — Jabe Bloom, Red Hat" src="https://cdn-images-1.medium.com/max/960/1*0YYNSfryAA_R4joFrDDSFg.png" /></figure><p>Transformation requires leadership at all levels to continuously balance investment across each of these capabilities.</p><p>Establishing a balance across the economies creates the conditions for transformation while enabling both efficiency and innovation.</p><p>Organisations that begin to see the results of this balance begin to grasp the potential of transformation at the organisational level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9Tase0Epj06Rk4HxgoQxcA.png" /></figure><p>Interested to hear more? Feel free to reach out and let’s discuss in more detail!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*4p1jbf_ueifojVMwAPMwCg.png" /></figure><p>Thank you very much for your time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be99a177de22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anna and La Pendule: 4 ingredients that helped her business win]]></title>
            <link>https://stefanvanoirschot.medium.com/anna-and-la-pendule-4-ingredients-that-helped-her-business-win-e7fdf749cdc7?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7fdf749cdc7</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[open-organization]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Tue, 03 Nov 2020 13:02:54 GMT</pubDate>
            <atom:updated>2020-11-03T13:02:54.859Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2janCFJvQGO8d1Md" /></figure><p><em>This is the written version (with some additions) of my presentation I delivered at the virtual Red Hat Forum on November 3, 2020. A recording of the session can be found </em><a href="https://youtu.be/G2vsRGpb3PA"><em>here</em></a><em> on YouTube. Please let me know your thoughts, questions, feedback, remarks, etc. in the comments. This is very much appreciated!</em></p><p>Welcome and thank you for investing your time to learn more about Anna and her restaurant La Pendule.</p><p>My name is Stefan van Oirschot and in my role as Chief Digital Advisor at Red Hat I’m a strategic advisor and sparring partner for CTO’s and CIO’s.</p><p>Being in IT for over 17 years, and working with Red Hat products for over 20 years, I have been involved in building, architecting and advocating for customers of all sizes. My background is computer science and during my professional career I have been in different roles varying from Solution Architect to CTO.</p><p>Before joining Red hat I was working for a Red Hat business partner and looking professionally at Red Hat’s Kubernetes distribution OpenShift, it was quickly clear that this was meant to be huge and a fundamental ingredient for awesome solutions. But wait, this post is not about products. It’s about combining people, processes and technology to unlock transformation and customer relevance!</p><p>Please allow me to share a little bit more about my past experience though. Back then, talking to customers, other professionals and colleagues more insights were found and a quick business plan built. For what? It was an early version of our company’s OpenShift-based service. Back in 2016, it provided a small suite of dev tools which could be easily deployed through self-service. Combined with our in-house managed services (SRE), training, onboarding services, and more, we knew we had the right ingredients for a developer-friendly container and microservices platform.</p><p>In 2017 I had the amazing opportunity to join Red Hat (Good to know that being part of Red Hat had long been my dream) and since then I’ve been able to use my experience of building platforms, and strong focus on user experience, in my customer conversations and breaking down the wall of confusing using the platform as an interface.</p><p>Today you will read about capabilities of a modern (software) organization, how they can be adopted, and how they relieve the users and help them become more effective, more motivated and more happy.</p><p>A metaphor of a restaurant is for illustration. The persona’s, challenges, observations and ideas in the story are very much relevant to the IT enterprises. Please let me know what you think of the mapping and what you recognize from your own organization!</p><p>Lets meet Anna!</p><figure><img alt="Meet Anna &amp; La Pendule" src="https://cdn-images-1.medium.com/max/1024/0*r-49bqU4AQOOqlUK" /></figure><p>Anna, 29 years young, comes from a long line of restaurateurs and chefs.</p><p>Founded back in 1782, La Pendule is located in the center of Paris, and has always been one of the finest restaurants in the city.</p><p>She has been told that La Pendule combines all the four essentials of an elegant room, smart waiters, a choice cellar, and superior cooking, and that this award-winning establishment has been a top ranking restaurant for years!</p><p>What could possibly go wrong…?! :)</p><figure><img alt="The start of a new adventure…" src="https://cdn-images-1.medium.com/max/1024/0*CuYcyPW0ZAO_4ijG" /></figure><p>Finally!</p><p>Today is the first day of a new adventure for Anna. She takes over the restaurant from her uncle who has been a restaurateur of La Pendule for 40 years.</p><p>Looking forward to making this a success Anna arrives at the restaurant at 8 am to meet with the team.</p><p>Annabelle the Chef at La Pendule introduces the rest of the team:</p><p>“Meet Charlie the Kitchen Manager, Monique the Head Cook and Melvin the Head Server” she says.</p><p>Anna learns that the 5 of them together make up the leadership team of La Pendule.</p><p>After a quick introduction she proposes to sit down to get better acquainted.</p><figure><img alt="Something is cooking…" src="https://cdn-images-1.medium.com/max/1024/0*ieIjBiomNkxuIHhS" /></figure><p>Even though Anna has been visiting La Pendule for all her life she is very much surprised about the formal atmosphere and the lack of ownership within her team.</p><p>Being just a few hours into her new venture Anna already has quite a list of worrying observations!</p><p>How can we serve all these tables with quality foods and drinks with such a small and unequipped kitchen?</p><p>And what about these kitchen tools, not sure if any new employees would actually be able to use these.</p><p>The serving team does not seem to be talking to the kitchen people and vice versa.</p><p>And next to all of this the automated supply of fresh ingredients seems to be non-existing,</p><p>To top it off La Pendule is not connected to any form of social platform and absenteeism seems to be way above market average!</p><p>Anna really is clueless to the fact that this place has been successful for so long.</p><figure><img alt="Superficial approaches don’t create lasting change." src="https://cdn-images-1.medium.com/max/1024/0*bL1vZHFM7xpwtDqW" /></figure><p>Talking to her team she quickly learns that things haven’t been going smoothly for quite some time… What did she run into!</p><p>There have been attempts to turn the ship around she learns.</p><p>An initial approach by her predecessor consisted of special rules, isolation, and incentives. But of course these only created temporary success. Unfortunately this success was not repeatable for business-as-usual.</p><p>She knew she would need to step up her game and that the clock was ticking…</p><figure><img alt="La Pendule’s 5 failures" src="https://cdn-images-1.medium.com/max/1024/0*bBKrOumC_Je-G9G2" /></figure><p>Introducing the 5 elements we can identify what is going wrong at La Pendule:</p><p>From an overall lack of vision from general management to inefficient and ineffective processes in kitchen management.</p><p>Furthermore they come up with products that nobody wants and on top of that they cook things wrong and cook the wrong things.</p><p>Having identified these failures let’s start putting together a plan to turn the kitchen around.</p><figure><img alt="“To measure is to know.”" src="https://cdn-images-1.medium.com/max/1024/0*SmpADWvwMxX-aeIA" /></figure><p>To measure is to know. It all starts with having the right metrics…</p><figure><img alt="Metrics should inform work practices." src="https://cdn-images-1.medium.com/max/1024/0*pVXL_5Z8_Rdg6yT9" /></figure><p>Metrics <strong>should</strong> inform work practices. Otherwise, how do you know you’re working on the right thing?</p><p>Executives can’t mandate cultural change. Practices create culture. As organizations, we are what we do.</p><p>Culture is the missing piece for countless failed transformation efforts.</p><p>We believe that culture is built through action &amp; behavior and “good culture” results from organizational transparency on goals and intended outcomes so basically, by focusing on these metrics, we will intrinsically be building culture.</p><p>A generative culture unlocks transformation, keeps you on top of market disruption, and leads to higher levels of business/mission performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tlxGGHX6lKIKcnTE" /></figure><p>Let’s revisit the 5 elements again and review them from an opportunity perspective.</p><p>Applying what the team just learned that “good culture results from organizational transparency on goals and intended outcomes” Anna confirms that direction &amp; ambition is essential.</p><p>The team revisits the other elements as well and stresses that they want to build the right things, the right way and make doing the right thing easy.</p><figure><img alt="Understanding the balance or often imbalance between the 5 elements." src="https://cdn-images-1.medium.com/max/1024/0*llIhxYW4hveRwP1v" /></figure><p>The focus areas of the individual elements differ meaning their fundamental priorities will differ.</p><p>Cooks and Chefs want to be innovative and focus on change while Kitchen Management wants to provide them with a stable set of processes and securing safety and working according to regulations.</p><p>The elements also have a different focus where it comes to short term and longer term.</p><figure><img alt="Elements are not roles, they are capabilities" src="https://cdn-images-1.medium.com/max/1024/0*r-gxMAX9mrGQAngX" /></figure><p>Multi-disciplinary teams adopt the 5 elements as capabilities. Elements are not roles and are not an individual’s responsibility but a team effort.</p><p>Within an organization or even an organizational unit, for example a department or a team, all these elements should be in place. They should be in balance &amp; interacting to reinforce each other!</p><figure><img alt="The 5 elements dynamic, an example" src="https://cdn-images-1.medium.com/max/1024/0*W4Yn1EzEWbKycgzG" /></figure><p>Let me give an example of the dynamic between the 5 elements and the customer:</p><p>The customer provides feedback about a dish, a serving, a beverage, the ambience which is input for the product team and, or the chef.</p><p>The chef builds an hypothesis for improving for example the menu.</p><p>The cooks and sommelier work with the hypothesis and find a way to deliver.</p><p>The Kitchen supports the production of the dish or beverage and the waiters serve the customer.</p><p>Guidelines are in place to make sure that everything happens the right way.</p><p>The leadership team and general management by Anna makes sure that everything they do is inline with their core values and helps them achieve their goals.</p><p>All the people in the team together cover the capabilities of the 5 elements, together making up the product, the service, providing the ultimate customer experience.</p><figure><img alt="The research done by Anna" src="https://cdn-images-1.medium.com/max/1024/0*_-bJsseY9HYD22tn" /></figure><p>What did she find in her research…</p><figure><img alt="Anna identifies 2 economies currently at play within her restaurant" src="https://cdn-images-1.medium.com/max/1024/0*4lkwZhd1dde0wlQF" /></figure><p>Anna identifies that there are 2 economies at play in her restaurant.</p><p>The economy of differentiation with a focus on accelerated differentiation and the creation of value. This is mostly owned by the restaurant’s guests but also by the Chef, for example with his work of coming up with new dishes.</p><p>On the other end you have the economy of scale, mostly led by Kitchen Management but also by the serving staff. They focus on operational excellence and efficiency.</p><figure><img alt="The 2 economies are actually two governing theories." src="https://cdn-images-1.medium.com/max/1024/0*N_Wm5F7K8rz6Yz2b" /></figure><p>Anna quickly notices that these 2 economies are actually governing theories.</p><p>On the one hand we focus on speed without safety; focusing on new opportunities, new markets, doing things differently and probably have lots of changes.</p><p>The economy of scale wants to make sure all is safe but this seems to be coming at the cost of speed. They focus on the good and best practices, making everything resilient and standardizing as much as possible.</p><figure><img alt="No compromise; we want to delight our customers" src="https://cdn-images-1.medium.com/max/1024/0*pcN-jPxGXnSi5wrT" /></figure><p>Anna and her team conclude that they do not want to compromise and that to be able to delight their guests they need to find a way to bring the worlds together, a 3rd economy; the economy of scope.</p><p>Doing online research she reads about constraints that enable innovation. The team agrees that they want to strike a balance between freedom &amp; flexibility on the one end and standardization, safety and compliance on the other. The recommoning of resources and services.</p><figure><img alt="The platform is the clutch that connects the 2 economies" src="https://cdn-images-1.medium.com/max/1024/0*bbbNNvfhm9qp_y0s" /></figure><p>The platform sits in the 3rd economy and acts as the clutch that connects the 2 economies.</p><p>The platform economy, the producers and the consumers on the platform, supported by the platform services make up the ecosystem where value of resources increases the more they are being consumed.</p><p>La Pendule should become a modern platform supporting a self-sustaining platform economy consisting of producers and consumers. New communication channels and ways to consume services are enabled here.</p><p>Suppliers deliver the predictable service to the platform. For example the fresh and quality ingredients. We use suppliers for example to eliminate redundancy.</p><p>Engineering means focusing on your true value add, your unfair advantage. So the build part in the build versus buy decision. In the case of La Pendule these are the services Anna and her team are delivering and supporting through the platform.</p><figure><img alt="Confusion as an Interface" src="https://cdn-images-1.medium.com/max/1024/0*nkDG4wBY7trxtPZ1" /></figure><p>But what about the current situation?</p><p>Currently there seem to be unsupportive processes in place and an inflexible infrastructure provided by kitchen management.</p><p>The supply chain of ingredients is definitely not efficient and the quality of ingredients is not up to standard.</p><p>Next to that the cooks do not have the right materials to do their work.</p><p>The products the cooks deliver are not according to the specifications thought out by the Chef but also are not according to customer demand adding to the frustration of the serving staff.</p><p>And on top of all of this the cooks preparing the food have no way of seeing the end-result.</p><figure><img alt="Platform as an Interface offering continuous compliance" src="https://cdn-images-1.medium.com/max/1024/0*h0RpaHPtqFCPncye" /></figure><p>Going forward, anchoring the foundation in a platform as an interface we immediately can see benefits.</p><p>Giving the Cooks insights into how their work delivers value for the business by delighting customers results in lower absenteeism and a smaller chance of people burning out.</p><p>Kitchen Management delivers an optimized workbench, providing the required tools and allows the cooks greater accessibility making them more effective.</p><p>The quality assurance processes as well as the safety procedures have been optimized, fully automated and incorporated as part of a trusted supply chain allowing for continuous assembly to order as well as continuous compliance.</p><figure><img alt="Anna’s trusted (software) supply chain" src="https://cdn-images-1.medium.com/max/1024/0*gmeQo90g-7Bz1YWg" /></figure><p>Anna and her team discovered a new way of delivering value to their customers.</p><p>Through her trusted supply chain she is able to excel in the area of customer intimacy as well as operational excellence.</p><p>The product staff embraced new methods in requirements gathering and design. Some of the practices they adopted are; behavior driven development, event storming, and priority sliders.</p><p>The kitchen personnel develops against these, using trusted quality ingredients as a baseline.</p><p>On committing a dish, it will always go through various stages in their workflow: For example automating quality, being able to provide a body of evidence to people in the loop.</p><p>But also authorizing the dish to go out and back to the team, rechecking the requirements backlog. This to ensure constant traceability.</p><p>Serving to the customer, the dish is now an end product that is trusted. The recipe is being updated and stored back in the trusted repos for re-use.</p><p>In the restaurant, we are performing continuous monitoring by the serving staff, again, with traceability to requirements, including feedback from users.</p><figure><img alt="Anna: My Own “Wiki” to the rescue!" src="https://cdn-images-1.medium.com/max/1024/0*yulUJgqSLTKUPaJi" /></figure><p>Anna’s close friend Sam, she often refers to him as “Wiki”, works as a transformation advisor in the IT sector.</p><p>He hears about Anna’s efforts of building a trusted supply chain and he chimes in sharing his experiences from building similar capabilities in the IT sector.</p><p>The 5 elements presented by Sam seem to have a big overlap with Anna’s.</p><p>Checking out the capabilities Anna sees she can learn a lot from Sam but that there are also specific capabilities for her industry.</p><p>Sam specifically highlights Wardley mapping as a practice which might be of interest for Anna. It’s an easy, accessible method for mapping out the value chain and exploring options for optimization.</p><p>She thanks Sam for his support and continues her journey together with the team.</p><figure><img alt="4 critical measures for success" src="https://cdn-images-1.medium.com/max/1024/0*cpU6EAMNczYwfpZW" /></figure><p>To measure is to know, we learned before.</p><p>Research found, as can (also) be read in the book Accelerate, that there are 4 critical measures for success. These measures focus on market agility and reliability.</p><p>Take Lead time for Change.</p><p>In the restaurant this would mean the time from committing order to the time it has been served to the customer. Why is this important? Shorter is often better but, in this specific restaurant use case you might want to factor in the customer experience factor. Shorter is better though if you consider the fact that we want feedback as soon as possible to be able to make adjustments.</p><p>Another essential measure is the MTTR or mean time to recovery.</p><p>In short; how long do we need to recover from a failure impacting one of our guests. The reason that this is important is that we should always keep in mind that we want to keep the balance between fast delivery and being able to support without negative customer impacts.</p><p>Excelling in these 4 areas has a direct impact on organizational performance. Having a way to measure these indicators is essential to her restaurant’s success Anna concludes.</p><figure><img alt="The (Pelorus) “restaurant” dashboard" src="https://cdn-images-1.medium.com/max/1024/0*FNDdCuzcfMlKHmUy" /></figure><p>Before continuing to the next part of her plan for La Pendule she recognizes that she should definitely make her progress visible for her and the rest of the team.</p><p>She proposes to build <a href="https://pelorus.readthedocs.io/en/latest/">a dashboard</a> for everyone to see where they can plot the success metrics defined.</p><figure><img alt="Tools can only be as good as the people using them." src="https://cdn-images-1.medium.com/max/1024/0*bpstRUg_zZXh3gYt" /></figure><p>Anna realizes that process and technology is very important but there is definitely a lot more to improve regarding the People aspect of the organization.</p><p>She understands that tools can only be as good as the people using them….</p><figure><img alt="Open organizations create sustained competitive advantage" src="https://cdn-images-1.medium.com/max/1024/0*Ed_1GtJeBsAPmVtU" /></figure><p>An open organization empowers people at all levels to act with accountability. Instead of focusing on driving decisions and planning from the minds of a few.</p><p>We believe that the best ideas should get a chance and collaboration can pool collective wisdom, and that leaders are not determined by title.</p><p>Combining open technology and an open culture unlocks new business models and revenue streams and allows for a faster time to market.</p><p>Embracing the characteristics of an open organization allows for a transformation of culture, building an ecosystem of innovation.</p><p>Being Open unlocks the world’s potential…</p><figure><img alt="The Open Organization key characteristics: TICCA" src="https://cdn-images-1.medium.com/max/1024/0*hmue_bfaHS36K5-V" /></figure><p>The open organization can be seen as a framework consisting of 5 characteristics; Transparency, Inclusivity, Collaboration, Community and Adaptability.</p><p>Anna and the team quickly realize that work is to be done but that this can be done granularly through an iterative process working towards an open organization that works for them.</p><p>What they all agree on is that they want to let the sparks fly and for that they need to change.</p><figure><img alt="Dojo: “The place of the way”" src="https://cdn-images-1.medium.com/max/1024/0*0w7-x_9XWdovDjwI" /></figure><p>The final element before putting it all together is the element of continuous learning and enabling a growth mindset.</p><p>A Dojo, “the place of the way”, is a place where a team works on the real product, the real project they are supposed to work on, actively coached by Dojo coaches.</p><p>They do the same work, with the same team, but in a different space and with different ways of working.</p><p>Benefits of a Dojo setup are for example the ability to introduce new practices and ways of working. But also to introduce new technologies and tools. Furthermore you Increase team autonomy and add continuous improvement focus.</p><p>Other benefits include a low barrier to onboarding new members or even new teams to existing product development, and also incubate and accelerate the development of new products with the use of all of the best practices and latest advancements in tech and tools available.</p><figure><img alt="Putting it all together…" src="https://cdn-images-1.medium.com/max/1024/0*MhHjBH1qm8_irxkT" /></figure><p>Combining all the ingredients Anna and the team come up with a plan for a phased delivery.</p><figure><img alt="Phased delivery for sustainable outcomes." src="https://cdn-images-1.medium.com/max/1024/0*QYpkUYMy-0h7IJWf" /></figure><p>We want to have a delivery for sustainable outcomes. To achieve this we put together a phased approach to success.</p><p>We start small, focusing on all elements and working on people, process and technology.</p><p>Demonstrating we can deliver business value we scale up to the next phase, adding more capabilities. Gaining more experience and having built the necessary capabilities we publicly launch and celebrate our progress.</p><p>We continuously review our progress, our relevance and the value we are delivering while focusing on people, process and technology.</p><figure><img alt="6 months later…" src="https://cdn-images-1.medium.com/max/1024/0*qxONUOrsruIJMlue" /></figure><p>Some time passes and about 6 months later Anna and I meet again!</p><p>Anna tells me she has been invited to deliver a keynote at one of the larger gastronomy events to share about the awesome progress she made with her team and her restaurant.</p><figure><img alt="La Pendule embraced the 5 elements and 3 economies delivering increased business value through people, process and technology" src="https://cdn-images-1.medium.com/max/1024/0*5NA3emqYpLPkIQgP" /></figure><p>Anna summarizes her findings and shares how she and her team made, once again, a winner from La Pendule.</p><p>By embracing the 5 elements and 3 economies they are delivering increased business value through people, process and technology.</p><p>The technical foundation has been anchored in a platform as an interface. They created an ecosystem which is being fed by the trusted supply chain, and embracing the characteristics of an open organization resulted in a change in behavior throughout the organization enabling a growth mindset and a continuous learning community.</p><figure><img alt="Thank you!" src="https://cdn-images-1.medium.com/max/1024/0*IFMr5lBZlLyujdNY" /></figure><p>Thank you very much for spending your time to learn about the story of Anne, La Pendule and the 4 ingredients that helped her business win.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7fdf749cdc7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From being strangers to being a team in just a few days!]]></title>
            <link>https://stefanvanoirschot.medium.com/from-being-strangers-to-being-a-team-in-just-a-few-days-5e0b46fe5707?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e0b46fe5707</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[continuous-improvement]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[open-practice]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Thu, 20 Feb 2020 18:51:06 GMT</pubDate>
            <atom:updated>2020-03-08T20:56:07.861Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>January 20–24 I had the opportunity to experience the best training I’ve ever had. DevOps Culture and Practices Enablement, or DO500 in short.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rfFIfCctgx8U9Kb6" /><figcaption>DevOps Culture and Practices Enablement — January 20–24, 2020 — Utrecht, The Netherlands</figcaption></figure><p><em>Let me start by saying I am a Red Hat associate and this being a Red Hat course you could assume that I’m biased to some extend :)</em></p><p>We kicked off on Monday morning at a training location in Nieuwegein near the city of Utrecht. As a group of 20+ people we were asked to sit down on the chairs who had been neatly positioned in a big circle. Being mostly strangers to each other we started with the introduction round and quickly learned the basics about each other, name, job, why are you here? Who could have thought that only after a few days we would leave the room as collaborative team members and even friends!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cIyNZDwjPcbuOwcY" /></figure><p>During the 5 days of training we were exposed to a great number of practices all mapping to the above Mobius loop including its foundation. What I learned early on during the course is that working hard can go hand-in-hand with having tons of fun!</p><p>Foundational practices around culture and collaboration like the Social Contract, Real-time Retrospective and Visualisation of Work as well as technical practices like Continuous Delivery, Test Automation and Configuration as Code provided the foundation for the Mobius loop of continuous discovery and continuous delivery.</p><p>While learning about the different practices I started reflecting on past experiences. I knew, and had previously experienced, most of the delivery loop practices, but what about the discovery loop practices? Of course I knew continuous discovery is essential and goes hand in hand with continuous delivery but little did I know about all the great practices that are out there to make this process a lot more effective. During the week we went through around 40 practices part of the <a href="https://openpracticelibrary.com/">Open Practice Library</a> getting a better understanding of the individual practices and how they work together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JN6jN4nToLJcjfd2" /></figure><p>The course is very well balanced between theory and hands-on exercises. Many games are part of the course to support the understanding of the theory and science behind practices. Games are executed in pairs, in your team (we had 4), or the entire group. The fun and laughs I had during the execution of the games definitely helped in the fast adoption and understanding of the practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jzh7sttPCvIAP26J" /></figure><p>My personal takeaway from this training is that you do not have to be a Dev or Ops person to make use of these open practices. The practices demonstrated can be utilised in any field. I work in sales as a Solution Specialist, and doing continuous discovery with my customer is one of my more important tasks. Applying open practices will make me collaborate with my customer more effectively.</p><p>During the training, whilst paying attention and absorbing all that was shared, I started thinking about how these open practices could be valuable during my sales conversations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7FlkSsV4LCkG3OMc" /></figure><p>In the above photo I’ve laid out some of the practices I have selected to utilise together with my customers. Of course one would not have to apply all these practices together all the time but this gives an idea of a possible flow for continuous discovery. So how would this work? Let’s dive in.</p><p>After having done our round of introduction and an ice-breaker game like the face game or animal drawing we start building our <a href="https://openpracticelibrary.com/practice/social-contract/">social contract</a>; some basic rules around our way of working we agree upon building a constructive, fun team culture. Before we start working on action items it’s a good idea to have shared knowledge and understanding regarding what it means for a work item to be done by the team; the <a href="https://openpracticelibrary.com/practice/definition-of-done/">Definition of Done</a>.</p><p>Almost forgot, the <a href="https://openpracticelibrary.com/practice/visualisation-of-work/">visualisation of work</a>. We build information radiators displaying our work and progress, for example a KanBan, the social contract, and more. Check out the photo earlier in this post with all the sticky notes. Next up is the <a href="https://openpracticelibrary.com/practice/burndown/">Burndown</a>, a visualisation of work left to do within a specified time period, displayed as a chart. Almost done preparing we finish with the <a href="https://openpracticelibrary.com/practice/realtime-retrospective/">realtime retrospective</a> practice. We want to get feedback as fast as possible and continuously improve the experience of our meeting.</p><p>Applying these practices will set the scene. Agreeing on how you want to work together in a meeting, agreeing on what you want to achieve, visualising and measuring progress and having the ability to continuously provide feedback to improve the quality of the meeting seems essential for every effective meeting. The level of detail you are able to cover will of course depend on the length of the meeting.</p><p>Having set the scene we jump into the emerging phase of our meeting. As a starting point I would kick-off the <a href="https://openpracticelibrary.com/practice/start-at-the-end/">start-at-the-end</a> practice describing what success looks like and use this to define our goal. We would use this goal as input for our next exercise the Impact Mapping. <a href="https://openpracticelibrary.com/practice/impact-mapping/">Impact Mapping</a> is a strategic planning technique which shifts the conversation from what (output) to why (outcome). We start this exercise by making sure our goal defined earlier is <a href="https://en.wikipedia.org/wiki/SMART_criteria">SMART</a>. Next up we identify relevant stakeholders (the actors, who), the impact (how) we want to make on them and finally what our deliverables (output, what) should be to realise the defined impact. Impact mapping is an easy to use, but very powerful technique, providing quick insights. A hypothesis to check our work can be build from right to left. For example; by delivering A does this provide impact B for stakeholder C achieving our goal D?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pDjnYS-IWz2Quw29" /></figure><p>Continuing our session we could apply the <a href="https://openpracticelibrary.com/practice/priority-sliders/">Priority Sliders</a> practice to get the conversation going around relative priorities to get a clear focus on upcoming activities.</p><p>Often we find ourselves in a situation were we want to have a better understanding of existing processes. For example; every IT-bit of each step in a workflow has been automated but still the workflow is slow. What’s happening? Applying <a href="https://openpracticelibrary.com/practice/vsm-and-mbpm/">Value Stream and Process Mapping</a> can give us the insights we need. We might discover that the manual approval steps between various departments are slowing us down. Furthermore it could help us design a new, faster process. This practice helps us identify bottlenecks and gives use a way to measure improvement. A very powerful technique to demonstrate that what you’re doing is actually worth it!</p><p>Working towards the end of the first(!) session <a href="https://openpracticelibrary.com/practice/target-outcomes/">Target Outcomes</a> is a great practice to capture and articulate the goals and outcomes a team is striving to deliver. Our final activity before doing a <a href="https://openpracticelibrary.com/practice/retrospectives/">retrospective</a> and checking if we have achieved our meetings goals is the User Story Mapping. <a href="https://openpracticelibrary.com/practice/user-story-mapping/">User Story Mapping</a> is tightly coupled with Value Slicing. As a team we map out our story using sticky notes and get quick insights in all the parts of the story. The second step would be to Value Slice this output against our previously defined Target Outcomes getting quick insights into the most important activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qp8keW0P0l8d6G61" /></figure><p>All of the output gathered during the execution of these practices is output for our transition to, and the execution of, the continuous delivery phase. The part of the Mobius loop where we refine our backlog, do our planning and start executing our sprints continuously improving our solution. Inherent to the working of the Mobius loop, output of the continuous delivery is input for our continuous discovery, helping us learn and improve. Reapplying the practices described before, or any of the other practices out <a href="https://openpracticelibrary.com/">there</a>, to continuously improve our services and helping us achieving our business/IT goals.</p><p>I’m super excited about the stuff I learned, the people I met and all the fun and laughs I had during the week. This Medium post is a repost of my <a href="https://www.linkedin.com/pulse/from-being-strangers-team-just-few-days-stefan-van-oirschot/">LinkedIn article</a> and the second step (<a href="https://www.linkedin.com/posts/stefan82_devops-leadership-teamwork-activity-6626507098299604992-TBtU">LinkedIn post being the first step</a>) after having finished the training late January to write up my experiences and making sure I maximise the effect of this training.</p><p>During the next few weeks I will more and more incorporate the practices in my day-to-day job and start accelerating customer conversations by applying these freshly learned practices. Looking forward to sharing with my customers what I’ve learned and seeing how applying these practices can make our conversations mutually more effective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*teD7V1ylCYkpvez5" /></figure><p>The DevOps Culture and Practices Enablement course is an immersive 5-day learning experience for everyone who wants to improve his collaboration skills and understanding of modern practices. Loads of fun and learning are guaranteed. <strong>Best training ever by a landslide!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e0b46fe5707" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running an LTO Network node on OpenShift 4 (on AWS)]]></title>
            <link>https://stefanvanoirschot.medium.com/running-an-lto-network-node-on-openshift-4-on-aws-669c1a6fd8d9?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/669c1a6fd8d9</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[openshift]]></category>
            <category><![CDATA[lto-network]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Fri, 02 Aug 2019 19:13:32 GMT</pubDate>
            <atom:updated>2019-08-17T15:21:00.636Z</atom:updated>
            <content:encoded><![CDATA[<p>So you decided you want to be part of the LTO Network, awesome! Ow… you were already part of the Community?! Even better! Nice to meet you!</p><p>If you read more of my How-to guides for setting up an LTO Network Public Node you can recall this introduction. Let’s jump into the new bits!</p><p>A great way to be part of the community is by actively participating as a node in the network. This blog post demonstrates the steps needed to get an <a href="https://lto.network/">LTO Network Public Node</a> up and running using a <a href="https://try.openshift.com/">Red Hat OpenShift 4</a> cluster on AWS (Amazon Web Services).</p><p>If you’re not an enterprise user you might not be familiar with Kubernetes or <a href="https://www.openshift.com/">OpenShift</a>. OpenShift version 4 was released a few months ago and is Red Hat’s latest and greatest enterprise Kubernetes distribution based on the community open source project called OKD. OpenShift is thé container application platform for many enterprises in the world.</p><p>This proof of concept, executed on Red Hat OpenShift 4 on AWS, shows the simplicity of deploying the platform as well as deploying a new application onto the platform. After deployment we no longer have to worry about our node. The Kubernetes orchestrator will make sure it keeps running and if a new version of the container image becomes available the OpenShift platform will automatically pull the new image and perform a rolling upgrade of our running node. Secrets will make sure stuff like our Wallet’s seed, password and API_key are kept safe and persistent storage will make sure we do not lose any working data generated by our workload.</p><p>In this guide I’ll be skipping the part about creating wallets, having a main wallet, a staking wallet, how to lease, etc. If you want to read more about this, please check out the steps 1 and 2 in <a href="https://medium.com/@stefan0000/lto-network-mining-in-5-steps-a492305c84ea">this guide</a>.</p><h3><strong>Deploying your OpenShift 4 cluster on AWS</strong></h3><p>Installing Red Hat OpenShift 4 and accessing your cluster takes no more than four, if I may say, simple steps:</p><ol><li>Configure an AWS account</li><li>Download the OpenShift installer</li><li>Deploy the OpenShift cluster on AWS</li><li>Access your new cluster!</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BixrJE5n9BvehOtpZTyK5Q.png" /><figcaption><a href="https://try.openshift.com/">https://try.openshift.com</a> — Our starting page</figcaption></figure><p>Let’s start our Proof of Concept by going to our starting page <a href="https://try.openshift.com/">https://try.openshift.com</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pMlp4gOdhDqgvhD85dA5hw.png" /><figcaption>OpenShift 4 — Infrastructure Provider selection</figcaption></figure><p>Different installation types are available for different platforms including AWS, Azure, Bare-metal and VMware. In this how-to guide we will use AWS as the infrastructure layer for our OpenShift 4 cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s1Bza2MqUWick8VNhkDJkw.png" /><figcaption>OpenShift 4 — IPI or Installer-Provisioned Infrastructure — A fully automated deployment</figcaption></figure><p>Installer-Provisioned Infrastructure gives us the fully-automated experience. With just 1 command we will be able to deploy a complete OpenShift 4 cluster as we will see in a minute.</p><p>Let’s start with Step 1, doing some preparations before kicking off the deployment.</p><h3>Step 1: Configure an AWS account</h3><p>Make sure you have an AWS account with access to enough resources to create an OpenShift cluster. In short this means multiple m5.large and m5.xlarge instances, load balancers, elastic ip’s, volumes and more.</p><p>We need a DNS zone for our OpenShift environment. We want to use AWS Route53 (53 being a reference to the well-known port number for DNS) to register a new domain or configure an existing one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsu3yEEZkvZpDi7J-JmAFA.png" /><figcaption>AWS Route 53 configuration</figcaption></figure><p>Next we need an access key. You can configure this under “Security credentials” under your User’s configuration. Please note; your Access key ID is “public”, the key itself is very much private. We will need both during the deployment of our OpenShift 4 cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YD5eiu4W4Yq__RoD" /><figcaption>AWS user configuration, creating an access key</figcaption></figure><p>These were all the required AWS configuration steps. The rest of the deployment can be done without going into the AWS control panel.</p><h3>Step 2: Download the OpenShift installer</h3><p>In this step you’ll download the installer. It’s available for Linux and MacOS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kKwsVRf4zpsi6ySprA15Bg.png" /><figcaption>OpenShift 4 — Installer + Client files.</figcaption></figure><p>In this how-to guide we only need the Installer. The client, available also for Windows, can be used to execute administrative tasks on the cluster using a command-line interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wY66dWx_Eo-In8d0-ZTqBw.png" /><figcaption>OpenShift 4 — Download of Install + Client on MacOS</figcaption></figure><p>To give you a complete picture I will share the details on the installer as well as the client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J8SGQlpLFXLXz8kRAkdBsg.png" /><figcaption>OpenShift 4 — Add oc (client) to your PATH</figcaption></figure><p>In the above screenshot you see the oc client being added to the PATH. The <strong>oc version</strong> command is executed to test that the addition was successful. The error message is expected.</p><p>Next up is the deployment of the cluster.</p><h3>Step 3: Deploy the cluster</h3><p>Alright, you’re ready to deploy the cluster. The cluster create process will initially create a Bootstrap instance and 3 Master (node) instances. You will need your access key id and actual key during the installation process as well as your Pull secret. Later on in the process 3 Worker (node) instances are deployed and in the end the Bootstrap instance will be shutdown.</p><blockquote>Make sure you have enough Elastic IP’s (VPC) available. You need to be able to allocate more than 5 (7?). If you only have 5 you can easily request more by <a href="https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&amp;limitType=service-code-vpc">requesting a limit increase</a> by raising a support ticket.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEhpRXrBZIl8ZygYATwcJw.png" /><figcaption>OpenShift 4 — Create Cluster</figcaption></figure><p>Kick-off the OpenShift 4 on AWS installation using the account specified above. The directory created will be used to store installation files as well as configuration information you will later need to logon to the OpenShift 4 cluster if you would want to use the command-line interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lYNwufQ3kq7O1ZAHcY7ETA.png" /><figcaption>OpenShift 4 — Pull Secret, you can copy it from the Installation page</figcaption></figure><p>The Pull Secret is one of the values you need to specify during the installation process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ho--LxL331yB-JnkSQHYew.png" /><figcaption>OpenShift 4 — Deployment in progress, all values specified</figcaption></figure><p>Let’s summarise the information needed for a successful deployment:</p><ul><li>SSH Public Key (system will try to detect this from your home directory)</li><li>Platform selection (AWS)</li><li>AWS Access Key ID and AWS Secret Access Key (available through your AWS control panel and created during step 1)</li><li>Region (you can choose any Region, i’ve chosen Paris / eu-west-3)</li><li>Base Domain (your domain name configured in Route53 during step 1)</li><li>Cluster Name (choose any name you want)</li><li>Pull Secret (copy this from the installation instructions)</li></ul><p>Deployment of the OpenShift 4 environment takes quite some time. Somewhere between 30–60 minutes is to be expected. Go grab a cup of coffee, or something stronger! :)</p><h3>Step 4: Access your new cluster!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djwGlP6hZXXQcJLlFlfkMQ.png" /><figcaption>OpenShift 4 — Deployment successful</figcaption></figure><p>You are now ready to access your OpenShift 4 installation through the browser (or command-line interface). Secure the specified logon information displayed in the console output. (<em>The above installation is no longer running, the reason the information is not blurred out</em>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FQscMKrzM5NWprJQzT8SKQ.png" /><figcaption>OpenShift 4 — AWS Instance overview of successful deployment</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RskxNp0-SO8gNcKj4iwDBg.png" /><figcaption>OpenShift 4 — Login page</figcaption></figure><p>Our first login to the OpenShift 4 platform will be using the kubeadmin account. Our first step after logging in will be to create a user we will use for our LTO Network Public Node project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSsJ85xvODJIPyP3ylC-XQ.png" /><figcaption>OpenShift 4 — Main Screen kube:admin</figcaption></figure><p>Our login was successful. OpenShift notifies us that we are logged on with a temporary user. Let’s create a “permanent” user. In this example we will use HTPasswd for authentication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zz825RYIbuHyMYWhRNkEyg.png" /><figcaption>OpenShift 4 — Identity Providers</figcaption></figure><p>We can choose HTPasswd as our Identify Provider. Doing this means we will need an HTPasswd file with our users configured. Let’s create an HTPasswd file for my user: stefan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nmYPjbPaYH22eTSm61iGDQ.png" /><figcaption>Command-line work to create our htpasswd file</figcaption></figure><p>As this is just an example we’ll keep it simple. Let’s create an HTPasswd file with just one user: stefan. I want to store this file on my desktop (temporarily) for easy access through my browser for uploading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KdSs8eLKnf9VmeqUdot6aQ.png" /><figcaption>OpenShift 4 — Add Identify Provider: HTPasswd</figcaption></figure><p>Just specify a name for the provider and select the HTPasswd file we just created. Now click <strong>Add</strong>. Log-out to be able to login with our freshly created user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mn6s7yboRdjviCJWPBOMsg.png" /><figcaption>OpenShift 4 — Choose Identity Provider</figcaption></figure><p>We are given the opportunity to choose our new Identity Provider. Select <strong>htpasswd</strong> and specify your username and password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RUAcsp-H0TE097Q5TlwCzg.png" /><figcaption>OpenShift 4 — Successful login with our new user account</figcaption></figure><p>We are all set! We have successfully deployed an OpenShift 4 cluster on top of Amazon Web Services and configured our user. Next up is the deployment of our first application, in our case the deployment of an LTO Network Public Node.</p><h3><strong>Deploying your LTO Network node on OpenShift 4</strong></h3><p>In this Proof of Concept I specifically used the browser interface to execute the steps. All of this can be done, if you’re familiar with the commands, in just a few steps from the command line. An extra advantage is that you would be able to <strong>automate these steps</strong> to make the process even simpler!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItfH8TyzC3BIom3XNj07Ig.png" /><figcaption>OpenShift 4 — Create Project</figcaption></figure><p>Before deploying our LTO Network Public Node on our OpenShift 4 environment we create a project (Kubernetes namespace). A project is only visible to you or to users you give access to. Lets create project called “lto-public-node”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vjp2853sUlk0Y5q-ocRx_w.png" /><figcaption>OpenShift 4 — Secrets</figcaption></figure><p>Immediately after creating a new project you’re presented with a wizard presenting you with interesting options like Browse Catalog and Deploy Image. But before we go there we need to configure some important stuff to make sure our Wallet’s seed, password and API key will be stored securely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3SjdIo7_0hMuo6f65kjODQ.png" /><figcaption>OpenShift 4 — Safeguard our precious information!</figcaption></figure><p>Select <strong>Workloads → Secrets</strong> from the menu on the left. We will create a Key/Value secret to store our various <strong>Keys</strong> (to be used as environment variables within the node) with our secret <strong>Values</strong>.</p><ul><li>LTO_WALLET_SEED → The seed of the Staking wallet</li><li>LTO_API_KEY → Your key for admin access to your node’s API.</li><li>LTO_PASSWORD → The password for the wallet file</li></ul><p>You can of course store any environment variable in a secret. I chose to go with these 3 as an example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*artsMX5WEZb0c7YTjcrq1A.png" /><figcaption>OpenShift 4 — Secret created successfully. We will later add this secret to our workload.</figcaption></figure><p>With our secret created successfully let’s go to the final preparation step before deploying our workload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CIAwBKgasOme2Imp_1YxFg.png" /><figcaption>OpenShift 4 — Configuring a persistent volume</figcaption></figure><p>Persistent storage or a persistent volume is not mandatory, it does come in handy though. A container deployed on the platform without a persistent volume attached loses its working data when destroyed.</p><p>In the case of an LTO Network Public Node this means the blockchain data. Of course we can easily re-download the blockchain on crash or when there is a new version but utilising a persistent volume is faster, saves time and saves bandwidth. It also adds to the availability of our node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2egk9njOFdNNS-5kKbCKNA.png" /><figcaption>OpenShift 4 — PersistentVolumeClaim being created</figcaption></figure><p>With our PersistentVolumeClaim being created let’s go to the next step and deploy our LTO Network Public Node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WUQ7Yukm2fCr7vouQ4RcaQ.png" /><figcaption>OpenShift 4 — Deploy Image</figcaption></figure><p>With the project setup we can start deploying our first image. Click on <strong>Deploy Image</strong>. The Image refers to the container image we’re going to deploy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvbJwyOoICi-KxHPlZm8Dg.png" /><figcaption>OpenShift 4 — Deploy Image — environment variables. We will attach the secret later!</figcaption></figure><p>LTO Network currently uses a public Docker repository to store their container images. The Image name is called: <strong>legalthings/public-node</strong>. Enter this name in the<strong> Image Name</strong> field and click on the search icon to lookup the image in the repository.</p><p>The system will give you a warning that the image will be running as <em>root</em>. This might be an issue in some production environments. It’s expected that this will be changed at some point in time.</p><p>You should configure the environment variables here which are not part of the secret you created earlier. We will attach the secret in the next step. In the above screenshot you can see the following environment variables:</p><ul><li>LTO_ENABLE_REST_API (Enable the API)</li><li>LTO_HEAP_SIZE (2g)</li><li>LTO_NODE_NAME (A name for our node)</li></ul><p>When you are done configuring click <strong>Deploy</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JLCIxER8EWf164ZJFEfAGA.png" /><figcaption>OpenShift 4 — Our LTO Network Public Node waiting for deployment</figcaption></figure><p>Before we roll-out our LTO Public Node we want to add the secret as well as the persistent volume we created earlier to our workload. Let’s start with the secret.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_tbXB6DQbrLYde_-bIR9IQ.png" /><figcaption>OpenShift 4 — Add Secret to Workload</figcaption></figure><p>Using the <strong>Workloads → Secrets</strong> menu we can find our secret called <strong>ltonode-configuration</strong> and add it to our workload by clicking the <strong>Add Secret to Workload</strong> button.</p><p>Now select our node from the dropdown box and click <strong>Save</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V15TRylfeoGvPv--PNi81w.png" /><figcaption>OpenShift 4 — Add persistent storage to our workload</figcaption></figure><p>Next up is adding the persistent volume to our workload. We will use the existing claim (created earlier). Be sure to enter<strong> /lto/data</strong> in the Mount Path field. This is the directory within the container where the blockchain data is being stored. Now click <strong>Save</strong>.</p><p>We are all set and ready to roll-out our container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hRf00RAMAtKywGUpXnB9jQ.png" /><figcaption>OpenShift 4 — Roll out of LTO Network Public Node workload</figcaption></figure><p>Select our workload from our project. You can do this as displayed in the above screenshot. Now click <strong>Start Rollout</strong> to deploy our LTO Network Public Node for the 1st time utilising our Secret for environment variables and using persistent storage to make sure we secure our data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MilAeSw2ryCZXMaHGXEETQ.png" /><figcaption>OpenShift 4 — Node is running</figcaption></figure><p>Our node is running. We can see our Pod in the “Running” status and being “Ready”. Let’s check out the console log of our container and see what it is doing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FNRoZpSG6TgXDxxdLacJzw.png" /><figcaption>OpenShift 4 — Console Log</figcaption></figure><p>The above screenshot shows the blockchain being downloaded. This is a one-time download. One-time because of our persistent volume on which we’ll store the data. The download will take quite some time. As of writing we’re almost at block number 300.000. Be patient and maybe grab another drink. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iJPjcp21ak-X4193-DWxPw.png" /><figcaption>OpenShift 4 — Create route screen</figcaption></figure><p>Almost there! Our node is running successfully. We decided to enable the API and to expose the API to the outside world. Important is that you enabled the API using the environment variable in an earlier step (LTO_ENABLE_REST_API = true). External traffic routed in OpenShift 4 is done using the routing layer. Your service will be behind a load balancer (part of OpenShift 4) when you expose it.</p><p>To expose the service to the outside world we click on the <strong>Create Route</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4hvX_zKgxMuforuiBOodnA.png" /><figcaption>OpenShift 4 — Configuring a secure route</figcaption></figure><p>Let’s create a Secure Route with Edge TLS Termination and an automatic Redirect for insecure traffic.</p><p>The LTO node exposes the API over HTTP. With this you can make it HTTPS. Make sure to select <strong>6869 → 6869 (TCP)</strong> as your <strong>Target Port</strong>.</p><p>Scroll down and click the route creation button to create the route and expose your Swagger UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RkHGRsKEEg96qvo1e3sFVg.png" /><figcaption>OpenShift 4 — Secure access to our API</figcaption></figure><p>In a real world scenario you would use a valid certificate, etc. to configure your route.</p><p>The above screenshot displays our Swagger UI giving us easy access to the API of our LTO Network Public Node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xfq_EQQ-z0FCe1TG0cUx6Q.png" /><figcaption>OpenShift 4 — Dashboard of our LTO Public Node project</figcaption></figure><p>That’s it. You’ve successfully mastered setting up a LTO Network Public Node on Red Hat OpenShift 4 (running on AWS). Awesome!</p><p><strong>Now wait for a 1.000 blocks…</strong> (if you actually set this up as your staking node :D )</p><p>Best of luck and thank you very much for contributing and being part of the LTO Network Community!</p><p>If you like this article please leave a small comment! Thank you very much.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=669c1a6fd8d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tesla? Some fuel for thought!]]></title>
            <link>https://stefanvanoirschot.medium.com/tesla-some-fuel-for-thought-55adc375eebe?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/55adc375eebe</guid>
            <category><![CDATA[electric-car]]></category>
            <category><![CDATA[tesla]]></category>
            <category><![CDATA[range-anxiety]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[why]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Sun, 28 Jul 2019 17:56:45 GMT</pubDate>
            <atom:updated>2019-08-17T15:21:14.059Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Hey Stefan! You drive a Tesla, right? You think you would choose one again if you were in the market right now?”</blockquote><p>At least once a week I get asked this question. Really not that weird because most of my colleagues, family and friends are (still) driving Diesel or petrol powered cars. A lot of my colleagues are thinking about switching to electric though, but are looking for validation if this is really the way to go. Some seem to want to trick me in confessing that I made the wrong decision, others are sincerly interested in getting a more complete picture. I am not a fanboy in that I am proactively trying to convert people, maybe you think I am by means of this blog ;), but I do share my thoughts and experiences with whoever wants to hear them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IxQc_kQJzsq7Fl5r7uWTxA.png" /><figcaption>Ducati Hypermotard 950SP Corse</figcaption></figure><p>In my opinion I am a true petrol head. I ride my motorbike (Hypermotard SP) whenever I have the opportunity. It’s a V2-engine (L-Twin) with a straight exhaust, open air filter, new software mapping, you get the idea. I like the raw sound of the engine, revving it to above 10.000 RPM, and shooting flames from the exhaust.</p><p>While all of this is amazing for my, mostly short, rides in the weekend -with friends- I like the quiet and comfort of my electric car during the week. Living in the south of The Netherlands and having office in Amsterdam I spend a lot of time on the biggest parking lot of the country, called the A2. Driving slowly on the highway does not give me any satisfaction (Neither does driving anywhere else slowly but that is beside the point :) ). My radio and streaming of audio with no engine noise gives me comfort. Add an enhanced autopilot and the comfort rises to another level making the journey a lot more enjoyable.</p><blockquote>“Don’t you miss the sound of the engine?”</blockquote><p>Hmm… what engine? Do you mean that 4-cylinder Diesel or maybe Petrol engine? Ah… you have a V8-engine. You are a unicorn, at least in The Netherlands, don’t switch!</p><p>One thing you will never have a discussion about is the performance of an electric car. Everybody knows how fast, for example a Tesla, can accelerate compared to a traditional car. If you want something that comes even close to this kind of performance you are talking real high-end cars like M, RS or AMG models of the premium German brands. I will not compare these cars with a Tesla, it is simply not the same. They target another audience in my opinion and are priced differently as well, definitely if you calculate total cost of ownership. I love them, it would be amazing if I had the opportunity to own one, but it would not work for me as a daily-driver.</p><blockquote>“But what about the charging, how many kilometers can you drive on a single charge?”</blockquote><p>Yes, true, that is great question and the answer depends on multiple factors; the way you drive but also the weather to name just two of the factors. The latest model Tesla’s have over 500 kilometers of range, some even more than that. There are also other brands out there who can over an amazing distance on a single charge. In my opinion the car should be able to cover my daily-kilometers 95+% of the time. In my case this is around 250 kilometers a day on average. This is probably already more then most people in The Netherlands will cover in a day. On rare occasions I have to travel over 500 kilometers a day, this means I have to charge during the day. While the Tesla Supercharger network is amazing and chargers can be found almost everywhere I do not use them that often. Most of the times I have the opportunity to charge my car at the customer location. After your appointment you leave with a partially or maybe even fully charged car, continuing your journey.</p><p>With my car my regular number of kilometers a day is not an issue. I have the opportunity to charge the car on my driveway. At the end of every day I plugin my car and after ~5 hours the car is fully charged again. Every morning I leave with a fully charged vehicle.</p><p>Covering my kilometers on the highway I see people filling-up their cars with fuel and I think that once I had to schedule these fill-ups as well. Now the only time I stop at a petrol station is when I want a cup of coffee or a sandwich. Range anxiety? It is something that is made up by people who do not own an electric car!</p><blockquote>“So, you charge your company car at home? Do you pay the electricity yourself or do you somehow expense this or …?”</blockquote><p>I am not sure if this is the same in other countries than The Netherlands, so please leave a comment if you have a different experience.</p><p>I use a 3-phase charging station at home. The charging station measures the number of kiloWatts and the manufacturer shares this information with my lease company. The lease company sends a bill to my company. I get a credit note from the manufacturer and we’re all set, It’s way simpler and I do no longer have to expense my fuel usage. A win-win :).</p><p>Regarding these fuel expenses. Electricity, in The Netherlands, is way cheaper than petrol, or Diesel. Driving my electric car, my refuel cost dropped to just 25% of my previous fuel cost driving the same number of kilometers. Cost of refuelling is definitely something to keep in mind when calculating your total cost of ownership.</p><blockquote>“I heard the software updates and the in-car games are amazing and fun, what do you think?”</blockquote><p>Yes and maybe. The software updates are amazing. Small incremental changes to your car’s software with new features added on a regular basis. This is amazing and works flawlessly. The car is getting better and better and more feature rich every day! Part of these software updates are also the famous easter eggs, the classic Atari games and, the newly announced, playing chess (Chessla?) against the car. Personally I do not really use them. Not sure really when to use them. Again the software updates are amazing and receiving regular updates to your car gives you the idea of real value for money.</p><blockquote>“Ok, sounds like a perfect car then?”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1jwIsXni5RCcHtQx5d_O9A.png" /><figcaption>You can’t argue about taste but in my opinion this is an amazing looking car! :)</figcaption></figure><p>Yes, No… Maybe. It depends… For me, with what is currently available, within reach, and with what I want from my daily-driver, it is the perfect car. It is fast, has great handling, it is quiet, comfortable and has all the features and gimmicks a nerd like me would (ever) want in a car. My next car, based on what I know now, will again be an electric car, maybe even the same brand. We’ll see what the future brings. It does look bright though. If you see how a start-up like Tesla is able to really connect customers to their brand; the way they sell cars, deliver cars, do service to their cars, deliver updates, reward customers and more. It’s Car 2.0; a different ballgame from existing manufacturers. Looking forward to see how this industry evolves during the next years. #TheFutureIsNow!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55adc375eebe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IBM, you made me miss Formula 1!]]></title>
            <link>https://stefanvanoirschot.medium.com/ibm-you-made-me-miss-formula-1-2d8a80bbbb92?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d8a80bbbb92</guid>
            <category><![CDATA[acquisition]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[partnerships]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[ibm]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Mon, 15 Jul 2019 13:47:18 GMT</pubDate>
            <atom:updated>2019-08-17T15:21:24.262Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>October 28, 2018, was the day the announcement was made that IBM was to acquire Red Hat for the amazing number of 34 billion dollars. This day was also the day that Max Verstappen drove to victory during the Formula 1 Mexico 2018 race and Lewis Hamilton claimed his 5th world title.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W4Dc-U-YHVKQu9_74UQEzg.png" /><figcaption>Source: <a href="https://www.formula1.com/en/racing/2018/Mexico.html">https://www.formula1.com/en/racing/2018/Mexico.html</a></figcaption></figure><p>Unfortunately the announcement -I saw it first being published on Bloomberg- made me miss the first 30 laps of the race ;)</p><p>This was not because I was not watching the TV, I was, but somehow I could not keep paying attention to make anything out of the race.</p><p>Soon after the initial “rumours”, the announcement was confirmed by my company Red Hat, and IBM, posting a news story on both their websites.</p><p>Amazing, weird, what does this mean, cool, huh? A lot came to mind in the first few minutes after the announcement. I needed more time to process this, that was for sure. I turned to my phone to check what my team members and colleagues were sharing.</p><p>Looking at the different chats all the feelings you can imagine were there. Rational responses, irrational responses. At that time we had only seen the official announcements, any response at the time, was solely based on these.</p><p>I turned back to myself. I had a lot of experience with IBM, their technology, their services, and their support department. Before joining Red Hat I was CTO at an IBM and Red Hat business partner using both vendors’ technology and service to support our customers.</p><p>During my years at Red Hat, I also have had the opportunity to work together with IBM, specifically the Global Business Services department, as part of our ongoing partnership. My prejudice went overboard the first time I met with these people.</p><p>Boys, girls of different nationalities. All extremely, intrinsically motivated people, sharing about their engagements in the areas of blockchain, IoT, machine learning, quantum computing, and more. Amazing projects, innovations and achievements. A different IBM, the new IBM, and the IBM I was going to work with.</p><p>From the initial announcement and during follow-up briefings we consistently heard Red Hat would be operating as a distinct unit within IBM’s Hybrid Cloud team. Great news, Red Hat is my company, of course, I want to keep my brand, e-mail address, technology, the same office, go-to-market, my team. I wanted to benefit of the this merger as well. How would this work?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z4DDpAYMvS7zEf1Uf7f0rQ.png" /><figcaption>Source: LinkedIn</figcaption></figure><p>Last week the merger was finally there. I am very happy with this milestone and am looking forward to experience what we can achieve together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d8a80bbbb92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vacation Insights!]]></title>
            <link>https://stefanvanoirschot.medium.com/vacation-insights-9541c142e766?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9541c142e766</guid>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[banana]]></category>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[vacation]]></category>
            <category><![CDATA[permaculture]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Mon, 01 Jul 2019 13:03:14 GMT</pubDate>
            <atom:updated>2019-08-17T15:21:30.776Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“I would like to visit a banana plantation on the last day of our vacation, are you coming with me?”</blockquote><p>This was the question my wife asked me during the last days of our vacation to La Palma. A little hesitant if this would be of interest to me, I agreed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*hmUNf6pZrGJOzHoI" /></figure><p>On that Wednesday morning we were waiting at 10:30 am at the agreed location in Puerto Naos. We saw the plantation at a distance. I asked my wife: “Do you see all those other plants growing among the banana trees?” Without knowing, I had just become acquainted with the impressive ecosystem of which I would later learn everything about.</p><blockquote><em>You know: A banana plant is a type of grass, so not a tree I learned :). There are around two hundred different edible varieties of banana. The banana plant has one of the largest leaves of all plants, in fact, the leaves of the plant continue in the “trunk”.</em></blockquote><p>We were welcomed by Fran, the owner of the plantation. Fran -a world improver in heart and soul- has been contributing to the climate with his plantation and ways of working for more than 10 years. He let us in and requested us to follow him. Walking through, what some people would call a jungle, it seemed as if I had ended up in a completely different world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Lc2dekNZTyJFGhyj" /></figure><p>The plantation with the name PlatanoLógico is an ecological banana plantation. Plátano spanish for banana and Lógico in this case the designation for the ecological aspect.</p><p>Ecological means that everything must be in accordance with the natural cycle. On the plantation this is achieved by building and then naturally evolving an ecosystem; balance, back to basics, back to nature.</p><p>Starting an ecosystem is not easy. We saw the result of years of hard work, learning and thinking! The ecosystem of the plantation functions without the use of artificial substances. As the word ecosystem indicates, the plantation maintains itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*WnWYsfVUI6yPEKsv" /></figure><p>If you walk through the plantation you will see different plant species; of course banana plants but also broccoli and many others. You also see many species of animals including caterpillars, butterflies, wasps, birds, ants, cockroaches, lizards, ladybirds and even some sheep, ducks and donkeys. Some plants have the purpose of being harvested for sale. Other plants, trees are present as food or housing for animals. Amazing! But why?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*5xUDa6Lf9iFkhgJQ" /></figure><p>Unfortunately, most banana users think that appearance is almost more important than taste and or nutritional value. This means that a banana must look nice. This is also expected from an ecological banana. An example: Caterpillars love to nest on banana plants. In a legacy monoculture, this would be combatted by spraying crops to keep the caterpillars away. This is of course out of the question at an ecological plantation. The ecosystem of PlatanoLógico shows that it is possible. By planting broccoli plants between the Banana plants, caterpillars already partially diverge. Wasps (Aphidius Colemani) and birds bring the rest of the balance. However, birds do not nest in a banana plant, this means that suitable housing should also be arranged for them in the form of trees. Good and bad, these are people’s value judgments, in this ecosystem everything works together and the whole is balanced; impressive!</p><p>This plantation has a banana production that is only 10% -15% inferior to the best-producing monoculture plantation! At the same time, it produces besides bananas many (10s of) other fruits and vegetables; incredible.</p><p>During the entire tour, Fran’s intrinsic motivation was tangible and inspiring. My visit to the PlatanoLógico ecosystem has opened my eyes further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Dob0BQjkXex8xkoi" /></figure><p>In the field of an organic lifestyle or even an ecological lifestyle I am following. My wife steers me and educates me. I follow and I learn. This new way of doing things can easily be maintained by the visible benefits of this changed lifestyle. This blog is my first step to moving from being lead, to (co) leading myself.</p><p>Not everything I do is ecological or even organic. However, I believe it is more important that everyone does something than that (only) a few people do it perfectly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9541c142e766" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vakantie-inzicht!]]></title>
            <link>https://stefanvanoirschot.medium.com/vakantie-inzicht-1e2d4985a12e?source=rss-cd36008b9e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e2d4985a12e</guid>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[banana]]></category>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[eco]]></category>
            <category><![CDATA[bio]]></category>
            <dc:creator><![CDATA[Stefan van Oirschot]]></dc:creator>
            <pubDate>Sat, 29 Jun 2019 12:21:18 GMT</pubDate>
            <atom:updated>2019-06-29T12:21:18.989Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Graag zou ik op de laatste dag van onze vakantie een bananenplantage bezoeken, ga je mee?”</blockquote><p>Dit was de vraag die mijn vrouw mij stelde tijdens de laatste dagen van onze vakantie naar La Palma. Enigszins onzeker of dit mij voldoende zou interesseren bevestigde ik.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*hmUNf6pZrGJOzHoI" /></figure><p>Op de betreffende woensdagochtend stonden we om 10:30 uur te wachten op de afgesproken locatie. Op een afstandje zagen we de plantage liggen. Ik zei tegen mijn vrouw: “Zie je al die andere planten groeien tussen de bananenbomen?”. Zonder dat ik het wist had ik zojuist kennis gemaakt met het indrukwekkende ecosysteem waarover ik nog veel zou leren.</p><blockquote><em>Weetje: Een bananenplant is een grassoort, zo leerde ik, geen boom dus :). Er zijn zo’n tweehonderd verschillende eetbare bananensoorten. De bananenplant heeft 1 van de grootste bladeren van alle planten, sterker nog, de bladeren van de plant lopen door in de “stam”.</em></blockquote><p>We werden ontvangen door Fran, de eigenaar van de plantage. Fran, een wereldverbeteraar in hart en nieren en al ruim 10 jaar bezig met bijdragen aan het klimaat met zijn plantage. Hij liet ons binnen en gebood ons hem te volgen. Lopende door een -wat sommige mensen wildernis zouden noemen- leek het wel of ik in een andere wereld terecht was gekomen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Lc2dekNZTyJFGhyj" /></figure><p>De plantage met de naam PlatanoLógico is een ecologische bananenplantage. Platano Spaans voor banaan en Lógico in dit geval de aanduiding voor de ecologische aspect.</p><p>Ecologisch wil zeggen dat alles in overeenstemming moet zijn met de natuurlijke kringloop. Op de plantage wordt dit gerealiseerd door het bouwen en vervolgens natuurlijk laten evolueren van een ecosysteem; balans, terug naar de basis, terug naar de natuur.</p><p>Een ecosysteem opstarten is niet eenvoudig. Wij aanschouwden het resultaat van jaren hard werken, leren en na blijven denken! Het ecosysteem van de plantage functioneert zonder het gebruik van artificiële stoffen. Zoals het woord ecosysteem aangeeft houdt de plantage zichzelf in stand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*WnWYsfVUI6yPEKsv" /></figure><p>Loop je door de plantage dan zie je verschillende plantensoorten; natuurlijk bananenplanten maar ook broccoli en vele andere. Ook zie je vele diersoorten waaronder rupsen, vlinders, wespen, vogels, mieren, kakkerlakken, hagedissen, lieveheersbeestjes en zelfs enkele schapen, eenden en ezels. Sommige planten hebben als doel om geoogst te worden voor verkoop. Andere planten, bomen zijn aanwezig als voedsel respectievelijk huisvesting voor dieren. Wouw! Maar waarom dan?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*5xUDa6Lf9iFkhgJQ" /></figure><p>De meeste gebruikers van bananen vinden helaas uiterlijk bijna belangrijker dan smaak. Dit betekent dat een banaan er mooi uit moet zien. Dit wordt ook verwacht van een ecologische banaan. Een voorbeeld: Rupsen nestelen maar wat graag op bananenplanten. In een achterhaalde monocultuur zou hiervoor uitgeweken worden naar het bespuiten van gewassen om de rupsen te weren. Uiteraard is dit uit den boze binnen een ecologische plantage. Het ecosysteem van PlatanoLógico laat zien dat het kan. Door het planten van broccoliplanten tussen de Bananenplanten wijken rupsen reeds gedeeltelijk uit. Wespen (Aphidius Colemani) en vogels brengen de rest van de balans. Vogels nestelen echter niet in een bananenplant, dit betekent dat ook voor hen passende huisvesting geregeld dient te worden in de vorm van bomen. Goed en slecht, dit zijn waardeoordelen van de mensen, in dit ecosysteem werkt alles samen en is het geheel in balans; indrukwekkend!</p><p>Deze plantage heeft een bananenproductie die slechts 10%-15% onder doet voor de best-producerende monocultuur plantage! Tegelijkertijd produceert het naast bananen vele (10-tallen) andere groenten en fruit; werkelijk verbluffend.</p><p>Gedurende de gehele rondleiding was de intrinsieke motivatie van Fran voelbaar en inspirerend. Mijn bezoek aan het PlatanoLógico ecosysteem heeft mijn ogen verder geopend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Dob0BQjkXex8xkoi" /></figure><p>Op het gebied van een biologisch levensstijl of zelfs een ecologische levensstijl ben ik volgend. Mijn vrouw stuurt mij, ik volg en ik leer. Het volgen is goed vol te houden door de zichtbare voordelen van deze aangepaste levensstijl. Deze blog is mijn eerste stap om van volgend naar (mede)richtinggevend te bewegen.</p><p>Niet alles wat ik doe is ecologisch of zelfs biologisch. Ik ben echter van mening dat het belangrijker is dat iedereen iets doet dan dat (slechts) een aantal mensen het perfect doen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e2d4985a12e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>