lessons learned
Never Panic!
Whether it is an unexpected problem at an inconvenient time or an all-out crisis, panic is never a good way to solve problems, 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 very 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 usually did an excellent job, but his reaction negatively affected everyone else 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. We organized everyone into three teams and attacked 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 let us finish user acceptance testing and go live the following day. A mindset shift 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 hardware, 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 went into production, the function immediately logged people out as they tried to log in.
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 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 encourage people to share mistakes and lessons learned in order to avoid them in the future. Recognizing that mistakes can happen to anyone helps people plan better and keeps 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 thriving in any high-pressure environment.
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.
The Value Created by a Strong Team
I participated in an amazing team-building exercise as a Board Member for the Children’s Hospital Foundation of Wisconsin. We were heading down a path that would lead to a decision on whether to invest $150M in a new addition. The CEO at the time, Jon Vice, wisely determined that each committee needed strong teams to thoroughly vet the idea from every possible perspective.
The process started with being given a book to read (“Now, Discover Your Strengths” by Marcus Buckingham & Donald O. Clifton, Ph.D.) and then completing the “StrengthsFinder” assessment using a code provided in the book. The goal was to understand gaps in perception (how you view yourself vs. how others view you) so you could better understand your strengths and weaknesses. Then, teams were created with people having complementary skills to help eliminate weaknesses from the overall team perspective. The results were impressive.
Over my career, I have been involved in many team-building exercises and events – some of which provided useful insights. However, most failed to combine the findings meaningfully, provide useful context, or offer actionable recommendations. Key areas that were consistently omitted were Organizational Culture, Organizational Politics, and Leadership. Those three areas significantly impact value creation vis-à-vis team effectiveness and commitment.
When I ran my consulting company, we had a small core team of business and technology consultants and leveraged subcontractors and an outsourcing company to take on more concurrent projects, as well as larger, more complex ones. This approach worked for three reasons:
- We had developed a High-Performance Culture that was based on:
- Purpose: A common vision of success, understanding why that mattered, and understanding how that was defined and measured.
- Ownership: Taking responsibility for something and being accountable for the outcome. This included responsibility for the extended team of contractors. Standardized procedures helped ensure consistency and make it easier for each person to accept responsibility for “their team.”
- Trust: Everyone understood that to be effective and responsive, they needed to trust and support each other and trust each other’s judgment. If there was a concern, we focused on context and process improvements to understand what happened and implement changes based on lessons learned. We avoided personal attacks for the good of the entire team.
- Empowerment: Everyone understood that decision-making involves risk, while also recognizing that delaying an important decision could be costly and create more risk. Therefore, each member was responsible for making good decisions as needed and communicating changes to the rest of the team.
- Clear and Open Communication: The team was very transparent and honest. When an issue came up, they tried to resolve it with that person first, then escalated if they couldn’t reach an agreement and decided to seek the team’s consensus. Everything was out in the open and done in a constructive, collaborative spirit.
People who were not a good fit would quickly wash out, so our core team consisted of trusted experts. A friendly competition helped raise the bar for the entire team, but when needed, the other team members became a safety net for each other.
We were all focused on the same goal, and everyone realized the only way to succeed was to work together. Win or lose, we did it together. The strength of our team created tremendous value – internally and for our customers that we sustained for several years. That value included innovation, higher levels of productivity and profitability, and an extremely high success rate.
This approach can work at any level but is most effective when it starts at the top. When employees see their company leaders behaving this way, it provides a model and sets expectations for everyone under them. If there is dysfunction within an organization, it often starts at the top – by promoting or accepting behaviors that do not benefit the whole of the organization. With a strong and positive organizational culture, the value of strong teams is multiplied and becomes an incredible competitive advantage.
Occam’s razor, our Maxima, and the Sage Mechanic
My wife has a Nissan Maxima and loves her car. Over the past 9 months, there has been a persistent but seemingly random problem: the radio is used for a few minutes while the car is off, and then the battery dies when she tries to start the car. This has happened more than a dozen times over the past 3 1/2 years, and it has been seen by two dealerships for a total of three times recently with no success – the most recent visit being one day before this problem occurred.
Saturday morning, I was running errands when my wife called to let me know the problem had happened again (the second time this week, and she was very frustrated). I was pretty excited because this time the problem occurred at home, not at some parking lot like usual, so I had the luxury of time to try to determine the root cause. I’m somewhat mechanical but no professional, so I followed my consulting advice and contacted a professional.
Dave T. is a mechanical guru with an uncanny ability to offer sage advice with only a modicum of information. He is incredibly busy but always willing to spend a few minutes and give helpful advice. It helps that he is a great guy, but it also helps him generate business (leads and referrals). This approach creates a constant backlog of work and a very loyal clientele, which is good business.
I called Dave, described the problem, and mentioned what I had read on various forums (i.e., similar electrical problems observed after some arbitrary mileage). Next, I mentioned that this had just been to the dealership, and they did not find anything wrong. Dave laughed and said, “There is a 99%+ likelihood that the alternator is bad, possibly both the alternator and battery.” He sounded very confident.
There was a pause, and then he asked, “What’s more likely – that there is some completely random problem that only happens when your wife is out and your son stays in the car and listens to music for a few minutes, which by the way only happens to Maximas after X number of miles, or that there are issues with the alternators where they tend to fail after a certain amount of use, which causes them not to charge the battery properly and leads to a condition where there is not enough of a charge to start the car?”
When Dave explained it like that, I felt kind of stupid, consoled only by the fact that other professional mechanics had not resolved the problem before me. He added, “Anything that could drain a battery within a few minutes would be noticeable. It would start a fire, melt wires, or smoke or smell. You haven’t seen or smelled anything like that, have you?”
I described my plan to troubleshoot the problem, and Dave suggested that I also test the alternator and the specific gravity of the individual battery cells. So, less than five minutes into that call, I had a plan and was off and running.
Yesterday afternoon I spent several hours using a methodical approach to troubleshooting, documenting everything with pictures and videos to help me recall details and sequence if needed. Sure enough, Dave’s knowledge and intuition led to the correct conclusion.
I called him to thank him, and while we talked, I wondered aloud why the dealership couldn’t figure this out. Dave replied, “It’s not that they couldn’t have done what you did, but instead, they focused on the symptoms you described. The mechanic probably sat there for 10-15 minutes with the lights and radio on while the car was off. After that, the car started, so they assumed everything was fine.
I listened to what you said, ignored the randomness and speculation, and honed in on the likeliest problem. The fact that this happened again so soon also made sense because now your battery was run down from the testing performed by the dealership.” He added, “In my business, I get paid for results, so I can’t get away with taking the easy way out.”
I’m big on lessons learned and want to make the most of every experience because I have learned that skills and knowledge are often very transferable. As I thought about this, I realized that Dave’s analysis was the perfect practical application of Occam’s razor. It’s a very helpful skill as a Consultant, but more importantly, it can help when problem-solving in any line of work.
- ← Previous
- 1
- 2
- 3
- 4
- Next →
