<?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 Michael Boufford on Medium]]></title>
        <description><![CDATA[Stories by Michael Boufford on Medium]]></description>
        <link>https://medium.com/@mboufford?source=rss-5d2837e1bffb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yZ5UQrZp0sJIMaPe.png</url>
            <title>Stories by Michael Boufford on Medium</title>
            <link>https://medium.com/@mboufford?source=rss-5d2837e1bffb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:30:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mboufford/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[Keys to Effective Feedback]]></title>
            <link>https://medium.com/@mboufford/keys-to-effective-feedback-529ca90dd65f?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/529ca90dd65f</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[emotional-intelligence]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Wed, 08 Nov 2017 18:54:49 GMT</pubDate>
            <atom:updated>2017-11-10T23:01:54.321Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most challenging aspects of leadership is the requirement that we deliver feedback to others. Sometimes it goes well, sometimes we walk away in frustration wondering what went wrong.</p><p>When the feedback that we deliver is received poorly, most of the time, it boils down to one thing that is well within our control: we haven’t prepared adequately for the conversation. By coming prepared to the conversation, we demonstrate respect by communicating care and intentionality to the recipient.</p><p>To help me prepare for difficult conversations, I’ve developed a list of questions that I use to reason about the feedback that I’m planning to provide. The questions below serve as a rough framework that I hope will be helpful to others:</p><p><strong>#1 — Is the feedback that I am about to provide true?</strong></p><p>When we receive feedback that feels out of sync with our view of reality, our natural inclination is to try to disprove the view and react defensively. To avoid this pitfall, I try to reason about the nature of the ‘truth’ that I intend to convey before the conversation: am I expressing a subjective view (e.g., “your presentation was too long”), or a fact (e.g., “you haven’t hit your sales quota”)? Do I have specific examples or other objective criteria to support the veracity of my claim?</p><p>Whenever objective criteria are present, doing the extra legwork to collect a few data points before the meeting pays off by providing a fact-based support structure for the discussion. If there are no objective criteria other than my own subjective assessment, it is important to take care to present the feedback for what it is: a perception, not an objective truth. Being mindful of how we present our subjective views and providing evidence to support those views decreases the likelihood of a defensive reaction on the part of the recipient.</p><p><strong>#2 — How can I make this feedback actionable/constructive?</strong></p><p>When we only hear criticism without a path to improve, feedback can feel assaulting. Most of the time we provide feedback because we would like to see a change take place. We are making an ask of the recipient that they do something differently. Sometimes we come to the conversation armed with ideas around how to improve, other times only the problem itself is obvious, and the solution requires some brainstorming to discover.</p><p>It can feel lonely, frustrating, and confusing to hear negative feedback without a clear path to improve. Coming to the conversation armed with both actionable ideas and an attitude of collective ownership in discovering a solution ensures that the person on the receiving end feels supported. Failing to communicate or discover an actionable path forward invariably leaves the recipient feeling that the feedback was unhelpful.</p><p><strong>#3 — How can I reframe this from an ‘identity’ issue to a ‘behavior’ issue?</strong></p><p>The worst type of feedback takes the form of a claim against the identity of the recipient such as ‘you have bad intuitions.’ This type of feedback leaves no room for improvement, since it is a claim about who the person is, not about the behaviors that we are hoping to change. Underneath every identity-based assessment that we make are a set of specific behaviors that can be isolated and addressed individually, but it does require some extra rigor to think through what those behaviors are, and to come up with solutions for how we might address them.</p><p>I find it helpful to ask myself the question “what about this person’s behaviors make me identify them in this way?” This question helps me to deconstruct and reason about the discrete behaviors that have caused me to think of them in this way. Once these behaviors have been identified, I have a fighting chance of developing actionable and constructive next steps to drive improvement.</p><p><strong>#4 — What do they believe to be true that makes this behavior make sense?</strong></p><p>Feedback is most often necessary when we identify some behavior that falls outside of our expectations for what we think <em>should</em> be happening. We provide feedback to communicate that this gap exists, and to try to find ways to close that gap. Where a belief system drives the behavior, it’s important to identify the space between our own beliefs and those of the person on the other side of the table. Working to bridge the gap in how we each think about the world is often far more effective than working to alter the individual behaviors that we’re unhappy with.</p><p>Let’s take a generalizable example: as a manager, I may have the belief that efficiency is more important than quality; meanwhile, a team member may believe that quality is more important than efficiency. The behaviors which fall out of each belief system will differ dramatically. Neither belief system is strictly right or wrong, so having an exploratory conversation about why we each believe what we believe can be helpful to close the gap.</p><p>At times it may be that the manager needs to simply clarify what is important to the business, and ask that the employee update their mental model unilaterally. But most of the time, it is beneficial for the manager to take the opportunity to learn why the employee believes what they believe: there may be an important organizational need that the team member is trying to address that the manager lacks visibility into. Asking questions to understand why the employee believes what they believe is always a helpful starting point in attempting to reset behaviors driven by a differing belief system.</p><p><strong>Preparation is everything</strong></p><p>Preparation for an emotionally loaded conversation is a sign of respect, it demonstrates care and intentionality, and demonstrates to the recipient that your feedback should be taken seriously. By spending time in preparation, your arguments will be better supported and more coherent, the emotional weight of your words will be better considered, and the outcomes from the conversation will be more actionable and effective.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=529ca90dd65f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bugs in Trust]]></title>
            <link>https://medium.com/hackernoon/bugs-in-trust-55bce19d9ad5?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/55bce19d9ad5</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Fri, 20 Oct 2017 15:21:01 GMT</pubDate>
            <atom:updated>2017-10-20T15:21:01.567Z</atom:updated>
            <content:encoded><![CDATA[<p>While some software teams have instituted expensive zero-tolerance policies, most teams try to balance the priority of each bug against a mountain of other worthwhile demands. Both absolutist and pragmatist policies can be perfectly appropriate depending upon the nature of the software–for instance, I’d like the software that keeps my plane aloft to work 100% of the time thank you very much. But, if a gif of a panda rolling around in the grass pauses half-way through, it’s not the end of the world. For “system of record” software like Greenhouse, we’ve found our own tolerance level sits closer to “keep the plane in the air” than gif-stuttering consumer site, but we don’t bring everything to a halt if a button is 3px left of where it should be in IE10.</p><p>To bring clarity to how we prioritize our work, we have developed a new term that has found its way into our day-to-day conversations at Greenhouse, so I am writing this short article to share this term with the broader community. While we do make trade-offs in prioritizing certain issues, we have recently instituted a zero-tolerance policy for what we call <em>trust bugs</em>. Let’s define the term.</p><p><em>Trust bugs</em> are distinct from other bugs, in that they cause the user to either:</p><ol><li>not believe that the data as presented are correct, <em>or</em></li><li>not believe that an action taken will reliably occur</li></ol><p>Bugs in this category are distinct because they don’t just cause frustration, they harm the relationship between a company and its customer. <em>Trust bugs</em> create skepticism every time a button is pressed, or a list appears, and this eventually leads to customer churn.</p><p>Trust is much harder earned than it is lost, so don’t let <em>trust bugs</em> sit in the backlog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55bce19d9ad5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/bugs-in-trust-55bce19d9ad5">Bugs in Trust</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Philosopher’s Approach to Building Great Teams]]></title>
            <link>https://medium.com/in-the-weeds/a-philosophers-approach-to-building-great-teams-80f0dde5948?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/80f0dde5948</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Fri, 07 Jul 2017 21:41:57 GMT</pubDate>
            <atom:updated>2017-07-07T21:41:57.692Z</atom:updated>
            <content:encoded><![CDATA[<p>In college, I was exposed to a philosophical construct called the “Original Position” created by the 20th-century philosopher John Rawls. The Original Position is a thought exercise, whereby we assume a blank-slate society and are tasked with developing a system of rules, values, and norms. Our new society could reward athleticism, productivity, or kindness, it could consolidate wealth with a small number of people, distribute the wealth evenly, or by whatever we consider meritorious. No matter the rules we devise, the thought exercise further stipulates that we wear a “veil of ignorance”. By pure luck or misfortune each of us could find ourselves representative of any one of society’s stations; low caste or high, naturally athletic or weak, beautiful or ugly, slow, average, or eminently intellectual. The exercise forces you to think about the justness and fairness of the rules we create in a society.</p><p>As the first engineer at Greenhouse, and later the head of the engineering organization, I was given a blank slate: a team which did not yet exist.</p><p>It struck me that I had found myself in a situation not unlike Rawls’ Original Position. I would be creating a new society. So, I started the thought exercise. What does a fair compensation system look like? What behaviors should be valued? What behaviors are unacceptable? What shape will my new society take?</p><p>A few weeks ago, I was given the opportunity to speak at the Firstmark Capital CTO Summit, and shared a vision of the Utopian work environment for software engineers that I’d come up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*ZN9GTQD-02u4Y3O0.jpg" /></figure><p>By no means comprehensive, this list of desires served as the foundation for how I would think about the rules, values, and norms that I would hope to cultivate in my new team as it grew from nothing to what is now a team of 60 engineers. The exercise helped me to be intentional in defining the core value system for the team I would build. Now, five years on, I am happy to report that this exercise has yielded a close approximation of the developer Utopia I’d imagined years before: a team of engaged, diligent, ever-improving, and pragmatic engineers who work everyday to make things better for our customers and for each other.</p><p>Starting from a blank slate, what shape will your society take?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80f0dde5948" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/a-philosophers-approach-to-building-great-teams-80f0dde5948">A Philosopher’s Approach to Building Great Teams</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting the most out of skip-level 1:1s]]></title>
            <link>https://medium.com/@mboufford/skip-level-1-1s-ffbbdd0056d3?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffbbdd0056d3</guid>
            <category><![CDATA[executive-coaching]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Wed, 21 Dec 2016 22:47:33 GMT</pubDate>
            <atom:updated>2016-12-23T14:04:33.359Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Problem: </strong><em>as a manager of managers it is hard to get enough visibility into your direct reports’ organizations to provide specific and actionable feedback.</em></p><p>You may now be a manager of managers, but your job is the same as it was as a first-level line manager: to make the organization that reports into you more effective through your support, decisions, and processes.</p><p>In my experience, the most useful forum for finding out the “why” and “how” behind what managers are doing has been via skip-level 1:1s. I have nearly sixty engineers on my team, but I still make sure to find time to meet with each person at least once per quarter. There are a number of benefits to doing this, but in this article I’m going to focus on one angle: finding out what’s going on inside of each manager’s team so I can offer specific and actionable feedback on how to improve. To jump straight to the meat and potatoes, below are a few of the questions that I ask individual contributors during skip-level 1:1s to that end:</p><p><em>Do you feel like you have a clear idea of what you’re doing well and where your areas of improvement are?</em></p><p><em>Do you feel like you are learning? Which skills are you focused on improving?</em></p><p><em>Do you feel like you have a good understanding of your career next steps and what it would take to get there?</em></p><p><em>Do you understand where the team is headed and how what you guys are doing affects customers and the company?</em></p><p><em>Do you feel like you get appropriate recognition when you do a great job?</em></p><p><em>Do you feel like you have the training &amp; resources to improve?</em></p><p><em>What do you think the rest of your team is most concerned about?</em></p><p><em>If you were running the team, what would be the first two or three things you would change?</em></p><p>Many of the managers of managers that I know try to take a shortcut by directly asking an employee “what do you think of your manager?” but fail to recognize the intensely uncomfortable position in which this places the employee. No one wants to be seen as undermining their manager by offering criticism to their manager’s manager. This line of questioning can make employees feel vulnerable to retaliation, and typically results in useless and sometimes apocryphal reviews. I avoid this type of unspecific question like the plague.</p><p>Each question I ask in a skip-level 1:1 is designed to provide me with answers about what type of activities are occurring (or not) within the team. When I ask a specific question such as “What professional development activities are you pursuing this quarter?” the employee either has a satisfying answer or they don’t. If they don’t, I just learned something that I can use to help the manager ensure each person on her team is receiving the appropriate level of support. The same goes for any of the questions I ask during skip-levels.</p><p>Sourcing this type of feedback directly from a manager’s team members removes much of my own subjectivity from the conversation, and provides me with actionable “inside the black box” results to work from. To some managers, having your manager talk to the people on your team might seem unnerving, but not only is this a great practice to ensure support for individual contributors, it’s also great for their managers! A common complaint among middle managers at many companies is that they don’t know where to improve. Properly leveraged skip-level 1:1s give you exactly the type of information that you need as a leader to provide meaningful support to the managers on your team.</p><p>The result? Managers feel like they’re getting better everyday and the employee feels heard, yielding both higher job satisfaction and improved results for the manager and the employee. As an executive leader, you still have the power to affect the quality of management at every level of your organization — but the first step is to make sure you are gathering enough information to do so constructively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffbbdd0056d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Distributed Denial of Customer Service]]></title>
            <link>https://medium.com/@mboufford/distributed-denial-of-customer-service-365a2a3d7483?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/365a2a3d7483</guid>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Mon, 26 Aug 2013 14:57:25 GMT</pubDate>
            <atom:updated>2013-08-26T18:59:45.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/699/0*0xELoF3Y3MFIwe5j.jpeg" /></figure><h4>On being helplessly suspended in the cloud.</h4><p>Nowadays, whenever my site goes down, along with it comes tumbling a significant segment of the consumer web. Yesterday, the Amazon US-East-1 region saw a major outage in their EBS infrastructure, which meant that Instagram, Reddit, Vine, and thousands of other sites went down hard. I don’t know about you, but I can live without sepia photo filters and cute pictures of panda bears for a couple of hours. What I can’t happily accept is that <em>my</em> site went down.</p><p>And every developer, company founder, and cloud infrastructure manager around the country felt the same frustration, at precisely the same moment. So what did we all do? <strong>We simultaneously emailed, called, and tweeted at our cloud providers</strong>—many of which are tragically helpless, as mere abstraction layers atop Amazon’s core infrastructure. My normally hyper-responsive <em>Web n.0</em> providers all of a sudden choked up, and all they could do was place me in a queue behind the other several thousand requests pouring into their inboxes—in a chorus we all screamed, “I don’t give a damn about those other sites, <em>my </em>site is down!”</p><p>On some level I felt bad for the poor people that had to respond to this deluge of frustration, but to be honest, I mostly just wanted them to fix my damn site.</p><p>As a community, we all stared blankly at minimalist status pages, impotently refreshing the screen every few seconds, praying for the red status indicator to flip back to green. After nearly two hours, I finally saw that green light saying we were back up—as did thousands of other helpless subscribers. We breathed a collective sigh of relief. We all sent emails around to our bosses and to our customers to tell them we were back, and we all came into the office today, uneasy about the lack of control that comes along with the nebulous abstraction that sits beneath our applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=365a2a3d7483" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I can plz has resume?]]></title>
            <link>https://medium.com/@mboufford/i-can-plz-has-resume-2b857af0a717?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b857af0a717</guid>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Sun, 11 Aug 2013 23:11:29 GMT</pubDate>
            <atom:updated>2013-08-11T23:11:29.727Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*G59SarXFdK7nv-We.jpeg" /></figure><h4>A how-to guide to writing awful recruiting emails, with real examples from my inbox.</h4><p><strong>Step 1. </strong>Border Control!</p><blockquote>Hi Michael,</blockquote><blockquote>Do you have a valid US work visa? Are you looking for a role as a Developer for Java with a company for one of the clients [sic]. If so, we should talk….</blockquote><p>We should definitely talk. But, quick question: will your company accept US citizenship in lieu of a work visa? Let me know, thanks. Ever since I was a little kid, I have dreamed of one day getting a job with <em>a company</em>, I hear they have been doing really amazing things in their space. Where do I apply?!?</p><p><strong>Step 2.</strong> Pretend to research the person you’re contacting.</p><blockquote>Based on your LinkedIn profile, I think you could be a great fit for this job. It is a full time job with an excellent company based in Tallahassee Florida and requires 7+ years experience in Python. Rates competitive for the right candidate. No relo. Please call me at (555) 555-5555 as soon as you can if you are interested.</blockquote><p>Well, call me flattered. Even though the job requires 7+ years in a language that I’ve barely used, and happens to be located 1,000 miles from where I now live, the recruiter was still kind enough to think of me. That is so nice. I will definitely give it some serious thought.</p><p><strong>Step 3. </strong>Only tell me the requirements.</p><blockquote>5+ years in large-scale product development<br>2+ years leading a team of back-end Engineers and front-end Engineers<br>3+ years working in an enterprise java stack<br>Expert in back-end (java/python/etc) development or front-end (html/js/css)</blockquote><blockquote>Let me know if interested.</blockquote><p>Finally. A gig that requires either several years of Java or HTML or whatever. Please, don’t bother mentioning anything about the company, its culture, why you think I would be a good fit, or why I should spend my valuable time speaking to you—none of that really matters if I don’t meet the requirements does it!</p><p><strong>Step 4. </strong>Advertise a salary that is WAY higher than what’s being offered.</p><blockquote>Well-known hedge fund seeks an exceptional Java developer, comp to $1M+</blockquote><p>Yes please! I would like all of the money, thank you. How much will they actually pay for someone with no finance experience? $100k? Wait, that means I will not be able to buy a mega-yacht and sleep on a bed of caviar and truffles. Never mind.</p><p><strong>Step 5. </strong>Have absolutely no idea what any of those acronyms mean.</p><blockquote>We want it to be fast, so we are building it in git instead of php.</blockquote><p><em>(source: </em><a href="https://twitter.com/molovo/status/360346792602259456/photo/1"><em>@molovo</em></a><em>)</em></p><p>You mean I could stop using a programming language entirely and build an app inside of a source-code repository protocol? What is this black magic you speak of. Unless git has just introduced “git if”, “git while”, “git declare:variable -name foobar=1,” and “git func” into its command language, I think the company’s efforts to replace PHP with git may be an uphill battle. I for one, am always looking for a challenge.</p><p>——</p><p>But please, don’t let this monochromatic picture of incompetence paint an apocryphal or negative picture of recruiters in general: this is truly a sampling of the worst of the worst.</p><p>One of the best jobs I’ve ever had came via a recruiter, who I felt was my advocate as much as he was the company’s. There are thousands of thoughtful, smart, careful, and knowledgeable recruiters out there responsible for building just about every great organization in the world. If you like having an iPhone, searching on Google, or saving the planet on Change.org, you have a recruiter to thank for helping to put the right team in place to get the job done.</p><p>My next blog post will also be drawn from the deep stack of real recruiting emails that I have received over the years, but instead, I will focus on the other end of the spectrum. You will see how the best of the best recruit, and no surprise, many of those recruiters work for the world’s best brands. Until next week.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b857af0a717" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Respond to bugs like a boss]]></title>
            <link>https://medium.com/@mboufford/respond-to-bugs-like-a-boss-7ad1ea328097?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ad1ea328097</guid>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Sat, 03 Aug 2013 04:08:52 GMT</pubDate>
            <atom:updated>2013-08-03T17:40:55.137Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*g7f49vJNudPFLw4r.jpeg" /></figure><h4>TL;DR: install Rollbar, win devoted customers.</h4><p>The day had started out well enough: the coffee pot was full upon arrival, the sun was shining, and I had just deployed our latest and greatest to prod. <strong>Then it happened</strong>: a confidence mangling collision between an obscure software bug and one of our biggest customers. Ouch.</p><p>Within seconds the entire dev team saw the exception hit their inboxes. In the email we had a stack trace, request params, the user’s email address, and all of the HTTP headers. We had everything we needed to turn this devastating failure into a win—but, we had to act fast. We immediately got to work: hotfix branch, bug fix, push to prod, and an email to the customer with something along the lines of:</p><p><em>Hi Jon,</em></p><p><em>We noticed that you ran into an issue while trying to switch between views on your dashboard. We’ve fixed the bug, feel free to jump back in and try again.</em></p><p><em>We really appreciate your patience, and please let us know if there is anything more we can do to help.</em></p><p><em>-Mike</em></p><p>This entire process took about <strong>8 minutes</strong>. We didn’t waste time SSH’ing to EC2, we didn’t need to scan the logs, we didn’t have to grep on the request ID to figure out the user ID, then search the database to find the user’s email address. Most importantly, we didn’t have to wait for the customer to tell us something had gone awry. We saw it immediately, fixed it in a matter of minutes, and received the following email in response from our user:</p><p><em>WOW! You guys are ON IT!<br>Sincerely,<br>Happy Customer</em></p><p>As a user of something like twenty-thousand websites over the past fifteen years, I can tell you that I have received customer service like this precisely zero times, ever. We built more confidence with our rapid response and personal touch than we ever could have if the view had just worked the way it was supposed to.</p><p>Although we are never happy to report that our attempts at building bug-free software have come up short, try as we might, the occasional bug is unavoidable—I will spare you quotations from Djikstra, Knuth, Voltaire, and Homer Simpson supporting this point, but it’s true. Besides, the love that we’ve received from customers by handling live bugs this way has been awesome:</p><p><em>“Seriously?!? How did you even know I had an issue?”</em></p><p><em>“Love the support!”</em></p><p><em>“OMG that’s great!”</em></p><p>We are frickin’ rockin’ it on customer service. Go us!</p><p>And… while I would love it if our team could hog all the credit for this awesome workflow, the truth is, we’ve had a secret weapon: <a href="http://www.rollbar.com/">Rollbar</a>.</p><p>For less than a bento box per month we have all of the information that we need to rapidly diagnose and discover issues, prioritize fixes, and ensure that our software quality stays high. Knowing that we have a reliable and immediate feedback loop lets us spend less time obsessing over 100% test coverage and more time building features that our customers actually care about.</p><p>Nowadays, we release new features at least once a week and rarely have a significant bug that survives more than a few minutes.</p><p>Errors are a fact of life: they are part of a beautiful feedback loop that teaches us how to be better, and we get better a heck of a lot faster when that feedback loop is in realtime.</p><p>P.S. I do not work for Rollbar, I pay for Rollbar, and so should you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ad1ea328097" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surviving that insufferable button]]></title>
            <link>https://medium.com/@mboufford/surviving-that-insufferable-button-da8a29717157?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/da8a29717157</guid>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Fri, 05 Jul 2013 19:43:27 GMT</pubDate>
            <atom:updated>2013-07-07T05:48:10.942Z</atom:updated>
            <content:encoded><![CDATA[<p>Adrenaline coursing through my veins. Passions rising sharply. Digging in for the battle ahead. “How could you possibly think that button should go there?!! It’s just not intuitive!”</p><p>As entrepreneurs and early start-up employees, we have all taken a substantial risk of some sort. At times, the success or failure of our companies &amp; products can feel less like external facets of our long and varied lives, and more like proxies for our immediate survival. The eons of experience expressed in our genes ensure that <em>we rationally fear the prospect of being lead down the wrong path</em>—a bad turn on a mountain pass during the winter could have easily meant the difference between life and death. Unfortunately, the wrong tactical placement of a homepage button can trigger a similar physiological response.</p><p>At the early stages of my current venture, I fought tooth and nail for my own intuitions surrounding product decisions. I subconsciously felt as if each decision, small or large, would make or break our company, and at a more base level, would make or break me. Only after careful inspection did I come to the following realizations: (1) my body was overreacting to the real consequences of minor product decisions; (2) my ability to collaborate effectively was suffering as a result; and (3) most of us are burdened with the same maladaptive tendencies.</p><p>On my path towards changing this response pattern, I found it helpful to ask myself the following questions:</p><ol><li>“Is it true that my intuitions are more likely to be right than those of the other very smart people on my team?”</li><li>On a case-by-case basis, “what are the consequences of following through with the proposed solution?”</li></ol><p>Not surprisingly, the answer to the first question was a resounding “no.” My teammates and founders were <em>at least</em> as smart, conscientious, and thoughtful as I am—that’s why I chose to work with them in the first place. The moment I consciously recognized that fact I felt a tremendous sense of relief: <strong>it’s not all on me! </strong>There is no force which better calms our survival instincts than knowing that you can trust your team to make great decisions.</p><p>With regard to the real consequences of small product decisions: let’s be honest, 95% of the time a single choice isn’t going to move the needle one way or the other, and—at least with web products—you can always change it later.</p><p>Recognizing these facts in a conscious way can help us to interrupt the survival instinct where and when it is surfaced inappropriately. If a company is going to succeed or fail, it is not going to be because of a misplaced button.</p><p><em>P.S. The misplaced button is merely a fictional character in this story, our button placement is actually pretty awesome ;)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da8a29717157" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If Heroku fixed these problems, I’d never leave…]]></title>
            <link>https://medium.com/@mboufford/if-heroku-fixed-these-problems-id-never-leave-13bc7f8ac26b?source=rss-5d2837e1bffb------2</link>
            <guid isPermaLink="false">https://medium.com/p/13bc7f8ac26b</guid>
            <dc:creator><![CDATA[Michael Boufford]]></dc:creator>
            <pubDate>Sun, 30 Jun 2013 01:39:35 GMT</pubDate>
            <atom:updated>2013-06-30T01:47:01.364Z</atom:updated>
            <content:encoded><![CDATA[<ol><li><strong>Transparency: tell me how everything works</strong>. I don’t need to read your code (though I would like to), but I do want to know the nitty gritty details of how your “dyno” cycling, deployment,routing, time-sharing, and monitoring strategies work. It shouldn’t require a RapGenius to figure out how traffic is directed.</li><li><strong>Your parentalism is great, to a point. </strong>Could I make better decisions about how to manage cloud infrastructure, on my own, than the very smart people at Heroku? <strong><em>No</em></strong>. However, the fact that I can’t easily partition my traffic for branch testing, deploy with zero downtime (or slowdown), or make my own load balancing decisions means that I feel unempowered as a customer.</li><li><strong>Help me answer my bosses.</strong> “I was in a demo with a huge client today, and the whole app randomly just hung, what went wrong?” I am sick and tired of saying “um, I dunno, Heroku blargeddyfargnerg??”<br>-<br>Sometimes I’ve written some stupidly slow code, or forgotten an index, or I’m wandering through a maze of hyper-normalized database tables to get to what I need; but, when I do something stupid, the performance is usually <em>consistently</em> bad, and I’m able to do something about it. On Heroku, the same request replayed under roughly the same load conditions can vary by a factor of 50, with no clear explanation in the logs. This comes back to my first point, what the hell is taking so long!?<br>-<br>Success in a services business is a recursive call to a function named <em>makeMyBossLookGood()</em>. I am your customer, so on some level, I am 1/nth your boss. I want to stay your customer, you guys are great, but sometimes you fail to make the initial <em>makeMyBossLookGood() </em>call, and it prevents me from making the subsequent call, and it prevents my boss from making the call for our customers, and the whole thing breaks down, and all I can do is blindly blame you for failing to call <em>makeMyBossLookGood()</em>.</li></ol><p>Make me look good. That’s all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13bc7f8ac26b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>