3 ms·
>How to effectively communicate the progress to non-engineer team members? The TL;DR is use the confusion matrix output from the ML library you're using to dem
by proverbialbunny 6y ago
>How to effectively communicate the progress to non-engineer team members?
The TL;DR is use the confusion matrix output from the ML library you're using to demonstrate model accuracy, false positives, false negatives, and so on.
The long answer is much more complex: Are you doing MLE work? DE work? DS work? Why are you using ML? Is it required for your current project? You haven't stated what kind of work you're doing. How you present has to do with what kind of work you're doing, so a clear answer can not be given, only a generic one.
A data scientist, for example, typically has to sit in tons of meetings hearing the business challenges over and over again, finding a way to solve the business problems, and then building a model to demonstrate feasibility and then proof of concept. They then presentation this proof of concept to sales, marketing, management, the board, or whoever else it pertains to as a way to solve their problems in an automated fashion with such-en-such percent of accuracy using a confusion matrix. The business then ruminates on this and then often comes up with more requests or modifications to the initial model, or a request to improve accuracy, or they're satisfied. When the model is satisfactory it gets handed off to a software engineer (machine learning engineer, data engineer, infrastructure engineer) who then takes their ideals and developts it onto a server and gets it connected up so that the customers end up getting that service. The engineers built it / put it all together in the end. The data scientist researched it.
Your situation sounds like you were thrown into a data scientist role and are approaching it like a software engineer, which is not an ideal way to go about things. I could be wrong. It could be the other way where you shouldn't be using ML to solve the problem, or you're productionizing other people's models. If you're truly doing engineer work, then you can show that customers are getting the service you're providing, which is a different kind of presentation, typically just updating management, not having a large company wide thing. Maybe you're expected to be management? That's a different story too.