<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jeff Spring on Medium]]></title>
        <description><![CDATA[Stories by Jeff Spring on Medium]]></description>
        <link>https://medium.com/@jeff_92036?source=rss-fd658d1a6a20------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bb0rijD4Ae3GTFhr</url>
            <title>Stories by Jeff Spring on Medium</title>
            <link>https://medium.com/@jeff_92036?source=rss-fd658d1a6a20------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:35:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeff_92036/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[Startup Imperfections & Efficiency]]></title>
            <link>https://medium.com/@jeff_92036/startup-imperfections-efficiency-6f9bfacf2985?source=rss-fd658d1a6a20------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f9bfacf2985</guid>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jeff Spring]]></dc:creator>
            <pubDate>Thu, 16 Feb 2023 05:25:02 GMT</pubDate>
            <atom:updated>2023-02-16T05:25:02.839Z</atom:updated>
            <content:encoded><![CDATA[<p>Many times I’m working with stakeholders who whole-heartedly believe in two things that are actually <strong>lethal</strong> to project success.</p><ol><li>They think that perfecting the product or feature is important</li><li>They think that the goal of review is to provide editorial input</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NuvXNw9JH6gbVNNnWhqhPg.jpeg" /></figure><h3>Perfection is an Artifice</h3><p>The suggestion came in today, “Sort the menu by alpha not by ID.”</p><p>My data engineer responded nearly immediately with a 👍 emoji. I immediately recognize this request as outside the pursuit of our core goals but the requestor didn’t, and the engineer just can’t resist.</p><p>Long before this report was created or needed it’s sort order modified, somewhere in clearer heads, our team knew we are a startup on a limited budget. For us, every minute and movement wins or loses the game for us.</p><p>Teams have issues remembering the first principals that drive forward a startup. Compromise and imperfection are key first principals that underly efficiency in a startup.</p><p>Sometimes a startup can get turned around. Stakeholders that come from outside the startup world can fall back into the corporate meeting room where adding value is key to one’s own psychological positioning within a team. This is a syndrome of the mind I’ve observed throughout corporate America. And when those not experienced in the startup world become active stakeholders or investors in startup projects, this mentality can seep in.</p><p>It’s rooted mostly in the psyche of each of us. It’s a personal pursuit to be valued and to make valuable contributions. We long to be heard and to contribute. It’s antithetical to think our contributions need to be metered and well designed before they will meet our startup’s goal of being efficient.</p><p>The more distance a person has between startup culture and corporate culture, the more this problem is exacerbated. Startups work in the world of Minimum Viable or Minimum Marketable Products. Corporates work in a world where endless time and budget are on tap to pursue perfection. In corporate practice, the final judgement of an effort’s success usually comes down to it’s proximity to perfection, stakeholders judge feedback coming from the top as the most important, and the rework or chaos this feedback causes is ignored in the name of perfection.</p><p>In a startup, the race to perfect is a race to the bottom. Imperfections are evidence that your team compromises in order to ship. Shipping compromises in less-than-consequential areas is an indicator that the team is protecting the time necessary to apply themselves to the most important goals of the business.</p><p>It’s generally difficult for stakeholders to understand that each engineer has a mental autonomy that that allows and causes them to establish a personal rank of priorities. Each engineer understands what’s important and what is not — fluff.</p><p>But engineers are not shot callers. Each time a shot is called that does not fit within the engineer’s instinct for the critical path, a bit of damage is done to the requestor’s credibility and a bit of time is wasted. Someone is being placated. Engineers are placating stakeholders because it’s faster to placate than to explain the connection their request has to the first principal of efficiency.</p><p>Over time this builds up as debt. The less stakeholders are held accountable to first principals, the more errant requests engineers are forced to respond to. The less success engineers have convincing stakeholders that perfection is not the pursuit, the more they cave. And lets face it, no one likes to tell their stakeholders that their suggestions don’t meet the thresholds set by the startup itself.</p><p>Asking stakeholders to consider cost, time &amp; complexity often causes an indirect rejection. Requestors will attempt to argue their way out with “local logic” or logical explanations within the context of the feature or request itself… forgiving them of the need to look at the bigger picture.</p><p>You’ll often hear things like, “But the feature would be just stupid without this” or “Why wouldn’t we make this change? It’s what our users need”. This is compounded by a general lack of familiarity with the time or complexity of any request.</p><p>Ideally, stakeholders would understand that their teams know more than they do about the implications of their requests. Ideally, stakeholders would receive a lot more declines and denials and they would be a lot happier to hear these denials.</p><h3>The Designers Explanation</h3><p>I find the work Dieter Rams has done to be valuable here. How popular it is throughout his principals that austerity and simplicity wins every time. These principals were so widely accepted by the design community for their reductive bent. Remove until only the essentials remain. I’m paraphrasing here.</p><p>As the smart people running the ball down the court, we need our stakeholders to understand the power of reductive design. Less is more — and this applies to your feedback, spur of the moment suggestions, and just-thought-of requests.</p><p>When you see an opportunity to perfect, assess it’s impact across these dimensions:</p><ol><li>What time will this take away from larger priorities?</li><li>What complexity could this cause engineers to deal with forever after today?</li><li>Am I personally motivated by the desire to look like a good contributor to my teammates?</li><li>Am I personally motivated by the desire to look good to an external party or client?</li><li>Will perfecting effect the bottom line? Will it get more revenue in the door? If the answer to this question is a multi-leap explanation about things affecting other things, the answer is often no.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f9bfacf2985" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>