<?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 Derek Edwards on Medium]]></title>
        <description><![CDATA[Stories by Derek Edwards on Medium]]></description>
        <link>https://medium.com/@DerekBEdwards?source=rss-847a2937e155------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QMEQfAXuwww1Qh7V4jpRJQ.jpeg</url>
            <title>Stories by Derek Edwards on Medium</title>
            <link>https://medium.com/@DerekBEdwards?source=rss-847a2937e155------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:31:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DerekBEdwards/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[My 5 Questions for When to Build vs. When to Buy]]></title>
            <link>https://medium.com/@DerekBEdwards/my-5-questions-for-when-to-build-vs-when-to-buy-b398cc4219f5?source=rss-847a2937e155------2</link>
            <guid isPermaLink="false">https://medium.com/p/b398cc4219f5</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Derek Edwards]]></dc:creator>
            <pubDate>Fri, 02 Dec 2016 17:26:26 GMT</pubDate>
            <atom:updated>2016-12-02T17:26:26.122Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Spi4GWzGyq--Mtf9oTTLow.jpeg" /></figure><h3>A system to address the CTO’s dilemma</h3><p>Throughout my entrepreneurial career I’ve more often than not been responsible for CTO duties even if I was the CEO on paper. One of the most frequent dilemmas I faced in that role was deciding whether or not to solve a particular internal pain point with our own technology or whether we were better off just paying for relief.</p><p>At first glance it would seem a decision like this would really involve all the stakeholders in the venture. Gather everyone together, discuss the options and get consensus on what to do. In reality, I was typically the only one on the team equipped with the context and knowledge to make these decisions. I could ask my business partners but, being mostly designers or those from a sales/marketing background, the question would immediately come back to me.</p><p>After encountering this situation a dozen or so times, I decided it was time to come up with some kind of repeatable method or system for making these decisions. The questions below are the same that I now ask myself any time I encounter the build vs. buy dilemma. Keep a tally of your affirmative responses and we’ll use that total in the end.</p><h4>1. Does this enable or implement a core part of the user experience?</h4><p>Things that the user sees or touches in the course of their interactions with your company or product become a part of your brand. While there are certainly exceptions to the rule, I generally believe that anything relating to your brand or brand perception are things that should be under your control.</p><h4>2. Is this solution part of your core differentiator or offering?</h4><p>I firmly believe it’s never a good idea to outsource your core offering or differentiator. Nobody understands your business as well as you do.</p><p>If your core offering is streamlined enterprise messaging, do you want to power your messaging experience with some generic and off the shelf messaging service? It may be tempting since there are so many quick back-end solutions to this challenge. Unfortunately you’d be stuck with a piece of technology at your core that you can’t customize to build differentiation from every other solution on the market.</p><h4>3. Is the time horizon to build less than 2 months?</h4><p>Somewhat arbitrary, I know, but my threshold of 2 months is based on the idea that I believe most concrete problems should be solvable* in no more than three 2-week sprints.</p><p><em>*solvable in the sense that the pain is alleviated</em></p><p>Time is precious in the world of startups. A month is already a long time. Don’t embark on building some custom solution that is going to take 6–9 months. You’ll be dead by then.</p><h4>4. Is the cost to buy more than 1 month of payroll?</h4><p>If there is a recurring charge involved, then annualize the expense for the purposes of answering the question.</p><p>Adjust to meet your threshold. If your team is still on a sweat-equity basis then anything is going to feel painfully expensive but you should pick a number that works within the budget.</p><p>On a related note, many SaaS/IaaS providers offer special startup discounts and/or credits to qualifying companies. This may significantly influence the build vs. buy decision if the long-term costs still work out.</p><h4>5. Is it a benefit more than a burden to maintain an in-house solution over the long haul?</h4><p>Many of my decisions really boil down to this: if I were to build a solution in-house, is this really something I want to be maintaining for the next 3–5 years? Is there a benefit to us having full control over the solution? Will we need to customize and adapt over time?</p><p>Or is this going to just turn into a huge pain of its own?</p><p>Let’s review the tally. To how many questions did you respond with a firm yes?</p><p>My rule is thumb is to build only if the tally came out to 3 or more. Any less and you’re generally better off paying for a solution and focusing your energy elsewhere.</p><p>What’s your decision process? Any questions you would add to this list? I would love to hear your responses below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b398cc4219f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apple v Theranos: avoiding death by your own Reality Distortion Field]]></title>
            <link>https://medium.com/@DerekBEdwards/apple-v-theranos-avoiding-death-by-your-own-reality-distortion-field-8d5e59417d13?source=rss-847a2937e155------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d5e59417d13</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Derek Edwards]]></dc:creator>
            <pubDate>Thu, 01 Dec 2016 18:55:47 GMT</pubDate>
            <atom:updated>2016-12-01T18:55:47.793Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p0dU9R_HZTwHOMX5B4WQXg.jpeg" /></figure><h3>Carefully crafted hype can be a powerful thing.</h3><p>Steve Jobs is perhaps the most prolific example of successfully wielding the Reality Distortion Field. In fact, the effect of this psychological manipulation didn’t even really have a name until the early 1980’s.</p><p>Coined by Bud Tribble, a member of the original Macintosh design team, the term referred to Jobs’ ability to use a combination of charisma and hype to convince himself and everyone around him to believe in things bordering on the impossible. It was used successfully for just about every aspect of the business — from motivating Apple’s designers and engineers to deliver on extremely short time lines to building a kind of buzz around product launches never before seen in history.</p><blockquote>“The reality distortion field was a confounding melange of a charismatic rhetorical style, an indomitable will, and an eagerness to bend any fact to fit the purpose at hand. If one line of argument failed to persuade, he would deftly switch to another. Sometimes, he would throw you off balance by suddenly adopting your position as his own, without acknowledging that he ever thought differently. Amazingly, the reality distortion field seemed to be effective even if you were acutely aware of it, although the effects would fade after Steve departed.” — Andy Hertzfeld</blockquote><p>Some may argue that Apple has lost its touch and that the Reality Distortion Field has been fading since the loss of Jobs. I’m among them. The launches of the last couple years in particular have been a mix of the boring with the downright disappointing. Furthermore, the quality that has typically been attributed to Apple products — and used to justify Apple price points — seems to be slipping.</p><p>Nonetheless, it’s hard to dispute that Apple and Jobs were very skilled and successful manipulators of perception for a long stretch of time. The effects of this manipulation still persist today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iG1YEWd4EImMmYiBaR63jw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*ke6G8MdsAq9N7Emh13jCQw.jpeg" /></figure><p>If Apple represents the most successful application of the Reality Distortion Field, Theranos represents the most public example of what can go wrong.</p><p>Elizabeth Holmes started Theranos in 2003 at the age of 19. Most of the early years of the company were out of the public eye. By the time Theranos started receiving coverage in mid-2013, Holmes had already successfully convinced investors to put over $100 million into the company and she was closing a deal with Walgreens to deploy testing centers across more than 40 locations.</p><p>Although it wasn’t until later that questions were raised about the legitimacy of these tests or the reliability of the underlying technology, it still begs the question of how Holmes managed to do all of this with seemingly no substance behind all of Theranos’ claims.</p><p>To me it’s clear that Holmes was a skilled operator of the Reality Distortion Field. She carefully crafted hype around the premise of addressing the pain surrounding traditional blood tests, used that to secure substantial funding, used the RDF to convince internal people to try to do the impossible, built a brand and packaged it nicely to secure a partnership with one of the largest drug store chains.</p><p>She even went so far as to adopt an image that strongly resembled Jobs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*EIY8FNJz0dbTXHVqKFjoNw.jpeg" /></figure><p>Many want to condemn Holmes as an example of the greed and everything else that is wrong with Silicon Valley. While there is no question that a lot of bad decisions and bad deals were made in the course of operating Theranos, I want to pose a question: was she fully aware of what she was doing? Or did she distort her own reality so much that she believed it?</p><blockquote>Did she distort her own reality so much that she believed it?</blockquote><p>Back in 2012, I started a company called Acclaimd with a couple co-founders. Our original premise was nothing too ground-breaking but at the same time addressed a common source of frustration for companies — recruiting new talent.</p><p>We collected some initial feedback from potential users that seemed to indicate an interest in using our platform. We used that feedback in conjunction with some branding and carefully crafted hype to raise initial capital from a group of local investors.</p><p>A few months later we had a prototype of the platform that was ready to put in the hands of some users. We went on-site, did hands-on training with employees within these companies and then we waited.</p><p>Two weeks went by. Not a single one of those “early adopters” used the platform.</p><p>When we followed up, the responses ranged from “oh, we didn’t realize our other employees would have to be in the system” to “we need this to integrate with our enterprise HR software to use it.”</p><p>We should have realized that this was a big red flag. We misinterpreted something earlier on or misread the level of interest. Instead, we went down the road of addressing this feedback.</p><blockquote>We should have realized that this was a big red flag.</blockquote><p>Several months and most of our funding later, we abandoned our original premise to build something else entirely. We had allowed our own hype to blind us not just once but twice.</p><p>Had we objectively evaluated the initial validation we got before we raised any capital or built a product, we would have reached the conclusion that our original premise was flawed. We would have saved ourselves over a year of wasted time. We would have preserved substantial capital.</p><p>None of us may be as skilled with the Reality Distortion Field as Jobs or Holmes but all of us are experiencing it right this moment and each of us have our own stories of where it blinded us from the truth.</p><p>To be successful, it is absolutely essential as entrepreneurs to not only be able to carefully craft hype and project a certain kind of charisma but also maintain our ability to see the truth through the noise. The trouble is, if we can’t trust our own perception of things, how do we see reality?</p><p>My answer is pretty simple: metrics and measurements. Start setting metrics and goals as early as possible and use whatever free/inexpensive tools are available to collect that data as often as possible.</p><p>Numbers don’t lie.</p><p>There is certainly a lesson to be learned from Theranos but I don’t think it has anything to do with the perceived greed or lies within Silicon Valley.</p><p>I see Theranos as more of an extreme cautionary tale of what happens when we can’t see the truth through our own reality distortion field.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d5e59417d13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Sweat the Small Stuff]]></title>
            <link>https://medium.com/@DerekBEdwards/dont-sweat-the-small-stuff-f6f1893641f2?source=rss-847a2937e155------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6f1893641f2</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Derek Edwards]]></dc:creator>
            <pubDate>Wed, 30 Nov 2016 17:23:36 GMT</pubDate>
            <atom:updated>2016-11-30T17:23:36.432Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mahRWW9F3JnIGHv9LNxV6g.jpeg" /><figcaption>Courtesy <a href="https://www.flickr.com/photos/nictalopen/">https://www.flickr.com/photos/nictalopen/</a></figcaption></figure><p>It’s all too easy to do. I fell into the trap just as I was starting to write this post. It wastes time, drains mental energy and makes me less effective than I could be.</p><p>I burned 10 minutes trying to find a clever header image. But just yesterday it was 20 minutes researching self-deprecating domain names to use for my publication. I’m sure it will be something tomorrow.</p><p>The problem, of course, is getting stuck in the details. Analysis paralysis. Over-engineering.</p><p>While the details become more important as you grow out of the garage and into fancy new digs, they are a tempting distraction when you aren’t even out of the starting gate.</p><p>Don’t let it happen to you.</p><p>What’s the single most important action you can be taking right this second?</p><p>You shouldn’t even have to think about it. If it’s not something that is directly and immediately driving or enabling growth/revenue, it can wait.</p><p>Of course, by definition, the single most important action will change over time. Those details that were irrelevant six months ago will inevitably become a pain point later on. That’s okay and expected.</p><p>Some might argue that it’s better to be proactive and plan ahead for problems that will crop up 3, 6 or 12 months from now. I strongly disagree*.</p><p>Do what will take you from $0 to $1000/mo in the immediate time frame. And then do what will take you from $1000/mo to $2500/mo. Ditto for $2500/mo to $10000/mo. Rinse and repeat.</p><p>Call it Lean Startup or just keeping it simple. This is as much a reminder to myself as it is to everyone else out there starting from $0.</p><p><em>*There are some niche industries where you have no choice due to regulatory issues and the like, but I still argue for this approach from a broad perspective.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6f1893641f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Entrepreneurial Struggle to Find Passion]]></title>
            <link>https://medium.com/@DerekBEdwards/my-struggle-3530fe568d38?source=rss-847a2937e155------2</link>
            <guid isPermaLink="false">https://medium.com/p/3530fe568d38</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Derek Edwards]]></dc:creator>
            <pubDate>Tue, 29 Nov 2016 18:05:55 GMT</pubDate>
            <atom:updated>2016-11-29T18:13:22.477Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jG2PABHACFQRx0qubDICTA.png" /><figcaption>courtesy <a href="http://somebodyslime.deviantart.com/">http://somebodyslime.deviantart.com/</a></figcaption></figure><p>November 22nd was my last day at CoachLogix. After a 3-year hiatus, I’m an independent, solo entrepreneur again.</p><p>I’m very proud of what my team and I accomplished. We built a company and a product serving Walmart, Linkedin and many other of the world’s largest and most successful brands. We did so with very limited resources and developed some very powerful patterns and best practices along the way. I’m confident the work I started will continue to positively impact the best and brightest leaders within these organizations in the capable hands of my friends and colleagues.</p><p>Those who have followed my journey know that the decision wasn’t easy. Since becoming a full-time entrepreneur almost a decade ago, I have constantly struggled with fighting my natural ADD tendencies where I always want to go work on something shiny and new instead of taking my existing work to completion. I was worried that was happening all over again.</p><p>In the end, it became clear that I was having trouble reconciling my passions with my day to day work. And if there’s one thing you absolutely need to have as an entrepreneur, it’s passion. Without it, the challenges and the grind will wear you down until you’re nothing but a shell of your former self (more on that another time.)</p><p><strong>What’s next?</strong></p><p>Before anything else, I’m focusing on getting back into a healthy, organized schedule again. I will be exercising, eating healthy and writing on a daily basis to chronicle my journeys and relay what I’ve learned.</p><p>After that, I will be dedicating serious effort to passion projects (more on those another time) and, in the time that remains, taking on various consulting projects as a CEO/CTO for hire.</p><p>I look forward to bringing you all along for the road ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3530fe568d38" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>