Here are some of the practices that can help organizations go from exploration and evaluation to implementation, so they can start deriving value from all machine learning has to offer.
1. Introduce more specialized machine learning roles
New roles—such as data ops specialists and machine learning engineers, who specialize in building and deploying machine learning models—are starting to stick. In fact, nearly 40% of sophisticated organizations have a designated ML engineer, double the number of organizations just getting started.
Not surprisingly, organizations with more experience deploying machine learning models to production are more likely to use these newer job titles, which also include data scientist, data engineer, and deep-learning engineer.
If history is any indication, the emergence of machine learning-specific roles is indicative of the hype around the technology. Just take the role of data scientist, for example: The title was coined around 2008 to describe practitioners who worked on data projects, and now more than half of all companies surveyed have hired for this role. Organizations that are hiring for machine learning roles now and putting resources behind its deployment will be better poised for the future of business.
2. Implement specific machine learning success metrics
Less experienced organizations rely more on product managers or executives to determine the criteria for machine learning project success, but sophisticated organizations entrust their data science leads to set team priorities. Additionally, respondents who belong to the most advanced organizations are likely to use multiple success metrics, which may include business metrics, ML metrics, and statistical metrics, and they measure for bias and fairness.
For example, over half (54%) of respondents who belong to sophisticated companies check for fairness and bias, compared to less than a third (32%) of companies that are just starting out.
This is another indication of how machine learning adoption introduces challenges that diverge from the standard practices of software engineering—and thus there's a need for leaders who can navigate the waters. This type of expertise helps organizations set parameters and build better models that generate better business results.
3. Approach machine learning model building differently
As machine learning becomes more widely used, many organizations are adapting the processes they've used in software development to build data products, such as agile methodology and Kanban. However, some experts have pointed out failures in those approaches and offer advice about how to work around them.
A key mindset shift required to address these issues involves understanding that machine learning model development is different from software development. As such, completion of the machine learning model-building process doesn't automatically translate to a working system.
The data community is still building tools to help manage the entire lifecycle, which also includes model deployment, monitoring, and operations. While tools and best practices are just beginning to emerge and be shared, it's still early days for model lifecycle management.
4. Build robust model-building checklists
Organizations that have extensive experience in deploying machine learning models have much more robust model-building checklists than their peers, already including checks for transparency and data privacy. In fact, 53% of respondents who belong to companies with extensive experience in ML check for privacy. Fortunately, for most organizations getting started, new regulations coincide with the rise of tools and methods for privacy-preserving analytics and ML.
Thus in a nutshell, Machine learning has enormous potential, but in order to reap the benefits, it's important to put your organization in a position to take advantage of all of it. By hiring for machine learning-specific roles and leadership, implementing success metrics, and building robust model-building checklists, your organization can start to advance on its machine learning journey. Now the next question is how to adopt How to Adopt Machine Learning? This we'll discuss in the next post.
1. Introduce more specialized machine learning roles
New roles—such as data ops specialists and machine learning engineers, who specialize in building and deploying machine learning models—are starting to stick. In fact, nearly 40% of sophisticated organizations have a designated ML engineer, double the number of organizations just getting started.
Not surprisingly, organizations with more experience deploying machine learning models to production are more likely to use these newer job titles, which also include data scientist, data engineer, and deep-learning engineer.
If history is any indication, the emergence of machine learning-specific roles is indicative of the hype around the technology. Just take the role of data scientist, for example: The title was coined around 2008 to describe practitioners who worked on data projects, and now more than half of all companies surveyed have hired for this role. Organizations that are hiring for machine learning roles now and putting resources behind its deployment will be better poised for the future of business.
2. Implement specific machine learning success metrics
Less experienced organizations rely more on product managers or executives to determine the criteria for machine learning project success, but sophisticated organizations entrust their data science leads to set team priorities. Additionally, respondents who belong to the most advanced organizations are likely to use multiple success metrics, which may include business metrics, ML metrics, and statistical metrics, and they measure for bias and fairness.
For example, over half (54%) of respondents who belong to sophisticated companies check for fairness and bias, compared to less than a third (32%) of companies that are just starting out.
This is another indication of how machine learning adoption introduces challenges that diverge from the standard practices of software engineering—and thus there's a need for leaders who can navigate the waters. This type of expertise helps organizations set parameters and build better models that generate better business results.
3. Approach machine learning model building differently
As machine learning becomes more widely used, many organizations are adapting the processes they've used in software development to build data products, such as agile methodology and Kanban. However, some experts have pointed out failures in those approaches and offer advice about how to work around them.
A key mindset shift required to address these issues involves understanding that machine learning model development is different from software development. As such, completion of the machine learning model-building process doesn't automatically translate to a working system.
The data community is still building tools to help manage the entire lifecycle, which also includes model deployment, monitoring, and operations. While tools and best practices are just beginning to emerge and be shared, it's still early days for model lifecycle management.
4. Build robust model-building checklists
Organizations that have extensive experience in deploying machine learning models have much more robust model-building checklists than their peers, already including checks for transparency and data privacy. In fact, 53% of respondents who belong to companies with extensive experience in ML check for privacy. Fortunately, for most organizations getting started, new regulations coincide with the rise of tools and methods for privacy-preserving analytics and ML.
Thus in a nutshell, Machine learning has enormous potential, but in order to reap the benefits, it's important to put your organization in a position to take advantage of all of it. By hiring for machine learning-specific roles and leadership, implementing success metrics, and building robust model-building checklists, your organization can start to advance on its machine learning journey. Now the next question is how to adopt How to Adopt Machine Learning? This we'll discuss in the next post.
0 comments:
Post a Comment