Until you make the effort to get to know someone or something, you don’t know anything. There are no shortcuts to knowledge, especially knowledge gained from personal experience. Following conventional wisdom and relying on shortcuts can be worse than knowing nothing at all.
The simple existence of an alternate, plausible scenario is often all that’s needed to keep hope alive among a worried workforce.
They scheduled an appointment and presented me with a slide deck detailing why my decision to start Oxide was quixotic, misguided, and downright stupid. They argued that it would steal precious resources from our core business while pursuing a product that would surely fail. I let them present all forty-five slides without my asking them a single question. When they finished I said, “Did I ask for this presentation?” Those were the first words I spoke as I made the transition from a peacetime CEO to a wartime CEO.
He said, “You need to stay home and make sure everybody knows where they stand. You can’t wait a day. In fact, you can’t wait a minute. They need to know whether they are working for you, EDS, or looking for a fucking job.” Damn. He was right. I sent Marc to New York and prepared to let people know where they stood. That small piece of advice from Bill proved to be the foundation we needed to rebuild the company. If we hadn’t treated the people who were leaving fairly, the people who stayed would never have trusted me again. Only a CEO who had been through some awful, horrible, devastating circumstances would know to give that advice at that time.
Early in my career as an engineer, I’d learned that all decisions were objective until the first line of code was written. After that, all decisions were emotional.
Startup CEOs should not play the odds. When you are building a company, you must believe there is an answer and you cannot pay attention to your odds of finding it. You just have to find it. It matters not whether your chances are nine in ten or one in a thousand; your task is the same.
Parcells: “Al, I am just not sure how we can win without so many of our best players. What should I do?” Davis: “Bill, nobody cares, just coach your team.” That might be the best CEO advice ever. Because, you see, nobody cares. When things go wrong in your company, nobody cares. The media don’t care, your investors don’t care, your board doesn’t care, your employees don’t care, and even your mama doesn’t care. Nobody cares.
My old boss Jim Barksdale was fond of saying, “We take care of the people, the products, and the profits—in that order.”
GOOD PRODUCT MANAGER/BAD PRODUCT MANAGER Good product managers know the market, the product, the product line, and the competition extremely well and operate from a strong basis of knowledge and confidence. A good product manager is the CEO of the product. Good product managers take full responsibility and measure themselves in terms of the success of the product. They are responsible for right product/right time and all that entails. A good product manager knows the context going in (the company, our revenue funding, competition, etc.), and they take responsibility for devising and executing a winning plan (no excuses). Bad product managers have lots of excuses. Not enough funding, the engineering manager is an idiot, Microsoft has ten times as many engineers working on it, I’m overworked, I don’t get enough direction. Our CEO doesn’t make these kinds of excuses and neither should the CEO of a product. Good product managers don’t get all of their time sucked up by the various organizations that must work together to deliver the right product at the right time. They don’t take all the product team minutes; they don’t project manage the various functions; they are not gofers for engineering.
They are not part of the product team; they manage the product team. Engineering teams don’t consider good product managers a “marketing resource.” Good product managers are the marketing counterparts to the engineering manager. Good product managers crisply define the target, the “what” (as opposed to the “how”), and manage the delivery of the “what.” Bad product managers feel best about themselves when they figure out “how.” Good product managers communicate crisply to engineering in writing as well as verbally. Good product managers don’t give direction informally. Good product managers gather information informally.
Good product managers create collateral, FAQs, presentations, and white papers that can be leveraged by salespeople, marketing people, and executives. Bad product managers complain that they spend all day answering questions for the sales force and are swamped. Good product managers anticipate the serious product flaws and build real solutions. Bad product managers put out fires all day. Good product managers take written positions on important issues (competitive silver bullets, tough architectural choices, tough product decisions, and markets to attack or yield). Bad product managers voice their opinions verbally and lament that the “powers that be” won’t let it happen. Once bad product managers fail, they point out that they predicted they would fail. Good product managers focus the team on revenue and customers. Bad product managers focus the team on how many features competitors are building.…
Good product managers think in terms of delivering superior value to the marketplace during product planning and achieving market share and revenue goals during the go-to-market phase. Bad product managers get very confused about the differences among delivering value, matching competitive features, pricing, and ubiquity. Good product managers decompose problems. Bad product managers combine all problems into one. Good product managers think about the story they want written by the press. Bad product managers think about covering every feature and being absolutely technically accurate with the press. Good product managers ask the press questions. Bad product managers answer any press question. Good product managers assume members of the press…
Good product managers err on the side of clarity. Bad product managers never even explain the obvious. Good product managers define their job and their success. Bad product managers constantly want to be told what to do. Good product managers send their status reports in on time every week, because they are disciplined. Bad product…
Valuing lack of weakness rather than strength The more experience you have, the more you realize that there is something seriously wrong with every employee in your company (including you). Nobody is perfect.
People rarely improve weakness they are unaware of.
Build strict processes for potentially political issues and do not deviate. Certain activities attract political behavior. These activities include: Performance evaluation and compensation Organizational design and territory Promotions
When someone raises an issue like this with you, you must be very careful about what you say, because everything that you say can be turned into political cannon fodder. Generally, it’s best to say nothing at all. At most, you might ask “why?” but if you do so be sure not to react to the reasons. If you indicate what you are thinking, that information will leak, rumors will spread, and you plant the seeds for all kinds of unproductive discussions.
Do not attempt to address behavioral issues without both executives in the room. Doing so will invite manipulation and politics.
Some questions that I’ve found to be very effective in one-on-ones: If we could improve in any way, how would we do it? What’s the number-one problem with our organization? Why? What’s not fun about working here? Who is really kicking ass in the company? Whom do you admire? If you were me, what changes would you make? What don’t you like about the product? What’s the biggest opportunity that we’re missing out on? What are we not doing that we should be doing? Are you happy working here?
The world is full of bankrupt companies with world-class cultures. Culture does not make a company.
Focus on the road, not the wall. When someone learns to drive a race car, one of the first lessons taught is that when you are going around a curve at 200 mph, do not focus on the wall; focus on the road. If you focus on the wall, you will drive right into it. If you focus on the road, you will follow the road. Running a company is like that. There are always a thousand things that can go wrong and sink the ship. If you focus too much on them, you will drive yourself nuts and likely crash your company. Focus on where you are going rather than on what you hope to avoid.