A friend shared a video with me today. They didn’t say what it was about but assured me I’d like it. They were right. It went deep on unconscious bias. This is something I’ve thought a lot about but frankly haven’t taken the time to study. The video did a great job of filling in lots of gaps. It shared a framework that can be used to mitigate unconscious bias. Here’s how it works:

• P – Pay attention and notice your reactions and assumptions. We all react to situations and people. Being on the lookout for how you do it is important.  
• A – Acknowledge your assumptions. Assumptions affect how we relate to people and situations. And they lead to your brain making decisions on your behalf without your conscious permission. Be aware of your assumptions to be aware of what’s affecting how you relate to people and make decisions.
• U – Understand your perspective. In other words, be self-aware. How is your history affecting how you perceive a situation or person? Different life experiences lead to different perspectives. Your perspective might not be the only way to see things.
• S – Seek different perspectives. This helps you understand that your point of view is just that, a point of view. Not the objective truth. Hearing other perspectives can help you understand whether your assumptions are valid. Making a habit of hearing and understanding (not necessarily agreeing with) other perspectives also helps build empathy. Building human connections with people who are different from you can lead to more positive impressions of entire groups of people.
• E – Examine your options. After disrupting bias with the above-mentioned steps, you probably have more options. Use them to make an objective decision.

I have bias, and so does everyone else. Today I learned that bias is natural and necessary for human survival and decision-making. It’s based on assumptions and helps us in many instances by reducing the amount of thought required to make a decision. Being aware of bias and not making critical or complex decisions decision based on bias is the key.

Today marks the end of my eighty-ninth week of working from home (mostly). Here are my takeaways from week eighty-nine:

• Connecting the dots – I spent a few weeks thinking about a problem and collecting insights from others. This week, I was able to connect some dots. I still have lots to figure out, but it felt good to make some progress. Not sure where this will go exactly, but I feel good about the direction.  
• New project – I hit an unexpected snag. I’m frustrated, but I’m reminding myself that part of the reason I’m doing this is to learn. I still want to get this wrapped up before Christmas, so I’ll keep pushing next week.  

Week eighty-nine was busy. Still have lots to get done before December 25.

When I look at products being sold to SMBs, I think back to my early days with my company. I looked at tools as adding to either my revenue or my fixed expenses. Any tool that contributed to revenue was an easy sell. For example, we started off keeping track of our product catalog in Excel spreadsheets. We could have offered hundreds of products to customers, but we couldn’t keep track of the product details or inventory levels in Excel. So, we limited the products that we offered to customers, which limited our revenue growth.

The problem became so painful that I sought a solution. The software I found was expensive, but I knew it would increase revenue, so I quickly pulled the trigger. Revenue did increase, and we were a customer for years. We replaced it only when we absolutely had to.

Tools that didn’t increase revenue I scrutinized harder and took more time to decide about. We still added plenty of these tools, but I made sure that each one more than justified increasing the company’s expense structure.

If you’re considering selling into SMBs (or any company for that matter), understand whether your product increases your customers’ revenue or their expenses, and adjust your sales strategy accordingly.

Today I listened to a founder describe his first start-up failure. His key takeaway: what matters most is what customers think, not what he thinks. He had a hypothesis, and he built a product around it without much input from customers. When the product launched, customers wouldn’t pay for it. He shuttered the company.

The founder started another company. He’s staying close to the customer this time—focusing, laser-like, on building what they want. Feedback from early customers uncovered key insights he didn’t anticipate. They led to changes that accelerated the company’s early traction and have become a core part of its strategy.

Companies exist to solve problems for their customers. The only way to know if you’re doing that is to talk to customers. They may not always tell you want you want to hear, but if you listen hard enough, they’ll tell you what they want you to build.

‍

Today a founder shared with me his vision for helping people communicate more effectively. He’s starting out by building software that helps people understand how effective—or ineffective—their pitch is in communicating their message. He has studied effective communication and has experience working in the space, and he believes he can improve outcomes by helping people communicate more effectively.

I think he’s on to something. Listening to him today reminded me of a meeting I had. I was sharing an idea with a group of founder friends. When I finished talking, I asked them to tell me what they’d heard and what I’d left out that they wanted to hear. Their answers were eye-opening. Everyone heard something slightly different! I walked away realizing that I needed to improve how I communicated the idea and fine-tune it with my audience in mind.

Effective communication is important. Many people could use help improving their skills in this area (myself included). If you’re an early-stage founder trying to communicate an idea, take time to consider how you’re doing it and who your audience is.

An entrepreneurial friend told me about some early challenges at his company. The team wasn’t being efficient or consistent about completing work. This created at least two problems. First, the longer it took to complete the work, the less satisfied the customers were (and the less likely they were to refer other people to the company). Second, the longer each job took, the more it cost because employees were paid by the hour. After months of talking to his team, he found the solution.

He changed the compensation structure. He began compensating his team for completed jobs. The fewer jobs they completed, the less money they made. The more jobs they completed, the more they made. My friend noticed an immediate impact. His team’s productivity went through the roof. Over time, his team made more money and his business saw increased revenue and profit. Customer satisfaction increased too.

Keeping a team aligned is difficult. Everyone moving in different directions or moving at different speeds is stressful for the founders and could even sink the business. If everyone is moving in sync and in the same direction, the employees can have more autonomy and the business can reach new heights.

An entrepreneur buddy recently was a guest on a podcast, and he shared the recording with me. He told the host about his journey and his learnings to date as an entrepreneur. One of the things he mentioned was that he’d had tunnel vision early on, which was a mistake. He kept his head down and executed as best he could. He didn’t grow up in an entrepreneurial family and didn’t know many entrepreneurs. He used his street smarts and hustle to figure it out . . . the hard way.

Looking back, he now realizes that his journey was more difficult than it needed to be because people who came before him did the exact same thing: built their businesses, heads down. They weren’t sharing what they were learning as they went along. My friend wants to change this approach, which perpetuates a cycle of people making the same mistakes and learning the hard way.

His journey as an entrepreneur is far from over, but he now makes a point of publicly sharing it and what he’s learned. He doesn’t have it all figured out, and he says so. But his hope is that someone listening will avoid some pitfalls and execute faster than he was able to. Or someone on the fence about entrepreneurship will be motivated to give it a try.

Kudos to him for being intentional about sharing his learnings in real time. All too often, successful founders wait until the end of their career to share their knowledge. It’s great that they do that, of course, but I think that doing it along the way gives the people who hear them information that’s more current and therefore more relevant—so it’s more helpful.

I hope more founders start sharing what they learn as they go!

I spoke with a buddy today who asked me for my thoughts on raising capital for his business versus bootstrapping. I shared the lessons I learned from bootstrapping my own start-up and from investing as a venture capitalist:

• Market size – It’s important to understand the size of the market you’re going after. If it’s a small market, raising capital is less likely to make sense. If it’s a large one, then raising capital can make sense, depending on other factors.
• Destination – Once you understand how big the market is, you can determine how much of it you want to capture. CCAW’s market was $40 billion. I figured we could realistically capture 1% of it and build a $400 million company. Sadly, I didn’t think about this early enough in my entrepreneurial journey.
• Speed of execution – Once you know how big a company you want to build, you can think about the time frame for achieving your goal. The faster you want to execute, the more resources you’ll need. If you believe you’re facing a closing window of opportunity, you may want to execute as fast possible.
• Team – Given the speed with which you want to execute, who do you need on your team? Unsurprisingly, the faster you want to execute, the more people you’ll need.
• Runway – Consistent execution is important. You’ll want to make sure you have enough financial runway (i.e., cash) to consistently execute on your plan at the speed you envision. If you’re executing at a slow to moderate pace, bootstrapping may suffice. It’s more challenging (though not impossible) to provide ample runway for rapid execution if you’re bootstrapping.
• Accountability – The bootstrapping approach usually means the founder isn’t accountable to anyone. If you raise capital from others, it comes with an enhanced level of accountability. In my experience, most people need accountability—but no one wants it.

How to capitalize a new or existing business is situational. This is one of many decisions a founder has to make. There’s no right or wrong answer in the abstract—only the right answer for your situation.

Today marks the end of my eighty-eighth week of working from home (mostly). Here are my takeaways from week eighty-eight:

• Christmas push – This week kicked off the push to Christmas. Lots to get done before then! The next few weeks will be busy.    
• Prioritization – I spent time thinking about my 2022 priorities. So far, they’re the same as in previous years, but they’re in a different order. I’ll spend more time thinking about this.
• New project – I started working on a new project. I’ve never done this before, and it’s been an interesting learning experience so far. I anticipate more bumpy learning but am hoping I can wrap it up before Christmas.  

Week eighty-eight was steady. Looking forward to getting a lot done before December 25.

I met with a technical founder who spent seven years at a big tech company that’s a household name. I was surprised to learn that he spent a lot of his time rebuilding decade-old systems. The company worked on those systems only when it had to. On the outside, this company is cutting-edge, but internally, not so much . . . but the public would never know. The founder said the company didn’t grow to be worth hundreds of billions of dollars by fixing things that worked perfectly fine.

This reminded me of my time in corporate America. I learned then that some of the most well-known organizations have antiquated systems or processes. Not pretty, but things still worked, and that’s what mattered most. If it wasn’t broken, they weren’t in a rush to replace it.

Early founders should remember that good enough is all you need in the early days. Get something working and pushed out. You needn’t worry about using the latest and greatest technology or building something perfect, because those aren’t always the best use of resources. In many cases, done is better than perfect.