AI needs data to function. Project management often involves using AI to assess risks, plan for the future, or schedule your workforce. Without accurate data, you won’t get accurate results - meaning you might under-budget, or ignore project threatening risks.
CTO for data science and AI at IBM, Deborah Leff, considers a lack of data as one of the main reasons projects fail. She states that “I’ve had data scientists look me in the face and say we could do that project, but we can’t get access to the data”.
It’s not enough to simply have unstructured, unorganised data. When it’s siloed between teams, stored in the wrong format, or simply lost, it means you don’t have the mature, wide-ranging, and accurate data you need. Implementing a data first strategy prevents this - and means that your teams won’t run into the problem Leff mentions.
What data do you need?
It’s important to understand what data you actually need. You don’t want to keep irrelevant information, and you also don’t want to throw away potentially valuable files. The quickest way to work this out is to ask a simple question: what do I want this data for?
For instance, if you’re looking for project completion estimates, then you’re likely to need time logs from previous projects rather than, say, customer service call logs! Ensuring you understand what you need means any AI you implement will have the right data to draw from, helping lead your projects in the right direction.
What is data maturity and what impact does it have on AI for project management?
According to Gartner, only 1 in 10 companies manage to get 75% or more of their AI projects into production. There are three major barriers to success: data accessibility, data scope and quality, and data volume. The concept of ‘data maturity’ covers all of these issues, and can help businesses keep track of how well they’re doing with their strategies.
What is data maturity?
Data maturity is a way of considering a company’s relationship with data. It’s not just about the quality or amount of data, either. Instead, it encompasses storage, analysis, security, and every other aspect of that relationship. There are a few ways to measure the maturity level, but we’ll be looking at TDWI’s.
In TDWI’s model, the level are:
This level is where companies new to handling data, or those who pay little attention to it, tend to sit. Businesses at this level don’t understand how to use data, provide no support to anyone intending to use it, and frequently lose or discard data.
With no long term plan, companies would struggle to make use of AI in PM - there’s no foundation to build on, and no infrastructure in place.
This step is very similar to the nascent stage, with many of the above problems still in place. However, the company is taking an active interest in using big data and analytics. They may be using external consultants, hiring new staff, and investing in new technology.
Pre-existing data is likely to be assessed, cleaned-up and stored appropriately. However, the company culture is yet to shift and there is no overarching structure or system in place.
3. Early adoption
Reaching this step is key to getting a data first strategy underway. At this stage, at least one executive-level staff member is involved and supportive. Teams working on company data are provided with the money, resources, and staff that they might need. However, companies may encounter conflicting goals between project managers and their data analysts, or project managers and the C-Suite.
Early adopters will have the relevant infrastructure in place. This means existing data can be given structure, with standardised naming systems, formats, and metadata . Most importantly, data is no longer discarded or lost. Research has started into improving data quality and security, but nothing has been fully implemented.
Between this stage and the next comes something known as the ‘chasm’ - the leap from small-scale adoption to company-wide adoption. It requires a culture change, significant investment, and perhaps most importantly, long term goals and strategies.
4. Corporate adoption
After the chasm comes corporate adoption. At this point, businesses have hired the right staff, designed a company-wide structure for data, and developed long term goals and strategies and it is feasible to implement AI. Project managers have access to comprehensive data sets, as well as the requisite staff to use them. Due to a clear data life cycle, strong data governance policies, and an active search for relevant data, AI has a sufficient foundation to build on.
Key to this stage is the company wide culture shift that happens - data-driven strategies become the norm, and end-users begin to get involved with data. It’s no longer the realm of a single team or specialist. Instead, it’s a key part of the business.
5. Mature / visionary
This level is tricky to reach, but that doesn’t mean businesses shouldn’t aim for it. A mature company has all the facets of one at the previous stage, but goes beyond it. The key difference is that these companies focus on continuous improvement. Whilst a company at the previous level may be content with a working solution, visionary companies seek out new and innovative technologies and tactics.
What are the risks of low data maturity?
As you can see from the five maturity levels, low levels come with a number of risks. Low data maturity will impact any part of the business that uses data - or analytics based upon it. The risks include:
Financial loss and reduced productivity
There are many ways poor data quality can cost a business money. Gartner’s Data Quality Market Survey estimates the average per year is $15 million. A lack of centralised infrastructure leads to inefficiencies, potentially leading multiple teams to repeat the same tasks, and poor security can lead to breaches. Overall, low data maturity is costly and time consuming.
As we noted, implementing AI before the corporate adoption stage is unlikely to succeed. This is because, if you’re relying on biased, incorrect, or incomplete data, you’ll get bad results. That could mean inaccurate project estimates, under budgeting, or ignoring potential risks.
Lack of security
If you don’t understand your data, you won’t know the best ways to look after it. That can lead to sensitive information being stored in easily-accessible locations, or without the appropriate level of security. This can make your data a tempting target for hackers.
Key steps to implement a data first strategy
Clearly, a data first strategy is a must-have if you want to implement AI in project management. While the amount of changes needed will vary based on which level your company is at, there are a few key steps everyone should follow:
- Get upper management involved. Ideally, you want the CDO (Chief Data Officer) but if this role doesn’t exist, then CTOs or the corporate lead of project management is the next best bet.
- Design your strategy, budget, and plan. By laying out your short- and long-term goals, as well as strategies to achieve them, you can avoid problems further down the line.
- Find the right people. For a data first strategy to succeed, you need experts in both data management and governance. You might hire new staff or bring in consultants to help.
- Invest in infrastructure. Hiring the right people is meaningless without the right technology. At minimum, you’ll need a central location (whether on-site or in the cloud) for storing data.
- Create universal data policies. Reduce the amount of time spent cleaning and validating data by having set policies in place. These policies might include naming conventions, quality conventions, and details on what to keep / discard.
- Training. It’s not enough to simply hire new people - you should train existing staff too. Anyone who interacts with data needs to have a clear understanding of data maturity, as well as their own role in maintaining it.
We all know that AI can help with Project Management. However, not everyone understands that it’s not just AI - it’s also about data. Without a data first strategy, AI can risk your projects, whether through poor decision making or sheer inefficiency. By taking these steps to improve your data maturity, you’ll create the perfect environment for AI - and your business - to thrive.
About the author
Lloyd Skinner, Chief Executive Officer, Greyfly Ltd, is a project professional with 25 plus years of experience working in multiple sectors and projects in both support and delivery roles. For the last two plus years, he has been investigating the use of AI in project management and developing the Greyfly proposition.