Once we pushed the Opsware stock price back above $1, the next problem was to rebuild the executive team. We had cloud services executives, but now w… - Ben Horowitz

In enterprise software companies, the two most important positions tend to be VP of sales and VP of engineering.

I managed the team to a set of numbers that did not fully capture what I wanted. I wanted a great product that customers would love with high quality and on time — in that order. Unfortunately, the metrics that I set did not capture those priorities. At a basic level, metrics are incentives. By measuring quality, features, and schedule and discussing them at every staff meeting, my people focused intensely on those metrics to the exclusion of other goals. The metrics did not describe the real goals and I distracted the team as a result.

Once we assembled the entire package, Mike named it Netscape SuiteSpot, as it would be the “suite” that displaced Microsoft’s BackOffice. We lined everything up for a major launch on March 5, 1996, in New York. Then, just two weeks before the launch, Marc, without telling Mike or me, revealed the entire strategy to the publication Computer Reseller News. I was livid. I immediately sent him a short email: To: Marc Andreessen Cc: Mike Homer From: Ben Horowitz Subject : Launch I guess we’re not going to wait until the 5th to launch the strategy. — Ben Within fifteen minutes, I received the following reply. To: Ben Horowitz Cc: Mike Homer, Jim Barksdale (CEO), Jim Clark (Chairman) From: Marc Andreessen Subject: Re: Launch Apparently you do not understand how serious the situation is. We are getting killed killed killed out there. Our current product is radically worse than the competition. We’ve had nothing to say for months. As a result, we’ve lost over $3B in market capitalization. We are now in danger of losing the entire company and it’s all server product management’s fault. Next time do the fucking interview yourself. Fuck you, Marc I received this email the same day that Marc appeared barefoot and sitting on a throne on the cover of Time magazine. When I first saw the cover, I felt thrilled. I had never met anyone in my life who had been on the cover of Time. Then I felt sick. I brought both the magazine and the email home to Felicia to get a second opinion. I was very worried. I was twenty-nine years old, had a wife and three children, and needed my job. She looked at the email and the magazine cover and said, “You need to start looking for a job right away.” In the end, I didn’t get fired and over the next two years, SuiteSpot grew from nothing to a $400 million a year business. More shocking, Marc and I eventually became friends; we’ve been friends and business partners ever since. People often ask me how we’ve managed to work effectively across three companie

here are the basic steps to organizational design: 1. Figure out what needs to be communicated. Start by listing the most important knowledge and who needs to have it. For example, knowledge of the product architecture must be understood by engineering, QA, product management, marketing, and sales. 2. Figure out what needs to be decided. Consider the types of decisions that must get made on a frequent basis: feature selection, architectural decisions, how to resolve support issues. How can you design the organization to put the maximum number of decisions under the domain of a designated manager? 3. Prioritize the most important communication and decision paths. Is it more important for product managers to understand the product architecture or the market? Is it more important for engineers to understand the customer or the architecture? Keep in mind that these priorities will be based on today’s situation. If the situation changes, then you can reorganize. 4. Decide who’s going to run each group. Notice that this is the fourth step, not the first. You want to optimize the organization for the people — for the people doing the work — not for the managers. Most large mistakes in organizational design come from putting the individual ambitions of the people at the top of the organization ahead of the communication paths for the people at the bottom of the organization. Making this step four will upset your managers, but they will get over it. 5. Identify the paths that you did not optimize. As important as picking the communication paths that you will optimize is identifying the ones that you will not. Just because you deprioritized them doesn’t mean they are unimportant. If you ignore them entirely, they will surely come back to bite you. 6. Build a plan for mitigating the issues identified in step five. Once you’ve identified the likely issues, you will know the processes you will need to build to patch the impending cross-organizational challenges.