<?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 Charles Brian Quinn on Medium]]></title>
        <description><![CDATA[Stories by Charles Brian Quinn on Medium]]></description>
        <link>https://medium.com/@seebq?source=rss-d3c64ad18e14------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_PuCdanwFi08OEYM.jpeg</url>
            <title>Stories by Charles Brian Quinn on Medium</title>
            <link>https://medium.com/@seebq?source=rss-d3c64ad18e14------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:44:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@seebq/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[The best job I ever had]]></title>
            <link>https://medium.com/@seebq/the-best-job-i-ever-had-1066dac99a87?source=rss-d3c64ad18e14------2</link>
            <guid isPermaLink="false">https://medium.com/p/1066dac99a87</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Charles Brian Quinn]]></dc:creator>
            <pubDate>Thu, 19 Jul 2018 15:35:04 GMT</pubDate>
            <atom:updated>2018-07-19T15:37:00.559Z</atom:updated>
            <content:encoded><![CDATA[<p>The best job I ever had is hard to explain in a nutshell. I’ll try, though.</p><p>A good friend and I tried to startup a company around a big idea we had. We convinced a friend of ours who had a successful, growing company to hire me and pay me a decent salary (I’ll disclose: it was 50k a year with benefits) to work 50% of my time on a special project for his company. The other 50% of my time, well, that was free for us to work on the startup. In consideration for that 50% “free time”, among other things, we considered it an early angel investment in our startup and wrote up some quick terms.</p><p>I loved this job. And it led me to create a very successful company, but not the one you’re thinking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*lCsPOOpNmWDMcXjCwZ7Ofg.jpeg" /><figcaption>Jetsetting by <a href="https://www.flickr.com/photos/seebq/8441591144/in/album-72157632675972589/">seebq</a> on Flickr. 2007!</figcaption></figure><p>So let me ask you something first, a test, if you will. Which project has a greater chance of success?</p><p>Project 1: Unlimited budget. Unlimited scope. Unlimited time, at least a year or more. Big market. Stakeholders give free reign.</p><p>Project 2: Extremely limited budget. Very limited scope. Very specific timeline (3 months). Small amount of customers, in the same building. Stakeholders, too and highly involved: critical and skeptical.</p><p>Which one is more successful?</p><p>Project 2, hands down. Every time.</p><p>Project 1 was the startup. Suddenly, we had unlimited time to figure out an even bigger idea for an even bigger problem to solve in our early startup stage. We had salary for me (unlimited runway)! And lots of time now! So the project expanded. With no customers, we could engage in all sorts of “customer discovery” and fun stuff to setup things The Right Way. Lots of setup. Lots of discussion. I even met with a banker to make sure it was the “right relationship.” This startup failed, for a number of reasons (big idea, too soon), but my main theory I realized later was that it lacked constraints and other factors that constraints breed.</p><p>Project 2 was the special project for the company. The need was very specific: a team of 20 field service agents, with a specific budget for the technology to enable them to do their job better: faster, quicker, more efficient. Had to be done in 3 months for the initial roll out, since that was the pilot they had sold (and I had to get back to the startup, of course). The customers were so close, in fact, my office was right outside the warehouse door, where the pallets came in for the first part of the problem we were solving. I even moved my laptop and did some of my best work with it sitting on top of the pallet, turning the screen around to the main users (customers) after watching them fumble through it, and saying to myself: “I’ll have to change that, and that.” And then coding up a change while standing there (my first standing desk), and grabbing the users again, with my laptop still on the pallet, and us both saying: “OK, try again now. Aha, much better!”</p><p>I should add that because the stakeholders of the special project were critical and highly involved. The COO was the one who hired us and made the deal, and his CEO was super skeptical that the whole thing wouldn’t work and made for some awkward initial encounters — now we’re great friends. The limitations and skeptical nature led the project (and me) to consistently prove that I was creating value. And in my head, the sooner I created this super valuable thing, the sooner I could get back to the startup. A funny thing happened, in that I got super excited about the special project, and found myself working on it, more than the 50% allotted for the startup. And learned a ton. Not just on the project, but to be fair, our investor wanted both to succeed, so I learned a ton about forming (and running) a successful company.</p><p>Project 2 was wildly successful. That company went on to be sold for lots of money, in part due to the unique software and technology we built together.</p><p>The startup (Project 1) with unlimited runway failed. But, after realizing that constraints make for better software, I started a software company that took that ethos to heart: constraints make better software. That company still exists today, and the formation stories of how <a href="https://www.bignerdranch.com/">Big Nerd Ranch</a> builds great software (and teaches others to do it) is for another time.</p><p>I wish there was yet another company that existed today that would help entrepreneurial minded startup founders connect with businesses that need software, and in exchange for hiring them on to work on projects (for 50% time), they get equity and the chance to start something up. A win-win situation.</p><p>If you’re interested in this from either side (a startup or a company that wants to hire an entrepreneurial person), write me. I’m always looking for customers to solve problems with real constraints.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1066dac99a87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we did a Customer Pilot first instead of a Public Launch]]></title>
            <link>https://medium.com/@seebq/why-we-did-a-customer-pilot-first-instead-of-a-public-launch-83e3d9fa8808?source=rss-d3c64ad18e14------2</link>
            <guid isPermaLink="false">https://medium.com/p/83e3d9fa8808</guid>
            <category><![CDATA[bignerdranch]]></category>
            <category><![CDATA[product-launch]]></category>
            <category><![CDATA[behind-the-scenes]]></category>
            <category><![CDATA[product-launch-strategy]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Charles Brian Quinn]]></dc:creator>
            <pubDate>Thu, 11 Jan 2018 16:16:59 GMT</pubDate>
            <atom:updated>2018-01-11T23:23:30.401Z</atom:updated>
            <content:encoded><![CDATA[<p>As Reid Hoffman of LinkedIn and Graylock Partners fame says: <a href="https://www.linkedin.com/pulse/arent-any-typos-essay-we-launched-too-late-reid-hoffman/">“If you’re not embarrassed by the first version of your product, you’ve launched too late.”</a></p><p>While we publicly launched <a href="https://thefrontier.bignerdranch.com/">The Frontier</a>, a screencast series for professional developers, <a href="https://www.bignerdranch.com/blog/the-frontier-screencasts-for-developers/">last week</a>, we actually did a customer pilot program first, for the month of December. This enabled us to launch 1 month earlier, by partnering with our earliest customers.</p><p><strong>Why partnering with your earliest customers is critical during a launch</strong></p><p><strong>1) We knew our existing customers knew us best and would tell us the truth.</strong></p><p>The Frontier is a complementary product for us at Big Nerd Ranch. We are well known for our <a href="https://www.bignerdranch.com/bootcamps/">bootcamps</a>, <a href="https://www.bignerdranch.com/training/">team training</a>, and <a href="https://www.bignerdranch.com/work/">consulting work</a>, but we saw a need: once developers went through our training or read our books, there were advanced questions — beyond the frameworks, related to everyday usage, small exercises to add on to the topics we cover, that our students were asking for. We didn’t have to look far to tell, it adds up in our <a href="https://forums.bignerdranch.com/">forums</a> and from the feedback in the post-class labs and questions. We decided to meet our customers in a way that was perfect for that type of learning: screencasts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/663/1*ZEkke7dns5Aq78AKNDzN2g.png" /><figcaption>The Frontier by Big Nerd Ranch: screencasts for professional developers</figcaption></figure><p>Our customers know our quality requirements. <a href="https://www.amazon.com/iOS-Programming-Ranch-Guide-Guides/product-reviews/0134682335/ref=cm_cr_dp_d_show_all_top?ie=UTF8&amp;reviewerType=all_reviews">We don’t half-ass anything.</a> So they’ll know if we’re pushing the limit. And they’ll tell us. One caveat, though is that because many love everything we do, and can look past things that new customers might not — they might not be as forthcoming and critical and must be directly asked. One way we did is through a detailed survey that asked about specific attributes, instead of asking open-ended, leading questions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/0*5GoxGKUXoiEllJci." /><figcaption>We asked specific questions to our early customers versus open-ended leading questions</figcaption></figure><p><strong>2) We could experiment very quickly</strong></p><p>With our customer pilot program, we could experiment quickly and roll out changes very fast and let them know. One quick piece of feedback we got right away was that we were not offering any trial or free videos, so we rolled that out in a few days. In fact, what we did was move even quicker. When we got the first response: “Do you have any way for me to preview the screencasts?” We quickly turned around, published them somewhere else and sent them the links. Personally, via email. Could we have done this with a public launch? Probably not. Then within a few days we had 2 screencasts ear-marked and live on the site as free trial, and updated our conversion metrics to see if that helped convert. It did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Cen4nUDlRyylTjNZ." /><figcaption>Sample Video Viewed = more conversions. Measured.</figcaption></figure><p>The same thing occurred with a feature for automatically keeping track of which screencasts our subscribers already viewed. We did it very quickly, in a phased approach — in fact it was done so quickly that the first version showed which ones were watched with a little dot in the top right corner, but someone asked again the next day, so we quickly implemented a more prominent visual icon to represent it. And we could get this feedback instantly from our customers in this pilot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/0*RprZMS6w4WvtETV6." /><figcaption>Before: Quick Fix to show Watched Screencasts</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/0*21ahO_t0jgdL__mt." /><figcaption>After: Much more visual indicator, and well received</figcaption></figure><p><strong>3) We could do things that don’t scale first, like ask for personal feedback</strong></p><p>For everyone that signed up, we emailed to say thanks, and asked why they signed up, and what they thought. For everyone who hit unsubscribe or cancelled their subscription, we asked why, too. For everyone who even signed up for step 1, but didn’t finish putting in their credit card to complete the subscription, we had a personalized email to find out why — this is great for figuring out if we aren’t telling our value proposition right.</p><blockquote><a href="https://www.entrepreneur.com/article/293393">“To Scale, Do Things that Don’t Scale”</a> — Reid Hoffman, in interview with Brian Chesky of AirBNB in Masters of Scale.</blockquote><p>A customer pilot program enabled us to launch quickly, get feedback rapidly, and ask directly (personally!) our best customers what to build. It enabled us to get their direct feedback, often without the use of “scalable” things like a support portal, ticket portal, and just asking directly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83e3d9fa8808" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Great Rewrite]]></title>
            <link>https://medium.com/@seebq/the-great-rewrite-87e80cbff743?source=rss-d3c64ad18e14------2</link>
            <guid isPermaLink="false">https://medium.com/p/87e80cbff743</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Charles Brian Quinn]]></dc:creator>
            <pubDate>Tue, 27 Dec 2016 13:36:00 GMT</pubDate>
            <atom:updated>2016-12-27T13:36:00.982Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*-v1qBYCeGwsdKYz-aKGOYQ.gif" /><figcaption>Dilbert by Scott Adams. New Website Developer. Monday October 17, 2016 <a href="http://dilbert.com/strip/2016-10-17">http://dilbert.com/strip/2016-10-17</a></figcaption></figure><p>There comes a time in the lifecycle of a software project, when inevitably the decision to “rewrite the whole thing” comes up. I’ve been on both sides of the debate, as the one initiating (and pestering the team and our stakeholders constantly about it). And I’ve been on the other side: “really, it’s not that bad, we can totally work around that, it’s making money, it works, it just takes longer to do things, which we’ve accounted for….”</p><p>I can understand both sides. Architectural decisions about how to build certain features made early on, by nature, are harder to change than the ones made last week. What is it about our personality as builders/creators/artists though, that makes us want to just rewrite it all? There’s certainly a fun aspect to it. Most good developers love architecting a clean, well-thought out system, and nothing beats the ability to do that on a brand new <a href="https://en.wikipedia.org/wiki/Greenfield_project">greenfield project</a> — an empty slate. Designers can certainly agree, it’s easier to just re-do the whole design than “migrate” incrementally to a cleaner one, I’d argue this is even harder than a rewrite in some cases. We can finally, once and for all, make those big changes.</p><p>On the other side, if the system works (albeit clunky, or slow, or not quite all there), are there workarounds or small changes that can snowball into bigger sweeping changes? Where best to direct our efforts when the great rewrite debate emerges?</p><p>True software craftsmen and craftswomen will use a refactoring technique, to slowly and deliberately replace pieces of the systems, adding modern components like tests and internal APIs to slowly replace parts and pieces until eventually a new system emerges, so that great rewrite (that was going to take a lot longer than you anticipated anyways) may not be necessary. The analogy would be flipping lots of tinier smaller switches and tiny migrations to replace components instead of one big massive migration and switch flip to turn on the new system.</p><p>In my experience, I’ve tried both the “Great Rewrite” and the “Great Refactoring” (and mixes of the two!). Most recently an attempt at refactoring was stopped after revealing fundamental changes to the business model that our new and (now)-legacy customers were asking for. In that case, our team made a deal: we would support the old system and quickly stand up a base, no-frills version of the experience with the fundamental differences, and migrate the older customers over to the new platform gradually over the course of 6 months as the features those customers were using came on-line.</p><p>When the great rewrite debate comes up, here are some things to keep in mind and ask yourself and your team:<br>* is the current software still providing value (making money) and can it continue in its current state?<br>* realistically can parts of the whole be carved off, and refactored separately to start versus re-doing it all?<br>* how much is a slower feature-release cycle really costing, and can the business really sustain a long lull in features while base functionality is rewritten?<br>* do we want to do the rewrite because it is really prudent, or can we really dig deep and maintain and patch at this phase of the business?<br>* if the rewrite takes longer than we estimate, are we ready to put the business at risk to keep doing so?<br>* can we plan beyond the rewrite to the sustaining phase of this product and if so, what does that look like?</p><p>Nothing beats experience, so whatever you decide: learn from it and hypothesize, and use that knowledge the next time this decision comes up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87e80cbff743" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning More When Things go Wrong: The Root Cause Analysis]]></title>
            <link>https://medium.com/@seebq/learning-more-when-things-go-wrong-the-root-cause-analysis-bfebf617d5e?source=rss-d3c64ad18e14------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfebf617d5e</guid>
            <category><![CDATA[root-cause-analysis]]></category>
            <category><![CDATA[cto]]></category>
            <dc:creator><![CDATA[Charles Brian Quinn]]></dc:creator>
            <pubDate>Tue, 20 Sep 2016 10:37:43 GMT</pubDate>
            <atom:updated>2016-09-20T12:41:56.552Z</atom:updated>
            <content:encoded><![CDATA[<p>Once, while touring the HQ of <a href="http://www.rackspace.com/">Rackspace</a> in San Antonio, Texas, we stopped at a wall of diagrams that looked like fishes, but with a ton of writing and technical diagrams on them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZOD942n41hYaQhDcZwRT1A.jpeg" /><figcaption>Rackspace’s RCA Wall, seen while on tour. photo: Charles Brian Quinn</figcaption></figure><p>Looking closer, our friend and guide, told us that this was the wall of RCAs, or Root Cause Analysis. An RCA is a process you use to determine what happened when something goes wrong. And what steps you’re taking to learn from it. Note: it’s not an attempt to make sure nothing ever goes wrong again, but rather that you can learn from each mistake.</p><p>At one of the product technology companies where I am CTO, we adopted the RCA template. Whenever we have an outage or a client on our platform is impacted, we do an RCA. We randomly assign someone to perform it, and they go off and collect the data and do the RCA. Each section has a set of questions, so anyone can facilitate it. While it helps to be close to the problem, the process benefits by having someone else (who may not have even known or experienced the problem) fill it out. That way, they can focus on the facts, and ask the relevant questions (hint: “why?” several times) to get to the root cause.</p><p>We’re not trying to prevent mistakes, in fact, at high performing companies where I’ve worked, it’s OK to make them. I’d argue you learn more from the mistakes than you do when everything goes right.</p><p>Here’s our RCA template (adapted and modified from versions found online and from <a href="http://www.cuc.org/files/3913/9172/0387/RackSpace_-_RCA_Overview.pdf">Rackspace’s RCA Overview</a>, thank you!):</p><p><strong>Step 1: Define the Problem</strong><br>Provides known specific details regarding the issue<br>Clearly States the Problem Statement — “What”<br>Specifies the Date &amp; Time of the problem — “When”<br>Identifies the location, area, equipment — “Where”</p><p><strong>Step 2: The Fishbone Diagram (optional) / Brainstorming</strong><br>The Fishbone Diagram should be considered an organized brainstorming activity and is comprised of six “bones” that are derived from the head (problem statement) of the diagram. The diagram helps to group known and potential causes of the problem, in turn helping to identify potential action items.</p><p><strong>Step 3: High Level Cause Map</strong><br>This section is intended to answer the “Why” at a high level. Working backwards from the problem statement and utilizing the fishboane diagram results to identify true “Root Cause”.</p><p><strong>Step 4: Summary of Issue &amp; Cause(s)</strong><br>This section is used to provide a summary of the issue, cause(s), timeline of the actions that lead to the issue occurring, and any remediation steps taken to stabilize the event.</p><p><strong>Additional Informatio</strong>n<br>A picture is worth a thousand words. When possible, we use pictures to visually identify the cause/problem in an effort to have individuals better relate to the issue being discussed.</p><p><strong>Step 5: Action Items Leading Towards Resolution</strong><br>Using the fishbone and the cause map, this section lists specific action items, owners, due dates and current status of the action item.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfebf617d5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning from Peer Learning Groups]]></title>
            <link>https://medium.com/@seebq/learning-from-peer-learning-groups-a4e802185b97?source=rss-d3c64ad18e14------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4e802185b97</guid>
            <category><![CDATA[developer-leadership]]></category>
            <category><![CDATA[peer-learning]]></category>
            <dc:creator><![CDATA[Charles Brian Quinn]]></dc:creator>
            <pubDate>Thu, 30 Jul 2015 17:44:32 GMT</pubDate>
            <atom:updated>2015-07-30T17:44:32.466Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a huge fan of peer learning groups. High-functioning peer groups, often called “<a href="http://www.thesuccessalliance.com/blog/napoleon-hill-and-mastermind-groups/">Master Mind Groups</a>” or roundtables foster a type of learning that can trump a google search or book club recommendation, any day.</p><p>In a peer learning group, a member might share an issue about an employee who keeps insisting that they need a raise (and expressing quite a bit of frustration and anger). The member who is sharing this issue is this employee’s manager, and confides in the roundtable that they actually don’t know whether or not they do need a raise, and also shares that they’re having trouble figuring out how to handle the situation, and what to say.</p><h4>Peer Groups Ask Probing Open-Ended Questions</h4><p>The peer group listens, and asks probing, open-ended questions: “Why do you think they feel this way?” or “How would other developers on the team feel about their performance or comp?” or “How have you handled this in the past?” Note that the questions are not fake advice hidden in a question: “Have you tried just talking to them?” (this is a bad question for a peer learning group for other reasons we’ll get to in a second).</p><h4>Peer Groups Trust Each Other</h4><p>Another high-functioning feature of a peer group is a level of trust that comes with time and effort. Because the group is supportive and made up of peers, there is no need for any one member to be prove that they have all the answers. They’re here to learn too, and by sharing an issue, even if they have experienced that exact same issue, they’re going to learn more from their peers about how they think and handle issues like these. The group also agrees to confidentiality, which helps deepen the trust. When a group knows that no one member will share anything said in the peer learning group, members can get to the true issues at hand, enabling real self-introspection and learning.</p><h4>Gestalt Language = Experience Sharing</h4><p>A good peer group doesn’t give advice. I know it seems counter-intuitive: here they are, with loads of advice to be given and shared, but the key difference in a high-performing group is instead of giving advice, they share their own experiences. This type of language is called <a href="http://ceoroundtables.webs.com/documents/CEORA%20Manual%20-%20Gestalt%20Language%20Protocol.pdf">Gestalt Language Protocol</a>.</p><p>So, in our hypothetical example, one of the other members of the group might share this experience:</p><blockquote>“When we implemented a career leveling chart (that I’d be happy to share a generic version with the group, but not our specific special secret one), many developers suddenly realized what they had to do to get a raise — it became very clear that performance towards the company’s goals (not just whoever asked loudest) was the way to get a raise, we just wrote it out in clear terms. That helped tremendously.”</blockquote><p>Another member of the group might share a completely different experience:</p><blockquote>“Your issue reminds me for some reason of this one time we had a developer who was always complaining about something, super negative, but we all knew they were an amazing developer, and could kick out tons of code and features. When they quit, we were scared the team wouldn’t be able to perform at all, but guess what — the team suddenly was even more effective and more productive without this negativity, it was like a void was lifted to allow the junior developers to rise up to fill the gaping void left by such a megalomaniac developer. Now, we don’t tolerate negativity and quickly address it via leading by example through our values of positivity and craftsmanship.”</blockquote><p>Note that no advice is given in these two experience shares, and two totally different stories were shared, but the experiences may shape a response (or solution) by the member experiencing the issue, and that response may be something entirely different but based on the experiences shared.</p><p>One of the interesting aspects of sharing experience in a high trust group is what it implies. When you give advice to someone, you are indicating “You don’t have the answer, <em>I don’t trust that you can figure it out</em>, so I will give it to you.” When you share your own experiences, you are indicating: “You ultimately are the best person to figure out the right answer, and <em>I trust you</em>, so I will share how I think to give you more information to help you.”</p><h4>Accountability</h4><p>After the experience shares, the member experiencing the issue then says: “I’m going to do X and Y by the next peer learning group meeting to solve this issue” — the group can hold them accountable by simply asking at the next meeting: “Well, how’d it go?” or in high-functioning groups, just by being there for the next one. The group by its own high-functioning accountable nature to learning from each other will not tolerate a member continuing to share the same issue or problem. When there’s high accountability, it doesn’t even have to be said — a member might think: “I better do what I said I would do because I don’t want to have to share the same issue next time with my peer learning group, I want to learn more and get better.”</p><h4>Let Me Google That For You</h4><p>While there are millions of results (at the time of writing) via search for “employee needs a raise” and “what to say to an employee needing raise”, and countless books on performance reviews, negotiation, and salary/comp/benefits — the probing questions and deep experience shares from a high-functioning, high-trust group of peers who will hold each other accountable enable a type of learning that is truly unparalleled.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4e802185b97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Premature Optimization for Difficult Conversations]]></title>
            <link>https://medium.com/@seebq/premature-optimization-for-difficult-conversations-dd2a3c8bc604?source=rss-d3c64ad18e14------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd2a3c8bc604</guid>
            <category><![CDATA[developer-leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Charles Brian Quinn]]></dc:creator>
            <pubDate>Tue, 28 Jul 2015 14:45:07 GMT</pubDate>
            <atom:updated>2015-07-28T14:45:07.342Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Premature Optimization can be defined as “optimizing before we know that we need to.” — <a href="http://c2.com/cgi/wiki?PrematureOptimization">http://c2.com/cgi/wiki?PrematureOptimization</a></blockquote><p>I’m an engineer. Nothing is worse than showing up to fix something and not having the right tool for the job. As a leader of engineers and developers, I’ve had to have some difficult conversations every now and then, and my tendency is to over-prepare.</p><p>I remember once I was managing a developer who just wasn’t delivering their best work. They had skipped a <a href="https://www.bignerdranch.com/blog/code-review-four-steps/">code-review</a> for their colleagues, which was now impacting the team productivity. This wasn’t the first time, either. I knew it was time for the talk.</p><p>First though, I was going to have to really research to see if they didn’t actually do the code review, maybe it was a fluke. Maybe I could write a script or some software that checks to make sure that <em>everyone</em> is doing code reviews on <em>all</em> code — premature optimization!</p><p>Alright, next I’m going to have to prepare for the conversation. I’ll need to re-read that book on negotiation sitting on my desk. Because what if they have an alternative explanation? I’ll just find a summary on-line real quick — premature optimization!</p><p>Well, maybe I can just role-play the conversation with someone, let me call in one of my other managers and discuss with them. I’m sure that whatever productive activity they’re doing can be interrupted by helping me with all the possible scenarios that could happen during this conversation — premature optimization!</p><p>OK, OK, time to visualize the outcome. I really just want this person to realize that one of the key activities is active code reviewing of the team, it helps them, it helps their teammates, and it helps the client. I want them to see the fallacy of their ways, and change their behavior. I can visualize an outcome where everyone realizes this, perhaps I’ll write a playbook for next time this happens, and send an all-company email — premature optimization!</p><blockquote>“Give me six hours to chop down a tree and I will spend the first four sharpening the axe.” -Abraham Lincoln</blockquote><p>Whenever I realize I’m delaying something, I’ll tell myself: Just Do It. I don’t always recognize this behavior, but I’m getting better, with practice.</p><p>The difficult conversation doesn’t have to be difficult. I remember a boss that always used a phrase that stuck with me, and resonated, when delivering important (or difficult news). He would say: “Let me be clear about this,” and then say: what happened, why it matters, and what needs to happen next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd2a3c8bc604" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>