How to Run an Artificial Intelligence Project
The following scenario illustrates some of the ways in which project planning for artificial intelligence (AI) projects differs from traditional IT and business projects. My goal in writing this is to give you an idea of what to expect with regards to the project planning process, and to set appropriate expectations regarding projects of this nature. It is not a comprehensive example, and is not intended for use as a how-to guide.
From the perspective of the project owner, projects generally go through the following phases:
- Pre-initiation (I have an idea!)
- IT Initiation (I need some techies…)
- Definition and Planning (Let’s be clear on what we’re doing here.)
- Launch and Execution of the Project (Let’s get this thing going, I have the money!)
- Performance and Controls on the Project (Are we making progress?)
- System Launch (It’s…Alive?)
- Launch business, make money
- Warranty Period (It’s not supposed to do that, fix it.)
- Project Close Out (I guess this is what I bought?)
Before a project is even kicked off, a lot of work should have already been done:
1. The owner/financier came up with a creative (or not so creative) way to make or save money.
2. Someone did a baseline analysis on how that will be accomplished, and what the limitations of the proposal are (hopefully).
Let’s assume the business analysis was done and it looks something like this:
- The idea: “I’m going to automatically classify people’s pictures for them!”
- I guesstimate I can charge $1 per person in the US for this service = $350 million potential!
- I guesstimate that only 3% of people will opt into this service = $350M * .03 = $10.5 million potential
- I guesstimate that we can only reach 10% US population with advertising = 10.5M * .1 = $1.5 million potential
- All of our costs come out to $800k says the business analyst…(1.5M – 800k = 700k) let’s figure out how we get at that $700k potential profit we still see out there!
- The limitation is that this opportunity will only be for six months and it will decay at 100k a month after that…so no pressure
- Let’s start a project to find our market (For the purposes of this article we’ll assume all of the marketing and other business resources are accounted for and ready to start at our whim. Hiring is a completely different issue we won’t address here.)
- Go/No-go decision.
- Do I want to spend the money on a more technical discovery phase to see what it will take to build this thing? If the Business Analyst says there is profit to be made, move forward. If they are super confident, they may try to skip the next phase where you get a more general assessment by technical architects and cost/timeline estimates from those experts. A common situation in projects is that the budget and timeline is set before anyone with a background in these types of projects is engaged
- With projects that have a budget and timeline that are set before getting estimates, it can go a few different ways:
- IT people are engaged and they respond "It'll be tight but we can pull it off…" because if they don't, they don't get the work/contract
- The budget they are given is too big... and they just spend it/bank it
- The budget they are given isn't big enough... and they work their butts off, only to deliver a subpar product, if anything at all
- Charter for the project
- Business goals, loosely defined
- Stakeholders defined, and their education level in AI is at least assessed if not addressed
- General estimate at the highest level, assessed by someone who has worked on a similar AI project purely for charter purposes
Next, develop the Project Charter in more detail to educate everyone involved on what is possible, and what is a stretch. The Charter is important for any project where you are going into a completely new realm: it sets expectations, helps prevent scope creep, and potentially saves a lot of headache as the project progresses and hits blockers, runs into issues, or exceeds expectations in ways that were not intended.
The Charter is a gauge that is set on the project before it even starts receiving resources (monetary or personnel). It’s a measuring stick for the project. Most of the analysis and decision making in this phase is high level, has very broad numbers and generalizations, and tends to be overly optimistic. It is a necessary and sometimes fortune-saving phase of the project even if it is flawed. If you can’t get through this step and justify a budget, you shouldn’t move on to phase 3, where you will do a much deeper dive into the analysis and planning and commit even more money. You can avoid complications if you do the initiation phase properly and receive honest feedback from all parties (How you ensure you have honest feedback is a separate issue beyond the scope of this discussion. If compensation is in any way tied to the project moving forward, the answer will almost always be "Great idea! Let’s do it!")
Questions You Need Answers To
What are the business objectives?
Answer: Build an AI system that:
- Forecasts (Finance, resource management, predicts
- What will the value of variable X be at Y time?
- Useful for making any type of decision
- Customer churn analysis/sales projections/pricing analysis/
- Combines some processes for automation and decision making
- Provides insight
- Representation of data and information in new ways that make more sense, commonly referred to as “Business Intelligence”
- Solves non-linear problems
- Balancing problems, gaming theory, decision matrixes, open ended problem solving
- Recommendation systems, auto encoders
What is your technology stack?
- Are we limited by pre-existing systems that are in place that we’ll have to integrate with?
- Which stack fits best with our objective? R, python, Sas, C++
- Are there technical requirements for performance availability or data integrity?
- Should there be?
- What are your technical skill resources?
- Do we have the people with the skills necessary to achieve this?
- Can we get them?
- How much do they cost?
- Are we gambling on unfamiliar technologies and are we good with that?
What is your budget?
- How much money do we have to work with/are we willing to spend to achieve this?
- Is the Return on Investment of the business objective higher than the cost to implement?
- If not, is it a strategic imitative that will have a halo effect on other initiatives?
- Can the Halo effect be quantified?
What is our timeline for launch?
- How does that impact other initiatives, resources, costs, and the ROI?
- If we had it right now we would make 800k
- If we wait six months it isn’t worth anything.
- Has any of this or something similar been done before that we can leverage?
Go/no-go decision…do you still want to do this project after all of that, even with your estimates?
Deliverables for this Phase
You will have:
- A commitment on budget
- A timeline to target
- Scientific Wild Ass Guess (SWAG) estimates around the major milestones that are hopefully within 20% of reality
- Metrics for those milestones defined so you can measure progress through the definition and planning phases.
The charter will be something that all stakeholders are in agreement on.
At this stage, the “organization” (could be one guy) has gotten through both the business market analysis and past the go/no-go decision point.
If the decision is a YES it’s worth spending the money for an IT Initiation. This decision should be based on the SWAG estimates provided in phase 2, in comparison to the business case return that was provided in phase 1. Together, they can be used to calculate a return on investment (ROI) for the project. If the ROI is negative, I hope you aren’t doing it for the money – but sometimes you aren’t! E.g., Elon Musk and Space X, Most medical research, Academics projects, community development projects, Art…etc.
Next, I'll get into the Definition and Planning Phase, as well as the Execution of the project in phases 3 and 4.