Entrepreneurs as Dissidents

Here’s to the crazy ones. The misfits. The rebels. The troublemakers. The round pegs in the square holes. The ones who see things differently. They’re not fond of rules. And they have no respect for the status quo. You can quote them, disagree with them, glorify or vilify them. About the only thing you can’t do is ignore them. Because they change things. They push the human race forward. While some may see them as the crazy ones, we see genius. Because the people who are crazy enough to think they can change the world, are the ones who do.

If you can’t see the video above click here.

Countries that put their artists and protesters in jail will never succeed in building a successful culture of entrepreneurship.  They will be relegated to creating better mousetraps or cloning other countries’ business models.

Entrepreneurs as Dissidents
When Steve Jobs returned to Apple, he ran the Think Different ads, a brilliant marketing campaign to make Apple’s core customers believe that Apple was still fighting for the brand.

But in hindsight, the ad captured something much more profound.

The crazy ones? The misfits? The rebels? The troublemakers? To celebrate those people as heroes requires a country and culture that tolerates and encourages dissent.

Because without dissent there is no creativity.

Countries that stifle dissent while attempting to encourage entrepreneurship will end up at a competitive disadvantage.

Pushing the boundaries
Most startups solve problems in existing markets – making something better than what existed before. Some startups choose to resegment a market – finding an underserved niche in an existing market or providing a good-enough low cost solution.  These are all good businesses, and there’s nothing wrong with founding one of these.

But some small segment of founders are truly artiststhey see something no one else does. These entrepreneurs are the ones who want to change “what is” and turn it into “what can be.“ These founders create new ideas and new markets by pushing the boundaries. This concept of creating something that few others see – and the reality distortion field necessary to recruit the team to build it – is at the heart of what these founders do.

The founders that make a dent in the universe are dissidents. They are not afraid to tell their bosses they are idiots or tell their schools they been teaching the wrong thing or to tell an entire industry to think different. And more importantly they are not afraid to tell their country it’s mistaken.

Freedom of Speech, Expression and Thought
Entrepreneurs in the United States take for granted our freedom of speech, freedom of expression and freedom of thought. It’s enshrined in our constitution as the first amendment.

In the last few years I’ve traveled to lots of countries that understand that the rise of entrepreneurship will be an economic engine for the 21st century. In several of these countries, the government is pouring enormous sums into building entrepreneurship programs, faculties and even cities. Yet time and again when I ask the local entrepreneurs themselves what questions they have, most often the first question is, “How do I get a visa to the United States?’

For years I thought the reason hands were raised was simply an economic one. The same countries that repress dissent tend to have institutionalized corruption, meaning the quality of your idea isn’t sufficient enough to succeed by itself, you now need new “friends in the right places.” But I now see that these are all part of the same package. It’s hard to focus on being creative when a good part of your creative energies are spent trying to figure out how to work within a system that doesn’t tolerate dissent.

Lessons Learned

  • Entrepreneurs require the same creative freedom as artists and dissidents
  • Without that freedom, countries will be relegated to cloning others’ business models or creating better versions of existing products
  • History has shown that the most creative people leave repressive regimes and create elsewhere

Listen to the post here:

Download the Podcast here

How We Fight – Cofounders in Love and War

I often get asked about finding cofounders and I usually give the standard list of characteristics of what I look for in a founder.  And I emphasize the value of a founding team with complementary skills sets – i.e. the hacker/hustler/designer cofounder archetype for web/mobile apps.  But Jessica Alter, Cofounder & CEO of FounderDating, pointed out that cofounders did not mean two founders in the same room.  She suggested that I was missing one of the key attributes of what makes successful startup teams powerful. She suggested that how cofounders fight was a key metric in predicting the success of a founding team.  So I asked her to write a guest post.

——————

I think about [cofounding] teams a lot – an insane amount.  And, not surprisingly, I frequently get asked what to look for or what to think about when starting the process of finding a cofounder – a true partner to start your next company with.

Like second nature, I start to recite a list of important attributes: complimentary skill sets, common visions, the notion of not trying to make someone fall in love with your idea (because the idea will likely change and then where are you?).  There are plenty more and they are important. But a few weeks ago after I sat on a panel about cofounders at Startup2Startup there was a small group dinner conversation to dig deeper on the topic.  Garry Tan (Posterous, YC), in recounting his personal experience said, “success can cover up a lot.”

And it clicked in my head – one of the key things to pay attention to in a search for a cofounder is how you fight.

Taking Time
How you fight with your potential cofounder(s) matters for a lot of reasons, the simplest of which is that you have time to fight – meaning you’ve worked together long enough to hit disagreements or bumps.  It’s one of the most common mistakes we see. I literally just received an email from someone (that I don’t know) asking to me to meet with them so that they can circumvent our regular process because, “I don’t feel like I have time for the regular FounderDating process.“  Quick advice to people that think finding a cofounder is a box to check and “don’t have time” – you won’t find someone and if you do the relationship is unlikely to last.  You’re looking for an employee, not a partner.

We tell all our FounderDating members that we’re a great starting point to connect with amazing people all with high intent to start something. But in order to figure out if you can work together you have to (wait for it…) actually work together.  That could be starting a side-project, heading over to a Startup Weekend or other hackathon, working full-time for a few months or some combination of those options.  However you do it, you need to build something together.  It doesn’t ultimately matter it if ends up being the right product, you will still have areas you disagree on throughout the process. Ask yourself: Have we had disagreements? If you haven’t, maybe you should consider a longer courtship period.

Simulating Real-Life
Consider what real startup life is going to be like.  For a long-time (longer than you plan) things are not going to work and you’ll have to figure out what to do – together.  If you do eventually reach a point where the company is making real progress, you’re still going hit crazy challenges on a regular basis that you’ll have to navigate together. This pressure – which is compounded by the sound of the ticking clock if you took money – will up the stress levels and hence the propensity to disagree.

If you don’t have at least a taste of what that’s going to be like, not only have you not done your homework, but also could be in for a rude awakening. So, let’s agree you’re going to fight. That, in and of itself, doesn’t mean anything. In fact, it’s quite healthy. What matters in real life is what are the fights like? Do they escalate rapidly or become knock down, drag outs? Can you recover quickly and keep moving? Entrepreneurship and early stage companies are about moving fast; if you’re caught in a disagreement for days at a time it means decisions are not being made and/or people are walking around feeling resentful.  Either one will eventually lead to failure.  Ask yourself: When we fight do we get over it quickly and respectfully?

What Are You Fighting About?
Finally, and this is insanely important, it matters what the fights are about.  Are you fighting about whether a button should be green or blue or are you fighting about whether or not you want to raise money?

A lot of people approach finding cofounders as just a skill set need and believe once that box is checked, everything will be smooth sailing. Complimentary skill sets are important and if you’re fighting about one functional area  (e.g. design, product) it might be a sign you have too much skill set overlap. But if it were just about complimentary skill set matching it wouldn’t be very hard.

What’s difficult is making sure you’re aligned on the softer side: Why do you want to build a company? What kind of company you want to build? What are your working styles? What are your values?  What are your other priorities (family, etc.)?  We don’t care if entrepreneurs want to build lifestyle businesses or go for IPOs, if they are tethered to their email or check out at 7pm – that’s a personal decision. But you better make sure you’re on the same page as your potential cofounder about those topics. These are the issues that break up relationships, not button colors.

Ask yourself: What are we fighting about and why?

Make no mistake; I’m not suggesting you should manufacture a fight. But every relationship has ups and downs, the ones that last are able to bounce back from the downs quickly and respectfully and be better for it.  So give yourselves permission and time to fight and reflect on how you do it before you take the leap together.
Listen to the post here: Download the Podcast here

Entrepreneurship is hard but you can’t die

I’m posting a series of articles on family, startup culture and careers. These vignettes are about how I’ve lived my life trying to make a dent in the universe. Hoping they’ll give you a point of view about the vast possibilities in life. I’ve posted five so far: the first post is here; the second here, the third here, the fourth here, and the fifth is here.


We Sleep Peaceably In Our Beds At Night Only Because Rough Men Stand Ready To Do Violence On Our Behalf

Everyone has events that shape the rest of their lives.  This was one of mine.

——-

I’ve never been shot at. Much braver men I once worked with faced that every day. But for a year and a half I saw weapons of war take off every day with bombs hanging under the wings. It never really hit home until the day I realized some of the planes didn’t come back.

Life in a War Zone
In the early 1970’s the U.S. was fully engaged in the war in Vietnam. Most of the fighter planes used to support the war were based in Thailand, or from aircraft carriers (or for some B-52 bombers, in Guam.)  I was 19, in the middle of a hot war learning how to repair electronics as fast as I could. It was everything life could throw at you at one time with minimum direction and almost no rules.

It would be decades before I would realize I had an unfair advantage. I had grown up in home where I learned how to live in chaos and bring some order to my small corner of it. For me a war zone was the first time all those skills of shutting out everything except what was important for survival came in handy. But the temptations in Thailand for a teenager were overwhelming: cheap sex, cheap drugs (a pound of Thai marijuana for twenty dollars, heroin from the Golden Triangle that was so pure it was smoked, alcohol cheaper than soda.) I saw friends partying with substances in quantities that left some of them pretty badly damaged. At a relatively young age I learned the price of indulgence and the value of moderation.

What a great job
But I was really happy. What a great job – you work hard, party hard, get more responsibility and every once in awhile get to climb into fighter plane cockpits and turn them on. What could be better?

Near the beginning of the year when I was at an airbase called Korat, a new type of attack aircraft showed up – the A-7D Corsair. It was a single seat aircraft with modern electronics (I used to love to play with the Head Up Display.) And it was painted with a shark’s mouth. This plane joined the F-4’s and F-105 Wild Weasels (who went head-to-head with surface-to-air missiles,) and EB-66’s reconnaissance aircraft all on a very crowded fighter base.  While the electronics shop I worked in repaired electronic warfare equipment for all the fighter planes, I had just been assigned to 354th Fighter Wing so I took an interest in these relatively small A-7D Corsair’s (which had originally been designed for the Navy.)

He’s Not Coming Back
One fine May day, on one of my infrequent trips to the flight line (I usually had to be dragged since it was really hot outside the air-conditioned shop), I noticed a few crew chiefs huddled around an empty aircraft spot next to the plane I was working on. Typically there would have been another of the A-7’s parked there. I didn’t think much of it as I was crawling over our plane trying to help troubleshoot some busted wiring. But I started noticing more and more vans stop by with other pilots and other technicians– some to talk to the crew chief, others just to stop and stare at the empty spot where a plane should have been parked. I hung back until one of my fellow techs said, “Lets go find out what the party is about.”

We walked over and quickly found out it wasn’t a party – it was more like a funeral.  The A-7 had been shot down over Cambodia.  And as we found out later, the pilot wasn’t ever coming home.

An empty place on the flight line
While we were living the good life in Thailand, the Army and Marines were pounding the jungle every day in Vietnam. Some of them saw death up close. 58,000 didn’t come back – their average age was 22.

Everyone shook their heads about how sad. I heard later from “old-timers” who had come back for multiple tours “Oh, this is nothing you should have been here in…” and they’d insert whatever year they had been around when some days multiple planes failed to return. During the Vietnam War ~9,000 aircraft and helicopters were destroyed. Thousands of pilots and crews were killed.

It’s Not a Game
I still remember that exact moment – standing in the bright sun where a plane should be, with the ever present smell of jet fuel, hearing the engines of various planes taxing and taking off with the roar and then distant rumble of full afterburners – when all of a sudden all the noise and smells seemed to stop – like someone had suddenly turned off a switch. And there I had a flash of realization and woke up to where I was. I suddenly and clearly understood this wasn’t a game. This wasn’t just a big party. We were engaged in killing other people and they were equally intent on killing us. I turned and looked at the pilots with a growing sense of awe and fear and realized what their job – and ours – was.

They say that you can only understand your future by looking at your past. That day I began to think about the nature of war, the doctrine of just war, risk, and the value of National Service. The seeds of the classes I would create decades later – Hacking for Defense, Technology, Innovation and Great Power Competition and the Stanford Gordian Knot Center – all have their roots on that hot flight line with that empty revetment almost half a century ago.

Epilogue
Captain Jeremiah Costello and his A-7D was the last attack aircraft shot down in the Vietnam War.

Less then ninety days later the air war over Southeast Asia ended.

For the rest of my career when things got tough in a startup (being yelled at, working until I dropped, running out of money, being on both ends of stupid decisions, pushing people to their limits, etc.), I would vividly remember seeing that empty spot on the flightline. It put everything in perspective.

Entrepreneurship is hard but you can’t die.

Lying on your resume

It’s not the crime that gets you, it’s the coverup.
Richard Nixon and Watergate

Getting asked by reporter about where I went to school made me remember the day I had to choose whether to lie on my resume.

I Badly Want the Job
When I got my first job in Silicon Valley it was through serendipity (my part) and desperation (on the part of my first employer.)  I really didn’t have much of a resume – four years in the Air Force, building a scram system for a nuclear reactor, a startup in Ann Arbor Michigan but not much else.

sgb 1980 resume at 26

sgb 1980 resume at 26

It was at my second startup in Silicon Valley that my life and career took an interesting turn. A recruiter found me, now in product marketing and wanted to introduce me to a hot startup making something called a workstation. “This is a technology-driven company and your background sounds great. Why don’t you send me a resume and I’ll pass it on.” A few days later I got a call back from the recruiter. “Steve, you left off your education.  Where did you go to school?”

“I never finished college,” I said.

There was a long silence on the other end of the phone. “Steve, the VP of Sales and Marketing previously ran their engineering department. He was a professor of computer science at Harvard and his last job was running the Advanced Systems Division at Xerox PARC. Most of the sales force were previously design engineers. I can’t present a candidate without a college degree. Why don’t you make something up.”

I still remember the exact instant of the conversation. In that moment I realized I had a choice. But I had no idea how profound, important and lasting it would be. It would have been really easy to lie, and what the heck the recruiter was telling me to do so. And he was telling me that, “no one checks education anyway.” (This is long before the days of the net.)

My Updated Resume
I told him I’d think about it. And I did for a long while. After a few days I sent him my updated resume and he passed it on to Convergent Technologies. Soon after I was called into an interview with the company. I can barely recall the other people I met, (my potential boss the VP of Marketing, interviews with various engineers, etc.) but I’ll never forget the interview with Ben Wegbreit, the VP of Sales and Marketing.

Ben held up my resume and said, “You know you’re here interviewing because I’ve never seen a resume like this.  You don’t have any college listed and there’s no education section.  You put “Mensa” here,” – pointing to the part where education normally goes. “Why?” I looked back at him and said, “I thought Mensa might get your attention.”

(In high school I was a terrible student and therefore I didn’t think I was that smart. My sister, much older and much wiser, thought otherwise and had me take a Mensa test when I was a junior. The numbers confirmed her suspicion. Being a Mensa member didn’t make school any easier but it gave me comfort that I wasn’t a complete idiot, just that I learned differently.)

Ben just stared at me for an uncomfortable amount of time. Then he abruptly said, “Tell me what you did in your previous companies.” I thought this was going to be a story-telling interview like the others. But instead the minute I said, “my first startup used CATV coax to implement a local-area network for process control systems (which 35 years ago pre-Ethernet and TCP/IP was pretty cutting edge.) Ben said, “why don’t you go to the whiteboard and draw the system diagram for me.”  Do what? Draw it?? I dug deep and spent 30 minutes diagramming trying remember headend’s, upstream and downstream frequencies, amplifiers, etc.  With Ben peppering me with questions I could barely keep up. And there was a bunch of empty spaces where I couldn’t remember some of the detail. When I was done explaining it I headed for the chair, but Ben stopped me.

“As long as you’re a the whiteboard, why don’t we go through the other two companies you were at.”  I couldn’t believe it, I was already mentally exhausted but we spent another half hour with me drawing diagrams and Ben asking questions. First talking about what I had taught at ESL – (as carefully as I could.) Finally, we talked about Zilog microprocessors, making me draw the architecture (easy because I had taught it) and some sample system designs (harder.)

Finally I got to sit down.  Ben looked at me for a long while not saying a word. Then he stood up and opened the door signaling me to leave, shook my hand and said, “Thanks for coming in.” WTF? That’s it?? Did I get the job or not?

That evening I got a call from the recruiter. “Ben loved you. In fact he had to convince the VP of Marketing who didn’t want to hire you. Congratulations.”

Epilogue
Three and a half years later Convergent was now a public company and I was a Vice President of Marketing working for Ben. Ben ended up as my mentor at Convergent (and for the rest of my career), my peer at Ardent and my partner and co-founder at Epiphany.  I would never use Mensa again on my resume and my education section would always be empty.

But every time I read about an executive who got caught in a resume scandal I remember the moment I had to choose.

Lessons Learned

  • You will be faced with ethical dilemmas your entire career
  • Taking the wrong path is most often the easiest choice
  • These choices will seem like trivial and inconsequential shortcuts – at the time
  • Some of them will have lasting consequences
  • It’s not the lie that will catch up with you, it’s the coverup
  • Choose wisely

Tenacious

TE·NA·CIOUS/TƏˈNĀSHƏS/

Adjective:

  1. Not readily letting go of, giving up, or separated from an object that one holds, a position, or a principle: “a tenacious grip”.
  2. Not easily dispelled or discouraged; persisting in existence or in a course of action.

When I was a entrepreneur I’d pursue a goal relentlessly. Everything in between me and my goal was simply an obstacle that needed to be removed.

This week I had another reminder of what it was like.

Plenty of Time
I was speaking at the National Governors Conference in Williamsburg Virginia and my talk ended Sunday at noon.  I knew I had to be in Chicago at 9:30Am Monday for a Congressional hearing (I was the lead witness) so I made sure I was on the next to last plane out of Richmond (just in case the last one got cancelled.)

My wife and I got to the airport for our 4:45pm plane and found it was delayed to 6pm. Ok, no problem. Oops now it’s delayed until 7:30pm.  Hmm, the last plane out looks like it’s leaving on-time at 8pm – can I get on that?  No, sold out.  So we sit around and watch our plane get delayed to 8pm, then 9pm then 10pm, then cancelled. Oh, oh this is looking a bit tight, but there’s a 6am from Richmond to Chicago. No problem. If we can get on that I can still make the hearing. The nice smiling United agent says “oh that’s sold out as well. Now I’m getting a bit concerned, “Well how about the American Airlines 6am?” “Sold out” she replied. The next flight is at 8am.” Ok put me on that one.  “Oh that’s sold out as well.”

We Have a Problem
I need to be in downtown Chicago by 9:30am.  Period.

So I ask, “where’s the nearest airport that has a 6am flight to Chicago?” Oh, that’s Dulles airport in Washington.”Ok, how far is that?” 120 miles.

We head back to the car rental booth, rent our second car of the day and head to Washington in pouring rain and drive in bumper to bumper traffic, crawling to our next airport. Three hours later we check into the airport hotel at 1:30am assured that all we needed to do is get 3 hours sleep and United would whisk  us on the way to Chicago.

Tenacious
Waking up at 4:15am I glance at my email and couldn’t believe it – United canceled our 6am from Dulles. The next flight they had would get us into Chicago at 10am – too late to testify in front of Congress.  It looked like there was simply no way to get where we needed to go.

My first instinct was to give up. Screw it. I tried hard, failed due to circumstances beyond my control.  Why don’t we just go back to bed and get a good nights sleep.

That thought lasted all of 30 seconds.

We quickly realized that Washington has two airports – the other one, National was 30 miles away. I looked up the flight schedule and realized that there was a 6am and 7am leaving from National. I booked the 7am online not believing we could make the earlier 6am flight.

The only problem is that there weren’t any taxi’s to be found at 4:30 in the morning – in front of the hotel or on Uber.  So I hiked over to the main road and flagged one down and had him drive me back to the hotel, pick up my wife and luggage and continued our adventure.

We got to Washington National Airport at 5am and walked directly into the longest security line I’ve seen in 10 years. Well, at least we can make the 7am plane (the one we’re ticketed on) and barely make the congressional hearing.

Getting through security the first gate we pass is the 6am for Chicago and they’re in the process of closing the door.  “Any chance you have any seats left?”  Oh, we have two seats in the back of the plane but we don’t have time to re-ticket you.

Trying to remember my reality distortion field skills from my entrepreneurial days I convinced her to let us on.

We made it to Chicago.  I actually got to sleep in our hotel for 45 minutes before the Congressional Field hearing.

Then I got to share this:

Lessons Learned

  • Your personal life and career will be full of things that block your way or hinder progress
  • Keep your eyes on the prize, not the obstacles
  • Remove obstacles one at a time
  • There’s almost always a path to your goal
  • Never, never  never give up

Listen to the post here: Download the Podcast here

The Startup Team

Individuals play the game, but teams beat the odds
SEAL Team saying

Over the last 40 years Technology investors have learned that the success of startups are not just about the technology but “it’s about the team.”

We spent a year screwing it up in our Lean LaunchPad classes until we figured out it was about having the right team.

Startup Team Lessons Learned
During the last 12 months we’ve taught 42 entrepreneurial teams with 147 students at Stanford, Berkeley, Columbia and the National Science Foundation. (As many teams as most startup incubators.)

Get into the Class
When I first started teaching hands-on, project/team entrepreneurship classes we’d take anyone who would apply. After awhile it became clear that by not providing an interview process we were doing these students a disservice. A good number of them just wanted an overview of what a startup was like – an entrepreneurial appreciation class (and we offer some great ones.) But some of our students hadn’t yet developed a passion for entrepreneurship and had no burning idea that they wanted to bring to market. Yet in class they’d be thrown into a “made-up in the first week” startup team and got dragged along as a spear-carrier for someone else’s vision.

Step One – Set a Bar
So as a first step we made students formally apply and  interview for the Lean LaunchPad class. We were looking for entrepreneurs who had great ideas and interest in making those ideas really happen. We’d hold mixers before the first class and the students would form their teams during week one of the class.

But we found we were wasting a week or more as the teams formed and their ideas gelled.

Step Two – Apply As A Team
So next time we taught, we had the students apply to the class as a team. We hold information sessions a month or more before the classes. Here students with preformed teams could come and have an interview with the teaching team and get admitted. Or those looking to find other students to join their team could mix and market their ideas or join others and then interview for a spot. This process moved the team logistics out of class time and provided us with more time for teaching.

But we had been selecting teams for admission on the basis of whether they had the best ideas. We should have known better.  In the classroom, as in startups, the best ideas in the hands of a B team is worse than a B idea in the hands of a world class team.

Here’s why.

Step Three – Hacker/Hardware, Hustler, Designer, Visionary
As we taught our Lean LaunchPad classes we painfully relearned the lesson that team composition matters as much or more than the product idea. And that teams matter as much in entrepreneurial classes as they do in startups.

 

In a perfect world you build your vision and your customers would run to buy your first product exactly as you spec’d and built it. We now know that this ‘build it and they will come” is a prayer rather than a business strategy.  In reality, a startup is a temporary organization designed to search for a repeatable and scalable business model. This means the brilliant idea you started with will change as you iterate and pivot your business model until you find product/market fit.

The above paragraph is worth reading a few times.

It basically says that a startup team needs to be capable of making sudden and rapid shifts – because it will be wrong a lot. Startups are inherently chaos. Conditions on the ground will change so rapidly that the original well-thought-out business plan becomes irrelevant.

And finding product/market fit in that chaos requires a team with a combination of skills.

What skills? Well it depends on the industry you’re in, but generally great technology skills (hacking/hardware/science) great hustling skills (to search for the business model, customers and market,) great user facing design (if you’re a web/mobile app,) and by having long term vision and product sense. Most people are good at one or maybe two of these, but it’s extremely rare to find someone who can wear all the hats.

It’s this combination of skills is why most startups are founded by a team, not just one person.

University Silos
While building these teams are hard in the real world, imagine how hard it is in a university with classes organized as silos. Business School classes were only open to business school students, Engineering School classes were only open to engineering school students, etc. No classes could be cross-listed. This meant that you couldn’t offer students an accurate simulation of what a startup team would look like. (In our business school classes we had students with great ideas but lacking the technical skills to implement it. And some of our engineering teams could have benefited from a role-model to follow as a hustler.)

So the next time we taught, we managed to ensure that the class was cross-listed and that the student teams had to have a mix of both business and engineering backgrounds.

I think we’ve finally got the team composition right – relearning all the lessons investors already knew.

But now on to the next goal – getting our mentor program correct.

Lessons Learned

  • Finding product/market fit in startup chaos requires a team with a combination of skills
  • Hacker/Hardware, Hustler, Designer, Visionary
  • At times an A+ market (huge demand, unmet need) may trump all
  • Getting the Mentors right is the next step

Listen to the post here: Download the Podcast here

You’ll Be Dead Soon – Carpe Diem

For the next few months I’ll be posting a series of posts on family, startup culture and careers. These vignettes are about how I’ve lived my life trying to make my dent in the universe and trying to teach others to do the same. I don’t expect you to agree with all the posts. (See the first post here.)

This second post in the series was written 15 years ago, but still relevant today.


Remembering that I’ll be dead soon is the most important tool I’ve ever encountered to help me make the big choices in life. Because almost everything – all external expectations, all pride, all fear of embarrassment or failure – these things just fall away in the face of death, leaving only what is truly important.

Steve Jobs

Watching an entrepreneur fail is sad but watching them fail from a lack of nerve is tragic.

Excitement
At the beginning of this year Bob, one of my ex-students was in entrepreneurial heaven. He had an idea for a new class of enterprise software insight-as-a-service based on big data web analytics as a Cloud/SaaS (Software As a Service) application.

Bob had taken to heart the business model canvas and Customer Development lessons. After graduating he put together a minimum viable product (MVP)and had quickly marched through Customer Discovery, iterating the MVP into a prototype with the help of CIOs and Fortune 1000 IT departments.

I had made one of the introductions to a Fortune 100 CIO so I got to hear his progress from both him and the CIO.

Takeoff
After 90 days, things seemed to be moving at startup speed. Bob had a backlog of users wanting to try his application, and the corporate IT people who were trying his early prototype said, “It’s crude, we hate the user interface, it’s missing lots of features – but we’ll kill you if you try to take it away from us.”

I pointed a VC who followed the space to the CIO who was testing the prototype. The VC told me the CIO wouldn’t get off the phone. He kept telling him he couldn’t remember when he had seen an enterprise software product with so much promise. The VC checked with other IT users and heard the same reaction. It was a “gotta use it, don’t take it away, we’ll have to buy it” product. After a demo and lunch, the VC (who normally did later stage deals) wrote my ex student a check for a seed round.

Life couldn’t be better.

I followed Bob’s progress in bits and pieces from updates from the CIO, the VC and his emails and blogs. He seemed to be on the fast track to startup success. But pretty soon a few worrying warning signs appeared.

The first thing that I noticed was that Bob couldn’t seem to find a co-founder. I wasn’t close enough to know if he wasn’t really looking for one, but given the early success he was having, it seemed a bit odd. But the next thing really got me concerned. Bob started hiring second rate developers. At best they were B- players.

Stall
A month went by, and the product stopped getting better. The U/I still sucked, and new features had stopped appearing. The next month, the same thing. I got a call from my CIO friend asking, “what was going on?” He said, “It was a great prototype, we would have loved to deploy it company-wide, and I hate to let it go, but it looks like Bob’s company just lost interest in developing it. I’m going to dump it and look for a substitute.” So I called Bob and suggested we grab a coffee.

I asked him how things were going and got the update on how the earlyvangelists were using the product. As I had heard, they were ecstatic. But Bob said he was worried he hadn’t found the right customer segment yet. “I’m not sure I can get all of these guys to pay me big bucks,” he said. “That’s why I stopped coding, and I’m spending all my time out in the field still talking to more customers.” “What does your VC say you ought to be doing?” I asked. “Oh, he hasn’t had much time for me, his firm almost never does seed deals. It turns out I was an exception.”  Oh, oh.

The conversation was starting to make the hair on the back of my neck stand up. Bob had gotten to a place most founders never do – his product was a “gotta have it for people with big budgets.” He should have been back rapidly coding, iterating and finding out what feature set would get him to paying customers.

Instead he had produced barely 3 weeks of progress in the last 5 months. His prototype was rapidly wearing out its welcome.

A Lack of Nerve
When I pressed Bob on this he admitted, “No I guess my engineers aren’t very good. But I hired guys who were cheap because I wasn’t sure if my hypotheses were right. Didn’t you tell us to test our hypotheses first?” Now it was my time to be surprised. “Bob, you’ve validated your hypotheses better than any startup I’ve ever seen. You found that out in the first month. You got customers begging you to finish the product so they could buy it. You should have been hiring world-class talent and building something these CIO’s will pay for. It’s not too late. It’s time to grab them by the throat and go for it.”

I wasn’t ready for the answer, “Steve, I’ve been reading all about premature scaling and making sure everything is right before I go for it. I want to be sure I get all of this right. I’m afraid I’ll run out of money.”

I thought I’d make one more run at it. “Bob,” I said, “few entrepreneurs get the first time response you have from an early product. At your rate you’re going to burn through your cash trying to get it perfect. It’s a startup. You’ll never have perfect information. You’re sitting on a gold mine. Grab the opportunity!”

I got a blank stare.

We made some more small talk and shook hands as he left.

Bob was in the wrong business, not the wrong market. He wanted certainty, comfort and security.

I stared at my coffee for a long time.

Carpe Diem – make your lives extraordinary.

Lessons Learned

  • Yes, premature scaling is a cause of startup death
  • Yes, you need to get out of the building and test your hypotheses
  • But, when an opportunity smacks you in the head for gosh sake grab it with both hands and don’t let go
  • If you can’t, get out of the startup game
  • Entrepreneurship is a calling for the fearless

Hiring – Easy as Pie

Over the last few weeks I’ve gotten involved in hiring for two startups, a public agency and a non profit.  Part of each conversation was getting asked to help them put together a “job spec.”

I had them leave with a pie chart.

——–

There must be something in the air. In the last week I had four separate groups through the ranch all wanting to talk either about hiring a senior exec or a senior exec looking for a new job. Having sat through these job discussions as an entrepreneur, board member, and now an interested observer, here’s what I concluded:

  1. Decide whether you’re hiring someone to help search for the business model or to help execute a business model you’ve already found (same is true is you’re looking for a job – are you going to be searching or executing?) Are you looking for a visionary or an operating executive?
  2. The job spec’s for the same title differ wildly depending on whether the job requires search versus execution skills. Founders search, operating executives execute.

If you’re hiring an operating executive (CEO, VP, Executive Director, etc.)

  • Don’t start with the candidate (board member x has a great VP of sales he knows, founder y wants this CEO he met at a conference, etc.)
  • Don’t even start with the job spec

Since I’ve always been a visual guy, job specs with their long lists of job requirements always left me cold. My eyes would glaze over at these recruiter/board wish lists. I wished there was a way to see them at a glance. (Just to be clear this isn’t the entire hiring process, just a way to visually begin the discussion.) So here’s my suggestion: Start with a Pie Chart.

  1. Draw a pie chart.
  2. List all the job specs as slices
  3. Adjust the width of the pie segments by importance. (Extra credit if you get the current CEO or internal candidate to help you write/draw the slices and weight their importance. Everyone involved in the hire gets to have an opinion on the slices and weights, but the person/group making the hiring decision gets to decide which ones to include.)
  4. Now that you have this spec, evaluate each candidate by showing his/her competence in each slice by length
  5. Compare candidates
  6. Easy as pie!

Lessons Learned

  • Are you hiring for search or execution skills?
  • Show the job requirements visually as a pie chart
  • Prioritize each requirement by the width of the pie
  • Show your assessment of each candidate’s competencies by the length of the slices
  • Now with the data in front of you, the conversation about hiring can start

Listen to the post here: Download the Podcast here

On Vacation

Exploring Spain.  Back soon.

 

The Internet Might Kill Us All

My friend Ben Horowitz and I debated the tech bubble in The Economist. An abridged version of this post was the “closing” statement to Ben’s rebuttal comments. Part 1 is here and Part 2 here.  The full version is below.

—————————————————
It’s been fun debating the question, “Are we in a tech bubble?” with my colleague Ben Horowitz. Ben and his partner Marc Andreessen (the founder of Netscape and author of the first commercial web browser on the Internet) are the definition of Smart Money. Their firm, Andreessen/Horowtiz, has been prescient enough to invest in social networks, consumer and mobile applications and the cloud long before others. They understood the ubiquity, pervasiveness and ultimate profitability of these startups and doubled-down on their investments.

My closing arguments are below. I’ve followed them with a few observations about the Internet that may help frame the scope of the debate.

Are we in the beginnings of a tech bubble – yes.
Prices for both private and public tech valuations exceed any rational valuation to their current worth. In 5 to 10 years most of them will be worth a fraction of their IPO price.  A few will be worth much, much more.

Is this tech bubble as broad as the 1995-2000 dot.com bubble – no.
While labeled the “dot.com” bubble, valuations went crazy across a wide range of technology sectors including telecommunications, enterprise software and biotech, not just the Internet.

Are tech bubbles necessarily bad – no.
A bubble is simply the redistribution of wealth from Marks to the Smart Money and Promoters. I hypothesize that unlike bubbles in other sectors  – tulips, Florida land prices, housing, financial – tech bubbles create lasting value. They finance companies that invest in new technologies, new ideas and new products. And it appears that at least in Silicon Valley, a larger percentage of money made in the last tech bubble is recirculated back into investments into the next generation of tech startups.

While most of the social networks, cloud computing, web and mobile app companies we see today will fail, a few will literally remake our lives.

Here are two views how.

The Internet May Liberate Us
In the last year, we’ve seen Social Networks enable new forms of peaceful revolution. To date, the results of Twitter and Facebook are more visible on the Arab Street than Wall Street.

One of the most effective weapons in the Cold War was the mimeograph machine and the VCR. The ability to copy and disseminate banned ideas undermined repressive regimes from Poland to Iran to the Soviet Union.

In the 21st century, authoritarian governments still fear their own people talking to each other and asking questions. When governments shut down Google, Twitter, Facebook, et al, they are building the 21st century equivalent of the Berlin Wall. They are admitting to the world that the forces of oppression can’t stand up to 140 characters of the truth.

When these governments build “homegrown” versions of these apps, the Orwellian prophecy of the Ministry of the Truth lives in each distorted or missing search result. Absent war, these regimes eventually collapse under their own weight. We can help accelerate their demise by building tools which allow people in these denied areas access to the truth.

Yet the same set of tools that will free hundreds of millions of people may end their lives in minutes.

The Internet May Kill Us
The next war will more than likely occur via the Internet. It may be over in minutes. We may be watching the first skirmishes.

In the 20th century, the economies of first-world countries became dependent on a reliable supply of food, water, electricity, transportation and telephone. Part of waging war was destroying that physical infrastructure. (The Combined Bomber Offensive of Germany and occupied Europe during WWII was designed to do just that.)

In the last few years, most first world countries have become dependent on the Internet as one of those critical parts of our infrastructure. We use the net in four different ways: 1) to control the physical infrastructure we built in the 20th century (food, water, electricity, transportation and communications); 2) as the network for our military interconnecting all our warfighting assets, from the mundane of logistics to command and control systems, weapons systems and targeting systems; 3) as commercial assets that exist or can operate only if the net exists including communication tools (email, Facebook, Twitter, etc.) and corporate infrastructure (Cloud storage and apps); 4) for our banking and financial systems.

Every day hackers demonstrate how weak the security of our corporate and government resources are. Stealing millions of credit cards occurs on a regular basis. Yet all of these are simply crimes not acts of war.

The ultimate in asymmetric warfare
In the 20th century, the United States was continually unprepared for an adversary using asymmetric warfare — the Japanese attack on Pearl Harbor, Soviet Anthrax warheads on their ICBMs during the cold war, Vietnam and guerilla warfare, and the 9/11 attacks.

While hacker attacks against banks and commercial institutions make good press, the most troubling portents of the next war were the Stuxnet attack on the Iranian centrifuge facilities, the compromise of the RSA security system and the penetration of American defense contractors. These weren’t Lulz or Anonymous hackers, these were attacks by government military projects with thousands of programmers coordinating their efforts. All had a single goal in mind: to prepare to use the internet to destroy a country without physically killing its people.

Our financial systems (banks, stock market, credit cards, mortgages, etc.) exist as bits.  Your net worth and mine exists because there are financial records that tell us how many “dollars” (or Euros, Yen, etc.) we own. We don’t physically have all that money. It’s simply the sum of the bits in a variety of institutions.

An attack on the United States could begin with the destruction of all those financial records. (A financial institution that can’t stop criminal hackers would have no chance against a military attack to destroy the customer data in their systems. Because security is expensive, hard, and at times not user friendly, the financial services companies have fought any attempt to mandate hardened systems.) Logic bombs planted on those systems will delete all the backups once they’re brought on-line. All of it gone.  Forever.

At the same time, all cloud-based assets, all companies applications and customer data will be attacked and deleted. All of it gone.  Forever.

Major power generating turbines will be attacked the same way Stuxnet worked— over and under-speeding the turbines and rapidly cycling the switching systems until they burn out.  A major portion of our electrical generation capacity will be off-line until replacements can be built. (They are currently built in China.)

Our transportation infrastructure– air traffic control systems, airline reservations, package delivery companies– will be hacked and our GPS infrastructure will be taken down (hacked, jammed or physically attacked.)

While some of our own military systems are hardened, attackers will shut down the soft parts of the military logistics and communications systems. Since our defense contractors have been the targets of some of the latest hacks, our newest weapons systems may not work, or worse if used, may have been reprogrammed to destroy our own assets.

An attacker may try to mask its identity by making the attack appear to come from a different source. With our nation in an unprecedented economic collapse, our ability to retaliate militarily against a nuclear-armed opponent claiming innocence and threatening a response while we face them with unreliable weapons systems could make for a bad day. Our attacker might even offer economic assistance as part of the surrender terms.

These scenarios make the question, “Are we in a tech bubble?” seem a bit ironic.

It Doesn’t Have to Happen
During the Cold War the United States and the Soviet Union faced off with an arsenal of strategic and tactical nuclear weapons large enough to directly kill hundreds of millions of people and plunge the planet in a “Nuclear Winter,” which could have killed billions more. But we didn’t do it. Instead, today the McDonalds in plazas labeled “Revolutionary Square” has been the victory parade for democracy and capitalism.

It may be that we will survive the threat of a Net War like we did the Cold War and that the Internet turns out to be the birth of a new spring for us all.
Listen to the post here Download the Podcast here