Skip to main content

How to Build the Best Predictive Analytics Team

Vinod Peris

Modern enterprise growth is heavily reliant on an organization's ability to assess past IT events to then look forward, anticipate and prevent service failures from happening. This is the crux of predictive analytics. Today's fast-moving enterprises have data and expertise locked up in siloed organizations, making it difficult to extract actionable insights, which inevitably impacts the scale, size and speed of a company's growth. 

There are two parts to successfully implementing a predictive analytics practice. The first is tech enabled: an open, scalable and unified way to collect, search, aggregate and analyze millions of metrics and logs across networks, infrastructure and applications. The second is talent enabled: finding the right skills to develop insights with domain-specific context for each business unit to carry forward.
 
The second part is one that most organizations struggle with. Do we build a dedicated, highly specialized team? Do we use a consultant or develop in-house talent? Do we train a cohort of non-IT employees on a licensed platform or do we reserve those capabilities solely for the IT department?

The following are steps to build the best predictive analytics team:

Identify the right representation of expertise

Just like building an app requires a marriage of design experts and full stack developers, a good analytics team needs to start with a mix of domain experts and data scientists. Once they have established some of the basic parameters, you can integrate developers into the mix. Depending on how accessible the data is, developers could provide data scientists with the tools to run the most optimal machine learning algorithms.

Use existing in-house talent and build additional support

There isn't always a need for a separate "predictive analytics team." Integrate data scientists into the functional teams and provide them with access to the data and ensure they can consult with domain experts. If you have multiple groups across the company, create an overlay team (or guild) of data scientists so that they have a forum for knowledge sharing, especially on the latest developments in AI/ML.

Recruit unconventional talent

Data scientists are in high demand, and while it's easier to find them in the hot tech markets of Silicon Valley and Boston, you will face tough competition in attracting and retaining new talent. So, rather than looking in traditional fields like Computer Science and Statistics, cast a wider net to include quantitative fields like Physics, Chemistry, Economics, Biostatistics, etc.

Set a framework to iterate upon

1. Assess the problem.

2. Compile and correlate all relevant data to the said problem.

3. Identify all needed tools for analyzing the data (machine learning, etc.)

4. Make data available to domain experts so you can evaluate the results and iterate on the assumptions.

Include employees outside of the tech walls

Once you have initial results, take the time to share and validate it across the organization. Input from support and services will go a long way in validating the results and gaining further insight into the data. For example, if a company is seeking to improve customer renewal health, share the dashboards/results that you generate with the customer success team so that they utilize this knowledge to improve renewals. Validate the outcome and make tweaks to improve the end-to-end process.

A notable value of predictive analytics is the ability to identify trends and patterns and to formulate different questions. These outputs will inevitably require more analysis and lead you down the path of discovery. So, the more cohesive and responsive your predictive analytics team is, the more poised your company is for dynamic growth.

Hot Topics

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

How to Build the Best Predictive Analytics Team

Vinod Peris

Modern enterprise growth is heavily reliant on an organization's ability to assess past IT events to then look forward, anticipate and prevent service failures from happening. This is the crux of predictive analytics. Today's fast-moving enterprises have data and expertise locked up in siloed organizations, making it difficult to extract actionable insights, which inevitably impacts the scale, size and speed of a company's growth. 

There are two parts to successfully implementing a predictive analytics practice. The first is tech enabled: an open, scalable and unified way to collect, search, aggregate and analyze millions of metrics and logs across networks, infrastructure and applications. The second is talent enabled: finding the right skills to develop insights with domain-specific context for each business unit to carry forward.
 
The second part is one that most organizations struggle with. Do we build a dedicated, highly specialized team? Do we use a consultant or develop in-house talent? Do we train a cohort of non-IT employees on a licensed platform or do we reserve those capabilities solely for the IT department?

The following are steps to build the best predictive analytics team:

Identify the right representation of expertise

Just like building an app requires a marriage of design experts and full stack developers, a good analytics team needs to start with a mix of domain experts and data scientists. Once they have established some of the basic parameters, you can integrate developers into the mix. Depending on how accessible the data is, developers could provide data scientists with the tools to run the most optimal machine learning algorithms.

Use existing in-house talent and build additional support

There isn't always a need for a separate "predictive analytics team." Integrate data scientists into the functional teams and provide them with access to the data and ensure they can consult with domain experts. If you have multiple groups across the company, create an overlay team (or guild) of data scientists so that they have a forum for knowledge sharing, especially on the latest developments in AI/ML.

Recruit unconventional talent

Data scientists are in high demand, and while it's easier to find them in the hot tech markets of Silicon Valley and Boston, you will face tough competition in attracting and retaining new talent. So, rather than looking in traditional fields like Computer Science and Statistics, cast a wider net to include quantitative fields like Physics, Chemistry, Economics, Biostatistics, etc.

Set a framework to iterate upon

1. Assess the problem.

2. Compile and correlate all relevant data to the said problem.

3. Identify all needed tools for analyzing the data (machine learning, etc.)

4. Make data available to domain experts so you can evaluate the results and iterate on the assumptions.

Include employees outside of the tech walls

Once you have initial results, take the time to share and validate it across the organization. Input from support and services will go a long way in validating the results and gaining further insight into the data. For example, if a company is seeking to improve customer renewal health, share the dashboards/results that you generate with the customer success team so that they utilize this knowledge to improve renewals. Validate the outcome and make tweaks to improve the end-to-end process.

A notable value of predictive analytics is the ability to identify trends and patterns and to formulate different questions. These outputs will inevitably require more analysis and lead you down the path of discovery. So, the more cohesive and responsive your predictive analytics team is, the more poised your company is for dynamic growth.

Hot Topics

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...