<?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 Jeff Warren Orr on Medium]]></title>
        <description><![CDATA[Stories by Jeff Warren Orr on Medium]]></description>
        <link>https://medium.com/@jeffworr?source=rss-9edd3229a0a8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LkSBIVMCisA3mbIDcq0UyA.png</url>
            <title>Stories by Jeff Warren Orr on Medium</title>
            <link>https://medium.com/@jeffworr?source=rss-9edd3229a0a8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:25:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeffworr/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[Nextdoor for Mexico City: validating a startup idea in less than a week, for <$100, without code]]></title>
            <link>https://blog.devgenius.io/nextdoor-for-mexico-city-validating-a-startup-idea-in-less-than-a-week-for-100-without-code-70d9f00448bc?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/70d9f00448bc</guid>
            <category><![CDATA[emerging-markets]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[no-code]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Tue, 23 Jun 2020 22:29:47 GMT</pubDate>
            <atom:updated>2020-06-30T15:11:53.976Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Nextdoor for Mexico City: validating a startup idea in less than a week, for under $100, without writing a single line of code</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sbzqrfJadGLnxegt" /><figcaption>Photo by <a href="https://unsplash.com/@max_duz?utm_source=medium&amp;utm_medium=referral">Max Duzij</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Something we see often at <a href="http://webuildyourapps.com/">webuildyourapps.com</a> are founders with big ideas, but little validation to back them up. The common path this leads down is (1) spending a lot of money and time to build an app (2) launching (3) finding out no one wanted the product in the first place. We can’t predict the future, but there <em>are</em> things we can do (in the idea stage) to see whether or not something might work.</p><p><strong>I’ll be using a real-life example (Nextdoor for Mexico City), and running a short (&lt;7 days) cheap (&lt;$100), no-code experiment to see if this idea has potential and get real customer feedback.</strong></p><h3>The Idea</h3><p>Splitting time between SF and Mexico City pre-COVID, I noticed interesting differences in available products. One example is Nextdoor. In the US, my family are avid Nextdoor users — they use it to buy/sell things, find lost animals, discuss safety. In Mexico City, I haven’t seen anything similar and for some reason Nextdoor hasn’t expanded much in LATAM.</p><p>SO, the basic idea is to create a product where users will be able to add messages on a community board, chat with neighbors, buy/sell things, and organize events in Mexico City. Why Mexico City?</p><ul><li>A lot of people with mobile phones</li><li>Densely populated</li><li>Enough things happening in a neighborhood to make for interesting content</li><li>Based on conversations with local friends, people are solving this problem <strong>offline</strong> via “asociación de colonos” (neighborhood groups), and most things done offline can be made more efficient online</li></ul><p>We’ll call it <strong>BARRIO</strong>.</p><h3>#1: Define the Experiment (1/2 day, $0)</h3><p>I’m starting by defining my hypothesis and identifying what I need to prove in order for it to be true. I’ll use a shareable Google Doc so the whole team can understand my thinking:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SNeq61e-_Nr2njkYBydIGg.png" /></figure><h3>#2: Build a Landing Page (2 Days, $12)</h3><p>Now I need to build a simple website that showcases the product. For this, I’m using <a href="http://webflow.com/">Webflow</a>, but any website builder will work (<a href="http://squarespace.com/">Squarespace</a> is good).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ifw2qc9yBFOzqJHXouEerw.png" /><figcaption>Simple landing page built without code on Webflow — <a href="https://barrio.webflow.io/">barrio.webflow.io</a></figcaption></figure><p>For right now, I really only need a logo, a rough mockup of the product, a clear value prop for what the service will offer, and a place to capture emails.</p><p>Obviously there’s no real product to take people to if they sign up with their email, so I’ll add a message there once they submit to let them know we’ll reach out once the product is live.</p><h3>#3: Get Traffic To The Landing Page via Facebook ads (3 days, $40)</h3><p>With the landing page built, now I need some traffic. I’ll use Facebook Ads targeting certain neighborhoods in Mexico City.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GpUiukTe7-_z-6kQeKETMw.png" /></figure><p>Other ways to drive this traffic might be:</p><ul><li>Posting in existing online communities (Reddit, Facebook Groups, blogs)</li><li>Google Search ads</li><li>Word of mouth/existing network</li><li>Physical fliers</li><li>Email marketing</li></ul><p>I ran a few different ads with different graphics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*2oyy1loRcAMAtlyhd6ECIA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*ulz6m5TET5tDsK2aTH8C8Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*yontIa5IYQ_w-B9NRHMUsQ.png" /></figure><h3>#4: Measure Results</h3><p>After letting the ads run for a few days, here were the results:</p><ul><li>Facebook Ad CTR: (1,093 clicks / 54,720 impressions) * 100 = <strong>2% CTR</strong></li><li>Landing Page conversion: (55 emails / 1,093 visits) * 100 = <strong>5%</strong> <strong>Landing Page Conversion</strong></li></ul><p>For reference, average FB ad CTR and landing page conversion rates fall around 1.04% (<a href="https://www.wordstream.com/blog/ws/2017/02/28/facebook-advertising-benchmarks#:~:text=The%20average%20click%2Dthrough%20rate,across%20all%20industries%20is%200.90%25.">source</a>) and 2.35% (<a href="https://www.wordstream.com/blog/ws/2014/03/17/what-is-a-good-conversion-rate#:~:text=But%20what%20is%20a%20good%20conversion%20rate%3F,rates%20of%2011.45%25%20or%20higher.">source</a>), respectively.</p><h3>#5: Make a Data Informed Decision</h3><p>There are three ways we can go from here:</p><ol><li><strong>Build!</strong> — the experiment worked great, we feel the hypothesis was proved, we feel confident investing time and money into building the first version of the product.</li><li><strong>Dig deeper </strong>— our experiment showed some promise, but we don’t feel like our hypothesis was fully proved (maybe we didn’t quite reach our conversion % on the landing page or our FB CTRs weren’t great). From here we should dig deeper. Can we reach out to people who gave us their emails for an interview? Can we run the same experiment but with a different audience? Should we change the value prop on the website?</li><li><strong>Pivot</strong> — our experiment failed, we didn’t even get close to the conversion % we wanted, we don’t feel confident in moving forward and building out the product. <strong>There’s a huge bright side to this</strong>: we saved thousands of dollars and months of our time by identifying early that our idea doesn’t resonate with customers. From here we can either scrap the idea and spend our resources on something else OR we can create a modification of this existing idea and retry with another experiment.</li></ol><h3>Next Steps</h3><p>Based on the results, I feel strongly that there is a need for a Nextdoor-esque service in Mexico City. The data beat or matched industry averages, and the qualitative feedback I got from comments and conversations was promising.</p><p>I’d like to build a simple messaging board to see if people would actually use it to post local content. If that goes well, I can continue building features in an iterative fashion. This is especially important in this context because what worked in the US may be very different than what will work in Mexico. Working in iterations (rather than building everything in the first version) helps me identify those needs and build something tailored to the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*-LVQMNTDKuNhyzhRAzPuVw.jpeg" /><figcaption>Skateboard = simple local message board</figcaption></figure><p>Hopefully this was a helpful read on validating startups still in the idea stage.</p><p>If you want to learn more, reach out — jeff@maplyapp.com ✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70d9f00448bc" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/nextdoor-for-mexico-city-validating-a-startup-idea-in-less-than-a-week-for-100-without-code-70d9f00448bc">Nextdoor for Mexico City: validating a startup idea in less than a week, for &lt;$100, without code</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflecting on 20 Countries in 2 Years]]></title>
            <link>https://medium.com/@jeffworr/reflecting-on-20-countries-in-2-years-ba5e39c5b1ba?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba5e39c5b1ba</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[digital-nomads]]></category>
            <category><![CDATA[travel-tips]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 15:58:23 GMT</pubDate>
            <atom:updated>2020-01-10T16:05:47.147Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve spent the better part of the past 24 months traveling.</p><p>I started in Europe, where I based in Madrid. Moved to Mexico City to learn Spanish. Traveled through South America. Explored Southeast Asia on motorcycle. Spent time in Guatemala. At the time of writing I’m in the Philippines, coming off a two month trip in China. I’ll head to Taiwan next, then to San Francisco for the foreseeable future.</p><p>This post is a retrospective on these experiences. Written with the intent of sharing observations and lessons learned walking off the beaten path.</p><h4>Travel won’t solve your problems, but it lets you look at them more objectively.</h4><p>When I first started traveling, I had just shut down my first company, which was a challenging and stressful experience. I vividly remember sitting on the roof of my hostel in Mallorca, Spain. I looked over the city and for the first time in two years felt completely free of anxiety. Like when people describe near-death experiences. Floating above their bodies in the hospital room — looking down at the stress, worry, and suffering of the world while feeling completely detached. Maybe this is a dramatic analogy, but it’s really how I felt.</p><p>I think the practical note here is that travel offers a temporary escape following a challenging life event — whether that’s shutting down a company, the loss of a loved one, divorce, etc. I don’t believe traveling has the power to fix things (it wasn’t going to save my company) but it does provide a different perspective. For some reason, the act of geographically distancing myself from the US created an “outside-looking-in” view. It helped me analyze things more objectively. From there I was able to see the bigger picture, learn from mistakes, and move on in a healthy way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F0ScbkWKxySKr0qZna90dg.png" /><figcaption>Harder to feel stressed on a volcano.</figcaption></figure><h4>You don’t have to be rich. (Time &gt; Money)</h4><p>There’s a belief, certainly in the US, that long-term travel is only for the rich. In the movie <em>Wall Street</em>, one of the character’s goals in life is to get rich enough to ride a motorcycle across China. The reality is you can do this trip for a few thousand dollars.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7X87yNTqimTaReZxAE4r4w.jpeg" /><figcaption>Riding a motorcycle in Ha Giang, Northern Vietnam. &lt;$400 for a week of rental, lodging and food.</figcaption></figure><p>Wealth, to me, comes in two forms. There’s financial wealth (which is the standard metric in the US) and there’s time wealth. Time wealth refers to the amount of time an individual has at their disposal. Often people with high financial wealth have limited time wealth (the businessman who works 100 hour weeks but doesn’t have time for family). Conversely, an unemployed person may have lots of time wealth but less financial wealth. (Striking a balance here is for another Medium post).</p><p>You obviously need money to travel. But what’s more important is creating time. This is why people often put off traveling until they retire (and have lots of time wealth).</p><p>Awesome interview by Tim Ferriss with Rolf Potts on this <a href="https://tim.blog/2014/11/04/rolf-potts/">here</a>.</p><h4>Meeting people is easier because you automatically share a common interest.</h4><p>Meeting people while traveling is easier because (A) they’re also traveling, and you share the common interest of travel or (B) they’re local, and you’re mutually interested in each others cultures. Both of these are generally sufficient starting points for a conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qC3LL1pdU7drvd4e_PP-WA.jpeg" /><figcaption>Fast friends in Vietnam (despite massive language barrier).</figcaption></figure><p>Maybe this is something I need to work on in my own country…but I just don’t feel this connection with strangers in the US.</p><h4>There are good and bad people everywhere — but most people are good.</h4><p>Many places portrayed badly by American media as “dangerous” have been full of the kindest people I’ve met. Scary stories are interesting, so the news often chooses to focus on them.</p><p>The reality is that danger exists everywhere in the world. My chances of being robbed in LA are similar to Mexico City if I’m being careless. The .01% of bad people in a country don’t reflect the 99.99% of good people living there.</p><h4>Loneliness — being abroad has a multiplying effect.</h4><p>One of the downsides of long-term (solo) travel has been feelings of loneliness. This has the highest impact on me while in Asian countries, where culture shock is generally higher, and time difference means that during the daytime, my friends/family in the US are asleep.</p><p>Ways I’ve learned to combat this while traveling:</p><ul><li>Meet people → obvious but effective.</li><li>Exercise → a long run clears the mind.</li><li>Write → the fastest way to beat negative emotions is to put them on paper.</li></ul><h4>Practical Notes</h4><ul><li>Never check a bag if you can help it. With some planning, there’s no reason you can’t pack everything you need in 1 carry-on bag and 1 personal item (the standard free allowance on most airlines). Benefits include: saves money, saves times, minimizes risk of lost baggage. If you must check a bag, keep your essential items in your carry on.</li><li>Hostel bars and lounges are great places to meet people. I prefer staying in Airbnbs, but doing so means I miss out on some of the social element of traveling. A way to get the best of both worlds is to find an Airbnb near popular hostels.</li><li>Having a pack of cigarettes, even if you don’t smoke, is a great way to start conversations.</li><li><a href="https://www.anker.com/products/107/power-banks">Backup chargers</a> are life savers.</li><li>Cash exchanges at airports are almost always a ripoff. Pull cash from an ATM instead.</li><li>This is a personal thing, but even if I have a short conversation with someone, I exchange WhatsApp or Instagram info. The world is small and you never know when you’ll again be in the same place.</li><li>Buy a local SIM if you’re going to be somewhere for longer than a week. It will be cheaper than an international plan (in most places) and if your phone is lost/stolen, you’ll have your main SIM safe (which is harder to replace while abroad).</li><li>Bring two debit cards. Leave one at the hotel, keep one on you.</li></ul><h3>✌️🌏</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba5e39c5b1ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Natural Selection Teaches Us About Building Products]]></title>
            <link>https://medium.com/@jeffworr/what-natural-selection-teaches-us-about-building-products-c416c5c31201?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c416c5c31201</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Thu, 01 Aug 2019 05:15:19 GMT</pubDate>
            <atom:updated>2020-04-29T23:42:45.646Z</atom:updated>
            <content:encoded><![CDATA[<p>“In natural selection, those variations in the genotype that increase an organism’s chances of survival and procreation are preserved and multiplied from generation to generation at the expense of less advantageous ones.”</p><p>This sounds a lot like the iterative process commonly used when building products.</p><p>We create changes — which are measured by their success against the environment — keep the strong and kill the weak. The end result is a product that’s best equipped to survive and grow.</p><p>Using nature as a teacher, here are some useful parallels I’ve been thinking about…</p><h3>#1</h3><h3>Faster Iteration = Better Chance of Survival</h3><p>The success of an organism is often tied to its ability to adapt. In software, we call this iteration. A product team that can rapidly ship new versions to test different variants will learn exponentially faster than a slow-shipping team. As a result, they’ll have a better chance at building something meaningful. More iterations means more learnings and more chances for a winning variant.</p><h3>#2</h3><h3>Clear Metrics Create Focus</h3><p>In nature, the metric of success is straightforward: survival.</p><p>As a result of nature’s laser focus on a single metric, it’s very easy to measure the success of a variant: did this improve or impair the organism’s ability to survive? Because of this clarity, decision making is easy.</p><p>In product development, we can trace this back to a “north star metric” — a specific metric that best defines the value your product delivers to your customers. Example: for Airbnb this may be # of nights booked, for Facebook this may be # of daily active users.</p><p>Choosing a north star metric creates focus and clarity. Decision-making is simplified to: did this or did this not improve our north star metric?</p><h3>#3</h3><h3>The Environment Has The Final Say</h3><p>In nature, no time is spent debating the potential success of a change. It simply creates the variant and sees how it plays out in the wild.</p><p>Product builders can learn from this bias towards action, and while I’m not advocating for abandoning internal discussion, I do believe that true learning can only come from seeing how people use something in the real world.</p><h3>#4</h3><h3>It’s Never Over</h3><p>Nature exists in a state of perpetual change — the planet cools, heats, water levels rise, disease happens, a meteor strikes. For this reason, evolution is never over. What works today won’t always work tomorrow.</p><p>In building products, things change too — consumer tastes, government regulations, competitors. As soon as we feel we’ve reached a state of perfection, external forces push us into disarray. By recognizing this, and never feeling as if your work is finished, you’ll continue to innovate, grow and survive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*8LDtqu9S5orWlewBB694EQ.jpeg" /><figcaption>Don’t end up like the dodo bird.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c416c5c31201" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Serendipity]]></title>
            <link>https://medium.com/@jeffworr/creating-serendipity-a86840d989da?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a86840d989da</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[luck]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Wed, 19 Jun 2019 15:17:14 GMT</pubDate>
            <atom:updated>2020-06-23T00:20:23.461Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Get Lucky</h3><p>Luck is when preparation meets opportunity — often following a seemingly serendipitous chain of events. This post is about creating those opportunities.</p><p>This is by no means an exhaustive list. Nor is it guaranteed to make you lucky. But it will put you in more situations where you have the potential for luck — in an unpredictable world I believe that’s the best we can do.</p><p>The most serendipitous events in my life, from raising $100K off a LinkedIn post to creating friendships with people all over the world, were all in some way influenced by one or more of the following practices…</p><h3>Having a ¯\_(ツ)_/¯ attitude towards rejection</h3><p>We’re scared of rejection (I know I am). But facing this fear and recognizing that the worst possible outcome is being ignored or hearing “no” is one of the more powerful realizations of my life.</p><p>This just played out in the real world. In July I’ll be traveling to Hong Kong. I did some research and found a startup there that had recently raised $300M doing interesting work in logistics. I decided to email an exec for coffee…worst case scenario is I don’t hear back or get a “no” (<em>maaaybe</em> a “f*** off”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TxiUBWyZ-pW986wiPte8jw.png" /><figcaption>Cold email to someone I’d like to meet. Worst case scenario is I never hear back or they say no ¯\_(ツ)_/¯</figcaption></figure><p>A few hours later, I received a friendly reply to schedule a time. Whether this manifests into opportunities remains to be seen, but the potential is there.</p><p>I’ve sent hundreds of these cold emails, most often never hearing back. It’s the few that respond making it worth the effort and opening doors that never would have presented themselves otherwise.</p><p>Another example was applying to be a featured startup at South by Southwest in 2017. We were seniors in college with an app that had a thousand users at the time (AKA not many). We applied to be featured at the conference, knowing that we probably weren’t qualified. The risk was spending an hour on an application and getting a “no” — pretty insignificant considering the possible upside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*_VREwSizVWEsM_-ENERbTQ.jpeg" /><figcaption>Featured Startup at South by Southwest 2017 and the $100,000 LinkedIn post</figcaption></figure><p>By some measure of good fortune, we were accepted (maybe they didn’t have many applicants 😅). The good news was shared on LinkedIn. A friend of a teammate’s family member saw it and asked to be introduced. Said friend ended up investing $100K into our company. This chain of events couldn’t have happened if we had been scared of “no.”</p><h3>Writing</h3><p>Writing is a magnet for interesting opportunities and meeting new people. It really doesn’t even matter what you write, so long as you’re passionate about it. Once published, it lives on the interwebs, waiting to be uncovered — creating unlimited serendipitous opportunities. It’s a lot like building software — you invest time/energy once to make it, then it continues to create value in perpetuity once released.</p><p>This just happened a few weeks ago. I published an article about <a href="https://uxdesign.cc/a-business-case-for-user-delight-5d3e6ad61adb">designing apps</a>. There was a real possibility that no one would read that post — and my few hours of effort would go unnoticed. I didn’t care. I love writing about building products and would do it anyways. <em>Most</em> <em>serendipitously</em>, a few days after publishing, someone from UX Collective, a Medium Newsletter with 270,000 followers, reached out and asked if I’d like to publish the story on their site. Of course!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M5-KRIQYBu5J_S77fK-8Pw.png" /><figcaption>Writing is a magnet for interesting opportunities.</figcaption></figure><p>I recognize that maybe no one will read this, but the “risk” of spending a few hours of my time is worth the potential upside, plus it’s fun 😊</p><h3>Traveling…alone</h3><p>As an introvert — the concept of befriending strangers isn’t necessarily an exciting one. But being solo in a foreign place forces it. The options are (a) be alone — which even for me gets boring after awhile or (b) get out of your comfort zone and make friends.</p><p>On a recent trip to Guatemala, I wanted to hike a volcano. The problem was I was traveling by myself — solo guides were expensive, so I needed others to split the cost with. Out of this necessity I found a group of other solo travelers interested in doing the hike. We hired a guide, made it to the top, and became good friends along the way.</p><p>I never would have met these guys had I not travelled alone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JgbUtk6urIZP3yjPT9oUw.jpeg" /><figcaption>Hiking a volcano in Guatemala. Traveling solo on this trip meant I had to get out of my comfort zone and meet others. Now, I have a friend in Guatemala, Italy, Germany and France (left to right).</figcaption></figure><p>All of these share a common theme: they’re <a href="https://twitter.com/naval/status/1054984950192181248">asymmetric opportunities</a>. In other words, there’s tremendous upside and very limited downside risk — so what if someone tells you “no”, so what if no one reads your writing, so what if you feel a bit lonely in a foreign place. The risks are worth the rewards.</p><p><strong>Good luck 🔮</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a86840d989da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A business case for user delight]]></title>
            <link>https://uxdesign.cc/a-business-case-for-user-delight-5d3e6ad61adb?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d3e6ad61adb</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Mon, 13 May 2019 00:32:44 GMT</pubDate>
            <atom:updated>2019-11-01T22:02:38.302Z</atom:updated>
            <content:encoded><![CDATA[<p>The things that typically get built first (in software) are those that can be measured against core metrics (growth, conversion, retention, etc.) These are the easiest features to justify and get on the product roadmap.</p><p>What’s harder to figure out is how much resources should be allocated for things that just <em>feel right — </em>a quick animation, a hidden feature, a clever notification<em>. </em>It’s hard to measure the impact of putting a smile on a user’s face. However, just because something’s hard to measure doesn’t mean it’s not important.</p><p>Some things I’ve noticed lately that show the business value of building <em>feel right</em> features…</p><h3>1. Delight builds loyalty</h3><p>When you exchange secrets with someone, you build trust. I believe the same applies to software. When users discover hidden parts of an app, they feel a connection.</p><p>Snapchat does this well. Their product is full of “secrets.” From press-and-hold on the home screen for Shazam, to the omnipresent but elusive Ghost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*U5kl1hmNx7EXRUKTrmeA9w.png" /><figcaption>This guy is everywhere yet nowhere.</figcaption></figure><p>Unpredictability makes Snap fun. You never know what you might find. By baking in variety to its design, Snapchat creates a moat: people feel more connected to the product from the secrets it’s shared.</p><h3>2. Happy users spread joy</h3><p>When Facebook rolled out dark mode, they could have buried an On/Off switch somewhere in Settings. Instead, they opted to add some delight by making it discoverable only by using a <a href="https://thenextweb.com/facebook/2019/03/04/enable-dark-mode-in-messenger-by-sending-an-emoji/">secret emoji</a> 🌒. When people discovered it, they felt special and wanted to share — like when you hear a good story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zasyaOgBjH3FiY87nWt_BQ.png" /><figcaption>“Hey everyone! I found this cool thing.”</figcaption></figure><p>One product that clearly prioritizes user delight is Zenly. I first heard about the social map app from a friend who had a great experience and just <em>had </em>to tell me about it. He’s not the only one wanting to share…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJwTysuTMNnjlupYtXKX9A.png" /><figcaption>Delighted users want to share their experience.</figcaption></figure><p>One could argue that the stickers, animations, sounds and other added effects in Zenly are fluff. But without them, Zenly wouldn’t stand out, and no one would care enough to talk about it.</p><h3>3.</h3><p>There is no number 3…but having a 2 item list didn’t feel right. So in closing:</p><p>It’s worth noting that all the products mentioned here would still be hugely popular even if they hadn’t designed for delight. However, by allocating some portion of their resources to creating these experiences, they benefited from increased organic growth, press coverage and customer loyalty…and who doesn’t need more of that?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d3e6ad61adb" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-business-case-for-user-delight-5d3e6ad61adb">A business case for user delight</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to do before launching your app (other than building it)]]></title>
            <link>https://medium.com/@jeffworr/what-to-do-before-launching-your-app-other-than-building-it-db9ea558f5c2?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/db9ea558f5c2</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[app-development]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Thu, 24 Jan 2019 17:39:27 GMT</pubDate>
            <atom:updated>2019-01-24T17:39:27.227Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I had just hit Send on an email to a client detailing what they need to do before launching their app. As I did, I realized this information is probably useful to someone else too. SO, </em><strong><em>here’s a quick article detailing the un-sexy essentials of preparing for an app launch.</em></strong></p><p>Building an app is exciting, and finding a company that can build it (like ours, <a href="http://webuildyourapps.com/">webuildyourapps.com</a> 😃) is great too. But once you have designers and developers getting to work, there are three important steps that should be completed before launching your product.</p><h3>Create a Terms of Service &amp; Privacy Policy 🖊</h3><p>The first is creating a Terms of Service and Privacy Policy.</p><p>Terms of Service (TOS) are essentially the “rules” a user agrees to follow while using your product — it offers a layer of protection in the event that one of your users takes legal action against your company.</p><p>Privacy Policy details how you use your user’s personal information and data.</p><p>Depending on the type of Developer Account you create with Apple, you’ll need these documents to register an account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7qcDwddwSNOUxU5XCChhGQ.jpeg" /><figcaption>Terms of Service and Privacy Policy — often overlooked, but important.</figcaption></figure><p>We like using <a href="https://www.lawtrades.com/">LawTrades</a> to find a lawyer to draft these documents. LawTrades will connect you online with a verified lawyer at an affordable price (you can typically negotiate a package deal for around $2K).</p><p>If you want to go the cheaper route, there are online templates you can use. However, this is generally not advised as you want to make sure a professional is overseeing these very important documents.</p><h3>Build a Website 🖥</h3><p>Having a website is best practice, even if it’s super simple. Also, Apple requires you to have a company website if you register as an Organization when you create your account.</p><p>Your website can literally be three pages: (1) a landing page: your logo + tagline/short description of company (and a download link to the app once that’s ready). (2) A contact page: a place where people can fill out a form and send you a message. (3) A page where you put your Terms of Service and Privacy policy. I think <a href="https://houseparty.com/">Houseparty</a> and <a href="https://islands.im/">Islands</a> have great examples of websites for their apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gqYfgT7Lc4hSwO6kn1lfpg.png" /><figcaption>Simple landing page for an app we built. Has the app name/logo, tagline, download link, and way to Contact Us and view the TOS + Privacy Policy at the bottom.</figcaption></figure><p>We recommend using <a href="http://squarespace.com/">Squarespace</a> to create the site — it’s easy-to-use (no code required) and includes a free domain name with the purchase of a 1 year subscription (which costs $144/year). P.S. we build these types of sites at <a href="http://webuildyourapps.com/">webuildyourapps.com</a>.</p><h3>Register your Apple Developer Account / Google Play Account ☑️</h3><p>After completing the steps above, you’ll want to register your account with Apple and/or Google (depending on if you’re building for iPhone or Android). <a href="http://learn.buildfire.com/publishing/apple-specific-articles/how-to-create-an-apple-developer-account">Here’s a step-by-step guide</a> for registering with Apple (skip Step 1). And <a href="https://help.swiftic.com/hc/en-us/articles/201709571-Create-a-Google-Play-Developer-Account">here’s a step-by-step</a> for registering with Google Play.</p><h3>Timeline ⏰</h3><p>It’s best to get started on these as soon as possible. If everything goes smoothly (and expedited), these steps could probably be completed within a week. However, we typically see it taking around 30 days.</p><p>As always, I hope this was helpful. If you’re building something (or thinking about building something) and want to work with award-winning designers and engineers, check out our work at <a href="http://webuildyourapps.com/">webuildyourapps.com</a> or reach me directly at jeff.warren.orr@gmail.com 😃</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pCYgEI6KK-ic8vxO685eBA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db9ea558f5c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Remote Freelance Guide]]></title>
            <link>https://medium.com/@jeffworr/remote-freelance-guide-847adf734966?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/847adf734966</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Wed, 02 Jan 2019 19:20:02 GMT</pubDate>
            <atom:updated>2019-01-02T19:20:02.321Z</atom:updated>
            <content:encoded><![CDATA[<p>The step-by-step guide I wish I had when I started working as a remote freelancer. From the first call to the final invoice and beyond ~</p><p><em>Disclaimer: This is based on my experience as a remote freelancer </em><strong><em>designing products and managing software development</em></strong><em> at </em><a href="http://webuildyourapps.com/"><em>webuildyourapps.com</em></a><em>. It hopefully has value for other freelance types, but will be most relevant to the </em><strong><em>client-facing side of building software remotely.</em></strong></p><p>Over the past 6 months, I’ve been running an all-remote software design and development company (<a href="http://webuildyourapps.com/">webuildyourapps.com</a>). We’ve built products for clients ranging from Trucking Logistics to Healthcare to Higher Education — giving me the freedom to work and live in 18 different countries. While making money from my laptop in an Argentinian cafe has always been a dream, there have been some hard lessons learned. Reading this will help you avoid some.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A2tqWDsr2faAGI7LOo6uJA.png" /><figcaption>“Office” of the day in Buenos Aires coffee shop.</figcaption></figure><h3><strong>First contact 📆</strong></h3><p>Yes!! We have a lead. Since creating said leads is worthy of another blog post, we’ll skip right to the first meeting.</p><p>As a remote freelancer, all my meetings are done via video call. <a href="http://appear.in/">Appear.in</a> is my favorite. Meeting in person is better than a video call — video call is better than a phone call. Matching a face with a voice is a good way to build trust.</p><p>My goals for this meeting are to (1) make sure both parties want to work together and (2) get the info I need to create a proposal (features, budget, timeline).</p><p>Most of my initial calls go like this:</p><p><strong>Introductions (10 mins)</strong></p><p>In the first ten minutes of the conversation I want to find out: where are they from? what do they do? how do they know the person that intro’d us? what do they do in their free time? do they like dogs?</p><p>I also use this time to establish my credibility. Something like:</p><p><em>“I launched an app that operates in 23 cities and reached top 100 in the Social Networking category. Now I work with other startups to help them build successful products too </em>😃<em>”</em></p><p><strong>Set Meeting Goals (~:30 seconds)</strong></p><p>After getting to know each other, I say what I hope to accomplish by the end of the meeting. Literally:</p><p><em>“By the end of this meeting I‘d like to have a solid understanding of what you’re building, as well as your budget and timeline. Sound good? Great.”</em></p><p><strong>Project Details (30–40 minutes)</strong></p><p>This is when we dive into the details of what’s being done. I ask questions on features and take notes. If something isn’t crystal-clear, I ask again. (Skip to the <strong>Proposal</strong> section to see what these notes will end up looking like).</p><p>If you’re non-technical, it’s wise to have someone on your engineering team on the call to clarify technical details.</p><p>Depending on the complexity of the project, figuring out the features may take a few hours. If this is the case, I schedule a 2-hour meeting or follow up to schedule another.</p><p>After figuring out features, I ask what their budget for the project is and when they need it done.</p><p><strong>Wrap Up (5 minutes)</strong></p><p>I ask “do you have any questions for me?” Answer those.</p><p>Then I let them know “next steps is I’ll send you a proposal by end of week. If you need anything in the meantime, feel free to reach out.”</p><p>By the time I end this initial meeting, I should know (1) is this a person I want to work with? And (2) what’s their product features, budget and timeline?</p><p>If yes to both, I move onto drafting the proposal. If (1) is no, I tell them we can’t do it (ASAP!) so they can find someone else. If (2) is no, I email or find another time to meet and clarify.</p><h3><strong>Proposal 🤝</strong></h3><p>(I’m not a lawyer so none of this should be considered legal counsel).</p><p>After deciding that (1) I want to work with this client and (2) it makes financial and logistical sense for my team to take on the project, I draft a proposal.</p><p>In the interest of time, I create one document that includes both the proposal AND the legal contract. This cuts out an additional step of sending docs back and forth.</p><p>My proposal will look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5J4V9gIO6KYl1LOQNL6dwA.png" /><figcaption>Proposal section describing what we’re building, how long it’ll take and how much it costs.</figcaption></figure><p>To break this up, the Proposal section will include:</p><ul><li><strong>Start date: </strong>when we are starting work.</li><li><strong>Billing Period: </strong>defines how we’ll be getting paid. I’ve found it best to do half before the project starts and half upon completion.</li><li><strong>Description of Services: </strong>the most important part of this document. Lays out very clearly what features are going to be built. The more specific, the better. This example proposal is probably too broad, but we were working with a client we had worked with before and there was already a clear understanding of what needed done.</li><li><strong>Project Fee: </strong>what it’s going to cost. This can be written as a ranged estimate (ex: $18K to $20K).</li></ul><p><a href="https://www.and.co/the-freelance-contract/contribute">Click here</a> for the entire proposal template that we use (including the legal section).</p><p>Once this document is completed, I email it in PDF form to the client. If they like it, they’ll sign and we can get to work.</p><p>A note on getting paid: if you’re doing the half-up-front payment plan, you’ll want to send an invoice and payment instructions after the contract is signed. We accept payment via Paypal and our invoices are simply this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*eCop1Z0Zxa73BqRcfhrRTw.png" /></figure><h3><strong>Kick off ⭐️</strong></h3><p>The kick off is generally 2 or 3 hours depending on the project complexity. The goal of this meeting is to decide how we’re going to weave together the features list into a cohesive product. By the end of meeting I should have enough information to create a wireframe of the app.</p><p>I find it best to break up the product into the main user actions. For example, a user of a Starbucks app will need to complete the following actions:</p><ul><li>Creating an account</li><li>Creating an order</li><li>Paying upon arrival</li></ul><p>With clear actions identified, I can create stories and work with the client on the user’s experience of completing these actions. I can ask specific questions like:</p><ul><li>I just downloaded the app, how do I create an account?</li><li>I want to order a coffee — how do I accomplish that?</li><li>I’m walking into the store — how do I pay?</li></ul><p>I take notes, ask a ton of questions, and focus on one feature set at a time. If I think the client is wrong, I tell him/her — that’s what they’re paying me to do.</p><p>Once I’m confident about how someone is going to use this product, I wrap up the meeting by letting my client know that I’ll create a wireframe and send it over for approval.</p><h3><strong>Design ✏️</strong></h3><p>I split design into (1) low-fidelity Wireframes and then (2) high-fidelity Mockups. <a href="https://www.behance.net/gallery/74018879/Paytient-UXUI-Design-Process">Here’s</a> a more in-depth look at my design process.</p><p><strong>Lo-Fi Wireframe</strong></p><p>You can either collaboratively create wireframes with the client or you can create them on your own and send them over for final approval. I work better when I have space to create on my own, so long as I have a clear understanding of the client’s needs from our kickoff meeting.</p><p>The beauty of a wireframe is that it’s fast to make and creates a framework for the rest of the project. I explain it to my client as “creating the architect’s blueprints before we start building a house.”</p><p>I’ll send over something like this and schedule a call to talk them through it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_iWtNpg9NtKgFpfal3pAKg.png" /><figcaption>A wireframe sent to a client for review and approval.</figcaption></figure><p><strong>Hi-Fi Mockup</strong></p><p>Once I’ve gotten approval on the wireframe, I can make it look nice. Client-facing steps at this point include:</p><ul><li>Deciding a color palette: I use <a href="https://coolors.co/">Coolors.co</a> for quickly creating palettes.</li><li>Picking font: I’ll find 3 that look nice and send them for the client to decide. If they can’t pick from those options, I tell them to use <a href="https://fonts.adobe.com/fonts">Adobe Fonts</a> to find one they like.</li><li>Note on choices: I normally only send 3 options at a time. More than that causes analysis paralysis.</li></ul><p>With wireframe, color palette and font decided, I can create a mockup of the finished product. I send it for final approval.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGakuv37R0D7Up-wgFb4ww.png" /><figcaption>A high-fidelity mockup, sent as a PNG to client for approval.</figcaption></figure><p>If all goes well, they’ll approve the mockup and development can begin. I reiterate at this point that all changes need to be final — once we start writing code it’s much harder to alter the design.</p><h3><strong>Development 🖥</strong></h3><p>Normally, development is the least client-facing activity. However, it’s important to keep them in the loop on progress. Things like sending screenshots of working parts of their app can be nice touch points. One of my favorite things to do once we have the app running on a device is to send them a photo of how it looks on the home screen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S756XLLjN4M9dAUiRroEow.jpeg" /><figcaption>Check out what your app is going to look like on people’s phones!</figcaption></figure><p>The sales tactic of “underpromise and overdeliver” also applies to development time estimates. If my team thinks it will take two weeks to implement a feature, I’ll tell the client it will take three. Best case scenario, they’re happy when we deliver early — otherwise, we get ourselves an extra week in case something goes wrong.</p><h3><strong>Testing 👀</strong></h3><p>Once we’ve completed development, we need to test the product to make sure it matches the design and is bug-free.</p><p>The first round of testing is generally rough. I recommend doing it yourself/with your internal team. Only when I think the app is 95% stable do I send it to the client to test.</p><h3><strong>Launch 🚀</strong></h3><p>Testing is complete…we’re ready to launch. This is an exciting moment for my client, especially if it’s their first time. I’ll keep them involved by sending screenshots of progress and email updates from Apple/Google (if we’re building a mobile app).</p><h3><strong>And beyond 💛</strong></h3><p>Following a successful launch, I’ll meet with my client to have closure on the project. In this meeting, there are a few things I want to cover:</p><ul><li>How did we do? Making sure they were happy with our work.</li><li>Discuss retainers/continued work — if I enjoyed working with this person, I’ll make it easy for them to continue the relationship. This meeting is a good time to discuss a retainer structure for if they’d like to keep us around.</li><li>Ask for referrals — if they liked me, they should tell their friends. To make this even easier, we offer our clients 10% of any deal they bring us.</li><li>Let them know you’re sending a final invoice.</li><li>Say thank you!!!</li></ul><h3>Random Tips 💁‍♂</h3><ul><li>Don’t get discouraged when leads don’t convert, this is often the nature of business development. Good things come to those who keep going.</li><li>Trust your gut on working with people. Red flags include: not having a budget to pay you, taking long periods of time to respond, not having a clear idea of what they want built.</li><li>Stay in touch with clients (even if they don’t keep you on retainer). I’ll create a calendar reminder 4 months after I complete a project to remind me to touch base with someone and see how they’re doing.</li></ul><p>I sincerely hope this was helpful. If you’re building something and think we can help, check out our work at <a href="http://webuildyourapps.com/">webuildyourapps.com</a> or reach me directly at jeff.warren.orr@gmail.com 😃</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=847adf734966" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our monthly update template]]></title>
            <link>https://medium.com/@jeffworr/our-monthly-update-template-5b06779d113?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b06779d113</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[investing]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Tue, 15 May 2018 05:45:22 GMT</pubDate>
            <atom:updated>2018-05-15T05:45:22.520Z</atom:updated>
            <content:encoded><![CDATA[<p>I laugh when I look back at the monthly update emails I used to send to people, but like most things entrepreneurial, they got better after time and failure. Here’s what works…</p><p>First, a few reasons to send monthly updates, regardless of company stage:</p><ul><li>They make you step back from the day-to-day and look at your business from a birds-eye-view. Thinking in months vs. days helps spot issues/inefficiencies and also find the small victories and trends.</li><li>They’re a monthly touch point with everyone important you’ve met— every time I meet someone interesting (potential investor, advisor, customer, connector) I ask if they’d like to be included in our monthly update email. I’ve made countless connections because someone I met one time saw something in an update and knew someone we should meet.</li><li>Investors appreciate being in the loop and can be more helpful if they know what’s happening — good or bad.</li></ul><h4><strong>Our template:</strong></h4><p>Subject: “[company name] // [month, year] update”</p><p>Hi all,</p><p>Here’s what we did this month, where we need help, and where we’re going next.</p><p><strong>KPIs</strong></p><ul><li>Bullet points listing KPIs for that month and percent change since last month. These change depending on the company.</li><li>ex: “4,576 event check ins (+11%), 17% WoW user growth over last 4 weeks (+2%), 57% monthly retention (-2%)</li></ul><p><strong>Help us with:</strong></p><ul><li>Include what you need help with near the top, it’s generally most important and will be more likely read.</li><li>Specific asks are better.</li><li>ex: “we’re looking for introductions to folks working in business development at digital mapping companies with 50–200 employees”</li></ul><p><strong>Product</strong></p><ul><li>What’s new with the product this month, what are next plans (plus any relevant metrics that accompanied a product change).</li><li>ex: “We launched location-based notifications this month and saw a 14% increase in daily app opens.”</li><li>ex: “Next month we’re working on integrating heat maps and optimizing map load times.”</li></ul><p><strong>News</strong></p><ul><li>Good/bad news about company and industry — new hire, market shift, big partnership, wins and losses</li><li>ex: “we’re excited to welcome Bertram Gilfoyle to the team as lead system engineer.”</li><li>ex: “Hooli acquired our competitor, Endframe.”</li></ul><p><strong>Appreciation</strong></p><ul><li>Give recognition to someone on your team and/or investor list who helped this month. This can also nudge those who aren’t helping :)</li><li>ex: “Thank you to Monica Hall for connecting us to three customers this month!”</li></ul><p>Thanks,</p><p>Jeff</p><h4>Notes</h4><ul><li>Shorter is better, focus on business/need-to-know. No one really cares about fun facts/culture/PR and this takes away from important info</li><li>Use bullet points, quicker to read. &lt;3 sentences per bullet point.</li><li>Write everything in the email body (not an attachment)</li><li>BCC everyone</li><li>Monthly updates aren’t just for existing investors, they can be a great tool for building trust among potential investors and staying in touch with relevant people.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b06779d113" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good books]]></title>
            <link>https://medium.com/@jeffworr/good-books-764c8d76803a?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/764c8d76803a</guid>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Sun, 29 Apr 2018 18:11:24 GMT</pubDate>
            <atom:updated>2019-04-29T01:58:44.603Z</atom:updated>
            <content:encoded><![CDATA[<p>A running list of books I’ve loved. In no particular order…</p><p><strong>Over the Edge of the World: Magellan’s Terrifying Circumnavigation of the Globe — Laurence Bergreen</strong></p><p>A story of determination against all odds. For those in startups, there’s an interesting parallel between Magellan’s journey and starting/building a company — big idea with big reward / raising $ / building a team / moving through failure / <a href="https://www.businessinsider.com/sam-altman-gave-himself-scurvy-2016-10">scurvy</a>.</p><p><strong>Shoe Dog — Phil Knight</strong></p><p>The story of Nike. Makes a compelling argument for taking at least one big risk in your life.</p><p><strong>How to Get Filthy Rich in Rising Asia — Mohsin Hamid</strong></p><p>Not your typical self-help book. It’s a quick read that will leave you feeling like you’ve lived another life.</p><p><strong>Sapiens — Yuval Noah Harari</strong></p><p>A brief history of mankind. The way Harari talks about our past will change the way you think about our future.</p><p><strong>Extreme Ownership — Jocko Willink and Leif Babin</strong></p><p>True leadership is complete accountability for everything that happens at every level of your organization. This applies to SEAL teams, 5-person startups, and Fortune 500 corporation.</p><p><strong>American Kingpin — Nick Bilton</strong></p><p>The unreal real story of Ross Ulbricht. Covers early bitcoin, hitmen, supply and demand. It follows the path of most tech startups — starting/scaling an internet company, funding, media relations, hiring…main difference being that Ross is building an online drug empire.</p><p><strong>The Everything Store — Brad Stone</strong></p><p>The story of Amazon starting in Jeff Bezos’ garage. I love books that show the lives of successful people before they made it. This is one of the best of that variety.</p><p><strong>Wherever You Go, There You Are — Jon Kabat-Zinn</strong></p><p>The best/most comprehensive book I’ve read on mindfulness and meditation. I found it best to read one chapter per day…reading cover-to-cover doesn’t allow enough time to think about ideas.</p><p><strong>The Hard Thing About Hard Things — Ben Horowitz</strong></p><p>Recommend this one to anyone in a challenging leadership position. Required reading for first-time founders.</p><p><strong>Angel — Jason Calacanis</strong></p><p>I’m not an angel investor but Angel gave me great perspective on what early-stage investors are thinking about. Helpful for fundraising.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=764c8d76803a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Idea to App Store in 7 Days]]></title>
            <link>https://medium.com/@jeffworr/idea-to-app-store-in-7-days-e096aa8a6bab?source=rss-9edd3229a0a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e096aa8a6bab</guid>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jeff Warren Orr]]></dc:creator>
            <pubDate>Sun, 29 Apr 2018 18:09:41 GMT</pubDate>
            <atom:updated>2018-12-05T19:33:57.333Z</atom:updated>
            <content:encoded><![CDATA[<p>My team built and shipped an iPhone app in 7 days. Here’s how it went down.</p><p><strong>The Idea</strong></p><p>There are two things we obsess over — local discovery and maps (our main product is <a href="https://itunes.apple.com/us/app/maply-local-event-sharing/id1161244763?mt=8">Maply</a> — a real-time event map). This means we use social map apps all day. One of our favorites is Waze.</p><p>A Waze feature that everyone seems to love is the ability to chat with other drivers. People use it to learn about road conditions or for entertainment from the passenger seat.</p><p>We asked ourselves — how can we incorporate map-based messaging to make it easier to figure out what’s happening at a certain location?</p><p>We began listing use cases/problems this could solve:</p><ul><li>Find out how crowded a bar/coffee shop is</li><li>Ask how many seats are left in the library</li><li>Make a new friend in a country you’re visiting next month</li></ul><p>From this, an idea was formed. Its working title was Marauder’s Map.</p><p><strong>Basics (Name, Logo, Interface)</strong></p><p>When we first started designing, we wanted to incorporate Marauder’s Map into Maply. It was gonna look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*sK7NKy1kgoE1oxJDu1aWBg.png" /></figure><p>We quickly decided to spin it off into a separate product. There were two reasons for this — (1) we’ve been wanting to build something with a very straightforward use case (three buttons or less) and (2) we’d rather iterate on a stand-alone product, make it really awesome, and <em>then </em>incorporate it within our main product (Maply).</p><p>So it was back to square one — which meant we needed a new name, logo and interface.</p><p>For the <strong>logo</strong>, we wanted something friendly. We also needed something that was within my limited logo design wheelhouse (hiring an outside designer would have cost time and money). Here were some very rough ideas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*hx_-V7nDo2Y6M3tt9J_qWA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*uKYBU7SB8-o_ysPsJe_j7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*82V83ZpjQ3z5PUqCUi1WaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*HSE-rjDzDaf1F8ale46Xww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*gHsoCIsujvZRE0yR-q10qQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*TfEw9WPDXmyaa0bgQwCD9A.png" /></figure><p>All of these kinda sucked. But what mattered was that they got us talking. We’ve found the fastest way to get creative is to kill your pride and accept that most of your early iterations will be garbage. In quickly making these logos, we created an environment for discussion that was open to any ideas, good or bad.</p><p>At one point someone asked “if this app was an animal, what would it be?”</p><p>Birds can fly and get a ‘birds-eye view’ of what’s happening below. That was fitting. Parrots are colorful fun-looking creatures. Cool.</p><p>I drafted up a few parrot logos (all created entirely with circles — easy). To decide which to pick I created an Instagram poll. The votes were cast and we had a logo:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*uHPh0HG9a1vkEIyXU1zbYw.png" /></figure><p>Next came the <strong>name</strong>. Again, we wanted something friendly. Ideas included Parrot, Mapchat, Chatmap, Chatter, Chattr. We went with Mapchat. (A few days after submitting to the App Store we changed the name to Mapchatter because ‘Mapchat’ is apparently very hard to rank for in the App Store.)</p><p>Once we had a name and logo, we bought the cheapest domain name possible (<a href="https://mapchat.cool/">mapchat.cool</a> for $4). This didn’t have to be anything fancy — its main use was to house our Terms of Service and provide the URL that the App Store requires.</p><p>To design the <strong>interface </strong>(what the app would look like) we asked ourselves what features absolutely needed to be included.</p><ul><li>A map</li><li>A way to display users on the map</li><li>A chat interface</li></ul><p>We did indulge ourselves on a few unnecessary features. We came up with “the wave” and the ability to change your emoji based on your current mood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*gm_T_L9DDfxvmB0Z_us11Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*fK0wBE_cYS6X0MMi6LWfGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*62JmvWI0uKPfCOXl-Gn6-A.png" /></figure><p><strong>Development</strong></p><p>With the design in place, our incredibly talented iOS developer (<a href="https://twitter.com/dallashoelscher">@dallashoelscher</a>) was able to build the app within the week.</p><p>Keeping the concept and design simple was valuable during development.</p><p>We shipped (experienced a lengthy review process with Apple) and were eventually approved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*JkiMYYK9ibWjbdu9bRZH6Q.png" /></figure><p><strong>In Conclusion</strong></p><p>We built Mapchatter in a week by following a few rules.</p><ol><li>We kept the idea and product simple. Create something that only does one thing. Challenge yourself to build an app with less than three buttons on the home screen.</li><li>We didn’t waste time on things that can be changed. We picked a name and logo that was relevant and communicated the personality of our product. We didn’t hire a graphic designer (you don’t need to be a professional to create the Facebook logo). We bought the cheapest domain name we could find and put the bare minimum on it.</li><li>We shipped the app as soon as it covered the basic features, rather than waiting until everything was ‘perfect.’ You learn exponentially faster this way.</li></ol><p>Here’s a link to check out the live app — <a href="http://apple.co/2hPuWSS">http://apple.co/2hPuWSS</a></p><p><strong>Afterward</strong></p><p>Two weeks after we released Mapchatter, on a sunny Austin TX day, I woke up to an excited text message from our iOS developer. He had been watching analytics on Mapchatter that morning and had found something unusual. The app had picked up traction in the Middle East with over a thousand active users and 100,000+ messages sent! I opened the app and panned over to find this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*-8f-N_HLrDwa26WtanLUsw.jpeg" /></figure><p>Each face was a complete stranger using something we created to communicate. Pretty neat.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e096aa8a6bab" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>