<?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 Johannes Dancker on Medium]]></title>
        <description><![CDATA[Stories by Johannes Dancker on Medium]]></description>
        <link>https://medium.com/@jobenjada?source=rss-267c245a3a9c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aRj4Aj_F4QoOCRVbI5AnJQ.jpeg</url>
            <title>Stories by Johannes Dancker on Medium</title>
            <link>https://medium.com/@jobenjada?source=rss-267c245a3a9c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:06:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jobenjada/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[(3/3) — I spent 9 months building a B2C app full-time, here are 19 things I learned.]]></title>
            <link>https://jobenjada.medium.com/3-3-i-spent-9-months-building-a-b2c-app-full-time-here-are-19-things-i-learned-c1b592430c2b?source=rss-267c245a3a9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1b592430c2b</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Johannes Dancker]]></dc:creator>
            <pubDate>Tue, 03 Aug 2021 11:18:52 GMT</pubDate>
            <atom:updated>2021-08-03T11:18:52.335Z</atom:updated>
            <content:encoded><![CDATA[<h3>(3/3) — I spent 9 months building a B2C app full-time, here are 19 things I learned.</h3><p><em>I am a first-time entrepreneur from Germany with a semi-technical background building a tech product. Around 5k users gave knugget a squeeze and we are currently at 80 DAUs — slowly but steadily decreasing… So, things don’t go particularly well. This what I learned so far! (Part 3 of 3)</em></p><p><a href="https://jobenjada.medium.com/i-spent-9-months-building-a-b2c-app-full-time-here-are-19-things-i-learned-fde76ce16323">In the 1st part I reflected on learnings I clustered as Entrepreneurial Skills(⚙️)</a> and in the <a href="https://jobenjada.medium.com/part-2-i-spent-9-months-building-a-b2c-app-full-time-here-are-19-things-i-learned-e76e37e75bb9">2nd part I wrote about my learnings as a first-time Product Manager(</a>💻)<a href="https://jobenjada.medium.com/part-2-i-spent-9-months-building-a-b2c-app-full-time-here-are-19-things-i-learned-e76e37e75bb9">.</a></p><p>In this the last part of this little blog post series I am dealing with one of the key skills of entrepreneurship: Decision-Making (🧠).</p><p>It’s part of the job to make many decisions and that naturally comes along with making many wrong decisions. Entrepreneurship is characterized by scarcity: time, money and data are short which makes it difficult to make informed decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*zbVm6ORsWRm_vr10qFuHRA.jpeg" /></figure><p>In a large enterprise, you can afford spending months and tens of thousands of dollars on research to inform a decision. If you try to do the same as a founder you run out of money or your window of opportunity is shut. We have to move fast. But how fast is too fast?</p><h4>🛑🧠 Mistake 1: I wanted to move fast which led to poor decision quality.</h4><p>When it comes to patience, I am pulling from two opposite directions:</p><p>I know that there is no such thing as <em>overnight </em>success and am happy to make baby steps in the right direction. At the same time, as soon as I open Notion, I feel that I am wasting my time when I don’t immediately start working on something.</p><p>The action bias led to me making lots of decisions by gut feeling. I think this is not necessarily a mistake, because often what feels right is the right decision — but having <em>experience </em>in a field is what separates deciding from guessing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ygy1X5q-2MS3ZbGLRXxmvA.jpeg" /></figure><p>Directed speed is <em>earned </em>through years of experience. Before that, getting the direction right is more productive than coming up to the right speed. This, I guess, happens automatically the closer you get to Product-Market-Fit.</p><h4>🟢🧠 Learning 1: Taking time to make the right call beats moving fast by jumping to conclusions.</h4><h4>🛑🧠 Mistake 2: Common-sensing too much.</h4><p>Once the tasks piled up, I reduced the amount of time I spent learning from blog articles and other resources to almost 0.</p><p>In many cases it might have come in useful to take sufficient time to first smarten up, instead of jumping right into the tasks and common-sensing it.</p><p>It can be annoying and confusing to go through lengthy tutorials or numerous methods to achieve X or Y. Going with the common sense is fast and easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*wCv7vaPI0EIRLPsGiGFoug.jpeg" /></figure><p>However, it creates path dependency, especially if others are affected by the decision: It makes it more difficult to switch lanes. On top of that, building the decision-making on a proven process or a best case example can prevent making mistakes others made already. The outcome can be substantially better.</p><h4>🟢🧠️ Learning 2: Schedule time to learn before jumping into something new. Don’t wing it (too often).</h4><h4>🛑🧠 Mistake 3: I did not write my reasoning down to review it later on.</h4><p>Instead of going by gut decisions, every time I face a decision I should take a step back to think. Think and write, to be precise, write down the answers to these questions:</p><ol><li>What is the desired outcome?</li><li>What are my options?</li><li>Is there an “out of the box”-type of option?</li><li>How is the outcome of each option bringing us closer to the overarching goal?</li><li>Why do I believe the desired outcome will happen?</li><li>What happens if it does not?</li><li>How do I feel about the decision right now and why?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*psXxSfUX_8IpbNpVoRwLhQ.jpeg" /></figure><p>I set up a decision-making journal in Notion, a simple table with a few date fields. When I am in the process of making a decision, I write down the answers to these questions and set a reminder date to evaluate this decision 8–12 weeks later, depending on the nature and magnitude of the decision.</p><blockquote>Never judge a decision by it’s outcome. Judge it by the decision-making process. — Rolf Dobelli</blockquote><p>Going through this process makes it easier for me to make decisions, stick with them and explain them to others. In the long run, I hope this will significantly increase the quality of my decisions, as I get the chance to recognize flaws and fallacies in my decision-making process.</p><h4>🟢🧠 Learning 3: Block time to make decisions and maintain a decision-making diary to refer to down the road.</h4><h3>What now?</h3><p>Looking back on this long list of mistakes, I could feel bad about it — it obviously doesn’t feel good to make mistakes.</p><p>With a few weeks of distance, I am actually pretty pumped about these mistakes. Mistakes are the quickest way to learn something new and these learnings are invaluable to me. They will inform all the decisions I will make as an entrepreneur down the line.</p><p>Will I repeat some of the mistakes? Most likely. Is this bad? No, it is part of the process. Contexts change, markets change, people change: What didn’t work in one situation might work marvelously in a different one.</p><p>I am eager to continue working on <a href="https://knugg.et/">knugget</a> and find a way to make it a success. It has been so much fun already and I can only imagine how thrilling it’s got to be if you build something people enjoy using and where you can maintain your livelihood off of.</p><blockquote>I don’t fail because I keep doing things until they work. — Fynn Kliemann</blockquote><p>Having said that, it is not sustainable for me to work full-time on knugget anymore as my governmental funding ran out last month. To pay the billz I will freelance and potentially work on a different project which generates revenue much sooner. I haven’t fully made up my mind yet and want to maintain the freedom to jump on opportunities when they arise.</p><p>So far, being an entrepreneur has been lots of fun! I met so many cool and capable people and learned so much that I can’t wait to see what the next couple of months will bring :)</p><p>Thanks for taking the time to read this!</p><p><em>If any of this resonated and you’d like to get in touch </em><a href="https://twitter.com/jobenjada"><em>you’ll find me on Twitter.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1b592430c2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(2/3) — I spent 9 months building a B2C app full-time, here are 19 things I learned.]]></title>
            <link>https://jobenjada.medium.com/part-2-i-spent-9-months-building-a-b2c-app-full-time-here-are-19-things-i-learned-e76e37e75bb9?source=rss-267c245a3a9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e76e37e75bb9</guid>
            <category><![CDATA[b2c]]></category>
            <category><![CDATA[first-time-founders]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Johannes Dancker]]></dc:creator>
            <pubDate>Thu, 15 Jul 2021 09:38:52 GMT</pubDate>
            <atom:updated>2021-08-03T11:23:37.275Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I am a first-time entrepreneur from Germany with a semi-technical background building a tech product. Around 5k users gave knugget a squeeze and we are currently at 100 DAUs — slowly but steadily decreasing… So, things don’t go particularly well. This what I learned! (Part 2of 3)</em></p><p><a href="https://jobenjada.medium.com/i-spent-9-months-building-a-b2c-app-full-time-here-are-19-things-i-learned-fde76ce16323">In the previous part I shared my mistakes and learnings regarding general Entrepreneurial Skills (</a>⚙️<a href="https://jobenjada.medium.com/i-spent-9-months-building-a-b2c-app-full-time-here-are-19-things-i-learned-fde76ce16323"> ).</a> In this part I now walk you through the fallacies, misconceptions and other hurdles that challenged me during the Product Management (💻) of knugget.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FLFAEMFCBbXI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DLFAEMFCBbXI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FLFAEMFCBbXI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5fc2d323ff848fceb8f144d29f4967ea/href">https://medium.com/media/5fc2d323ff848fceb8f144d29f4967ea/href</a></iframe><p>Before starting to build <a href="https://knugg.et/">knugget</a> I didn’t know what the job of a Product Manager (PM) looks like — now I have the utmost respect for it!</p><p>Not only does a PM need to be proficient in a wide range of different skills and knowledgeable in many more fields, their product decisions can lastingly impact the future outcome of the overall business. Phew…</p><p>It was the first time for me to manage a tech product so to the seasoned PMs reading this: There’s probably not much in it for you 👋</p><p><strong>For everyone new to the game: </strong>These are the key things I learned and I hope you can get an insight or two out of reading this.</p><p>Let’s get to it! 🤸</p><h4>🛑 💻 <strong>Mistake 1: I thought tests are meant to prove my solution RIGHT.</strong></h4><p>This might come across as hair-splitting but to me, it is one of the most important learnings of the past months. Had I deeply understood this earlier, I might have postponed writing code a few more weeks to first get a clear understanding of whether what I want to build actually works.</p><p>I thought, foolishly, that tests are meant to prove if an idea can fly.</p><p>They are not. The intention is to find out why an idea would <strong>not </strong>fly. This is a significant difference because it changes the expectations of what a test is supposed to do and how to approach testing in general.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ljbh6UmwJ2mRkpfOcZi5cg.jpeg" /></figure><p>To build a growing, sustainable business <strong>a lot</strong> of things must fall into place. Hence, if you want to know if the business as a whole works, you have to build it out as this is the only way to eradicate all doubt.</p><p>In other words: there are numerous reasons for why a business can fail. Looking at it from this side has a significant advantge: To find out what makes it fail, you don’t have to build the whole thing. You isolate the reasons why it would fail and test them individually.</p><p>To do that, you are free to run a test that is very far away from the solution you envision, as long as the results prove one of your underlying hypotheses right or wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*r9fBLi-zfXrSn8tbRC4LvA.jpeg" /><figcaption>Me at the beginning of building knugget.</figcaption></figure><p>In my case I thought that I have to build it to really know, if knugget will work or not. “Tests”, I thought, “only provide weak data that might serve as an indicator but will not reliably tell me if knugget will work.”</p><p>What I should have thought about are the reasons why knugget would <strong>not</strong> work, rank them based on their <em>fuck-the-whole-thing-up-potential</em> and work my way down from the top.</p><p>Yes, this is less fun than coding. Yes, this does not feel like progress. Yes, this can be discouraging at times. But it builds a solid foundation to build a solid business upon.</p><h4>🟢️💻 <strong>Learning 1: Tests help me find out why my solution might FAIL.</strong></h4><h4>🛑 💻 Mistake 2: I took false positives from users for real</h4><p>At the beginning of this year, I made a LinkedIn video and people loved the idea behind knugget. 250 people commented that they want to test the MVP so I was pretty pumped. In the first week, we got 140 users signed up. Is it really that easy?</p><p>No (:</p><p>After the retention of the first MVP was pretty bad, I asked the users why. Most of them were very positive and “loved the idea” and “would use it if it only were an app”. Easy peasy I thought, you got to listen to your users and build what they want — an app we can build!</p><p>So we did. It didn’t solve our retention problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*igqh2rJnesK2EekQJ0haPg.jpeg" /></figure><p>People are polite or (un)consciously portrait an image of themselves that not always aligns with their behaviour. Only a few OGs told me knugget doesn’t work for them ❤ It’s important to keep them around as long as possible (which isn’t so easy if your product comes short of fulfilling its value proposition).</p><h4>🟢️💻 Learning 2: Only listen to past experiences of a user. Every statement about the future is overly optimistic and meant to make me feel good.</h4><h4>🛑 💻 Mistake 3: I overestimated the importance of good UX at an early stage</h4><p>Our users wanted an app for two reasons: To not have to have their laptop close by when they read and to get push notifications on their phones to reread their knuggets.</p><p>I believed them, I made the same experience.</p><p>But I should have been more skeptical. If knugget would have solved a burning problem, they would’ve gone through the pain of typing up their knuggets on their laptop.</p><p>In other words: The channel or platform (email/web vs. app) is rarely the reason why people don’t use an MVP. There is a different problem which the users are not aware of or which they don’t want to openly communicate.</p><p>In this case: Most people don’t like to stop reading to write up a knugget — this is quite an effort as you have to condense it down while typing it out. Switching to an app did not make this much easier, going from 10-finger-typing to two thumbs.</p><p>Lastly, if you offer so much value that people go through a lot of friction to use your product, chances are much higher that they are willing to pay for it down the line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*yNC-eIROYOyI-sECtqdy2g.jpeg" /></figure><h4>🟢️💻 Learning 3: A crappy UX can be my friend: It filters out users with a passing annoyance which helps to find users with a real problem. And it can help strengthening the proof of concept.</h4><h4>🛑 💻 Mistake 4: We launched two tech products with little to no analytics.</h4><p>For the webapp we had very basic analytics running and for the native app we added granular analytics a couple of weeks down the line.</p><p>We were aware of the importance of analytics but wanted to launch fast, so we prioritized it down. It would have made more sense to take one week to learn how to do it properly and set it up before the launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*d2seDNaXU5B6EoUbrQTCvg.jpeg" /></figure><h4>🟢️💻 Learning 4: Always launch with full-fledged analytics set up.</h4><h4>🛑 💻 Mistake 5: I looked for data that supported my hunch.</h4><p>When making product decisions, I almost always ended up going with my initial hunch. I knew I need data to base my product decision on and went through different chats and charts to pick the sentences and KPIs that supported the hunch.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FKChOCrUh2lYxW%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FKChOCrUh2lYxW%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FKChOCrUh2lYxW%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/2686a57242af2927b23435cfd0e92a6f/href">https://medium.com/media/2686a57242af2927b23435cfd0e92a6f/href</a></iframe><p>What I should’ve done is look for data that disproves my believe. Chances are much higher that I am wrong anyways and knowing that early on is super valuable. And if I cannot find much data that proves me wrong, my assumption ends up being much stronger.</p><h4>🟢️💻 Learning 5: Don’t fall for the confirmation bias: Look for data that disproves the assumption first.</h4><h4>🛑 💻 Mistake 6: I didn’t talk to enough users in a structured way early on.</h4><p>This is a short one: I had loads of chats with loads of people who liked knugget.</p><p>And I asked a few friends who read a lot how they go about managing their insights and challenges when it comes to knowledge retention.</p><p>I did not do a proper Mom Test before starting to build🙄</p><h4>🟢️💻 Learning 6: Talk to more users in a structured way.</h4><h4>🛑 💻 Mistake 7: I didn’t organize my user insights.</h4><p>I did not catalog the insights I got from users in a digestible and accesible way. I collected insights in different Notion pages and tables and aggregated them to make product decisions, but there was no real methodology or framework to it. Most critically, building an app for knowledge retention, I should have known that I will sooner or later forget what people told me which will weaken the quality of my decisions down the line.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FmGc0ns31KuHm5Nwg3r%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FmGc0ns31KuHm5Nwg3r%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FmGc0ns31KuHm5Nwg3r%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/a3ac949e0ed5b76b06432a8d8fc00c94/href">https://medium.com/media/a3ac949e0ed5b76b06432a8d8fc00c94/href</a></iframe><p>To get the most insight out of it (and value the time the interviewees generously offered) I have to be more disciplined in managing the insights better.</p><h4>🟢️💻 Learning 7: Organize user insights properly and make them easily accessible to go back to at a later iteration.</h4><h3>How about “Fail fast, reflect often” ?</h3><p>I have built a little tool to help myself do these reflections regularly. It blocks my browser on Sundays until I wrote at least a few hundred words of reflection.</p><p>I played around to find the best set of questions and triggers for deep reflection of what happend in the last week, what could’ve gone better, etc.</p><p>And, most importantly, I want to have a seamless experience when doing meta-reflections. It was already super annoying jumping back and forth between four docs, trying to find the overarching themes and patterns.</p><p>I don’t want this shitty UX to stop me from getting the most out of quarterly and bi-yearly meta-reflections, so I started to design a seamless way to facilitate the monthly, quarterly and bi-yearly meta-reflections.</p><p><strong>Wanna test it?</strong></p><p><a href="https://calendso.typeform.com/to/JfbnshMQ"><strong>Please leave your mail (and answer a few questions) here so I can reach out</strong></a><strong> :)</strong></p><p>In the upcoming last part I will share with you a few insights regarding decision-making.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e76e37e75bb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(1/3) — I spent 9 months building a B2C app full-time, here are 19 things I learned.]]></title>
            <link>https://jobenjada.medium.com/i-spent-9-months-building-a-b2c-app-full-time-here-are-19-things-i-learned-fde76ce16323?source=rss-267c245a3a9c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fde76ce16323</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[b2c]]></category>
            <category><![CDATA[tech-product]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <dc:creator><![CDATA[Johannes Dancker]]></dc:creator>
            <pubDate>Thu, 08 Jul 2021 09:39:31 GMT</pubDate>
            <atom:updated>2021-07-15T09:42:16.774Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I am a first-time entrepreneur from Germany with a semi-technical background building a tech product. Around 5k users gave knugget a squeeze and we are currently at 130 DAUs — slowly but steadily decreasing… So, things don’t go particularly well. Here is what I learned (Part 1 of 3).</em></p><p>What’s knugget? knugget (“nugget”) is a network to discover knowledge nuggets with a built-in spaced repetition feature. We aim to enable people to retain their key insights so they can apply them in their lives. It’s the first time I build a tech-product and I made allllll the mistakes: I’ll share with you the 19 things I learned so far — in three parts, so bear with me.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1fzKSz9aRJg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1fzKSz9aRJg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1fzKSz9aRJg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b9a3d326f399cd5698a24b2fdc0f02e/href">https://medium.com/media/8b9a3d326f399cd5698a24b2fdc0f02e/href</a></iframe><p>While sharing my learnings, I will provide some context. I hope this increases the likelihood of others finding themselves in the description. I find advice within context more valuable because it reduces the room for misinterpretation.</p><p>More importantly, when I read (and ignored) generalized advice, I used to think: “Well yes, that makes sense, but it doesn’t apply to me in this situation because <em>BLA-overconfidence meets lack of experience-BLA</em>”. Now I know that the likelihood that my hunch is wrong is significantly higher than that the person sharing learnings from a real experience is wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*F7QUK0EMlBiZNHYY7-6Wsw.jpeg" /><figcaption>I be like</figcaption></figure><p>I hope to prevent some of you from making this meta-mistake by expanding on the context. So let’s do this!</p><p>The learnings broadly fall in three categories: Entrepreneurial Skills (⚙️), Product Management (💻), and Decision-Making (🧠). In this first part I’ll share my learnings regarding product-agnostic Entrepreneurial Skills(⚙️).</p><h4>🛑⚙️ Mistake 1: I started building right away</h4><p>Many of the following mistakes are rooted in impatience: I wanted to start building as soon as possible. So I did — big mistake!</p><p>I recently heard this quote in a podcast, which sums it up perfectly:</p><blockquote>If you don’t have the time to do solid research at the beginning, I sure hope you have time to change everything later on.</blockquote><h4>🟢⚙️ Learning 1: Be patient. The time you invest in solid research, thinking and planning pays back manifold down the line.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*U-u625cXchrN1idzQPK3lQ.jpeg" /></figure><h4>🛑⚙️<strong> Mistake 2: I built for “people who forget things”</strong></h4><p>I did not understand the importance of market segmentation. Theoretically, I got it: developing a customer persona, finding a small group of people who have a pressing problem etc. but in my day-to-day work that wasn’t reflected. I did not put together a detailed customer profile and therefore failed to strictly search or filter for people who match that profile. I invited everyone to test knugget and give feedback — the more the merrier.</p><p>I had a broad idea to build knugget for people who are interested in Self-Development and bother that they forget so much from the books they read. This is way, way, way too broad and undifferentiated to gather deep, precise user insight, identify a pressing problem and build a compelling solution for that.</p><p>The not-so-targeted targeting led to the perfect confusion: I ended up with lots of contradictory feedback which made it really difficult to make informed product decisions.</p><p>More importantly, it <strong>set the whole endeavour up for failure</strong>, as we will see soon.</p><h4>🟢⚙️ Learning 2: It’s really important to know exactly who I build for. The profile should be ridiculously specific at first and adjust as I gather more information.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*jkbgxPQcaEhXaQFDUQZRcg.jpeg" /></figure><h4>🛑⚙️ Mistake 3: I didn’t deeply explore the problem nor defined the problem context precisely.</h4><p>The initial problem description was something like this: “We forget insights from non-fiction books before we can apply them. This makes reading ineffective and inefficient.”</p><p>My reasoning was simple: If you want to apply an insight, you have to retain it. Many studies prove that spaced repetition is one of the best ways to increase knowledge retention — let’s apply it to insights from books!</p><p>This <strong>oversimplification led to an unspecific value proposition which led to a product which doesnt solve anyone’s problem. </strong>But I’m jumping ahead.</p><p>What I should have done is narrowing down the problem <strong>and </strong>problem context significantly, looking like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bp0fSCiR1OTTvp5goBd6vA.png" /></figure><p>Segmenting the market beforehand is a great starting point. A few simple questions to start with are:</p><ul><li>Who has this problem?<em> (your segment)</em></li><li>When does it occur?</li><li>Where does it occur?</li><li>How does it effect the person?</li><li>How does it make them feel?</li></ul><p>With the context at hand, I could go deeper on the problem. Asking “Why?” several times and exploring each of the layers with surrounding questions can lead to many new insights and entry points for further research.</p><p>Organizing them in a problem tree can help:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SNgXSDAMpz38jvZ98w_AUw.jpeg" /><figcaption>Used miro.com to make it — it’s free!</figcaption></figure><p><em>The process of finding the right segment to build a solution for while defining the problem context is iterative. During the research, more and more insights clear up the understanding of who has which problem.</em></p><h4>🟢⚙️Lesson 3: Examine the problem and problem context. Keep refining the segment I want to solve this problem for.</h4><h4>🛑⚙️ Mistake 4: Running with an unspecific value proposition.</h4><p>I couldn’t formulate a precise and specific value proposition because I had the impression that I would leave things out — this is a red flag 🚩</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NLm2zdjK26iCT-_8-m6y0w.png" /></figure><p>“keep things in mind” is the not a very precise value proposition, to put it mildly.</p><p>This vague value prop left people testing out knugget confused <strong>and</strong> made it very difficult to streamline the product itself. There are many different use cases knugget caters to broadly but not a single one knugget caters to precisely.</p><p>Had we built a specific solution for a pressing problem of a small group of people, we could’ve iterated closer to a compelling solution instead of shipping somewhat random features a small subset of our current users requested. A solid product-solution fit would’ve increased the chances significantly of acquiring paying customers.</p><h4>🟢⚙️Lesson 4: If I can’t put my value proposition in a few words, check my segmentation and problem research.</h4><h4>🛑⚙️ Mistake 5: I didn’t geek out on what’s already there.</h4><p>Once you know exactly who you want to solve which problem for, it’s time to explore the <strong>solution space</strong> or do what I call “concept research”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*N3-EIKsLkfqZzbN_Zeju_w.jpeg" /></figure><p>I conducted just a broad concept “research”. I spent a few hours googling, signed up for a few similar tools and played around with them for a bit before I thought: “This is too far away from what I envision. Don’t waste your time.”</p><p>I did not become a power user to experience the value these tools really provide (vs. what they promise) and to understand their weaknesses. Doing so would’ve provided deep insights into the challenges current users have and how these tools address them. I could’ve tried to reverse engineer the user insights the team behind the tool might have and how they responded to them.</p><p>Furthermore, I should’ve seeked advice from experts in the field. It took <a href="https://twitter.com/andy_matuschak">Andy Matuschak</a> three messages on Twitter (thanks for replying🙏) to question the underlying hypothesis knugget was built on: Resurfacing insights helps us retain them better. It doesn’t.</p><p><em>Back then I had never used Twitter and didn’t know how responsive many people are. But I’d probably had thought that “it’s different in my case” anyways — remarkable how humbling failing is.</em></p><h4>🟢⚙️Lesson 5: Take at least a full day per main competitor to dive deep into the tool, use it to its full potential, read comments from users, stalk founders on Twitter, in Podcasts etc. Collect all of it in a comprehensive matrix to deeply understand the niche and where I can position my product. Oh, and ASK PEOPLE WHO KNOW STUFF — most are happy to help.</h4><h4>🛑⚙️ Mistake 6: Being a Digital Nomad made it difficult for me to stay emotionally engaged.</h4><p>I spent the past months here and there, working on the go. It’s really hard to feel bad about the progress you are making with your startup, when you hike up a volcano or lay at the beach with a Mojito and friends.</p><h3>Suhail on Twitter: &quot;19/ I was ruthless about ensuring I had as much deep work time as possible. Live somewhere boring. Eliminate meetings. Don&#39;t meet investors if you&#39;re not raising. Build a rhythm each day that enables the largest chunk of hours to get great work done. Users will notice your pace. / Twitter&quot;</h3><p>19/ I was ruthless about ensuring I had as much deep work time as possible. Live somewhere boring. Eliminate meetings. Don&#39;t meet investors if you&#39;re not raising. Build a rhythm each day that enables the largest chunk of hours to get great work done. Users will notice your pace.</p><p>Initially, I thought this is the perfect combination: Work your ass of during the week and explore the world on the weekends. I know that this works if someone else tells you what to do or you know exactly what you are doing. Being new to the game I think it is essential to stay tuned in to your startup, to keep thinking about how things go on the weekends and in the evenings and what you can do about it to make it work better.</p><p>Being out exploring over the weekends, I struggled to stay tuned in with knugget. On Mondays I found myself with a lot of motivation and self-induced pressure to GET SHIT DONE but I was lacking the reflection over the weekend to keep adjusting the direction we were running towards. A friend told me in March that direction beats speed and having run somewhere without really knowing where, I now get what he meant.</p><h4>🟢⚙️Lesson 6: Stay at one place to have routines free up your cognitive capacity for your startup (at least until it is clear, what you are building and how you get there).</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT9Igrp5DiYwi1KQIE%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fshameless-season-1-episode-2-xT9Igrp5DiYwi1KQIE&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2FxT9Igrp5DiYwi1KQIE%2Fgiphy.gif%3Fcid%3D790b7611637dda4488268f708b04d3bdca249e569bc69451%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/97c887c1438cdf118171ab7a628fa8d9/href">https://medium.com/media/97c887c1438cdf118171ab7a628fa8d9/href</a></iframe><h4>🛑⚙️ Mistake 7: Schedueling MUST DO tasks on weekends.</h4><p>I scheduled a few tasks on the weekend, which were MUST DOs — and did some of them half-assed or not at all. Being my own boss, nothing really happened but it harmed the development of knugget in the long run and, if other people were involved, weakened my credibility.</p><p>Building a company is a marathon and for me it is important to prevent that it doesn’t fill up my life completely. During the winter days and with COVID, I worked through weekends a few times and could feel how much less productive and motivated I was in the following week.</p><p>For me it’s crucial to get at least one day free of any appointments to sleep in and do whatever I feel like doing. Sorry, no #hustleporn today.</p><h4>🟢⚙️Lesson 7: Do what I gotta do on week days and keep the weekends free to do things I enjoy. Meet friends, run, learn something startup related, read, do a do-my-shit-day, work on other projects, get bored: Recharge.</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FC4Dn7okAW1nUSKzVTA%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FC4Dn7okAW1nUSKzVTA%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FC4Dn7okAW1nUSKzVTA%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="334" frameborder="0" scrolling="no"><a href="https://medium.com/media/878f1268ca099c23f77b832dcda13f49/href">https://medium.com/media/878f1268ca099c23f77b832dcda13f49/href</a></iframe><h4>🛑⚙️ Mistake 8: I didn’t regularly reflect on what I did.</h4><p>It’s the last one for today but certainly one of the biggest mistakes I made. I started doing weekly reflections for a month at the beginning, but didnt make it a lasting habit.</p><p>The positive effect of reflections are twofold: The process of writing down what lingers around my brain clears my mind to make better decisions. But I only get half the value out of it, if I don’t take the time to do a meta-reflection regularly.</p><p>You’d be surprised how much of what you wrote down slipped your mind again, falling back into old thinking patterns. Only when you take the time to read through all of it and extract patterns and trends, you reap all the fruit and progress faster.</p><h4>🟢⚙️Lesson 8: Do weekly, monthly and quarterly check-ins. Meta-reflect to lastingly learn from my own experience.</h4><h3>How about “Fail fast, reflect often” ?</h3><p>I have built a little tool to help myself do these reflections regularly. It blocks my browser on Sundays until I wrote at least a few hundred words of reflection.</p><p>I played around to find the best set of questions and triggers for deep reflection of what happend in the last week, what could’ve gone better, etc.</p><p>And, most importantly, I want to have a seamless experience when doing meta-reflections. It was already super annoying jumping back and forth between four docs, trying to find the overarching themes and patterns.</p><p>I don’t want this shitty UX to stop me from getting the most out of quarterly and bi-yearly meta-reflections, so I started to design a seamless way to facilitate the monthly, quarterly and bi-yearly meta-reflections.</p><p><em>I think there is great potential to have GPT-3 assist us during the tedious work of reviewing and extracting patterns in meta-reflections — would love to talk to anyone who has played around with GPT-3!</em></p><p><strong>Wanna test it? </strong><a href="https://calendso.typeform.com/to/JfbnshMQ"><strong>Please leave your mail here so I can reach out</strong></a><strong> :)</strong></p><p>In the upcoming part I will share with you all the mistakes I made as a first-time Product Manager — oh boi this is gonna be fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fde76ce16323" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>