With this in mind, 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 challenge
American businessman
Showing quotes in randomized order to avoid selection bias. Click Popular for most popular quotes.
As success drives the need to hire new engineers at a rapid rate, companies neglect to train the new engineers properly. As the engineers are assigned tasks, they figure out how to complete them as best they can. Often this means replicating existing facilities in the architecture, which leads to inconsistencies in the user experience, performance problems, and a general mess. And you thought training was expensive.
One interview technique that I’d used to sort the good from the bad was to ask a series of questions about hiring, training, and managing sales reps. Typically, it would go like this: Ben: “What do you look for in a sales rep?” Candidate: “They need to be smart, aggressive, and competitive. They need to know how to do complex deals and navigate organizations.” Ben: “How do you test for those things in an interview?” Candidate: “Umm, well, I hire everybody out of my network.” Ben: “Okay, once you get them on board, what do you expect from them?” Candidate: “I expect them to understand and follow the sales process, I expect them to master the product, I expect them to be accurate in their forecasting. . . .” Ben: “Tell me about the training program that you designed to achieve this.” Candidate: “Umm.” They would then proceed to make something up as they went along.
People offer many complex reasons for why Bill rates so highly. In my experience it’s pretty simple. No matter who you are, you need two kinds of friends in your life. The first kind is one you can call when something good happens, and you need someone who will be excited for you. Not a fake excitement veiling envy, but a real excitement. You need someone who will actually be more excited for you than he would be if it had happened to him. The second kind of friend is somebody you can call when things go horribly wrong — when your life is on the line and you only have one phone call. Who is it going to be? Bill Campbell is both of those friends.
An early lesson I learned in my career was that whenever a large organization attempts to do anything, it always comes down to a single person who can delay the entire project. An engineer might get stuck waiting for a decision or a manager may think she doesn’t have authority to make a critical purchase. These small, seemingly minor hesitations can cause fatal delays. I could not afford any hesitation, so I scheduled a daily meeting with Anthony, Jason, and the team — though they were now based in Plano. The purpose was to remove all roadblocks.
Works in ChatGPT, Claude, or Any AI
Add semantic quote search to your AI assistant via MCP. One command setup.
As a venture capitalist, I have had the freedom to say what I want and what I really think without worrying what everybody else thinks. As a CEO, there is no such luxury. As CEO, I had to worry about what everybody else thought. In particular, I could not show weakness in public. It would not have been fair to the employees, the executives, or the public company shareholders. Unrelenting confidence was necessary.
Be aware that management books tend to be written by management consultants who study successful companies during their times of peace. As a result, the resulting books describe the methods of peacetime CEOs. In fact, other than the books written by Andy Grove, I don’t know of any management books that teach you how to manage in wartime like Steve Jobs or Andy Grove.
THE FINE LINE BETWEEN FEAR AND COURAGE “I tell my kids, what is the difference between a hero and a coward? What is the difference between being yellow and being brave? No difference. Only what you do. They both feel the same. They both fear dying and getting hurt. The man who is yellow refuses to face up to what he’s got to face. The hero is more disciplined and he fights those feelings off and he does what he has to do. But they both feel the same, the hero and the coward. People who watch you judge you on what you do, not how you feel.” — CUS D’AMATO, LEGENDARY BOXING TRAINER