#37 Machine Learning Engineering for Production (MLOps) Specialization [Course 1, Week 3, Lesson 13]

An instructor walks through scoping AI projects: start with business problems, brainstorm AI and non-AI solutions, assess feasibility and ROI, then set milestones and budget. E-commerce examples show how search quality, recommendations, and demand prediction map to concrete business goals like increasing conversions and reducing inventory.
Chapters
I'd like to share with you a process for scoping projects that I hope will be valuable for how you decide what to work on. When I'm speaking with a company for the first time about their AI projects, this is the process that I use as well. Let's dive in when brainstorming projects to work on, the first thing I do is usually get together with a business or product owner. Often not an AI person, but someone that understands a business or an application, and to brainstorm with them what are their business or application problems. And at this stage I'm trying to identify a business problem, not an AI problem. So if I'm speaking with a econ retail business, like the example from the previous video, I might ask what are the top few things, top three things you wish were working better? And maybe they'll share business problems like they'd like to increase conversions, number of people that go to the website and convert to a sale, or or reduce inventory so you don't need as much stuff sitting around in a warehouse or increase margin, increase the profit per item sold. At this point in the process, I'm not trying to identify an AI problem. In fact, I'll often tell my partners I don't want to hear about your AI problems, I want to hear about your business problems. And then it's my job to work with you to see if there is an AI solution. And sometimes there isn't, and that's fine too. Feel free to use the exact same words as well when brainstorming projects with your non AI partners if you want. Having identified a few business problems like the three examples on the right, only then do I see or start to brainstorm if there are possible AI solutions. Not all problems can be solved by AI, and that's okay, but hopefully we'll come up with some ideas for using machine learning algorithms to address some of the business problems. I find that it's helpful for this process to separate out the identification of the problem from the identification of the solution. As engineers, we are pretty good at coming up with solutions, but having a clear articulation of what is the problem first often helps us come up with better solutions. This type of separation between problem and solution is something you might hear about in the writings on design thinking as well. After brainstorming a variety of different solutions, I would then assess the feasibility and the value of these different solutions. Sometimes you hear me use the word diligence to refer to this phrase. Diligence is a term that actually comes from the legal field, but it basically means double checking if an AI solution really is technically feasible and valuable, or double checking if something that you're hoping is true really is true. After validating technical feasibility and the value or ROI return on investments of a given project. If it still looks promising. If it still looks promising, we then flesh out the milestones for the project and finally budget for resources. Let's take a deeper look at this process of identifying problems and solutions and we'll use these three examples from Ecom. So the first one Increase Conversion if a business wants to increase conversions, you may have different ideas for doing that. For example, you may want to improve the quality of the website's search results so people find more relevant products when they search. Or you might decide to try to offer up better product recommendations based on their purchase history. It is quite common that one problem may lead to multiple ideas for solutions, and you may be able to brainstorm other ideas as well, such as maybe a redesign of how products are displayed on a page. Or you may find interesting ways to surface the most relevant product reviews to help users understand the product and thus hopefully purchase it. So there could be many ways to increase conversions. Take the next problem from the previous slide of reducing inventory. Maybe you will. You could imagine a demand prediction project to better estimate how many people buy something from you so you don't purchase too many or too few and have more accurate inventory in your warehouses. Or you may decide to come up with a marketing campaign to drive sales for specifically the products that you bought too many of so as to steer more purchases of stuff sitting in your warehouse. And that could also reduce inventory. And there could be many other ideas for solutions or for the problem of increasing margin. You may come up with some ways to use machine learning to optimize what to sell, what is worth selling, and what is not worth selling. In econ retail, sometimes this is called merchandising, just deciding what to sell. Or you can recommend bundles where if someone buys a camera they maybe you can recommend to them a protective camera case. And these bundles can also increase margin the problem identification is a step of thinking through what are the things you want to achieve, and solution identification is a process of thinking through how to achieve those objectives. One thing I still see too many teams do today is jump into the first project that they're excited about. In my experience, if you have deep domain knowledge about an application or industry, maybe the first thing your gut gets excited about could be okay. But even then I find it worthwhile to first engage in divergent thinking where you brainstorm a lot of possibilities to be followed by convergent thinking, where you then narrow it down to one or a small handful of the most promising projects to focus on. One thing I hope you might avoid is working really hard on a project and creating a certain amount of monetary or social value. If for the same amount of work, there's a different project that could have created 10 times more, you know, monetary or social or other positive types of value, and I think this type of scoping process will help you to do that.










