Advanced Search Filters
Filter search results by source, date, and more with our premium search tools.
" "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
Ben Horowitz (born June 13, 1966) is an American businessman, investor, blogger, and author.
Biography information from Wikiquote
Filter search results by source, date, and more with our premium search tools.
Related quotes. More quotes will automatically load as you scroll down, or you can use the load more buttons.
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.
Chat naturally about what you need. Each answer links back to real quotes with citations.