<?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 James Van Dyne on Medium]]></title>
        <description><![CDATA[Stories by James Van Dyne on Medium]]></description>
        <link>https://medium.com/@jamesvandyne?source=rss-135a503f1bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rlVUjEowf-_Kpiq5.jpeg</url>
            <title>Stories by James Van Dyne on Medium</title>
            <link>https://medium.com/@jamesvandyne?source=rss-135a503f1bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:54:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jamesvandyne/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[Features are Icebergs]]></title>
            <link>https://medium.com/building-kwoosh/features-are-icebergs-4192d73cbdce?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4192d73cbdce</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Fri, 21 Apr 2017 22:31:31 GMT</pubDate>
            <atom:updated>2017-04-21T22:31:31.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*uh-1CsZWjKaxv8Q-." /></figure><p>For my first ever job writing software professionally, I was hired to write a system to manage the day-to-day operations of the business. It would be responsible to control key aspects of the business and replace the current hodgepodge of spreadsheets, forms, databases and apps they used. One unified system to rule them all.</p><p>After building and launching there were a number of feature requests that would come down from above and often these new features would conflict with existing functionality or branch business logic and completely alter a workflow.</p><p>Being naive, at first I’d just try my best to implement the feature and fit in the work new screens or workflows at the same time. As these piled up, development slowed. And as it slowed my boss seemed to start becoming frustrated.</p><p>When I explained why the level of effort involved in a request he’d often respond with “Just add a checkbox”. Wanting to make my boss happy I’d go with his suggestion. But as we added more checkboxes for more edge cases the software became a lot more difficult to understand and use.</p><p>These checkboxes were Icebergs. On the surface at the top all you see is a checkbox. Underneath, hidden from view is an entire pile of logic, tests, and services setup to support this little checkbox, just poking above the water.</p><p>A single iceberg is easy to navigate around and understand. It’s off in the distance, you turn extra wide around it and you’re likely to not even notice it there.</p><p>Navigating through a sea filled with icebergs is difficult and dangerous. Too far to the north and you could hit that seemingly unrelated iceberg. And as they move around in the ocean they can easily hit off one another — making the known safe route potentially hazardous.</p><p>The next time you’re adding a feature to your software ask yourself are you adding an iceberg or are you adding to the glacier, safe on land?</p><p><em>We are building </em><a href="https://kwoosh.com/"><em>Kwoosh</em></a><em> to help us manage our software projects and map our glaciers and icebergs. </em><a href="https://medium.com/building-kwoosh"><em>Follow along with our process of building a SaaS app</em></a><em> and send us any questions you might have </em><a href="https://twitter.com/kwoosh"><em>@kwoosh</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4192d73cbdce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kwoosh/features-are-icebergs-4192d73cbdce">Features are Icebergs</a> was originally published in <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Build Products?]]></title>
            <link>https://medium.com/product-people/why-build-products-3a18dd41b4fc?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a18dd41b4fc</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[makers]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Fri, 23 Dec 2016 19:58:01 GMT</pubDate>
            <atom:updated>2016-12-23T20:27:38.421Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3hGtC-jmerxfWYz51AsvvQ.jpeg" /></figure><p>Given the choice to work more after a long day or watch the latest episode of Game of Thrones, most will pick the later. Some, however, do not. They instead choose to build. They write, they edit, they draw, they code, they imagine. Why?</p><p>Inside most Product People there’s this need to create. A desire to hone our craft. To make something from seemingly nothing. Profit is always a nice goal, but timelines aren’t strict.</p><p>Doing things right is more important than deadlines.</p><p>Others come to product from a pure profit mindset. They can still be successful product makers, but the road will be less fulfilling.</p><p>Part of sculpting your products is how your products sculpt the maker. How have you changed? What have you learned?</p><p>With Kwoosh we’re pouring everything we’ve learned about software into it. Over 30 collective years of tinkering, making and testing things out. And while profit is a destination on our road map, it’s not <em>the</em> destination.</p><p>First and foremost our goal is the build a useful product that helps us and our customers make better software. Once we can do that, we are confident we can find profit.</p><p>In the end, profit may mean we only made $2–3 an hour when bootstrapping, but we march forward. We dream. We build. We create. We are Product People</p><p><em>Our goal is to help customers build better software products and want to help you start the year off strong. Tell us what you’re building </em><a href="https://twitter.com/kwoosh"><em>@Kwoosh</em></a><em> and follow along as we’re </em><a href="https://medium.com/building-kwoosh"><em>building Kwoosh</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a18dd41b4fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-people/why-build-products-3a18dd41b4fc">Why Build Products?</a> was originally published in <a href="https://medium.com/product-people">Product People</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Behind the Scenes]]></title>
            <link>https://medium.com/building-kwoosh/behind-the-scenes-24cb28847cc4?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/24cb28847cc4</guid>
            <category><![CDATA[makers]]></category>
            <category><![CDATA[handmade]]></category>
            <category><![CDATA[behind-the-scenes]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Thu, 17 Nov 2016 23:06:15 GMT</pubDate>
            <atom:updated>2016-11-17T23:15:48.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*W6vraQquSM6ASjsuzE2_Gw.jpeg" /><figcaption>Photo from <a href="http://www.fuse.tv/galleries/2013/09/nirvana-throwback-thursday-photos#10">fuse.tv</a></figcaption></figure><p>When I bought my first album the anticipation was almost unbearable. I heard this song on the radio in the car going to school one day. From the first time the bridge played I was hooked and had a new favorite song. I had no idea who it was, we didn’t have Shazam back then, so I made my Mom listen to the same station whenever we were in the car, hoping that they would play it again.</p><p>After what seemed like weeks, but was probably only a few days, the song came back on just as we were pulling into the driveway. After some begging and pleading, my mom let me stay in the car to listen to it all and find out who it was.</p><p>Three minutes later I knew the name of my new favorite song, who the band were and the fact they they also had a brand new album out that month.</p><p>The special pleading started as soon as I threw my bag at the bottom of the stairs. I had to have this CD. After a few days of talking about nothing else my Mom caved and said she would take me to the mall at the weekend and we would get it.</p><p>I was almost skipping as I came out of store with my new precious object. I opened it as quickly as I could, tugging and scratching at the impenetrable cellophane coat that would be the bane of humanity until MP3s became popular years later.</p><p>We didn’t have a CD player in the car, so I had to sit and wait until we got home to put it in my boombox. With nothing else to do I started to look at the album art and track list. I open the jewel case and immediately attempted to spin the matching colored CD in place. By total chance I then noticed that the front insert wasn’t just a single sheet of paper, but was a little booklet.</p><p>I spent the rest of the ride home glued to its content.</p><p>Thumbing through it I wondered what the band were thinking when they decided on this artwork. Why this image for that song? Were they playing this song when this photo was taken? So that’s what a recording studio looked like. Oops, I had been singing the wrong lyrics to my favorite song.</p><p>Seeing these photos gave me a glimpse into the life of these artists. These are the people who <em>made</em> this, I thought. They’re so cool and talented. I wondered what the rest of the studio was like, and daydreamed about being in there someday with them.</p><p>Showing the behinds the scenes of how the album was made, forged a bond between me and the band. It made them become more than just a voice on the radio. They were no longer just Nirvana. They were Kurt, Krist, and Dave. I knew them now. I was a true fan.</p><p>As makers of digital products we need to remember that there are real people behind each purchase. They are human, not a transaction number, and as humans they crave stories to give meaning to things.</p><p>Sharing the story behind how your product is made shows the human aspect of a largely inhuman industry. Where one byte is the same as another, we have to bring more to the table that just the end product..and that’s the story.</p><p>There is no holding, feeling, or smelling a digital product. You cannot see where the maker made their mark. So instead we need to tell the story of how our bytes got to be the way they are. We have to offer a glimpse into the workshop to show how the product was crafted and by whom. We have to humanize our products so that they are elevated from being a mass produced item to a handcrafted masterpiece.</p><blockquote><em>Don’t just sell a disc of plastic, sell the story behind how the music was made.</em></blockquote><p><em>Whilst we build </em><a href="https://kwoosh.com/"><em>Kwoosh</em></a><em>, a software project management tool, we are showing off a lot of the behind the scenes stuff in our </em><a href="https://medium.com/building-kwoosh/tagged/kwoosh"><em>monthly reviews</em></a><em>. We also post updates and glimpses into all our work on </em><a href="https://twitter.com/kwoosh"><em>twitter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24cb28847cc4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kwoosh/behind-the-scenes-24cb28847cc4">Behind the Scenes</a> was originally published in <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You don’t need more knowledge]]></title>
            <link>https://medium.com/@jamesvandyne/you-dont-need-more-knowledge-83c5247e8f60?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/83c5247e8f60</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[procrastination]]></category>
            <category><![CDATA[gtd]]></category>
            <category><![CDATA[makers]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Thu, 10 Nov 2016 12:59:20 GMT</pubDate>
            <atom:updated>2016-11-10T12:59:20.350Z</atom:updated>
            <content:encoded><![CDATA[<h4>Read these 5 books. Take this online course. Subscribe to those newsletters. Watch these videos. Sign Up for this webinar.</h4><p>Everywhere you look people are trying to throw knowledge at you as the silver bullet to solve all your problems. They tell you that you can’t succeed without their five step process for only three easy payments of $29.95. They tell you that the reason you didn’t succeeded before was that you didn’t know their methods; you need to build an audience, pick a niche, hire a designer, make a viral video, code it in ruby, create landing pages, create a hashtag. All of which you can learn from them.</p><p>The thing is: you don’t need more knowledge. You already know enough to start today.</p><p>Before starting we think we must be able to answer every issue that could possible occur, lest someone on the <em>Internet</em> think we’re stupid.</p><p>We watch inspirational videos. We drive to that coffee shop that plays just the right music. We research tools to to handle customer support before we have any customers. Anything that tricks us into feeling progress without actually making any progress.</p><p>You don’t need to read another book, you don’t need to take a course, you don’t need to watch more videos…you just need to start and work hard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ddaR1xfF4mnMqsht." /></figure><blockquote>The thing standing between you and your goal isn’t knowledge, it’s work</blockquote><p><em>When we work on </em><a href="https://kwoosh.com/"><em>Kwoosh</em></a><em> we break everything down into tasks. We then break those tasks into multiple sub-tasks and those into sub-tasks etc. This leaves us with bite-sized chunks of work that are never too big to overwhelm us. We are removing all obstacles between our minds and getting the task done…</em><a href="https://kwoosh.com/"><em>we invite you to join us too</em></a><em>.</em></p><p><em>What do you think is stopping you from reaching your goals? Tell us</em><a href="https://twitter.com/kwoosh"><em> @kwoosh</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83c5247e8f60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starters and Finishers]]></title>
            <link>https://medium.com/building-kwoosh/starters-and-finishers-724bc7f67ecc?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/724bc7f67ecc</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 13:01:01 GMT</pubDate>
            <atom:updated>2016-10-26T14:57:21.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TGzuypE-GfQo02Gu4XuOhg.jpeg" /><figcaption>Photo by <a href="https://www.flickr.com/photos/pmillera4/16591695840/in/photolist-rh9M8o-HyMGBr-scxSov-oiT1ok-6nrAn7-oEYonE-ojcKDG-oXhMHo-4Dhy53-2zdRwV-4sdurN-5jrR7w-byyskC-nmEkHu-nJDD9g-6zGSbp-rGBPJR-bLFueR-byysP9-ccfVgU-ejR1eu-stzYig-M2rKM-Gvev4-GvcPu-ppt2wh-2PHWVu-NZ6X6-88bD7N-3ctepC-2zeaDn-on1FuN-Hcyde-3fnLSw-Gvev2-JEr7i-KQNpf-23Qd9V-GTCPU-2ze1QK-GvcXF-3gARDr-33s5i9-3ctehw-Hcydn-82UVPz-GvagT-LRWM6-33s5uq-2zeaD8">Peter Miller</a></figcaption></figure><h4>Writing has always been a challenge for me. I can sketch out essays and ideas, but honing it is always a struggle. With practice I’ve gotten better, but it’s still difficult.</h4><p>Throwing a ball 90+ miles per hour takes a lot out of you. That’s why it’s rare to see a pitcher pitch an entire game of baseball. The stamina required and risk of injury just isn’t worth it.</p><p>Some pitchers can throw “slow” fastballs for a long period of time. Others can throw “super-fast” fastballs for a short period of time. Alone, neither could finish a complete game. Instead they work together as a team.</p><p>The first pitcher will get you through most of the game, then around the 7th inning a “finisher” is brought in to close out the game.</p><p>Jacob, my co-Founder with <a href="https://kwoosh.com/">Kwoosh</a>, doesn’t publish much here on Building Kwoosh. It’s not that he can’t write. He just has trouble starting.</p><p>Getting the raw ideas out of his head into a first draft is a struggle. He starts and stops too much, focussing on the perfect sentence or word choice instead of a general outline.</p><p>What he’s great at is finishing.</p><p>He can take an outline that I’ve scrawled out at Starbucks over a flat white, reword some sentences, add in some sports metaphors, praise himself lavishly, and turn it into a finished essay.</p><p>He’s a finisher.</p><p>Last week I had an idea for a post, <a href="https://medium.com/building-kwoosh/ask-100-makers-what-they-want-to-do-more-of-and-the-answer-is-always-to-ship-more-work-25c8507dbbd3">Fear vs Shipping</a>. Left to my own devices it would have taken a week or more to get it written, and even then, it would have needed more work. Instead of struggling through it, I brought in my finisher.</p><p>I shared my draft with Jacob, and in an hour we had a published essay. Neither one of us could have posted the essay on our own, but as a team we could.</p><p>Identifying our roles has vastly improved our work. It means that my thoughts get written clearer and published sooner. And that I can lay the foundations for Jacob’s, before he comes back to construct them fully.</p><p>By focusing on our strengths we get more done.</p><p>I feel that a lot of makers fall into the same two categories of “starters” and “finishers”.</p><p>There are countless stories of people starting project after project and never finishing. Almost as many as the number who have great ideas, but procrastinate, and never get started.</p><p>If you can identify which category you fall into. You can either push through the part you know you struggle with. Knowing that it’s not your strong suit, and you just have to be determined to get through it. Or you can join forces with somebody to compliment your strengths and finish more perfect games (or projects).</p><p><em>We’re building our </em><a href="https://kwoosh.com/"><em>software project management tool Kwoosh</em></a><em> in the same way. I throw together the basic elements, and Jacob refines and adds the polish. You can read more about what we’re doing in our publication, </em><a href="https://medium.com/building-kwoosh"><em>Building Kwoosh</em></a><em>.</em></p><p><em>We’d both love to hear if you’re a starter or a finisher, so tweet us </em><a href="https://twitter.com/kwoosh"><em>@kwoosh</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=724bc7f67ecc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kwoosh/starters-and-finishers-724bc7f67ecc">Starters and Finishers</a> was originally published in <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fear vs Shipping]]></title>
            <link>https://medium.com/building-kwoosh/ask-100-makers-what-they-want-to-do-more-of-and-the-answer-is-always-to-ship-more-work-25c8507dbbd3?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/25c8507dbbd3</guid>
            <category><![CDATA[shipping]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[makers]]></category>
            <category><![CDATA[fear]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Tue, 18 Oct 2016 22:19:32 GMT</pubDate>
            <atom:updated>2016-10-26T14:55:54.559Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/657/0*o57Td5Oh7Zukk_1Q." /></figure><h4>Ask 100 makers what they want to do more of and the answer is always to ship more work. Ask them why they don’t, and the common response is fear.</h4><p>It’s a common issue that all makers face. You face it when you release a new product or upload a new video. I’m facing it now with this essay. We all get scared when it comes to submitting our work to the public.</p><p>We fear we have nothing to say, that it has already been said by others and that everybody already knows and understands it. We’re scared of judgement from strangers, that people on reddit will think we’re stupid. That nobody will show up and read our work. We’re anxious that our English isn’t good enough.</p><p>All of these “what-ifs” run through our heads and stop us from posting. We get paralyzed by the “Upload” or “Post” button. We sit down and watch TV instead. Consume more content rather than produce it. That way we don’t have to face the fear.</p><p>You look at all the other makers out there and think they are better than you as they don’t have the fear of shipping. You see them writing blog posts, sending newsletters and shipping new products. They mustn’t face the same fear as you right?</p><p>Wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*_uDaUXy9_oQyLmwozHvUkg.png" /></figure><p>They have just learned one secret.</p><p>The anxiety of shipping never goes away. It just affects you less the more you ship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/0*rjv2euLEYxfTSh8V." /></figure><blockquote><em>The rate at which we ship things is directly proportionate to the amount of anxiety we feel when shipping.</em></blockquote><p>It’s a very catch-22 situation. You are scared to ship, but the only way to get over that fear is to ship; and to do it often. The reason why you see makers like <a href="https://medium.com/@mijustin">Justin Jackson</a>, <a href="https://medium.com/@brennandunn">Brennan Dunn</a> and <a href="https://medium.com/@pjrvs">Paul Jarvis</a> produce so much stuff is because they consistently press that “post” button and so they are less anxious each time.</p><p>With practice and consistency you too will reduce the fear. It won’t ever go away completely, but you will learn to live with it, and next time you hear the little voice in the back of your head telling you it’s not good enough.</p><p><strong>Don’t listen to it.</strong></p><p>Press the “post” button, ship your work, and reduce the fear for next time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/0*VN1ps-dhzcRMcaIP." /></figure><p><em>To help us get over the fear of shipping we are building our product </em><a href="https://kwoosh.com/"><em>Kwoosh</em></a><em> in public. </em><a href="https://medium.com/building-kwoosh"><em>Sharing our story</em></a><em> as we go along makes us less scared to release it to the public. Last month </em><a href="https://medium.com/building-kwoosh/show-your-work-september-2016-e85833346457"><em>we focused on polish</em></a><em>. Tweet us </em><a href="https://twitter.com/kwoosh"><em>@kwoosh</em></a><em> the next time you ship something. We’d love to check out what you’re working on.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25c8507dbbd3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kwoosh/ask-100-makers-what-they-want-to-do-more-of-and-the-answer-is-always-to-ship-more-work-25c8507dbbd3">Fear vs Shipping</a> was originally published in <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Product Playbook is Wrong]]></title>
            <link>https://medium.com/building-kwoosh/your-product-playbook-is-wrong-c9f038bee10b?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9f038bee10b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Tue, 20 Sep 2016 13:01:52 GMT</pubDate>
            <atom:updated>2016-09-20T13:01:52.631Z</atom:updated>
            <content:encoded><![CDATA[<p>Meet John. John is building a new start up. He won’t quit talking about it. It’s a machine learning based app, for helping you find the optimal time to take your dog out (it will log when you currently take your dog out and then predict the future times you will need to take them out). John’s product isn’t finished yet, but it’s getting there.</p><p>Just a few more sprints he says. Since he’s lean, he’s only building what he needs for his MVP (minimal viable product). After he launches he tells us he plans on A/B testing his landing page and that he wants to figure out the optimal shade of blue for his sign up button. Soon he’ll be a stock-option billionaire he assures us.</p><p>This is the common, predictable joue-du-jour: pre-sell your smallest idea, build it as quickly and as cheaply as possible, launch, then A/B test your way to profit.</p><p>I don’t think this is the right play.</p><p>You have an inkling of an idea and in order to save yourself wasted effort, you begin to find customers you can sell to. Find ten who will commit and you can start laying down code.</p><p>You find a few customers quickly and they seem excited about the idea and would totally buy it if it could also send email.</p><p>Wanting to make the sale, you cave. It’s OK you tell yourself. This feature will just add a day or two to development. And this feature will make the next sale easier.</p><p>Before long your product doesn’t resemble your original idea. If you really strain your eyes, you can see your product idea. But each feature concession you made to get each pre-sale has removed the vision bit by bit.</p><p>It your product is perfect for everyone it’s made for no one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*amxUs3OvUk8Mj6o64Bj0qQ.jpeg" /><figcaption>Homer designed a car “perfect” for everyone and bankrupted the company</figcaption></figure><p>Others are able to resist the temptation to bolt on a feature for a sale, because they’re building a quick MVP with all of the features they think they’ll need on launch day.</p><p>The feature list for an initial version is very impressive. But you can clearly see where the design team changed midway through: half of the app looks like it came from Bootstrap and the other half looks like Windows.</p><blockquote>MVP has been interpreted incorrectly. It should be a slice <em>up</em> the value chain. It should be 2 features done amazingly. Not 20 features done half-baked.</blockquote><p>Great product development doesn’t happen when your focus is split in many different directions: focus like a laser on your core idea and polish.</p><p>If you successfully manage get your product out the door and gain a few customers, then you can A/B test and iterate to success!</p><p>While A/B testing is valuable and can produce a lot of revenue, it creates a culture that doesn’t value the slow thinking and intuition required to build great products.</p><p>Our most cherished possessions in life are the ones that are made to last. That pair of artisan boots brings joy day after day. Those crocs you bought drunk on Amazon only fill you with regret.</p><p>Your product should aim to bring lasting joy, not the emptiness of a one-night stand.</p><p><em>Our playbook with Kwoosh is the opposite of the popular playbook. We’re polishing a few features to help you make better software for launch. We’re not doing any pre-sales, though you’re welcome to </em><a href="https://kwoosh.com/"><em>join our mailing list</em></a><em> or follow us on twitter </em><a href="https://twitter.com/kwoosh"><em>@kwoosh</em></a><em>.</em></p><p><em>What are you working on? We love hearing from fellow product people.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9f038bee10b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kwoosh/your-product-playbook-is-wrong-c9f038bee10b">Your Product Playbook is Wrong</a> was originally published in <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Give yourself permission to rest]]></title>
            <link>https://medium.com/building-kwoosh/give-yourself-permission-to-rest-76e7f5b0b817?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/76e7f5b0b817</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Mon, 29 Aug 2016 20:59:51 GMT</pubDate>
            <atom:updated>2016-08-29T20:59:51.972Z</atom:updated>
            <content:encoded><![CDATA[<p>A friend of mine is working on a side project. He’s got plenty of great contract work keeping him busy during the week and a side project for the rest of the time. Like me, he’s a builder.</p><p>As builders our inclination is to build all the time. After all, it’s where we’re most comfortable. We tell ourselves if we <em>just </em>power through <em>one-more</em> weekend, we’ll have completed the product.</p><p>And to a certain extent this is true. Pushing through the weekend does get the feature finished. It might even complete our masterpiece. But chances are, pushing through the weekend will be for naught as we’re going to find excuses to continue building. “Just one-more-thing”, we tell ourselves.</p><p>My builder friend doesn’t have any plans for the weekend. Which means it’s a prime opportunity to get some time in on the side project. But this weekend he lamented:</p><blockquote>“I wish “side-project” didn’t feel so much like “work”. Got nothing to do this weekend but also got no motivation to touch the laptop.”</blockquote><p>When builders have no motivation to work on their side projects, a common mistake they make is to ignore it.They sit in front of the computer browsing reddit…err.. waiting for inspiration.</p><p>Rather than sitting around and waiting for inspiration, we should walk away. When we walk away we should think about the work that remains. Plan out how we’re going to implement it. Then come back the next day, fully rested, and execute our plan.</p><p>Taking these breaks to recharge isn’t just for people who are just getting started. People at the top of their industries recognize the importance of rest and build it into their organizations.</p><p>el Bulli is a 3-star restaurant in Spain known for its creativity in food and molecular gastronomy. The chef, Ferran Adria is largely regarded as one of the best chefs in the world. While most restaurants are open 6 or 7 days a week serving the same menu day after day, el Bulli charged its creativity by only opening in seasons. It would open for seven months and close for five months to experiment and recharge.</p><p>Stefan Sagmeister, a leader of graphic design, takes a year off every seven years to recharge his creative stores. Before taking his first sabbatical, his work all started to look quite similar. After a year recharging his creative battery, his client work looks completely different and has new life that wouldn’t have been possible without a break.</p><p>The habits we form when starting to build our products and businesses are the ones that will shape the rest of the journey. If we don’t allow ourselves to step away and rest for a day when we’re small, we never will, no matter the size.</p><p><em>I’m</em><a href="http://medium.com/building-kwoosh/"><em> building Kwoosh</em></a><em>, a tool to help you manage your app development. I didn’t work on it this past weekend. I went swimming and read a book instead. It was pretty great. Now, I’m rested and ready to work on </em><a href="http://twitter.com/kwoosh/"><em>Kwoosh</em></a><em> some more.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76e7f5b0b817" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kwoosh/give-yourself-permission-to-rest-76e7f5b0b817">Give yourself permission to rest</a> was originally published in <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Houston, we have a problem]]></title>
            <link>https://medium.com/building-kwoosh/houston-we-have-a-problem-7f3b8eb9489b?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f3b8eb9489b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[space]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[nasa]]></category>
            <category><![CDATA[software-craftsmanship]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Thu, 14 Jul 2016 13:15:15 GMT</pubDate>
            <atom:updated>2016-07-14T13:15:15.512Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*QNHnoH8iH80cZZgdfIuBwg.jpeg" /></figure><p>Apollo 11’s Eagle lunar lander guidance computer source code was recently open sourced on Github. As a programmer, especially one surrounded by NASA, it’s fascinating to see and read code written and tested 50 years ago right here in my neighborhood.</p><p>Reading through it I’m left with many questions. What were their work routines like when developing this? What kinds of challenges did they run into? How did they overcome them?</p><p>I wonder what type of people the programmers were. Did they enjoy their work? What did they look like? I imagine the majority had short hair, slide rules in their pockets and wore ties to work. Quite different from today’s hoodies, headphones and baseball caps.</p><p>Reading through the code I found some interesting comments. It made me realize that as different as we may appear on the surface, the challenges that we face as programmers are now the same challenges from 50 years ago.</p><p>They ran into the same pitfalls a modern programmer finds themselves running into: code that should be temporary becomes permanent.</p><blockquote>TC BANKCALL # TEMPORARY, I HOPE HOPE HOPE<br>CADR STOPRATE # TEMPORARY, I HOPE HOPE HOPE<br><a href="https://github.com/chrislgarry/Apollo-11/blob/dc4ea6735c464608d704fa183f3e3d08b013c42f/LUNAR_LANDING_GUIDANCE_EQUATIONS.s#L179">Lunar Landing Guidance Equations.s</a></blockquote><p>50 years ago the developer who wrote this code had a time crunch. He likely had to hit a <a href="https://youtu.be/TUXuV7XbZvU?t=2m21s">tight deadline</a>. While we’re not in the space race today, the average developer’s life is still based on deadlines and the result is the same: temporary code is anything but temporary.</p><p>The code you’re writing today will probably not change. Those shortcuts you write to save 20 minutes today will be there tomorrow. And if the Eagle’s guidance computer is any model, it will be there 50 years from now as well.</p><p><em>We are building </em><a href="https://www.kwoosh.com/"><em>Kwoosh</em></a><em> without any hard deadlines. Follow the </em><a href="https://medium.com/building-kwoosh"><em>Building Kwoosh</em></a><em> publication to see our work in progress to launch and beyond. I’d love to </em><a href="https://twitter.com/jamesvandyne"><em>meet you on twitter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f3b8eb9489b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kwoosh/houston-we-have-a-problem-7f3b8eb9489b">Houston, we have a problem</a> was originally published in <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quality isn’t an Accident]]></title>
            <link>https://medium.com/building-kwoosh/quality-isnt-an-accident-f10321faca58?source=rss-135a503f1bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/f10321faca58</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[James Van Dyne]]></dc:creator>
            <pubDate>Thu, 07 Jul 2016 20:22:58 GMT</pubDate>
            <atom:updated>2016-07-08T19:12:05.258Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SeOkyFYYXVreGJR0mkCw2g.jpeg" /></figure><p>How many times have you tried to plug in a USB cable and failed on the first try? If you’re like me that number is nearly the number of times I’ve ever attempted to connect a USB device. How many times has this happened with a network cable?</p><p>While most people have heard of the term <em>k</em>aizen<em>, </em>or continuous improvement, when talking about Toyota and it’s lean manufacturing principles, fewer have heard of kaizen’s unsung sibling <em>poka-yoke,</em> or mistake proofing.</p><p>The main idea of poka-yoke is to draw attention to human errors as they occur, so they can be corrected or prevented, reducing the number of defects in a product.</p><p>After observing a defect, we identify the root cause of the mistake, and then apply a fix or change in process that attempts to prevent the same error from happening again. This learning can then be applied to improve the design and function products.</p><p>Building your products with poka-yoke requires more initial effort, however the end result is a higher quality and more reliable product.</p><p>As developers, our tool to poka-yoke our services are unit tests.</p><p>Tests are small pieces of software that exercise a piece of code and verify that it’s behaving as intended. Writing tests are, however, many developers least favorite thing about creating software. We like to build new services and libraries because they’re fun and there is a sense of immediate gratification.</p><p>While writing good tests is time consuming and not fun. Setting up the scaffolding, defining test cases, and setting the test data can feel like tedious grunt work without an end in sight. However boring tests may be, they are essential to quality software.</p><p>With Kwoosh we’re aiming for high reliability, minimum regressions, and fast operations. Part of our testing strategy is to have “workflow” integration tests. These tests aim to help make certain that our tests are comprehensive while being easy to understand.</p><p>Each test currently has a maximum of two tests named ‘test_get_workflow’ and ‘test_post_workflow’. Each test then calls a series of descriptively named helper functions to assert behavior.</p><pre><strong>def test_get_workflow</strong>(self):<br>    # Make sure that anonymous users are redirected to login<br>    # and that users are denied access to data that&#39;s not theirs<br>    self.redirect_for_anon_get()<br>    self.not_found_for_wrong_account()</pre><pre>    # Check that our filter interface is filtering data properly so<br>    # calls to &quot;mine&quot; only show tasks assigned to me and so forth.<br>    self.filters_response(self.sub_task_data[&#39;title&#39;], &#39;all&#39;, [])<br>    self.filters_response(self.my_task_data[&#39;title&#39;], &#39;mine&#39;,<br>                          [self.sub_task_data[&#39;title&#39;],<br>                          self.completed_task_data[&#39;title&#39;]])<br>    self.filters_response(self.completed_task_data[&#39;title&#39;],<br>                          &#39;complete&#39;,<br>                          [self.sub_task_data[&#39;title&#39;],<br>                          self.my_task_data[&#39;title&#39;]])<br><br><strong>def test_post_workflow</strong>(self):<br>    # Make sure that all post requests are redirect<br>    # or return 405 and denied<br>    self.redirect_for_anon_post()<br>    self.post_not_allowed()</pre><p>As a lot of the tests will have some helpers in common (such as confirming anonymous users get redirected to login), we can bundle up these helper methods in small classes and include them into the tests, reducing the amount of code we need to maintain.</p><blockquote>Less code = Fewer places for bugs = Less maintenance</blockquote><p>Having descriptively named helper methods will allow future me to glance at the test I wrote today and identify exactly what’s being tested, without having to read through hundreds of lines of code.</p><p>Quality isn’t many things. Quality isn’t free. It isn’t flashy. It isn’t fancy. And it sure as hell isn’t an accident.</p><p>We are documenting designing and building Kwoosh. Follow the <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> publication to see our work in progress to launch and beyond. I’d love to <a href="https://twitter.com/jamesvandyne">meet you on twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f10321faca58" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kwoosh/quality-isnt-an-accident-f10321faca58">Quality isn’t an Accident</a> was originally published in <a href="https://medium.com/building-kwoosh">Building Kwoosh</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>