<?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 Felix Bodensteiner on Medium]]></title>
        <description><![CDATA[Stories by Felix Bodensteiner on Medium]]></description>
        <link>https://medium.com/@FBodensteiner?source=rss-46a73946f97d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*GRDnfgj-fKRNJnOoUBF-SQ.jpeg</url>
            <title>Stories by Felix Bodensteiner on Medium</title>
            <link>https://medium.com/@FBodensteiner?source=rss-46a73946f97d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:47:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@FBodensteiner/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[What does it take to be a top performer?]]></title>
            <link>https://medium.com/@FBodensteiner/what-does-it-take-to-be-a-top-performer-d6364a98cd2d?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6364a98cd2d</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[marathon]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Mon, 29 Apr 2024 11:14:13 GMT</pubDate>
            <atom:updated>2024-04-29T11:14:13.728Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AmcF7-XPYEc8Y1VJLXyHPg.jpeg" /><figcaption>What does it take to be a top performer?</figcaption></figure><p>I’ve tried to become one the last 12 months.</p><p>Be part of the elite.</p><p>After trying for over a year.</p><p>Today, I have the answer.</p><p>Well — sort of.</p><p>More like an approach.</p><p>Three learnings that helped me to improve performance (in running) and how I apply the same learnings in my professional life.</p><p>Here is how it all started:</p><p>Sports has been an important part all my life and most recently, I’ve got into marathon running. While it’s a niche sport, there is a vibrant community, with races all over the world on every weekend.</p><p>A year ago, my best result was pretty average (fastest 40%). A decent start, positive feedback &amp; pats on my back.</p><p>But shortly after, I’ve hit a slump.</p><p>A genuine unawareness of what’s next lead to stagnating progress led to mental fatigue led to a stubborn injury.</p><p>What started out as a positive accelerant became a burden.</p><p>“I am doing well — isn’t that enough” — I said to myself — “No one cares and … I don’t <em>need</em> more”.</p><p>However — one thought kept me awake at night: “Do I <em>want</em> more?”.</p><p>This was an important conversation I needed to have with myself because it begged the question:</p><p>“<em>Could</em> I be a TOP performer?”</p><p>I wanted to know. No — I MUST know.</p><p>I dove into the theory.</p><p>The good thing about running is that you have laboratory-like environment, allowing you to measure performance (running time), inputs (training time) and progress (pace over time).</p><p>Top performance (fastest 10%) for most marathons was a time under 3 hours, which roughly requires running close to 100km / 60 miles per week for several months.</p><h3>Learning 1: You need to change more than you think.</h3><p>Working backwards from my desired outcome, I’ve put together a trainings plan.</p><p>The bad thing: It was unrealistic to achieve. Utterly unrealistic given my then habits.</p><p>Becoming a top performer is not a minor change, it’s a whole different league, which requires a different level of focus and commitment.</p><p>If you are an above average performer you already have a trait that makes you successful — in absolute terms.</p><p>However — a top performer is standing out <em>relative</em> to all others — others that are also successful.</p><p>This is a hard thing to wrap your head around. While there is no ultimate glory, there also isn’t any trouble. I can’t be ‘that far’ from top performance — right? … RIGHT?</p><p>I had to be realistic. Like the famous saying goes: “Insanity is doing the same thing over and over again and expecting different results”.</p><p>Just starting to do one extra run on a Tuesday is not going to cut it.</p><p>To give you the back of the envelope math. I needed to 2.5x my effort (= weekly milage) for a mere 30% increase in relative performance (= percentile finishing time). Not just 10% or 20%.</p><p>For several months. Not just for the next ‘sprint’.</p><p>In case you are wondering what it takes to go from top 10% to world class / top 1% — It’s another whole hour faster and ~2.5 more milage.</p><p>High performance has a steep curve.</p><p>I needed to change more than I thought.</p><p>At work, I was always <em>willing</em> to change, but especially in my early professional years, was struggling more to understand WHAT exactly I had to change.</p><p>Now that I’ve managed various team at a large company, I realized that the difference from doing well (e.g. flawless feedback ratings) and being a top performer (~being promoted faster than anyone else) is nebulous for many.</p><p>Unlike running, comparing performance in cross functional teams is non-trivial.</p><p>The way to bring awareness for ‘what’ is needed is to start with first principles thinking, breaking down your overall goal into the multiple dimensions that you would need to excel in.</p><p>To succeed at work, you would start with things like professional network, communication, people management, strategy etc.</p><p>To succeed at running, it was physique / technique, pace and endurance. Then, I had to find ways to (further) improve each dimension. To improve pace, I need to do interval runs. And so forth.</p><p>The plan was born.</p><h3>Learning 2: Prioritize the things that you love doing</h3><p>Plans are great — but execution is what’s standing between idea &amp; reality.</p><p>And the prospects of execution were … lengthy.</p><p>Ahead of me was a year of increasing milage weekly, little running ‘vacation’ and over 300 training days.</p><p>Ouch — not a quick win.</p><p>For this, you must have few &amp; clear priorities.</p><p>It’s just too easy to lose faith and/or interest along the way, so you want to be certain that you’re all in.</p><p>For me that was hard to say — I was certainly motivated enough to invest time &amp; effort — that’s what got me here to begin with.</p><p>But I wasn’t sure if it was enough.</p><p>So I ran an experiment — an energy audit.</p><p>I made space, freeing myself up to execute on my running plan. For a month I went through the motions. After every week, I registered what gave me vs costed me energy.</p><p>Was I feeling more energizing after each exercise? After working on a specific project?</p><p>Or did my mind go wandering? Did you feel burnt out after a meeting?</p><p>An energy audit helps you to clarify what the things are that you love. Things that you love will give you MORE energy.</p><p>More energy usually equates to better the performance. Therefore, ideally you structure your day around only things that give you energy.</p><p>What I found that my running exercises was something that I loved — I was all in.</p><p>Great — that was the easy part.</p><p>Then there was a hard part.</p><p>I also had several things on my calendar each week that were costing a lot of energy without contributing to anything that I truly wanted.</p><p>I had to get serious about priorities — and this required tough choices. Choices that a lot of my friends call stupid with substantial financial ramifications. Projects that I already invested a lot of time or that I thought would be ‘easy’ and ‘little effort’.</p><p>I knew, continuing like this, execution will fail.</p><p>Big goals require big prioritization.</p><p>Depending on what roles we play at work, this might be something we have more or less control over. Making these radical choices would not have been feasibly in my early professional years.</p><p>At least once you have awareness, you can start moving in the right direction through open communication with your manager about the role you want to play on the team, the projects or task you want to focus on etc.</p><p>You’ve ramped up your effort significantly. You’ve set priorities, allowing you to execute.</p><p>Now it’s time to play.</p><h3>Learning 3: Short feedback cycles</h3><p>Life is a game of chance.</p><p>A stubborn cold, a freaky injury, a new boss, a company ‘reorg’. The cards can be reshuffled at any moment.</p><p>This is very likely when working on extended timelines — like elevating yourself to be a top performer.</p><p>The ability to adapt is crucial. You have to give your body rest when you need it — and accelerate when there is an opining.</p><p>That’s why short feedback cycles are desperately needed.</p><p>They inform us how we adapt to new challenges.</p><p>For my running plan that meant setting weekly (to manage execution) &amp; monthly (to manage progress) goals.</p><p>The key is to view yourself holistically — how does my priority fit in into the big picture — what’s my heart rate? Sleep? Mood?</p><p>One insights (that I luckily got early) was that my approach to ‘recovery’ was … not cutting it.</p><p>I largely followed recovery ‘best practice’ from the internet. But it just wasn’t working for me. My technique was sloppy and I was doing too little. Then my legs felt empty on the hard efforts &amp; I wasn’t able to push myself to where I needed to be.</p><p>I put in the effort. I set the priority.</p><p>But thanks to my set feedback cycles, I quickly found that I wasn’t improving as planned.</p><p>Capturing this insight, allowed me to iterate. And those tweaks yielded a program that was much more valuable, because it working for ME.</p><p>For running, you can reasonably well predict &amp; spot variations.</p><p>At work that’s less trivial — you can’t just check your apple watch to see the heart rate of team morale, customer sentiment or your manager ‘s assessment.</p><p>But that doesn’t mean you can’t know these things. You can — if you just ask.</p><p>While most teams in my line of work use some method to set (quarterly) goals (like OKRs) and plan execution (like sprint plans), they rarely use it for <em>themselves</em>.</p><p>To illustrate, I could set a plan to say if we continue to develop our product &amp; ship improvements every week, our customers should rate us with X in 2 weeks, with Y in 4 weeks and with Z in 8 weeks.</p><p>Now when executing, and you ask your customer, you have a short feedback cycle.</p><p>What makes you succeed is NOT getting your predictions all correct.</p><p>That’s only a testament to <em>where you started</em>.</p><p>What matters is that you are iterating and improving.</p><p>Because that’s what’s defining <em>where you end up</em>.</p><h3>Conclusion — where did I end up?</h3><p>I’ve didn’t make it ‘all the way’ into the fastest 10%, landing at 13%.</p><p>But honestly — that doesn’t really matter because this journey increased my quality of life.</p><p>I wasn’t feeling stuck or unaware where I was going.</p><p>I’ve done mostly things that I love and made a significant investment in myself.</p><p>And since sharing is caring.</p><p>I wanted to open source this approach with you hoping that it moves you an inch in the direction towards improving your quality of life by improving performance in your craft.</p><p>The triangle of 1) being clear what you have to change, 2) being fully committing to priorities and 3) designing short feedback cycles, sets you on a good path.</p><p>It’s up to you to walk to walk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6364a98cd2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating Incumbency: A Product Thinker’s Guide Turning Interesting Innovations Into Impact]]></title>
            <link>https://medium.com/design-bootcamp/navigating-incumbency-a-product-thinkers-guide-turning-interesting-innovations-into-impact-2642e022b130?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2642e022b130</guid>
            <category><![CDATA[corporate-politics]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Tue, 16 Apr 2024 12:18:46 GMT</pubDate>
            <atom:updated>2024-04-18T18:31:42.660Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product innovation: How to turn Insights Into Impact At A Large Enterprise</h3><p>Imagine you just spend the last few months working on a compelling product innovation.</p><p>You are pitching your insights to a big shot Vice President (VP) at a large enterprise.</p><p>Then — your stakeholder VP says: “Wow, this is very <em>interesting</em>”.</p><p>Happiness. Relief — you made it!!</p><p>But then a few weeks pass and …. nothing happens.</p><p>You are pulling yourself together &amp; confronting the same stakeholder, getting a telling response:</p><p>“It’s really interesting … maybe next quarter / don’t have the resources / would have been great to have X / you would need support from Y / I don’t have time / fill in the blank.”</p><p>Working at an enterprise, I have seen this play out over &amp; over again.</p><p>Talented &amp; ambitious professionals with good ideas that are becoming frustrated with stagnation, when reaching a dead end thanks to the many corporate layers at an enterprise.</p><p>I’ve spend the last five years innovating on data &amp; AI products and leading transformations at IBM.</p><p>Here is my playbook, that I have used to turn insights into impact, despite many layers of incumbency, along with common pitfalls &amp; an illustrative example.</p><blockquote>If you have an idea or product and are looking for support or advice tailored to your situation, please get in touch via <a href="https://www.linkedin.com/in/felix-bodensteiner-94964bbb/">LinkedIn</a>.</blockquote><p>This is my product management journey, turning insights from interesting to impact.</p><h3>The playbook to turn product innovations from interesting insights into Impact at a large enterprise</h3><p>There are many reasons why even great work gets stuck in the layers of incumbency.</p><p>To make this article practical, I’ve laid out this playbook as a framework. Applying this framework gives you a structured approach to narrow down shortcomings, from where you can iterate and succeed.</p><p>Innovation in this context means that we identify an action or feature that will be beneficial for our product or strategy. This doesn’t have to be a re-invention of the wheel.</p><p>An innovation can be a new feature for a tool, a tweak in the marketing or hiring strategy, an idea for process optimization or more — anything that informs a new or different action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Se9_4LfoSPwMt_-D88L_-Q.png" /><figcaption>The framework has five stages: Data, information, knowledge, insight and wisdom.</figcaption></figure><p>When your work reaches the information or knowledge stage, it starts to become interesting. But only excelling at the last stage wisdom, will yield impact.</p><p>Let me explain.</p><h3>Stage 1: Data</h3><p>The first stage, data, the goal is to build basic data understanding.</p><p>This is a requisite to any <em>data</em> driven action.</p><p>Our work can be a raw dump from a database or an excel file, such as user analytics or sales data, but really any documentation or other unstructured data would work.</p><blockquote><strong><em>What is important:</em></strong></blockquote><blockquote>- Data dictionary: Learn meaning of each column (e.g. what is a deal ‘status’). Tip: Tool walkthrough to understand user behavior (e.g. default values)</blockquote><blockquote>- Data understanding: Data types &amp; values (e.g. ‘status’: Open, Closed, Withdrawn). Tip: Do a ‘common sense’ check against known aggregated numbers (e.g. from a company’s annual report: Total Revenue, # employees, pipeline, …)</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C1GrA26WVK-0BjQw4wTn8w.png" /><figcaption>Here is an example of a data dictionary of a sales pipeline. At a minimum, it should have a description of each field.</figcaption></figure><p>Ideally, the team adds rich commentary based on their discovery (reading documentation and talking to subject matter experts).</p><p>A common mistake that teams do in this first phase is to rush into the analysis, without proper data diligence.</p><p>This leads to severe flaws in the following stages and can cost your credibility.</p><p>For example, imagine you jumped into the analysis, and you find that one country, Germany, seems awful at getting deals closed. You pitch your findings to stakeholders, and they point out that, ‘yes’ this is indeed the case … because they use another system / the tool differently / data entries were optional / some other process inconsistencies.</p><p>Ouch. Product innovation dead on arrival.</p><p>As this is likely the first stakeholder interaction, it’s an opportunity. Knowledge sessions, where you learn about data (&amp; high-level processes) is the first opportunity to build a relationship.</p><p>And you don’t want to miss that.</p><p>Eventually, looking at an illustrative example, you should land at this first stage at something like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*ij5Pbi-houdMmFuAleG_ZQ.png" /><figcaption>Here, we’ll look at a list of deals.</figcaption></figure><p>Thanks to our data dictionary, we put ourselves in a good starting position.</p><p>Let’s get to work.</p><h3>Stage 2: Information</h3><p>The second stage, information, aims to make sense of our data and to set a focus area.</p><p>The data is now (somewhat) structured. Think excel pivot table, applying filters &amp; sorting etc.</p><blockquote><strong><em>What is important:</em></strong></blockquote><blockquote>- Before you start: Set purpose by writing down your hypothesis (or multiples). Tip: Hypothesis is focused &amp; testable (with the data &amp; experts you have)</blockquote><blockquote>- Simple &amp; quick analysis: Choose your preferred method (pivot, python, excel, …). Tip: Cite sources &amp; (complex) calculations in footnote to build credibility</blockquote><p>Beware of “analysis paralysis”. Especially for young(er) professionals, it might be hard to say when a hypothesis for a product innovation is “good enough” to proceed, spending enough but not too much time.</p><p>You certainly don’t want to spend months finding the needle in the haystack.</p><p>But then again, you also don’t want to get to your big pitch with trivial insight that your stakeholder already knows.</p><p>The mistake I observe in this phase is that practitioners build insights from their perspective (vs not from their customers).</p><p>A lot of things will be interesting to YOU. And NEW to YOU. But you might only have worked on a specific data set / problem space for a couple of weeks.</p><p>It won’t change the way a big shot Vice President makes an impact yielding decision.</p><p>Instead, (quickly) work out a clear hypothesis that you can test cheaply.</p><p>In our example, we started with the hypothesis that some local sales teams in countries are better at closing deals than others.</p><p>Our expected impact was that, by making these local best practices available globally, we can enable sales teams to close more deals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*-MlzuZkx9mZvQw0UavVz-Q.png" /><figcaption>Hence, we tried identifying which local sales team is successful (if any) by looking at aggregate deal numbers by country.</figcaption></figure><p>Why did we choose this specific pivot table?</p><p>Because it answers our hypothesis (are some countries better at closing deals than others) —if we find significant variations across countries, indicating that our hypothesis might be correct, that is a sign of ‘good enough’.</p><p>Especially in an enterprise setting with many layers, do test your hypothesis with experts.</p><p>Not necessarily the big shot VP — but maybe one or two levels down.</p><p>Someone who (willingly) spends time and that you eventually can turn into a champion (someone who supports your big pitch).</p><p>Where teams loose time is not necessarily being slow– it’s more of doing the ‘wrong’ things.</p><p>Testing the waters quickly creates short feedback cycles which makes sure that you build conviction prior heavy investments in the subsequent stages.</p><p>Speaking about subsequent stages.</p><h3>Stage 3: Knowledge</h3><p>In the third stage, knowledge, the objective is to develop analytical knowledge.</p><p>At this stage, we glean our first takeaways from the information gathered like statistics, trends etc.</p><p>We don’t yet know what pieces of that analytical knowledge will be actionable or impactful. But we build a mental bridge between an nugget of knowledge and the outcome / impact it <em>could</em> create.</p><blockquote><strong><em>What is important:</em></strong></blockquote><blockquote>- Segment, Segment, Segment: Find patterns by looking at different slices of data. Tip: Leverage categorical values from management systems (e.g. market).</blockquote><blockquote>- Apply key performance indicators (KPIs) to different segments. Tip: Check Google for benchmarks plus slides from Company All Hands, internal documents or sources, annual report etc.</blockquote><p>This is where the average person (prematurely) ends their journey at an “interesting” innovation.</p><p>Let’s dig in here with an example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*xtbtFW-yQA8mC-t9xqWRXw.png" /><figcaption>Turning information into analytical knowledge</figcaption></figure><p>In our example, we found out that one country, France, seems to get better &amp; better in closing deals.</p><p>When pitching this, the VP likely finds this interesting — but won’t do anything about it.</p><p>No need to be harsh to the VP and call him / her lazy. There are just significant layers missing for analytical knowledge to be actionable.</p><p>Because it’s just knowledge and not something that can be actioned on (e.g. like a gameplan that describes who needs to do what by when) — the ball simply never starts to roll.</p><p>Why?</p><p>Most people in product management or data analytics fall flat when it becomes time to see “the big picture”.</p><p>The big picture is what the VP sees the whole day, every day — but you just get a glimpse of it / have to piece it together.</p><p>The big picture requires your product innovation to consider implications for people, processes &amp; tools.</p><p>Again you might be asking yourself — why?</p><p>Some people might object, saying: “People? Process? Tools? That is not MY job”.</p><p>Candidly, you can’t have high aspirations to drive impact at scale while simultaneously reducing your job role to data cruncher.</p><p>Consider what a VP can &amp; can not do.</p><p>A VP can not (or likely won’t) do discovery — but a VP will provide strategic guidance to inform guidelines &amp; delegate tasks.</p><p>Therefore, for your VP to take action, he /she not just needs analytical knowledge, but a detailed gameplan on what guidelines to change &amp; tasks to delegate.</p><p>So how do we get the ball rolling for our innovation?</p><p>We need to provide our VP with a detailed gameplan.</p><p>A gameplan that says something like call your sales lead Pierre in France, to codify ABC activity, Laura in IT to enable XYZ required tooling and Alex to do change management to train everyone on the new process.</p><p>To summarize this stage: Analytical knowledge is just a step on your innovation journey but not the end.</p><p>Telling your VP: “France is closing deals” is interesting. The end, nothing more. The VP will go back to the other +50 meetings he/she has EVERY week. No impact from your innovation.</p><p>If we want to drive innovation and be impactful, we have to go beyond, pulling multiple strings together.</p><h3>Stage 4: Insights</h3><p>In the second to last stage, we want to tie patterns to outcomes.</p><p>Fundamentally, you now are able to answer the ‘why’ behind your nugget of knowledge from the previous layer.</p><p>Why is France closing more deals? It’s because of X.</p><p>In this stage we aim to understand cause effect relationships.</p><blockquote><strong><em>What is important:</em></strong></blockquote><blockquote>- ‘So what?’: Highlight importance by connecting pattern to success metric. Tip: Leverage (internal) benchmarks to illustrate differences.</blockquote><blockquote>- Expert interviews: Validate cause-effect with subject matter experts (plural!). Tip: Isolate root cause AND leads for solution</blockquote><p>Reaching this stage is great — we’re slightly shifting gears, this phase is less about doing analytics, but more so drafting up potential actions.</p><p>This shift in gears is non trivial for a lot of professionals.</p><p>At an incumbent, your team is likely either one of many, far decoupled from the problem space itself and / or many hierarchical levels away.</p><p>You have to be able to pick up the phone / email / slack subject experts at your company. People that you never met and won’t necessarily care what you do. These people have 50 other meetings to get to and ten other priorities on their plate that are more important than your work.</p><p>From my experience, professionals who excel at these ‘dotted line’ relationships are able to do two things well: 1) they have sales skills, allowing them to build a holistic network &amp; have many conversations (vs few &amp; missing key interviews) and 2) they simplify &amp; present their innovation with clarity, unlocking productive interview sessions (vs spiraling into wild goose hunts).</p><p>As with previous phases, these stakeholder conversations are not just an opportunity to build your pitch, but also to build relationships &amp; convert experts into champions.</p><p>There is real value in having a top sales guy as a champion testimonial for your innovation.</p><p>Let’s look at our example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*LKO1FbCEsLuifyjLfbPQcA.png" /><figcaption>Turning analytical knowledge into an insight by understanding cause — effect relationships</figcaption></figure><p>Here, we have honed our analytical knowledge (France closes more deals) into an insight.</p><p>France is closing more deals due to high close % from an industrial client. We validated it with the local sales team, which had a similar sentiment.</p><p>To close of this stage, I just wanted to re-iterate how much more powerful your pitch is after this stage compared to the last one.</p><p>Last stage you had generic knowledge that was not actionable. If it’s not actionable, it can’t create impact.</p><p>Now, you kicked the tires, tied a pattern to an outcome &amp; validated with experts. And suddenly, you hold a valuable insight that is (somewhat) actionable.</p><p>If we can get more industrial leads, we might be closing more deals globally.</p><p>And this brings us to our last stage.</p><h3>Stage 5: Wisdom</h3><p>In the fifth &amp; last stage, wisdom, we want to formulate an innovation strategy for implementation.</p><p>In this stage, we want to lay out how we can operationalize (action on) our innovation.</p><p>In basic terms, we want to have a gameplan, a list of actions that will create an effect which will lead to our desired impact.</p><p>Following out example, the insight was that France was able to get &amp; close more industrial leads.</p><p>The output of this stage would be a list of actions. Once all the actions are completed, all sales team (not just France) would ALSO be able to get &amp; close more industrial leads. The actions required = our innovation strategy.</p><p>Thanks to our sales funnel innovation, the company would be able to close more deals.</p><blockquote><strong><em>What is important:</em></strong></blockquote><blockquote>- Sanity check &amp; feasibility of implementation: Kicking the tires of your concept. Tip: Observe ‘impact’ at point of decision, e.g. ‘Shadowing’ / ‘mini pilot’.</blockquote><blockquote>- Make insights actionable through Workflow enablement: Activate ‘good pattern’. Tip: Back of the envelope business case to estimate ‘return’ of investment</blockquote><p>This stage is part discovery &amp; design (e.g. for the actions / workflow) and part corporate politics.</p><p>For your insight to be actioned on you might need support not just from your customers, but also from supporting teams. Think HR, IT, Finance etc.</p><p>Why?</p><p>Professionals fail because they are thinking too small. At a large incumbent, any larger effort will have plenty of teams involved.</p><p>Firstly, teams that are tangentially influenced by your innovation will need to be aligned &amp; bought in, especially if they have to invest their own resources.</p><p>IT needs to enable the new workflow. HR might need to change their hiring strategy to bring on people with a network of industrial clients. Finance might have an objection because industrial clients might be less/more profitable — and how would that change commission structure? Maybe the US sales team has an insight themselves that they want to test first? And this list can go on &amp; on &amp; on.</p><p>And yes, all of those teams that might (will) have conflicting incentives, complicating alignment even further.</p><p>Secondly, navigating corporate politics can be elaborate.</p><p>Large enterprises are notorious for ‘prep’ meetings. You take someone through your idea, who then wants to show it to his / her boss, who wants it to show to his / her boss, and then to a few peers, who also want to show it to his / her boss and …. You spend an absurd amount of time in meetings &amp; weeks getting more ‘notes’ than you would have liked.</p><p>Don’t show up at the eleventh hour at stakeholders’ doors. Life is too short for that prep meeting circus.</p><p>Key is to leverage all of your stakeholder interactions of the previous stages as ‘prep’ meetings.</p><p>These need to test the waters enough for you to be aware from which other departments you face head- or tailwind.</p><p>You need to know.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*Rw20432CdRFUItV2Ia0ntg.png" /><figcaption>For insights to be actionable wisdom, you need to identify action that enable your innovation</figcaption></figure><p>In our example, we identified three actions that we could take to make our product insight actionable.</p><p>Out of the options, hosting workshops seems to be the best option, given that is estimated to deliver a decent lead increase and is not utilized yet.</p><p>In general, the simpler the actions, the better.</p><p>Why? Because innovations with simple implementation will be far easier to get off the ground (e.g. a small pilot) than to change everything at once (e.g. new tool or process).</p><p>It will be substantially more difficult to change marketing spend to focus on workshops, change IT resourcing to build the required infrastructure, train all sellers globally on the new process etc.</p><p>Just get a few sellers to send out word on LinkedIn &amp; host a zoom workshop.</p><p>Like with the early days of a startup, my advice is to do things that don’t scale.</p><p>To go deeper, check out my <a href="https://medium.com/design-bootcamp/the-product-launch-framework-six-steps-for-product-manger-daf85e37d02e">product launch framework</a>.</p><p>At the end of this stage, you now pulled everything together for your product innovation pitch, insight &amp; implementation.</p><p>Now reward yourself by getting the most out of your pitch.</p><h3>The pitch</h3><p>How to handle a pitch at a large enterprise could be an article in itself.</p><p>In the context of presenting a product innovation, three points are crucial.</p><p>Firstly, know your goals &amp; get to your points, fast. Don’t beat around the bush, start the meeting with what matters.</p><p>Example: “Hi VP — in this meeting we want your approval to do workshops for potential industrial clients. Based on our findings by looking at sales best practices in France, this would increase clients we close by X.”. Then pause. Wait for the VP to concur. Then go into findings.</p><p>Secondly, tailor the story line to your stakeholder audience.</p><p>At large companies, (meeting) culture can be quite heterogeneous — different VPs will have different preferences. Some are more in the weeds, others hate weeds.</p><p>Structure your deck accordingly and/or stay flexible throughout.</p><p>Thirdly, leverage champions. This is the real unlock and I find that people that advance the ranks fast are doing this particularly well.</p><p>Having a trusted executive (like the US sales leader in our example) pitching that he / she wants to do have your innovation (more workshops to land industrial clients) is significantly more powerful, than a pitch solely coming from you.</p><p>Ideally, the only thing a VP needs to do is to say ‘Yes’. That’s how easy you need to make it.</p><p>And with an ‘interesting’ product innovation PLUS a clear cause — effect insight AND actionable wisdom, you can make the decision very easy.</p><p>Go reap that impact.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2642e022b130" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/navigating-incumbency-a-product-thinkers-guide-turning-interesting-innovations-into-impact-2642e022b130">Navigating Incumbency: A Product Thinker’s Guide Turning Interesting Innovations Into Impact</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three insights from running a marathon on managing work load, strategy & team building.]]></title>
            <link>https://medium.com/design-bootcamp/three-insights-from-running-a-marathon-on-managing-work-load-strategy-team-building-e51d1971c561?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e51d1971c561</guid>
            <category><![CDATA[marathon]]></category>
            <category><![CDATA[execution]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Wed, 05 Oct 2022 11:58:46 GMT</pubDate>
            <atom:updated>2022-10-06T05:32:37.215Z</atom:updated>
            <content:encoded><![CDATA[<p>Like for many others (who apparently need a hobby), running a marathon was part of my bucket list.</p><p>The history &amp; proverb around a marathon are ubiquitous.</p><p>What I like is that running a marathon is as simple as it’s difficult.</p><p>Technically it’s a simple sport, you just have to go from A to B — no equipment required. Everyone can join.</p><p>But it’s also difficult — based on my Strava activity, it took 4,119 calories to get from A to B.</p><p>That is the equivalent energy of ~79.2 apples.</p><p>I have been training for this since the pandemic started +2 1/2 years ago. This actually was my <em>forth</em> iteration since then— three times I did even make it through my training.</p><p>With every iteration, I reflected on what can I improve &amp; with every iteration I was able to run faster &amp; longer.</p><p>So the question I asked myself: If this works for my <em>personally</em> — why shouldn’t it work for me <em>professionally</em>?</p><p>This is where I began to see the similarities between increasing performance at both my marathon training as well as at work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8vvNhbxQ9yYan9kPBHwyA.png" /><figcaption>Finally — Happy like a child after reaching my milestone after 2 1/2 years</figcaption></figure><p>Here are my three insights:</p><h3>1. Run slow to run fast</h3><p>Contrary to common believe, professionals rarely go all in.</p><p>Endurance runners spend &gt;80% of their training in the “aerobic” zone (~15% BELOW top performance).</p><p>Why?</p><p>Training “anaerobic” (close to top performance) creates muscle fatigue &amp; soreness, increasing risk of injury as prolonging recovery.</p><p>Not going aerobic means longer wait to get back to training.</p><p>Going slow allows training more often AND longer, leading to higher gains.</p><p>At work, going ‘anaerobic’ is the equivalent on jumping from meeting to meeting, trying to be a fireman 24/7.</p><p>Think short term fix of leaks. ETC.</p><p>For me, key at work is to regularly break out of the high intensity zones.</p><p>This means taking time for strategic thinking, zooming out of the day to day.</p><p>The change of pace refreshes thinking, build clarity and enables focused execution (in aerobic zones).</p><p>Teams can then consistently ‘train’, significantly increasing their ‘mileage’.</p><h3>2. Setup a plan</h3><p>One of the first thing I prepped, was a trainings plan.</p><p>I spend days researching &amp; tweaking.</p><p>The plan defines training type, mileage, pace, implied recovery, timing and nutrition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pN03xml8zNf8aKfpCuAliQ.png" /><figcaption>My marathon plan — plan on the left, actuals with comments &amp; iterations on the right</figcaption></figure><p>There is even a comment section for additional notes.</p><p>When I leave my house for a run, I know EXACTLY what I am going to do.</p><p>When I come home after, I log my actual performance, compare that to the expectations and iterate the following sessions accordingly. For instance, if I had knee pain, I would reduce the pace of the next run.</p><p>To me, this is logical as it optimizes my training progress.</p><p>Yet, when it comes to work, people often drop that logic and waste training opportunities.</p><p>Joining meetings without prep, not specifying purpose, or not having a process to register feedback &amp; iterate accordingly. And the list goes on.</p><p>Before I tackle work or ahead of important meetings, I note down my key assumptions &amp; arguments in a sort of ‘elevator style’.</p><p>Independent of you anticipating the right questions (= concise arguments ready) or not (= realize shortcomings / learn a new perspective), this leads to faster progress.</p><h3>3. If you want to go fast, go alone. If you want to go far, go together.</h3><p>Professional runners use ‘pacers’, not just in training, but especially for a race.</p><p>For Eliud Kipchoge’s recent marathon world record, pacers took responsibility, leading him for more than half the race (before he took off).</p><p>Running behind a pacer, protects you from weather, ensures that you run ‘on time’ and gives a mental boost.</p><p>It is a win-win strategy: Compared to running alone, it lowers the effort required, allowing for for higher overall performance individually.</p><p>Being part of a team, increases performance, allowing you to go further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8IambsQ60IqufldWZdKXA.png" /><figcaption>Leveraging ‘voluntary’ pacers to manage effort</figcaption></figure><p>Going at the same pace is key: If someone goes faster or slower, the team dynamics become a lose-lose.</p><p>If low performers can’t contribute, top performers either must slow down (lower performance) or continue alone (no team benefit).</p><p>This led to two learnings that I apply for work:</p><p>Firstly, I want to surround myself with people that can take over responsibility &amp; lead (especially on parts where you need support), creating a clear benefit. It also means that I need to match the pace of top performers to maximize return.</p><p>Secondly, quality beats quantity. A team of 5 or 10 might not sound like a major difference. But keeping everyone at the same pace, is several orders of magnitude more complex in larger the team.</p><p>Like for Eliud, a small team is enough for you to reach peak performance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e51d1971c561" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/three-insights-from-running-a-marathon-on-managing-work-load-strategy-team-building-e51d1971c561">Three insights from running a marathon on managing work load, strategy &amp; team building.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruthless execution: Sprints to success with strategy, agile & culture]]></title>
            <link>https://medium.com/design-bootcamp/ruthless-execution-sprints-to-success-with-strategy-agile-culture-3390eb48ddd6?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3390eb48ddd6</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[execution]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Fri, 19 Aug 2022 11:11:57 GMT</pubDate>
            <atom:updated>2022-08-24T11:24:40.947Z</atom:updated>
            <content:encoded><![CDATA[<p>What is the difference between a great idea and a great product?</p><p>Execution.</p><p>When we execute on our ideas, we start building towards a product.</p><p>How can we do well on our idea and make the most out of it?</p><p><em>Ruthless execution.</em></p><p>Ruthless execution is the fertilizer for product managers and any start ups who embark on an entrepreneurial journey.</p><blockquote><em>“Ideas are worth nothing unless executed. They are just a multiplier. Execution is worth millions” Steve Jobs</em></blockquote><p>There are three ingredients you need for ruthless execution — Strategy, agility, and culture.</p><p>Strategy describes the (unique) advantages for a product and lays out the blueprint required to succeed. The strategy could be to bake bread that is crispier than others.</p><p>The agile methodology is a way to drive clarity of outcomes &amp; efficiency for tasks and is a way for empowered teams to quickly iterate. Agile iterations mean building &amp; finetuning, to eventually have a machine that bakes crispy bread.</p><p>Culture is what makes the machine work, prescribing ways of working. Staying in our bread metaphor, Culture is the electricity &amp; oil, it’s what makes the machine <em>ruthless</em> (or a failure).</p><p>Let’s break them down.</p><blockquote>A quick note on the author: Felix is Product Manager @ IBM and a startup angel investor. If you have an idea or product and are looking for support or advice tailored to your situation, please get in touch via <a href="https://www.linkedin.com/in/felix-bodensteiner-94964bbb/">LinkedIn</a>.</blockquote><blockquote>You might also like: Check out my <a href="https://bootcamp.uxdesign.cc/the-product-launch-framework-six-steps-for-product-manger-daf85e37d02e">product launch playbook</a>, which gives you a framework for each stage in the product lifecycle.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YI_Y46T5er3ld5JHDSA3OQ.png" /><figcaption>Ruthless Execution is where strategy, agile delivery &amp; culture align</figcaption></figure><h3>Strategy — Define your unique advantages to be executed</h3><p>The first ingredient for ruthless execution is strategy — it gives teams a north star to aim for.</p><blockquote><em>“Strategy defines the company’s distinctive approach to competing and the competitive advantages on which it will be based. A good competitive strategy is one that creates unique value for a particular set of customers”</em></blockquote><blockquote><em>Strategy definition from the </em><a href="https://www.isc.hbs.edu/strategy/Pages/strategy-explained.aspx">Harvard Business School</a><em>.</em></blockquote><p>Good strategy makes your idea accessible, and your team intuitively understand the rationale on why they work on specific tasks.</p><p>Bad strategy is the opposite — it’s an abstract mess. ‘Solving world hunger’ is an honorable strategy that your developer won’t be able to execute on. The big picture should instead be used as your <em>vision</em>, reflecting on what is the purpose, why your product needs to exist.</p><p>A shared understanding of the “why” is essential for efficient execution. For as long as someone does not understand the strategy, he/she will take decision to solve a task that are sub-optimal.</p><p>Vision is the initial thought about what kind of place it will be and why it will matter. Strategy is the blueprint for the foundation and framing.</p><p>Imagine you tell someone to build wheels for your car that are 30% more resistant. Your scientist makes the wheel size slightly heavier, which gives even 50% more resistance. Great! But if your strategy to have superior energy efficiency, the heavier wheel now cost more energy &amp; you are <em>hurting</em> your desired advantage.</p><p>Specifically with technical teams, smaller tasks quickly can become over-engineered. At fault is the product manager, not the developer.</p><p><strong>If the importance of a given task is unknown, team members are not able to prioritize nor work the most <em>efficient</em> solution, but rather strive for the most <em>sophisticated</em>.</strong></p><p>A roadmap is a great way of visualizing strategy &amp; making it accessible. My favorite way of plotting a roadmap is the cupcake, birthday cake, wedding cake methodology, which is rooted in design thinking.</p><p>Here is an illustrative example how this concept could look like in practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mADyGK70V6BO378Su6LzQA.png" /><figcaption>Strategic Roadmap using the Cupcake — Birthday Cake — Wedding Cake methodology</figcaption></figure><p>Here is how you would put the above together:</p><p>Think about what is your USPs and strategy. Research &amp; discovery, primarily via user engagements will help you determine how that would look like. Your strategy gives you two things:</p><p>First the dimensions that are relevant to your product (e.g. for Airbnb it could be hosts, travelers and the app itself). Ideally those categories are MECE (ME = Mutually Exclusive = there is no overlap and CE = Collectively Exhaustive = it lists ALL that you need to do). Generic concepts to start with are Front end, back end &amp; user or people, process &amp; tools.</p><p>Second, strategy gives you the input for wedding cake &amp; each dimension. In our example, Airbnb strategies for hosts could be to have a ‘Self-serve platform for hosts to upload, maintain &amp; optimize listings’.</p><p>Once you have dimensions &amp; strategy set, work your way backwards to the cupcake.</p><p>What is the least resource intensive way to get to a testable version? For our host dimension, you really want to have a host to begin with. Brainstorming gives you the to do’s you can start with to eventually reach a desired milestone (like number of hosts signed up).</p><p>Lastly, the birthday cake is the intermediate step between cupcake &amp; wedding cake. It describes the steps that are required to scale the cup cake approach.</p><p>The main reason I am a big fan of this framework, is that it creates team alignment.</p><p>Having the strategy laid out clearly makes it easy for team to stay aligned to the core of a product. It’s now intuitive for teams to not over engineer specific tasks (like not building a UI for admins to enter listings since that is not the strategy). The strategy is to have hosts (not admins) to maintain listings, clarifying things that need to be <em>built to last</em>.</p><p>Understanding the strategy empowers team members to take the best (not sub-optimal) decisions for the product.</p><p>Alongside, it also helps to gives an insight how success looks like and lays out the different stakeholders.</p><p>One comment on timeline and why there is an arrow between milestones / OKRs and strategy. The idea behind the cakes is to think in <em>timeboxed</em> three different phases. Maybe your cupcake is just a two-week sprint and quarterly OKRs is your birthday cake. The timeline will vary depending on team productivity &amp; product maturity.</p><p>While strategy describes you action plan on a ‘macro level’, running your team on agile would be the ‘micro’ level, or ‘how’ to tackle task from the action plan.</p><h3>Agile — execute on your unique advantages</h3><p>Agile delivery is an execution methodology aiming to accelerate development.</p><p>We’ll review the premise of agile in theory before taking a look how it’s implemented in practice.</p><h4><strong>Agile, the unlock to accelerate development</strong></h4><p>Agile is based on three core objectives:</p><p>1. Remove slack by driving <strong>clarity of outcomes</strong>,</p><p>2. simplify the decision-making process through <strong>self-directed teams</strong></p><p>3. and user validation to enable <strong>quick iterations</strong></p><p>Let’s dig into one by one.</p><p>Clarity of outcomes allows team to focus on developments <em>needed</em>, not possible. Outcome oriented execution keeps slack to a minimum.</p><p>The north star here is user value. In essence, if I can attribute every piece of development (be it UI, backend, workflow, marketing, etc) to a business outcome, I am able to prioritize perfectly. In theory, what gives the biggest increase in value, should come first and will be released under agile <em>as soon as it is ready</em>.</p><p>This stands in contrast to traditional, waterfall driven, project management. Here, a release date is set months in advance and teams bundle together what can be done it that period of time. But the user can’t enjoy any value until the release date.</p><p><strong>This changes team perspective, the focus of development teams is not the <em>project timeline</em>, under agile it’s <em>user value</em>.</strong></p><p>A focus on timeline invites teams to take sub-optimal decisions. From my experience, it’s usually an over-ambitious timeline leading to teams not building enough slack on high value features.</p><p>If the focus is user value, teams will optimize to build <em>no</em> slack — not too little (untapped user value), not too much (known redundancy).</p><p>The second objective is self-directed team.</p><p>If every decision must be signed off by a boss or stakeholder, development speed slows down. The team spends their time educating &amp; pitching, rather than developing. Your product is not getting better, it’s getting explained within your company.</p><p>Note that there is an order to the objectives. Without clarity of outcome, teams will build something off-course. Imagine your New York team has been given the desired outcome to go west. Some will go to Mexico, others to Canada, but if you want them to go to California, that needs to be <em>clear</em>.</p><p>This aspect makes management hesitant to let loose. They don’t trust their teams to build the <em>right</em> things. Somewhat ironically, the manager, who wants to accelerate, then becomes the bottleneck himself. A slippery slope.</p><blockquote><em>“If words of command are not clear and distinct, if orders are not thoroughly understood, then the general is to blame. But, if orders are clear and the soldiers nevertheless disobey, then it is the fault of their officers.” Sun Tzu — The art of war</em></blockquote><p>As a manager that wants self-directed teams, you need to empower you team.</p><p>What’s underestimated is how difficult it is to empower teams. It’s not simply letting loose and a manager saying “do what you want”.</p><p><strong>I believe, it boils down to if your team can distinguish out<em>put</em> (I build X) from out<em>come</em> (building X will increase Y user value).</strong></p><p>If they can: Decentral lies the expertise. A developer will come up with a better architecture than a manager. A UX expert will create a better design than a manager. And the list goes on.</p><p>Empowering teams is a longer process that requires multi-domain workshops, collaborations, discussions and more. As mentioned above, transparent strategy and a team capable (skilled &amp; motivated) of evaluating outcomes, is required to make your team work.</p><p>Lastly, agile is associated with quick iterations. Not just because of the move away from waterfall releases, but also by giving user validation are a more prominent role.</p><p>This is the key differentiator from other methodologies. Once teams understand outcomes &amp; are empowered to take decisions, user validation is how self-directed teams learn &amp; iterate.</p><p>If I am a developer, in traditional project management I am given a <em>backlog</em> of tasks and work my way down. Moving to agile, understanding the outcomes &amp; taking decisions based on my expertise, finds arguably ‘better’ decisions. Then user validation is my learning process required to iterate.</p><p>User validation is the unlock to accelerate quicker. In agile, the doer is the expert and takes decisions based on user value. That’s the flywheel. No need to communicate learnings upwards and/or risk getting insights lost in translation. No need to wait for prioritization.</p><p>The doer knows what’s best. Thanks to clarity of outcome, the ability to take decisions as part of a self-directed team and uses user validation to learn &amp; drive quick iterations.</p><p>So how can this be implemented?</p><p><strong>Agile in practice</strong></p><p>In agile, work is managed through a tracking board, usually from Jira, Zenhub, Trello or related.</p><p>While each tool has their nuances, the core concept of tacking work is the same.</p><p>Each work effort is described on a card. Each card should contribute to a strategic objective (‘Epic’, OKR, …), which is a simple test to check for outcome vs output.</p><p>From the teams I’ve worked in, the way cards are written drastically differs. Some like it simple (which works in a high trust &amp; high performance culture), some more descriptive (better support for junior talent).</p><p>Each card is a one pager that has several elements:</p><p>· Title: Intuitive, so when a team says I am working on X, everyone knows what is being talked about.</p><p>· Owner: Who bears the responsibility? Ideally this person also writes the card</p><p>· Problem statement: Why are we doing this? Essential to establish a connection to user value</p><p>· Description: What needs to be done? Ideally this is written from the perspective of a user.</p><p>· Checklist: What steps get us to desired outcome? Good if this flags dependencies.</p><p>· Definition of done: When do we know we have done our work &amp; can ‘close’ the card?</p><p>· Success metric: How will we (eventually) track success?</p><blockquote><em>Example card for a new hypothetical feature for a grocery delivery app</em></blockquote><blockquote>· <em>Title: Cooking recipes inspirations</em></blockquote><blockquote>· <em>Owner: Felix / User Experience</em></blockquote><blockquote>· <em>Problem: When a user wants to prep a certain dish, the app makes it time consuming to navigate too all required ingredients and they have to toggle between our app &amp; their recipe.</em></blockquote><blockquote>· <em>Description: As a user (persona), I want to get inspired to cook a certain dish &amp; an app that does the shopping for me, so that I save time when planning meals. Users see on their home page a bar with recipe recommendations. When the users clicks on a recipe, the users then can read the recipe, select the expected guests &amp; the app will add all appropriate ingredients in the shopping basket.</em></blockquote><blockquote>· <em>Checklist: Add sample recipes to database; Map recipes ingredients to units; Enable recipe bar in the homepage; Create new UI for recipe details; Create logic for adding list of ingredients to shopping cart; Test UI with x test users; Deploy changes</em></blockquote><blockquote>· <em>Definition of done: X number of cooking recipes inspiration live in production</em></blockquote><blockquote>· <em>Success metric: Users that engaged with recipe inspirations show higher A) user retention &amp; B) average shopping cart size</em></blockquote><p>Cards are the center piece of the agile methodology as it basically is the main channel of team management.</p><p>Team management is done via different sessions, called ‘ceremonies’.</p><p>Given that the intention is to accelerate development, you don’t want to commit to anything you don’t know. Hence, agile is done in sprints, commonly two weeks. Every two weeks, the clock resets. Teams can adjust course to their new learnings.</p><p>Each sprint has the following ceremonies:</p><p>1. Sprint planning: Create tasks for each member (first Monday of the sprint)</p><p>2. Standup: Updates on task &amp; discuss on intersections (daily)</p><p>3. Backlog refinement: Review progress &amp; adjust tasks (second Monday of sprint)</p><p>4. Playback: Showcase progress (last day of sprint)</p><p>5. Retrospective: Update ways of working (last day of sprint)</p><p>In the first ceremony, sprint planning, the team finalizes &amp; agrees on what gets worked on for this sprint. It’s usually on the first day of the iteration. Practitioners prepared their cards <em>to the best of their ability</em> prior to the discussion.</p><p>You might ask — each card looks quite detailed and requires oversight into more than just domain. How can the owner know <em>all</em> the right things to build, inside and outside their domain?</p><p>Sprint planning itself is a session, that can run anywhere from 30 minutes to three hours, where teams can have a collaborative discussion. Each card is reviewed one after another, sometimes jumping back &amp; forth, editing the contents on each card.</p><p>Ultimately, the sessions’ objective is to agree on the steps to be build and how they are build. It’s the product manager’s role (depending on the version of agile, also called iteration manager or scrum master), to hold the team accountable. Required is from each practitioner to A) create cards in line with the set requirements, B) check prioritization (as it’s the person with the most oversight) and C) make sure everyone has <em>just enough</em> on their plate (ensuring maximum productivity).</p><p>Next up is the daily standup.</p><p>The intent here is to keep your team in the loop on each other progress as well as to catch blockers early.</p><p>Since the task checklist is not always isolated to the owner, it is common to have overlaps into other departments. Following the recipe inspiration feature example above, the Product Manager might provide you with the recipes. Or a back-end developer might create the shopping cart logic.</p><p>Raising awareness when a task is ready to tackle, reduces idle time. If I am a backend developer hears that the recipes come two days later than expected, he or she can adjust his or her schedule.</p><p>Daily standups can happen any day of the sprint. The main updates from each role should be super crisp, so that the team can get in &amp; out in 10 minutes. If there is something that needs more explanation or a general adjustment, there could be additional deep dives. Those are somewhat extension on issues raised through the standup &amp; could be customer or tech deep dives.</p><p>Halfway through the sprint is the backlog refinement. It’s a slimmer version of the sprint planning, allowing the team to make changes as things changed. Maybe the initial user reaction prompts a change in UI and therefore requirements. Or a high priority ad hoc request needs to be handled first.</p><p>The most benefit in my opinion comes from “yes, and” moments. In those moments, owners can say</p><p>As each owner work on their respective task, they identify further valuable features (= ‘yes, and’ moment). This could be a theme that came out of user validation (for instance, they might like the recipe inspiration, but they also want to get recipe recommendations). It could also be technical nature, for instance today we are pulling data via this workflow, but we could also do it this in the following improved way.</p><p>The backlog can quickly become a trash landfill. It can bloat up, making it difficult to navigate or prioritize. It’s up to the Product Manager to identify themes, merging relevant topics, and removing out of date redundancies.</p><p>On the last day of a sprint, there a two more sessions, the playback and the retrospective.</p><p>The playback is a showcase of the team’s work. Each member gets a fixed time slot to do a show &amp; tell. The keep the session focused, the Product Manager needs to set a format how each member presents their progress.</p><p>The playback is a driver of motivation, as it gives each contributor the stage to receive recognition for their work. If presented well, other team members are much more likely to engage and more likely to provide constructive feedback.</p><p>Also, it serves as inspiration for the next sprint, as it demonstrates where more work should be done or additional ideas that were generated.</p><p>Lastly, it’s a great communication channel to stakeholders, especially internal leadership. It’s likely the most intuitive demonstration of progress. It’s the only ceremony where I would advise to add non-product teams and/or leadership.</p><p>The retrospective can be the last session of the week and tackles the ways of working.</p><p>What does the team feel were detractors? What was helpful?</p><p>This ensures to continuously drive team efficiencies. The session can be done via sticky notes or virtual emulators like mural or miro.</p><p>If team don’t feel they can be open, this session is a waste of time. It all about calling out deficiencies. The regular occurrence of this session gives an invitation to share that feedback. Examples are opaque decision making (reducing motivation) or deviations from process (creating inefficiencies).</p><p>The gist usually is: Sometimes it’s just a small change for an individual that makes a big difference to others. The feeling of being heard itself can be a driver of a good working environment.</p><p>Which brings us to the next topic</p><h3>CULTURE — Execute ruthlessly</h3><p>Culture is difficult to understand or navigate — but it’s there. Always.</p><p>If execution would be a Tesla — strategy would be each component. Agile would be how each component interacts with each other, like if you turn the steering wheel, the wheels turn as well. Then culture is your charging station.</p><p>The charging station is symbolic for the work environment. It’s not what you do (strategy) and how you do it (agile). it’s the energy level of your execution.</p><p>To execute <em>ruthlessly</em>, culture needs to be a power <em>source</em>, not a power <em>drain</em>.</p><p>Culture can be divided in three pillars: individual mindset, team interaction and customer engagement.</p><p>The individual mindset is about standards that each member sets for him or herself.</p><p>While it might seem counter intuitive, from my experience, individuals set standards not based on their own preference, but primarily in response to their peers. If you come into an ambitious team, you are setting yourself ambitious standards.</p><p>For instance, working in investment banking, a traditional high-performance culture, the common mindset is that everyone is keen to be seen as <em>ahead of the pack</em>.</p><p>Not everyone has the ambition to be number one, but no one wants to be last. Therefore, everyone sets their standards slightly higher, which leads to peers raising their standards, creating a flywheel.</p><p>As an organization, culture starts with the mindset of each individual. When new hires come in, do they feel challenged, accept a challenge &amp; raise their standard?</p><p>A leadership team has two ways to influence individuals’ mindsets: Being a role model &amp; meritocracy.</p><p>Leaders must be role models for ambition. If unambitious targets are set or too much organizational slack exists, ambition decreases, and each individual will lower their standards.</p><p>Meritocracy is a great reality check to validate if organizations foster a high-performance culture. Are people promoted based on time served? Or is the age structure heterogeneous within one management layer?</p><p>Individuals who see their managers &amp; peers being ambitious and see plenty of career examples of upward mobility, will set higher standards for themselves.</p><p>Higher standards are essential for a growth mindset and therefore the learning curve of your organization. This is essential to <em>accelerate, not decelerate</em>, your execution.</p><p>The second pillar of culture is team interaction.</p><p>This is usually what people anticipate culture to be all about — how are team members communicating with each other? Is the conversation hostile or friendly?</p><p>Team communication is critical for ruthless execution. If teams are pre-occupied figuring themselves out, there is no time left to figure out what product to build.</p><p>A team needs to be aligned, to streamline efforts. Two values are critical: being empathic &amp; candid.</p><p>Being empathic makes interactions comfortable. Being empathic is only secondary about being nice, but primarily about acknowledging &amp; respecting the perspective of my counterpart.</p><p>Conversations need to be around what <em>my counterpart</em> understands &amp; values. A product manager that approaches an engineer with “I want X because I need Y”, will create friction. Better: “if you create X, we achieve Y, which is good because Z”.</p><p>Empathy enables better execution because there will be less leakage. Conversations will be fewer &amp; shorter. Tasks are not only better understood, but practitioners will have greater motivation, given they understand the “why”.</p><p>Starting to think more about others than yourself, builds the muscle to be purpose — driven. Considering your audience, it will become easier to set meeting agenda’s and clearly communicate where support is beneficial.</p><p>Being candid makes interactions efficient. Peers are the first line of defense. For no one it is easier to recognize constructive feedback than for peers. But how many times did you walk over to your peer and told him what he/she can improve?</p><p>In most organizational cultures, a candid interaction, especially peer to peer, is unheard of. A drain of power.</p><p>Saying “this is interesting”, instead of “this needs more work”, makes you a nicer person, but is a missed opportunity to better execute.</p><p>Due to your peer’s proximity to your work, their tactical advice is a source of power. To tap into it, candid feedback needs to become <em>frequent</em>, so that it’s <em>common</em>.</p><p>Analogous to culture being the charging station, it needs a <em>steady</em> flow of power. Not too much and not too little.</p><p>The retrospective ceremony is key of finetuning the flow. It allows team to ask for less or more. Because the retrospective is a reoccurring meeting, its perfectly suitable for candid feedback. This makes it the ideal lever to adjust to build a healthy team interaction culture.</p><p>A candid culture helps teams (&amp; their manager) holding everyone accountable to their objectives, making sure execution stays on track.</p><p>Executing <em>ruthlessly</em> will feel uncomfortable at times. If being candid is not a onetime event, but an integral part of the culture, it will make feedback <em>a gift</em>.</p><p>Lastly, the cultural approach to customer engagement not only amplifies your culture externally, but also drive urgency.</p><p>Talking to customers can be anything between insightful and annoying. Urgency is what makes it worthwhile.</p><p>If you are not able to reflect standards, it will be tough to scratch anything but the surface.</p><p>If you are not able to interact empathically &amp; candid, it will be tough to understand &amp; uncover real pain points.</p><p>This will <em>hamper</em> execution.</p><p>When an organization is able to do well on the first two dimensions, it can use customer engagement to <em>benefit</em> execution.</p><p>An organization then needs to open the pathway for customer engagement to various parts of the organization. The unlock for agile is the focus on outcome, not on output. Without customer pathway, it will be difficult, if not impossible, for teams to execute.</p><p>Therefore, building a culture that embraces customer engagement is vital. Teams where non-client facing roles drive organically to shadow sales calls, participate in workshops or similar opportunities (at least passively) engage, is a telling sign for customer focus.</p><p>Teams can build a customer focused culture by putting an effort into tracking customer input diligently. There are different levels: Is it scribbles in someone’s notebook? Is it text in a document? Is it a systematic approach tracked in a spreadsheet? Or are they using a dedicated software to aggregate multiple sources of inputs?</p><p>Practitioners are able to infer to what extent their organization values a customer engagement culture by how work is delegated to them. Is it a ‘please add feature X’ or the product manager explaining requirements from a customer perspective (e.g. ‘customer want to do Y, therefore we want feature X’).</p><p>If investing in culture seems like an obscure product of chance, the organization is likely an undiagnosed but ill patient.</p><p>One who experienced a high performance culture will immediately spot a low performance culture and will either adapt or leave.</p><p><strong>A good leader, that embraces an individual mindset with high standards, empathic &amp; candid team interactions and urgency around customer engagement, is one of the best investments a company can make.</strong></p><h3>CONCLUSION</h3><p>As the old saying goes — great ideas fail with poor execution and mediocre ideas succeed with great execution.</p><p>Executing ruthlessly is no easy feat. It’s about bringing together strategy, agile delivery and culture.</p><p>Agile delivery &amp; great culture will fail with poor strategy, as teams will run in circles without direction.</p><p>A great strategy &amp; culture only will fail with non-agile delivery, as teams will be pre-occupied fighting bureaucracy &amp; process, rather than building a product.</p><p>A great strategy &amp; agile delivery itself will fall apart with poor culture, as teams won’t follow suit.</p><p>Being in the center of that Venn diagram increases the chances of success.</p><p>So — What <em>really</em> is the difference between a great idea and a great product?</p><p><em>Ruthless execution</em>.</p><p>Because ruthless execution gets you from idea to product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3390eb48ddd6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ruthless-execution-sprints-to-success-with-strategy-agile-culture-3390eb48ddd6">Ruthless execution: Sprints to success with strategy, agile &amp; culture</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Product launch framework: Six steps for product managers to go live]]></title>
            <link>https://medium.com/design-bootcamp/the-product-launch-framework-six-steps-for-product-manger-daf85e37d02e?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/daf85e37d02e</guid>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-launch]]></category>
            <category><![CDATA[define-success]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Fri, 22 Jul 2022 12:39:58 GMT</pubDate>
            <atom:updated>2023-01-07T10:17:38.706Z</atom:updated>
            <content:encoded><![CDATA[<p>For any product manager, the launch of their product takes courage and can be a daunting task.</p><p>Is this product useful? What if no stakeholder wants to use it? Can we even build it?</p><p>How do I measure success or know if we have product market fit?</p><p>Like many with many product management questions, the secret sauce is breaking down the launch into smaller, manageable chunks of work.</p><p>In this article, we will be highlighting each launching phase, from start to finish. It gives you the toolkit to evaluate success.</p><blockquote>A quick note on the author: Felix is an angel investor &amp; start up advisor. If you have an idea or product and are looking for support or advice tailored to your situation, please get in touch via <a href="https://www.linkedin.com/in/felix-bodensteiner-94964bbb/">LinkedIn</a>.</blockquote><blockquote>You might also like: Check out my post on <a href="https://medium.com/@FBodensteiner/ruthless-execution-sprints-to-success-with-strategy-agile-culture-3390eb48ddd6">Ruthless Execution</a>, how you can bring together Strategy, Agile &amp; Culture to successfully move from idea to product.</blockquote><p>The time it takes to go from just an idea to maturity can be quite long. Having a clear path for execution will set your roadmap up for success. At a minimum, it will increase the odds of success.</p><p>Depending on the phase you are currently in, you’re likely benefiting from diving deeper into the respective nested framework.</p><p>Note that in practice, the product launch phases rarely flow from left to right. Only in the absolute best of launches, everything goes silky smooth.</p><p>You likely will jump back &amp; forth between the phases. As you validate (or more importantly reject) assumptions, you will find yourself to go back one phase, revisit for instance your hypothesis or pilot, before proceeding (again) to the next phase.</p><p>The most important thing that you cannot put in any framework: Your genuine motivation.</p><p>If a product launch is a dreadful task, it likely be an unsuccessful one. Clarity around outcomes creates excitement &amp; let’s you be open to pivots when needed.</p><p>These frameworks will help you to objectively assess performance, endure pushbacks and, eventually, ensure a <em>sustainable</em> product management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oIE78xpU2atyDLB10O0PFQ.png" /></figure><p>Without further a due, let’s get into it.</p><h3><strong>1. Research: Getting to a good hypothesis</strong></h3><p>Before working on an idea, you first need to know what to work on. This sounds trivial, but often, teams are jumping the gun. They dig deep into a specific topic, spending countless hours already on development. They build an asset before having a rough idea of the landscape they injected themselves into.</p><p>The risk of rushing informally through several launch phases is that you find yourself spending time on an asset that don’t work and/or don’t create interest.</p><p>Research lays the foundation to make sure you are building a product (a thing that creates value) and not an asset (just a thing).</p><p>The research phase is often described as phase zero or mixed together with the discovery phase, because in both phases you are spending time on understanding the context.</p><p>I differentiate the two phases because each has their own, distinct success metrics.</p><p>In the research phase, a few Google searches or topic-relevant conversation might suffice, you primarily want to land on well-formulated hypothesis.</p><p>You want to avoid obvious red flags. If your idea is to launch a lemon stand on Moon, quick research would indicate that the problem might not be the recipe, but rather the lack of oxygen. This might not something you want to.</p><h4>Critical for research is: A good hypothesis is both focused and testable.</h4><p>Focus is essential to make meaningful progress. Without boundaries, the attention of product managers is sliced thin.</p><p>Let’s say you want to supply farmers with water during the hot summer months and your idea is to build a dam. A hypothesis like ‘water is valuable’ is too broad. Your discovery phase would be too lengthy &amp; you might lose interest before you even get started.</p><p>The deeper you can go, the better. A product manager needs to have a clear answer, at a minimum, for the ‘who, ‘how’ and ‘why.</p><p>A good start is always to fill the sentence: As a persona (who), I can do a core action (how) to achieve a benefit (why). This turns ‘water is valuable’, to ‘As I farmer, I receive water from the dam, to grow yield in the summer’.</p><p>Next, a hypothesis should also be testable. Testable means that an experiment or pilot will say if the hypothesis was true or false. Water saved through dams either benefited farmers or it did not.</p><p>In contrast, you likely are not able to test if you would sell any lemonade on the moon.</p><p>This is where the great product managers stand out of the crowed. They can think practically. Don’t throw up your hands just yet.</p><p>Being practical means, that you can modify the hypothesis just enough, so can test a similar thing, but under much (much) simpler conditions.</p><p>For example, we can simplify our space hypothesis to ‘Astronauts like lemonade’. While circumstances on earth are arguably different then on the moon, now your hypothesis is testable.</p><h3><strong>2. Discovery: Positioning your product</strong></h3><p>With the hypothesis set, the product discovery framework helps you ironing out the details of your idea.</p><p>This phase requires you to think in both broader &amp; deeper dimensions than before.</p><p>One skill that I learned when working as a peasant in Investment Banking was to properly outline work. Before building any model or doing any research, a senior executive would hand me a (handwritten) strawmen presentation. A strawmen, which serves as a framework, is a presentation that already has a story line &amp; set elements, but only mockups or (vague) placeholders for text.</p><p>A good framework scopes your work both from a horizontal as well as from a vertical perspective. Horizontally, you define buckets, that encompass a limited number of mutually exclusive, collectively exhaustive (MECE) topics. Vertically, since you only have a limited amount of space in the strawmen, it limits the depth of your discovery.</p><p>Once you have set a framework (the strawmen), you can start execution and can make the often so difficult first step. It also helps you to stay organized and not getting lost in the forest.</p><p>This ensures that you have balanced view on all dimensions, before going deep into one specific area, where you sense the most opportunity.</p><h4>My favorite discovery framework for a product launch, comes from <a href="https://www.caseinterview.com/case-interview-frameworks">Victor Cheng</a>, and has four dimensions: Customer, Product, Company and Competition.</h4><p>The order is not chosen at random and roughly reflects how you would sort a start pitch deck as well.</p><p>It starts with the customer and their pain point. Who even is the customer? What are their pain points? How severe is each pain point? Would solve that pain point make a significant difference to their daily life? Or would it just be a marginal improvement?</p><p>Next, you can think about the product. Does it solve the customers pain point? How does it look like? How are you distributing your product to customers and how would they interact with it? Would customers pay for it? If so — how much?</p><p>Now, time to turn inward and look your team, organization or company: What are our capabilities that make the product better and/or enable us to serve the customer better? Also important — an initial calculation on unit economics.</p><p>The last element in the discovery framework is competition. If customers don’t use your product, what else are they doing? Are there competing products or substitutes? Be honest about if your product is a marginal or a substantial improvement? As a rule of thumb, investor legend Peter Thiel famously said that you have to be at least ten times (!) as good as the second best to succeed.</p><p>The insights of each dimension, summarized your discovery under a Proof Of Concept</p><p>Once you have looked into each dimension, a product manager can piece together the puzzle for a sanity check. Can I be the one who solves the pain point? Do I have customers with a pain point big enough to be interested in my product? Can I produce &amp; distribute the product at a profit (eventually)? And would my product substantially be differentiated from others?</p><p>Let’s look at one examples.</p><p>Assume you found that astronauts, after a stroll on the moon, would really like a class of lemonade (customer). You think you can innovate a space safe lemonade (product). And you are already supplying NASA with goods, so you theoretically have a distribution channel (company). But NASA supplies astronauts with lemon water, so your product, while better, might only be a marginal improvement at a probably highly (irresponsible) cost over the ‘competition’.</p><p>It is crucial that every dimension clicks.</p><p>Take ultrafast grocery delivery for example, a market where several companies like Flink, Gorillaz, Getir, Zapp, Jiffy, Dija, Weezy, Fancy, Buyk, JOKR, Gopuff,Fridge No More, 1520 and probably many more are currently fighting (failing) for market attention.</p><p>Many people don’t like or don’t have time to go to the grocery store (customers). Delivering food can solve that pain point (product). Companies found it easy to build an app and a network of riders at a reasonable loss — reasonable for venture capital that is (company). Ordering groceries for me only takes two minutes, going to the grocery store ~30 minutes, meaning delivery is substantial improvement (competition).</p><p>Each dimension gives product managers the building blocks for their elevator pitch. This elevator pitch is your summarized discovery, your concept.</p><p>Since we’re looking for a <em>Proof of</em> concept, the concept has to be validated. Your completed product discovery framework should give you the confidence to proceed, and put your concept in front of customers.</p><p>Product validation is a pitfall, that would make even the largest landfills jealous.</p><p>Validating your discovery with a meaningful number of potential customers is a critical milestone and often done wrong.</p><p>For starters, the sample size has to be large enough. To give ballpark numbers, a validation should at a minimum be more than 10 interviews for a B2B idea and more than 100 for B2C. The more random the people are in the sample, the better.</p><p>What is a meaningful number depends on the purpose. At the end of the day, a product manager needs to determine after speaking with x people, if they are confident with their assessment or not.</p><p>We let our own (confirmation) bias tell us that we found the new sliced bread instead of activating critical thinking. Only because you spend time on a product launch does not make it a good product.</p><p>We cheat ourselves in customer interviews. Graphical speaking, it’s ok to lead customers to the water, but don’t stuff your idea down their throat.</p><p>Imagine a product manager asking: ‘You would like grocery delivery right??’ and seeing ‘I guess so …’ as validation. It is not.</p><p>A lot of startups ask the wrong questions, and end of ‘validating’ their concept, only to find out later on, that no one is willing to buy their product or service.</p><blockquote>My personal two key pieces of advice for customer interviews:</blockquote><blockquote>1. Talk about the customers pain point, NOT about your idea. If customers talk about your idea, perfect. If not, it’s likely not a severe pain point. The best validation is an interview where you talk about your idea, without even mentioning it.</blockquote><blockquote>2. Explain or write down your discovery and give it to someone else to interview customers. Removing yourself prevents you to fall in a bias trap. This someone else, should intentionally NOT be an expert. It’s a great sign if notes from a non-expert match your concept.</blockquote><p>By talking strictly focusing on key pain points (without leading the witness), you quickly learn if the problem you want to solve is an actual problem or a ‘nice to have’.</p><p>During the discovery phase, your initial hypothesis matured to a Proof of Concept. You actually have not built anything, but now have a Proof of Concept.</p><p>Back to our water dam example, a proof of concept could be that you find out that farmers (customer) could have one more harvest with raising their plants quicker via your additional water supply. And you theoretically could store sufficient rain water during the winter months that you then can distribute (product) at reasonable unit economics.</p><h3><strong>3. Product Development — getting to a Minimum Viable Product</strong></h3><p>The Proof Of Concept gives clarity around what customer problem to focus on as well as how to solve it. Theoretically, you can now build &amp; position your product in the market.</p><p>Product development has both a technical (build) as well as a non-technical (position) component.</p><p>Building the product, enabling customer to actually purchase your product, is an obviously fundamental step. Less obvious is the second, non-technical component: Product positioning.</p><p>Let’s start with the building the product: The goal of this phase is to have a Minimum Viable Product, or MVP. While some see a few pretty pictures as a MVP (which I would define as POC), in contrast, I put emphasis on ‘Viable’.</p><p>Viable means ‘capable of working successfully’, and nothing short of that. Your customer should be able to complete the core action of your product. The core action refers to the key pain point your product tries to solve.</p><p>If your idea is instant grocery delivery, customers should be able to get groceries delivered. That is the core action.</p><p>The difference between an MVP and a mature product are the non-core actions. At this stage, those can be non-existent. Your groceries could be ordered by landline and delivered via horse carriage. Maybe you even only can order only toilette paper and bananas. This does not matter as long as completing the (directionally) core action is viable — in this case ordering groceries.</p><p>Good product management thinks in practical terms when it comes to MVPs. Clarity around the core action is crucial. This helps reduce all non-core action to a minimum. Development time has opportunity and often financial cost. Hence, product manager should thin through the ‘time to value’.</p><p>Shorter development cycles could mean faster time to value. Leveraging existing technologies, like no-code applications, especially for everything that is not core to your product, has huge timeline implications.</p><blockquote>One problem I frequently see is that founders &amp; product teams always equate technical sophistication to customer value. It is not. The customer does not care which tech stack you are using, or million features your recommendation engine takes into considerations. Abstract away complexity away from your customer with intuitive UX and a simple (!) process.</blockquote><p>The key is to allow to test your core action — how that action is delivered is somewhat irrelevant. Paul Graham at YC coined the term ‘do things that don’t scale’ to underline that time is best spend first on proving value (even if it’s through manual intervention &amp; drastically simplification, and second on scaling &amp; sophistication.</p><p>Speed however, is just one of two components in getting an MVP ready to pilot.</p><p>That’s where the second element, product positioning comes in. Speed needs to be balanced by market positioning.</p><p>Market positioning is thought to be an exercise left to the big &amp; mature players, but it really is not. Keeping your core action in mind, product managers need to prepare a pilot by getting customer buy in. In this phase, customer buy in should be, at a minimum, a confident assumption, that your product will create demand.</p><p>Without customer buy in, you are unlikely to drive meaningful validation out of your pilot. Great product managers build lean MVPs that create excitement with customers. They are able to position their product in a way that it fits seamlessly into a customer’s workflow or daily routine.</p><p>In our grocery delivery example, let’s say instead of order by landline, you letting customers order by mail. That saves you 2 weeks of development time, which is great. But now you positioned your product outside of the problem-solving zone. By requesting order by mail, you in fact created a new pain point (longer time to get groceries), instead of solving one.</p><p>Market positioning in itself is an entire marketing topic in itself, in short, in the context of product management, its success can be approximated by customer buy in.</p><p>Artifacts for buy in are letter of intents (B2B) or pre-orders (B2C). A more popular (but somewhat of a ‘vanity’ metric, is a waitlist or having a good ol’ customer interviews.</p><p>Especially first-time founders are often hesitant to ask customers for hard artifacts of their interest. The imposter syndrome can kick it: You don’t have a product and maybe not even have a company yet. If your product is for internal use, sell your stakeholder on a pilot playbook that prescribes minimum usage &amp; fixed feedback cycles.</p><p>By requesting these artifacts, you gauge how interest customers are.</p><p>If the pain point is real (proof of concept) but failing to gain buy in, the positioning is off. Iterate on how you pitch your value proposition (e.g. from grocery delivery to meal kit delivery) and/or how you are serving customers (e.g. order by email instead of landline).</p><p>Eventually, you have brought together a minimum viable product, where you can confidently say, that there is sufficient buy in for a pilot.</p><h3><strong>4. Pilot — time to fly</strong></h3><p>Your product finally emerges out of stealth mode and is ready for action.</p><p>This moment is often glorified, product managers dream from going viral and seeing the success roll right in.</p><p>Before I go into the actions, I do want to mention that this phase takes an enormous mental toll, especially on startup founders. Your product is out in the wild — criticism, lack of attention, embarrassing moments, devastating feedback can now be part of your daily routine.</p><p>It is extremely important to maintain emotional boundaries during this phase, separating your product from yourself. For sustainable success, build a healthy habit around how to deal with feedback.</p><h4>Read between the lines and ignore the intensity of feedback.</h4><p>Reading between the lines helps you to categorize feedback and put it into actionable tasks. The better you are in identifying problem themes, the bigger the value of your updates. Seeing every piece of feedback as a problem by itself, you risk of building too many individual features, leading to only incremental value updates and a bloated product that is too complex to scale.</p><p>The hard question you need to continuously ask yourself: Am I executing on requests or am I solving a pain point?</p><p>In both cases, you’re shipping features, but only in the second, you’re shipping value and can eventually achieve product market fit.</p><p>Ignoring the (emotional) intensity of feedback helps you to differentiate need and urgency. Urgency is if 90% of your customers encounter the same problem. Urgency is NOT if one customer is extremely upset. The loudest customer does not automatically have a birthright claim on the most urgent requests.</p><blockquote>Rules of engagement are not only helpful for yourself, but also for your stakeholders (your team, investors and customers). it is crucial to lay out the framework for the pilot to get on the same page on how product market fit is going to be assessed.</blockquote><p>Product market fit is as much art as it is science. What success is for a one, might be failure for someone else. Alignment (In writing!) on how value creation is measured in a pilot is, in my opinion, table stakes.</p><p>At a minimum, a pilot requires agreement on the core action. Why the core action? The core action solves the pain point &amp; thus is most likely to generate demand / economic viability.</p><p>Product market fit for me is that you are able to show the completion of your core action.</p><p>The key here is to understand the nuances ‘completion’.</p><p>For instance, TurboTax offers a lot of help on filling your taxes. But unless you’re actually filing your taxes through them (= the core action), they don’t make any money. Users might have visited, checked out the content &amp; found it super helpful. But if they are not willing to complete the action with your product, you’re not solving a meaningful pain point.</p><p>Ideally the pilot would happen under ‘real life’ boundaries, meaning it is consistent with the market positioning you worked out in the previous step. Price &amp; placement is comparable to what it eventually will be for scaling. This is often unrealistic, given the simplicity of MVP pilots.</p><p>For instance, imagine your product are sunglasses and you hand them out for free at Coachella. I am sure you will complete your core action (people taking &amp; wearing your glasses). Yet I still would have doubts how applicable this proof point is for scaling.</p><p>It is important to note that proof of value creation can be monetary nature (someone pays for your product). Money is a strong indicator. But it could be non-monetary and still compelling. If you do ESG consulting on assets for time poor, high-net-worth individuals, having your user spend an enormous amount of time (which is a limited resource), can count as validation.</p><p>Observing how user complete your core action should run for an adequate time and/or sample size. What is adequate depends on your product and price point. 30 sales are impressive for the above ESG consulting product if it costs $5000. But If your product is a $5 healthy popcorn, 30 sales is not sufficient.</p><p>What makes a great investment case is that a product can take a substantial share in a micro-market..</p><p>Imagine, you’re selling 30 healthy popcorn snacks in your local movie theater. On that day, only 40 people came (75% share). it’s a great proof point. If 3000 guests came (1% share), not so much. And if you show a for an entire month, every day and sell popcorn to 75% of visitors, and maybe that share is even increasing, that’s what will spark interest.</p><p>A ‘stable’ completion rate of your core action makes investors comfortable, that your product might work in more than just this one micro market.</p><p>That is the proof point you want to take away from your pilot. It <em>could</em> work at scale.</p><blockquote>And by the way — unsuccessful pilots are important because it avoids costly mistakes and allows you to re-focus on other items. Not selling a lot of popcorn in a cinema informs you that either popcorn is the wrong product, movie theater is the wrong place, or the product is just not appealing. Any of those paths help you to pivot gracefully.</blockquote><p>In this initial stage, founders are often tempted to look at things besides their core metric.</p><p>Other metrics, that do not generate economic activity, like (free) downloads, waitlist, views, demo’s (and the list goes on), should not be considered in assessing initial product market fit.</p><p>Don’t get me wrong — if you have 100k people on your waitlist and/or your app has been downloaded 50k times, I am impressed. I count that as ‘attention’ and a significant Go-to-market advantage for scaling, but don’t see it as initial product validation.</p><p>Once you know you have an initial product market fit, it’s time for scaling.</p><h3><strong>5. Scaling — one step, two step, many steps</strong></h3><p>The distribution of your product is often underrated.</p><p>The mentality ‘we’ll build it &amp; they will come’ is dangerous. I personally would rather invest in a mediocre product with excellent distribution than an excellent product with mediocre distribution.</p><p>Think about it — have you eaten the best sushi in the world yet? Chances are the best sushi chef has not settled for a restaurant close to your home. And then you probably have eaten mediocre sushi.</p><p>Scaling can happen it multiple ways, there is no ‘one size fits all’ growth. Depending on your budget, team or other constraints, growth might be slow or hyperbolic.</p><p>What you want to look for during scaling is the reoccurring completion of your core task from an increasing number of users, for instance with a cohort analysis.</p><p>In essence, a cohort analysis lays out cohorts (e.g. when a user signed up) and tracks the completion of the core action over time. For instance, user who signed up in March, what percent was still a Monthly active user in April, May, June, July. Does it drop to 0% (bad, not reoccurring)? Or are 99% still active (great, action reoccurring)?</p><h4>A cohort analysis allows you so see how ‘reoccurring’ your business model and core task is.</h4><p>Let’s dive first into the ‘why’ the business model is relevant for scaling. A product manager needs to be aware that support for his / her product might be limited, despite having the product being a smashing success otherwise.</p><p>If you initially paid $1 for google ads from which you generated that $2 in profit, does this ratio hold true the longer and more you invest. If you see that ratio drop to &lt;1, meaning negative unit economics, it shows that you reached the end of you product market fit. At least for the product in its current version.</p><p>Depending on how risk averse you are, unit economics don’t have to be highly profitable on day one (although that would be very nice). But eventually, investor need to see path to positive unit economics to sustain a business.</p><blockquote>Not all growth is sustainable. Moviepass offered unlimited movie theatre tickets for $10 per month. Customers subscriptions skyrocketed (core action = subscription) and they enjoyed low churn. They pitched investors likely on turning a profit eventually (more revenue via higher subscription fee’s and lower cost, e.g. by better negotiating rates with movie theatres). There were signs of product market fit and the growth was great.</blockquote><blockquote>But it was not a business model where you wanted core actions to reoccur, making scaling unsustainable and the company imploded.</blockquote><p>Unit economics need to get better as you scale (or stay the same if they are profitable at the beginning). If you realize that either users are not as engaged as before (reduction of core action) or observing shifting unit economics, it’s time to adjust. Otherwise you’re throwing money into a furnace.</p><p>It’s important to recognize that growth should be iterative.</p><p>Iterative here means that you don’t have to stick to your initial concept 100% as you scale. In fact you probably should not. Things change, customer tastes &amp; market environments require you to adapt. Great organizations are able to iterate quickly AND continuously.</p><p>Digital players here have a clear leg up as they are primed for A/B testing. Players like AirBnB, Facebook &amp; Google test tweaks by showing modified version of it’s webpage to subset of users. For instance, for testing which color a certain button should be, while most users would see the original color (= A sample), the test set would get the button in a different color (= B sample). Based on user engagement, the team knows if A or B yielded higher engagement &amp; proceed accordingly.</p><p>A/B testing enables you to break your cohort analysis into more dimension. More testing means faster progress, which usually increases your chances of winning a market. What works for big tech, also works for every ecommerce or even every website or app.</p><p>The ability to find innovative ways for repeatable value creation is what will allow you to ‘cross the chasm’, going from early adopters to mainstream.</p><h3><strong>6. Maturity — time to say goodbye</strong></h3><p>Markets are finite. At a certain point your product will reach saturation, where growth will plateau.</p><p>Back in our food delivery example, maturity could mean that essentially everyone who orders food online, is doing it through your app. Given that some people remain on substitutes (going to the store themselves) or competitors (another food app), growth can quickly flat out.</p><p>So — what’s the plan then?</p><p>A question that Venture Capitalist sometimes asks founders is ‘what is your exit strategy’. This sometimes catches founders on the wrong foot. They are about to build a product, not abandon it.</p><p>The intend of this question is not only of financial interest, but also reflects well on if the founder has a vision of how success looks like.</p><h4>There are two elements to this question that are key for product maturity: Financial &amp; product endgame.</h4><p>Financial endgame represents that each product eventually should lead to financial success. Financial success is defined as Return on Investment, or ROI in short. The return (= benefit) outweighs the investment.</p><p>In our food delivery app example, if you took in money from investors, how are they receiving a payout? Is a local grocery chain going to buy your app &amp; integrate within their services?</p><p>Or if you are building a product within a company, once you enabled a benefit, how can you eliminate investment (= time spend)? When is the right time to cap (= end) investment and transition the product to an operator to optimize ROI?</p><p>Financial endgame considers different scenarios (options) to test. The ROI serves as decision metric to choose the best path going forward.</p><p>Product endgame on the other hand, informs you <em>when</em> to pull the trigger.</p><p>Let’s say the vision for food delivery app was that millennials are ordering lunch through your app. The key here is to understand how success looks like. Is it 20% or 80% of millennials? Are they ordering once a week or five times a week? The goals you had set for the pilot were a starting point. As the product is iterating &amp; growing, targets should be adjusted.</p><p>Once reasonable time &amp; adequate testing show only no to marginal improvements, a product might has hit a plateau. Maybe it’s just x% of millennials that like to order food — or maybe they only want to order y days per week.</p><p>Overcoming barriers is tough — ROI offers an insights into which path would enable you to better deploy your time and/or capital.</p><p>Scenarios to consider are to divest, invest or to maintain (delay).</p><p>Divesting could mean selling it externally (e.g. your grocery app to a grocery chain) or internally (e.g. from your engineering team to an ‘operator’ team or another business unit).</p><p>Investing would mean that you see light at the end of the tunnel &amp; it’s worth going big once more. This is a viable option if the ROI of expansion is attractive. Expansion can be by either customer (e.g. serve millennials and Gen Z) or market (e.g. serve new cities / adding secondary products) or both (Leveraging your USP for a new purpose, e.g. Uber using their networks effects to go from ride hailing to uber eats).</p><p>Maintain is the decision that is often taken unconsciously. Stereotypical for slower, larger corporates, people like to ‘wait another quarter’ to feel more comfortable taking a decision. This is a good option, especially if the leadership sees conflicting evidence or misaligned teams.</p><p>In practice, this decision is rarely, black &amp; white, nice &amp; easy.</p><p>For sports teams, you often see that some teams decide to stick with their team &amp; only make minor tweaks, and all of a sudden performance explodes, breaking the level that was seen as barrier previously. Other teams buy a whole new team and are playing for the championship right away (e.g. big three at Miami heat). At the same time, this concepts fails for others (e.g. Brooklyn nets).</p><blockquote>As per the famous quote from Theodore Roosevelt: ‘In any moment of decision, the best thing you can do is the right thing, the next best thing is the wrong thing, and the worst thing you can do is nothing.’</blockquote><p>There is no <em>right</em> answer — but ROI can help you find a <em>possible</em> answer.</p><h3><strong>7. Conclusion — Product management is playing the odds</strong></h3><p>In each step of the lifecycle, you can use frameworks to your advantage. They make it easier to attest success and failure. They enable teams to learn faster &amp; build better products.</p><p>The reality is: Most projects will show mixed results and interpreting success can be more an art of reading the tea leaves than a science.</p><p>Building products are no experiment in a laboratory. External forces will always cloud performance &amp; infuse volatility.</p><h4>Frameworks are your toolkit to raise standards, drive urgency and align teams.</h4><p>Raising standards is a crucial element to lead an ambitious team, clear targets sharpen the focus on the right things. Distractions come in form of bloated products.</p><p>Objectives force you to timebox phases, which drives urgency. This is a substantial management advantage for efficiency, as it makes progress transparent to every team member.</p><p>Transparent objectives are meaningless when not embraced day in &amp; day out. Aligning your team around an ownership mentality will make or break execution.</p><p>Even a great idea won’t see the light at the end of the tunnel if executed poorly. But many mediocre ideas become successful through great execution.</p><p>Hence, leveraging this toolkit allows you to create an opportunity to success. It increases the odds of success. Only destiny will tell if your product has the legs to become a billion-dollar product.</p><p><strong>My advice: Play the odds with diligent execution.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daf85e37d02e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-product-launch-framework-six-steps-for-product-manger-daf85e37d02e">The Product launch framework: Six steps for product managers to go live</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Corona testing — What are the options for the Bundesliga?]]></title>
            <link>https://medium.com/@FBodensteiner/corona-testing-what-are-the-options-for-the-bundesliga-cd6cdfe82fd2?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd6cdfe82fd2</guid>
            <category><![CDATA[corona]]></category>
            <category><![CDATA[bundesliga]]></category>
            <category><![CDATA[corona-testing]]></category>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Fri, 24 Apr 2020 09:25:23 GMT</pubDate>
            <atom:updated>2020-04-24T09:29:07.749Z</atom:updated>
            <content:encoded><![CDATA[<h3>Corona testing — What are the options for the Bundesliga?</h3><p>After some (most) western countries initially neglected corona testing, they now want to ramp up their capacities. It’s not only governments that are interested, but also the private sector is watching closely.</p><p>The Bundesliga, German’s professional soccer league, wants to continue the season, testing every player &amp; support staff once a week/prior to a game — Supporters are not allowed.</p><p>Even “Ghost Games” (this is what Germans call games without supporters) would require 20,000 tests — a large amount for only nine match days. Tests that could also benefit doctors, teachers or people that are arguably “more important” than soccer players. The league is deflecting, saying that Germany has free testing capacity &amp; that they are investing in testing expansion, benefiting non-soccer stars as well.</p><p>While both sides (may) have a point, in the end, it’s just a question of money, as hospitals don’t have funds to extend testing their staff and the <a href="https://rp-online.de/sport/fussball/bundesliga/corona-krise-letzte-rate-der-tv-gelder-fuer-die-bundesliga-steht-noch-aus_aid-50075819">Bundesliga gets +€300mn in television rights</a> to finish the season. Test kits bought checkmark.</p><p>Let’s imagine everyone had enough funds &amp; there are no limitations, if you had an instant test available for your employees / customers, we could go back to business as usual. Right?</p><p>It’s not as easy as that as there a different testing options, meaning corona test != corona test and, spoiler, none of them is instant. For the following options, a swab absorbs body liquid from the nose or throat &amp; is then analyzed.</p><p><strong>Option 1: Antibody test (“quick &amp; dirty”)</strong></p><p>Antibody tests are the fastest option (~15 minutes), they looks into the proteins in the sample, specifically viral ones, called antigens, or the antibodies produced by our body.</p><p>While quick, this option has two big drawbacks: Firstly, antigens are only produced ~one week into the disease, meaning in the first few days, when people are most contagious, the test results would come back negative. Detecting antibodies (produced in the second week) only shows that the patient has actually already got through corona. Secondly, the test accuracy is lower — depending on the study (or product!) of your choice, <a href="https://www.ft.com/content/a93e6b28-3778-4089-8d80-4e6775996aea">it’s anywhere between 60–90%.</a></p><p>The Bundesliga wants to use those test as they are practical, however, knowing that the statistics would tell us that +2 players of the 22 players on the pitch have a false diagnose, then you actually can NOT safeguard the health of each player. At that point, they could also consider simply taking the temperature, which would yield only slightly worse results (you would miss asymptomatic infections), with significant less effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ZeEAnJxlKPpnxZem" /><figcaption>Financial Times: <a href="https://www.ft.com/content/a93e6b28-3778-4089-8d80-4e6775996aea">https://www.ft.com/content/a93e6b28-3778-4089-8d80-4e6775996aea</a></figcaption></figure><p><strong>Option 2: Genetic test (“the real deal”)</strong></p><p>Genetic tests are slower, taking several hours, but far more reliable. Most labs are using the polymerase chain reaction (PCR) method.</p><p>In simple terms, the test swab has string of DNA, you then isolate certain regions of the genome (in this case, the “Corona” nucleic acid) and then PCR amplifies that sample, running for +20 cycles &amp; exponentially breeding new strings, eventually creating billions of DNA strings. This is essential to make anything visible given the small size of a DNA string. Now that you have a large sample, you add a gel to visualize the presence of the Corona virus. Voilà!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BsqPq_IN_JvN_41W.jpg" /><figcaption>PCR factsheet: <a href="https://www.genome.gov/about-genomics/fact-sheets/Polymerase-Chain-Reaction-Fact-Sheet">https://www.genome.gov/about-genomics/fact-sheets/Polymerase-Chain-Reaction-Fact-Sheet</a></figcaption></figure><p>Genetic tests are extremely accurate &amp; automated but takes 2–4 hours. While technically perfect, it would be too long for the Bundesliga to test players before a game. Besides time, a second disadvantage over the antibody test is, that it only identifies currently infected patients, NOT recoveries, an information that would be valuable as well.</p><p>The best way would be to use a combination of both tests, but that would make the Bundesliga look pretty greedy and who wants that negative PR.</p><p><strong>So what</strong></p><p>Given that many smart minds worldwide are currently investigating testing innovations, expect this article to be outdated in the next couple of months (if not weeks). But there are limitations (time &amp; accuracy) that are unlikely to be resolved entirely, so I would not expect a testing quick &amp; inexpensive enough to test people entering the New York subway, FC Bayern games or for other high-volume applications.</p><p>In the end, the Bundesliga has to balance infections (being active, wearing protective gear, …) &amp; investments (testing gear &amp; frequency, …). What I find interesting is, in the absence of a clear answer, this decision will mainly reflect the willingness to accept risk. It seems soccer clubs, on the verge of insolvency, are willing to accept the risk &amp; are satisfied with flimsy testing safety.</p><p>— -</p><p><em>(This article is part of TheIntriguing.com newsletter — </em><a href="https://www.theintriguing.com/"><em>sign up now</em></a><em>)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd6cdfe82fd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How much should your country pay for Corona?]]></title>
            <link>https://medium.com/@FBodensteiner/how-much-should-your-country-pay-for-corona-4ff8f468bc78?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ff8f468bc78</guid>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[debt]]></category>
            <category><![CDATA[coronabond]]></category>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Wed, 01 Apr 2020 11:31:03 GMT</pubDate>
            <atom:updated>2020-04-01T11:31:03.788Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week was Corona Stimulus week — nearly every country worldwide announced economic packages supporting their national economy. With stores closed, work from home and significant layoffs, policy makers agreed on additional fiscal support (= government spending).</p><p><strong>So if stimulus is needed — then how much stimulus is too much?</strong></p><p>Fiscal stimulus is mostly financed through debt, at some degree, those packages might not be affordable. Countries could find themselves not able to repay the debt, causing a debt crisis, that would send the local economy spiraling, potentially far worse than any corona crisis.</p><p><strong>What are Corona packages?</strong></p><p>Different countries announced different measures, for the most part it includes company bailouts (e.g. travel/aviation industry), loans &amp; grants to businesses (e.g. Germany KfW loans) but also health care funding, funding of social services and even one-time payments to individuals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*iHJXBEh3bYfyRL-6oe8FUA.png" /><figcaption>Source: <a href="https://www.aljazeera.com/news/2020/03/congress-approves-2-trillion-coronavirus-rescue-package-200327133845317.html">Budget Dog</a></figcaption></figure><p><strong>It’s important to note two things:</strong></p><p>1) Countries have different opinions about what measures are effective, which is why packages differ from country to country.</p><p>2) Fiscal policy is only half of the truth, monetary policy (e.g. USA = FED, Europe = ECB), provides liquidity by injecting (more) money into the economy by buying government &amp; company debt. Without monetary policy, it would be nearly impossible for some countries to raise an exorbitant amount of debt in a short time period.</p><p><strong>How much can each country spend?</strong></p><p>A difficult question, as there is no set ceiling. For simplification, this is dependent on 1) the ability to repay debt and 2) the amount of debt a country can raise.</p><p>Let’s look at the ability to repay first: Countries are no startups — We actually have a history about their budgets and how (ir)responsible they spend money / build reserves. The last five years have been extremely positive, economically speaking, for most countries. If we look at a countries stock index (e.g. DAX for Germany), as indicator for economic growth, we get a sense of “returns” that a country could have used to repay debt / build reserves.</p><p>After all, excess returns should be used to pay down debt (you hear your German friend say). If we compare the “stock return” proxy to the increase (or decrease) of debt per country, we can see an interesting picture: European countries (e.g. Germany), reduced their debt by 22%. Over the same time period the DAX was up 41%, meaning they used this prosperous time to build reserves, which is responsible (Note that there is an argument to be made that Germany should have invested more).</p><p>To compare different economies, we can look at the delta of these two numbers, e.g. Germany 19% (= -22% + 41%), to get an estimate on how much the country overspend in this period (if phrased as euphemism, you could say 19% “invested”). As comparison, The US debt increased by 2%, despite the S&amp;P 500 being up 77% (=79% overspending). Clearly, the US was less eager to build reserves than Germany.</p><p>Arguably, the lower the overspending, the more likely someone would lend money to that country. It’s far off from a financial measure of actual ability to repay, but it tells you something about the borrowers’ profile. If you were overspending before, cost cutting restructuring need to be far more painful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*Z6SQjkCtACJXwoRnuMHjwA.png" /><figcaption>Size of bubbles = GDP; Source: GDP (<a href="https://www.imf.org/external/pubs/ft/weo/2019/02/weodata/weorept.aspx?pr.x=57&amp;pr.y=17&amp;sy=2019&amp;ey=2019&amp;scsm=1&amp;ssd=1&amp;sort=country&amp;ds=.&amp;br=1&amp;c=512%2C668%2C914%2C672%2C612%2C946%2C614%2C137%2C311%2C546%2C213%2C674%2C911%2C676%2C314%2C548%2C193%2C556%2C122%2C678%2C912%2C181%2C313%2C867%2C419%2C682%2C513%2C684%2C316%2C273%2C913%2C868%2C124%2C921%2C339%2C948%2C638%2C943%2C514%2C686%2C218%2C688%2C963%2C518%2C616%2C728%2C223%2C836%2C516%2C558%2C918%2C138%2C748%2C196%2C618%2C278%2C624%2C692%2C522%2C694%2C622%2C962%2C156%2C142%2C626%2C449%2C628%2C564%2C228%2C565%2C924%2C283%2C233%2C853%2C632%2C288%2C636%2C293%2C634%2C566%2C238%2C964%2C662%2C182%2C960%2C359%2C423%2C453%2C935%2C968%2C128%2C922%2C611%2C714%2C321%2C862%2C243%2C135%2C248%2C716%2C469%2C456%2C253%2C722%2C642%2C942%2C643%2C718%2C939%2C724%2C734%2C576%2C644%2C936%2C819%2C961%2C172%2C813%2C132%2C726%2C646%2C199%2C648%2C733%2C915%2C184%2C134%2C524%2C652%2C361%2C174%2C362%2C328%2C364%2C258%2C732%2C656%2C366%2C654%2C144%2C336%2C146%2C263%2C463%2C268%2C528%2C532%2C923%2C944%2C738%2C176%2C578%2C534%2C537%2C536%2C742%2C429%2C866%2C433%2C369%2C178%2C744%2C436%2C186%2C136%2C925%2C343%2C869%2C158%2C746%2C439%2C926%2C916%2C466%2C664%2C112%2C826%2C111%2C542%2C298%2C967%2C927%2C443%2C846%2C917%2C299%2C544%2C582%2C941%2C474%2C446%2C754%2C666%2C698&amp;s=NGDPD&amp;grp=0&amp;a=">IMF</a>), Government Debt &amp; growth (<a href="https://www.imf.org/external/datamapper/GGXWDG_NGDP@WEO/OEMDC/ADVEC/WEOWORLD">IMF</a>) and Stock returns (<a href="https://finance.yahoo.com/">Yahoo</a>)</figcaption></figure><p>That brings us to the second dependency, a countries ability to raise debt. The more debt a government already has, the higher the financial burden / risk. As a benchmark, the EU guideline for debt as a percentage of GDP is 60%. Well, they call it a guideline, seeing that most countries are well above that it’s more of a well-intentioned advice from a distant uncle.</p><blockquote>Looking at country’s debt together with the respective overspending, we see that the European countries (plus Canada &amp; UK) have been significantly more responsible than the rest of the world. In a global world, it is important to understand that countries can just not look at only themselves. If the two big overspending bubbles (USA &amp; China) burst, it will be a severe blow to the European savers. Good thing they build reserves.</blockquote><p><strong>How does the corona stimulus impact debt loads?</strong></p><p>While measures are similar across countries, the size is different. Learning from above that Germany might have more legroom than other countries (as they used the last five years to retire some of their debt), it is less surprising that they announced the largest package (as % of GDP) yet.</p><p>Plotting the Corona stimulus as % of GDP together with the (pre-corona) planned budgeting, this gives us an indication about which country might be willing to load on even more debt. Germany planned to repay another 22% of their debt, but now decided to spend ~$810bn (or 21% of their GDP) on their Corona package — a zero-sum game, highlighting that Germany operates still within their means (the “black zero” as they like to call it).</p><p>Now, if your country is on the other side, meaning that they already had planned a deficit (e.g. USA almost 10%), putting another significant debt load will be riskier. The only thing we can say is, that it is risky, but, as we see, not impossible to get done. We’re likely going to see additional stimulus from the countries that only initiated smaller packages so far (e.g. Italy, India, France, Brazil).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*ygRxQ9Q-i3PDBw3SfXQmNQ.png" /><figcaption>Source: Planned debt (IMF, same as above), Corona Stimulus (at bottom), as of 3/31</figcaption></figure><p><strong>Debt Innovation — the Corona Bond</strong></p><p>So far we only looked at country-specific debt &amp; stimulus. While this is the only option for isolated countries (e.g. USA, China), Europe is a community that could pull together (financially). This is where the so-called “Corona-Bonds” are coming in, which is issued debt guaranteed by all / multiple member countries.</p><p>Since the cost of debt (interest) is dependent on a countries risk, e.g. Germany actually earns money when they issue debt (through negative interest rates) while less fortunate countries pay ~2%, Corona Bonds would increase interest for some, while reducing for others. To highlight this difference, if Germany would have paid their package through a Euro bond, they would have need to PAY ~$16bn/year instead of EARNING ~$3bn — A $20bn difference (which is almost the size of Germanies entire spending on education per year).</p><p>Not surprisingly, Germany (&amp; the Netherlands) are opposing this proposal, while others (e.g. France, Spain, Italy, Portugal) are in favor. Opponents are afraid they are getting stuck with someone else’s debt. To make the concept of Eurobonds compelling, the European union would need either one (ideally both) of the following two things:</p><p>1) Generate fiscal proceeds used to repay the debt (e.g. each country needs to give a fixed % of their tax revenue to the EU)</p><p>2) Fiscal spending rules (e.g. Proceeds are only allowed to spend for certain things)</p><p>Both of these require the transfer of national authority to the European Union. This would be an unprecedented step, as of now, maintaining the sovereignty of each country is one of the fundamental rules.</p><blockquote>This comes at a time where nationalist governments are trying to isolate themselves (e.g. UK, Poland). It is going to be VERY interesting to see how this develops as it will shape European politics for decades.</blockquote><p>Richer countries, such as Germany, have to balance if they want to either A) guarantee European debt with the risk of assuming some of it eventually or B) seize the opportunity to build a strong financial bound that would make Europe significantly more competitive globally, more competitive than any country ever would be individually.</p><p>This might also serve as a role model for an Africa, ASEAN or LA-bond.</p><p><strong>Time to be practical, no time for bureaucratic soul searching.</strong></p><p><em>(This article is part of TheIntriguing.com newsletter — </em><a href="https://www.theintriguing.com/"><em>sign up now</em></a><em>)</em></p><p>— —</p><p>Sources:</p><p>GDP per country: <a href="https://www.imf.org/external/pubs/ft/weo/2019/02/weodata/weorept.aspx?pr.x=57&amp;pr.y=17&amp;sy=2019&amp;ey=2019&amp;scsm=1&amp;ssd=1&amp;sort=country&amp;ds=.&amp;br=1&amp;c=512%2C668%2C914%2C672%2C612%2C946%2C614%2C137%2C311%2C546%2C213%2C674%2C911%2C676%2C314%2C548%2C193%2C556%2C122%2C678%2C912%2C181%2C313%2C867%2C419%2C682%2C513%2C684%2C316%2C273%2C913%2C868%2C124%2C921%2C339%2C948%2C638%2C943%2C514%2C686%2C218%2C688%2C963%2C518%2C616%2C728%2C223%2C836%2C516%2C558%2C918%2C138%2C748%2C196%2C618%2C278%2C624%2C692%2C522%2C694%2C622%2C962%2C156%2C142%2C626%2C449%2C628%2C564%2C228%2C565%2C924%2C283%2C233%2C853%2C632%2C288%2C636%2C293%2C634%2C566%2C238%2C964%2C662%2C182%2C960%2C359%2C423%2C453%2C935%2C968%2C128%2C922%2C611%2C714%2C321%2C862%2C243%2C135%2C248%2C716%2C469%2C456%2C253%2C722%2C642%2C942%2C643%2C718%2C939%2C724%2C734%2C576%2C644%2C936%2C819%2C961%2C172%2C813%2C132%2C726%2C646%2C199%2C648%2C733%2C915%2C184%2C134%2C524%2C652%2C361%2C174%2C362%2C328%2C364%2C258%2C732%2C656%2C366%2C654%2C144%2C336%2C146%2C263%2C463%2C268%2C528%2C532%2C923%2C944%2C738%2C176%2C578%2C534%2C537%2C536%2C742%2C429%2C866%2C433%2C369%2C178%2C744%2C436%2C186%2C136%2C925%2C343%2C869%2C158%2C746%2C439%2C926%2C916%2C466%2C664%2C112%2C826%2C111%2C542%2C298%2C967%2C927%2C443%2C846%2C917%2C299%2C544%2C582%2C941%2C474%2C446%2C754%2C666%2C698&amp;s=NGDPD&amp;grp=0&amp;a=">IMF</a></p><p>Debt per country: <a href="https://www.imf.org/external/datamapper/GGXWDG_NGDP@WEO/OEMDC/ADVEC/WEOWORLD">https://www.imf.org/external/datamapper/GGXWDG_NGDP@WEO/OEMDC/ADVEC/WEOWORLD</a></p><p>Stock index return: <a href="https://finance.yahoo.com/">https://finance.yahoo.com/</a></p><p>Stimulus per country:</p><p><a href="https://www.dw.com/en/coronavirus-what-aid-packages-have-governments-agreed/a-52908669">https://www.dw.com/en/coronavirus-what-aid-packages-have-governments-agreed/a-52908669</a></p><p><a href="https://www.reuters.com/article/us-health-coronavirus-japan-stimulus/japan-plans-huge-stimulus-package-to-cushion-blow-from-coronavirus-idUSKBN21E0UW">https://www.reuters.com/article/us-health-coronavirus-japan-stimulus/japan-plans-huge-stimulus-package-to-cushion-blow-from-coronavirus-idUSKBN21E0UW</a></p><p><a href="https://www.cnbc.com/2020/03/26/coronavirus-india-needs-a-support-package-larger-than-20-billion-dollars.html">https://www.cnbc.com/2020/03/26/coronavirus-india-needs-a-support-package-larger-than-20-billion-dollars.html</a></p><p><a href="https://www.bbc.com/news/business-51921922">https://www.bbc.com/news/business-51921922</a></p><p><a href="https://www.reuters.com/article/us-health-coronavirus-italy-stimulus/italy-pm-adopts-new-measures-to-help-coronavirus-hit-economy-idUSKBN21F0WS">https://www.reuters.com/article/us-health-coronavirus-italy-stimulus/italy-pm-adopts-new-measures-to-help-coronavirus-hit-economy-idUSKBN21F0WS</a></p><p><a href="https://www.bbc.com/news/world-us-canada-52022506">https://www.bbc.com/news/world-us-canada-52022506</a></p><p><a href="https://www.ft.com/content/0f289d20-6e97-11ea-89df-41bea055720b">https://www.ft.com/content/0f289d20-6e97-11ea-89df-41bea055720b</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ff8f468bc78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t be fooled by Corona numbers — they are wrong]]></title>
            <link>https://medium.com/@FBodensteiner/dont-be-fooled-by-corona-numbers-they-are-wrong-8f549187dbf2?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f549187dbf2</guid>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[corona]]></category>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Tue, 24 Mar 2020 11:30:19 GMT</pubDate>
            <atom:updated>2020-03-24T17:46:53.423Z</atom:updated>
            <content:encoded><![CDATA[<h3>Don’t be fooled by Corona numbers — they are wrong</h3><p>Who doesn’t like the neatly-designed corona stats, updated throughout the day, giving us the impression that we have an overview on A) how bad it is (Total number of cases) and B) Where it’s bad or worse (country by country comparison).</p><p>Independent on which news outlet you are consuming, all are quoting the same set of numbers — John Hopkins map is the new sliced bread. One source of truth is good, assuming the data is correct — but it isn’t.</p><p>The number of cases shown us the results from successful tests conducted. If you don’t conduct tests (e.g. UK, USA), your numbers stay (incorrectly) low. You are NOT looking at number of corona cases — you are looking at a TEST statistic.</p><p><strong>Why the testing statistic is flawed</strong></p><p>(Even) in Germany, where tests are somewhat available, getting tested are only A) people of a risk group (e.g. pre-existing condition / advanced age, which are only few people), B) people who recently traveled to China (very few people), C) people who were in contact with confirmed cases (even fewer people) or D) if you belong to a special group (e.g. professional athlete, which is close to no one). Not to mention the vast majority of cases, which are mild &amp; are highly unlikely to be tested to begin with.</p><p>While many people understand this conundrum, the implications are somewhat misunderstood.</p><blockquote>How would you model cases by country, (largely) independent of test results?</blockquote><p>First, Let’s do some math to see where each country started:</p><p>China has 1bn international travelers per year, Hubei (the providence where the virus originated) makes up ~4% of the Chinese population, meaning we would expect ~40mn international travelers from Hubei per year. Well, Hubei residents are probably less likely to travel international than people from Shanghai, so let’s half that to ~20mn.</p><p>China’s Corona alert to the WHO was on Dec 31, (partial) lockdown in Hubei started on Jan 23: 24 days the virus spread without limitations, in this time frame (24 days) we would expect ~1.4mn people who traveled internationally from Hubei, spreading the virus globally (if infected).</p><p><strong>So how many people where affected?</strong></p><p>If the time from infection to death is 14 days and 14 days after the lockdown, on Feb 7th, the reported Chinese death toll was 722, assuming a mortality rate of 4.3% (as per China closed cases 3/22), the implied number of affected people was close to 17k. If only severe cases are tested (~20%), the true number of active cases was likely ~84k, which is ~0.15% of the Hubei population. To visualize, that is 15 out of 10,000 people or ~100 people in a sold-out Allianz Arena (home of soccer club Bayern Munich).</p><p>If in the alert to lockdown period ~20mn people traveled internationally from Hubei and ~0.15% were infected, ~2k infected people left China. The R0 (people one infected person transmits the disease to) is 2.2, the world excluding China started with ~4,500 corona cases. A lot of math for one number.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/1*O7fMgnIFa58YhEddF6SlXw.png" /><figcaption>Calculations from above — sources at bottom</figcaption></figure><p><strong>Where did the infected people go?</strong></p><p>Since the virus is spread via people, it is fair to assume that the virus (without) intervention spreads highly correlated to the economic relationships of China, meaning more trade = higher spread.</p><p>For the following, we assume that people traveled internationally proportionally to Chinese export to the respective country. For instance, Chinese exports in 2018 totaled ~$2.500bn, thereof ~$500bn to the US, which implies that close to 20% of corona cases abroad or 870 were in the US on Feb 7th. Here you see the first disconnect to reported numbers — the US reported only less than 100 cases even until March, with +870 cases only officially reached on Mar 10th (more than one month later)</p><p><strong>Now that we distributed all base cases to the countries, how did the virus expand?</strong></p><p>Korea, a corona role-model (more on this below), has likely one of the most reliable testing data. On their Corona peak on Mar 3rd, 851 new cases were added to a base of 4,335, implying a ~20% growth rate per day. Using this growth rate, we can estimate the corona numbers for all countries. For instance, if the US had 870 cases on Feb 7th, they had 1,041 on Feb 8th, 1,245 on Feb 9th and so forth.</p><p>Looking at the table below, e.g. for the US on Mar 6th, we would expect the number of true cases to be ~131k, ~26k with symptoms (~20% of true cases) and close to 6k deaths (using the same 4.3% death rate as above). As quality check, Korea had 6,593 confirmed cases on Mar 6th, compared to our 5,981 estimated cases with symptoms (those likely to be tested), which only represents a ~10% ‘error’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NUnc4irwBFSKOhIRwGwpiQ.png" /><figcaption>True Number of Cases per country (top 25 countries per export excluding HK as distribution hub)</figcaption></figure><p><strong>Why not testing extensively is a big issue</strong></p><p>Let’s pause for a second and say we believe there is a high number of true cases, undetected by tests: This group of people are likely socially active (they caught the virus) &amp; healthy (no severe symptoms). It’s not children or seniors — (Young) adults are the “super-spreader’ and motor of the virus.</p><p>This is why Korea is a role model, encouraging (!) tests for ALL individuals, which no restrictions (such as those for Germany mentioned above). If you really want to slow down the spreading / “flatten the curve” you need to close the fuel tap of the virus, which is to take young adults out of the equation. E.g. in Germany, since we merely diagnose patients, we don’t use testing as powerful prevention tool. This is why social distancing won’t yield the same results in western countries as we saw in Korea.</p><p>Back to the numbers: From a western country perspective, there are two distinct phases, the first period, ‘growth’, from Feb 7th to early March (picked Mar 6th for simplification), and a second, ‘containment through social distancing’, where awareness &amp; restrictions were considerable higher.</p><p>I didn’t adjust the growth numbers for the second period, however, through raised awareness, people belonging to an ‘endangered’ group are likely to be more cautious. Comparing the death cases in Italy on Mar 20th to what we expected, we see that A) our forecast is actually pretty close to the reported numbers, which in Italy are arguably more reliably as the authorities conducted a large number of tests, and B) a little bit over-estimated, which is why we’ll adjust deaths by 17% downwards to incorporate the benefit of social distancing for all countries.</p><p><strong>What does this all mean</strong></p><p>If your country shows a high number of cases, but only a small number of reported cases, don’t be surprised that once extensive testing starts, cases will skyrocket (e.g. US). The real true numbers of cases is probably somewhere in the middle of this analysis (which is not more than an educated guess) &amp; the reported cases. Secondly, it will be VERY different by country (depending on the counter measures &amp; social habits).</p><p>In my opinion, this analysis is only (somewhat) indicative for western countries: Korea, Japan etc are influenza experienced through the SARS outbreak last decade. Beneficial social habits (e.g. wearing face masks), are much more common. From my personal experience, when I lived in China, my colleagues were wearing masks when they only showed very mild symptoms (that was 5 years ago, independent of any outbreak), while in Germany, even these days, people feel socially awkward wearing basic protection such as mask &amp; gloves and choose not to do it.</p><p>My conclusion is, that building the right social habits (behavior when sick, hygiene) with extensive testing is the sustainable path. Social lockdowns are useful, but only for bearable for a limited time (and less useful without extensive testing).</p><blockquote>Only when you reduce the number of true (!) cases, you can flatten the curve</blockquote><p>Don’t be fooled by reported cases. Let other’s stay safe.</p><p><em>(This article is part of TheIntriguing.com newsletter —</em><a href="https://www.theintriguing.com/"><em> sign up now</em></a><em>)</em></p><p>—</p><p>Sources:</p><p>China international traveler: <a href="https://www.nationalgeographic.com/environment/urban-expeditions/transportation/air-travel-fuel-emissions-environment/">https://www.nationalgeographic.com/environment/urban-expeditions/transportation/air-travel-fuel-emissions-environment/</a></p><p>Population China &amp; Hubei: <a href="https://en.wikipedia.org/wiki/List_of_Chinese_administrative_divisions_by_population">https://en.wikipedia.org/wiki/List_of_Chinese_administrative_divisions_by_population</a></p><p>China altert &amp; lockdown: <a href="https://www.aljazeera.com/news/2020/01/timeline-china-coronavirus-spread-200126061554884.html">https://www.aljazeera.com/news/2020/01/timeline-china-coronavirus-spread-200126061554884.html</a></p><p>Reported case numbers per country: <a href="https://www.worldometers.info/coronavirus/country/">https://www.worldometers.info/coronavirus/country/</a></p><p>Percentage of corona causing symptoms: <a href="https://ourworldindata.org/coronavirus">https://ourworldindata.org/coronavirus</a></p><p>Corona R0: <a href="https://www.livescience.com/coronavirus-myths.html">https://www.livescience.com/coronavirus-myths.html</a></p><p>China Export data: <a href="https://wits.worldbank.org/CountryProfile/en/Country/CHN/Year/2018/TradeFlow/EXPIMP/Partner/by-country">https://wits.worldbank.org/CountryProfile/en/Country/CHN/Year/2018/TradeFlow/EXPIMP/Partner/by-country</a></p><p>Math (e.g. getting from reported death to true cases): <a href="https://medium.com/@tomaspueyo/coronavirus-act-today-or-people-will-die-f4d3d9cd99ca">https://medium.com/@tomaspueyo/coronavirus-act-today-or-people-will-die-f4d3d9cd99ca</a></p><p>Why Korea is a corona role-model, here is the data source (listing test conducted &amp; cases): <a href="http://ncov.mohw.go.kr/en/">http://ncov.mohw.go.kr/en/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f549187dbf2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The new California data privacy law a start or only a drip in the bucket?]]></title>
            <link>https://medium.com/@FBodensteiner/the-new-california-data-privacy-law-a-start-or-only-a-drip-in-the-bucket-9583a5d9e18d?source=rss-46a73946f97d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9583a5d9e18d</guid>
            <dc:creator><![CDATA[Felix Bodensteiner]]></dc:creator>
            <pubDate>Fri, 17 Jan 2020 20:37:19 GMT</pubDate>
            <atom:updated>2020-01-19T18:34:56.748Z</atom:updated>
            <content:encoded><![CDATA[<h3>The new California data privacy law a start or only a drop in the bucket?</h3><p>Arguably more stringent that Europes General Data Protection Regulation (‘GDPR’), the California Consumer Privacy Act (short “CCPA”), went into effect on Jan 1st.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZvgWeq4871xqP2Ek-k5qDw.jpeg" /><figcaption>You know. They know.</figcaption></figure><p>This law grants a consumer certain rights over their data, primarily on request, companies have to disclose which infos are collected, used, shared and/or sold — well usually we want to know all of the above.</p><p>It is a start because it shows that governments realize that thinking about data is important. Effective or not, it raises awareness, which is the first step to enlightenment. One could also make the argument that people don’t care enough about data protection (yet).</p><p>It is en vogue to give away DNA for free (DNA heritage test), receiving shopping recommendations based on our speech profile (Alexa &amp; friends) or volunteering as medical test subject (fitbit / google). Having something is better than nothing. A start.</p><p>On the other hand, some of the provisions, specifically to the sale of data, are a joke. Yes, consumers have now the right if his/her data is sold and yes, they can opt-out that companies can sell their data.</p><p>BUT: Each individual has to send a request to the respective company. Seriously, how many people who doesn’t wear a aluminum hats will do that? Certainly not the majority citizen that needs the protection the most.</p><p>With most data collectors (Facebook / Amazon) being vertically integrated (selling targeted advertising / merch), this doesn’t even count as sale and is therefore excluded from the bill to begin with. A drop in the bucket.</p><p>So how does the perfect data law look like? Exactly, it doesn’t. While some of the proposals (e.g. instead of asking if I want cookies, ask me if they can sell my data, a link for more info &amp; a button for my decision), the enormous compliance cost specifically for smaller companies might outweigh any benefit.</p><p>Meanwhile, It will depend on the engaged citizen, media and whistleblower to play detective &amp; identify black sheep’s.</p><p>—</p><p>Don’t miss the next story, subscribe to the TheIntriguing newsletter: <a href="https://www.theintriguing.com/">https://www.theintriguing.com</a></p><p>Read the law here: <a href="http://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720180AB375">http://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720180AB375</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9583a5d9e18d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>