<?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 Robert Lippert on Medium]]></title>
        <description><![CDATA[Stories by Robert Lippert on Medium]]></description>
        <link>https://medium.com/@robsblog?source=rss-9ecb1ce89a97------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OTEPs7SnAowD71EhS8kpdA@2x.jpeg</url>
            <title>Stories by Robert Lippert on Medium</title>
            <link>https://medium.com/@robsblog?source=rss-9ecb1ce89a97------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:50:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@robsblog/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[To foster, where we disagree]]></title>
            <link>https://medium.com/@robsblog/to-foster-where-we-disagree-71d6246caad0?source=rss-9ecb1ce89a97------2</link>
            <guid isPermaLink="false">https://medium.com/p/71d6246caad0</guid>
            <category><![CDATA[peer-review]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[team-development]]></category>
            <dc:creator><![CDATA[Robert Lippert]]></dc:creator>
            <pubDate>Fri, 08 Jun 2018 14:53:03 GMT</pubDate>
            <atom:updated>2018-06-08T14:53:03.111Z</atom:updated>
            <content:encoded><![CDATA[<h4>Peer Review: Identify, nurture and reflect on your skills</h4><p>In a previous article, I described a method for <a href="https://medium.com/@robsblog/how-to-mature-as-a-scrum-master-while-keeping-focused-on-your-project-38a4e6569257">maturing as a Scrum Master, while keeping focused on your project</a>, as a flexible model to identify and to nurture relevant skills, without loosing yourself in theory. (Not only for Scrum Masters.) Basically a combination of the <em>Kano model</em> to prioritise skills and the <em>Peer Review</em> technique to nurture them with feasible action items.</p><p>Here, I am going to describe a typically Peer Review, the way we conduct it at <a href="https://mayflower.de/">Mayflower</a> for the advanced training our Guilds of Scrum Masters and Product Owners, or as one approach for our in-house coaching affairs.</p><p>This will be a How-to — feel free to use it as a template for your own Peer Reviews.</p><p>There is a <strong>tl;dr;</strong> in form of an agenda at the end of this article.</p><h3>Timeframe and teammates</h3><p>I recommend a timeframe of 90 minutes. This is suitable for up to four people (one reviewgee and three peers). (Reviewgee is not a word.)</p><p>The person being reviewed should pick her/his peers. The peers should not consist of direct colleagues, only — while it is useful, that at least one peer has an advanced knowledge on the topic being discussed, diversity is key in a Peer Review, as well as everywhere else. A suitable peer knows, what you are doing, or is directly affected by your work. (Out of experience: a trainee may be as “useful” as a senior member, so do not be afraid of inviting “less experienced” people — usually it’s just “less time spent with your company”, than “less experience”. ;-)</p><p>Please keep in mind: While having less than three peers in your group is totally fine (you need at least one peer for obvious reasons), more than four peers won’t add much additional value and probably will just mess with your timeframe.</p><p>Key: 90 minutes. One person being reviewed. Up to three peers.</p><h3>Setting the stage</h3><p>I want to be honest with you — I always want to skip this part, because I always feel like “hey, everyone knows, why we are here, so what’s the point of a formal introduction to this meeting? Can’t we just be friends and have a chill?”</p><p>No, you can’t. While it <em>feels </em>cheesy to the host, setting the stage formally will kind of “frame your audience”. That is: your peers will understand the purpose of this meeting and as a result, they will stay focused and engaged with the peer review. (This is, why you never want to skip the setting the stage part in any meeting, by the way.)</p><p>Key: Welcome everyone to the party, explain, why you are facilitating the peer review (here: to compare self-perception with the perception of your peers, so that you will be able to spot the differences, which are key to improve upon further iterations) and ask for the expectations of your peers.</p><h3>Peer Review</h3><p>For each item (here: each skill), that you want to get reviewed and to improve, there are five simple classifications. So in the peer review, you present your skill/item and describe it — and then ask your peers, how they would rate them on a given scale.</p><p>This scale ist:</p><ul><li><em>Role Model</em>: There is a given track record and we can name examples and people, who got inspired by them. These people name you as a role model for the given category.</li><li><em>Maker</em>: There is a given track record and we can name examples.</li><li><em>Teammate</em>: There are a few examples and few people now them.</li><li><em>Padawan</em>: We can name one example and a few efforts in the right direction.</li><li><em>Spectator</em>: There are no examples and personally, one is interested in other areas of interest.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9hBHFgDpAH8mdc4XYjzdQ.jpeg" /><figcaption>We may, or we may not have Star Wars inspired cards for the Peer Review process.</figcaption></figure><p>Please, keep in mind: it is not important, where you rank in particular, but where you and your peers differentiate the most. It is the delta on your perception giving you a hint, where you should focus on with future efforts.</p><p>If there is a delta — come to an agreement on how to improve the situation with a suitable action item, in a second step.</p><h3>Review &amp; Closing</h3><p>After you went through your skills/items being reviewed (or you have reached the end of your timebox), I recommend to take the opportunity to take a step back and to review your elaborated action items.</p><p>Regarding the timeframe (let’s say, three months until the next peer review) and the overall workload (your daily business lurking around) — on what action item do you want to commit yourself to?</p><p>Write down/document this commitment, so you can track your progress over time and over the following peer reviews.</p><p>Try to match these results with everyone’s expectations, as stated in the setting-the-stage part.</p><p>Be brave enough to ask for feedback on the peer review meeting, so that you get a hint on where to improve your methodology for the next execution. A simple ROTI (Return On Time Invested) should be sufficient.</p><h3>How-to Peer Review</h3><h4>tl;dr;</h4><ul><li><strong>Timeframe &amp; teammates</strong><br>90 minutes. One person being reviewed. Up to three peers.</li><li><strong>Setting the stage (5 minutes)<br></strong>Welcome everyone to the party, explain, why you are facilitating the peer review (here: to compare self-perception with the perception of your peers, so that you will be able to spot the differences, which are key to improve upon further iterations) and ask for the expectations of your peers.</li><li><strong>Peer Review (up to 80 minutes)<br></strong>Present each of your our skills/items and describe it — and then ask your peers, how they would rate them on a given scale. If there is a delta — come to an agreement on how to improve the situation with a suitable action item, in a second step.</li><li><strong>Review &amp; Closing (5 minutes)<br></strong>What action item do you want to commit yourself to (timeframe: 3 months)? Then ask for feedback on the peer review meeting (ROTI).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Py-wtw9H1rwLQwWT3BpVw.jpeg" /><figcaption>I just love this image by Mitchel Hollander (via Unsplash). Scrolling down to the end of this article, watching the hands disappear into a void makes me want to share and to clap these hands … ;-)</figcaption></figure><p>Curious about details, mad about something or happy to share your own ideas? Feel free to add a comment, to follow <a href="https://twitter.com/robsblog">@robsblog</a> on Twitter or contact me via <a href="http://www.linkedin.com/in/robertlippert">LinkedIn</a> or <a href="https://www.xing.com/profiles/Robert_Lippert">Xing</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71d6246caad0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to mature as a Scrum Master, while keeping focused on your project]]></title>
            <link>https://medium.com/@robsblog/how-to-mature-as-a-scrum-master-while-keeping-focused-on-your-project-38a4e6569257?source=rss-9ecb1ce89a97------2</link>
            <guid isPermaLink="false">https://medium.com/p/38a4e6569257</guid>
            <category><![CDATA[peer-review]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[talent-management]]></category>
            <dc:creator><![CDATA[Robert Lippert]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 13:51:20 GMT</pubDate>
            <atom:updated>2018-06-08T14:55:12.244Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>A flexible model to identify and to nurture relevant skills, without loosing yourself in theory. (Not only for Scrum Masters.)</h4><p>So here is the challenge: you want to further develop relevant skills to master your current profession, but you and your team are stuck in a project, where certain improvements just don’t add any value. How can you improve your skills? How will you identify “relevant” skills? And how will you add value to the project or to your team while doing so?</p><p>In this article, I would like to describe a learning model, that we already practice for while now at <a href="https://mayflower.de/">Mayflower GmbH</a> and that feels more flexible and more coherent to our agile approach than maturity models like CMMI (<a href="https://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration">Capability Maturity Model Integration</a>) or other, more process-focused techniques.</p><p>Our model will help you identify “relevant” skills — skills, that fill foster your project, when applied correctly, and that will help you to improve in your profession. In short terms: you will carve out the business value of individual skills, helping you to argue for building up knowledge in that area. And you will be able to track and develop your progress. (<em>Bonus</em>: as a company, you will be able to do your staffing/identify the right expert for a project more efficiently.)</p><p>It is one part identifying and prioritizing skills and one part building up knowledge. This is, what we are doing and this model should adapt to other roles as well, beside Scrum Masters and Product Owners. I may introduce the Mayflower <em>Kano Maturity Model</em>.</p><p>(Find a <strong>tl;dr;</strong> at the end of the article.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*22ZSVYPjAd4UjkOBilXF3A.jpeg" /><figcaption>Clean. Simple. Optimistic. The golden area of 70s design. And four-quadrant-graphs, apparrently. (Picture by Joey Banks, via Unsplash)</figcaption></figure><h3>Kano for the satisfaction</h3><p>In the late 70s, Professor Noriaki Kano came up with a model to identify and map drivers for customer satisfaction. This so-called <a href="https://en.wikipedia.org/wiki/Kano_model">Kano Model</a> acts as a simple design tool for Quality Function Deployment — sorting items by <em>Basic Needs</em>, <em>Performance Needs</em>, <em>Exciters</em> and just the <em>Do Nots</em>.</p><p>By mapping the skills of the role, that we want to develop, Kano will help us to understand and to distinguish the needs of that role and to prioritise them.</p><h4>Identifying skills for the kano model</h4><p>This is the simple part. Sit down with your team, take yourselves some time let’s say, a 10-Minute timebox) and write down whatever skill will come to your mind. One skill per Post-it. Then just throw them together and sort-out duplicates.</p><p>At Mayflower, we came up with more than 100 skills for a Scrum Master at the first try. This number will certainly vary, depending on your and your teams size and maturity. But don’t worry, with the help of the Kano Maturity Model you will be able to break that number down to a much more manageable size, where you can get skills on track for your project and be able to nurture them.</p><h4>Prioritising skills with the Kano Model</h4><p>Now you have a large set of skills and usually you will not have the time to develop an grow on each individual one. This is why we need to prioritise and it is very important to understand, that it is not just about sorting-out the extremes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uGP-O4BtfcfdoMGbB7GpcQ.jpeg" /><figcaption>Example: Mapping and prioritising Scrum Master skills for a client’s project — what skills do we need in our current situation and where should we improve in particular? We ended up with 32 out of 112 identified skills.</figcaption></figure><p>You will need a good mixture of fundamentals (to be able to do any work at all), performance skills (that will add over time and will broaden your capability as a professional) and exciters (that will assure you a competitive advantage) as well. What kind of skills actually matter to your project (that is: bringing additional value) depends on the project. For example, a <em>basic </em>skill like “teaching Scrum fundamentals” is a must-have, when there is no Scrum-knowledge at all. In more experienced environments, you may want to skip that skill in favour of being able to “do a proper release forecast”.</p><p>As a rule of thumb: 6 to 10 percent of exciters should fit very well — if you keep your overall capacity in mind, it will give you a feeling of how many skills you will be able to manage and to grow over time.</p><p>As a result, you will get a good starting point to educate your skills based on actual needs (of your project/client/whatever environment will pay your bills). But how can you learn and track your improvements, now that you have identified your ideal skill set?</p><h3>Peer Review: shared understanding, perception and the delta to improve on</h3><p>The peer review process described here requires two to three peers — people you trust and than can give a diverse and professional feedback on your role where you want to develop your skills. If you are a Scrum Master, pick another Scrum Master and a regular team member, for example.</p><p>During the review, go through each identified skill step-by-step. Explain the skill to each other, so you will build up a shared understanding of what you are going to talk about. The person reviewed will then talk about its perception of where he/she stands, regarding the maturity of this individual skill and the peers will give feedback — in the end, this will clear-up the perception of that skill, based on individual and external references.</p><p>It is not important, if one has mastered a skill or if one completely lacks any competence. What is relevant, however, is that you identify the delta in your perceptions, because that is, where you can improve.</p><p>Repeat these steps for every skill, so that you will have a good starting point with relevant action items to improve on your overall skill set.</p><h3>Summary</h3><p>By going through the hole process, every three months, as described here — identifying the relevant skills, that are needed right now, by utilizing Kano for prioritisation and going into a peer review, then, you will mature in your role (here: as a Scrum Master), while keeping focused on your project.</p><p>I will describe a typical peer review in detail (how to prepare for it, what kind of questions to ask, how to facilitate and execute such a meeting/workshop and how to keep track of progress being made) in an upcoming article: <a href="https://medium.com/@robsblog/to-foster-where-we-disagree-71d6246caad0">How to foster, where we disagree</a> (Peer Review: Identify, nurture and reflect on your skills)</p><h4>tl;dr;</h4><p>So here are the important take-aways: you may use the Kano model to identify and prioritise “relevant” skills. You can utilize the Peer Review model as a reference point to carve out action items to actually improve your skills. And by repeating these steps every three months (because that is a reasonably timeframe) you will mature and drive your professional capabilities on to the next level.</p><p>Curious about details, mad about something or happy to share your own ideas? Feel free to add a comment, to follow <a href="https://twitter.com/robsblog">@robsblog</a> on Twitter or contact me via <a href="http://www.linkedin.com/in/robertlippert">LinkedIn</a> or <a href="https://www.xing.com/profiles/Robert_Lippert">Xing</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38a4e6569257" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I didn’t know I could actually talk to you people …]]></title>
            <link>https://medium.com/@robsblog/i-didnt-know-i-could-actually-talk-to-you-people-416fb47f435d?source=rss-9ecb1ce89a97------2</link>
            <guid isPermaLink="false">https://medium.com/p/416fb47f435d</guid>
            <category><![CDATA[smalltalk]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Robert Lippert]]></dc:creator>
            <pubDate>Thu, 01 Jun 2017 12:27:47 GMT</pubDate>
            <atom:updated>2017-06-01T12:27:47.696Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>No need for awkward situations at a conference booth: Constructive Smalltalk on top of the regular session program</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WP6KO200_UShyKDQnDf8ZA.jpeg" /></figure><p>Every now and then we are visiting conferences not just as speakers or trainers, but as an exhibitor as well. For some reason, attendees expect you to sell something — that feels a bit awkward, especially when it is no sales fair, but a conference that is based on information exchange and networking.</p><p>So attendees are positively surprised when they find out, that they can actually discuss their own topics with us at our booth. That there are (almost) no salespersons behind the desk, but our colleagues, that would otherwise give a talk or a workshop (basically the same things we do for our clients as well). This is also where a constructive exchange of ideas may give you more value than listening to a talk where its slides will be available on Slideshare later on, anyway.</p><p>To keep things simple and short — I would like to encourage you to exchange ideas or to ask an exhibitor, if they are willing to listen to you or if they mind to give free advise. People behind the desk are more than willing to skip the part, were they have to sell you something, they didn’t know you would need it anyway.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=416fb47f435d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I don’t like pre-defined tests in the recruiting process]]></title>
            <link>https://medium.com/@robsblog/why-i-dont-like-pre-defined-tests-in-the-recruiting-process-d2756b6b48e9?source=rss-9ecb1ce89a97------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2756b6b48e9</guid>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[talent]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[hr]]></category>
            <dc:creator><![CDATA[Robert Lippert]]></dc:creator>
            <pubDate>Sun, 05 Mar 2017 13:16:17 GMT</pubDate>
            <atom:updated>2017-03-05T13:22:16.874Z</atom:updated>
            <content:encoded><![CDATA[<h4>Looking for talents is different than looking for someone to do the job</h4><p>Talent is a strange thing. You can teach people a lot of things, but without talent — without a little something, that is driving them from within — they will never live up to their full potential.</p><p>“I want to achive $things in my life” is all good, but when you have never started doing them, yet, chances are that you got no talent in doing so. I can’t teach you to become a software developer, when you never had written a single line of code. I can’t teach you to become a writer, when you have never tried to write something down. You get the idea.</p><p>I strongly believe, that everyone has got their specific talents. Sometimes these are hiding in things people do without even thinking about it. And sometimes talents are pretty obvious and people are aware of what they like and try to develop their required skills further.</p><p>But I want to write about the recruiting process. To hire someone is a delicate task sometimes. Start with questioning yourself: why do you want to hire someone?</p><p>Just for doing a predefined job? Without the need for change or improvement? Just go hire <em>someone</em>.</p><p>Your are looking for a person, that will be able to improve your processes? That will foster innovation and by doing so, discover new opportunities for your business? A person, that is able to do things differently than you have done them before?</p><p>Chances are high, that a single test to rule them all won’t fit them. A test to rule them all is a message to the applicant, that you don’t care for their talent, because you just want them to do a “job”.</p><p>I don’t want to limit a colleague to what I want him to do. I want them to push their limits in a way, that is unique to their style — something no one else can deliver. That’s why I’m looking for <em>talents</em>. And it’s my job to engineer the setting in a way, these talents can push us further and make us successful.</p><p>Talent is a USP and I can’t afford to iron out these skills just because I got no idea how to make the best out of it.</p><p><em>These notes are part of a little series, where I write down some ideas without much polishing. The writing’s rough and the storytelling may be broken, but we got something to talk about. Feel free to comment and to ask questions. For a handshake, visit my profile on </em><a href="https://www.linkedin.com/in/robertlippert/"><em>LinkedIn</em></a><em> or </em><a href="https://www.xing.com/profile/Robert_Lippert"><em>Xing</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2756b6b48e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We have to be more agile]]></title>
            <link>https://medium.com/fintech-weekly/we-have-to-be-more-agile-e7b26472b8ed?source=rss-9ecb1ce89a97------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7b26472b8ed</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Robert Lippert]]></dc:creator>
            <pubDate>Fri, 28 Aug 2015 15:43:21 GMT</pubDate>
            <atom:updated>2015-08-28T15:43:21.848Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>A dynamic shift is challenging the financial industry</h4><p><strong><em>tl;dr;</em></strong><em> While becoming “more agile” might mimic someone else’s good solution, there might be a better way to benefit from the value of Agile.</em></p><p>In a recent <a href="http://t3n.de/magazin/zukunft-finanzbranche-expertensicht-muessen-agiler-239391/">interview in the german t3n magazine</a>, FinTech experts discuss the future of the financial industry. It may be no surprise that it is challenged by a growing need for continuous innovation, especially in terms of advancing in the digital landscape.</p><p>While becoming “more agile” is an obvious step for software developers, the <em>Agile Transformation</em> is a risky step for the enterprise. The agile concept evokes a different culture that may just not be the best answer to your enterprise&#39;s business needs. Focus on what you are good at.</p><p>Currently, corporations are experimenting with different approaches to improve their agile momentum. They merge/absorb small and agile companies. And it may work for a few months, if at all. They outsource groups of agile experts into subsidiary companies. Which may work, if they manage to find them before they get absorbed again.</p><p>But as I mentioned <a href="https://medium.com/fintech-weekly/fintech-is-doomed-in-germany-759e2fd3b0d2">in another story</a>, you may not need to mimic agile culture just to benefit from its value for your core services. For some it’s a business model to deliver valuable financial services to their customers. For others it’s to develop software.</p><p>Just image they could team up for a project.</p><p>Coincidentally, I may suggest to reach out to the fine people of Mayflower — here you will find some best in class skills to <a href="https://mayflower.de/fintech">benefit from software for your FinTech needs</a>.</p><p>Questions? Reach out for me via <a href="https://linkedin.com/in/robertlippert">LinkedIn</a> or <a href="https://www.xing.com/profile/Robert_Lippert">Xing</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7b26472b8ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fintech-weekly/we-have-to-be-more-agile-e7b26472b8ed">We have to be more agile</a> was originally published in <a href="https://medium.com/fintech-weekly">FinTech Weekly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fintech is doomed in Germany …]]></title>
            <link>https://medium.com/fintech-weekly/fintech-is-doomed-in-germany-759e2fd3b0d2?source=rss-9ecb1ce89a97------2</link>
            <guid isPermaLink="false">https://medium.com/p/759e2fd3b0d2</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[germany]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Robert Lippert]]></dc:creator>
            <pubDate>Tue, 11 Aug 2015 16:48:28 GMT</pubDate>
            <atom:updated>2015-08-11T16:50:28.582Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cNpyQHlAxjv9PXiPTCtbiQ.jpeg" /></figure><h4>… but you can do something about it.</h4><p><strong><em>tl;dr; </em></strong><em>Instead of blaming high wages, start to tackle your real problem. Start to think outside the box — the experts you are looking for are already there (and you probably won’t need to employ them in the first place).</em></p><p>As Bloomberg mentioned in a recent Article, <a href="http://www.bloomberg.com/news/articles/2015-08-09/high-banker-pay-is-one-hindrance-for-frankfurt-s-tech-startups">High Banker Pay Is One Hindrance for Frankfurt’s Tech Startups</a>. Basically, the finance industry is in the need for more software developers that can handle the challenges in more and more dynamic markets.</p><p>Now, as Bloomberg states, skilled developers are rare and more likely to go to more trending Cities like Berlin, London or the Silicon Valley. On top of that, as the article points out, “a conservative culture, a lack of IT skills and bank salaries are hindering the fintech scene in Frankfurt […]”.</p><p>That is, when you are speaking from within that particular community. Which is a pity, because there are skilled people and companies in the Frankfurt area, who have embraced an innovative/disruptive/agile culture, who can deliver best-of-class IT skills (even for the financial sector) and who offer business value for your money.</p><p>The thing is … these people may not wear suits. They may not write their software in Java code, but use other technologies. They may not be available for an employment. And I start wondering, when will the finance industry start to think outside its boxes? Sure, when your startups can’t deliver working software, a lack of skilled IT professionals may be the source of your problem. And you will address this in the long run. But for now, all you need is working software. What is holding you back?</p><p>While you may argue about web technology being less safe or somehow less enterprise-grade than your existing Java stack; while you may be making plans on how to employ skilled people; while you may criticize the high salaries in the financial sector … well, in the meantime, all the stuff you are still talking about is already happening in other companies (<a href="https://mayflower.de/">like this one</a>. <em>Disclaimer: I work for this particular company</em>).</p><p>Why not stop complaining and just start doing?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=759e2fd3b0d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fintech-weekly/fintech-is-doomed-in-germany-759e2fd3b0d2">Fintech is doomed in Germany …</a> was originally published in <a href="https://medium.com/fintech-weekly">FinTech Weekly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I walk a mile for a good Brötchen]]></title>
            <link>https://medium.com/agile-concepts/why-i-walk-a-mile-for-a-good-brotchen-1a79197628a7?source=rss-9ecb1ce89a97------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a79197628a7</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[theory-of-constraints]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Robert Lippert]]></dc:creator>
            <pubDate>Sat, 10 Jan 2015 19:57:40 GMT</pubDate>
            <atom:updated>2015-08-28T15:24:25.263Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>An unawareness for the Theory of Constraints (and a few other models) has led to a massive decrease of service and quality in nearby bakeries. And when the demanding customer starts to walk a mile for a good Brötchen, your business will soon be in trouble.</h4><p>Dear readers from abroad, in germany you start a sunny sunday with a good Brötchen (bun, baguette, croissants …). I’ve been quite lucky over the past years, because there is a bakery just one door away. Unfortunately, for a <em>good </em>Brötchen, I will have to walk a mile, now. Because all those basterds disrespect the Theory of Constraints — they just can not deliver what I need as a demanding customer anymore.</p><p>Now, what happened in the fist place is, that my local bakery served me a lousy Brötchen — again. You see, a good product is supposed to be rich, well-shaped and as delicious as it is charming to the eye. But during my last visits the friendly craftsmen hand-picked some ugly, flat and dead-like buns. Which is an insult to the german customer, especially on sundays. When I told them, they acknowledged that I was right and the product should have never been sold in the fist place and that I can have a second one, if I liked to. Of course there was no need to have another product that should have never been sold in the first place. How embarrassing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o0xG7JpqQp30qt5v4BOGiA.jpeg" /></figure><h3>Bad user experience will drive your customers away</h3><p>So while the staff is friendly and insightfully, the products are lousy. And because that is having a negative impact on the customer’s experience, I will call that a bottleneck. So they need a process to improve their products, which obviously is a second bottleneck (because they did not know how to do that). But more on that, later. Since there are more bakeries around, let me try one of the competitors …</p><p>I tried a second bakery, a real hipster one, where they still make all their bread &amp; brötchen by themselves (instead of just crisp them up, like the franchise businesses do). Real tasty manufactured products for a perfect start of my sunday? Oh boy, how could I be so wrong. Oh, they had cakes. And tea. And coffee “to go” (that is what germans call a cup of coffee to take away with you). But. No. Brötchen. So I had a bakery that could not sell any Brötchen on a sunday, which is definitely a huge bottleneck.</p><p>The third bakery I tried that day has been closed forever. Well, they had a spin-off in a nearby supermarket, but regular stores are closed on sundays, so … bottleneck.</p><p>The fourth bakery is about one mile away. Ok, they crisp-up their goods (bottleneck), but the starting product is of good quality and they take care of the process (solution). I have to stand in line for two or three minutes (bottleneck), because quite a lot of customers are looking for a good experience on sundays, but that is fine for me. There are about seven crew members serving fresh and warm Brötchen to their customers. These people are friendly and their smiles make me forget about waiting in line (solution). I am so happy to get my fresh Brötchen on a sunday morning (solution), that I even enjoy the one mile walk (and the second one to get back home — bottleneck). Sure, their bread &amp; buns are expensive as everywhere else in this big city neighborhood, but that is ok to me and everyone else. And probably for that bakery, because they drive sales from all the lousy bakeries to themselves.</p><h3>Focus on the needs of your customers and remove one bottleneck a time</h3><p>Customers usually do not care much about your business. They have their own needs and it is up to you to offer a solution to these needs. Wether you are a bakery selling Brötchen on a sunday morning, or offering development services as a software company — you can do that, because someone out there needs your support. Especially when there is competition out there, you may want to make sure, your customers enjoy their stay. Basically, it is all about the one bottleneck, that is having the most negative impact of your business. Finding a solution to break up this bottleneck (and the other ones to follow) is supposed to improve your services up to a point, where customers will walk that extra mile to buy <em>your </em>Brötchen.</p><p>There are different systems to identify your bottlenecks and to develop your business in a way, were you can differentiate yourself from your competition and start offering a unique experience that will help to develop a leading role in your market segment. There is Goldratt’s <a href="http://en.wikipedia.org/wiki/Theory_of_constraints">Theory of Constraints</a> (to identify major bottlenecks one after another to improve, basically) or Mewes’ <a href="http://de.wikipedia.org/wiki/Engpasskonzentrierte_Strategie">Engpasskonzentrierte Strategie</a> (EKS: adding some theory, basic principles and actual recommendations on how to identify &amp; get rid of your bottlenecks and to build up innovation on top of that, basically).</p><h3>Make me a loyal customer</h3><p>Based on that theories, what will it take to make <em>me </em>a loyal customer? If you would like to start up a new bakery, you need to know your competition and overall setting for your business. Following the EKS, there are seven steps to consider:</p><ul><li><strong>Identify your strengths<br></strong>You are a bakery and you know how to make a good and tasty product (obviously).</li><li><strong>Pick your area of business<br></strong>Well, it will be a bakery, in this case (just to fit in context with this article, otherwise you may consider some bakery consulting services with all those lousy bakeries nearby …)</li><li><strong>Pick your target audience<br></strong>The rent for businesses is high in this neighborhood, your customers should be able to pay the average prices of such a gentrified quarter. These people are demanding customers that value (and have already experienced) good service.</li><li><strong>Find out the biggest challenge for your customers<br></strong>What do they expect from a great bakery and what is their biggest bottleneck to enjoy such an experience? How can you differentiate from our local competition? Lower prices will be hard to achieve (see Step 3). Better service? Most bakeries are quite good around here, so that is more like a challenge for you. What is missing are <em>local products </em>at <em>superior quality. </em>Selfmade, not crisped up, in less than a mile distance.</li><li><strong>Innovate, once you can deliver<br></strong>How about some biological exotic grain compositions for your next line of products? Cakes and Coffee to go? There is always something to improve.</li><li><strong>Keep your core capabilities in focus<br></strong>Are you still a bakery? Has that changed (for better or for worse)? Should you outsource part of your work that is out of focus (or cooperate with other businesses)?</li><li><strong>Understand your customer’s basic needs<br></strong>Being able to constantly fulfill the regular needs of your customers is a key to keep your business on top of the line.</li></ul><p>Now, please: <em>Be that Brötchen expert </em>and I might owe you a beer for not having to walk that extra mile anymore. Oh, and just in case you are one of the bakeries mentioned here: you definitely want to <a href="http://robsblog.de/contact">get in contact</a> with me. :-)</p><p>Originally <a href="http://robsblog.de/2015/why-i-walk-a-mile-for-a-good-brotchen/">published in my personal blog</a>, because I think Medium is fundamentally broken, since they rendered collections unusable. But hey, it’s all about the content, and you are free to choose to read my articles wherever you like:-)</p><p>Questions? Reach out for me via <a href="http://linkedin.com/in/robertlippert">LinkedIn</a> or <a href="https://www.xing.com/profile/Robert_Lippert">Xing</a>. Or just get amazed by a good ol’ contact form, <a href="http://robsblog.de/contact/">over here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a79197628a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agile-concepts/why-i-walk-a-mile-for-a-good-brotchen-1a79197628a7">Why I walk a mile for a good Brötchen</a> was originally published in <a href="https://medium.com/agile-concepts">Agile Concepts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good enough: You are doing it wrong]]></title>
            <link>https://medium.com/agile-concepts/good-enough-you-are-doing-it-wrong-bf2a36538f0e?source=rss-9ecb1ce89a97------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf2a36538f0e</guid>
            <category><![CDATA[goods]]></category>
            <category><![CDATA[technical-debt]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Robert Lippert]]></dc:creator>
            <pubDate>Sun, 08 Dec 2013 21:15:29 GMT</pubDate>
            <atom:updated>2015-06-20T10:40:32.710Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>The concept of “good enough” is often mistaken by the definition of done. This comes at a price: An increasing technical debt of your projects.</h4><p>You may already know what it is like to finally launch that new project. Your team is full of excitement, your clients are happy and yet, there is this distinct feeling that you could have done better. Of course it is not like you are the perfectionist — you do know that concept of <em>good enough</em>, when 80 percent readiness suddenly become, well, good enough.</p><p>While this is great and <em>might be</em> something your stakeholders will approve as a final version, you should be aware that a minimum viable product (MVP) does not comply with a definition of done. And while there often is no chance to actually develop that product any further (like when your client is perfectly happy with that MVP and will not pay for additional features or bugfixes) there is still a debt on your project.</p><h4>Lessons learned: Never stop improving</h4><p>There is a common perception that you are done, when it is <em>good enough</em>. You are not. The most important steps have to be taken once you are done with your project:</p><ul><li>Write down your lessons learned.</li><li>Do apply these lessons learned, when needed (that is, you have to actually learn &amp; to understand them).</li></ul><p>If you miss these two actions, you (and your team) are doomed to start from sketch with every new project. Remember those moments, when you think by yourself “wow, this is just an everyday project and it feels like we are doing this for the first time — again!” This is your hidden technical debt, the lack of know-how you could have gained last time. It is expensive. It will slow you down. It will prevent you from learning the new stuff — because you have to learn the old stuff, again.</p><h4>Good enough, not yet done</h4><p>It is perfectly fine to finally launch a project that is considered good enough. It is not acceptable to expect you are done, though. Learn your lessons. Be aware of the things that did not work as expected and think about how you can do better next time. This is not about being perfect, but about being professional. Over time, you will be able to deliver much greater solutions and to raise the level of readiness of your projects. Even when they are “just good enough.”</p><p>Want to know more? Feel free to add a comment or contact Robert Lippert via <a href="http://www.linkedin.com/in/robertlippert">LinkedIn</a> or <a href="https://www.xing.com/profiles/Robert_Lippert">Xing</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf2a36538f0e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agile-concepts/good-enough-you-are-doing-it-wrong-bf2a36538f0e">Good enough: You are doing it wrong</a> was originally published in <a href="https://medium.com/agile-concepts">Agile Concepts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>