Business Ownership and Management
Acting Like a Startup
Over the years, I have heard comments like, “We operate like a startup,” “We act like a startup,” and “We are an overnight success that was 10 years in the making.” These statements are often euphemisms for “We are small and not growing as quickly as we would like.”
There are numerous estimates of startup and failure rates in their first few years. One of the best descriptions I have found is from Failory. Investopedia and LendingTree have similar but differing takes on the statistics and root causes. The net result is that failure is much more common than success, especially over time. So, “acting like a startup” is not necessarily good, even when true. Instead, you want to “act like a successful startup!“
Understanding the various causes and the data on success and failure should become significant inputs to business plans focused on long-term success. As a Founder, there are several points that I believe to be key to success:
- You have specific expertise that is in demand and would be valuable to an identifiable number of prospective customers. How would those customers use those skills, and how would they quantify the value? That understanding provides focus on what to sell and to whom.
- A detailed understanding of the market and key players is needed to hone in on a niche to succeed.
- Understand your strengths and weaknesses, then hire the most intelligent and ambitious people who complement your weaknesses and strengths.
- Understand how to reach those potential customers and the messaging you believe will compel them. Find a way to test and refine those assumptions as necessary – before you go all in. Remember, Marketing and Lead Generation are very important but also expensive, so it pays to get this right the first time.
- Have a plan for delivering on whatever you sell before you get your first sale. A startup needs to develop its track record of success, beginning with its first sale.
- Cash flow is king. It is far too easy to run out of money while looking at an excellent balance sheet because of receivables. Understand what matters and why.
- Founders need to understand the administrative side of a business – especially the financial, legal (especially contract law), insurance, and taxes. Find experts to validate your approach and fill in knowledge gaps.
- Consistency leads to repeatable success. You standardize, optimize, and automate everything possible. Wasted time and effort become wasted opportunities.
- Finally, there needs to be sufficient cash on hand to fund the time it takes to find and close your first deals, deliver and invoice the work, and then receive your first payments. That could easily be a 3-6 month period.
Those are the foundational items that are reasonably tangible. What is not as concrete but equally as important are:
- Having or developing the ability to spot trends early and identify gaps that could become opportunities for your business.
- An agile mindset allows you to pivot your offerings or approach in order to refine your business model and hone in on that successful niche. Don’t fall into a sunk-cost fallacy.
- Foster a sense of innovation within your business. Always look for opportunities to deliver a better product or service, improve the efficiency and effectiveness of your business, and create intellectual property (IP) that adds long-term value.
- Focus on being the best and building a brand that helps differentiate you from your competition.
- Become a Leader, not a Manager (lead people, manage processes). Create your vision of success, set expectations for each person and team, and help eliminate roadblocks to their success. Trust your team to help you grow and replace members quickly if it becomes clear they are not a good fit.
Steve Jobs once said, “It doesn’t make sense to hire smart people and then tell them what to do; we hire smart people so they can tell us what to do.” To grow, you need to choose the best people you can afford, guide them, and trust them to perform in the best interest of your company. That is true in any size organization.
Winning is hard, so focus on the journey. Making your customers’ lives easier and allowing your employees to be creative while doing something they are proud of will lead you to your destination. But when things start going well, don’t sit back and convince yourself you are successful. Instead, feel the pressure of the competition – they are out there – and continue to focus on ways to improve and grow.
Success means different things to different people, but longevity, growth, profitability, and some form of contributing to the greater good should be dimensions of success for any vision.
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.
Understanding the Real Issue using Root Cause Analysis
Too often people, including Consultants, spend time trying to solve the wrong problem due to having incomplete or incorrect information. Once, I was investigating a series of performance problems and unplanned outages that were assumed to be two separate problems. As I gathered information, several people shared anecdotal stories of anomalous behaviors in various systems, speculated about the “real problem,” and discussed “chasing ghosts” during previous attempts to resolve it.
I remember stating that I was there to solve a real problem that was seriously impacting production, and that it was not my intent to chase ghosts or do anything else that would unnecessarily waste time. Next, I outlined the approach I would use to make a Root Cause determination and that we would reconvene to discuss the real problem and potential solutions. A few people scoffed and felt this was a waste of time and money.
The process followed was simple, structured, and logical. It took everything we knew to be true and mapped it out. I looked for patterns, commonalities, and intersections of systems and events. Within two days, my team and I had identified a complex root cause involving multiple components, which we demonstrated would reliably reproduce the symptoms that our client was experiencing. From there, we worked with their teams to make minor network changes, system configuration changes, and several small application changes.
By the end of the second week, they were no longer experiencing major slowdowns or unplanned outages. Each outage cost the company tens of thousands of dollars in lost sales because of the time-sensitive nature of their product. Within one week, they had recovered the cost of hiring my team and me. What stuck with us was how many really smart people “believed in ghosts” and failed to focus on the information they already had.
A few years later, we created a white paper to help others who needed a simple, structured approach. Below is a link to that white paper written by one of the top people on my team. We received very positive feedback then, so it still seems useful today. Please take a look and let me know what you think.
Innovations “Iron Triangle”
The concept of an Iron Triangle is that each side of the triangle represents an item constrained by the other two sides. In Project Management, this is often referred to as a triple constraint. This identifies the fundamental relationships (such as Time, Cost, and Scope in Project Management) without addressing related aspects such as Risk and Quality. It provides a simple understanding of both requirements and tradeoffs.
Yesterday I spoke with Dave Mosby, an impressive person with an equally impressive background. He related Innovation to Fire, noting that in order to create fire, you need fuel, oxygen, and heat. He added that they must be in the right combination to achieve the desired flame. What a brilliant analogy.
Dave stated that for Corporate Innovation to succeed, you need the proper balance of Innovation, Capital, and Entrepreneurship. I found this enlightening because his description substituted “entrepreneurship” for “culture” in my mental model. While the difference is subtle, I found it to be important.
As noted above, simplified frameworks do not provide a complete understanding. But they help understand and plan around the foundational items required for success. Mapping this to past experiences, I gained a better understanding of things that did not move forward as desired and what I could have done differently to be more effective.
One idea was to create a fault-tolerant database using Red Hat’s JBoss middleware. We had a Services partner willing to create a working prototype, tune it for performance, document the system requirements and configuration, and package it for easy deployment. They wanted $10K to cover their costs.
I didn’t have a budget at the time, so I created a purchase request supported by a logical justification. It modeled potential revenue increases for database subscriptions based on the need for a failover installation and growth from potential expanded use cases. This was a slam dunk!
In my mind, this was simple as it was “only $10K,” and I had funded many similar efforts when I had my own company. But that’s the rub. I viewed these efforts as investments in understanding, lessons learned, and growth. Not every investment had a direct payoff, but nearly each had an indirect payoff for my company. It was an entrepreneurial mindset that accepted risk as something required for rewards and success. I now see, many years later, how reframing my proposal as a way to foster innovation and entrepreneurship within the company could have been far more effective, since training is usually a budgeted item that is much easier to justify.
It is never too late to gain new insights and lessons learned. A slightly different perspective on an important topic provided the understanding that should help position projects for future success. This came from a discussion with an interesting person who has “been there, done that” many times.
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.
