<?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 CJ Cummings on Medium]]></title>
        <description><![CDATA[Stories by CJ Cummings on Medium]]></description>
        <link>https://medium.com/@cummings.solutions?source=rss-2d676c2736ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OdeH5WepMsOXn2WUUiH0RA@2x.jpeg</url>
            <title>Stories by CJ Cummings on Medium</title>
            <link>https://medium.com/@cummings.solutions?source=rss-2d676c2736ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 17:32:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cummings.solutions/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[Creating Software, Right to Left]]></title>
            <link>https://medium.com/@cummings.solutions/creating-software-right-to-left-7925b79757f7?source=rss-2d676c2736ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/7925b79757f7</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[CJ Cummings]]></dc:creator>
            <pubDate>Wed, 30 Aug 2023 20:29:54 GMT</pubDate>
            <atom:updated>2023-08-30T20:29:54.923Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8FEFyuP6yc3VKcUo" /><figcaption>Photo by <a href="https://unsplash.com/@er1end?utm_source=medium&amp;utm_medium=referral">Erlend Ekseth</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In software development, the objective is to move fast. But in practice, it feels like we move slower than tar running uphill in January.</p><p>Slow development is expensive, frustrating, and leads to desperate acts to improve process — usually in the form of more meetings, better KPIs, and micromanagement. This “agile” methodology doesn’t involve being agile, fast, or innovative.</p><p>Many articles have been written analyzing these broken processes. However, at the foundation of all these issues is a lack of framework for turning vision into a reality — thinking from right to left while moving left to right.</p><h4>Vision is misunderstood</h4><p>A vision is a future snapshot of the world that is so clear it can be visualized, ubiquitously. People often don’t realize that vision should be owned by employees, which requires frequent communication at all levels about the company’s goals. It’s not just a vision statement or a manager’s Gantt chart once per quarter (please, don’t do this).</p><p>When a great leader talks about what they believe in, what we visualize is a world that differs from and is better than today&#39;s — a desired outcome from change. It&#39;s the desired outcome that provides clarity and it turns into a goal for those committed to making it a reality.</p><blockquote>Vision is a projection of desired outcomes through change in the minds of those who make it a goal to make the changes necessary for transforming that picture into a reality.</blockquote><p>Having a vision though, isn’t enough on its own. When moving into an apartment, for example, merely visualizing a fancy TV cabinet doesn’t get one closer to having an exciting Friday night sports-watching get-together.</p><p>The desired outcome is a great experience watching sports on TV, but a goal is nearly useless without a plan. And most importantly, both the vision and plan can change.</p><p>When shopping for that TV cabinet, the many choices that weren’t thought about initially might open doors to a new vision. Maybe a speaker system wasn’t planned, but it&#39;s identified that it could be integrated into the cabinet — that would certainly make the sports game more exciting.</p><p>Through this process, some questions might arise (maybe in the isle of a furniture store, or while planning the next software development increment):</p><ul><li>Do we have a vision?</li><li>Is changing the vision worth it?</li><li>Do we know what our values, goals, and desired outcomes are?</li><li>Are we prepared to make decisions around vision quickly and easily?</li><li>If others are involved, could they make these decisions or ask the right questions?</li></ul><h4>Timelines aren’t the enemy</h4><p>Every project happens on a timeline, left to right. Often, when developing and executing a plan, things are addressed and thought about only in terms of a timeline and deadline — addressing immediate needs without contemplating vision on the right first.</p><p>Don’t do this. It will only lead to technical debt, frustration, incohesive software, and a bad user experience. In short, it will be slow, expensive, and painful.</p><blockquote>Haste makes waste. — famous idiom</blockquote><p>It&#39;s not only speed that matters, but direction even more so. For the non-physics nerds or those who haven’t seen the movie <em>Despicable Me</em>, a vector (which has both magnitude and direction) cannot be made without two points or some reference angle. That other point and reference is a vision — another point on the timeline further to the right that is the basis for short-term decision-making.</p><p>For our TV cabinet example, not having a complete vision would be like picking a cabinet out because you like the color — not knowing that your significant other has quite a few books they’re hoping to put on it. It might function well as a bookshelf, but it might not. It most likely will not be the best bookshelf available. Not a very logical process — potentially having to make a return before contemplating another solution. Luck isn’t a reliable method either.</p><p>In software development, our TV cabinet could be many things — a technology to use, a process, product feature decisions, problem-solving techniques, etc… Without vision, even conversations around these decisions are nearly impossible to have.</p><p>The trick when working left to right efficiently, is to think right to left first, frequently, and carefully. More points can always be added on the right to accommodate changing goals, values, a dynamic market, or a vast technical landscape. Determine direction, and then you’re prepared to go fast in that direction.</p><h4>Requirements are not the way</h4><p>One common way to address this right-to-left dilemma is having “better” requirements. This is a horrible solution.</p><p>Going back to the TV cabinet, if the requirement is at least 3 shelves, what might come home is a cabinet with 10 shelves, but all 5 inches high that won’t accommodate books.</p><p>There are never enough requirements in software development — they are never good enough, specific enough, and can’t contain all the domain knowledge necessary for all things. No Jira ticket template will be a technical organization&#39;s salvation.</p><p>This could be a several-article topic, but this is because we aren’t starting with “why” when writing requirements. The projection of a vision isn’t taking place. An engineer can read requirements forever without understanding the desired outcomes of what is being built. For some things, this can work — a top-secret project or perhaps teams with temporary and extremely specific needs for example. However, for most software development, this must change — software development does not break down into an assembly line well. If you’ve ever heard or said, “be the user” this should make sense.</p><h4>Conclusion</h4><p>Stop doing things that don’t make sense for your product, yourself, and your team — I’m tired of seeing it and feeling it in bad software and processes.</p><p>Much like you wouldn’t purchase furniture that won’t work, stop writing software without knowing and anticipating what will work. Invest in frequently and carefully considering the “what will work” part as a team, so that decisions in support of the vision can be made efficiently.</p><p>Talk frequently about the desired outcomes of your software and make this the focus of your process. First, organize and prioritize goals, then decide how they can be incrementally realized. This becomes the vision in everyone&#39;s mind and a guide for requirements that aren’t set in stone.</p><p>Think from right to left in vision, so that when it’s time to work left to right there’s a framework. This is the prerequisite to not only innovation but <strong>delivering</strong> innovation.</p><p>Soon, you’ll find that you, your team, and your company will be moving at Mach 5 in a good direction relative to that tar attempting to run uphill.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7925b79757f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>