<?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 Jim van der Waal on Medium]]></title>
        <description><![CDATA[Stories by Jim van der Waal on Medium]]></description>
        <link>https://medium.com/@jimvdwaal?source=rss-e240d3eb58------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*U6Gp8S6_AxaRBaaBGCsrVA.jpeg</url>
            <title>Stories by Jim van der Waal on Medium</title>
            <link>https://medium.com/@jimvdwaal?source=rss-e240d3eb58------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:00:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jimvdwaal/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[Agile IRL: Scrumming a Move]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://jimvdwaal.medium.com/agile-irl-scrumming-a-move-f1b5272c398?source=rss-e240d3eb58------2"><img src="https://cdn-images-1.medium.com/max/2224/1*3I2LUzZjYexUc6fRrUL0_w.jpeg" width="2224"></a></p><p class="medium-feed-snippet">Applying some pragmatic Scrum for a big personal project like moving.</p><p class="medium-feed-link"><a href="https://jimvdwaal.medium.com/agile-irl-scrumming-a-move-f1b5272c398?source=rss-e240d3eb58------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://jimvdwaal.medium.com/agile-irl-scrumming-a-move-f1b5272c398?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1b5272c398</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Thu, 26 Nov 2020 14:00:17 GMT</pubDate>
            <atom:updated>2020-11-26T14:00:17.960Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Agile IRL: Early and Continuous Delivery in Sri Lanka]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://jimvdwaal.medium.com/agile-irl-early-and-continuous-delivery-in-sri-lanka-f2e785c4f247?source=rss-e240d3eb58------2"><img src="https://cdn-images-1.medium.com/max/2224/1*OPEsMm1PYNKOTmhSs99b4A.jpeg" width="2224"></a></p><p class="medium-feed-snippet">What we can learn from the Sri Lankan hotel business.</p><p class="medium-feed-link"><a href="https://jimvdwaal.medium.com/agile-irl-early-and-continuous-delivery-in-sri-lanka-f2e785c4f247?source=rss-e240d3eb58------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://jimvdwaal.medium.com/agile-irl-early-and-continuous-delivery-in-sri-lanka-f2e785c4f247?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2e785c4f247</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[rethink]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 12:58:58 GMT</pubDate>
            <atom:updated>2020-11-02T12:58:58.178Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Dealing with Deadlines]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.productcoalition.com/dealing-with-deadlines-2f92a1a0fe50?source=rss-e240d3eb58------2"><img src="https://cdn-images-1.medium.com/max/2224/1*TPnGFFWylwf3UXBkKUbdMg.jpeg" width="2224"></a></p><p class="medium-feed-snippet">How MoSCoW can help you as a Product Manager to make your committed dates.</p><p class="medium-feed-link"><a href="https://medium.productcoalition.com/dealing-with-deadlines-2f92a1a0fe50?source=rss-e240d3eb58------2">Continue reading on Product Coalition »</a></p></div>]]></description>
            <link>https://medium.productcoalition.com/dealing-with-deadlines-2f92a1a0fe50?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f92a1a0fe50</guid>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 16:28:16 GMT</pubDate>
            <atom:updated>2020-10-01T16:28:16.780Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Corona Dashboard: putting the Health in Health Metrics]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.productcoalition.com/corona-dashboard-putting-the-health-in-health-metrics-2b323967defa?source=rss-e240d3eb58------2"><img src="https://cdn-images-1.medium.com/max/1698/1*Xo_0ncZa1ZHZqVBxc_LBxw.png" width="1698"></a></p><p class="medium-feed-snippet">What Product Managers can learn from the Dutch Government when setting up (Product) Health Metrics.</p><p class="medium-feed-link"><a href="https://medium.productcoalition.com/corona-dashboard-putting-the-health-in-health-metrics-2b323967defa?source=rss-e240d3eb58------2">Continue reading on Product Coalition »</a></p></div>]]></description>
            <link>https://medium.productcoalition.com/corona-dashboard-putting-the-health-in-health-metrics-2b323967defa?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b323967defa</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[coronavirus]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Thu, 23 Jul 2020 06:39:29 GMT</pubDate>
            <atom:updated>2020-07-28T13:45:37.397Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Product Roadshows: Promoting your Internal Products]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/product-roadshows-promoting-your-internal-products-98e5e6a7f6cf?source=rss-e240d3eb58------2"><img src="https://cdn-images-1.medium.com/max/2053/1*69K6IvgXtTsqSmNh-BYHEA.png" width="2053"></a></p><p class="medium-feed-snippet">How to build relationships with your customers and increase the impact of your internal products.</p><p class="medium-feed-link"><a href="https://medium.com/swlh/product-roadshows-promoting-your-internal-products-98e5e6a7f6cf?source=rss-e240d3eb58------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/product-roadshows-promoting-your-internal-products-98e5e6a7f6cf?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/98e5e6a7f6cf</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Tue, 23 Jun 2020 09:01:01 GMT</pubDate>
            <atom:updated>2020-06-23T09:01:01.705Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Product Owner vs. Product Manager: what is the difference?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://jimvdwaal.medium.com/product-owner-vs-product-manager-what-is-the-difference-fb9a7c0c2255?source=rss-e240d3eb58------2"><img src="https://cdn-images-1.medium.com/max/1602/1*A5JEPykNWSvMU0Eb_TDlBQ.png" width="1602"></a></p><p class="medium-feed-snippet">A simplified and opinionated explanation.</p><p class="medium-feed-link"><a href="https://jimvdwaal.medium.com/product-owner-vs-product-manager-what-is-the-difference-fb9a7c0c2255?source=rss-e240d3eb58------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://jimvdwaal.medium.com/product-owner-vs-product-manager-what-is-the-difference-fb9a7c0c2255?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb9a7c0c2255</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Thu, 04 Jun 2020 06:01:20 GMT</pubDate>
            <atom:updated>2020-11-04T16:56:28.169Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Making SLOs Fast]]></title>
            <link>https://medium.com/onefootball-locker-room/making-slos-fast-42acb8145ca9?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/42acb8145ca9</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[service-level-objectives]]></category>
            <category><![CDATA[sre]]></category>
            <category><![CDATA[site-reliability]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Mon, 25 May 2020 07:20:55 GMT</pubDate>
            <atom:updated>2020-05-25T07:20:55.779Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rB8LS_CJiBztjSpcBuMrpA.jpeg" /></figure><h4>How we created a tool that makes practicing Site Reliability Engineering (SRE) easier.</h4><p><em>This article is collaboratively written by </em><a href="https://medium.com/@dominikgarber"><em>Dominik Garcia</em></a><em> (Software Engineer) &amp; </em><a href="https://medium.com/@jimvdwaal"><em>Jim van der Waal</em></a><em> (Product Manager), who were both part of the team that developed the SLO Creation Tool.</em></p><p>In the last years the SRE movement has got a lot of traction. After the publication of <a href="https://landing.google.com/sre/sre-book/toc/index.html">the book</a> the practices have spread within no time. And with very good reasons! We don’t want to get into the theoretical talk about SRE but tell you how we put them into practice at Onefootball.</p><p>We noticed it is easy to talk about it but to actually practice it and embed it in your way of working, is way harder. In this article we share the story on why and how we created a tool to make the creation of SLO’s simple for all the product teams. Making it easy for all teams to adopt the most important practice of SRE, building Service Level Objectives (SLO’s). Helping to drive the SRE mindset.</p><h4>Onefootball &amp; the Core team</h4><p>At Onefootball, performance plays an important role. With over 11 Million monthly users, all across the world, there is a significant load and we need to build products and services that scale. Which is why there was an increasing urgency in driving SRE practices within Onefootball.</p><p>At Onefootball we work with <a href="https://medium.com/onefootball-locker-room/life-at-onefootball-scary-close-to-fully-autonomous-teams-1293d9ede4b">autonomous product teams</a>, each responsible for building and running their applications. This brings a lot of benefits, but it also has its challenges. Because each team has a wide set of responsibilities, with Reliability (just) being one of them. And not every team is (or has) an SRE expert.</p><p>This is where <strong>the Core team</strong> comes in. It has always been hard to label the Core team, but when we started the team we formalized our mission as: “We enable teams to build a reliable and scalable Onefootball platform.” So how do you do that?</p><p>We believed that providing the proper tools was just a small component, and an important part of the mission of the team was around the sharing of the knowledge encompassing SRE, and creating awareness about the importance of building reliable applications. You can have the best tools, but without the culture, it will not have any effect on your customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6AsQ0Ho2RTA0P9ln" /><figcaption><em>Tools vs. Culture, a diagram we used to illustrate that it is not all about having the best tools.</em></figcaption></figure><h4>Origin of the idea</h4><p>We started by giving a good example, defining and implementing SLO’s for the applications we owned as the Core team. Practice what you preach. What we found out is that the theory of Service Level Objectives is relatively simple and easy to understand. But implementing it yourself is another story, where the Devil is definitely in the details.</p><p>We had so many (good) discussions within the team. About the meaning of percentiles, the use of error budgets, rolling and fixed time-windows, and so on. And then came the practical discussions on how to translate this into something we could actually start monitoring with our tools. And although these were good discussions, we knew that if we really wanted to make a change in mindset, we needed to make it easy.</p><p>That is why we started to think about how we could make the creation of SLO’s easier. Because we still believed this was the best starting point for teams to get started with the SRE practices and get awareness about the reliability of their applications. And if it would be easy and would only take a couple of minutes, then what would be stopping them?</p><h3>SLO Creation Tool</h3><p>We tried to think of a way that would use the existing theory but making it more accessible, using our own experiences to make the creation of SLO’s a walk in the park. Introducing: The SLO Creation Tool.</p><h4>The Requirements</h4><p>Once we started to discuss the actual implementation we decided that the final solution needed to address a few key points:</p><ul><li><strong>Short and sweet.</strong> It should be simple enough that anyone at Product &amp; Engineering should be able to create an SLO. It was clear to us that if only product managers or only engineers could use the tool it would not work out, because everyone should be involved in the process. As well, it should not take a lot of time to create an SLO. We knew that if people felt productive with it, they would be more likely to use it again.</li><li><strong>Integration with our tech stack.</strong> It was really important to us that the SLO Creation Tool would be able to use tools that we already had to gather the required information and create the SLOs. This way we were not imposing a new tool for the team to adopt, making it easier to integrate into existing ways of working.</li><li><strong>Review process.</strong> As we mentioned previously, we wanted everyone to be involved in the process. Therefore, we decided that there should be a review process for SLOs so that the team that created the SLO could discuss it and make changes until they were happy with the result.</li><li><strong>SLI Menu.</strong> We got this idea from Google’s workshop: The Art of SLOs. For us, it meant making it as simple as possible to select an SLI, just as it is choosing food looking at a restaurant’s menu.</li></ul><h4>The Solution</h4><p>We are surely proud of the solution we created. We felt that it managed to address the key points mentioned above. In general, it took <strong>less than 5 minutes</strong> to be able to create an SLO (excluding the review &amp; discussion). Something that we believe was key to this, is that the tool is divided into multiple steps. This gave us the ability to give users a powerful explanation of what they should do at any point in time, as well as making sure that they would not feel overwhelmed by all the information in front of them.</p><p><strong>Introduction. </strong>In the next image, you can see the introduction to the tool. In this step, we could give users a good overview of the tool and they could see there were only 5 steps between them and a brand new SLO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zxeWnWAvoE3O4HRX" /></figure><p><strong>Basic info. </strong>In the first step, shown in the next image, we just ask for the basics: application name and user flow name. The cool thing about this step is that we retrieve a list of all the applications that have data on New Relic (our performance tracking solution) so you can easily pick the application you want to create an SLO for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JeFJvjK2Cx6O20MH" /></figure><p><strong>SLI Menu. </strong>As mentioned before, the SLI Menu was a key focus point of the solution. First, we needed users to understand what an SLI is and how to choose one. As well, it was very important for us to not be too ambitious and add too many SLIs at first, which would probably have decreased the quality of the application. Therefore, we went with Latency and Availability as our first SLIs since we believe these are the easiest to understand for anyone that is just getting started.</p><p>As you can see in the next picture, we also added a short but precise high-level description, which together with the UI makes it feel like an SLI Menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I5Ln620seIF6bXoR" /></figure><p><strong>Events. </strong>After the SLI Menu, we added the last setup step, before actually creating the SLO. In the Events step, users can select the HTTP methods and paths included to measure the SLO against.</p><p><strong>Choosing the SLO. </strong>This was by far the step that took us the most time to feel that we got it right. It needed to encapsulate the previous information, follow the SLO specification that we defined, and be able to ask for the required information of each SLI. To achieve this, we decided to split this step into substeps when more than one SLI was selected. This decision allowed us to add more meaningful information for each SLO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*APrl22vBprXhA2-v" /></figure><p>As you can see in the above, below the input field there is a sentence that contains the whole SLO, putting everything together in a very visual way.</p><p>The next image shows something crucial about SLOs: 100% is never a good choice. We wanted to share this statement at the moment it mattered most, linking to a section of Google’s SRE Workbook about <a href="https://landing.google.com/sre/workbook/chapters/implementing-slos/#reliability-targets-and-error-budgets">Reliability targets and Error budgets</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/0*Tl-2BZ5Ug9S2KS3h" /></figure><p><strong>Review. </strong>The only thing remaining was showing the user a preview of their SLO, before they submitted it for review. We decided that the simplest solution for reviewing was to use GitHub. It was already integrated with the workflow of Product &amp; Engineering and it has strong review capabilities.</p><p>Having an SLO on Github allowed for the team to discuss it and together improve it to a point where everyone was comfortable with it. This process ensures that the whole team is involved since there might be many different ways of measuring an SLI and mostly, it is important to be in sync when setting an Error Budget.</p><p><strong>Push to Dashboard. </strong>Last but definitely not least, once the SLO was merged, the tool allowed users to create a dashboard for it on New Relic with just a single push of a button. Having a way to visualize an SLO is what really made the teams feel that they achieved something. They could monitor how the application was actually performing against their SLO and tweak the values if necessary.</p><p>This also was the most important step to make sure the SLO provided its (future) value and that it was not just a one-time thing. By having it as a dashboard that can be easily reviewed, and displayed in all kinds of places, it really acquired a place in the teams’ ways of working.</p><h3>Results</h3><p>Looking at what we wanted to achieve, we definitely succeeded. But as with any software that you develop, there are some things you are proud of and less proud of.</p><h4>Proud of…</h4><p>Within just one month, we were able to create a tool that enabled teams to create SLO’s and generate corresponding dashboards in a matter of minutes.</p><p>This also paid off in the amount of SLO’s that were created, and the dashboards you would see around the office floor. By giving all teams a TV for monitoring purposes, now SLO’s and performance graphs were popping up on the screens. Which helped to create awareness about Reliability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fc3N-0wzK5DeP1shjttCLw.jpeg" /><figcaption>An example of the SLO dashboard of the AdTech team.</figcaption></figure><p>Now at least each week the team reviews the dashboard and sees if any action needs to be taken. Which is easy — if its red (so below the SLO) — it needs attention. There is no discussion because all of the bickerings if something is (too) slow or if it is really that bad for the user, already happened when you defined the SLO <strong>as a team</strong>.</p><h4>Less proud of…</h4><p>While we put a lot of effort into advocating SRE, it took quite some time. And as a team we still think we should improve. In hindsight our efforts fell short in that we took a pretty bottom-up approach, advocating towards our peers (the other teams), without a lot of pressure from “above”. Only after we created the tool and the creation of SLO’s was acknowledged in our department goals, it really took off.</p><p>Another thing is that the tool is crazy scalable, but after all the amount of teams and services that use the tool is limited. Onefootball is not the biggest company, so such a sophisticated tool might be an overkill. But we do believe that the investment was small enough to justify it. And who knows, maybe other companies can take some learnings from it and expand on the idea or maybe even in the future we can think of open-sourcing it?</p><h3>Conclusion</h3><p>We hope the article gave you some insights and inspiration from how we improved the SRE mindset at Onefootball, and how we use SLO’s to ensure a reliable experience for our users. To wrap it up, we would like to end with the following key takeaways:</p><ul><li><strong>SLO’s can be complex but it is possible to make it understandable for everybody.</strong> We recommend to start SLOw. Starting with a couple of SLI’s and maybe the “easier” applications. That is why for example we started with the HTTP focused SLI’s and the backend services that already had some instrumentation implemented.</li><li><strong>If you want to change a mindset, you need to make things easy.</strong> Before we introduced the tool we had quite some discussions with teams, and although they fully understood the concept, it was still too complex for them to actually “implement” it and make it part of their Way of Working. By using existing tools and integrations we were able to connect the dots already for them.</li><li><strong>For any change you need “management” support. </strong>Bottom-up change is admirable, but also very hard. You need to address it from both sides. In the end as P&amp;E there was a goal set (top-down) that we defined SLO’s for all critical services. This created at least some urgency and illustrated that management supported it. Conclusively we believe it was still (too) limited to really move towards an SRE mindset, but maybe it was fair to say that as Onefootball it was not the biggest problem that we had.</li></ul><p>Always share what you think, and let us know if you are interested to know more about the tool!</p><h3>References</h3><ul><li><a href="https://landing.google.com/sre/books/">SRE Book: free online version</a></li><li><a href="https://medium.com/onefootball-locker-room/life-at-onefootball-scary-close-to-fully-autonomous-teams-1293d9ede4b">Life at Onefootball: scary close to fully Autonomous teams</a></li><li><a href="https://landing.google.com/sre/resources/practicesandprocesses/art-of-slos/">Art of SLO’s: workshop resources</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LeupW3-PCDH8EA_T9TqwXQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42acb8145ca9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/onefootball-locker-room/making-slos-fast-42acb8145ca9">Making SLOs Fast</a> was originally published in <a href="https://medium.com/onefootball-locker-room">OneFootball Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Teams: striving for Autonomy & reaching for Business Agility]]></title>
            <link>https://jimvdwaal.medium.com/product-teams-striving-for-autonomy-reaching-for-business-agility-e9311ffb7dbe?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9311ffb7dbe</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[team-organization]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Tue, 12 May 2020 06:22:43 GMT</pubDate>
            <atom:updated>2020-05-12T06:22:43.424Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9GoqPwRGkW7mIDu2ztvIzQ.png" /></figure><p><em>Within The Netherlands, </em><a href="https://careers.bol.com/tech/"><em>bol.com</em></a><em> is known for being an early adopter of agile practices and has been an example for a lot of companies in their (agile) transformation. But while I was working there as a product owner I still felt that we were not quite there yet regarding agility.</em></p><p><em>The main struggle I faced was the lack of end-to-end responsibility of a software development team hence for me as a product owner. But as I never had the hands-on experience of working with full-blown multidisciplinary teams with end-to-end responsibility myself, was it fair that I said we should change?</em></p><p><em>Then the opportunity came to work at a company that was working in this fashion, the company I currently work for, </em><a href="https://onefootball-company.netlify.app/about"><em>Onefootball</em></a><em>. And although the companies are not comparable (2000 vs 200 employees, 100 vs 5 engineering teams), I am truly convinced: every company should try to organize their teams to have end-to-end responsibility. I call them: product teams.</em></p><p>In this article, I try to explain what I mean with product teams and the reasons why I think every company should strive for them. Then amplifying these arguments with some of the anti-patterns of non-product teams.</p><p>I know a lot has been written about this subject and it has been called a lot of different names. So keep in mind that this is just my way of explaining things, based on my experiences, and I hope it can help you to reflect on your own situation.</p><h3>Product Teams</h3><p>When I picture a Product Team, I think about a team that has all kinds of different <strong>roles </strong>within the team, that is fully <strong>autonomous</strong> and that has a clear <strong>customer </strong>(focus).</p><h4>Multidisciplinary teams</h4><p>Probably a term you heard before. For a team to be autonomous you need to have all the expertise in place, and ideally, all these crafts have a dedicated spot within the team. This does not only mean being able to cover the entire technology stack (front-end, backend, infra) but also being able to design solutions, doing user research, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9GoqPwRGkW7mIDu2ztvIzQ.png" /><figcaption>A multidisciplinary product team with all kinds of roles.</figcaption></figure><p>Does this mean one or multiple FTE’s for each expertise/role? Maybe, maybe not. This comes down to practicalities and nobody can say without knowing your situation what will be the best way of organizing it. But it means that the team should have access to all the expertise at the time the team needs it.</p><p>What you can read between the lines here is that this also means that “business” and “IT” are working together as one team. Or at least that these two teams are so aligned that they can operate as one team, working together on a daily basis and being able to make decisions fast.</p><h4>Autonomy enables Continuous Innovation</h4><p>With end-to-end responsibility I mean teams being responsible all the way from idea generation until the customer feedback (looping back to idea generation). And giving them the tools to make all the decisions regarding their product themselves. Full autonomy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wdw2ydmvO7gX5bQ4yzzvhw.png" /><figcaption>Product Teams are responsible for both the Discovery &amp; Delivery of their product.</figcaption></figure><p>Why would you want to give your teams autonomy? Well if you ask that question, it makes me a bit sad, but okay… I will bite. There is a lot written about this already, but for me there are two main reasons: <strong>agility</strong> &amp; <strong>drive</strong>.</p><ul><li>If you are not new to the agile world, you probably know that to be really innovative and moving forward in a fast-changing world, you need to be able to respond fast: to be agile. The more you empower teams to make decisions themselves, the easier it is for them to respond while working on the product.</li><li>Empowering is not only good for your business, it is also good for your people and their motivation. If you haven&#39;t done so already I would highly recommend reading the book <a href="https://www.amazon.com/Drive-Surprising-Truth-About-Motivates/dp/1594484805">Drive</a> of Daniel Pink. He explains very well what motivates people, and surprise surprise, one of the three factors is <strong>autonomy</strong>.</li></ul><h4>A Product has a Customer</h4><p>Why do I call it product teams? Well, that is simple: you are responsible for a product. A product that has customers. You know, those people who you try to create value for. The people who determine what you do and the reason for existence as a team or even as a company.</p><p>Although that sounds obvious, it might not always be the case. Too often I heard teams naming all their (software) services or API’s when answering the question for what product they are responsible for. And although there are cases where this is actually your product, and the people/developers consuming your API are actually your customers, most of the time it is just blurring your real end-user.</p><p>If you get to the point where you cán identify your (end-)customer, where you cán talk to them and start to really get to know them, you should be very happy. All of a sudden it becomes so much easier to improve your product. You can use real-life customer feedback from yesterday to improve the product today and have happier customers tomorrow. Yes, that sounds like the agile dream, but with modern software practices, it can be a reality.</p><blockquote>You can use real-life customer feedback from yesterday to improve the product today and have happier customers tomorrow.</blockquote><p>And again I will refer to Daniel Pink. Next to autonomy he also mentions <strong>purpose</strong> as a motivator. People want to make an impact and most of the time this means an impact on other people (and their lives). I can not tell you how fulfilling it is to release something and have a customer tell you the next day how happy he or she is. Or the other way around: how motivating it is to hear customer problems, real struggles from real people, and being able to solve/work on them the next day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qHYRBLRXzJtJeegNsp9SZQ.jpeg" /><figcaption>A real customer giving suggestions based on his struggles with the product.</figcaption></figure><p><em>At my team at Onefootball, we have a slack-channel where customer feedback is coming in real-time (using a Usabilla integration) which is highly motivating/rewarding, to say the least.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OtCRzuo9r4Qy0a5cIVlmoQ.png" /><figcaption>A user who shows his appreciation for the new search feature.</figcaption></figure><h3>Antipatterns of Non-Product Teams</h3><p>Sorry, I don&#39;t have a very creative way of describing &quot;non-product teams&quot;. Teams that are not organized based on (customer) products but something way more practical, like based on a certain skill set, the size of the team, or on the software architecture that is already in place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Wkj7h7sMkRYkKyq66B8Yg.png" /><figcaption>A common team structure for larger companies with more teams and more customer types.</figcaption></figure><p>In those teams it will be super hard to really work autonomous as a team and also to feel the connection with the customer, affecting the agility and the motivation of a team. Because what happens with the customer feedback? And how are new ideas introduced? Most of the time this needs some kind of coordination or governance structure, caused by the dependencies between the teams.</p><h4>The Idea Waterfall</h4><p><em>We live in an ever-changing world and that is also very true when it comes to software development. I don’t want to pretend like I am some dinosaur who has seen it all and say things like “remember the time…” but… well, fuck it, I will do it anyway: remember the time where teams were only responsible for the development of their software and not for deploying and running it?</em></p><p><em>I experienced the DevOps movement first-hand and it was the next step in working agile at bol.com. Teams taking responsibility for the </em><strong><em>delivery ánd the operations</em></strong><em> of their software. It was awesome to get this autonomy as a team. There is a reason why we said: </em><a href="https://techlab.bol.com/agile-journey-far-part-3-build-run-love/"><em>You build it, You run it, You love it</em></a><em>.</em></p><p>So now picture these super agile (software development) teams. Working sprint by sprint, user story by user story, developing software, deploying it to production, and making sure it keeps on running smoothly. Isn’t that what autonomy is all about?</p><p>But what about this phase before the development starts? What if the <strong>discovery</strong> for ideas is not the responsibility of the team that also does the implementation? What if there is an entire (business) team of people working on ideas, figuring out what the value is of solving a certain problem, or developing a certain feature. Where this team is building business cases for weeks if not months, only to then pitch it to a manager or product owner of a team who needs to give them the bad news: sorry our roadmap is already full.</p><p>How do you make sure you get their attention and get it on the roadmap? Well, you can do two things: make your idea bigger (they need to pay attention to the next big thing right?) or maybe just picture the numbers and value a bit better, I mean.. otherwise all the work you put into was all for nothing.</p><p>I hope it is obvious what the risk is of this idea waterfall.</p><ul><li>People will work weeks or months on something that will never be implemented.</li><li>The ideas will become huge projects.</li><li>And if they are actually going to be as valuable as projected, well.. let’s see. Because probably there was also no time for an experiment right?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yb66PxUMk2iJ1VqGoOT4LQ.png" /><figcaption>The risks of disconnecting the discovery and delivery between different (business &amp; IT) teams.</figcaption></figure><p>This is exactly why you need to treat this discovery phase as a funnel. Not all ideas should be researched, not all ideas should be prototyped or experimented with. This elimination can be done before you decide not to implement something. For that reason it makes the most sense to give the <strong>ownership</strong> of this discovery funnel to the same team that is responsible for the delivery. Because they know their velocity best, and they know when there is a big need for new ideas or when it’s best to spend your energy elsewhere.</p><h4>Blurry Customers</h4><blockquote>Too often I heard teams naming all their (software) services or API’s when answering the question for what product they are responsible for. And although there are cases where this is actually your product, and the people/developers consuming your API are actually your customers, most of the time it is just a dependency in disguise. With your real customer out there somewhere, but the view and connection to them “blocked” by another team.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mDlcEn7hDeiAlx3zabc_jQ.png" /><figcaption>Team A might be less aware of their (end) customer.</figcaption></figure><p>If you want teams to have end-to-end responsibility they need to be able to identify the product they work on and the value they create for… <strong>the customer</strong>.</p><p>In the way of working I described earlier, it will be really hard to handle small requests based on user feedback. Because with the “discovery team” responsible for the <strong>innovation</strong>, and the “delivery team” for the <strong>operation</strong>, what happens to <strong>optimization</strong>?</p><p>If the user feedback will be heard by the delivery team at all, they probably have no time to implement it. Because how can this user feedback compete with all these big ideas that people have been working on for weeks or months? And how are you going to organize it with all the dependencies with the other teams to make this happen?</p><p>Sometimes you will see a pattern that teams have <strong>optimization</strong> <strong>weeks</strong>, time that some product owners or teams probably had to fight for. Handling all these piled up small requests and trying to implement as many as possible. Different teams working together and bringing value with incredible speed. If you ask any team that experienced such a week, they loved it. They could work on something they know that sucked and customers have complained about for months or years.</p><p>My point is that although these are incredible initiatives and I credit and applaud any person that starts them, they should not be needed. Teams should be able to make the decision to pick up a story based on customer feedback they got, in-scope it in their sprint, and get it done. This should not require any pitching of time, or any hard coordination or process.</p><p>Because come on… if you wake up as an engineer, a designer, or any other role within a team, and you want to improve your product and make an impact on your customer, but you don’t because it will take too much of your energy to coordinate… there really is room for improvement.</p><h3>How to create Product teams</h3><p>So I hope by now I could convince you a little bit that product teams are the way to go. And if you want to move towards product teams, why not organize them around the <strong>products</strong> you have?</p><p>For small companies this is simple, it might be the entire product. But how do you do it for large organizations? Do you split it by feature? Do you split it by customer type? I will not pretend I am some kind of team organization expert, but there is a lot of good theory about this ever-interesting topic. I would really recommend reading the book <a href="https://teamtopologies.com/?gclid=EAIaIQobChMIl7SAy7nx6AIVluvtCh0gkAElEAAYASAAEgICR_D_BwE">Team Topologies</a>. It gives a simple framework explaining the different nature of teams and guidelines on how to organize your teams, combining all the existing theories out there.</p><p><a href="https://www.linkedin.com/posts/jimvdwaal_team-topologies-workshop-with-manuel-pais-activity-6598611721546448896-7MsC">Jim van der Waal posted on LinkedIn</a></p><h3>Wrapping it up</h3><p>I hope I could share some of my passion for product teams and inspire you with some of the (anti-)patterns I have seen and have experienced. I know it’s not an article that will guide you in re-organizing your teams but I hope it did trigger you to think about how you can improve your own setup, strive for autonomy and reach for business agility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aGPEjVjJhA1mQuEXw5waow.png" /></figure><p><em>At bol.com I noticed already that I was not the only one who questioned our team setup. So I playfully promised a group within bol.com that I would come back to share my first learnings with them, which I did. I gave a talk at the conference of bol.com: </em><a href="https://techlab.bol.com/spaces-summit-launching-for-the-3rd-edition/"><em>Spaces Summit</em></a><em>, which you can watch below.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fzmyh7TLHlsQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dzmyh7TLHlsQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fzmyh7TLHlsQ%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/3a1acdf62f131f59d08ca3a6ba4750cb/href">https://medium.com/media/3a1acdf62f131f59d08ca3a6ba4750cb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9311ffb7dbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life at Onefootball: scary close to fully Autonomous teams]]></title>
            <link>https://medium.com/onefootball-locker-room/life-at-onefootball-scary-close-to-fully-autonomous-teams-1293d9ede4b?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/1293d9ede4b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development-team]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[team-organization]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Tue, 05 May 2020 16:45:31 GMT</pubDate>
            <atom:updated>2020-05-05T16:45:31.818Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This talk was given last year at the Spaces Summit, an internal conference of </em><a href="https://careers.bol.com/about-us/who-is-bol-com/"><em>bol.com</em></a><em>. Sharing my first experiences on how we work at Onefootball, focused on Product &amp; Engineering. Explaining how our teams are organized, giving insights in our ways of working, and giving my opinion why this is working so well.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fzmyh7TLHlsQ&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dzmyh7TLHlsQ&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2Fzmyh7TLHlsQ%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/4f01f342da099c5bc08b1cd6e18392ff/href">https://medium.com/media/4f01f342da099c5bc08b1cd6e18392ff/href</a></iframe><h3>Summary</h3><p>Below you can find a short summary of the talk, a TL;DW, highlighting some of the important points.</p><h4>Onefootball</h4><p>We are a very international <a href="https://company.onefootball.com/">company</a>, with around 200 people we are building the ultimate Football platform for fans. Bringing together all content so that you only need one (digital) product.</p><p>We have a lot of loyal and active users around the world. With more than 11 million Monthly Active Users (MAU&#39;s), with an average of 50 sessions per month. Illustrating the football fans and our product being part of their routine.</p><h4>Team organization &amp; Way of working</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZZgDbi2q6LOyuq8P1xXeug.png" /></figure><p>Within Product &amp; Engineering, we are working with multidisciplinary Product teams. It depends on the product which disciplines are within the team, but in the end it will result in different types of engineering disciplines, design &amp; product, working together in one team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E5OOH_VrEpP8CVAsPj5oOw.png" /></figure><p>At the time we have different domains (News, Scores, Platform), with different product teams in each domain. Where each team has end-2-end responsibility for their product. Both of the discovery (determining the most valuable ideas) and the delivery (implementing it for the users).</p><h4>Why this is so awesome</h4><ul><li><strong>Purpose: </strong>with this setup, you can really focus on the customer and make a direct impact on them.</li><li><strong>Autonomy: </strong>as a multidisciplinary team we are working with Business + IT (or Product &amp; Engineering) together as one team and really have autonomy.</li></ul><h4>Why this is needed</h4><ul><li><strong>Customer focus: </strong>you need to balance innovation, optimization, and operation. This is only possible if you have full responsibility and autonomy as a team, making these decisions based on what is best for the customer.</li><li><strong>Continuous Innovation: </strong>true business agility comes from the ability to test ideas, adapt fast to different opportunities, which can only be done if you are also responsible for the discovery.</li></ul><h4>Our own challenges</h4><ul><li><strong>Startup &gt; Scaleup: </strong>growing as a company comes with its own challenges, where not everybody can be involved everywhere anymore.</li><li><strong>Bottleneck can shift: </strong>where normally the bottleneck is on the development, now also the bottleneck can be the analysis and discovery capacity within the team.</li><li><strong>It&#39;s a mindset change: </strong>you really need to become outcome-driven. This way of working means that sometimes as an engineer you will write less code. If you don&#39;t focus on the outcome this can feel unproductive.</li></ul><p>For more examples and illustrations, watch the talk! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1293d9ede4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/onefootball-locker-room/life-at-onefootball-scary-close-to-fully-autonomous-teams-1293d9ede4b">Life at Onefootball: scary close to fully Autonomous teams</a> was originally published in <a href="https://medium.com/onefootball-locker-room">OneFootball Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Perfect Job Opportunity]]></title>
            <link>https://jimvdwaal.medium.com/the-perfect-job-opportunity-f9b62c42fe5a?source=rss-e240d3eb58------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9b62c42fe5a</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Jim van der Waal]]></dc:creator>
            <pubDate>Thu, 30 Apr 2020 10:10:40 GMT</pubDate>
            <atom:updated>2020-04-30T10:10:40.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*Fdvlo5h-DO39bGXF" /></figure><p><em>This article is part of a series regarding Personal and Career development. It elaborates more on the “opportunities” of the </em><a href="https://medium.com/@jimvdwaal/a-way-to-think-about-career-personal-development-7c7b42aabf24"><em>earlier discussed framework</em></a><em>. It dives deeper in how to look for job opportunities and a way how you can analyse them.</em></p><p>In the end we don’t need to forget that your career is also there to make a living, making sure you can pay the bills (and probably all your fun holidays next to it). But we want to do this in a fun and fulfilling way. The article about <a href="https://medium.com/@jimvdwaal/creating-your-own-profile-81578f6a8f97">your profile</a> focuses on discovering on what would make a job fun and fulfilling. But if there are no (job) opportunities out there that match them, it’s hard to get to that point. There is a reason why not everybody is doing charity work, how fulfilling it might be. So what are these opportunities? And how can you pursue them? Looking for this sweet spot where the opportunities out there match your interests and skills. And how do you assess what’s the best opportunity to take? In this article I try to give some tips and also provide a little framework that might help to assess job opportunities.</p><h3>A way to think about Job Opportunities</h3><p>So you searched hard for job opportunities, or maybe you got approached by a recruiter. What makes it a good opportunity? Is it the salary? Is it the job/role? Is it the company? Is it your future manager? There is a very simple answer: yes.</p><p>After assessing some job opportunities for myself. And after doing quite some coaching conversations with students who were all in the middle of the same search: getting that perfect first job, I saw a certain pattern. I would like to share this pattern which I converted to a little Venn-diagram/framework (did I mention I love conceptual frameworks?). You can see it below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/0*hsNqOib2UETsV2_1" /></figure><p><em>Note: I see salary and other perks (holidays, etc.) as a constant that needs to be met. Like a hygiene factor. You need at least a minimum salary to consider it. Above that level it will probably not be a decisive factor for whether it’s a good fit. At least I think it shouldn’t be, but some may argue.</em></p><h4>Job / Role — doing something you like on a daily basis.</h4><p>The <em>job</em>, <em>role</em> or <em>position</em> reflects on what your daily work and responsibilities are. It’s often the thing you will see online as a vacancy. I think it’s quite straight forward. You want to do something that you like, something that gives you energy, on a daily basis. If the opening describes “You will visit clients all over the world.” and you hate traveling, then it’s probably not a good fit. Make sure you get a good view of what these daily responsibilities are.</p><h4>Culture &amp; People — working in a nice environment.</h4><p>This is not all about the best company parties (although it does say something). It’s more about how the company goes around, the people that work there, and how they interact with each other. A culture can be very important. On the one hand for what matches your personality but maybe also what matches the stage of your career. If you are looking for a first job I think personally that it is really important to look for a company that has a culture that stimulates personal development and growth. A company that for example stimulates mobility within the company, that has very proper guidance and coaching, and lets you try out new things.</p><p>For me I was lucky. Bol.com was growing and the culture was very dynamic. This really suited my personality in a way that each day was different and as soon as I thought I was going to be bored, there was always a new opportunity (and I was motivated to take it). But for some people this dynamic culture will also feel chaotic. Re-organizing each year, teams that change composition constantly, let’s just say there was a lot of change. And some people like a little bit more consistency. Which is fine. Be honest with yourself. Again the culture is a personal preference.</p><h4>Company &amp; Product — feeling connected.</h4><p>This is illustrating what the purpose and the products of the company is, and if you feel connected to it. Sometimes this subject is overlooked, but I think nowadays with movements like “<a href="https://startwithwhy.com/">Start with Why</a>” it gets more attention. We all want to make an impact, but what this impact is and what we want it to be is different for each person. Having a connection with the products or services you are working on will definitely help in feeling like you made an impact. An easy example is a charity organization. If you are passionate about animals you will probably feel very connected to the WWF, and actively working on fulfilling its goals will definitely make you feel like making an impact. But let’s take a more personal example. For me to <a href="https://www.linkedin.com/feed/update/urn:li:activity:6500380783566557184">go and work</a> for a company that works on products for football fans, combining tech and football, is definitely a good fit for a football fan like myself.</p><h3>Creating your perfect job opportunity</h3><p>So how would your perfect job look like? What kind of activities would you do on a daily basis? On what kind of products/services and goals would you be working? And what kind of culture would there be while doing that? Again why not try to make a profile for yourself answering these questions. Making it concrete again.</p><h4>Assessing job opportunities</h4><p>This is where it should come in handy. If you are going to compare jobs/positions/whatever, just think about these different perspectives. Create the different “job profiles” and why not compare them with your <a href="https://medium.com/@jimvdwaal/creating-your-own-profile-81578f6a8f97">own profile</a>. Or compare them with each other and see which one speaks to you the most.</p><p><strong>Some ways/tips for doing research:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*0su-H4JqCiNBK7UX" /></figure><p>In a career there are probably many, many, many opportunities that pass by. Some handed to you, some you searched and fought very hard for. These opportunities can be new jobs, new companies, you name it. But let’s assume you are now in a position where you are looking for a new job, or you are looking for a better fit. How do you do this, how do you start your search? If you are an accountant and happy with the role it’s easy. Google “accountant jobs” and there is probably a list of job openings from various companies. But what if you are a student and studied Business Administration like myself. It is not really if you were educated for a particular role. Maybe CEO or Entrepreneur comes close, but they are not really starting roles. So I think the best way to get started is just start your research. Start broad and try to narrow it down later.</p><p><strong>Some ways/tips for doing research:</strong></p><ul><li>Of course.. The internet. There are so many ways to start. Just go to companies that speak to you and see what kind of openings they have. Open LinkedIn and start your research in what kind of openings there are out there. There is a lot of input and it can all help to further shape your perfect job. In the end it’s as simple as: if you are reading the job description, do you think: is this something I can see myself doing?</li><li>Drink lots of coffee with people. Build up a network and ask people if they are up for a cup of coffee where they can tell more about their job. You will be surprised at how many people will accept this offer. And if they don’t, you probably don’t want to talk to them anyway. Because you want to speak to people who are passionate about their jobs, and people who are passionate about their jobs don’t mind drinking coffee with strangers and talking about it. Trust me. I sat on both sides of the table now. During these conversations you will learn a lot about how their daily jobs really look like. And you will definitely notice if it speaks to you or not. And having a personal connection with this person also says something. Because if you are alike, and he or she is enjoying his or her job, you will probably too.</li><li>Drinks lots of coffee with people. I am just stating it again. Because I know that this tip can be a bit “out of your comfort zone”. Cold calling, sending messages on LinkedIn just feels stalkerish. But just do it. One of the biggest benefits of this is also the network you’re building up. All of these persons can also look out for jobs for you in the future. And again if they are passionate people they will really help you.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*M9N896884mVW7JA2" /></figure><h3>Some last remarks</h3><p>I want to end with a note that maybe deteriorates the conceptual framework, but… It’s not an exact science. In the end you need to go for a job opportunity that feels good. The “theory” above should just help to quantify that gut feel a little bit.</p><p>Also, don’t let the search freeze you. I had a coachee who was so busy looking to get the perfect first job that he wanted to do some extra internships after his studies. And although I really admired his ambitious goal of doing something he loves from the beginning, you should also just start. We live in a time where switching jobs is normal. And during your first job you will probably learn so many new things about yourself and about companies/jobs in general, you can better start in what might be a lesser perfect first job.</p><p>Again, hope this all helps to think about your career and to get a job that you are passionate about!</p><blockquote><em>Imagine a world in which the vast majority of us wake up inspired, feel safe at work and return home fulfilled at the end of the day.</em></blockquote><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/perfect-job-opportunity-jim-van-der-waal/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9b62c42fe5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>