Ben Horowitz Quotes

Enforce functional training by withholding new employee requisitions. As Andy Grove writes, there are only two ways for a manager to improve the output of an employee: motivation and training. Therefore, training should be the most basic requirement for all managers in your organization. An effective way to enforce this requirement is by withholding new employee requisitions from managers until they’ve developed a training program for the TBH, “To Be Hired.

NO PERFORMANCE MANAGEMENT OR EMPLOYEE FEEDBACK PROCESS Your company now employs twenty-five people and you know that you should formalize the performance management process, but you don’t want to pay the price. You worry that doing so will make it feel like a “big company.” Moreover, you do not want your employees to be offended by the feedback, because you can’t afford to lose anyone right now. And people are happy, so why rock the boat? Why not take on a little management debt? The first noticeable payments will be due when somebody performs below expectations: CEO: “He was good when we hired him; what happened?” Manager: “He’s not doing the things that we need him to do.” CEO: “Did we clearly tell him that?” Manager: “Maybe not clearly . . .” However, the larger payment will be a silent tax. Companies execute well when everybody is on the same page and everybody is constantly improving. In a vacuum of feedback, there is almost no chance that your company will perform optimally across either dimension. Directions with no corrections will seem fuzzy and obtuse. People rarely improve weakness they are unaware of. The ultimate price you will pay for not giving feedback: systematically crappy company performance.

A good practice is to have the employee send you the agenda in advance. This will give her a chance to cancel the meeting if nothing is pressing.

a bunch of high-IQ people with the wrong kind of ambition won’t work.

Once inside AOL, I was assigned to run the e-commerce platform and Marc became the chief technology officer. After a few months, it became apparent to both of us that AOL saw itself as more of a media company than a technology company. Technology enabled great new media projects, but the strategy was a media strategy and the top executive, Bob Pittman, was a genius media executive. Media companies focused on things like creating great stories whereas technology companies focused on creating a better way of doing things. We began to think about new ideas and about forming a new company.

The only thing that prepares you to run a company is running a company.

As a result, I grew up in the city affectionately known by its inhabitants as the People’s Republic of Berkeley.

All the mental energy you use to elaborate your misery would be far better used trying to find the one seemingly impossible way out of your current mess. Spend zero time on what you could have done, and devote all of your time on what you might do. Because in the end, nobody cares; just run your company.

there’s no recipe for motivating teams when your business has turned to crap.

Mark Zuckerberg believes in innovation and he believes there can be no great innovation without great risk. So, in the early days of Facebook, he deployed a shocking motto: Move fast and break things. Did the CEO really want us to break things? I mean, he’s telling us to break things! A motto that shocking forces everyone to stop and think. When they think, they realize that if you move fast and innovate, you will break things. If you ask yourself, “Should I attempt this breakthrough? It will be awesome, but it may cause problems in the short term,” you have your answer. If you’d rather be right than innovative, you won’t fit in at Facebook.

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.

After eight years of running Loudcloud and Opsware, I had learned so many hard lessons that building the team was easy. I understood the importance of hiring for strength rather than for lack of weakness, and I understood the meaning of “fit.

To really understand how this stuff works, I knew I had to dig deeper. So I asked myself, How many of the following questions can be resolved by turning to your corporate goals or mission statement? Is that phone call so important I need to return it today, or can it wait till tomorrow? Can I ask for a raise before my annual review? Is the quality of this document good enough or should I keep working on it? Do I have to be on time for that meeting? Should I stay at the Four Seasons or the Red Roof Inn? When I negotiate this contract, what’s more important: the price or the partnership? Should I point out what my peers do wrong, or what they do right? Should I go home at 5 p.m. or 8 p.m.? How hard do I need to study the competition? Should we discuss the color of this new product for five minutes or thirty hours? If I know something is badly broken in the company, should I say something? Whom should I tell? Is winning more important than ethics?

how Loudcloud was born. Interestingly, the most lasting remnant of Loudcloud is the name itself, as the word cloud hadn’t been previously used to describe a computing platform. We incorporated the company and set out to raise money. It was 1999.

Even if you know what you are doing, things go wrong. Things go wrong because building a multifaceted human organization to compete and win in a dynamic, highly competitive market turns out to be really hard.