Life
Perfection is the Enemy of Progress
The title is a quote from Winston Churchill. I have learned in my career that these behaviors can be very costly from a business perspective, especially when decisions affect large parts of a business. It took me years to learn this lesson as I transitioned from perfectionist to “reformed perfectionist,” which was challenging.
Below are a few examples that could help you better understand people like this, and if you are someone like this, it might even provide motivation to try to change.
Early in my career, as I expanded my role from Programmer to Analyst Programmer to Systems Analyst, I often found myself spending too much time and effort on things that had minimal impact. Applications and subsystems looked a little better, ran a little faster, integrated more easily, were easier to modify, and generally had fewer problems. Those are all good things, but in hindsight, those benefits often did not justify the associated costs.
Some industries and applications require a degree of quality and reliability, such as nuclear power plants and lifesaving medical equipment. Since very few things are perfect, there are usually a variety of built-in safeguards to mitigate the impact of errors and failure. I have worked on a few of those systems, and I get it. But they are not in the majority.
Identifying the intersection of meeting the stated requirements, delivering the required quality, and knowing what “good enough” looks like is essential. That’s where diminishing returns set in for every additional hour spent on an activity.
I worked with a hardcore perfectionist at a small software and services company. On a consulting engagement, he spent two days on a task that I viewed as a 2-4 hour effort. We discussed it, and he told me he had at least three more days to finish. We had a heated discussion, and he was frustrated with me for a while. Years later, he admitted I was right, talked about how difficult it was to change, and how much more productive he is now.
I had a consulting engagement with a small software company that spent 10+ years on a SaaS product and was always “just two to three weeks away” from their MVP (minimum viable product). I started working with them over three years ago, and they are still at that point today. Software is never perfect, so waiting for perfection can kill a company.
I have also sold to companies stuck in analysis paralysis because they (leaders and teams) are always second-guessing decisions and want to be 100% certain before making a decision. Those companies need to solve a problem, or they would not be seeking a solution. In most cases, making an informed decision on a proven solution now will solve their problems and deliver value quickly. There is an actual business cost for every month of delay.
Are these behaviors costing you or your company money? If yes, dig a little deeper to understand the potential positive impact making small changes could have. Daily improvement is a great thing!
Never Panic!
Panic is never a good problem-solving tool, regardless of your position or role. It is especially bad when you are in charge of people or brought in for your expertise. Fear is a distraction, and panic leads to a myopic view of the problem. That hinders creativity and fosters dread, and those are not the ingredients for a solution.
The point in my career when this became readily apparent was when I was working for a small software company. We had a new product (Warehouse Management System) and were launching our third deployment. This one was more complicated than the rest because it was for a pharmaceutical company. In addition to requirements like refrigeration and lot control, there was a mix of FDA-controlled items requiring various forms of auditing and security, and storage areas significantly smaller than previous installations (think small packages of medicine versus pallets of one product). It was a challenge, to be sure.
A critical component, “Location Search,” failed during this implementation. About 10-12 people were in the “war room” when my boss, the VP of Development, began to panic. He was extremely talented and normally did an excellent job, but his reaction negatively affected the others in the room. The mood quickly worsened.
I jumped in and took over because I didn’t want to be stuck there all weekend, and because I wanted this implementation to succeed. I asked my boss to go out and get a bunch of pizzas. Next, I organized a short meeting to review what we knew and what differed from our prior tests, and I asked for speculation about the root cause. The team came up with two potential causes and one potential workaround. Everyone was organized into three teams, and we began attacking each item independently and in parallel.
We identified the root cause, which led to an ideal fix a few days later and a workaround that allowed us to finish the user acceptance testing and go live the following day. A change in mindset fostered the collaboration and problem-solving needed to move forward.
But this isn’t just limited to groups. I was a consultant at a large insurance company on a team redesigning their Risk Management system. We were using new software and wanted to ensure the proper environment variables were set during the Unix login process for this new system. I volunteered to create an external function executed as part of the login process. To keep the code clean, I added an “exit” at the end of the function. It worked well during testing, but once it was placed into production, the function immediately logged people out as they attempted to log into the system.
As you can imagine, I had a sinking feeling in my gut. How could I have missed this? This was a newer system deployed just for this risk management application, so no other privileged users were logged in at the time. Then, I remembered reading about a Unix “worm” that used FTP to infiltrate systems. The article stated that FTP bypassed the standard login process. This realization allowed me to FTP into the system and then delete the offending function. In less than 5 minutes, everything was back to normal.
A related lesson learned was to make key people aware of what happened, noting that the problem was resolved and there was no lasting damage. Hiding mistakes kills careers. Then, we created a “Lessons Learned” log, with this as the first entry, to foster the idea of sharing mistakes to avoid them in the future. Understanding that mistakes can happen to anyone is a good way to get people to plan better and keep them from panicking when problems occur.
Staying calm and focused on resolving the problem is a much better approach than worrying about blame and the implications of those actions. And most people appreciate the honesty.
As the novelist James Lane Allen stated, “Adversity does not build character; it reveals it.” Maintaining your composure and sense of calm (“equanimity”) makes chaos more manageable and helps develop resilience within the team. That is key to surviving in any high-pressure environment.
Using Themes for Enhanced Problem Solving
Thematic Analysis is a powerful qualitative approach used by many consultants. It involves identifying patterns and themes to better understand how and why something happened, providing context for other quantitative analyses. It can also be used when developing strategies and tactics because of its “cause and effect” nature.
Typical analysis tends to be event-based. Something happened that was unexpected. Some type of triggering or compelling event is sought to either stop something from happening or to make something happen. With enough of the right data, you may be able to identify patterns that help predict what will happen next based on past events. This data-based understanding may be simplistic or incomplete, but often it is sufficient.
But people are creatures of habit. If you can identify and understand those habits and place them within the context of a specific environment that includes interactions with others, you may be able to identify patterns within the patterns. Those themes can be much better indicators of what may or may not happen than the data itself. They become better predictors of things to come and can help identify more effective strategies and tactics to achieve your goals.
This approach requires that a person view an event (desired or historical) from various perspectives to help understand:
- Things that are accidental but predictable because of human nature.
- Things that are predictable based on other events and interactions.
- Things that are the logical consequence of a series of events and outcomes.
Aside from the practical implications of this approach, I find it fascinating relative to AI and Predictive Analysis.
For example, you can proactively monitor data, activities, and patterns by understanding recurring themes and triggers. That provides actionable intelligence that can be automated and incorporated into a larger system. Machine Learning and Deep Learning can analyze tremendous volumes of data from various sources in real-time.
Combine that with Semantic Analysis (and products like AllegroGraph) to harness the power of language through taxonomies and ontologies. The monitoring system would better understand what is happening (not just be aware of it), possibly determine how and why it happened, and result in even more focused and accurate predictions. Finally, include spatial and temporal data such as IoT, metadata from photographs, etc., and you should be able to view something as though you were very high up – providing the ability to “see” what is on the path ahead. It is obviously not that simple, but it is exciting.
This approach provides a multi-dimensional view of events and their causality, giving you the means to identify and prevent complex problems before they negatively affect a business.
Keeping these thoughts in mind will help you see details others have missed. Better tools can make for better analysis, better strategies, and better outcomes. Who wouldn’t want that?
Are you Thinking About Starting a Business?
The last post on Starting a Business was popular, so I wanted to share a key lesson I learned and link to previous posts that offer insights as you launch your own business. If you have any questions, just post them in the comments; I’d be happy to reply.
The COVID-19 pandemic has created a great deal of uncertainty and opportunity. For many, now is the ideal time to explore their dream of starting a business and jumping into entrepreneurship. That can be exciting, fun, stressful, financially rewarding, and financially challenging, all within the same short period of time.
Being prepared for that roller coaster ride and having the ability and strength to continue pushing forward is important. Something to understand is that “Things don’t happen to you. They are the Direct Result of your own Actions and Inactions.” That may sound harsh, but here is a prime example:
When I was closing my consulting business down, I trusted my Accountant and Payroll company to handle all of the required Federal, Wisconsin, Ohio, and Colorado filings – something they stated they would handle, and I accepted at face value. Both companies had done a great job before, so why would I expect any less this time?
About nine months later, I started receiving letters from Ohio and Colorado about filings due, so I forwarded them to the Accountant and Payroll company. I thought this was “old business” and was being handled, plus I had moved on. It was probably just a timing error, something easy to explain away.
Skipping forward nearly three years, I had been threatened by the IRS and the revenue departments in both Ohio and Colorado. I started with a combined total of nearly $500K in assessments. Slowly that dropped to $50K, and then to $10K. I spent countless hours on the phone and writing letters explaining the misunderstanding. It wasn’t until I finally found a helpful person in each department willing to listen and tell me specifically what needed to be done to resolve that situation. My final cost was around $1,000. I was relieved that this fiasco was finally over.
I blamed both the Accountant and Payroll Service for these problems for the longest time. Ultimately, I realized that it was my business and, therefore, my responsibility to understand the shutdown process – regardless of who did the work. I would have saved hundreds of hours and several hundred dollars by gaining that understanding earlier.
I was not a victim of anything – this situation directly resulted from my own inaction. It didn’t seem very important at the time, but my understanding of the situation and its importance was wrong, and I paid the price. Lesson learned. It was my business, so it was still my responsibility to the very end.
Below are the other links. You don’t have to read them all at once, but it’s worth bookmarking them and reading one per day. Every new perspective, idea, and lesson learned could be the thing that helps you achieve your goal a day, week, or month sooner than expected. Every day and every dollar matters, so make the most of both!
- Comments on and a link to an article on Curt Culver about Entrepreneurship.
- Comments on and a link to an HBR article about Start-ups and Entrepreneurship.
- Innovation, Intelligent Failure, and Failing Productively.
- Acting Like an Owner – Good Preparation for Becoming an Owner.
- Profitability Through Operational Efficiency.
- What Are You Really Selling?
- Continuous Improvement and a Growth Mindset.
- The Value Created by a Strong Team.
Presentation about Starting a Business and Entrepreneurship
It is interesting how often you see ads for franchise offerings that tout, “Become your own boss.” While that may not be all bad, it is just the tip of the iceberg. The presentation below is intended to provide insight to people considering starting their first company. This was from a one-hour presentation that glosses over many things, such as the need for registrations and insurance, but it could be helpful for a first-timer.
One of the first and most important lessons I learned when I started my consulting company long ago was that paying attention to cash flow was far more important than focusing on my balance sheet. Once you understand a problem, it becomes easy to change what you do to manage it. For example, using fixed pricing based on tasks where we received 50% up-front and the remaining 50% upon acceptance of the deliverable smoothed out cash flow, which was a big help.
So, take a look and post any questions that you may have. If one person has a question, many more will likely do as well! Cheers.
- ← Previous
- 1
- 2
- 3
- …
- 8
- Next →
Where Ideas, Experiences, and Lessons Learned Intersect 