<?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 Tom Lipscomb on Medium]]></title>
        <description><![CDATA[Stories by Tom Lipscomb on Medium]]></description>
        <link>https://medium.com/@tomlipscomb?source=rss-29f925089677------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xJUES3S0zNCRPdf4.</url>
            <title>Stories by Tom Lipscomb on Medium</title>
            <link>https://medium.com/@tomlipscomb?source=rss-29f925089677------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:56:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tomlipscomb/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[Solve Problems via Compartmentalization]]></title>
            <link>https://medium.com/@tomlipscomb/solve-problems-via-compartmentalization-8bcd3eb9371?source=rss-29f925089677------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bcd3eb9371</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Tom Lipscomb]]></dc:creator>
            <pubDate>Sat, 04 Nov 2017 13:30:06 GMT</pubDate>
            <atom:updated>2017-11-04T13:51:46.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5rrm6zkYVgPegS7yNaCdCw.jpeg" /></figure><p>A brilliant engineering friend years ago once told me that any problem can be solved if you subdivide the problem into small enough pieces. Therefore, a large problem becomes many small problems. And as we know small problems are much easier to resolve than those larger problems. In engineering, a problem can simply be how to design and develop a solution (e.g. a new product). In business, a problem can be how to increase revenue. And in business/proposal development, a problem is how to win a contract.</p><p>This sounds great, right? Big problem solved! A concept to resolution sounds simple and sometimes it is, while more often it isn’t.</p><p>In Object Oriented Programming there is a fundamental concept called Encapsulation that binds together functions and data and then hides the complexities. Encapsulation is a form of compartmentalization. In Psychology, compartmentalization is a coping and defense mechanism. We apply compartmentalization all the time to deal with conflicting ideas often without realizing it.</p><p><strong>5 Steps for Compartmentalization to solve a problem</strong></p><p>1. Sub-Divide Problems — Divide the problem into subproblems based on manageable boundaries. In other words, break a problem down into small enough pieces that you can easily achieve your goal by creating many small goals. If a sub-divided problem is still too difficult, divide the subproblem into smaller subproblems.</p><p>2. Organized your Subproblems — Map out your sub-divided problems into components. Using a Mind Map software application will help you visualize your components and their relationships to each other.</p><p>3. Ignore and remove (filter out) non-value information/material. — Non-value information is details that clutter the core goal and generates complexities. Make it simple!</p><p>4. Focus — Address one subproblem at a time. Increment through your subproblems and clear your mind between each subproblem by taking a break. If you are not making progress with your current subproblem, go to the next one and come back later.</p><p>5. Review and Test — After completing a subproblem check it for accuracy and ask if it helps to solve the larger problem. Test your solution with various scenarios. When you discover a new scenario, go back and retest/check. This is a process of validation, ensuring that your solution meets your intended goal. If your solution for your subproblem fails, either dispose of it or redo (refactor) it. Measure your success with each change to determine your improvement.</p><p><em>“Simplicity is the ultimate sophistication”. — Leonardo da Vinci</em></p><p>Tom Lipscomb is the President and Founder of Atebion LLC.</p><p>Atebion LLC develops software solutions for business development, proposal teams, and others. <a href="http://www.atebionllc.com/">Atebion LLC website</a></p><p>Two primary principles followed are “Continuous Improvement” and “Simplification” in product design and development. These principles translate into Easy-to-Use software solutions and frequent releases.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bcd3eb9371" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>