Dennis Ashby

“I felt like I had no more stories, no more speeches, and no more “rah-rah” in me. I decided to level with the team and see what happened. I called an all engineering meeting and gave the following speech: “I have some bad news. We are getting our asses kicked by BladeLogic and it’s a product problem. If this continues, I am going to have to sell the company for cheap. There is no way for us to survive if we don’t have the winning product. So, I am going to need every one of you to do something. I need you to go home tonight and have a serious conversation with your wife, husband, significant other, or whoever cares most about you and tell them, ‘Ben needs me for the next six months.’ I need you to come in early and stay late. I will buy you dinner, and I will stay here with you. Make no mistake, we have one bullet left in the gun and we must hit the target.” At the time, I felt horrible asking the team to make yet another big sacrifice. Amazingly, I found out while writing this book that I probably should have felt good about it. Here’s what Ted Crossman, one of my best engineers, said about that time and the launch of the aptly named Darwin Project many years later: Of all the times I think of at Loudcloud and Opsware, the Darwin Project was the most fun and the most hard. I worked seven days a week 8 a.m.–10 p.m. for six months straight. It was full on. Once a week I had a date night with my wife where I gave her my undivided attention from 6 p.m. until midnight. And the next day, even if it was Saturday, I’d be back in the office at 8 a.m. and stay through dinner. I would come home between 10–11 p.m. Every night. And it wasn’t just me. It was everybody in the office. The technical things asked of us were great. We had to brainstorm how to do things and translate those things into an actual product. It was hard, but fun. I don’t remember losing anyone during that time. It was like, “Hey, we gotta get this done, or we will not be here, we’ll have to get another job.” It was a tight-knit group of people. A lot of the really junior people really stepped up. It was a great growing experience for them to be thrown into the middle of the ocean and told, “Okay, swim.” Six months later we suddenly started winning proofs of concepts we hadn’t before. Ben did a great job, he’d give us feedback, and pat people on the back when we were done.”
― Ben Horowitz, The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers—Straight Talk on the Challenges of Entrepreneurship