Inspiring Tech Quotes

If you are on social media, and you are not learning, not laughing, not being inspired or not networking, then you are using it wrong.

We need teams of missionaries, not teams of mercenaries.

5 Ways To Build Your Brand on Social Media: 1 Post content that add value 2 Spread positivity 3 Create steady stream of info 4 Make an impact 5 Be yourself

It's easier for a rich man to ride that camel through the eye of a needle directly into the Kingdom of Heaven, than for some of us to give up our cell phone.

Tweet others the way you want to be tweeted.

If you are in a position where you can reach people, then use your platform to stand up for a cause. HINT: social media is a platform.

Just because you have baggage doesn't mean you have to lug it around.

Further, your industry is constantly moving, and we must create products for where the market will be tomorrow, not where it was yesterday.

A full-out rebellion would take a major amount of luck and coordination. The Tech Nos and Domotor looked at me, waiting. No one else would be able to organize both sides. I drew in a deep breath. We had the technology, the intelligence and the people—put enough sheep together and you have a herd, a force to be reckoned with. We needed a leader.

I can't believe that we have reached the end of everything. The red dust is frightening. The carbon dioxide is real. Water is expensive. Bio-tech has created as many problems as it has fixed, but we're here, we're alive, we're the human race, we have survived wars and terrorism and scarcity and global famine, and we have made it back from the brink, not once but many times. History is not a suicide note - it's a record of our survival.

Don't bore the universe.

There are worse things than dying." "Really?" said Meg. "Of course," said the tech. "Living badly.

I’m not standard; I’m deviant. But I’m not alone. I’m a complete freak of nature, and I emerged from a set of circumstances that are improbable on an astronomic scale. The same is probably true for you too.

The little secret in product is that engineers are typically the best single source of innovation; yet, they are not even invited to the party in this process.

Fall in love with the problem, not with the solution.

What you're really seeing is Agile for delivery, but the rest of the organization and context is anything but Agile.

The nation once idolized astronauts and civil rights leaders who inspired hope and empathy. Now it worships tech innovators who generate billions and move financial markets. We get the heroes we deserve.

Finally, it's all about solving problems, not implementing features. Conventional product roadmaps are all about output. Strong teams know it's not only about implementing a solution. They must ensure that solution solves the underlying problem. It's about business results.

If you are not embarrassed or ashamed of your first version then you are shipping too late’.

The difference between Amazon, Netflix, Google, Facebook, and the legions of large but slowly dying companies is usually exactly that: product leadership.

That is, there are two essential high‐level activities in all product teams. We need to discover the product to be built, and we need to deliver that product to market.

Historically, in the vast majority of innovations in our industry, the customers had no idea that what they now love was even a possibility.

No matter what your title or level may be, if you aspire to be great, don't be afraid to lead.

Rather than being measured on the output of their design work, the product designer is measured on the success of the product.

one of the most critical lessons in product is knowing what we can't know,

product managers are constantly asking developers to look at the code to tell them how the system really works, then you're probably missing a principal product manager.

I was just a kid growing up in Jamaica with dreams, and I want people to know that it’s possible to dream bigger and accomplish those dreams.

In the model I'm describing, it is management's responsibility to provide each product team with the specific business objectives they need to tackle. The difference is that they are now prioritizing business results, rather than product ideas. And, yes, it is more than a little ironic that we sometimes need to convince management to focus on business results.

The first truth is that at least half of our ideas are just not going to work. There are many reasons for an idea to not work out. The most common is that customers just aren't as excited about this idea as we are.

Where the product vision describes the future you want to create, and the product strategy describes your path to achieving that vision, the product principles speak to the nature of the products you want to create.

To summarize, these are the four critical contributions you need to bring to your team: deep knowledge (1) of your customer, (2) of the data, (3) of your business and its stakeholders, and (4) of your market and industry.

Why would I what?” Will asked, wanting another bite of his burger. “Why would you risk your job teaching some stupid fantasy book?” “Because alternative universe literature promotes critical thinking, imagination, empathy, and creative problem solving. Children who are fluent in fiction are more able to interpret nonfiction and are better at understanding things like basic cause and effect, sociology, politics, and the impact of historical events on current events. Many of our technological advances were imagined by science fiction writers before the tech became available to create them, and many of today’s inventors were inspired by science fiction and fantasy to make a world more like the world in the story. Many of today’s political conundrums were anticipated by science fiction writers like Orwell, Huxley, and Heinlein, and sci-fi and fantasy tackle ethical problems in a way that allows people to analyze the problem with some emotional remove, which is important because the high emotions are often what lead to violence. Works like Harry Potter tackle the idea of abuse of power and—” Will stopped himself and swallowed. Everybody at the table, including Kenny, was staring at him in openmouthed surprise. “Anyway,” he said before taking a monster bite of his cooling hamburger on a sudden attack of nerves, “iss goomfer umf.” “It’s good for us,” Kenny translated, sounding a little stunned

We say if you're just using your engineers to code, you're only getting about half their value. The little secret in product is that engineers are typically the best single source of innovation; yet, they are not even invited to the party in this process.

The racial oppression that inspired the first generations of the civil rights movement was played out in lynchings, night raids, antiblack pogroms, and physical intimidation at the ballot box. In a typical battle of today, it may consist of African American drivers being pulled over more often on the highways. (When Clarence Thomas described his successful but contentious 1991 Supreme Court confirmation hearing as a “high-tech lynching,” it was the epitome of tastelessness but also a sign of how far we have come.) The oppression of women used to include laws that allowed husbands to rape, beat, and confine their wives; today it is applied to elite universities whose engineering departments do not have a fifty-fifty ratio of male and female professors. The battle for gay rights has progressed from repealing laws that execute, mutilate, or imprison homosexual men to repealing laws that define marriage as a contract between a man and a woman. None of this means we should be satisfied with the status quo or disparage the efforts to combat remaining discrimination and mistreatment. It’s just to remind us that the first goal of any rights movement is to protect its beneficiaries from being assaulted or killed. These victories, even if partial, are moments we should acknowledge, savor, and seek to understand.

Good teams get their inspiration and product ideas from their vision and objectives, from observing customers' struggle, from analyzing the data customers generate from using their product, and from constantly seeking to apply new technology to solve real problems. Bad teams gather requirements from sales and customers.

Where a lot of novice product people go sideways is when they create a high‐fidelity user prototype and they put it in front of 10 or 15 people who all say how much they love it. They think they've validated their product, but unfortunately, that's not how it works. People say all kinds of things and then go do something different.

If the first time your developers see an idea is at sprint planning, you have failed. We need to ensure the feasibility before we decide to build, not after. Not only does this end up saving a lot of wasted time, but it turns out that getting the engineer's perspective earlier also tends to improve the solution itself, and it's critical for shared learning.

Advances in technology can be empowering, progressive and enriching. History has shown this across civilisations and societies. But it has also shown, and the present and future will continue to show, that it is foolish, risky, flawed and folly without us raising our individual and collective consciousness and mindfulness to accompany it - to ensure we use it shrewdly, kindly and wisely.

a quote from John Doerr, the famous Silicon Valley venture capitalist: “We need teams of missionaries, not teams of mercenaries.” Mercenaries build whatever they're told to build. Missionaries are true believers in the vision and are committed to solving problems for their customers. In a dedicated product team, the team acts and feels a lot like a startup within the larger company, and that's very much the intention.

A bilo je to itekako dražesno, smatrala je Mary. Nekako je humanije, promatrati različite rukopise, različite tinte, različite načine na koje bi netko nekad nešto krivo napisao. Bio je to vizualni ekvivalent razgovora, svatko bi u zapisu ostavio nešto sebi svojstveno, unikatno - za razliku od unosa uvijek istih, provjerenih natipkanih riječi. Međutim, to je donekle otežavalo traženje neke određene bilješke ili napomene. S druge strane, iščitavanje svega od početka moglo bi vam pomoći da primijetite nešto što vam je možda ranije promaknulo.

The Objectives and Key Results (OKR) technique is a tool for management, focus, and alignment. As with any tool, there are many ways to use it. Here are the critical points for you to keep in mind when using the tool for product teams in product organizations. Objectives should be qualitative; key results need to be quantitative/measurable. Key results should be a measure of business results, not output or tasks. The rest of the company will use OKRs a bit differently, but for the product management, design, and technology organization, focus on the organization's objectives and the objectives for each product team, which are designed to roll up and achieve the organization's objectives. Don't let personal objectives or functional team objectives dilute or confuse the focus.

The unfortunate truth is that right now men's voices dominate and we see the results. Popular products from the tech boom - including violent and sexist video games that a generation of children has become addicted to - are designed with little to no input from women. Apple's first version of its highly touted health application could track your blood-alcohol level but not menstruation. Everything from plus-sized smart phones to artificial hearts have been build at a size better suited to male anatomy. As of late 2016, if you told one of the virtual assistants like Siri, S Voice, and Google Now, 'I'm having a heart attack,' you'd immediately get valuable information about what to do next. If you were to say, 'I'm being raped,' or 'I'm being abused by my husband,' the attractive (usually) female voice would say, 'I don't understand what this is.

Initially working out of our home in Northern California, with a garage-based lab, I wrote a one page letter introducing myself and what we had and posted it to the CEOs of twenty-two Fortune 500 companies. Within a couple of weeks, we had received seventeen responses, with invitations to meetings and referrals to heads of engineering departments. I met with those CEOs or their deputies and received an enthusiastic response from almost every individual. There was also strong interest from engineers given the task of interfacing with us. However, support from their senior engineering and product development managers was less forthcoming. We learned that many of the big companies we had approached were no longer manufacturers themselves but assemblers of components or were value-added reseller companies, who put their famous names on systems that other original equipment manufacturers (OEMs) had built. That didn't daunt us, though when helpful VPs of engineering at top-of-the-food-chain companies referred us to their suppliers, we found that many had little or no R & D capacity, were unwilling to take a risk on outside ideas, or had no room in their already stripped-down budgets for innovation. Our designs found nowhere to land. It became clear that we needed to build actual products and create an apples-to-apples comparison before we could interest potential manufacturing customers. Where to start? We created a matrix of the product areas that we believed PAX could impact and identified more than five hundred distinct market sectors-with potentially hundreds of thousands of products that we could improve. We had to focus. After analysis that included the size of the addressable market, ease of access, the cost and time it would take to develop working prototypes, the certifications and metrics of the various industries, the need for energy efficiency in the sector, and so on, we prioritized the list to fans, mixers, pumps, and propellers. We began hand-making prototypes as comparisons to existing, leading products. By this time, we were raising working capital from angel investors. It's important to note that this was during the first half of the last decade. The tragedy of September 11, 2001, and ensuing military actions had the world's attention. Clean tech and green tech were just emerging as terms, and energy efficiency was still more of a slogan than a driver for industry. The dot-com boom had busted. We'd researched venture capital firms in the late 1990s and found only seven in the United States investing in mechanical engineering inventions. These tended to be expansion-stage investors that didn't match our phase of development. Still, we were close to the famous Silicon Valley and had a few comical conversations with venture capitalists who said they'd be interested in investing-if we could turn our technology into a website. Instead, every six months or so, we drew up a budget for the following six months. Via a growing network of forward-thinking private investors who could see the looming need for dramatic changes in energy efficiency and the performance results of our prototypes compared to currently marketed products, we funded the next phase of research and business development.

Let's start at the top—the source of ideas. This model leads to sales‐driven specials and stakeholder‐driven products. Lots more to come on this key topic, but for now, let me just say that this is not the source of our best product ideas. Another consequence of this approach is the lack of team empowerment. In this model, they're just there to implement—they're mercenaries.

Likewise, we have no idea what it will cost to build. Without knowing the actual solution, this is extremely hard for engineering to predict. Most experienced engineers will refuse to even give an estimate at this stage, but some are pressured into the old t‐shirt sizing compromise—just let us know if this is “small, medium, large, or extra large.

First, collaboration is built on relationships, and product teams—especially co‐located teams—are designed to nurture these relationships. Second, to innovate you need expertise, and the durable nature of product teams lets people go deep enough to gain that expertise. Third, instead of just building what others determine might be valuable, in the product team model the full team understands—needs to understand—the business objectives and context. And most important, the full team feels ownership and responsibility for the outcome.

Principles of Product Vision These are the 10 key principles for coming up with an effective product vision. Start with why. This is coincidentally the name of a great book on the value of product vision by Simon Sinek. The central notion here is to use the product vision to articulate your purpose. Everything follows from that. Fall in love with the problem, not with the solution. I hope you've heard this before, as it's been said many times, in many ways, by many people. But it's very true and something a great many product people struggle with. Don't be afraid to think big with vision. Too often I see product visions that are not nearly

ambitious enough, the kind of thing we can pull off in six months to a year or so, and not substantial enough to inspire anyone. Don't be afraid to disrupt yourselves because, if you don't, someone else will. So many companies focus their efforts on protecting what they have rather than constantly creating new value for their customers. Fall in love with the problem, not with the solution. The product vision needs to inspire. Remember that we need product teams of missionaries, not mercenaries. More than anything else, it is the product vision that will inspire missionary‐like passion in the organization. Create something you can get excited about. You can make any product vision meaningful if you focus on how you genuinely help your users and customers.

Determine and embrace relevant and meaningful trends. Too many companies ignore important trends for far too long. It is not very hard to identify the important trends. What's hard is to help the organization understand how those trends can be leveraged by your products to solve customer problems in new and better ways. Skate to where the puck is heading, not to where it was. An important element to product vision is identifying the things that are changing—as well as the things that likely won't be changing—in the time frame of the product vision. Some product visions are wildly optimistic and unrealistic about how fast things will change, and others are far too conservative. This is usually the most difficult aspect of a good product vision. Be stubborn on vision but flexible on the details. This Jeff Bezos line is very important. So many teams give up on their product vision far too soon. This is usually called a vision pivot, but mostly it's a sign of a weak product organization. It is never easy, so prepare yourself for that. But, also be careful you don't get attached to details. It is very possible that you may have to adjust course to reach your desired destination. That's called a discovery pivot, and there's nothing wrong with that. Realize that any product vision is a leap of faith. If you could truly validate a vision, then your vision probably isn't ambitious enough. It will take several years to know. So, make sure what you're working on is meaningful, and recruit people to the product teams who also feel passionate about this problem and then be willing to work for several years to realize the vision.

Evangelize continuously and relentlessly. There is no such thing as over‐communicating when it comes to explaining and selling the vision. Especially in larger organizations, there is simply no escaping the need for near‐constant evangelization. You'll find that people in all corners of the company will at random times get nervous or scared about something they see or hear. Quickly reassure them before their fear infects others.

Principles of Product Strategy As we discussed previously, there are any number of approaches to product strategy, but good strategies have these five principles in common: Focus on one target market or persona at a time. Don't try to please everyone in a single release. Focus on one new target market, or one new target persona, for each release. You'll find that the product will still likely be useful to others, but at least it will be loved by some, and that's key. Product strategy needs to be aligned with business strategy. The vision is meant to inspire the organization, but the organization ultimately is there to come up with solutions

that deliver on the business strategy. So, for example, if that business strategy involves a change in monetization strategy or business model, then the product strategy needs to be aligned with this. Product strategy needs to be aligned with sales and go‐to‐market strategy. Similarly, if we have a new sales and marketing channel, we need to ensure that our product strategy is aligned with that new channel. A new sales channel or go-to-market strategy can have far-reaching impact on a product. Obsess over customers, not over competitors. Obsess over customers, not over competitors. Too many companies completely forget about their product strategy once they encounter a serious competitor. They panic and then find themselves chasing their competitor's actions and no longer focusing on their customers. We

can't ignore the market, but remember that customers rarely leave us for our competitors. They leave us because we stop taking care of them. Communicate the strategy across the organization. This is part of evangelizing the vision. It's important that all key business partners in the company know the customers we're focused on now and which are planned for later. Stay especially closely synced with sales, marketing, finance, and service.

As an example, early on at eBay we found we needed a product principle that spoke to the relationship between buyers and sellers. Most of the revenue came from sellers, so we had a strong incentive to find ways to please sellers, but we soon realized that the real reason sellers loved us was because we provided them with buyers. This realization led to a critical principle that stated, “In cases where the needs of the buyers and the sellers conflict, we will prioritize the needs of the buyer, because that's actually the most important thing we can do for sellers.

create their own OKRs for their own organization. For example, the design department might have objectives related to moving to a responsive design; the engineering department might have objectives related to improving the scalability and performance of the architecture; and the quality department might have objectives relating to the test and release automation. The problem is that the individual members of each of these functional departments are the actual members of a cross‐functional product team. The product team has business‐related objectives (for example, to reduce the customer acquisition cost, to increase the number of daily active users, or to reduce the time to onboard a new customer), but each person on the team may have their own set of objectives that cascade down through their functional manager. Imagine if the engineers were told to spend their time on re‐platforming, the designers on moving to a responsive design, and QA on retooling. While each of these may be worthy activities, the chances of solving the business problems that the cross‐functional teams were created to solve are not high.

free-range discovery could inspire innovation no one could foresee, at equally unforeseen market velocity.

First we lose, then we win in Life." Recently many people in the IT and Tech sectors are facing a difficult phase of their life. I had similarly faced a difficult phase in the Finance sector in the year 2008. We all have gone through failures in life. But that should not stop us from trying for success. Staying hopeful and working toward our goals bring us an opportunity to achieve success.

It is not only about Tech.. It is also about imagination!

The purpose of product discovery is to address these critical risks: Will the customer buy this, or choose to use it? (Value risk) Can the user figure out how to use it? (Usability risk) Can we build it? (Feasibility risk) Does this solution work for our business? (Business viability risk)

They saw me as an “Important Manager” at an “Important Company,” whereas the colleagues who’d started out with me at New York Tech just saw me as Ed. As my position changed, people became more careful how they spoke and acted in my presence. I don’t think that my actions changed in a way that prompted this; my position did. And what this meant was that things I’d once been privy to became increasingly unavailable to me. Gradually, snarky behavior, grousing, and rudeness disappeared from view—from my view, anyway. I rarely saw bad behavior because people wouldn’t exhibit it in front of me.

For that particular session, everyone said they picked it because of the word entitled in the descriptor. They’d all encountered people who acted entitled at Pixar—people who insisted on having their own piece of equipment, even if it could be shared, or who groused that they couldn’t bring their dogs to work. “This is a job,” one animator said. “A great job. We are well paid. These people need to wake up.” What was most striking to those in attendance at the “Great Workplace” session was how much they had in common. The Systems guy told a story about answering a frantic call for tech support. He rushed over to assess the problem, only to be told by the aggrieved artist that the machine should be fixed during lunch—because that’s when it would be most convenient for her. “I need to eat lunch, too,” he told the group, as everyone nodded their heads. The chef told a similar story about a last-minute request to cater a working lunch that came without any acknowledgement of the hassle (and hustle) it would require of her staff.

Product evangelism is, as Guy Kawasaki put it years ago, “selling the dream.” It's helping people imagine the future and inspiring them to help create that future. If you're a startup founder, a CEO, or a head of product, this is a very big part of your job, and you'll have a hard time assembling a strong team if you don't get good at it.

A strong product culture means that the team understands the importance of continuous and rapid testing and learning. They understand that they need to make mistakes in order to learn, but they need to make them quickly and mitigate the risks. They understand the need for continuous innovation. They know that great products are the result of true collaboration. They respect and value their designers and engineers. They understand the power of a motivated product team. A strong VP product will understand the importance of a strong product culture, be able to give real examples of her own experiences with product culture, and have concrete plans for instilling this culture in your company.

A product team is a group of people who bring together different specialized skills and responsibilities and feel real ownership for a product or at least a substantial piece of a larger product.

When a product succeeds, it's because everyone on the team did what they needed to do. But when a product fails, it's the product manager's fault.

If the product manager doesn't have the technology sophistication, doesn't have the business savvy, doesn't have the credibility with the key executives, doesn't have the deep customer knowledge, doesn't have the passion for the product, or doesn't have the respect of their product team, then it's a sure recipe for failure.

it is management's responsibility to provide each product team with the specific business objectives they need to tackle. The difference is that they are now prioritizing business results, rather than product ideas. And, yes, it is more than a little ironic that we sometimes need to convince management to focus on business results.

The difference between vision and strategy is analogous to the difference between good leadership and good management. Leadership inspires and sets the direction, and management helps get us there.

The idea behind business objectives is simple enough: tell the team what you need them to accomplish and how the results will be measured, and let the team figure out the best way to solve the problems.

The purpose of product discovery is to address these critical risks: Will the customer buy this, or choose to use it? (Value risk) Can the user figure out how to use it? (Usability risk) Can we build it? (Feasibility risk) Does this solution work for our business? (Business viability risk) And it's not enough that it's just the product manager's opinion on these questions. We need to collect evidence.

unless I knew the product would be something that users and customers wanted.

Our work is important but rarely is it the most important thing in our lives. Companies usually survive just fine without your putting in those extra twenty hours when you could be eating dinner with your family, sleeping, or going for a run. By hiring employees with different lives and different work styles, tech companies could engender new perspectives and creativity. And they would give employees the ability to have a longer-term perspective, not just for their own lives, but for whatever product they're rolling out.

CHAPTER 12 The Engineers In this chapter, I describe the engineering role (also commonly known as developers or, in some circles, programmers). But as with the last chapter, I'm not trying to speak here to the engineers—I'm aiming this discussion at product managers who need to learn how to work effectively with engineers. There's probably no more important relationship for a successful product manager than the one with your engineers. If your relationship is strong, with mutual and sincere respect both ways, then the product manager job is great. If your relationship is not strong, your days as product manager will be brutal (and probably numbered). Therefore, this is a relationship worth taking very seriously and doing everything you can to nurture. This strong relationship begins with you.

Realize that any product vision is a leap of faith. If you could truly validate a vision, then your vision probably isn't ambitious enough. It will take several years to know. So, make sure what you're working on is meaningful, and recruit people to the product teams who also feel passionate about this problem and then be willing to work for several years to realize the vision.

group

We need teams of missionaries, not teams of mercenaries.” Mercenaries build whatever they're told to build. Missionaries are true believers in the vision and are committed to solving problems for their customers.

They are empowered to figure out the best way to meet those objectives, and they are accountable for the results.

will tell you there's never a perfect way to carve up the pie. Realize that, when you optimize for one thing, it comes at the expense of something else. So, decide what's most important to you and go with that.

There are essentially three ways for a product manager to work, and I argue only one of them leads to success: The product manager can escalate every issue and decision up to the CEO. In this model, the product manager is really a backlog administrator. Lots of CEOs tell me this is the model they find themselves in, and it's not scaling. If you think the product manager job is what's described in a Certified Scrum Product Owner class, you almost certainly fall into this category. The product manager can call a meeting with all the stakeholders in the room and then let them fight it out. This is design by committee, and it rarely yields anything beyond mediocrity. In this model, very common in large companies, the product manager is really a roadmap administrator. The product manager can do his or her job. The honest truth is that the product manager needs to be among the strongest talent in the company. My intention in this book is to convince you of this third way of working. It will take me the entire book to describe how the strong product manager does his or her job, but let me just say for now that this is a very demanding job and requires a strong set of skills and strengths.

Every business depends on customers. And what customers buy—or choose to use—is your product. The product is the result of what the product team builds, and the product manager is responsible for what the product team will build.

The successful product manager must be the very best versions of smart, creative, and persistent.

By persistent, I mean pushing companies way beyond their comfort zone with compelling evidence, constant communication, and building bridges across functions in the face of stubborn resistance.

preparation for this role. Start by becoming an expert in your users and customers. Share very openly what you learn, both the good and the bad. Become your team's and your company's go‐to person for understanding anything about your customer—quantitative and qualitative. Work to establish a strong relationship with your key stakeholders and business partners. Convince them of two things: (1) You understand the constraints they operate under. (2) You will only bring to them solutions that you believe will work within those constraints. Become an undisputed expert on your product and your industry. Again, share your knowledge openly and generously. Finally, work very hard to build and nurture the strong collaborative relationship with your product team. I'm

If, for example, your company provides a two‐sided marketplace with buyers on one side and sellers on the other, there are real advantages to having some teams focus on buyers and others focus on sellers. Each product team can go very deep with their type of customers rather than have them try to learn about all types of customers.

There are a few product teams out there that have modified their product roadmaps so that each item is stated as a business problem to solve rather than the feature or project that may or may not solve it. These are called outcome‐based roadmaps.

Product Vision and Strategy The product vision is what drives and inspires the company and sustains the company through the ups and downs. This may sound straightforward, but it's tricky. That's because there are two very different types of product leaders needed for two very different situations: Where there is a CEO or a founder who is the clear product visionary Where there is no clear product visionary—usually in situations where the founder has moved on

Most important, the product vision should be inspiring, and the product strategy should be focused.

The MVP should be a prototype, not a product. Building an actual product‐quality deliverable to learn, even if that deliverable has minimal functionality, leads to substantial waste of time and money, which of course is the antithesis of Lean. I find that using the more general term prototype makes this critical point clear to the product team, the company, and the prospective customers. So, in this book, I talk about different types of prototypes being used in discovery and products being produced in delivery.

John Doerr, the famous Silicon Valley venture capitalist: “We need teams of missionaries, not teams of mercenaries.” Mercenaries build whatever they're told to build. Missionaries are true believers in the vision and are committed to solving problems for their customers.

In product companies, it is critical that the product manager also be the product owner.

The hallmark of a great CTO is a commitment to continually strive for technology as a strategic enabler for the business and the products. Removing technology as a barrier, as well as broadening the art of the possible for business and product leaders, is the overarching objective.

Just because someone can use our product doesn't mean they will choose to use our product.

strong product teams understand these truths and embrace them rather than deny them. They are very good at quickly tackling the risks (no matter where that idea originated) and are fast at iterating to an effective solution. This is what product discovery is all about, and it is why I view product discovery as the most important core competency of a product organization.

It is management's responsibility to provide each product team with the specific business objectives they need to tackle.

The key is to understand that the root cause of all this grief about commitments is when these commitments are made. They are made too early. They are made before we know whether we can deliver on this obligation, and even more important, whether what we deliver will solve the problem for the customer.

The difference between vision and strategy is analogous to the difference between good leadership and good management. Leadership inspires and sets the direction, and management helps get us there. Most important, the product vision should be inspiring, and the product strategy should be focused.

The first truth is that at least half of our ideas are just not going to work.

the winning solutions didn't come from users, customers, or sales. Rather, great products require an intense collaboration with design and engineering to solve real problems for your users and customers, in ways that meet the needs of your business. In each of these examples, the users had no idea the solution they fell in love with was possible.

It's what I call the two inconvenient truths about product.

Strong tech‐product companies know they need to ensure consistent product innovation. This means constantly creating new value for their customers and for their business.