Hi. [inaudible]. Is it having really terrific ideas? Well, when we get a new idea, we're excited about it. We want to tell everybody. We want to render it into software, so it can be magically successful. But the reality is a lot of the time, that idea is not that good or it's not ready yet to be rendered into software, and we crash and burn. Is it being really technical and code savvy? Well, that will help you certainly engaged to the details, but your job isn't to tell your developers how to do their job, your job if you're the product person is to do your job really well and create an environment where they can be successful. So by itself, this isn't the answer either. The answer is grinding it out. We go out. We talk to users in a very specific way. So we learn what is on their alias, what's important to them. We test our propositions, our solutions before we go build them, so that we make sure we're not going to build something no one wants. We organize that in actionable ways for a development team, and that's how we get to our happy place, and we get there as a team. Let's talk about how to do this. Well, in the venture design process, we move in this particular sequence because as you go along, your options are going to decrease, your costs are going to go up. Now, that is just the nature of developing software systems, but you want to make sure that you've maximized your opportunities to understand your user, to test your ideas, so you increase your odds of building something that's valuable. Now, in the specialization, we'll show you how to do that. In Course 1, we'll show you how to humanize your customer or your user with personas and learn what's on their a list by using problem scenarios. So you don't build something nobody wants, and we'll show you how to bring that forward into better user stories and prototypes to drive better more purposeful discussions and better more purposeful action with your team. In Course 2, running design sprints, we'll show you how to use one week design sprints to go research those personas and problem scenarios. Number two, to go out and test motivation. In the third type of design sprint, we'll show you how to test usability, and in the fourth, we'll show you how to look at architectural alternatives and consider those who make good decisions about how to build your product. In Course 3, we'll show you how to use a lot of these things you probably heard about in relation to Agile, like stand-ups, and methodologies like XP and Scrum, and we'll show you how to evaluate those against the fundamental jobs of software development rather than just rattling through them. So that you can decide which are most applicable or most likely to be applicable to your project, your team, your particular situation. In Course 4, we'll show you how to create a culture of experimentation. Nothing will more reliably improve your practice of Agile than testing everything, whether that's an idea about how to be delivering something valuable to your user or making your practice of Agile better. Testing that will help you manage the uncertainty inherent in any software execution, so that uncertainty doesn't manage you. I hope that you will consider joining me for this specialization. Thanks.