The Young Project Manager

How AI Projects Fail Before They Even Begin

Most AI projects begin with a strong sense of excitement.

A team hears about success stories from another department or a vendor introduces a tool that promises faster results or lower costs. The budget gets approved. The kickoff meeting is full of optimism, maybe even talk of a “transformational” moment.

Everything seems ready for a big step forward.

But then, reality arrives much sooner than anyone expects.

Within a few weeks, people start feeling lost. It is unclear who owns the work. The data is scattered and messy. Confusion spreads.

Sometimes a leader sends a vague message telling everyone to “just try ChatGPT and see what you get.”

After six months, the system is technically live, but almost nobody uses it.

The project slips into the background. Later, in a meeting, people blame “low adoption” for the failure.

But if you look closer, the real problems appeared much earlier.

AI does not usually fail because of what happens during the launch or the technical build.

Most failures begin with the assumptions teams make long before the project starts.

Let me explain what really goes wrong.

The Illusion of Readiness

Many organizations jump into AI using the same thinking they used for past technology projects, like process automation or cloud moves.

They see AI as just another tool to install. But AI is not simple or predictable. It works differently from traditional systems.

AI is based on probabilities, not clear rules. That means even when nothing changes, the results can feel strange or inconsistent.

This unpredictability confuses teams who expect systems to work the same way every day.

The deeper problem is not about technical skills. The problem is about understanding what kind of work AI actually creates.

When you start an AI project, you are not just managing technology. You are also managing behavior, new habits, and sometimes even ethical questions.

If you do not ask those questions at the start, the project takes the wrong shape and quickly loses direction.

Lack of Problem Clarity

Another early mistake is to start with a tool instead of starting with a real problem. Often, a team will say, “Let’s use AI to become more efficient.”

But what does that really mean?

Which process is the focus?

Where exactly are the delays?

What decisions take the most time?

AI is most useful when the problem is narrow and clearly defined. Broad or vague goals usually lead to weak results.

To picture this, imagine fixing a car without knowing which part is broken. You just keep changing pieces and hope the problem disappears.

This is how many AI pilots begin.

The team treats technology as a magic solution. But AI does not solve problems by itself.

It gives people new ways to solve problems, if they know what they are looking for.

No Ownership, No Accountability

In most traditional projects, you know who the sponsor is. There is someone who signs off and makes decisions. AI projects are different.

They sit between strategy, data, technology, and change management. Because of this, teams often avoid naming a real owner.

Or sometimes, they pick someone without the influence to actually move the work forward.

If the person leading the AI effort does not have the trust and authority to clean up data or set realistic goals, the project quickly becomes an experiment with no clear outcome.

People lose interest.

Leaders stop asking for updates.

The work continues, but it is mostly for show.

True ownership is not just about putting a name on a document. Ownership means someone has both the power and the clarity to decide what success looks like, and to adjust the plan when things do not go as expected.

Overpromising, Under-Understanding

A lot of AI projects fail because of unrealistic expectations. This is not only about hype from marketing. Many leaders believe AI will automate everything and bring fast savings.

So they launch a project with big promises to “reduce headcount” or “cut time by half.”

Soon they discover the AI tool requires ongoing supervision, better data, or even changes to other business processes.

Instead of saving time, the project demands even more attention.

AI brings new kinds of work. Teams have to monitor, review, adjust, and often explain results to others.

If no one prepared for this extra work, the whole effort feels like a step backwards. Rather than fixing the plan, leaders often just close the project quietly and move on.

Ignoring Culture and Communication

People naturally distrust what they do not understand. When a new AI system appears with little or no explanation, people worry.

Will this replace my job? Will I be blamed if something goes wrong?

In many workplaces, these questions are not spoken aloud. But the fear is there. When trust is low, adoption is low as well.

Projects that struggle early often skipped the “human” steps. They did not share clear internal updates.

They ignored early doubts and concerns. They never explained what the AI would and would not do.

The silence filled up with anxiety, and that anxiety turned into quiet resistance.

Communication is not a luxury. It is as essential as the code or the data.

Forgetting the Feedback Loop

AI is not something you set up and forget. Yet many teams do exactly that. They launch a tool, send one announcement, and expect people to start using it.

But AI systems depend on feedback to learn and improve. If there is no routine for collecting real user experiences, mistakes, or surprises, the project cannot get better. And if it does not get better, it slowly fades away.

This feedback is not only for the software. It is for the team as well.

What did we notice after one week?

Did anything surprise us after three weeks?

What are people doing with the tool that nobody predicted?

If you are not listening, you are not managing. You are simply watching things drift.

A Better Way to Begin

Successful AI projects usually follow a different pattern.

They do not start by shopping for tools.

They start by asking hard questions.

What exactly are we trying to improve? Who will be involved? What is the true problem we want to solve? What data do we have, and how reliable is it? Who is responsible for the outcome? What will we do if things do not work? Are we prepared for the learning curve that comes with something new?

These questions take time to answer, but that time is a wise investment.

It saves months of confusion later.

AI projects rarely fail because the technology is too complex.

They fail because nobody invested in the work needed to make it useful.

The beginning shapes everything.

If you rush or skip those early steps, the system cannot support itself later.

And once trust is lost, it is very difficult to earn back.

You write them, clean them up, hit send, and then silence. No reactions. No questions. Not even a polite "thanks."

It’s frustrating. And it happens more often than it should, especially when your update is hard to follow, too long, or sounds like it came from a meeting nobody wanted to attend in the first place.

So let’s fix that.

You don’t need to be a brilliant writer. You just need structure, a bit of clarity, and maybe a small push from AI to make your updates easier to read and more likely to be noticed.

But before we start, two quick reminders:

First, protect your data - Do not paste sensitive or confidential information into AI tools unless you know your company’s rules. Some organizations are fine with it. Others are very strict. And even if no one says anything now, it’s still your responsibility to manage information carefully.

Second, these prompts are not magic - They give you a draft, not a final answer. You still need to review, tweak, and make the message sound like it came from a real person. Like you.

Now let’s get to the prompts...

1. Status Update with Context

Use this when you're writing a weekly or biweekly update that needs to focus attention and create alignment.

Input YOU must answer:
What changed since the last update?
[YOUR INPUT]
What is the current status of scope, timeline, budget, and team morale?
[YOUR INPUT]
What is the most important deliverable or decision this week?
[YOUR INPUT]
Are there any blockers or unresolved issues?
[YOUR INPUT]
Who needs to act or be informed?
[YOUR INPUT]

Instruction:
Write a short, focused update that covers only what changed, what matters, and what’s needed. Use four to six sentences. Avoid task lists.

Constraints:
No passive voice. Each sentence must pass the “so what” test. Keep it readable in under 20 seconds

Example:
Last week’s supplier integration failed QA due to unexpected API changes, putting the June 15 launch at risk. Scope remains stable, and morale is high, but timeline is now yellow. The team is focused on restoring API stability and retesting payment by Friday. We are blocked by legal’s SLA approval, needed by Wednesday. If not resolved, we face a full sprint delay.

2. Executive Update Rewriter

Use this when your current draft is too detailed or technical, and your audience is short on time and context.

Input YOU must answer:
What’s the overall project status and why?
[YOUR INPUT]
What are the top two delays or risks?
[YOUR INPUT]
What decisions or support are needed?
[YOUR INPUT]
Who is the audience?
[YOUR INPUT]

Instruction:
Rewrite the update using only bullet points. Each bullet must communicate impact or a decision.

Constraints:
Maximum five bullets. Every bullet must include a verb, a stakeholder, and a consequence. No acronyms unless explained

Example:
Timeline at risk: Vendor delay may shift launch one week; mitigation under review. Legal review pending for SLA; approval needed by Wednesday to stay on track. QA passed for core features; full regression begins Monday. Budget holding, but reserve may be needed if delay exceeds seven days. Request: Confirm go or no-go for pilot by Friday end of day

3. Translate Technical Progress for Business Stakeholders

Use this when you need to explain technical work to people who care about outcomes, not infrastructure.

Input YOU must answer:
What was completed in technical terms?
[YOUR INPUT]
What does this change in terms of delivery or risk?
[YOUR INPUT]
What do you want stakeholders to understand or approve?
[YOUR INPUT]
What happens if they ignore this?
[YOUR INPUT]

Instruction:
Write a three-paragraph update: What happened, using no jargon. Why it matters, using business language. Re-write something technical if needed into simple terms. What we need from them, using a specific request

Constraints:
No unexplained technical terms. You must name a real-world impact (timeline, money, customer, or risk)

Example:
The engineering team completed a full sync between our system and the supplier’s platform. This means product data will now update in real time across all customer channels.This solves a recurring mismatch issue that previously delayed launches and created support overhead. It also sets us up to expand to new markets without duplicating effort.Please confirm that all training content reflects this change by Monday. If not, the go-live date may need to shift.

4. Risk Update with Accountability

Use this when you're reporting a red or yellow item and need people to take it seriously.

Input YOU must answer:
What area is at risk?
[YOUR INPUT]
What is causing the issue?
[YOUR INPUT]
What happens if it’s not fixed?
[YOUR INPUT]
Who owns the fix?
[YOUR INPUT]
What’s the deadline?
[YOUR INPUT]

Instruction:
Write a four-sentence risk update: State the risk. Name the root cause. Describe the consequence. Assign responsibility or action

Constraints:
Write as if the risk already happened. No words like “might,” “could,” or “possibly”. Be clear about who is responsible- Create sense of action for the reader

Example:
Our contract with Vendor X is still unsigned, which now threatens the onboarding timeline. Legal review has been stuck for nine business days with no response. If not approved by Wednesday, the implementation team will stand down and we lose the entire next sprint. Legal must confirm final edits by Tuesday at 3pm to avoid escalation.

5. Stakeholder Engagement

Use this when you need responses, not silence.

Input YOU must answer:
What input or decision is needed?
[YOUR INPUT]
From whom?
[YOUR INPUT]
By when?
[YOUR INPUT]
What happens if no one replies?
[YOUR INPUT]

Instruction:
Write a one-line closer that either demands action or assigns responsibility.

Constraints:
No soft phrasing. Include a consequence. Phrase it so silence equals a decision. Use compelling words to engage and create awareness

Example:
Unless we hear otherwise by Thursday, we’ll proceed with Option A and notify the vendor.

If your updates are still being ignored, the issue isn’t visibility. It’s clarity.

Maybe you’re not being read because you’re not being useful. Maybe you’re not being answered because you haven’t created pressure to respond.

These prompts are designed to help you fix that. They’re not writing aids.

They’re thinking filters. They force relevance, ownership, and speed. If you can’t answer the inputs, you’re not ready to send the update.

Save this. Use it weekly. Share it with your team. Add it to your onboarding for every new project manager.

Don’t let weak communication waste good work.

And if you’re serious about levelling up how you think, lead, and communicate as a PM, subscribe to Project Management Compass.

Let’s raise the standard. One update at a time.

This exercise is simple on paper, but surprisingly tough when you do it honestly.

You just write down your tasks and split them into three categories:

List 1: Tasks AI Can Do (Today, Not Someday)

• Drafting meeting agendas

• Writing follow-up emails

• Preparing risk logs

• Formatting slides and reports

List 2: Tasks Only You Can Do as the Project Manager

• Navigating team conflicts and trade-offs

• Facilitating decisions when no one agrees

• Reading the silent signals in stakeholder meetings

• Making calls when nobody has enough data, but the project can’t wait

List 3: Tasks No One Should Be Doing Anymore

• Over-reporting just to keep people happy

• Chasing people for updates they already gave

• Rewriting meeting notes to make them sound more formal or polished

The Hidden Cost of Staying Stuck in the Wrong Lists

McKinsey’s research shows that knowledge workers spend about 30 percent of their time on tasks that could already be automated with existing tools.

And in project management, this shows up as endless admin tasks, reporting loops, and busy work that adds little to no strategic value.

But the real risk is not that AI will take your job.

The risk is that someone will finally point at all those tasks in List 1 and automate them for you, leaving you exposed because you never built the muscle of focusing on List 2.

And that’s the shift we need to make — not tomorrow, not when the next tool rolls out, but now.

This is not a complex framework. You can do it on a scrap of paper or in your notes app. The point is not the format, but the honesty.

When I do this with teams, I ask them to block 20 minutes, write the lists, and compare them openly.

I’ve seen some of the best conversations in my career happen during these sessions.

People admit they are stuck in busy work. People are realizing they are avoiding the conversations that matter most. People see, sometimes for the first time, where their real value is — and where it isn’t.

If you want to do this for yourself, I suggest you don’t overthink it. Write what comes to your head first.

The gut answers are often the most revealing. And if you’re brave enough, share your List 1 with your team. Let them see where you’re willing to let go.

You might be surprised how many of them were secretly thinking the same.

But why? Well... There’s a lot of noise right now about how AI will change project management.

But honestly, I think we’re asking the wrong questions. Because this is about focusing your energy on the parts of the work only you can do... The human, emotional, complex, leadership moments that make projects succeed or fail.

And if you can’t clearly see those tasks today, that’s the signal to pause and reflect.

Because the longer you stay stuck in Lists 1 and 3, the harder it will be to reclaim your space in List 2 later.

Sometimes, we all need a small, uncomfortable mirror. This one helped me. Maybe it can help you too.

Starting your first project feels exciting. Until it doesn’t.

One moment you’re proud of your new title. The next, you’re sitting in a meeting, hearing words you don’t fully understand, and wondering how everyone else seems to know exactly what’s going on.

And then, people turn to you for answers.

Inside, you’re hoping nobody asks a question you can’t handle.

I know that feeling. Most of us start there.

You try to look confident. You try to act like you belong. But deep down, you’re thinking, “Am I the only one here who has no idea what they’re doing?”

That voice is loud. But here’s the important part: it doesn’t mean you’re failing. It means you care.

It means you’re paying attention.

Confidence Isn’t About Knowing Everything

When I started leading projects, I believed I had to look like I had it all figured out. Smile, nod, write everything down, and hope nobody notices how lost I am. I thought if I looked confident, I would feel confident.

But it didn’t work that way.

Pretending was exhausting. And it didn’t help me get better. What helped was something much simpler: action.

Real confidence grows from doing things. Small things, awkward things, even scary things.

Every time you face something uncomfortable and survive, you build a little more trust in yourself.

When you say, “I don’t know, but I’ll check and come back to you,” you’re not failing. You’re building credibility. With others, and with yourself.

Confidence Comes From Experience, Not Magic

There’s actual science behind this. Albert Bandura, a respected psychologist, called it self-efficacy. In simple words, when you do something challenging and succeed, even a little, your brain starts to believe you can do it again.

Each small success adds to your confidence bank.

Your brain learns through these experiences. It adapts. Thanks to neuroplasticity, every time you take action and get a good result, you’re literally reshaping how your brain reacts to challenges.

But here’s the catch. If you avoid challenges, your brain learns to expect failure. It learns that fear wins.

That’s why even small things, like speaking up in a meeting or taking on a small task, feel huge at the start. Your brain is treating it as a threat. Not because it is, but because it’s unfamiliar.

The good news is, you can train it. Step by step.

Confidence Builds Slowly, But It Builds

One of the biggest mistakes I made was thinking confidence would just arrive one day. Like a switch flipping.

I thought if I kept working, kept waiting, there would be a morning when I would wake up and feel like a perfect project manager. Ready for anything.

That day never came. And honestly, it still hasn’t. But my confidence has grown.

Not from a single moment, but from hundreds of small ones.

Leading my first project meeting. Fixing a missed deadline without hiding. Having tough conversations and realizing they’re not as scary as they seemed.

Confidence builds with repetition. With practice. With showing up even when you feel unsure.

It’s like getting stronger in the gym. You don’t think your way into lifting heavier weights. You lift, struggle, get a little better, and over time, you get stronger.

Same thing here. Action first. Confidence later.

Simple Moves to Build Real Confidence

When you’re new, it’s easy to get overwhelmed by advice. Frameworks, methodologies, templates. But you don’t need complicated tools to build confidence. You need simple habits.

For example:

• Focus on the bigger goal, not just the tasks.
  Remember what the project is trying to achieve. That helps you stay grounded when you get lost in details.

• Build relationships early.
  Get to know your team. Talk to them. Understand what matters to them. Confidence grows faster when you feel connected.

• Keep your plans simple.
  A clear, usable plan is better than a perfect one nobody reads. Focus on what’s next, who is involved, and by when.

• Communicate more than you think is necessary.
  Silence creates doubt. Small, regular updates create trust. Be visible. People respect that.

• Celebrate small wins.
  Every little success matters. Notice them. Recognize them. They build momentum.

None of this requires you to be perfect. You just need to stay in the game.

Stop Trying to Know It All

One of the quickest ways to destroy your confidence is believing you should have all the answers.

I used to think asking questions would make me look weak. I was wrong.

The best project managers I know are not the ones who pretend to know everything. They’re the ones who say, “I don’t know, but I’ll find out.”

Pretending isolates you. Asking questions builds connection.

Your job is not to be an encyclopedia. Your job is to bring people together, solve problems, and deliver results.

That means being curious. Being honest. Being open to learning.

People Matter More Than Perfection

In the end, projects succeed because of people, not because of perfect Gantt charts.

They succeed because teams trust each other. Because someone spotted a risk and spoke up. Because when things got hard, people worked together to fix them.

If you’re new, focus on this:
Technical mistakes can be fixed. Broken trust is much harder to repair.

Invest in relationships early. Be someone people want to work with. Show up with honesty, not ego.

People will forget if you stumbled in a project update.
But they’ll remember if you listened when it mattered.

A Simple Reminder for New PMs

Confidence grows when you keep this in mind:

• You don’t have to know everything.

• Your voice matters, even if you’re new.

• Mistakes are part of the process.

• Small wins are what build momentum.

• People are always more important than processes.

Your Turn: Take One Small Step Today

Reading is fine. But real confidence comes from doing.

So here’s a challenge:
Before today ends, take one small step that feels a bit uncomfortable.

Maybe it’s asking a question you’ve been avoiding.
Maybe it’s sending a simple project update.
Maybe it’s thanking someone for their help.

Pick something. Do it.

It doesn’t need to be big. It just needs to be real.

Because every small action you take is one more step toward becoming a project manager people trust.

Not a perfect one. A real one.

New project, but no real experience?

They still expect you to deliver, right? Yeah, I know the feeling…

And you know what?

That’s exactly where real project managers are born: in the middle of the unknown, which we can call a storm.

I still remember the day I got my first project as a project manager.

It wasn't at a big corporation or a fancy tech company. It was at PMI Rio Grande do Sul, where I had just started volunteering.

The chapter needed a full review of the volunteer process: from onboarding new volunteers to supporting them through their journey until the end.

I said yes because I wanted to learn, but deep inside, I kept thinking, "What if I mess this up? What if people realize I have no idea what I'm doing?"

The first meetings were tough.

I tried to look confident, nodding at the right moments, taking lots of notes.

But it didn’t take long to realize something important: I didn’t need to have all the answers. I wanted, but it was not possible.

What saved me was actually connecting with people.

Listening to their experiences.

Asking for their suggestions.

Slowly, piece by piece, we built something nice together.

And that's the real secret: projects aren't just about tasks and deadlines.

They're about people and progress.

So if you're about to lead your first project, or maybe you’re in the middle of one and feeling that knot in your stomach, let’s walk through how I’d approach it today.

Your Simple Compass: 5 Steps

Leading your first project doesn't have to feel like trying to assemble IKEA furniture without the instructions (which can be a pleasant game, actually).

Let's keep it simple:

Understand the Real Mission: Forget about deliverables for a second. Ask yourself: What’s the real problem we’re solving? What’s the real change we want?

Meet and Map Your People: People matter more than Gantt charts. Who’s involved? Who cares? Who can support you or make your life harder?

Build a Simple Plan: Think sticky notes, not corporate reports. What are the big steps? Who does what? When?

Communicate and Solve: Don’t just report problems. Be the person who brings options. Overcommunicate until it feels almost too much.

Close Strong: Finish what you started. Document lessons, thank your team, and celebrate. Projects aren't over until they’re truly over.

Now, let's bring this back to my real story, because theory is nice, but you and I both know real life is messier.

How It Played Out in Real Life

1. Understand the Real Mission

It wasn't about reviewing documents. It was about making the volunteer experience smoother and more meaningful. That was the real goal.

2. Meet and Map Your People

I talked to everyone I could: current volunteers, onboarding coordinators, chapter directors, even a few people who had recently left. Their feedback wasn’t just helpful, it shaped the entire project.

3. Build a Simple Plan

I made a rough roadmap: interview people, map the journey, spot pain points, propose improvements, validate, and implement. Nothing fancy. Just clear.

4. Communicate and Solve

I gave constant updates, even when things moved slowly. When we hit dead ends (like missing documents from years ago), I didn’t just highlight the problem. I proposed alternatives.

5. Close Strong

We finalized the new process, shared it with the entire chapter, and celebrated with a small gathering. There was even cake. And honestly? That moment of celebrating something we built together still sticks with me.

Let’s Go a Bit Deeper

You might be thinking, "Is this really enough?"

Because everything I just said sounds too simple, right?

Here’s where it gets interesting.

The PMBOK Guide (7th Edition) moved its entire structure to a value delivery system.

Not just about processes, but about outcomes.

Research by PMI reveals that 57% of unsuccessful projects fail due to a breakdown in communication.

It's not the lack of a detailed Gantt chart that kills most projects.

It's silence, assumptions, and missed expectations.

Another important angle comes from "The Five Dysfunctions of a Team" by Patrick Lencioni.

He highlights that trust and healthy conflict are the foundations of any strong team, two things that no "project plan" can create by itself.

In "Drive" by Daniel Pink, he explains that autonomy, mastery, and purpose are what motivate people, not tight deadlines or micromanagement.

When you lead your first project, giving your team clarity about purpose can ignite their motivation far more than any formal kick-off meeting.

The "Standish Group CHAOS Report" famously showed that only about 30% of IT projects succeed.

A major reason?

Lack of user involvement and vague requirements.

Again, people and clarity matter more than complex tools.

Another strong reference is "Scrum: The Art of Doing Twice the Work in Half the Time" by Jeff Sutherland.

He argues that early delivery of working results and rapid feedback loops are better than massive upfront planning.

Even small wins build momentum.

Finally, when we look at PMI’s "Pulse of the Profession" report, one theme stands out year after year: Agile capabilities, soft skills, and emotional intelligence are increasingly more valuable than technical certifications alone.

So no… Leading your first project isn’t about being a "process machine."

It's about leading humans to achieve real results, one real step at a time.

Bring This to Your World

If you’re leading your first project, don’t overcomplicate it.

Start small.

Here's a detailed step-by-step you can follow:

Step 1: Define the Mission

Sit down, alone or with your sponsor. Ask: What real-world problem are we solving? Write it in two sentences. No buzzwords.

Step 2: Map Your People

List everyone involved. Core team. Stakeholders. Skeptics. Influencers. Allies. Get names. Understand their roles and interests.

Step 3: Sketch the Plan

Lay out the major steps. Think phases, not tasks. Big deliverables. Key checkpoints. Assign tentative owners.

Step 4: Build Early Trust

Schedule one-on-ones. Listen more than you talk. Show you’re here to help them succeed, not to micromanage.

Step 5: Share and Adjust

Communicate your rough plan. Ask for feedback. Adjust it openly. Don’t defend it — improve it.

Step 6: Start Small

Pick a small, low-risk part of the project and deliver it fast. Early wins create momentum.

Step 7: Communicate Often

Weekly touchpoints. Visible tracking (even a simple board). Make progress and risks visible without drama.

Step 8: Manage Problems Calmly

When something breaks (and it will), bring solutions, not blame. Own it. Solve it.

Step 9: Capture Lessons Along the Way

Don’t wait for the end. Keep a "lessons" log. Improve as you go.

Step 10: Celebrate and Close

End strong. Celebrate the team. Capture final learnings. Leave everything better than you found it.