<?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 Nathan Dintenfass on Medium]]></title>
        <description><![CDATA[Stories by Nathan Dintenfass on Medium]]></description>
        <link>https://medium.com/@ndintenfass?source=rss-23661b33b7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*nmf9zbA_K5Iqwg8Q.jpg</url>
            <title>Stories by Nathan Dintenfass on Medium</title>
            <link>https://medium.com/@ndintenfass?source=rss-23661b33b7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:42:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ndintenfass/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[Chairs With Wheels]]></title>
            <link>https://medium.com/@ndintenfass/chairs-with-wheels-1d5365aa55e8?source=rss-23661b33b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d5365aa55e8</guid>
            <dc:creator><![CDATA[Nathan Dintenfass]]></dc:creator>
            <pubDate>Sat, 16 Jul 2016 20:35:28 GMT</pubDate>
            <atom:updated>2016-07-16T20:35:28.214Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<p>A former colleague once told me a story that I think of whenever in a discussion of investing in technology to solve business problems…</p><p>Long ago (circa early 90&#39;s) he was pitching a consulting project to a major telco. The telco had put out an RFP to various development shops asking for help solving a classic problem — they had a number of different systems for billing, provisioning, customer service, etc. Their customer reps would have to physically go to different terminals to deal with different aspects of the support process, causing a lot of inconvenience and wasted time.</p><p>Of course, all of the proposals that came back talked about various ways to integrate the systems using then state-of-the-art enterprise software techniques, and, of course, all of those proposals were quite hefty in terms of time and cost. My friend submitted his proposal and waited to hear back.</p><p>After a couple of weeks the telco got back to him — he did not land the project, but not because some other shop had beat him out. Instead, the telco told him that they had bought all of the customer reps chairs with wheels on them, making it much easier for them to move among the various terminals, so they no longer considered it a burning problem.</p><p>True or not (the guy who told me this story swore it was true) this parable always helps frame technology investment decisions for me. When tackling hard problems, I always look to see if you can find a “Chairs With Wheels” solution before (or, in many cases, while) investing in the automated solution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d5365aa55e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Son, I need to talk with you about your sexism.]]></title>
            <link>https://medium.com/@ndintenfass/son-i-need-to-talk-with-you-about-your-sexism-bfee5aa32c98?source=rss-23661b33b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfee5aa32c98</guid>
            <dc:creator><![CDATA[Nathan Dintenfass]]></dc:creator>
            <pubDate>Fri, 26 Sep 2014 20:51:32 GMT</pubDate>
            <atom:updated>2014-09-27T01:57:50.852Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEX0TRvFS-XFHeZ76BzfUQ.jpeg" /></figure><p>Recently I attended my 9-year-old son’s class to watch him take his turn at the regular 4th grade “Current Event” presentation. I beamed proudly as he nailed his short talk about flying cars, after which he took questions for ten minutes from the thirty or so kids sitting there. With many hands still in the air the Q&amp;A had to be cut short for time, and my wife and I left, proud of the great work he had done preparing and presenting. I lamented only one thing about his presentation that day: of the dozen or so students he called upon only one was female. No, it was not because only boys had raised their hands. It was because my son had, unconsciously, looked over that sea of raised hands and selected, with one exception, only boys. This included having called upon two of the boys twice while ignoring many hands brandished by female students.</p><p>Despite our best intentions and various attempts to provide our sons with models of gender equality, strong female protagonists, and more generally trying to instill an ethos of not judging on the basis of demographic details, our boys, disappointingly often, have exhibited decidedly dated views of gender roles. I make no claim to greatness in parenting on this front or any other, but that my boys can carry these views demonstrates to me just how far we have to go. The episode left me more determined to talk with them explicitly about how to wield (and not wield) their role as tall, white, middle-classed males to tear down and not prop up unjust social norms.</p><p>The evening after his presentation I talked with him before bedtime. We talked about how he felt things had gone with his presentation, and I gave him the appropriate kudos. Then I mentioned that I noticed a pattern in the way he called on people that morning. At first, he was incredulous, claiming it was just because he started calling on people from front to back, and there happened to be mostly boys in the front (a demonstrably false claim). After some discussion back and forth about whether he had, in fact, had a bias in his selection based on gender I proposed that not only must he consciously work to avoid such bias, he should engage in outright, intentional gender balance in his selection the next time around.</p><p>I’ve worked all of my adult in life in various corners of the San Francisco tech industry. The recent ratcheting up of the discussion around all kinds of bias in our broader community is a healthy development but a saddening reminder that the human race is nowhere close to our destination on this front. Now I have these precious few years to influence the values and behavior of two humans. Two male humans growing up with plenty of privilege. I don’t want to blow it. I want my boys to be net sources of good in the world, to leave the planet better for having had them in it. Fathers of sons need to play our role in the ongoing attempt to make the human race better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfee5aa32c98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deconstructing Agile: The Language of Agile is Broken]]></title>
            <link>https://medium.com/deconstructing-agile/deconstructing-agile-the-language-of-agile-is-broken-e0b60ba28901?source=rss-23661b33b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0b60ba28901</guid>
            <dc:creator><![CDATA[Nathan Dintenfass]]></dc:creator>
            <pubDate>Wed, 19 Mar 2014 08:35:14 GMT</pubDate>
            <atom:updated>2014-03-19T16:25:20.111Z</atom:updated>
            <content:encoded><![CDATA[<h4>New words are just the beginning</h4><p>The vocabulary of Agile does more harm than good. In helping companies adopt Agile methods we find we need to correct mistaken impressions people have gotten from Agile literature. Our first task is often to help them unlearn unhelpful language so that they can set the right goals and get buy-in from teams. As George Orwell wrote in his famous essay, “Politics and the English Language,” “language can also corrupt thought. A bad usage can spread by tradition and imitation even among people who should and do know better.” Perhaps <a href="http://pragdave.me/blog/2014/03/04/time-to-kill-agile/">Agile is dead</a>, but in any case it’s definitely time for a new product development vernacular.</p><p>Teams that are new to Agile are particularly susceptible to flaws in the lexicon, often getting the wrong impressions about why these practices might help them. We’ve seen teams go from openly hostile to embracing Agile practices when we get them past the literal meaning of the words, so let’s stop needing to explain so hard and start getting a better set of words to use.</p><p>The worst words we use…</p><h4>“Sprint”</h4><p>A sprint implies a furious run as fast as you can over a short distance, after which you are out of breath, sweaty, and generally spent. <a href="http://productsarehard.com/sprint-is-a-four-letter-word/">Agile is supposed to be the opposite of that</a>. We want a regular rhythm — not death marches to hit arbitrary deadlines, not idle time waiting for monolithic product requirements documents to get finished. Many teams want “going agile” to make them faster — a goal that is counterproductive and ultimately damaging to success. The theme of speed is woven throughout the Agile lexicon, and it has not served product people well. The language should imply doing work on a regular cadence in intervals short enough to allow for confidence in estimating what we can get done but long enough to allow for meaningful progress in each cycle. I prefer words like “cycle” or “interval” or “period” or “stretch” (I don’t care for “iteration” because it often implies for too many people that we will only ever make small changes).</p><h4>“Velocity”</h4><p>In an ideal world teams are relatively stable from cycle to cycle and have a consistent level of productivity. The point of <em>velocity</em> is to give us a reflection of the amount of work we can expect to produce as a team over a known period, so it’s seductive. But teams are rarely ideally configured, and how many points we get done can vary widely. Even when we are producing at a consistent pace the implication is still that we’re measuring speed, and it’s hard to resist the temptation to want to go “faster,” especially since we’re measuring our velocity with a number (assuming we’re using story points).</p><p>Velocity, as a quantifiable measure of productivity, is destructive to the goals most teams set out with in changing their processes. Managers tend to want to increase velocity by doing things like giving bonuses for getting more story points done. That attitude is profoundly misguided, not least because of the obvious corruption of incentives when teams are given reasons to inflate points or otherwise come up with a larger aggregate number for its own sake. What we actually want is frank assessments of relative difficulty in order to accurately and confidently gauge what we can get done in a given cycle. When velocity is corrupted to be something other than a means to achieve decent estimates (and thus commitments) it has a net-negative impact on producing good software.</p><p>I much prefer words like “capacity” or “load” that get us away from thinking about speed and the sensation of hurtling to the finish line and towards thinking about how we can do our own reality check on the work we commit to do.</p><h4>“Backlog”</h4><p>Backlog isn’t nearly as bad as sprint or velocity, but it isn’t great. The biggest problem is that in other parts of life we don’t <em>want</em> backlogs — the word implies things that are piling up, undone. It implies chores you have been putting off, things that stress you out because they are backed up. Constipated. We don’t have a “backlog” in any other domain that we are looking forward to tackling, so why use that word in our work? How about “pipeline”? We like to have a healthy pipeline of things. Or perhaps “slate” or even the very broad “board” as a more general list of things we’re currently focused on.</p><h4>“Story”</h4><p>The formal structure of common templates for user stories can be very useful. We’ve seen lots of people embrace the “As a… I want to… So that…” model with good results. That said, we’ve also seen a lot of product managers get very hung up on trying to write a “story” because that word implies a lot of structure and skill, not to mention just sheer word count. We would prefer the artifact use as few words as needed, and we find that over time teams start to find the formal structure to be cumbersome. If we have developed short-hands through conversations, that’s exactly what we want, and feeling pressure to make each line item a “story” with a narrative structure can be counter-productive. Call me old-fashioned, but I think “ticket” works well because it’s fairly general, cognitively allowing for a wide range of granularity. Some might prefer “feature” as distinct from bugs or tasks.</p><h4>“Scrum Master”</h4><p>The role of Scrum Master is the most problematic for organizations making a transition to Agile processes. Much of the difficulty has nothing to do with the name, but the name does carry unnecessary baggage into the discussion of what a Scrum Master does and why they are good to have. As a role that isn’t directly responsible for making something concrete, many managers who would otherwise be enthusiastic about Agile are loathe to pay for someone to “just” run sprint rituals. That resistance is exacerbated by confusion about the power (or lack thereof) that person will hold by virtue of the title “master.” Sometimes the best people to play this role are actually up-and-coming engineers who are eager to better understand Agile methods and take on a leadership role. “Coach” or “captain” can help frame the role better in the minds of managers and team members.</p><h4>“Agile”</h4><p>Finally we come to the name of the entire discipline. Once again we are faced with speed-based thinking, and once again we endanger the success of our process by focusing on the wrong thing. We’re right back to setting the wrong expectations that we’ll be magically faster and cheaper. It’s nice to have a named set of tenets, but the reality is that teams have specific and distinct challenges and constraints. Rarely should we implement a pure version of any of the flavors of Agile practices. It has become increasingly common to see <a href="https://flowchainsensei.wordpress.com/2014/03/11/i-dont-want-agile-back/">long-time advocates</a> for Agile practices become <a href="http://mikehadlow.blogspot.com/2014/03/coconut-headphones-why-agile-has-failed.html">disillusioned</a> with what “Agile” has <a href="http://blog.8thlight.com/uncle-bob/2013/12/10/Thankyou-Kent.html">come to mean</a>.</p><p>In our consulting work we focus on tailoring the recommended changes to the specific team and the goals they have. Usually we end up focusing on being more adaptive and responsive or on shortening the distance between ideas and manifestation of those ideas (both in terms of communication and elapsed time). A process well-matched to a team should be derived by that team based on first principles that come from introspective self-awareness by that team.</p><p>In summary, here’s a mapping of some suggested changes to the vernacular, in rough order of my preference.</p><p><strong>Agile → Responsive</strong>; Humanized</p><p><strong>Sprint → Cycle</strong>; Interval; Period</p><p><strong>Velocity → Capacity</strong>; Throughput</p><p><strong>Backlog → Pipeline</strong>; Slate</p><p><strong>Story → Ticket</strong>; Feature; Token</p><p><strong>Scrum Master → Coach</strong>; Captain</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0b60ba28901" width="1" height="1" alt=""><hr><p><a href="https://medium.com/deconstructing-agile/deconstructing-agile-the-language-of-agile-is-broken-e0b60ba28901">Deconstructing Agile: The Language of Agile is Broken</a> was originally published in <a href="https://medium.com/deconstructing-agile">Deconstructing Agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Be our Copernicus, Dave]]></title>
            <link>https://medium.com/slow-startups/be-our-copernicus-dave-75f34e41523d?source=rss-23661b33b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/75f34e41523d</guid>
            <dc:creator><![CDATA[Nathan Dintenfass]]></dc:creator>
            <pubDate>Wed, 18 Sep 2013 19:32:01 GMT</pubDate>
            <atom:updated>2013-09-18T19:32:01.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5MWR10fWJR82DU0Z.jpeg" /><figcaption>Photo Credit: Master and Fellows of Trinity College Cambridge</figcaption></figure><h4>An open letter to Dave Hornik about VC tribalism</h4><p>I recently had this interaction with Dave Hornik regarding his <a href="http://www.ventureblog.com/2013/09/want-to-get-funded-get-an-introduction.html">blog post</a> urging entrepreneurs to get a direct introduction to him through his trusted network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/0*vGNJGYrEoD8gBQ0d.png" /></figure><p>Rather than getting into it 140 characters at a time I’m writing this note to him in public (because he is hardly alone in his views on introductions among VCs).</p><p>Let me first say that I like you, Dave. You probably don’t remember me, but we have met a few times (a couple of group dinners in Berkeley and an interview in your office in 2006), and I worked in one of your <a href="http://www.saymedia.com/">portfolio companies</a> for a little while in 2007. I have always considered you to be one of the good ones. Your blog paved the way for a whole generation of transparency in an industry previously known for its abstruseness. Dave, you’re on my very short list of VCs I’d want to work with if I were doing a venture that was appropriate for your fund. So I write this <em>because </em>I think you have the power and character to do another Good Thing for the startup world.</p><p>I’m also in the fortunate position of being able to get an introduction to you. I mention this only to dispel the notion that I write this because I can’t have what you’re suggesting. I also mention this because I understand how little “resourcefulness” I would need to get a meeting with you — it’s much more a factor of the worlds you and I move in. I know lots of people who have done startups. I know lots of people who have gotten investment from VCs. I have spent years cultivating various friendships and business relationships that put me a degree away from you, Dave, through several people you know (one data point: we have 48 common connections on LinkedIn).</p><p>But…</p><p>But, Dave, this is exactly the problem. What you see as “resourceful” is really just common tribal affiliation. And when you see getting a warm intro as the gating factor for access to you, you put yourself at the center of the universe of people you might want to invest in. More importantly, if you think about how common your network is to every other local VC, you are all fishing from the same tiny pond. And what’s worse, the ideas in that little pond are much more prone to echo chamber effects that don’t breed breakthrough innovations. Do you really intend to create such a narrow, incestuous pipeline to choose from?</p><p>Then there’s the issue of access. Lots has been written in recent years about the club of rich, white men who dominate the startup world. Dave, don’t be part of the problem on that front. Instead, take yourself out of the center of the universe and realize that the vast majority of aspiring entrepreneurs aren’t friends with your friends. They don’t necessarily live in those social circles or enjoy the same ways to spend their weekends. They didn’t necessarily go to the same schools or work in the same companies as your friends. Put another way, the set of people who have direct access to someone you trust is a relatively homogenous group and represents a tiny slice of the world of ambitious, bright entrepreneurs. And I’ll go ahead and say it: the people with direct access to your friends disproportionately skew male, white, and wealthy.</p><p>Recognizing that you only invested in people that your friends recommended to you is an opportunity. You can stay at the center of that bubble, continuing to be satisfied that anyone who doesn’t have the trust of people you already trust isn’t worth your time, or you can realize this means you’ve been missing the vast pool of people outside that bubble and open yourself to new avenues for deal flow. Avenues that few of your colleagues/competitors are pursuing. Avenues that offer different perspectives on market opportunities and innovation methods. Avenues where your broad experience, kindness, and wisdom would be welcomed and well-leveraged.</p><p>So be our Copernicus, Dave. Take yourself out from the center of the model and make a new model that fully takes advantage of the universe of entrepreneurs. Find ways to connect to entrepreneurs that don’t know your friends yet. Challenge the assumption that there is a strong correlation between success potential and cloistered tribal affiliation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75f34e41523d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slow-startups/be-our-copernicus-dave-75f34e41523d">Be our Copernicus, Dave</a> was originally published in <a href="https://medium.com/slow-startups">Slow Startups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>