Like technical debt, management debt comes in too many different forms to elaborate entirely, but a few salient examples will help explain the concep… - Ben Horowitz

As we thought about what would make us both better and different, two core ideas greatly influenced our thinking: First, technical founders are the best people to run technology companies. All of the long-lasting technology companies that we admired — Hewlett-Packard, Intel, Amazon, Apple, Google, Facebook — had been run by their founders. More specifically, the innovator was running the company. Second, it was incredibly difficult for technical founders to learn to become CEOs while building their companies. I was a testament to that. But, most venture capital firms were better designed to replace the founder than to help the founder grow and succeed. Marc and I thought that if we created a firm specifically designed to help technical founders run their own companies, we could develop a reputation and a brand that might vault us into the top tier of venture capital firms despite having no track record. We identified two key deficits that a founder CEO had when compared with a professional CEO: 1. The CEO skill set Managing executives, organizational design, running sales organizations and the like were all important skills that technical founders lacked. 2. The CEO network Professional CEOs knew lots of executives, potential customers and partners, people in the press, investors, and other important business connections. Technical founders, on the other hand, knew some good engineers and how to program.

The key to a good one-on-one meeting is the understanding that it is the employee’s meeting rather than the manager’s meeting. This is the free-form meeting for all the pressing issues, brilliant ideas, and chronic frustrations that do not fit neatly into status reports, email, and other less personal and intimate mechanisms. If you are an employee, how do you get feedback from your manager on an exciting but only 20 percent formed idea that you’re not sure is relevant, without sounding like a fool? How do you point out that a colleague you do not know how to work with is blocking your progress without throwing her under the bus? How do you get help when you love your job but your personal life is melting down? Through a status report? On email? Yammer? Asana? Really? For these and other important areas of discussions, one-on-ones can be essential. If you like structured agendas, then the employee should set the agenda. 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. It also makes clear that it is her meeting and will take as much or as little time as she needs. During the meeting, since it’s the employee’s meeting, the manager should do 10 percent of the talking and 90 percent of the listening. Note that this is the opposite of most one-on-ones.

a high quality human resources organization cannot make you a well-managed company with a great culture, but it can tell you when you and your managers are not getting the job done.